COVER PAINT PROTECTOR SATURN
POWERPOINT & SWITCH PAINT PROTECTOR TRANS
COVER PAINT PROTECTOR SATURN
POWERPOINT & SWITCH PAINT PROTECTOR TRANS

Paint Protector, 250 Pack, Saturn Series, Transparent

Catalogue Number: 4000PP
COVER PAINT PROTECTOR SATURN
POWERPOINT & SWITCH PAINT PROTECTOR TRANS
COVER PAINT PROTECTOR SATURN
POWERPOINT & SWITCH PAINT PROTECTOR TRANS
Colour: Transparent
Colour: Per UOM Std.
  • Transparent 1 PCE
Added to cart

Specifications

hide show
Range of product
Saturn Series 4000
Product brand
Clipsal
Marking
without marking
Sustainable offer status
Green Premium product
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
Circularity Profile
N/A

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • CAD Files and Packs

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

Do the 4000PP suit both the Saturn and Saturn Zen ranges?

Yes, the 4000PP will cover bother ranges.

For more information, please refer to the link:
https://www.clipsal.com/Trade/Products/ProductDetail?catno=4000PP

What is the part number for Saturn paint covers?

4000PP-TR ( sold as a pack of 250)

Will the 2000pp fit the C2000 series?

No, unfortunately you will need to use a C2000PP paint protector.

For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=C2000PP

How do I scale 0 - 4095 to 6400 - 32000 using 984 Ladder Logic?

The following network scales data from 0-4095 to 6400 - 32,000 when 4-20ma (6400 = 4 mA, 32,000 = 20 mA) outputs are required
but a 0-20ma analog output is used. .





Register 400001 and 400002 are used together in the top node of the EMTH Block, where 400001 is
always 0000 data and 400002 is the variable data, 0-4095, to be scaled. Register 400003, displayed in data
format float, is a fixed floating point value that the user enters as 6.25153 (note that two registers are
used to create the floating point value, 400003 & 400004 in this example). Register 400005 (and 400006)
is the floating point result of the integer and floating point multiplication (EMTH block).





The FTOI (Floating Point TO Integer) block converts the floating point result of registers 400005
and 400006 to an integer value in a single register 400007.

The AD16 block adds the top node register 400007 to the middle node constant 6400 and places
the result in register 400009. This register will then map to one of the analog outputs.

The following data screens shows the input values of 0 and 4095 and there corresponding results.





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 scale data from 0-32,000 to 0-4095 using 984 Ladder Logic?

 

The following network scales data from 0-32,000 to 0-4095 for use with analog signals.





 
Register 300001 contains the analog input data (0-32,000).

This data gets BLKM (Block Moved) to register 400002. 

Registers 400001 and 400002 are the top integer nodes of an EMTH (Divide Integer by Floating point) which is divided by registers 400003 and 400004 (display 400003 as data type float), the middle node registers that contain the floating point constant (7.814408).  

The floating point result is found in registers 400005 and 400006 that is then converted by the FTOI
(Floating point TO Integer) Block to register 400007.

Can I tell what the Modbus Plus address of my Modicon PLC is via 984 ladder logic?

Yes, the contents of the address configured in node 2 of the MSTR Instruction Function Code #3 (Get Local Statistics) will give you the Modbus Plus Network address of the PLC.
Below is a example of a MSTR Instruction using Function Code #3 (Get Local Statistics) to get the Modbus Plus address of the PLC

400001 = 3 (Operation Type)
400003 = 1 (length)
400004 = 2 (Offset)
400010 = 2 (Network address of this station)

What is the mounting frame for the 4025H2

 Part code is 4000H2

Will the 5000MP suit the DLT and eDLT?

 The eDLT wall switch range will come with a plate (5000MP) but will be available seperately for 2nd fix. 5000MP is for the eDLT range. The DLT range is ok with standard wall plates and wall clips (154).
Please see following brochure link for more information.
https://www.clipsal.com/Trade/search-results?q=5000mp

What is the part number for Wilco range 400amp 5 pin plug?

Our range of Wilco plugs only goes to 200amps.

What is the part number for a 3 pole 400amp INS load break switch?

The part number for a 3 pole 400amp INS load break switch is - 31110

For further information visit link below:-

https://www.schneider-electric.com.au/en/search/31110
User-added image

Are there paint protectors available for Iconic range?

Yes, there are paint protectors available in packs of 100 for iconic range and the part number is 3000PP.

What is the Run Current and In-Rush current for FLS50LED, LED slimline floodlight 50W 4000K?

FLS50LED has the below details 

-Run current: 0.249A 
-In-rush current: 15A 

Datasheet attached for further reference. 


 

What is the part number for the paint protectors for the 2000 series?

The paint protector for the 2000 series is 2000PP.

What is the Cut-Out, Dimensions and/ or Template for a 4000VH2 quad surround?

Please see the below image for the Dimensions and/ or Template for a 4025H2 quad outlet.

