Quantcast

Mounting Block, 1 Gang, 103x49x25mm

White Electric | Mounting Block, 1 Gang, 103x49x25mm

Mounting Block, 1 Gang, 103x49x25mm

Item Number: 47-WE

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Product brand

Clipsal

Sustainable offer status

Green Premium product

Physical

REACh Regulation

Free of Substances of Very High Concern above the threshold

REACh free of SVHC

Yes

EU RoHS Directive

Pro-active compliance (Product out of EU RoHS legal scope)

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)

Environmental Disclosure

ENVPEP110719EN

Others

Package 1 Bare Product Quantity

1

Unit Type of Package 1

PCE

Number of Units in Package 1

1

Package 1 Height

2.5 cm

Package 1 Width

10.3 cm

Package 1 Length

4.9 cm

Package 1 Weight

36 g

Unit Type of Package 2

BB1

Number of Units in Package 2

5

Package 2 Height

8.8 cm

Package 2 Width

10.4 cm

Package 2 Length

12.6 cm

Package 2 Weight

0.22 kg

Unit Type of Package 3

CAR

Number of Units in Package 3

50

Package 3 Height

23.7 cm

Package 3 Width

20.3 cm

Package 3 Length

30 cm

Package 3 Weight

2.2 kg
Show all specifications

Frequently Asked Questions

hide show

What is the voltage tolerance level at nominal voltage for the electrical auxiliaries used in Low Voltage Circuit Breakers

The voltage tolerance level for the electrical auxiliaries (example: undervoltage release(Mn), shunt coil(Mx)) used in Low Voltage Circuit Breakers is defined as per the IEC 60947-2 standard.
 
The tolerance level defined by IEC60947-2 is 0.85% for minimum nominal voltage (Un) and 1.1% for maximum nominal voltage (Un).
 
Example:
For Un = 220 Vac, Minimum tolerance Level is (0.85% of 220 V AC) = 187 Vac, Maximum tolerance Level is (1.1% of 220V AC) = 242 Vac. This means voltage range : 187 VAC - 242 Vac.

Where to download the firmware (V 1.13.0) for SpaceLogic C-Bus Controllers NAC and AC?

The new firmware (version 1.13.0) for SpaceLogic C-Bus Controllers NAC and AC is available for download on se.com. and in Exchange Platforms

The new firmware version V1.13.0 is available for 5500NAC2, 5500AC2, 5500NAC, 5500SHAC, LSS5500NAC, LSS5500SHAC.

The main features of this new firmware release  (V1.13.0) are:
 

  • Scheduler Enhancement
  • Error reporting application improvements
  • Bug fixes

Related documents can be downloaded along with the firmware file:
  • Release Notes for V1.13.0
  • User Manual update for firmware V1.13.0
Links for www.se.com page and Exchange to download the firmware and the related documents:
 
 
5500NAC2
SpaceLogic C-Bus Network Automation Controller
Commercialized
 
 
Se.com: Link   
 
Exchange:
Firmware download page link
 
Direct link to the firmware file
 
5500AC2
SpaceLogic C-Bus Application Controller
Commercialized
 
 
Se.com: Link 
 
Exchange:
Firmware download page link
 
Direct link to the firmware file
 
5500NAC
C-Bus Network Automation Controller
End of Commercial
 
 
Se.com:  Link   
 
Exchange:
Firmware download page link
 
Direct link to the firmware file
 
5500SHAC
Wiser for C-Bus Automation Controller
End of Commercial
 
 
Se.com: Link
 
 
Exchange:
Firmware download page link
 
Direct link to the firmware file



 

How to change the power sign on 5.2E, 6.2E, 5.3E,6.3E trip units for Powerpact H, J and L frame breaker?

Issue:
How to change the power sign on 5.2E, 6.2E, 5.3E,6.3E trip units for Powerpact H, J and L frame breaker?

Product Line:
Powerpact H, J and L

Resolution:
The power sign can be changed through Modbus registers or with RSU software and UTA test kit STRV00910.

RSU:
Modify the Power sign using the RSU software and UTA Tester STRV00910, see link for free RSU download.
https://www.se.com/us/en/download/document/Micrologic_RSU_Compact+NSX_rev_13.3.2_Setup/

