Clipsal - Mounting Accessories, Weather Protective Box, 137x110x77mm, with Clear Lid and Locking Provision

Grey | Clipsal - Mounting Accessories, Weather Protective Box, 137x110x77mm, with Clear Lid and Locking Provision

Clipsal - Mounting Accessories, Weather Protective Box, 137x110x77mm, with Clear Lid and Locking Provision

Item Number: 255-GY



Qty UoM EAN Colour



Product brand


Sustainable offer status

Green Premium product


Device mounting



137 mm


110 mm


77 mm

REACh Regulation

Free of Substances of Very High Concern above the threshold

REACh free of SVHC


EU RoHS Directive


Toxic heavy metal free


Mercury free


China RoHS Regulation

 Pro-active China RoHS declaration (out of China RoHS legal scope)

RoHS exemption information


Environmental Disclosure




PVC (polyvinyl chloride)


Package 1 Bare Product Quantity


Enclosure type

weatherproof enclosure



Unit Type of Package 1


Number of Units in Package 1


Package 1 Height

10.8 cm

Package 1 Width

10.4 cm

Package 1 Length

14 cm

Package 1 Weight

256 g
Show all specifications

Frequently Asked Questions

hide show

Can the IEM3000 series read energy output from a Solar Panel?

To be able to measure the energy out from a Solar Panel a meter needs to be able to do Four Quadrant Calculation.

This means it is capable of Identification of imported and exported active and reactive energy allows you to monitor energy flow in both directions: delivered from the utility and produced on-site.

In the iEM3000 series the following meters are capable of Four Quadrant Calculation.

iEM31** range - iEM3135, iEM3155, iEM3165, and iEM3175
iEM32** range - iEM3235, iEM3255, iEM3265, and iEM3275
iEM33** range - iEM3335, iEM3355, iEM3365, and iEM3375
iEM34** range - iEM3455, iEM3465, iEM3555, and iEM3565


How can I connect SoMove to an Altivar Process drive via Ethernet TCP/IP or Profinet?

Connecting SoMove to the VFD using the Ethernet network connection.

Product Line:

Ethernet IP or Profinet option installed.
VW3A3316, VW3A3320, VW3A3627 VW3A3720

Drive is not detected when attempting to connect.

See attachment for screenshots showing SoMove V2.9.4

Turn OFF your computers firewall before starting so you will have access to your Ethernet port. 
somove Ethernet 32

Edit Connection on your computers ethernet port and setup IP address in the Altivar Drive using an HMI.
Computer or PC setup:
Example setting up your PCs IP address.
Search Ethernet settings
-Change adapter options
- Choose the Ethernet port you want to use.
-Choose Properties
-Make sure IPV4 and IPV6 are both checked. 
-Double click on the IPV4 settings
-Select "Use the following IP address" and now enter in an IP address for your PCs ethernet port. 
Note this IP address needs to match your Drives IP address up to the last octet. 
Drives IP address= (for the Drive) and your PC's IP address = (your computer)
Subnet address=
-Choose ok
Somove Ethernet 1

Drive Setup
Example set your Drives IP address using the remote HMI under the Ethernet settings in the programming. 
IP address= (for the Drive) 
Subnet address=
-Power cycle your Drive after changing the IP address 

Open up Somove 2.9.4 or newer and setup your "edit connection/scan" settings.
-Click on  "edit connection/scan"
-Choose Modbus TCP double click
-Choose the advanced settings (small gear wheel icon).
-Choose More
-Choose Scan tab
-Now type in your Drives IP address example  
-Choose Single Scan and enter 1 
-Apply and OK
-Ok again 
Somove Ethernet 2

-Now Scan for the Device to see if your PC finds the Drive. 
-double click on the picture of the drive to connect and load from the device.

Somove Ethernet 3

Please read and understand before checking OK. 

Somove ethernet 4

Somove is loading settings from the Drive to your Somove on your PC. 

somove ethernet 5b

Your are now connected to the Drive when the bar across the top turn's orange. 

Somove Ethernet 6a



This example should work using. 
-Ethernet TCP
-Ethernet IP



Configure Sufficient ClearSCADA Logging