When using Concept, what may cause a 4000h Stop Code on my Momentum I/O Bus CPU?

The 4000h stop code may be generated by a bad I/O map, extended memory error or missing loadable. This error will also occur when a Momentum I/OBus network has a third party Interbus device on the network but undefined. The Concept ModConnect tool must be used to generate a MDC file that will define the module and allow the Concept database to insert this definition in the I/O map configuration. A common symptom of this problem is the program will download and start with no problems with an older computer that has the MDC definitions installed. When the project is moved to another computer without the modules MDC file, the project will report a 4000h error after download/ start. To eliminate this error generate a new MDC file using the Concept Modconnect tool.


What is the part no for the C2000 series paint protection covers?

The part no is C2000PP/50 > pack of 50
or C2000PP > pack of 250

This is the link to the page https://www.clipsal.com/Trade/Products/ProductDetail?catno=C2000PP

User-added image

What is the replacement lamp for a EXITSM?

Unfortunately we do not sell these as spare part you will need to seek a different manufacturer such as osram etc.

The specs are a 4000K, 1.2 Watt LED Tube.
Highly efficient LED lamp: The fitting is equipped with a 1.2W LED tube which provides longer life and lower power consumption.

How can a floating point value be moved into 4XXXX registers in a Quantum PLC with 984 LL?


A floating point value can be moved into 4XXXX registers with the equation network. An example of moving a floating point value of 123.456 into registers 40001 and 40002 is shown below:

 

The “Generic Modbus” application does not provide status bits values in binary

Issue:
The “Generic Modbus” application does not provide status bits values in binary

Product line:
Generic Modbus Application or Similar application


Environment:
Generic Modbus Application or Similar application


Cause:
The “Generic Modbus” application does not provide status bits values in binary


Resolution:
Take the value provided by the application and convert it to binary by using a calculate like the one provided by Windows.  If using the Windows calculator, you may have to change the calculator to scientific or Programmer mode to accomplish this conversion.

Below is a couple of examples from a Galaxy VX:

Example 1:  Register 400002 (16385)

16385 in BIN 100 000 0000 0001

This example has 14 bits and to get to 16 bits two zeros were added to the left (red text)

10 0000 0000 0001 is 0010 0000 0000 0001

 

Example 2:  Register 400010 (512)

512 in BIN 10 0000 0000

This example has 10 bits so six bits needs to be added to the left (red text)

10 0000 0000 is 000 0010 0000 0000



The “Generic Modbus” application does not provide status bits values in binary

Issue:
The “Generic Modbus” application does not provide status bits values in binary


Product line:
Generic Modbus Application or Similar application


Environment:
Generic Modbus Application or Similar application


Cause:
The “Generic Modbus” application does not provide status bits values in binary


Resolution:
Take the value provided by the application and convert it to binary by using a calculate like the one provided by Windows.  If using the Windows calculator, you may have to change the calculator to scientific or Programmer mode to accomplish this conversion.
Below is a couple of examples from a Galaxy VX:
Example 1:  Register 400002 (16385)
16385 in BIN 100 000 0000 0001
This example has 14 bits and to get to 16 bits two zeros were added to the left (red text)
10 0000 0000 0001 is 0010 0000 0000 0001
 
Example 2:  Register 400010 (512)
512 in BIN 10 0000 0000
This example has 10 bits so six bits needs to be added to the left (red text)
10 0000 0000 is 000 0010 0000 0000

 

Does PowerLogic SCADA support waveform data of ION meters?

No, Powerlogic SCADA (PLS) currently does not support the waveform data from ION meters; valid through PLS v7.10 SR3.
Waveforms from the following devices are currently supported as of v7.10 SR3: Circuit Monitor 3000s, Circuit Monitor 4000s, Power Meter 800s, and Sepam 20s, 40s, and 80s.


Legacy KB System (APS) Data: RESL200266 V2.0, Originally authored by KBAdPM on 10/16/2009, Last Edited by MaTh on 12/01/2010
Related ranges: PowerLogic SCADA 7.1

Accutech Modbus Register Mapping

Modbus RTU protocol is supported on the BR10 and BR20 Base Radios. Transmission rates of 9600, 19200, 38400, 57600, 115200 are supported with even, odd or no parity, 8 data bits and 1 or 2 stop bits. The Modbus settings are configured by using the push buttons on the base radio only. The BR10 contains 1 RS-485 port for Modbus communications. The BR20 contains 1 RJ45 connection called the "Short Haul Data" port. This port can be configured for 2-wire RS-485 or 3-wire RS-232 by a dipswich next to the serial port.

The following menu items are used to configure Modbus in the base radio via the push buttons. For a complete menu map of all Accutech Instruments, please reference the Accutech Wireless User Manual that is installed along with Accutech Manager Software an your PC.

BAUD RT - Baud Rate
DEV ID - Modbus Device ID
PARITY - Parity
STOPB - Stob bit selection
MODMAP - Register mapping options (see below)
MODADR - Modbus address of base radio
ORDER - Floating point word order

