switch 1gang key operated

SWITCH 1 GANG KEY OPERATED

Catalogue Number: 31VK1
switch 1gang key operated
Colour: White Electric
Colour: Per UOM Std.
  • White Electric 1 PCE 1

Specifications

hide show
Range of product
Standard Series
Product brand
Clipsal
Device presentation
basic element with full cover plate
Switch function
1-way
Actuator
key
Local signalling
without
[Ue] rated operational voltage
250 V AC
Rated current
  • 20 A
  • 16 AX, fluorescent lamp
    • Marking
      ON-OFF
      EU RoHS Directive
      Compliant
      Circularity Profile
      N/A

      Documents & downloads

      hide show
      Filter items
      • All

      • CAD Files and Packs

      • Installation Instruction

      • Product Environmental

      • Specifications

      • Certificates (MSDS)

      Frequently Asked Questions

      hide show

      Are spare keys available for part number 31VK1?

      Keys can be provided as special order.

      In the 31VK1 series can the key be removed in the " on " position ?

      No , to remove the key in the " on position a 31VK2 is required , 31VK1 will only allow key removal in the " Off " position.

      Can i get multipule 31VK1 switches with the same key?

      Yes, you can get multiple 31VK1 switches with the same key.
      If you put CK after the part number they come with the same key.

      Some of the key features are:
      • Key Operated Switches
      • Common Keyed
      • Locks in off position

      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=31VK1CK

       

      Do you offer a key switch like the 31VK2 but in the 2000 Series?

      No, Unfortunately we do not offer a key switch in the 2000 series. The only series we offer a key switch is the Standard Series and the industrial 56 Series.

      Is there a lockable double GPO in any residential range?

      No there isn't but you can install a 31VK1, upstream from the GPO and control the power to it that way...

      In the 31VK switches what is the difference between a K1 and K2?

      The 31VK1 can have the key removed in the OFF position only while in the 31VK2 the key can be removed in both the ON and OFF positions.

      For further information please visit https://www.clipsal.com/Trade/search-results?q=31VK

      Can the key be pulled out in both ON and OFF position in 31VK2 and 31VK2/2 key operated switches?

      Yes, the key can be pulled out in both ON and OFF position in 31VK2  (one way) and 31VK2/2 (two way) key operated switches. They lock in ON and OFF position
      For further information, please visit
      https://www.clipsal.com/Trade/Products/ProductDetail?catno=31VK2
      https://www.clipsal.com/Trade/Products/ProductDetail?catno=31VK2/2
      User-added image

      Can the key switches from the 31VK series be removed and placed onto a 4 gang plate?

      No, unfortunately the key switch mechanisms are not removeable and therefore cannot be put onto any other plates.
      Some of the key features for the 31VK Series are:
      • 1 gang
      • Dimension: 115 mm Length x 73 mm Width x 11 mm Depth
      • Mounting centers: 84 mm
      • Common keyed switch
      • Locks in on and off position
      For further information please visit https://www.clipsal.com/Trade/search-results?q=31VK%20Series
       

       

      What is the dimension of 31VA, 32VA, 33VA, 34VA, 35V and 36VA standard sized vertical flush switches?

      31VA, 32VA,  33VA,  34VA,  35VA and 36VA standard sized vertical flush switches have a dimension of 115mm(length) x 73mm(width) x 11mm(depth). Mounting centres are 84mm apart. The switches are rated to 250V AC, 10A, 1 way/ 2 way.
      For further information, please visit https://updates.clipsal.com/ClipsalOnline/Files/Brochures/A0000108.pdf

       

      What is the part number for the key only for the 2036VKT4?

      The part number for the key only for the 2036VKT4 is 2036VKT.

      Some of the key features are:
      • To suit 2036VKT and 36VKT series switches
      For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=2036VKT
       

      When polling dual registers in InfraStruXure Central 6.0, both registers must be polled together.

      Issue:

      When polling dual registers in InfraStruXure Central / StruxureWare Data Center Expert, both registers must be polled together.

      Product Line:

      InfraStruXure Central / StruxureWare Data Center Expert

      Environment:

      Modbus communications

      Cause:

      Modbus registers are limited in size, which limits the values they can store and return to a BMS. Unsigned values can not exceed 65535. Because some values returned by ISXC may be greater than this maximum value, we have created the ability to use 2 registers together as a pair to allow for this larger output. If you choose to configure 31001 as a dual register, it will encompass 31001 and 31002.

      Resolution:

      When polling these registers, poll both 31001 and 31002 (or whatever register pair you have set up this way) during the same poll. Failure to do so will return invalid results.

      Can StruxureWare Data Center Expert output a 32 bit register with its Modbus output?

      Issue:

      A single register in StruxureWare Data Center Expert's modbus output is limited to 16 bit.

      Product Line:

      StruxureWare Central / StruxureWare Data center Expert

      Environment:

      StruxureWare Central any version
      StruxureWare Data center Expert any version

      Cause:

      The output of a single register for StruxureWare is a 16 bit unsigned integer. This means that any value larger than 65535 can not be handled by a single register. This includes values lower than 65535 that report with a decimal such as 6553.5. DCE will output 65535 but your BMS will need to divide by 10 in such cases.

      Resolution:

      We can not output a 32 bit register in StruxureWare. To overcome this limitation, StruxureWare Data Center Expert can be configured to output a value to 2 registers. This must be configured during the initial setup for the output of each register. StruxureWare does not know which registers may be too large for an individual register so each must be done manually. Each should be polled a 16 bit unsigned integer

      To configure this option, go to the system menu and building management settings. Select the device that you will be using and choose modify device settings. If you double click any register, you get the option to "Edit the Slave Sensor Register Value" which is not necessary and you get the option to "Edit the number of registers used for this sensor". This second field can take a value of either 1 or 2. For values above 65535, you must enter the number 2 and hit OK. If the register chosen was 31000, the next available register will now be 31002. The sensor that may have been set to use 31001 will now change. This is also why this should be done upon initial setup as if the system is already configured and a register is changed, the polling software must be reconfigured with the new registers.

      If you set 31000 to a double register, you then need to poll 31000 and 31001. you then take the 1st register and left shift the first register (31000) by 16. In binary, it would look like this:

      Assuming a value of 131071, a 32 bit register would return:
      00000000000000011111111111111111

      With 2 registers, you must poll both.
      31000 returns 0000000000000001 If this were a single register, = 1
      31001 returns 1111111111111111 = 65535

      With 2 registers however, you must left shift the 1st register and add it to the second.

      00000000000000010000000000000000 is the 1st register left shifted by 16 and is equal to 65536.
      Add this value to the value returned from the second register:
      1111111111111111 = 65535


      Now you have a 32 bit number capable of holding values up to 4,294,967,295
      00000000000000011111111111111111 = 65535 + 65536 = 131071

      This math must all done on the side of the querying application.
       

      How to I monitor NetBotz alarms using Modbus?

      Issue:
      Monitoring alarms on NetBotz using Modbus.
       
      Product Line:
      NetBotz
       
      Environment:
      NetBotz 550
      NetBotz 570
      NetBotz 450 (with Advanced Software Pack)
      NetBotz 455 (with Advanced Software Pack)
       
       
      Cause:
      This is just a guide showing how to monitor NetBotz events using Modbus. Modbus output is not available on the 4xx units by default.
       
      Resolution:
       
      In this example, I have configured a NetBots 570 with a rack access pod NBPD0171. I want to see when there is a forced entry into a rack door being monitored by this NetBotz configuration. Any supported firmware should work but in this case, I have used version 4.5.2.
      There is no way using Modbus to know the exact error message. Based on the return values and the register maps, you can tell what sensor is in an error state and you can tell what level of event is occurring. Let me first state that this mimics the DCE modbus output and you can use the following document (at least the beginning of it) to figure out the level of alarm:
      https://www.apcmedia.com/salestools/JRUK-7R4L9N/JRUK-7R4L9N_R3_EN.pdf?sdirect=true
      This is app note 156 and the link may change over time.
       
      First, Enable the Modbus output on the “Modbus Slave Communications” applet in NetBotz Advanced View (AV). On a 4xx unit, you must first install the advanced software pack. On a 5xx unit, this is enabled by default. 3xx units and older version 2 units does not support this feature.

      This example is using Modbus over TCP but there is a serial option. Please see the user manual for your unit as to how to use the serial connections.
       
      Next, using the ”Modbus Slave System” applet in AV, find the appropriate pod. In this case, I am using Rack Access Pod 170 (03)

       
      Click “Modify Pod Settings” and you will be able to give the pod a slave address and create a register map for all it’s sensors:


      After this configuration, you can view and subsequently export the register map back on the “Modbus Slave System” page.
      You will see the alarms configured this way (and more):
      all   30992(0x7910)  Alarm #03                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
       all   30994(0x7912)  Alarm #02                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
       all   30996(0x7914)  Alarm #01                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor

      You will also see each pod as it’s own slave. Here you can see the main unit as slave 1 and the NetBotz 170 pod as slave 2:
       
      001   31000(0x7918)  NetBotz Rack Monitor 570:Ethernet Link Status                     002     INT16        RO      Value - 0(Down), 1(Up)
       001   31002(0x791a)  NetBotz Rack Monitor 570:A-Link Bus Power                         002     INT16        RO      Value - 0(OK), 1(Overloaded)
       
       002   31000(0x7918)  Rack Access Pod 170 (03):Handle  (2)                              002     INT16        RO      Value - 0(Up), 1(Down)
       002   31002(0x791a)  Rack Access Pod 170 (03):Handle  (1)                              002     INT16        RO      Value - 0(Up), 1(Down)
       002   31004(0x791c)  Rack Access Pod 170 (03):Lock  (1)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
       002   31006(0x791e)  Rack Access Pod 170 (03):Reader  (2)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
       002   31008(0x7920)  Rack Access Pod 170 (03):Reader  (1)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
       002   31010(0x7922)  Rack Access Pod 170 (03):Door  (1)                                002     INT16        RO      Value - 0(Open), 1(Closed)
       002   31012(0x7924)  Rack Access Pod 170 (03):Lock  (2)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
       
      Please note that each register is actually listed as 2 numbers higher than the last. This is because each sensor is configured as 2 registers. If you're looking for data on a specific register say 31000, you actually have to pull 31000 and 31001. Note the register in bold is 31010. To get the data for this sensor, you need to pull 31010 and 31011. It also shows this is the door sensor and the value should be 0 for open and 1 for closed. Knowledge base FA214410 can assist if you’re unsure how to use dual registers but it should not be necessary in this specific instance.
       
      Next, when you poll for alarms, you poll register 30999. This  shows how many alarms there are. Register 30998 shows the highest severity of the alarms if there are multiple. For each alarm, you should read 2 registers back. In this case there is 1 alarm so reading 2 registers before the 30998 is 30997 and 30996.
       
      In this image from AV, you can see the door is open and in an error state:

       
      Upon polling the device’s IP and slave address 2, you can see that 31010 and 31011 (31011 is the important one) is reading 0. This means from the register map that the door is open. Value - 0(Open), 1(Closed)
       

      Here is what that same register looks like if I close the door:

       
       
      Putting the door back in alarm, you can see that 30999 is 1 meaning there is 1 error and 30998 is 2 which means it is level 2 (error)....the latter is defined in the DCE app note 156 linked above.

       
      The register 30997 above reports the sensor. The return is 31010. This matches the register on that door sensor as shown in the register map. The register 30996 reports the actual error. This is also defined in the DCE app note. It's in HEX in the app note so you have to show the return in hex as I am doing here:

       
      Note that 30996  is reporting 000E. If you check the device alarm codes here (again from app note 156), you'll see that 000E relates to "General Device Alarm":

       
      So with this information, I opened a door with a locked handle and the information I pulled via Modbus shows that sensor (register) 31010  is in an alarm state of general device alarm and it is an error level. Looking at the register map I can tell that 31010 (remember, it's 2 registers on a sensor) is a door sensor and since it's return is 0, the door is open. You can also check the other sensors such as handle to see if it is down or check the lock to ensure it is locked etc.