In the Metering setup/Power sign window, select the power sign:
• + The power running through the circuit breaker from top to bottom is
counted positively.
• - The power running through the circuit breaker from top to bottom is
counted negatively.
The default value of the power sign is +.


MODBUS:
Power Flow
Sign 3316 3315 RW — — UINT 0–1 E
Power flow sign
0 = the active power flows from upstream (top) to downstream (bottom) (default).
1 = the active power flows from downstream (bottom) to upstream (top).
The power flow sign command (command code = 47240) configures the content of the power flow sign register.

8000 7999 — — UINT 46240 E Command code = 46240
8001 8000 — — UINT 12 E Number of parameters (bytes) = 12
8002 8001 — — UINT 5121 E Destination = 5121 (0x1401)
8003 8002 — — UINT 1 E 1
8004
8005
8003
8004 — — STRING — E Level 4 password (default value = ‘0000’ = 0x30303030)
8006 8005 — — UINT 0–1 E
Power flow sign
0 = the active power flows from upstream (top) to downstream (bottom)
(default)
1 = the active power flows from downstream (bottom) to upstream (top).
 

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:
 

ViewX

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 To Update SCADAPack x70 Firmware & Bootloader

Firmware and Bootloader files come with the Remote Connect installation package. 
Please download the latest RemoteConnect for the SCADAPack x70
 
Under My Network, right-click on SCADAPack x70 Controller Settings -DeviceDTM and select Additional Functions > Update Device Firmware or Bootloader. 

remoteconnect

Select Update Device System firmware and click next

remote connect

Select the latest firmware version for the list and click next. The process starts and it takes a while to complete. 

remote connect

The firmware file has a .biz file extension. By default, the firmware file is stored in one of the following directories:
64-bit systems: C:\Program Files (x86)\Schneider Electric\RemoteConnect\Firmware\SCADAPack XXX
32-bit systems: C:\Program Files\Schneider Electric\RemoteConnect\Firmware\SCADAPack XXX

To read about updating the firmware and bootloader instructions refer to the Maintenace section of User Manual
scadapack 474
 

SCADAPack X70 Intermodule Cables Selection

SCADAPack X70 Series with 6000 I/O (20-pin to 20-pin) Expansion module cable

6000 expansion modules do include a 2-inch inter-module cable inside the box. A longer cable can be ordered separately if it is required

Expansion module cable part number:

  • TBUM297918    Shielded intermodule cable, 12 inches (0.3m) long
  • TBUM297919    Shielded intermodule cable, 18 inches (0.45m) long
  • TBUM297920    Shielded intermodule cable, 24 inches (0.61m) long
  • TBUM297921    Shielded intermodule cable, 30 inches (0.76m) long
  • TBUM297922    Shielded intermodule cable, 45 inches (1.14m) long
  • TBUM297923    Shielded intermodule cable, 72 inches (1.82m



SCADAPack X70 to 5000-Series I/O Modules

SCADAPack X70,  SCADAPack 53xE, and 6000 series I/O expansion modules provide a 20-pin I/O bus connector while 5000 series modules provide a 16-pin connector. Use the adaptor provided (part number TBUM297138) to transit from a 20-pin connector to a 16-pin connector. The length of the cable is between 2 and 2.5 inches as shown below. 

TBUM297138 Adapter Cable for SCADAPack

In case your installation requires a longer cable, you will need extension cables. An example of the setup is provided below. 


Example: 
SCADAPack 53xE or 47x or 57x RTU or 6000 series I/O (with provided 20-pin IMC female connector)

to

TBUM297138 Adapter cable (20-pin male to 16-pin female IMC)

to

TBUM297212 IMC cable extension adapter for 5000-Series I/O modules (16-pin male to 16-pin male IMC)

to

One of the six IMC cables listed below for 5000-Series I/O modules (16-pin female to 16-pin female IMC)

  • TBUM297269 Shielded intermodule cable, 12 inches (0.3m) long
  • TBUM297192 Shielded intermodule cable, 18 inches (0.45m) long
  • TBUM297193 Shielded intermodule cable, 24 inches (0.61m) long
  • TBUM297131 Shielded intermodule cable, 30 inches (0.76m) long
  • TBUM297162 Shielded intermodule cable, 45 inches (1.14m) long
  • TBUM297174 Shielded intermodule cable, 72 inches (1.82m) long

to

 A 5000-Series I/O module (16-pin male IMC)

Show More