There are two user options to determine Modbus mapping in the base radio/field units. The MODMAP configuration determines if the mapping will be DEV mode (Device ID) or REG mode (Register)

Device ID Mode

  • Poll for individual devices (Base Radio and Field Units)
  • Modbus Station ID = Base Radio Modbus Station Address + Field Unit RF ID
  • Modbus starting register = 40001

Register Mode

  • Poll single Modbus station ID for complete Accutech network
  • Modbus Station ID = Base Radio Modbus Station Address
  • Field unit Modbus address are multiples of their RF ID
  • Modbus starting register = (Field Unit RF ID * 10) + 40001

Base Radio Registers

Base Radio Holding Register (Device and Register Mapping Modes)

Device ID: 1 To 247 Max.

Address

Description

Register Type

40001

Base Radio Device Type

16-Bit Unsigned Integer

40002

Base Radio Device Status

16-Bit Unsigned Integer

40003

Number of Field Units Expected on the wireless network.

16-Bit Unsigned Integer

40004

Number of Field Units actually online in the wireless network.

16-Bit Unsigned Integer

40005

Online/Offline Status Of Field Units with RFIDs 1-16

16-Bit Unsigned Integer

40006

Online/Offline Status Of Field Units with RFIDs 17-32

16-Bit Unsigned Integer

40007

Online/Offline Status Of Field Units with RFIDs 33-48

16-Bit Unsigned Integer

40008

Online/Offline Status Of Field Units with RFIDs 49-50

16-Bit Unsigned Integer

40009

Diagnostic Counter (increments each second)

16-Bit Unsigned Integer

40010

Reserved For Future Use

16-Bit Unsigned Integer

 

Field Unit Holding Registers

Field Unit operational data is stored in a sequential block of 10 Modbus registers in the Base Radio. The Modbus Station address and the actual register addresses will vary depending on the Modbus Mapping mode set in the base radio. The Modbus Station address and register locations are described below for each Mapping mode.

Device ID Mapping Mode

When DEVMODE is selected, the base radio stores the field unit and base radio operation data (10 Modbus holding registers) in separate Modbus Station addresses. In this mode, the SCADA Host (Modbus Master) needs to send an individual poll request for each field units data and the base radio data. Station addresses are determined using Base Radio Device ID parameter and the Field Units RFID parameter. This mode is suitable for systems using a template for each field unit.

Field Unit Modbus Station Address = Base Radio Device ID + Field Unit RFID

Field Unit Holding Register Addresses

Field Unit Register Description

Register Type

40001 and 40002

Device Type

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40003 and 40004

Device Status

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40005 and 40006

Primary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40007 and 40008

Secondary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40009 and 40010

Tertiary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

1The default floating point format for Modbus database registers is Low Word, High Word. For example if a floating point value is in registers 40001 and 40002 then 40001 is the low word and 40002 is the high word. For SCADAPack controllers 40001 is the high word and 40002 is the low word. The floating point word order is decided by Modbus Floating Point Order of base radio Modbus Communication Configuration.

2Any field unit that is currently offline will return NaN (Not a Number) when queried for its primary, secondary or tertiary measurement value. If a field unit is online, NaN will also be returned for measurement values that do not exist in the device. For example, a field unit providing one measurement will return NaN for its secondary and tertiary values.

Register Mapping Mode

 When REGMODE is selected, the base radio stores the field unit and base radio operation data (10 Modbus holding registers) in sequential blocks of registers located at a single Modbus Station address. The base radio uses register addresses 1 through 10 with subsequent groups of 10 registers used by each field unit. Station address is determined by the base radio Device ID and the Register addresses for each field unit are offset from the base radio registers by a factor of 10 times the field unit RFID parameter. This mode is suitable for a system that wants to poll for multiple field unit devices at once.

Field Unit Modbus Station Address = Base Radio Device ID

Field Unit Holding Register Addresses

Field Unit Register Description

Register Type

40001 + (RFID * 10) and 40002 + (RFID * 10)

Device Type (see list below)

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40003 + (RFID * 10) and 40004 + (RFID * 10)

Device Status (see list below)

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40005 + (RFID * 10) and 40006 + (RFID * 10)

Primary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40007 + (RFID * 10) and 40008 + (RFID * 10)

Secondary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

40009 + (RFID * 10) and 40010 + (RFID * 10)

Tertiary Sensor Value2

Two Modbus registers formatted as a 32-Bit IEEE Floating Point1

 

1The default floating point format for Modbus database registers is Low Word, High Word. For example if a floating point value is in registers 40001 and 40002 then 40001 is the low word and 40002 is the high word. For SCADAPack controllers 40001 is the high word and 40002 is the low word. The floating point word order is decided by Modbus Floating Point Order of base radio Modbus Communication Configuration.

