MASTER YOUR CASTLE with your new build or reno project
Enter competition
BOX PVC WEATHERPROOF
box pvc weatherproof
BOX PVC WEATHERPROOF
box pvc weatherproof

255

Weather Protective Box, 137x110x77mm, With Clear Lid and Locking Provision

BOX PVC WEATHERPROOF
box pvc weatherproof
BOX PVC WEATHERPROOF
box pvc weatherproof
Colour: Grey
Colour: Per UOM Std.
  • Grey 1 PCE
Added to cart
Successfully added, you can view your cart here

Key Features & Specifications

hide show
  • Dimension: 137 mm Length x 110 mm Width x 77 mm Depth
  • Horizontal and vertical mounting direction
  • With clear lid and locking provision
Product brand
Clipsal
Enclosure type
weatherproof enclosure
Shape
rectangular
Device mounting
surface
Material
PVC (polyvinyl chloride)
Length
137 mm
Width
110 mm
Depth
77 mm
EU RoHS Directive
Compliant
Toxic heavy metal free
Yes
Mercury free
Yes
RoHS exemption information
Yes
China RoHS Regulation
 Pro-active China RoHS declaration (out of China RoHS legal scope)
Circularity Profile
N/A

Documents & downloads

hide show
Filter items
  • All

  • CAD Files and Packs

  • Product Brochures

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

Frequently Asked Questions

hide show

What is the part number for the flap of 255 as a spare?

The part number for the flap of 255 as a spare is 255FLAP-TR.

What is the part number for flap to suit 255?

The part number for flap to suit 255 is 255FLAP-TR.

Does a 2025RCD30-WE fit into a 255 weather protected box?

Yes, the 2025RCD30-WE will fit into a 255 weather protected box.The 2025RCD30-WE is 27mm deep and the 255 has 35mm depth. The bottom screwed plug will need to be shortened if not used as a cable entry.

Is part no 255 available in shallow version

There is not a shallow version of part no 255 available

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


User-added image

Vamp 255 communications maps

Issue    
Need the register list for my VAMP relay.

Product Line
Vamp 255

Resolution
See the attached files for the VAMP 255 communications maps, this includes maps for:
Modbus
Profibus
SPA bus
DNP3
IEC101
IEC103
Modbus Master
ProfibusDP

Note:  Latest information is available in m.vamp.fi

Will Zen switch plate fit in 223H and 255 enclosures?

Yes, Zen switch plates will fit in 255 as it has a depth of 77mm. It will not fit in 233H as it has a depth of 29mm only.

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

https://www.clipsal.com/Trade/Products/ProductDetail?catno=255

 

What is the operating voltage for the Vamp 255 digital inputs?

Issue: Need to know the operating voltage of the Vamp 255 digital inputs.

Product Line: Vamp 255

Resolution: The Vamp 255 has 2 sets of digital inputs. Digital inputs 1-6 are internally wetted with 48Vdc. The other 12 digital inputs operating voltage is defined by the part number ordering code:
A = 40 - 265 VAC/VDC
B = 18 - 36 VDC
C = 40 - 265 VAC/VDC + ARC Protection
D =  18 - 36 VDC + ARC Protection
E = 40 - 265 VAC/VDC + D19, DI20 + ARC channel
F = 18 - 36 VDC + D19, DI20 + ARC channel

Keywords: Vamp 255, Vamp 255 digital inputs, Vamp 255 operating voltage

Can you get the flap / lid only for the 255 weatherproof enclosure?

Yes, the part number for the flap / lid is 255FLAP-TR

What is part number for lid to suit 255?

Part number is actually 255FLAP -TR

What are the dimensions for a PDL Thermosafe heater?

PDL no longer supplies the Thermosafe range, or any heating appliances.

255 x 362 is the cutout size for the flush mount box.
See attached pdf for more.

 

What is the part number for a replacement flap for the 255?

The part number for a replacement flap for the 255 is - 255FLAP

For further information , visit link below:-
https://www.clipsal.com/Trade/search-results?q=255FLAP

What is the IP rating of the 255?

The IP rating of the 255 is IP53.

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

Metasys Communication with ION7650

Issue
Metasys does not establish communication with an ION7650.  The ION7650 is a replacement for an ION7600.

Product Line
Metasys, Johnson Controls, ION7650

Environment
Metasys, Johnson Controls

Cause
Modbus/TCP is a Modbus protocol variant that defines the packet structure and connection port (port 502) for the industry standard TCP/IP protocol. The Modbus ID for Modbus/TCP communication is 255 in an ION7650 meter while it is 100 for an ION7600.

Resolution
In Metasys the Modbus address should be changed from 100 to 255 which corresponds to the new Modbus ID for ION7650.
 

PM5320 and PM5340 meter not communicating

Issue
PM5320 and PM5340 meter not communicating. The Meter doesn't communicate with Modscan tool or ION Setup. 


Product Line
PM5320
PM5340

Environment
Ethernet Communications

Resolution
As per Modbus TCP/IP standards unit id for standalone meter will be 255.  The unit id of PM5320 and PM5340 meter is 255 and it cannot be changed.

Note: The Slave Id of PM5320 and PM5340 cannot be changed.

Is it possible to add 255 as the "Remote ID" for PM5340 as a Remote Device Connection in EGX300

Issue:
- For  EGX300 firwmare 4.37 and lower, it is not possible to monitor PM5340 over Modbus TCP/IP using "Remote Device Connections" function.
- PM5340 is a meter with Ethernet communications only. It's device ID is set to 255.
- If 255 is added as the "Remote ID" under "Device List", the "Remote ID" will be blank after clicking "Apply"

Product Line:
EGX300
PM5340

Environment:
EGX300 web page- Remote Device Connections

Cause:
The EGX300 firmware 4.370 and lower does not support remote ID of 255.

Resolution:
- Remote Device Connection monitoring of PM5340 (Remote ID:255) using an EGX300 is not supported by the current EGX300 firmware (v4.37). The next firmware release will support "Remote ID" of 255.  For the latest version of firmware for the EGX300 please see FA242399.

