Quantcast

Clipsal Iconic Zone 1 Rocker 10 Pack

Vivid White | Clipsal Iconic Zone 1 Rocker 10 Pack

Clipsal Iconic Zone 1 Rocker 10 Pack

Item Number: 40Z1R-VW

Build this product i

Retail
$33.55
RRP (Inc. GST)

Turn your home or business into a more energy efficient space with the Clipsal Iconic Dolly Rocker. With a clearly visible Zone 1 marking, these dolly rockers are perfect for larger spaces as it allows you to turn on the lights or power to one area.

Colour Vivid White (VW)
  • Vivid White 1 PCE

Product Dimensions

Width icon

Width23 mm

Height icon

Height23 mm

Depth icon

Depth9 mm

See full specifications

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Range

Clipsal Iconic

Product or component type

rocker

Colour tint

vivid white (VW)

Physical

Quantity per set

set of 10

Marking

ZONE1

Switch function

2 positions

Height

23 mm

Width

23 mm

Depth

9 mm

REACh Regulation

Reference contains Substances of Very High Concern above the threshold

EU RoHS Directive

Not 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

Others

Unit Type of Package 1

PCE

Number of Units in Package 1

1

Package 1 Weight

14 g

Package 1 Height

9.17 mm

Package 1 width

98 mm

Package 1 Length

175 mm
Show all specifications

Frequently Asked Questions

hide show

What are dimensions of Saturn Z4061 & 4061?

Dimensions for both Z4061 & 4061:

97.5mm (H) x 34mm (W) 31.6mm (D)

 

Starting Register number in Modbus Read functions

Goals and Symptoms

When performing Modbus read commands, it is important to apply the right starting register address in the read function. Otherwise, the wrong register will be accessed from the meter, giving unexpected data for the meter parameter being read.


  • Meter is functioning as expected. The front panel values for voltages and currents are within expected ranges for the system being monitored. However, modbus read functions from a master station (e.g. a PLC) give values that do not correspond to the front panel values.

Facts and Changes

Modbus, modbus rtu, function read, modbus map, holding register, staring register, function 03, modbus read packet

Causes and Fixes

Cause
One probable cause would be that, the modbus function read command is not pointing to the right registers. The modbus protocol requires an offset to be introduced in the starting register address when reading the slaves register.

Resolution

When reading the meter parameters, the Master must send the device a Read Holding Registers packet. This packet must specify a start register and the number of registers to read. When the function read is received, the slave responds with a packet containing the registers in the range defined in the read request.

However, consider the 3710 Modbus map, which states that according to the MODBUS protocol, in response to a request for address 4xxxx, the master reads register xxxx-1 from the slave (3710). For example, a request for register 40011 returns register 10 from the slave.

What does the above statement mean? Why is an offset required?

Holding registers, by default, are defined the 4xxxx range, the first holding register staring at 40001. The starting register in the read packet is, on the other hand, numbered from zero. Hence, the start register zero automatically points to holding register 40001, starting register one points to holding register 40002, etc. The fact that the first holding register is 40001 and not 40000 explains the offset that needs to be introduced in the starting register number.

Hence, considering the 3710 Modbus Map statement, if the Master needs to read register 40011, then the corresponding starting register that needs to be put in the read function would be 10 (0A hex) since register 40011 is the register 10 from the first holding register, 40001:
40001 > Start register 0
40002 > Start register 1
40003 > Start register 2
40004 > Start register 3
40005 > Start register 4
40006 > Start register 5
40007 > Start register 6
40008 > Start register 7
40009 > Start register 8
40010 > Start register 9
40011 > Start register 10

The Modbus Read Request Packet for a master reading 3 registers from a slave with unit ID 100 (64 Hex) and for starting register of 40011 should be:
 

Slave ID
Function
Start Register (40011)
# of Registers
CRC Checksum
64
03
00
0A
00032C3C


To summarize, when looking at a modbus map, the starting register number to be used in the read function:

Start Register = Modbus Register 40001.

 

Original article#12774

Public

All content © 1992-2007 Schneider Electric


Legacy KB System (APS) Data: RESL188799 V1.0, Originally authored by KBAdPM on 11/03/2007, Last Edited by KBAdPM on 11/03/2007
Related ranges: Modbus / JBus

How do I Monitor Analog Input Over-Under Range conditions on a SCADAPack 350?

Only the Scadapack models 314, 334 and 357 (only AI on the 5606 Lower IO board) have register assignments that monitor the out-of-range status for analog inputs.

The only way to monitor if an analog input has failed, would be to monitor the raw input and look for a zero or full scale value.