2Any field unit that is currently offline will return NaN (Not a Number) when queried for its primary, secondary or tertiary measurement value. If a field unit is online, NaN will also be returned for measurement values that do not exist in the device. For example, a field unit providing one measurement will return NaN for its secondary and tertiary values.

What is the Colour Light output (CCT) of the CLIFLS20LED Floodlight

The output CCT is 4000K

​How to read Modbus Status bits

Issue:
How to read Modbus Status bits

 

Product line:
All products


Environment:
All products


Cause:
How to read Status bits



Resolution:
Using a Modbus tool like Generic Modbus Tester you receive the values in the two examples below.  The Generic Modbus tester does not provide binary values so the examples below shows the conversion.  If the application used provides binary then keep that part.

 

Below is a couple of examples from a Galaxy VX:

Example 1:  Register 400002 (16385)

16385 in BIN 100 000 0000 0001

This example has 14 bits and to get to 16 bits two zeros were added to the left (red text)

10 0000 0000 0001 is 0010 0000 0000 0001

Below is the mapping of the bits to the Modbus registers to the Galaxy VX.  You start the with zero on the right and end with 15 on the left.


 

Example 2:  Register 400010 (512)

512 in BIN 10 0000 0000

This example has 10 bits so six bits needs to be added to the left (red text)

10 0000 0000 is 000 0010 0000 0000

Below is the mapping of the bits to the Modbus registers to the Galaxy VX.  You start the with zero on the right and end with 15 on the left.

Modbus; How to read Status bits

Issue:
Modbus; How to read Status bits


Product line:
All products


Environment:
All products


Cause:
How to read Status bits


Resolution:
Using a Modbus tool like Generic Modbus Tester you receive the values in the two examples below.  The Generic Modbus tester does not provide binary values so the examples below shows the conversion.  If the application used provides binary then keep that part.
 
Below is a couple of examples from a Galaxy VX:
Example 1:  Register 400002 (16385)
16385 in BIN 100 000 0000 0001
This example has 14 bits and to get to 16 bits two zeros were added to the left (red text)
10 0000 0000 0001 is 0010 0000 0000 0001
Below is the mapping of the bits to the Modbus registers to the Galaxy VX.  You start the with zero on the right and end with 15 on the left.


 
Example 2:  Register 400010 (512)
512 in BIN 10 0000 0000
This example has 10 bits so six bits needs to be added to the left (red text)
10 0000 0000 is 000 0010 0000 0000
Below is the mapping of the bits to the Modbus registers to the Galaxy VX.  You start the with zero on the right and end with 15 on the left.




 

Can I poll 6 Digit Modbus registers with Telepace Studio?

The MSTR and MSIP use a block of registers to store their configurations.

If the MSTR block uses register 41001 in the SCADAPack as it's configuration start register, then :

41001 = Comm port number

41002 = function code

41003 = slave controller address

41004 = slave register address

41005 = master register address

41006 = length

41007 = time out in 0.1s increments

Trying to configure the MSTR block in Telepace prevents you from putting in a slave register address greater than 49999.

Using a PUTU block, you can put an unsigned integer in the range 40001-65535 into register 41004 to indicate the slave register address. It appears as though the program will take the value in register 40004 and subtract 40001 to determine the holding register offset that gets sent in the actual modbus message.

For example, using PUTU to put a value of 50010 into register 40004 would then cause the MSTR block to poll for a holding register with an offset of 10009 in the message which would correspond with a 6 digit address of register 410010.

The largest unsigned integer you could put into register 40004 would be 65535, which would correspond with a 6-digit modbus holding register of 425535.



 

Is it possible to do Ethernet I/O scanning with the Advantys OTB1E0DM9LP Ethernet module?

 

Goals and Symptoms

Yes, you will need to set up the Ethernet I/O scanner in the following way. For this example we are using a Momentum Ethernet processor and Concept.
NOTE: You will want to make sure that the executive in the PLC is up to the latest revision, if not you will not be able to I/O scan.

Causes and Fixes

As noted below the Read Ref Slave address must be 400001 and the Write Ref Slave must be 400101.


What is the colour temperature for the L882WH ?

The colour Temperature for the L882WH is 4000K . This is more of a cool white
For more information regarding this product please visit the Clipsal website on the link provided
https://www.clipsal.com/Trade/search-results?q=l882wh

What are the part#'s for the Panelmate Plus Modbus Plus Interface Board?

The part #'s for the Panelmate Plus Modbus Plus Interface Boards are:
1) MM-PMMP001C - Panelmate Plus 2000 / 3000 / 4000 Modbus Plus Interface, CE
2) MM-PMMP002C - Panelmate Plus 2000 / 3000 / 4000, Dual MB+ Interface, CE
3) MM-PMMP003C - Panelmate Plus 1000 / 1500 Modbus Plus Interface, CE

How SCADAPack's digital input can be used as 32-bit counter and then input for TelePACE FLOW block?