Is there an alternative for the Neo switch?

Yes, the nearest alternative is the Saturn series C-bus range.

Some of the key features are:
  • Glass fascia
  • Mounting centres: 84 mm
  • Operating temperature range: 0 to 45 deg C
  • Dimmer control: 255 possible levels
  • Dimensions: rectangle 116 x 76 mm
  • C-bus connection: one terminal block to accommodate 0.2 - 1.5 sq mm(24-16 AWG)


For further information please visit https://www.clipsal.com/Trade/Products/Integrated-Systems/C-Bus-Input-Units/Wall-Switches
 

 

SoMachine Basic FB send receive SMS: Com Error 255 with Oper Error 16

OperError Codes when CommError Code is 255 (Message refused) 
 
   Values   Operation
 
16
  Phone number of the received message not matching with the list (white list protection)
17
Received message doesn’t match with the cmd list (issued only if the sender phone number matches with the one entry of the phone list)

Solution:
16 : Write the Phone number list with international notation, exemple: for 0518497647 use 33518497647  where 33 is the international code number of the country.
17 : The received message must be the same as the one configured (Case sensitive)

 

What is the ID number of Ethernet enabled ION meters for PowerLogic SCADA?

Issue
ID number is not known for ION Meters connected by Ethernet in  Power Scada Expert

Product Line
Power Scada Expert 7.20
Power Scada Expert 7.40
Power Scada Expert 8.0

Environment
Power Scada Expert with Ethernet connected ION meters 

Cause
ID number is not known

Resolution
Try 255 or 100 for the ID number. One of these is likely to work since ION devices default to one or the other of these two numbers.

Why do some registers in meters read -32768?

Product Line
PowerLogic Meters

Environment
Register Readings

Resolution
There are two situations that will cause a register in a PowerLogic Circuit Monitor, Power Meter, or other PowerLogic device to contain a value of -32768.

  1. When there is no input (voltage or current) to calculate or measure a metered value.
  2. When the register value is non-applicable for the mode of the meter.
  3. When you are reading the wrong unit ID of an Ethernet device, i.e., unit ID 1 instead of 255 on a PM5560

Example: The frequency register in a CM4250 will read -32768 when no voltage or current is present.

Note: System Manager Software (SMS) will indicated N/A when a register value contains the value -32768 and Power Monitoring Expert (PME) 8.1 will show 0.

What is the Unit ID in ION Setup for a PM5300 series meter that is connected by Ethernet?

Issue
What is the Unit ID in ION Setup for a PM5300 series meter that is connected by Ethernet?

Product Line
PM53xx Meters

Environment
Connecting PM53xx series meter in ION Setup or Modbus Tester.

Cause
Unit ID or Unique Modbus Address is required to read data from ION Setup or Modbus Tester

Resolution
Unit ID is hardcoded to 255 when connecting to the PM53xx by Ethernet directly.

Does the 5082NL fascia come complete with the buttons?

The 5082NL fascia does not come complete with the buttons. If you require the buttons you will need to buy the entire unit.
Some of the key features are:
  • 2 gang
  • Glass fascia
  • Mounting centres: 84 mm
  • Operating temperature range: 0 to 45 deg C
  • Dimmer control: 255 possible levels
  • Dimensions: rectangle 116 x 76 mm
  • C-bus connection: one terminal block to accommodate 0.2 - 1.5 sq mm(24-16 AWG)
  • An inbuilt non-volatile memory retains programmed information of the unit in the event of a power failure
  • LED gang indicators provide illumination and status feedback
  • programmed via learn mode or the c-bus toolkit software
  • C-bus learn enabled
For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=5082NL


 

What is the full switch to suit the Facsia 5082F-PW?

The full switch to suit the Facsia 5082F-PW is a 5082NL-PW.
Some of the key features are:
  • 2 gang
  • Glass fascia
  • Mounting centres: 84 mm
  • Operating temperature range: 0 to 45 deg C
  • Dimmer control: 255 possible levels
  • Dimensions: rectangle 116 x 76 mm
  • C-bus connection: one terminal block to accommodate 0.2 - 1.5 sq mm(24-16 AWG)
  • An inbuilt non-volatile memory retains programmed information of the unit in the event of a power failure
  • LED gang indicators provide illumination and status feedback
  • programmed via learn mode or the c-bus toolkit software
  • C-bus learn enabled
For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=5082NL





 

How it can be integrated Sepam Protection Relays using Sepam multi-protocol communication interfaces ACE850 ?

Com'X and ACE850 can communicated over Modbus TCP/IP protocol, ACE850 is not a Com'X library native device,
in many application where Sepam 40(fw version > 7.00), or Sepam 80(fw > 6.00) communication network
has been built using ACE850, it will be able to communicate with Com'X via the following configuration:

   1. From the Ethernet Devices Menu select "Generic Modbus TCP to Serial Gateway"
   2. Configure the Gateway with the IP Address of the ACE850
   3. From the Modbus Serial Devices Menu select the appropriate Sepam
   4. For the Slave ID, enter "the Unit-Id 255 or any value in the range 1-247"
 

What is the mounting hole size required for a 9001O pilot light?

Issue:
Need to know the mounting diameter of the 9001O pilot lights.

Product Line:
Harmony Pushbuttons

Environment:
All Products

Cause:
Product Features

Resolution:
0.68`` ; 17.5mm

 

How do you set up the ATV61/ATV71 drive with an VW3A3316 ethernet IP option card to use assemblies 100 and 101?

Issue:
How do you set up the ATV61/ATV71 drive with an VW3A3316 ethernet IP option card to use assemblies 100 and 101?

Product Line:
Altivar ATV61 ATV71 with VW3A3316 or VW3A3320 option cards

Environment:
All 

Cause:
Using an Allen Bradley PLC they need to set up the ATV61 with an VW3A3316 ethernet IP option card to use assemblies 100 and 101.

