SWITCH MECHANISM 3 POSITION BLANK
sw mech 3 position blank
SWITCH MECHANISM 3 POSITION BLANK
sw mech 3 position blank

Switch Mechanism 3 Position Blank

Catalogue Number: 39MPLAIN
Colour White Electric (WE)
  • White Electric 1 PCE 1

Specifications

hide show
Number of Units in Package 1
1
Package 1 Height
21 mm
Package 1 Length
32 mm
Package 1 width
21 mm
Unit Type of Package 1
PCE
Range of product
  • Standard Series
  • Series 30
    • Product brand
      Clipsal
      Device presentation
      basic element
      Control type
      rotary knob
      Number of rocker
      1
      Device mounting
      flush
      Local signalling
      without
      [Ue] rated operational voltage
      250 V AC
      Rated current
      10 A
      Marking
      without marking
      Package 1 Weight
      0.01 kg
      Sustainable offer status
      Green Premium product
      REACh Regulation
      Reference contains Substances of Very High Concern above the threshold
      EU RoHS Directive
      Compliant
      Mercury free
      Yes
      RoHS exemption information
      Yes
      China RoHS Regulation
      Product out of China RoHS scope. Substance declaration for your information
      Environmental Disclosure
      ENVPEP120506EN

      Frequently Asked Questions

      hide show

      Is there a Plain (unlabelled) 3 position rotary switch 30 series mechanism?

      Yes: 39MPLAIN-WE

      What is part no for 39m mech no marking

      Part no 39MPLAIN

      for more information on this part please refer to https://www.clipsal.com/Trade/Products/ProductDetail?catno=39MPLAIN

      User-added image

      What is the part number for the Clipsal 3 position rotary switch with no engraving in white?

      The part number is 39MPLAIN-WE.

      See attached.

       

      What is the Clipsal part number for a 3 position switch mechanism with no writing?

      The part number for a 3 position switch mechanism with no writing is a 39MPLAIN-*
      * =Colour code e.g. 39MPLAIN-WE is White Electric

      Some of the key features are:
      • 3 Position Blank
      • 10A Rated
      • 240V AC
      • 30 Series Style Mechanism
      • No Label
      • Various Colours Available.



       

      What is the product code for the 30 Series PLAIN 3 position switch?

      The part number for a 3 position switch mechanism with no writing is a 39MPLAIN-*
      * =Colour code e.g. 39MPLAIN-WE is White Electric

      Some of the key features are:
      • 3 Position Blank
      • 10A Rated
      • 240V AC
      • 30 Series Style Mechanism
      • No Label
      • Various Colours Available.
      For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=39MPLAIN

      How to edit the message related to ANSI events shown on Vista and Web applications for Sepam in Power Monitoring Expert PME8.1

      Customer Request
      Why the alarms under the PME tab Alarms only shows the ANSI number for Sepam alarms.
      The steps below explain how to edit those events to add more detail in the description.
      Example, Instead of "ANSI 50_51 Unit 2 Pickup Status" display "ANSI 50_51 Unit 1 - Phase overcurrent"

      Prior to start
      The following steps require manual changes on every “.ion” for each SEPAM series files (Located at System\translators folder) and [dbo].[EventString] table (ION_Data DB) so:
      • Make backup of your databases
      • Make backup of your original  .ion files (Located at System\translators folder) for each Sepam
      • I might suggest stopping all ION and Application Modules services, doing the changes according the scenarios described below.
      • If you work with second scenario (explain below) make sure that message match in ION file and database.

      Overview
      The description for the Sepam events are in “.ion” file.  You will need to identify each event you would like to edit. As example, refer to picture below: (Clue: they include the word “Status”)

       
       
      So, in *.ion file the first event from the picture will look like :

       
      When a new PME System is installed, the [dbo].[EventString] table is empty.  Once a specific event is logged in database for first time, it will create a record associated with the “event type” according the description specified in ion file.  If an event with same description is generated later,  [dbo].[EventString] won’t be modified and will use the information that is already there.
      To identify in your system which ANSI events has occurred at least once in your system, you can run this query:
      USE [ION_Data]
      GO
       
      SELECT [ID]
            ,[String]
            ,[QuantityID]
            ,[ShortString]
        FROM [dbo].[EventString]
        WHERE String like '%ANSI%'
      GO
      All events that you get listed after running the query, means you will need to do changes also on [dbo].[EventString] table.  

      Scenarios (Full description included in the PDF attached)
      Scenario 1. If specific event is not yet in database, is sufficient to edit only the .ion file for each sepam (System\translator). Events will reflect changes in Webapp and Vista.
      (Prior any change, I would recommend to contact Technical support to ask if there is a new version of driver that included the changes)

      Scenario 2. If a event message has been already recorded in [dbo].[EventString], it must be edited also there. This will be reflected in old and new events.

      Scenario 3. If a event message has been already recorded in [dbo].[EventString] and the string is not edited (only the ion file is edited), a new record will appear in the EventString table. Changes will be reflected only in new events. Old events will show original message

       
      Final recommendations

      Changes might be time consuming and those required high concentration. Make the changes in chunks; always make sure that services are not running while doing any change.  If observe any issue, restore to previous known and working stage. 
      L4 has also logged PCR number – 67341, to request this change goes into the product.  Deadline unknown. So, developer recommends going ahead and making the required edits in the .ion file and in the database so that your customer sees what they would like. 
      Show More