In SCADAPack-s with TelePACE firmware, 32-bit integers are stored in the form: Lower word at lower address, higher word at higher address. If digital input at address 10001 is used to count pulses and ladder logic shown in the attachment, then 32-bit unsigned integer (double word) at address 40009 can be used as input register for FLOW block.
 

How fast can the CM4000T update the analog outputs?

Issue:
A customer would like to know how fast the analog output status for a CM4000T can be updated for use in a high speed application.

Product Line:
CM4000T

Environment:
CM4000 I/O

Resolution:
The analog output statuses are updated once every 100 ms.  If the desired application requires faster update rates the 4000T may not be appropriate.

What size cut-out do i need for a TPDL300 downlight?

You would need a 90mm cut-out for the TPDL series downlight.

Some of the key features are:
  • 3000K and 4000K lamp temperature options
  • 30,000 hours rated lamp life to L70
  • Integral driver
  • Wide trim
  • 90mm cut-out

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

Can a time value be forced into the ET (Elapsed Time) of a Concept IEC timer?


No, If a value is forced into the variable attached to the ET output of the block; it will be updated with the timers internal value when the block is solved.

A variable time is created located to 400001 and it is given an Initial Value of 23 seconds.


The variable is attached to a TON block and downloaded to the controller with Initial Values.



When the controller is started and the block is set to solve the ET output will be updated with the internal time of the block.



Note: This applies to all / most function blocks either in Concept IEC or Unity Pro IEC.


Legacy KB System (APS) Data: RESL177128 V1.0, Originally authored by on , Last Edited by on
Related ranges: Concept

I/O Scanner Offset Inconsistent Issue Across Different PLC Platforms

Goals and Symptoms

To explain users the offset inconsistent issue across different PLC platforms when using Unity Pro software to configure I/O scanner table.

Facts and Changes

Due to the historic heritage reason, The Quantum product line including NOE77100/10/01/11, Quantum Copro 140CPU65150/60 do not support address %mw0 (or 400000). But Premium, M340 product line support address %MW0. So Unity Pro software allows users to put Read/Write index 0 for slave index in case the slave device is a Premium or M340 PRODUCTS.
The consequence is that using Unity Pro software, if the remote slave device is a Quantum product, the Read and Write index number will be increased by 1. If the remote slave device is Premium or M340 product, there is no offset by one.
Several I/O scanner configuration examples are used below for explaining this issue.

· Example 1: NOE77101 I/O scanner configuration table using Concept software

    • Master device: Quantum NOE77101
Slave device: Quantum NOE77111
Read/Write length: 1
Software: Concept V2.6


Offset issue: NO.
Read Ref Master (master address): 400001 (%mw1)
Read Ref Slave (slave address): 400001(%mw1)
Write Ref Master (master address): 400002 (%mw2)
Write Ref Slave (slave address): 400002(%mw2)


· Example 2: NOE77101 I/O scanner configuration table using Unity software
    • Master device: Quantum NOE77101
Slave device: Quantum NOE77111
Read/Write length: 1
Software: Unity V2.3

Offset issue: YES.
Read Master Object (master address): %mw1 (400001)
Read salve address: %mw1 (400001) Read slave Index: 0 the slave device is Quantum NOE, index number automatically increased by 1
Write Master Object (master address): %mw2 (400002)
Write salve address: %mw3 (400003) Write slave Index: 2 the slave device is Quantum NOE, index number automatically increased by 1

· Example 3: Quantum NOE77101 I/O scanner configuration table using Unity software
    • Master device: Quantum NOE77101
      Slave device: 140 CPU65150
Read/Write length: 1
Software: Unity V2.3

Offset issue: YES.
Read Master Object (master address): %mw1 (400001)
Read salve address: %mw1 (400001) Read slave Index: 0 the slave device is Quantum Copro, index number automatically increased by 1
Write Master Object (master address): %mw2 (400002)
Write salve address: %mw3 (400003) Write slave Index: 2 the slave device is Quantum Copro, index number automatically increased by 1

· Example 4: 140 CPU65150 I/O scanner configuration table using Unity software
    • Master device: Quantum 140 CPU65150
Slave device: Premium ETY 5103
Read/Write length: 1
Software: Unity V2.3

Offset issue: NO.
Read master Object (address): %mw1
Read slave address: %mw0 Read slave Index: 0 the slave device is Premium ETY, index number remains the same, no added offset by one.
Write master Object (address): %mw2
Write slave address: %mw2 Write slave Index: 2 the slave device is Premium ETY, index number remains the same, no added offset by one.


· Example 5: ETY5103 I/O scanner configuration table using Unity software
    • Master device: Premium TSX ETY5103
Slave device: NOE77101
Read/Write length: 1
Software: Unity V2.3

Offset issue: YES.
Read Master Object (master address): %mw1
Read salve address: %mw1 (400001) Read slave Index: 0 the slave device is Quantum NOE, index number automatically increased by 1
Write Master Object (master address): %mw2
Write salve address: %mw3 (400003) Write slave Index: 2 the slave device is Quantum NOE, index number automatically increased by 1