Resolution:

PLC settings:

The Ethernet Scanner Module needs to be configured as followed. 
1.  Set up the input and output tables as a Generic option. 
2.  Assembly 100 output table Size 16 bytes (8 integer) (writing command)
3.  Assembly 101 input table Size 16 bytes (8 integer) (reading command)
4.  Configuration size 0.
5.  Single INT or single Integer. 

Drive settings:
[Note] - programming example only you can configure the drive to match your logic input configuration. 

1.  Menu 1.6 [COMMAND]
Ref 1 channel  = Com card
Profile = I/O profile
CMD  Switching = LI3
CMD channel 1= Com card
CMD channel 2= Terminal control
ref 2 Switching = channel 1 active

2.  menu 1.7 [APPLICATION FUNCTION]
Ref Switching
Ref 1 B Switching = LI3
Ref 1 B channel = AI1

Programming will match LI3 to switch between Com card command and reference / Terminal command and AI1 speed reference.
Example LI3=1 Drive is commanded  from terminal command and speed ref is from AI1
              LI3=0 Drive is commanded  from com card and speed ref is from the com card. 

Using assemblies 100 and 101 will allow will the PLC's Scanner module to interface with the Drives internal Com Scanner modules in menu 1.9.

3.  Menu 1.9 [COMMUNICATION]
Set up your IP address  123 456 789 456 (example)
Set up your Subnet address 255 255 255 0 (example)
Set up your Gateway address if it applies.

Com Scanner INPUT Table  is used for assembly 101 Read only
3201 ETA drives status word
8604 rFrd output speed in RPM's
0
0
0
0
0
0

Com Scanner Output table is used for assembly 100 write only
8501 CMD  or command word to start the drive
8602 LFRD speed reference in RPM's
0
0
0
0
0
0
0
0
To add additional parameter addresses please refer to the ATV61/71 Communication Parameters Manual on the Schneider Electric website.

What is the maximum number of registers the Modbus Device Importer (MDI) can configure and support?

Issue
What is the maximum number of registers the Modbus Device Importer(MDI) can configure and support?

Product Line
ION Enterprise 5.6, ION Enterprise 6.0, SPM 7.0.1, PME 7.2.x, PME 8.x

Cause 
User would like to know maximum number of registers the Modbus Device Importer(MDI) can be configured and supported. 

Environment
Creating device type thorough Modbus Device Importer (MDI) 

Resolution 

When configuring MDI, user will have to create Managers then Modules and then registers. Therefore, they each have their own limitation as described below. 

User can have maximum of 128 Managers, 4095 modules per each manager, and 255 registers per each module(by convention).