This article is a brief summary of several detailed articles about configuring ClearSCADA logging that can be found in the Logging and Log File Analysis  section. It should be understood that in most cases the default logging settings in ClearSCADA are only sufficient to capture a time window of a few minutes. One should always make sure that ClearSCADA logging is configured to capture events over a sufficient time window in order for log files be useful when troubleshooting issues.

The information provided below will explain how to increase the number of log files for ClearSCADA server, drivers and clients.

For more information about each type of ClearSCADA logging please go over the dedicated articles in the Logging and Log File Analysis  section.

This article covers the following topics:

  • Setting up Server Logging
  • Setting up Driver Logging
  • Setting up Snapshot Logging
  • Setting up DBClient Logging
  • Setting up ViewX Logging (for ClearSCADA 2014 R1 onwards)
  • How Much Logging is Sufficient?

Setting up Server Logging

To configure server logging, please right click on the ClearSCADA Server Icon and select Configuration. Once the Server Configuration dialog is displayed, navigate to the page shown in the screen capture below and change Maximum Size Of Each FileMaximum Number of Files and Number of Old Files to Keep to sufficient values. The location of the server log files is shown in File Base.

Server log

Sometimes a Schneider Electric engineer might ask you to enable/disable certain server logging options. To do such, please right click on the ClearSCADA Server Icon and select Status for the Status dialog to get displayed. Once the dialog is displayed, navigate to the section below for a list of all server side logging options available in ClearSCADA. To enabled/disable an option, right click on the option and select Enable/Disable respectively.

Server status

Setting up Driver Logging

To configure driver logging, please right click on the ClearSCADA Server Icon and select Status. In the Status dialog, navigate to the section below for a list of all ClearSCADA drivers installed on the server. Right click on the particular driver and select "Logging...". Under the Configuration tab, increase Maximum Size of Each FileMaximum Number of Files and Number of Old Files to keep to sufficient values. File Base shows the location of the driver log files.

Server status

Sometimes a Schneider Electric engineer might ask you to enable/disable certain driver logging options. To do such, navigate to the Current Options tab in the Driver Logging dialog as per the screen capture below. To enable (disable) additional logging options, select (deselect) the required option from the Options list and apply the change.

Logging setup

Setting up Snapshot Logging

On some occasions a Schneider Electric engineer might ask you to increase the amount of ClearSCADA snapshot log files. To do that please right click on the ClearSCADA Server Icon and select Configuration. Navigate to the Registry section (shown in the screen shot below) and increase LogMaxFileLogMaxSize and LogOldFiles to the requested amount. The location of the DBSnapshot log files is shown in LogFileBase.

Snapshot logging

Setting up DBClient Logging

To configure DBClient logging, open up Windows Registry and navigate to \HKEY_CURRENT_USER\Software\Schneider Electric\ClearSCADA\DBClientNamed. Make sure the logging is enabled and increase LogMaxFilesLogMaxSize and LogOldFiles values. The location of the DBClientNamed log files is shown in LogFileBase.

DB client logging


Setting up ViewX Logging (for ClearSCADA 2014 R1 onwards)

ViewX in CS2014 R1 onwards uses WPF and .NET technologies. The configuration of this new ViewX application uses SE.Scada.ViewX.exe.config XML files located adjacent to the SE.Scada.ViewX.exe application itself (%ProgramFiles(x86)%\Schneider Electric\ClearSCADA\ SE.Scada.ViewX.exe.config).

In File Browser, with no visible extensions:


In command line or with file extensions visible:

Cmd line

And the SchneiderElectric.Scada.ViewX.Properties.Settings element defines its configuration. Specifically, to control logging, the following elements’ values need changing:

Logging changes

It is likely that the SE.Scada.ViewX.exe.config file will require administrator permissions to edit the settings.
To edit settings, open the editor (e.g. Notepad) as administrator and then open the XML configuration file from within the editor.
Note that an upgrade of ClearSCADA will overwrite the existing XML configuration file with the default configuration.
The XML configuration file will need to be re-configured after an upgrade of ClearSCADA takes place.

How Much Logging is Sufficient?