In summary, getting the offset by one or not, it all depends on the remote device if accepting address %mw0 or 400000. If yes, it has no offset issue. If no, user will see the index number automatically increased by 1.

Causes and Fixes

Schneider Electric current has no plan to fix this issue because we don't want the large existing customers to change their application if they download the new firmware with the offset change.

Why is there a minimum mains short circuit current rating mentioned in ATV680 datasheets? What is the purpose behind it?

The minimum short circuit current is necessary to ensure the protection by the built-in semiconductor fuses. In case of an internal failure (broken IGBT, short circuit in the DC bus, …) the mains MUST be able to deliver a short circuit current which is big enough to break the fuse.
 
Example (see attached picture):
If an ATV680C16Q4X1 with 400A fuses is supplied by a generator which delivers just 1000A in case of a short circuit, the fuse will take 60 sec (!) to melt. With the recommended minimum short circuit current of 4000A it will take just 2 milliseconds!
 
 

What is the UL Type 1 Conformity Kit for the ATV630 High HP drives?

Issue:
Customer is trying to select a UL Type 1 Conformity Kit from the ATV630 catalog.  The catalog lists two options.
VW3A9212
VW3A9213 (without brake resistor)

Product line:
Altivar 630, ATV630
ATV630C22N4
ATV630C25N4
ATV630C31N4

Environment:
models listed

Cause:
Catalog error

Resolution:
The ATV630 drive cannot use Brake resistors.  So the only available Type 1 Conformity kit is VW3A9213.

 

MGE STS, Galaxy 3000, 4000, 5000 and Galaxy PW; Wiring information for EGX100 to any 66061-supported products

 
 
Issue:
Wiring information for EGX100 to any 66061-supported products


Product line
EGX100 and all products supported by 66061 – STS, Galaxy 3000, 4000, 5000 and Galaxy PW


Environment:
EGX100 and all products supported by 66061 – STS, Galaxy 3000, 4000, 5000 and Galaxy PW


Cause:
Wiring information for EGX100 to any 66061-supported products


Resolution:
The 66061 JBUS/Modbus card is configured for 9600, 8, N and 1.  Slave address is 1 and wiring is 2-wire with no parity and termination.  This assumes only one 66061 card or UPS or STS is connected to the enclosure but if more than one change as required.  The JBUS/Modbus card has two female DB9 connectors.  The DB9 on the right side of the card is RS232 for configuration.  The left side DB9 connector is the RS485 connections that the EGX must be wired to.
 
The EGX Monitoring Enclosure has a CB, power supply and EGX100.  The EGX is configured and has been Modbus communications was factory tested.  The EGX 100 IP address is 169.254.0.10 with subnet mask of 255.255.0.0.  The IP address needs to be configured at the site.  Make sure that the dip switches on the side of the EGX are configured correctly.  One is down (off position) and all others are up. 

 
EGX layout



The wiring of the devices is below and keep in mind that the 66061 JBUS/Modbus card has a female DB9 so a male DB9 cable is required on the UPS/STS.  The male DB9 connector is not supplied with the UPS but a black terminal block is supplied with the EGX.


 


 


 
 

Where to find documentation for the CM4000 series meter?

Issue
Where to find documentation for the CM4000 series meter?

Product Line
CM4000 series (includes models 4000, 4250, 4000T)

Environment
Brochure, Technical Datasheet, Installation Guide, Reference Manual

Cause
Where to download documentation for the CM4000 series meter

Resolution
See the attached CM4000 series meter documentation below:

​What would be an appropriate lighting option for my backyard?

FLS Series

Perfect for general illumination in residential or light commercial buildings. The 4000K colour temperature produces a warmer light output when compared to traditional floodlights, making them suitable for lighting entertainment areas or other spaces that have frequent human traffic.

Features and benefits

  • IP65 rated aluminium die-cast body
  • 4000K lamp temperature
  • High lumen output
  • 36,000 hours rated lamp life to L70
  • 105˚ beam spread
  • Supplied with flex
  • 3-year warranty
For further information please visit https://updates.clipsal.com/ClipsalOnline/Files/Brochures/A0000276.pdf

 

What is the part number for the LED down lights?

There are multiple LED downlights the series is TPDL.
Some of the key features are:
  • 3000K & 4000K Lamp temperatures
  • 30,000 hours rated lamp life to L70
  • 100 degree beam spread
  • Integral driver
  • Wide trim
  • 90mm Cut-Out
  • IP44 rating
  • Easy to install
  • Supplied with flex
  • Able to be hardwired with one or two twin TPS cable
  • Dimmable
For further information please visit https://www.clipsal.com/Trade/search-results?q=TPDL&p=1

Are light fittings attachable on the Caloundra Sweep fans?

You cannot fit a light to the non-light versions of Caloundra range. The only fan that has a light is the C4HS1300L-WE and this light is integrated into the fan, it is not a kit.
This is a 4000K natural white LED. However, if customers prefer a warmer colour temperature, we also sell a 3000K warm white LED array separately (LEDFANKIT-WW).
 