It is possible to have multiple managers of the same type in the MDI (the translators definitely don't care about this).

These limits are for compatibility with the MDI, to make it easier to validate what is an unused handle when automatically allocating new handles.

NOTE: In previous versions of the MDI the maximum was around 300-400 registers total. This limit was removed in version 5.6 of ION Enterprise when extensions logging support was added to the MDI.

C-BUS - Can I open/close all shutters but still have individual control?

Yes you can, if you have for example 5 shutter relays all with separate group address for individual control and would like a master switch to open or close all then try the following:

On a device supporting scenes, create a close scene with all of those shutter relay groups set to 0%, under the Trigger Control tab create a Trigger Group with the action selector set to 0.
Now duplicate that scene and set the groups to 100%, under the Trigger Control select the same Trigger Group but now set the Action selector to 255.

On a key input (switch) change to the secondary application and select the Trigger Group with function on/off.

When pressed this will send the 255 to trigger one scene and when pressed off will send the 0 level to trigger the alternate scene.

 

How do I enable and configure the I/O Scanner on the Altivar Process Drive?

Issue:
How do I enable and configure the I/O Scanner on the Altivar Process Drive?

Product Line:
Altivar Process Drive

Environment:
All serial numbers for Altivar Process Drive

Cause:
To configure I/O scanner tables 

Resolution:
On the Altivar Process the I/O Scanner cannot be enabled or configured through the keypad or the Web Server. 
The Web Server is for monitoring only.
The I/O Scanner can only be configured through the Somove software.

Somove
When connected to Somove go to [Parameters Lists] tab, [Fieldbus] menu, then click on [Port - Modbus TCP]

Drive I/O Profile will allow you to configure I/O scanner input/output tables of up to 32 registers
To read and write to each table you will still have to configure you PLC with Unit ID 255.

 

Details Returned from Sun Systems via Advanced Device Crawlers

Issue:

Details Returned from Sun Systems via Advanced Device Crawlers

Product Line:

NetBotz

Environment:

NetBotz version 2 Advanced Device Crawlers.

Cause:

The following information can be queried via Advanced Device Crawlers for Sun systems assuming the Sun DDF (Device Definition File) is installed on the NetBotz appliance and the Sun system is SNMP enabled. Please note that not all information listed below is available on all Sun models.

Resolution:


 
  • Description
  • Ambient Temperature
  • System Board Power Status
  • Processor Temperature
  • Control Board Power Status
  • I/O Cabinet Power Status
  • Fan Tray Power Status
  • Fan Power Status
  • Support Board Power Status
  • Bulk Power Supply Status
  • System Board CIC0 ASIC Temperature
  • System Board MC ASIC Temperature
  • System Board XDB2 ASIC Temperature
  • System Board PROC0 ASIC Temperature
  • System Board 3.3V DC Temperature
  • System Board VDD Core Temperature
  • System Board 5V DC Temperature
  • System Board VDD (3.3VDC) Voltage
  • System Board 5V DC Housekeeping Voltage
  • System Board 5V DC Voltage
  • System Board VDD Core Voltage
  • System Board 3.3V DC Voltage
  • Control Board PS1 (5V DC) Temperature
  • Control Board Temperature Sensor
  • Control Board 5V DC Voltage
  • Control Board Housekeeping 5V DC Voltage
  • Control Board Housekeeping 3.3V DC Voltage
  • Control Board VccPer (5V DC) Voltage
  • Control Board VccFan (5V DC) Voltage
  • Center Plane Temperature Points
  • Support Board PS (3.3V DC) Temperature
  • Support Board Housekeeping 5V DC Voltage
  • Support Board Housekeeping 3.3V DC Voltage

STBNIP2212 Advantys RoHs Ethernet NIM Firmware Upgrade - Exec v.2.73

Release Notice

The purpose of this resolution is to inform STBNIP2212 users that the Exec was upgraded to the following:

    • Exec v.2.73
    • Kernel v. 2.22
    • Web page v.1.20.05

Goals and Symptoms

Exec file, nip2212_upgrade_[k]_v2.22.02_[fw]_v2.73.01_[web]_v1.20.05.exe, is now available and will automatically run the loader utility program when executed and prompt the user to enter the IP address of the Ethenet NIM. The Exec, Kernel, and web files will load sequentially and then reboot the NIM when completed.

Facts and Changes

The new Exec., Kernel and web versions are field upgradable and will work with any STBNIP2212 Ethernet NIM hardware whose firmware is version 2.70 or higher. This Exec cannot be loaded into NIMs that have an SV 2.30 or lower.

  • STBNIP2212's whose Exec versions are 2.3x or less are non-RoHs units. STBNIP2212's whose Exec versions are 2.7x or higher are RoHs units. The Execs between these units are not interchangeable.
    • RoHs is the acronym for Restriction of Hazardous Substances. RoHS, also known as Directive 2002/95/EC, originated in the European Union and restricts the use of specific hazardous materials found in electrical and electronic PRODUCTS. The substances banned under RoHS are lead (Pb), mercury (Hg), cadmium (Cd), hexavalent chromium (CrVI), polybrominated biphenyls (PBB) and polybrominated diphenyl ethers (PBDE).
  • Firmware for the RoHs and Non-RoHs Ethernet NIMs is available on Planet.

Causes and Fixes

The following issues have been resolved in this version:

  • Modified the STBNIP2212 to re-send TCP packet data after 2 Keep-Alives instead of 3 Keep-Alives.
  • Allows the value 255 to be used in any IP address octet for gateway or device.

Legacy KB System (APS) Data: RESL204948 V1.0, Originally authored by DaDz on 03/28/2011, Last Edited by DaDz on 03/28/2011
Related ranges: Modicon STB

170ANR1209x Discrete Inputs Oscillate On/Off Under Certain Conditions

Release Notice

The purpose of this Resolution is to inform users of 170ANR12090 and 170ANR12091 Momentum I/O Bases of a problem with the discrete input data oscillating on and off, although no input signals are present.

  •  

Goals and Symptoms

The discrete input bits (lower byte of input word 2) will continuously oscillate on/off when at least one of the inputs is turned on from the field side. This occurs if the parameters for the analog outputs are set to either of the following two configurations:

  1. When User Defined Value is selected for Channel 3 and the value is set greater than 255 decimal or 100 hex. (4x I/O map word #6)
  2. When User Defined Value is selected for Channel 4 and the value is set to a any number other than zero. (4x I/O map word #7)

The other 2 analog output parameter selections, Minimum Output, and the default parameter Hold Last Value, do not produce this condition.

Facts and Changes

Units affected are:

  • 170ANR12090
  • 170ANR12091

Causes and Fixes

A firmware solution has been implemented. Modules with an SV of 1.10 and a PV02 have this fix.


  • This is not a field upgradable option. Applications using this module that are experiencing discrete inputs issues using the above mentioned parameters may be exchanged under warranty. With the parameter settings described, the problem will occur when a discrete input is made active. Parameter settings other than those described above will not exhibit this problem.

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

STBNIP2212 Advantys Non-RoHs Ethernet NIM Firmware Upgrade - Exec v.2.33

Release Notice

The purpose of this resolution is to inform STBNIP2212 users that the Exec was upgraded to the following:

    • Exec v.2.33
    • Kernel v. 2.04
    • Web page v.1.20.05

Goals and Symptoms

Exec file, nip2212_upgrade_[k]_v2.04.06_[fw]_v2.33_[web]_v1.20.05.exe, is now available and will automatically run the loader utility program when executed and prompt the user to enter the IP address of the Ethenet NIM. The Exec, Kernel, and web files will load sequentially and then reboot the NIM when completed.

Facts and Changes

The new Exec., Kernel and web versions are field upgradable and will work with any STBNIP2212 Ethernet NIM hardware whose firmware is version 2.70 or higher. This Exec cannot be loaded into NIMs that have an SV 2.30 or lower.

  • STBNIP2212's whose Exec versions are 2.3x or less are non-RoHs units. STBNIP2212's whose Exec versions are 2.7x or higher are RoHs units. The Execs between these units are not interchangeable.
    • RoHs is the acronym for Restriction of Hazardous Substances. RoHS, also known as Directive 2002/95/EC, originated in the European Union and restricts the use of specific hazardous materials found in electrical and electronic PRODUCTS. The substances banned under RoHS are lead (Pb), mercury (Hg), cadmium (Cd), hexavalent chromium (CrVI), polybrominated biphenyls (PBB) and polybrominated diphenyl ethers (PBDE).
  • Firmware for the RoHs and Non-RoHs Ethernet NIMs is available on Planet.

Causes and Fixes

The following issues were resolved in this version:

  • Modified the STBNIP2212 to re-send TCP packet data after 2 Keep-Alives instead of 3 Keep-Alives.
  • The NIM now allows the value 255 to be used in any octet for the gateway or device IP address.

Legacy KB System (APS) Data: RESL204945 V1.0, Originally authored by DaDz on 03/28/2011, Last Edited by DaDz on 03/28/2011
Related ranges: Modicon STB

How to add a webpage to the PM8ECC?

Issue
The only webpages available are energy readings and power readings under monitoring tab on PM8ECC webpage.

Product Line
PM8ECC

Cause
By default there is only Instantaneous readings under monitoring tab on PM8ECC webpage.

Resolution
Use WebPageGenerator to add Circuit summary, Load Current, Demand Current, Power and energy readings web pages.  WebPageGenerator is a unique tool that creates built in web pages that can be downloaded by going to FA212905.

After downloading WebPageGenerator follow the steps below to add the webpages.

  1. Open WebPageGenerator, and if you do not have the files to send, select new at the first screen and then select OK.
  1. Enter the Equipment Name and Select PM8 Ethernet Card. Then Select Next >.
 
  1. Add the device to the list on the right using the Device List and the > arrow. Once it is in the right box change the address to the meters Modbus address(Address 255 may be appropriate). Then select Next >.
  1. Unless changes are needed, the defaults can be left and Finish can be selected.
  1. Enter the IP Address, UserName, and Password, and select Next >.
    • ​​PM800 defaults:
      IP Address 169.254.0.10
      User name Administrator
      Password Gateway
  1. Select Send to upload the pages to the PM8ECC.

Additional Information: Utilizing the embedded web server in the PowerLogic CM3000 or CM4000 circuit monitor with Ethernet Communications Card (ECC21), PowerLogic PM800 power meter with Ethernet Communications Card (PM8ECC) or the Powerlogic EGX400 Ethernet Gateway, the WebPageGenerator (WPG) creates web pages and loads them to the embedded web server providing a simple web interface for viewing real-time and historical information from power monitoring, control, and circuit protective devices.

How do I send a start/stop and a speed command to the Altivar Process Drive over Ethernet (Embedded) protocol?

Issue:
How do I send a start/stop and a speed command to the Altivar Process Drive over Ethernet (Embedded) protocol?

Product Line:
Altivar Process Drive

Environment:
All serial numbers for Altivar Process Drive

Cause:
N/A

Resolution:

Unit ID: 1

Command:
DRIVECOM (CiA402 profile)
You profile is set to separate or not separate and you need to command the drive.  Your Unit ID is set to 1


On the Drive,
[Communication] [Comm parameters] [Modbus SL] [Modbus Fieldbus]
- Set Modbus Address to 1

[Complete settings] [Command and Reference] [Control Mode] CHCF
- Set to [Not Separ.] or [Separate Mode]

Command Word Register: 8501
To start the drive under DRIVECOM profile, you will need to write a decimal value of 6, 7, and 15 directly to the command word 8501
Toggling 7 and 15 will either stop or start the drive.


I/O Profile
To profile is set to IO Profile and your Unit ID is set to 1

On the Drive,
[Communication] [Comm parameters] [Modbus SL] [Modbus Fieldbus]
- Set Modbus Address to 1

[Complete settings] [Command and Reference] [Control Mode] CHCF
- Set to [I/O profile]

Command Word Register: 8501 (16 bit register)
Reference Frequency: 8502 (0.1hz) or 8602 (1 rpm)
To start the drive under I/O Profile profile you will need to toggle off and on bit 0. 
After Command is sent a speed reference is given by writing a decimal value in units of 0.1Hz to the register 8502 or 8602 in units of 1 rpm.
[Nominal Motor Speed] value will have to be set correctly in the [Motor parameters] Menu.



Unit ID: 255

With the Unit ID of 255 you do not need to set your modbus address (leave it set at 0)
You will just need to turn on IO scanner through Somove
The drive will automatically look at the IO scanner input/output table. 

Please reference FAQ - "How do I enable and configure the I/O Scanner on the Altivar Process Drive?"


 

Video: How to configure an ION meter as a Modbus Gateway

Issue
PM8000, ION7550, ION7650, and ION8650 devices equipped with Ethernet communication can be used as Ethernet Gateways to allow communications to serial devices. The Ethergate feature of the meters requires that TCP Ports 7801, 7802 or 7803 be used to access the gateway connection. 3rd Party Software or Hardware may not be able to communicate Modbus on a port other than the standard 502, and therefore are unable to access the downstream meters. 

Product Line
PM8000
ION 7550 / 7650
ION 8650

Environment
Meter Communications

Resolution
The ION7550 / 7650 v350 Firmware release introduced a new feature called ModGate. When configured, a modbus request is sent through Ethernet using Modbus TCP to the gateway meter over port 502. If this request is addressed with the slave ID of one of the downstream serial devices, the meter forwards the message to that device using Modbus RTU. When the downstream device responds, the gateway meter forwards the response back to the master. Modbus gateway supports an additional slave address of 255 (in addition to 0-247), which sends a packet to the gateway meter only. The figure shows a typical setup: 



How to configure ModGate using the ION Setup software:

1) Connect to the ION meter using ION Setup [See FAQ FA212816]
2) Using the Setup Assistant, under Communications > Serial Settings, set the Protocol of the Serial Port in question to Modbus Master. (Also ensure the baud rate, parity are configured properly to that of the daisy chain meters). 
3) Close out of the Setup Assistant (and click NO to connect to a different device), and then enter the Advanced Mode by holding CTRL and clicking on the meter.
4) Locate the Modbus Master Options Modules folder and double click it.
5) Double click on the Modbus Master Options 1 module and go to the Setup Registers tab. 
6) Select the MMO1 Serial Connection 1 and set it to the Comm port that was configured in Step 2. Click OK. 
7) Select the MMO1 ModbusGate Connection and set it to Gateway Enabled - Serial Connection 1. Click OK. 
8) Click Send to save and send the configuration to the meter. 