For a SP350 using a 5V/20mA register assignment and a 4-20mA input:

The screen shot below shows logic that scales the raw value of input 30001 to produce a scaled value in register 40110 (in mA)


With the 5V/20mA register assignment, a count of 32767 will appear when seeing a full scale value or an out of range value. In either scenario, the mA reading will never go above 20mA which is why the threshold has been set to 19.99mA.

For a SP350 using a 10V/40mA register assignment and a 4-20mA input:

The screen shot below shows logic that scales the raw value of input 30001 to produce a scaled value in register 40110 (in mA)

With the 10V/40mA register assignment, register 30001 can now measure beyond 20mA so it is now possible to tell a full scale value apart from an out of range value. Full scale 20mA now corresponds to a raw input value of 16384. The logic is looking for an out of range condition when it sees 20.01mA or greater.

Can you access the fault history in an ATS46 softstart using ModBus?

Issue:
Fault history access in an ATS46 softstart using ModBus.
 
Product Line:
ATS46
 
Environment:
All
 
Cause:
N/A
 
Resolution: 
from the Global Help desk:
``You can access by ModBus with W4090 (from 1 to 4) for the fault number, the value is in W4069 and W4091 is used by the ATS to Recall the fault.``

What I think this means is that if you put a value of 1 in word 4090, the most recent fault will be reported in W4091. If you put a 2 in 4090, you will read the next oldest fault in 4091. 4090 is used as a pointer, and 4091 is used to display the value that is pointed to.


 

Accutech values from ModBUS are close but do not match what is on the display

Problem:

The Accutech field unit display is showing one value but the local HMI is seeing a slightly different value. The value is close but not quite the same and it doesn't seem to fluctuate or show typical noise you might see from a regular analog signal.
 

Solution 1:

One possibility is that the process value is changing faster than the modbus variables are updating. As a battery powered, wireless RF field device, certain communication delays are inherent.
  • The field unit updates it's readings based on the configured Sample Rate (SR).
  • The field unit transmits its values back to the base radio based on the configured Transmit Rate (TR).
  • The PLC or HMI will poll the base radio for data periodically based on it's polling rate (PR).
  • Any RF weakness or interference can also cause retries and resynchronizations to add additional delay.
Note: Sample Rate and Transmit Rate will affect the expected battery life for the Accutech field unit.

These delays can mean that it will take some time for a change in values to make it's way through to an HMI or PLC.
For example, assume SR = 5 seconds, TR = 20 seconds , PR = 60 seconds. The worst case scenario, would involve the process value changing at t = 0. The field unit polls the new value at t = 5 seconds, it then gets transmitted to the base radio twenty seconds alter at t = 25 seconds and the PLC polls it a minute later at t = 85 seconds. The PLC now sees the value from nearly a minute and a half ago.
 

Solution 2:

A second possibility can be caused by a mismatch in the floating-point word-order in combination with a modbus table offset.

The base radio stores its field unit process values as 32-bit floating-point numbers. By default, the base radio stores the FP low word in the low register and the high word in the higher register number (MODBUR ORDER = 3412 by default). SCADAPack RTUs store 32-bit floating point numbers with the word order swapped. That is the FP low word is in the higher register number and the FP high word is in the lower register number. This corresponds to a base radio with MODBUS ORDER = 1234.

In addition to word order, different devices use different conventions for numbering their registers.
In a Base Radio or SCADAPack RTU, the very first holding register in the table (a register offset of 0) is identified as register 40001.
For some other devices, the very first holding register in the table (a register offset of 0) could be identified as register 40000.
This discrepancy can cause the expected register addressing to be off by 1.

These two factors combined can result in seeing a process value that is close but not quite. For example:



The base radio is storing it's temperature value in registers 40015 and 40016 of the base radio and it shows the correct value of 23.33 degrees C.

In the second case with the word order swapped and looking at the register index off by 1, you could come across the value of 23.375 degrees C which is close to the expected value but not quite.

To ensure this isn't the case with a system setup, it is important to poll for all of the field unit registers and examine all of the results.

In the second case, the least significant word will always be FFFF so you won't see tiny fluctuations in the process value that you might expect for an analog value. In fct, you might not see a change until the temperature reaches 23.25 (41B9FFFF)  or 23.5 degrees (41BBFFFF).

Why is the trip C.B. feature not available for Sepam 40?

Issue
The option to select trip CB is not available in the protections.

Product Line
Sepam 40

Resolution
The Trip C.B. feature for ANSI 46 is only available if CB Control is set to ON.


 
Show More