When the maximum number of log files that ClearSCADA generates is reached, the oldest log files get overwritten and information they contain gets lost. Therefore one should always make sure the log files of interest get collected before they get overwritten. The number of log files to keep is specific to each application as the amount of information logged depends on the nature of the application, the size of the database, drivers used, logging options enabled etc. Ideally one would want ClearSCADA log files to at least capture a time window of several days to cover weekends, long weekends and other long holidays to make sure the log files do not get overwritten when there is no one is available to collect them. To check how much time is captured by a certain type of ClearSCADA log files, one could simply locate the set of these log files using their File Base and check Date Modified of the first and of the last log file of the same type.

Log files

Be aware that enabling (disabling) additional server or driver logging options will reduce (increase) the time window captured by ClearSCADA logging. This means that the amount of log files of a particular type that ClearSCADA generates will need to be adjusted accordingly to capture the same time window.

Please be mindful of the space available on your hard drive. For example, if Maximum Size Of Each File is set to 5000KB, 
Maximum Number of Files is set to 25 and Number of Old Files to Keep is set to 2, the required space on the hard drive is going to be:

Maximum Size Of Each File x Maximum Number of Files x (1 current set + Number of Old Files to Keep) or

5000KB x 25 x (1 + 2) = 375000KB

Where 375000 / 1024 = 366MB

Planning which disk / partition is going to store log files is important, to avoid impacting other ClearSCADA file-relate operations – e.g. consider using a separate disk for log files. 

Planning and configuring log file collection at the time deployment of the system is planned is important. For instance, reserving insufficient disk space and switching ‘off’ many of the default categories of logging for normal operation of the system will be a problematic position: when a problem is detected and logs are required to investigate the problem, little information will be in the logs and re-dimensioning disks/partitions may be necessary to get the logging required to investigate the problem on a subsequent occurrence. Whereas, well planned and sufficient, default logging, will hopefully provide sufficient information to investigate a single occurrence of a problem.


How do you change the Modbus device number on the master Smartlink SI B controller (either in the web page or through the EcoStruxure Power Commission software) from 255 to a lower number?


Change the Modbus device number on the master Smartlink SI B controller from 255 to a lower number

Product Line:

Acti 9 Smartlink


Smartlink SI B


The Smartlink SI B (A9XMZA08) has a fixed Modbus Address of 255, it is not possible to change it.

The Smartlink - Modbus RS485 slave (A9XMSB11) address can be configure in the range of 1 to 99. You can set the address adjusting the two thumbwheels:

-The left-hand thumbwheel sets the tens.
-The right-hand thumbwheel sets the units.

Modbus RS485 slave address cconfiguration

Smartlink SI B (A9XMZA08) user guide: 

Who do I need to contact to get Start- Up Services on an AC Drive or Softstarter?

Contact to get Start -Up Services on an AC Drive or Softstarter.

Product Line:
AC Drive or Softstarter


If startup services has already been purchased, contact the project manager at the appropriate distributor or Schneider Electric sales office to schedule the service.
If startup services needs to be ordered, contact an authorized startup technician, searchable at the following link,


Or you can call DPSG (888-778-2733 option 2, option 4), and we'll be happy to submit a request to have you contacted to set up a visit by our Services department. 

What will cause EPF2 fault on ATV32 or ATV320 when communicating over Ethernet?

EPF2 fault on ATV32 or ATV320 when using Ethernet.

Product Line:


FDR detected fault
IP address duplication detected fault

First check the FDR on the Ethernet IP card is deactivated. In case the FDR is activated, that will explain the "EPF2" fault. The reason is that the Drive is waiting for a configuration from PLC, but PLC doesn't answer once the timeout is reached. This causes the drive to trip in "EPF2".

The second reason for "EPF2" fault is the range of IP address. In case of IP address 192.0.0.x and Sub net mask of can cause "EPF2". Change the range of the IP address.

Additionally, an incorrect configuration of the drive can cause this fault when using Assemblies other than 100 and 101. Drive must be configured as follows:
  • Ref 1= Communications card
  • Profile= Separate controls
  • CMD switching= C312
  • CMD channel 1= Communication card
  • CMD channel 2= Terminal control
  • Ref 2 Switching= C313
  • Ref 2 Channel= AI1 or AI2
Show More