Note: For the PM8000 and ION7550/7650, the following procedure can also be used:

1) Connect to the ION meter using ION Setup. 
2) Using the Setup Assistant, under Communications > Serial Settings, set the Protocol of the Serial Port in question to Modbus Master. (Also ensure the baud rate, parity are configured properly to that of the daisy chain meters). 
3) (If using PM8000) Select Basic Ethernet > TCP/IP and set the Modbus Gateway to the Serial Port in question.
3) (If using ION7550/7650) Select Network Settings > TCP/IP and set the Modbus Gateway to the Serial Port in question.

How to configure ModGate using Power Monitoring Expert software:

1) Open the meter in Designer
2) Open Communications Setup
3) Right-click on the Comm port in question
4) Double-click on Protocol and set to Modbus Master. (Also ensure the baud rate, parity are configured properly to that of the daisy chain meters). Click OK.
5) Close the Communications Setup window and navigate to Advanced Setup > Core Modules
6) Right-click on Modbus Master Options Modules
7) Double-click on MMO1 Serial Connection 1 and select the Comm port that was configured in Step 3. Click OK.
8) Double-click on MMO1 ModbusGate Connection and set to Gateway Enabled - Serial Connection 1. Click OK.


The meter will now route all incoming traffic on TCP Port 502 to the configured serial port. In order to communicate to the gateway meter itself using Modbus, Unit ID 255 must be used. 