What is the altitude derating for a TeSys D-Line contactor?

Issue:​
What is the altitude derating for a TeSys D-Line contactor?

Product Line:
Digest 177 Section 18 : Contactors and Starters, IEC

Environment:
North American Products

Resolution:
The contactors are fully rated up to 3000 meters. Following are derating multipliers for altitudes above 3000 meters for both voltage and current:

Voltage
3500m x 0.90
4000m x 0.80
4500m x 0.70
5000m x 0.60

Current
3500m x 0.92
4000m x 0.90
4500m x 0.88
5000m x 0.86

For example, an LC1D80 at 5000 meters:
- The maximum rated operational voltage is 1,000V (IEC947-4) and 690V (UL/CSA). At 5000 meters it becomes 1000V x 0.6 = 600V (IEC947-4) and 690V x 0.6 = 414V (UL/CSA).
- The maximum rated operational AC3 current is 80A. At 5000 meters it becomes 80A x 0.86 = 68A.



 

Why is my M1E not IO scanning my Advantys STBNIP2212 island?

Title

 

Issue

 

Product Line

 

Environment

 

Cause

 

Resolution

Ensure that the ethernet network, IP addresses and subnet masks are configured properly and all devices can be pinged.  Now verify that in the M1E IO scanner setup that the 'Read Ref Slave' memory location is set for 45392 and not 40001 as would be the case if scanning a Momentum IO base with an ENT communication adapter.  This is a common error with Advantys STB.

MSTR TCP 'Open Connection' Option

Goals and Symptoms

The purpose of this Resolution is to inform users of Momentum Ethernet processors of an enhancement option to the MSTR function block that allows the TCP connection to remain open.

  •  

Facts and Changes

This resolution describes how to implement the Open Connection option for the MSTR TCP/IP block in the 984LL Exec (v.1.20 and higher) and the MSTR EFB blocks in the IEC Exec (v.1.21 and higher).

Causes and Fixes

984LL MSTR Function Block
A new feature has been added to 984LL Exec. versions 1.20 and higher where power is asserted to the bottom input of the MSTR block. Asserting this go-again input, along with the top enable input, causes the TCP connection to remain open. Once the connection has been established, only Modbus command and response packets are transmitted onto the Ethernet. The only difference is that the repetition rate cannot be specified. It goes as fast as the scan and the target server can accommodate. No dynamic changes to the control block are accepted until the ENABLE (top) input is pulsed.

984LL Function Block Example for Open Connection operation.



IEC MSTR EFB's
A new feature has been added to IEC Exec. versions 1.21 and higher by setting a bit in the Slot_ID of the EFB TCP_IP_ADR. Asserting this go-again bit, along with the TCPIP operation bit causes the TCP connection to remain open. Once the connection has been established, only Modbus command and response packets are transmitted onto the Ethernet. The only difference is that the repetition rate cannot be specified. It goes as fast as the scan and the target server can accommodate.

The Slot_ID of the EFB TCP_IP_ADR has extended usage:
Bit 0 = 0 MBP operation
1 TCPIP operation

Bit 1 = 0 The TCP port will be closed after the transaction has completed (as before)
1 The TCP port will be held open

Bits 2 through 7 are reserved and must remain at 0.

Note Map_Idx = 0 for Momentum M1E Processors

IEC EFB Example for Open Connection operation:
Register 400050 = 3 hex

This feature is only useable for the following EFBs:
CREAD_REG
CREADREG
CWRITE_REG
CWRITEREG
MBP_MSTR (needs to be always kept active: ENABLE=1)

Do NOT use this feature with the following EFBs:
READREG
WRITEREG
READ_REG
WRITE_REG


Legacy KB System (APS) Data: RESL170179 V3.0, Originally authored by on , Last Edited by on
Related ranges: Modicon Momentum

General Tips for Reading Modbus registers from micrologic 6.0 P devices

Answer

Issue:

Having troubles reading the modbus registers from the devices micrologic 6.0 P

Product Line:

Micrologic 6.0P

Environment:

modscan and kepserver; micrologic's menu; Micrologic_RCU

Cause:

EXAMPLE:
*can read the registers from the directions 400000 (300000) until the directions 401000 (or 301000) using a software for PC (modscan and kepserver). Those directions give us some information about baud rate, node, and other communications parameters.
*When trying to read the registers farther of the direction 401000 (301000), returned values are only "32768". More precisely, many registers before the direction 401000 (301000) also read the same.
* There's an option in the micrologic's menu that can't be changed and this is the next: "remote access = NO". It has an "access code= 0000". This also cannot be changed. In the user's guide, its says that "if you want to enable this option you need to call to your sales manager".
* downloaded software from the schneider's webpage called Micrologic_RCU, this software permit us read parameters as currents, power factors (PF's), voltages and the different kinds of power. Don`t know why if this software can read the micrologics's registers why the other ones not. I attach a document where you can see my readings with the readings using the modscan and the readings using Micrologic_RCU.


Resolution:


1. NOT all Modbus registers in use for Micrologic P. For example: value "32768" simply means that it is NOT applicable from register 560 to 571, 578 to581, or 585 to 586 in Micrologic 6.0P

2. Remote setting could be only modified locally via Micrologic P display. It is in Com. setup menu under "History, maintenance and setup" (Wrench sign). Access permit and Access code could be changed here in Remote settings.

3. In the same way, remote control could be only modified locally too. It is in Remote setup menu under "History, maintenance and setup" (Wrench sign). Remote control is set as "manual" by default because the breaker could be close/open by mistake if it is in "Auto" mode to enable it.

4. Those values of currents, power factors (PF's), voltages, and the different kinds of power could be viewed via RCU as well as any other Modbus software as long as you read the right Modbus register number. For example: Using Modscan32, input Address = 1016 (register number); Length = 1; select your Device ID and holding register, you will receive 41016: = . This value represents the phase A current in amps.

5. When opening communication of RCU, it will enable remote access automatically for Micrologic P. It is recommended to use Micrologic software like RCU, RDU, or RSU rather than the third party software to work with Micrologic P or H type relay.

Est ce que les ATV58 e ATV68 peuvent supporter un pic transitoire du reseau superieur ou egale aa 915 V ( allant jusqu' a 6000V selon la norme IEEE C...

Goals and Symptoms

Est ce que les ATV58 e ATV68 peuvent supporter un pic transitoire du réseau supérieur ou égale àà 915 V ( allant jusqu' à 6000V selon la norme IEEE C62.41 - 1991 )

Causes and Fixes

Nos variateurs ne répondent pas à cette norme américaine qui concerne foudre. Nos tests sont faits à 4000v selon EN 61-4-4 soit un train d'ondes de 15 ms avec des pulsations de 50 nanosec, 300 ms de repos puis reprise du cycle. Cycle total de 2 mins en positif et 2 mins en négatif.

How much heat is generated by my Conext system?

Issue:
Questions about how much heat each part of a Conext system uses.

Product Line:
Conext Battery Based Inverters
Conext MPPT Solar Charge Controllers

Environment:
Battery based inverter in an enclosed environment.

Cause:
Proper system design needs to account for system cooling.

Resolution:
The power in BTUs per hour (BTU/hr) is equal to 3.412141633 times the power in watts (W):
P(BTU/hr) = 3.412141633 × P(W)

The efficiency and load of each unit can be used to calculate power loss in watts and then the above formula can be used to convert to BTU/hr.

Conext XW+ 6848
Load (W) Efficiency Loss (W) Heat (BTU/hr)
6800 87% 884 3016
3000 94% 180 614
1500 95% 75 256

Conext SW 4024 NA
92% efficient at 4000W = 320W losses = 1092 BTU/hr

Conext MPPT 60 150
98% efficient at 48V battery at 3500W = 70W losses = 239 BTU/hr

Conext MPPT 80 600
96% efficient at 48V battery at 4800W = 192W losses = 655 BTU/hr
 

Adding the 170ADM85010 and 170ADO83030 I/O bases to the module pick list in Concept.

Goals and Symptoms

The purpose of this resolution is to illustrate the steps necessary to add the 170ADM85010 and 170ADO83030 I/O bases.

Causes and Fixes

The attached MDC files will be needed to add these modules. Put the MDC files in the Concept root directory and remove the .txt file extension.
Once this is done, launch the ModConnect Tool from the Programs menu as seen below:
.
Once the ModConnect tool is running, Choose "Open Installation File"
.
Choose the appropriate MDC file from the window shown below:
.
The next window will allow the user to choose which modules are added. Choose "Add All"
..
The tool will then show the added modules:
.
The tool can be closed. When Concept is launched, these bases will be available from the pick list for Momentum bases.

NOTE: This procedure must be done on every computer where the project will be used. If it is not done on a computer where the project is used, the Momentum controller will not run the project and will come up with a 4000h error code.

How to manually set the clock in a Modicon PLC using Concept software?

Goals and Symptoms

The Time of Day clock in a Modicon PLC consist of 8 registers. The steps below explains how to manually set the clock on the Modicon PLC should you want to synchronize the PLC clock with a HMI or SCADA.

Causes and Fixes


Hardware:
Modicon 984
Quantum
Momentum
Compact

Software:
Modsoft
Proworx PLUS/NXT/32
Concept
 

1)From the Control Register 4x

  • Enter 0000h. This will stop the clock from being updated

 

2) Set the TOD registers 4x + 1 to 4x + 7 to the correct time.

 

3) From the Control Register 4x, enter 8000h (This sets bit 1, Clock value are being set).
If successful, the control Register should display 2000h,

4) From the Control Register 4x

  • Enter 4000h (This sets bit 2, Clock values are being read)
    If successful, the control Register should display 2000h
Show More