The video below depicts how to configure ModGate using the ION Setup software.

PowerSCADA Expert - Maximum number of IODevices of MODNET type

Customer request:
To integrate in the PowerSCADA Expert (PSE) project 400 sets of Ethernet devices which support Modbus TCP protocol.
The question was if all the devices can be integrated to one PSE Server, and the SCADA system is redundant.
In the legacy software version, one IOServer could only have one TCP/IP Board and 255 Ports can be created on that type of Board.
Can we integrate all the devices into one PSE Server? If yes, then how to configure the communication including IO Server, Board, Port and IODevice?

Resolution:
The maximum limit in PowerSCADA software is of 16383 IODevices per project and 4095 simultaneous multiple protocols.
BOARD types have to be unique per IOServer.
You may find reference of the word "Channel" in various documentation resources.
To be clear, PORT = Channel.
PORT number limits are hardcoded into each communication driver.
The TCPIP driver (TCPIP.DLL) supports 512 PORTS per board since DLL version 2.4.4.0, thus MODNET driver (MODNET.DLL) supports 512 PORTS (channels) since driver version 2.6.21.0.

These limits are theoretical limits, in reality there are Kernel Queues that introduce another limitation.
[Kernel]Queue has a max of 5000 (which is also default value), but some drivers like Modnet consume more queues per channel than others.
Modnet consumes 13 Kernel Queues per PORT.
As a result, a 512 hardcoded limit for Modnet PORTs will be downgraded to 300-350 because of these queues.
So, consider the limit at 350 MODNET PORTS per BOARD (per IOServer).
If you use ModbusTCP/RTU Gateways, then you can have thousands of IODevices on the same IOServer, just because for each of the 350 PORTS you could have several different IODevices, with different Addresses (UnitID).
For example: 1 Gateway to collect 5 SEPAMs means: 5 IODevices (5 different IODevice Addresses), 1 PORT (the same PORT that uses Special Options for Gateway's IP address), 1 BOARD (TCPIP).

To overcome the 350 PORTS limit, more IOServers are needed.

Further, another reduction should be made, imposed by the recommended number of IODevices per IOServer.
In the same project, the same Cluster, the same Network Address, the PowerSCADA team recommendation (rule) is: either 50000 tags or 250 IODevices per IOServer. Whichever comes first.
To create another IOServer in the same Cluster and the same Network Address, simply add another IOServer but specify a different Port (this is the Port from the IO Server dialog window).
Doing so, you will need to define different Ports for the extra IOServers: default is 2082, so you may add any unused TCP port: 3082 for second IOServer, 4082 for third IOServer and so on.

Here are some configuration screenshots (using Excel and DBF Add-in) to illustrate the IODevices distribution per IOServers:

IOServers:


Boards:


Ports:


IODevices:



                                            
Created on 8th JUL 2015 by
Adrian Dicea
Global Expert Technical Support Engineer - Support Prime PSE / EGX

How do I troubleshoot an Altivar Process Drive that would not connect when trying to communicate with a Modbus over Ethernet (Modbus TCP) network?

Issue:
How do I troubleshoot an Altivar Process Drive that would not connect when trying to communicate with a Embedded Modbus Ethernet network?

Product Line:
Altivar Process Drives (ATV630, ATV930, ATV650, ATV950, ATV660, ATV960, ATV680, ATV980)

Environment:
All serial numbers for Altivar Process Drives

Cause:
N/A

Resolution:
Note: This FAQ goes over some basic checks and troubleshooting tips. For extended troubleshooting please refer to your drives Embedded Modbus Ethernet manual that is attached at this FAQ. 

Drive Will Not Connect
  • Installation
  • Network
    • No Duplicate IP addresses
    • Make sure Modbus Address is correctly set
  • Programming
    • Make sure all Basics Settings are configured correctly in the drive and that the drive is properly Powercycled after all settings are made
      • Configure Modbus Settings
        • [Communication] [Comm parameters] [Modbus SL] [Modbus Fieldbus]
      • Configure Ethernet Settings
        • [Communication] [Comm parameters] [Embd Eth Config]
Drive Connects but Will Not Run on a Command
  • Checking the Network
    • If you cannot write to the drive, first verify you can read from the drive. If unable to read from the drive then re-verify the drive is connect properly to the Modbus Ethernet network
    • Verify that you are reading the proper input and output addresses
    • Check for possible register offsets
  • Checking the Drive
    • Confirm that the drive is properly to receive commands from the Network
    • Check Command and Reference Menu
      • [Complete settings] [Command and Reference]
    • ​Check Control Mode
      • Are we using IO Profile or DriveCom (Separate or Not Separate)
    • Check drive for any faults
      • Check top left corner of the keypad.
  • ​Addtional Troubleshooting Tips:

How Historic data and Event Journal files are stored in the database

DISCLAIMER

The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.

ClearSCADA stores historic data as files on the computer's hard disk. The location of those files is configured in the Location section of the Server Configuration Utility (System Configuration > Location). So that the ClearSCADA can find the data as required, it is stored in folders within those locations, with each folder being named according to certain rules.

When objects are created they are automatically assigned a unique ID which starts at 0, the root group object, and incrementing for each new object. If an object is removed from the database its unique ID is not reused.

Both event journal and historic data are stored in what is known as a stream. A stream (or historic group) specifies how many different folders (and files) are used for storage of historic data. When the ClearSCADA server needs to search through this historic data, it is able to search a smaller subset of data when it is split into different streams and hence performance can be improved. A stream size of 8 (the default) will mean that a maximum of 256 (2 to the power of "stream size") objects will be placed in a sub-directory. i.e. Objects with the unique IDs of 0 to 255 will go in directory JnI00000, objects in the range 256 to 511 will go in JnI00001. The number of segments will depend upon the highest object id in the database and is not a predefined number.

Event Journal

The Event Journal data files are stored in a folder named Journal. This location is user definable in the Server Configuration. Under this directory, the data directory names are made up of 8 characters. The first two characters are always 'Jn'. The third character is a capital letter in the range D to O which represents the stream size.

Letter Stream Size Objects
Per Folder
D 3 8
E 4 16
F 5 32
G 6 64
H 7 128
I 8 256
J 9 512
K 10 1024
L 11 2048
M 12 4096
N 13 8192
O 14 16384


The remaining 5 letters are digits which represent the stream number. The stream number is a number generated from the Object Id. The stream size is configurable from the Server Configuration Dialog and specifies the number of objects to store in one 'stream' of data. A stream can be used to improve performance by keeping smaller subsets of data together. This means that searches for data may only need to search subsets of all data if the data required is across only one or two streams.

For new installations of ClearSCADA, the stream size field defaults to 8.

Event Journal filenames start with 'H' (for hour) followed by a decimal number that is the number of hours since 1-Jan-1601 00:00:00 UTC. The file extension is 'MWJ'.

Historic Data

The directory structure is similar to that used for the event journal described above. The root level folder is named Historic and under this are a number of folders with 8 characters in the folder name. The first two characters are always 'Hd'. The third character is a capital letter the same as that used by the journal. The remaining 5 letters are digits that represent the stream number (based on the historic group size).

For new installations of ClearSCADA, the historic group size field defaults to 8. This setting is controllable via the registry key

HKEY_LOCAL_MACHINE\Software\Schneider Electric\ClearSCADA\DB\HistoricGroupSize

If the value of this key is changed, the server will need to be restarted, and on restart, the server will rearrange the folder structure on the hard disk to match the new group size. File formats do not change between versions, only the location of the files.

Historic filenames start with 'Wk' (for week) followed by a decimal number that is the number of weeks since 1-Jan-1601 00:00:00 UTC. There are several file extensions in use for different types of historic data:
File Extension File Contents
HRD Historic Raw Data
HMD Historic Modified Data
HAD Historic Annotation Data
HSD Historic Suppression Data (introduced in ClearSCADA 2010)
HUD Historic Units Data (deprecated)

In most servers, almost all the historical data will be in HRD files.

Other Comments

It is not necessary for two servers in a main-standby arrangement to have the same historic and event journal stream sizes. If however the historic data is manually copied from one machine to another and the sizes do not match, ClearSCADA will reformat the historic data on startup of the second server to make the formats different based on the stream sizes. This is not a problem as far as redundancy is concerned. It simply means that the physical file structure on the two servers will be different.

Data that is archived from a server from a particular stream size can be mounted on a server with a different stream/group size without problems.

What is Modbus and How does it work?

Issue:
What is Modbus and How does it work? 

Product line: 
All Product lines 

Environment: 
All Serial Numbers   

Cause:
Install 

Resolution:    

What is Modbus? 

Modbus is a serial communication protocol developed by Modicon published by Modicon® in 1979 for use with its programmable logic controllers (PLCs). In simple terms, it is a method used for transmitting information over serial lines between electronic devices. The device requesting the information is called the Modbus Master and the devices supplying information are Modbus Slaves. In a standard Modbus network, there is one Master and up to 247 Slaves, each with a unique Slave Address from 1 to 247. The Master can also write information to the Slaves.

The official Modbus specification can be found at https://www.modbus.org/ 


What is it used for?

Modbus is an open protocol, meaning that it's free for manufacturers to build into their equipment without having to pay royalties. It has become a standard communications protocol in industry, and is now the most commonly available means of connecting industrial electronic devices. It is used widely by many manufacturers throughout many industries.Modbus is typically used to transmit signals from instrumentation and control devices back to a main controller or data gathering system, for example a system that measures temperature and humidity and communicates the results to a computer. Modbus is often used to connect a supervisory computer with a remote terminal unit (RTU) in supervisory control and data acquisition (SCADA) systems. Versions of the Modbus protocol exist for serial lines (Modbus RTU and Modbus ASCII) and for Ethernet (Modbus TCP).


How does it work?

Modbus is transmitted over serial lines between devices. The simplest setup would be a single serial cable connecting the serial ports on two devices, a Master and a Slave. 

 

The data is sent as series of ones and zeroes called bits. Each bit is sent as a voltage. Zeroes are sent as positive voltages and a ones as negative. The bits are sent very quickly. A typical transmission speed is 9600 baud (bits per second).

 

What is hexadecimal?

When troubleshooting problems, it can be helpful to see the actual raw data being transmitted. Long strings of ones and zeroes are difficult to read, so the bits are combined and shown in hexadecimal. Each block of 4 bits is represented by one of the sixteen characters from 0 to F. 

  

Each block of 8 bits (called a byte) is represented by one of the 256 character pairs from 00 to FF. 
 

How is data stored in Standard Modbus?

Information is stored in the Slave device in four different tables. Two tables store on/off discrete values (coils) and two store numerical values (registers). The coils and registers each have a read-only table and read-write table. Each table has 9999 values. Each coil or contact is 1 bit and assigned a data address between 0000 and 270E. Each register is 1 word = 16 bits = 2 bytes and also has data address between 0000 and 270E.
 

 

Coil/Register Numbers can be thought of as location names since they do not appear in the actual messages. The Data Addresses are used in the messages. For example, the first Holding Register, number 40001, has the Data Address 0000. The difference between these two values is the offset. Each table has a different offset. 1, 10001, 30001 and 40001. 

What is the Slave ID?

Each slave in a network is assigned a unique unit address from 1 to 247. When the master requests data, the first byte it sends is the Slave address. This way each slave knows after the first byte whether or not to ignore the message. 

What is a function code?

The second byte sent by the Master is the Function code. This number tells the slave which table to access and whether to read from or write to the table.

 

What is a CRC?

CRC stands for Cyclic Redundancy check. It is two bytes added to the end of every modbus message for error detection. Every byte in the message is used to calculate the CRC. The receiving device also calculates the CRC and compares it to the CRC from the sending device. If even one bit in the message is received incorrectly, the CRCs will be different and an error will result. .

What are the formats of Modbus commands and responses? 

 

What are data types?

The example for FC03 shows that register 40108 contains AE41 which converts to the 16 bits 1010 1110 0100 0001 Great! But what does it mean? Well, it could mean a few things. Register 40108 could be defined as any of these 16-bit data types:
 

A 16-bit unsigned integer (a whole number between 0 and 65535) register 40108 contains AE41 = 44,609 (hex to decimal conversion) 

A 16-bit signed integer (a whole number between -32768 and 32767) AE41 = -20,927 (hex to decimal conversion that wraps, if its over 32767 then subtract 65536) 

A two character ASCII string (2 typed letters) AE41 = ® A 

A discrete on/off value (this works the same as 16-bit integers with a value of 0 or 1. The hex data would be 0000 or 0001) Register 40108 could also be combined with

40109 to form any of these 32-bit data types:
 

A 32-bit unsigned integer (a number between 0 and 4,294,967,295) 40108,40109 = AE41 5652 = 2,923,517,522 

A 32-bit signed integer (a number between -2,147,483,648 and 2,147,483,647) AE41 5652 = -1,371,449,774 

A 32-bit double precision IEEE floating point number. This is a mathematical formula that allows any real number (a number with decimal points) to represented by 32 bits with an accuracy of about seven digits. AE41 5652 = -4.395978 E-11 Here is a spreadsheet IEEE float calculator for inputs of 4 bytes or 2 words. To download a copy, right click and select Save Target As... 

A four character ASCII string (4 typed letters) AE41 5652 = ® A V R More registers can be combined to form longer ASCII strings. Each register being used to store two ASCII characters (two bytes). 

What is byte and word ordering?

The Modbus specification doesn't define exactly how the data is stored in the registers. Therefore, some manufacturers implemented modbus in their equipment to store and transmit the higher byte first followed by the lower byte. (AE before 41). Alternatively, others store and transmit the lower byte first (41 before AE). Similarly, when registers are combined to represent 32-bit data types, Some devices store the higher 16 bits (high word) in the first register and the remaining low word in the second (AE41 before 5652) while others do the opposite (5652 before AE41) It doesn't matter which order the bytes or words are sent in, as long as the receiving device knows which way to expect it. For example, if the number 29,235,175,522 was to be sent as a 32 bit unsigned integer, it could be arranged any of these four ways.

AE41 5652 high byte first high word first

5652 AE41 high byte first low word first

41AE 5256 low byte first high word first

5256 41AE low byte first low word first 

What is a Modbus Map?

A modbus map is simply a list for an individual slave device that defines - what the data is (eg. pressure or temperature readings)

- where the data is stored (which tables and data addresses)

- how the data is stored (data types, byte and word ordering)

Some devices are built with a fixed map that is defined by the manufacturer. While other devices allow the operator to configure or program a custom map to fit their needs. 

What is the difference between Modbus ASCII and Modbus RTU?

Modbus RTU and Modbus ASCII talk the same protocol. The only difference is that the bytes being transmitted over the wire are presented as binary with RTU and as readable ASCII with Modbus RTU. important to note about RTU is that the RTU message does not have a Start_of_text indication. The receiving party  in the communications uses a "silent" time in order to determine the start of a new message. ASCII does have a start-of-text token. Binary messages are shorter than ASCII and therefore theoretically faster to transmit/receive. You may be happy to see update rates of about 100 ms in your HMI/SCADA and could choose either communication.

Summary:
- use RTU is possible
- use ASCII in case RTU is giving timeout problems on WinNT or when using slow communications media
like 300 bps or dialup modems Most OPC Servers for Modbus support ASCII as well as RTU communications.. 

What are extended register addresses?

Since the range of the analog output holding registers is 40001 to 49999, it implies that there cannot be more than 9999 registers. Although this is usually enough for most applications, there are cases where more registers would be beneficial. Registers 40001 to 49999 correspond to data addresses 0000 to 270E. If we utilize the remaining data addresses 270F to FFFF, over six times as many registers can be available, 65536 in total. This would correspond to register numbers from 40001 to 105536. Many modbus software drivers (for Master PCs) were written with the 40001 to 49999 limits and cannot access extended registers in slave devices. And many slave devices do not support maps using the extended registers. But on the other hand, some slave devices do support these registers and some Master software can access it, especially if custom software is written. 

How does 2-byte slave addressing work?

Since a single byte is normally used to define the slave address and each slave on a network requires a unique address, the number of slaves on a network is limited to 256. The limit defined in the modbus specification is even lower at 247. To get beyond this limit, a modification can be made to the protocol to use two bytes for the address. The master and the slaves would all be required to support this modification. Two byte addressing extends the limit on the number of slaves in a network to 65535. By default, the Simply Modbus software uses 1 byte addressing. When an address greater than 255 is entered, the software automatically switches to 2 byte addressing and stays in this mode for all addresses until the 2 byte addressing is manually turned off. 

How can you send events and historical data?

Enron Modbus includes commands for moving events and historical data.. 

What is Enron Modbus?

Enron Modbus is a modification to the standard Modicon modbus communication protocol developed by Enron Corporation.

See Enron Modbus for details.