Image of  DI-MA DALi Infinity 5 pole snap in screw connector male blue

Dalicontrol Snap in Screw Connector Male Blue Dali 2, 5 Pole, 20A

Catalogue Number: DI-MA
Image of  DI-MA DALi Infinity 5 pole snap in screw connector male blue
Retail
N/A
RRP (Inc. GST)

Specifications

hide show
Product brand
Clipsal
Range of product
DALI Infinity
Package 1 Weight
0.05 kg
Package 1 Height
15 mm
Package 1 width
50 mm
Package 1 Length
50 mm
Sustainable offer status
Green Premium product
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
envpep090103en

Frequently Asked Questions

hide show

What current can the DI-SS carry?

The DI-SS starter socket is rated at 20A.

Support on Buildings Management Systems and Pelco Security Solutions

 For support on Buildings Management Systems and Pelco Security Solutions please visit:  https://buildingskb.schneider-electric.com/

Which anti-virus softwares are compatible with Vijeo Citect 7.0

Anti-virus software may be used with Vijeo Citect on computer but that may result dismal performance like trend gaps, extraneous I/O update times and slow page updates.

Be aware that when virus scanning software is enabled there may be issues with trend history files and other files actively being written to.

In typical real-time environments data needs to be requested, collected, processed and later stored without delays. Vijeo Citect needs regular write access to the trend history files. Delays and potential locking of files by virus scanning each file write may lead to high CPU usage and instability.

We recommend that the trend history files (and other files actively written to) are not included in virus scanning on writes. If anti-virus software is required, find a product that result in acceptable performance. The Citect corporate standard, McAfee, is a good option.

Be sure to test the performance impact with actual I/O devices, i.e. not with disk devices.

Energy Certificate workflow

Goals and Symptoms

Energy Certificate workflow

Since Energy Certificate does not show up in Portlet tree list, may be difficult for user to realise this is selectable in chart under Analysis after creating an Energy Certificate from the top menu.

Causes and Fixes

The energy certificate allows you to create differents templates. Then on each chart, you decide to switch to an EnergyCertificate view and select the associated template.

This workflow is similar to the Dynamic Display one. Will just need to be called out in user guide to find Energy Certificate template selection in Specific Analysis.


Legacy KB System (APS) Data: RESL208830 V1.0, Originally authored by AdDi on 08/10/2012, Last Edited by AdDi on 08/10/2012
Related ranges: Vizelia

Does PowerSCADA Operation support communication with IEC 61850 devices based on Parallel Redundancy Protocol?

Applies to:
All PowerSCADA versions using IEC61850N driver, although it refers to the current PowerSCADA version at the moment of publishing.

Question:
Does PowerSCADA Operation support communication with IEC 61850 devices based on Parallel Redundancy Protocol?

Answer:
YES, PowerSCADA Operation 8.2 (PSO) supports communication with other IED nodes as defined by IEC 61850 standard, over a network that uses Parallel Redundancy Protocol (PRP) nodes as defined in the standard IEC 62439-3 (March 2016).
Implementing the IEC 61850 standard, PSO can communicate as a Client with any Server (IEDs) by using the native IEC61850N driver.
The IEC61850N communication driver uses MMS (Manufacturing Message Specification) which is an Application Layer protocol (7th, top layer of OSI model).
PRP is a Link Layer redundancy protocol (Layer 2 of OSI model), which allows higher layer network protocols to operate without modification.
This means that MMS protocol works without problems, further means that PowerSCADA Expert IEC61850N driver will work.
PRP implements redundancy in the nodes rather than in the network.
Thus, to connect a PowerSCADA Server node to such network, a Redundant Box (RedBox) device is needed.
For redundant PowerSCADA server nodes, a RedBox device is needed for each node.
This RedBox requirement should not be seen in any way as a limitation of PowerSCADA software, it is a hardware device that is needed to connect to such a redundant network.
 
Created on April, 11th 2018 by
Adrian Dicea
PowerSCADA Product Prime @ Expert Level - Global Technical Support

PowerSCADA Expert - A way to fix Gateway Exceptions 0xB for Modbus Slave devices behind EGX100

Customer Issue:
Frequent disconnection for MODNET11 type IODevices behind an EGX100 Gateway.
Project was a DataCenter in UK.
Devices are DAC - Dry Air Cooler.
PSE 7.40 SR1 + HFs and Drivers used are the latest to date.
Glossary: PSE = PowerSCADA Expert; SR1 = Service Release 1; HFs = HotFixes

Resolution:
Several attempts to tune the Timeout, Retries and Driver Error Masking (Citect's KB - Q5923 Driver Error 00008203 (0x0000200b) with MODNET driver when connecting via a gateway) on PSE side, Response Time on serial port of EGX100 side, were not helping at all.
The EGX100 was replying with exception responses as if DAC devices were offline: GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND_EXCEPTION = 0xB
It was happening several times during runtime (I cannot say the period), but the response was not always neither to the same registers request, nor persisting more than 1 response/frame, meaning that the next Modbus request from PSE was answered properly.
It looked like a problematic Modbus Slave device.
The only efficient way to fix it was by replacing the IODevice Protocol MODNET with PwrModbus and enabling RetryException in [PWRMODBUS] section of citect.ini:
[PWRMODBUS]
RetryException = 1
Note: RetryException = 0 by default, meaning that retries on exceptions are disabled. More info about this parameter (like to what exception codes it retries) are found in PwrModbus Driver's help and the same in PowerSCADA Expert System Integrators Manual.
The number of default retries for PwrModbus driver is 3; this is handled by "[PWRMODBUS]retry" parameter.
I reduced this to [PWRMODBUS]retry = 2 and in this case and it worked, however it is something that can be tuned.

This RetryException is a feature that PwrModbus driver has, while MODNET hasn't (among others).
                                            
Created on 3rd AUG 2015 by
Adrian Dicea
Global Expert Technical Support Engineer - Support Prime PSE / EGX

Single Line Configuration utility: The active project is not showing in the list of projects

Applies to:
PSO 8.2 and Cumulative Updates (1 through 7)

Issue:
When opening the Single Line Configuration utility the active project is not showing in the list of projects.

Causes:
If the main project is not including "PLS_Include" but a renamed copy of the original "PLS_Include", then the Single Line Configuration utility will not detect and will not add the main project into the list of projects.

Fixes:

*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).

To make this work, replace the "PLS_Include" name with the new project name inside these 2 configuration files: GenieDefinitions.xml and SupportedGenies.xml.
In GenieDefinitions.xml there is originally a "Project" XML tag having "PLS_Include" as name attribute:
<?xml version="1.0" encoding="utf-8"?>
<GenieDefinitions>
  <Project name="PLS_Include">
This string has to be changed to the new included project name.

The same in SupportedGenies.xml there is originally a "Project" XML tag with "PLS_Include" name attribute:
<?xml version="1.0" encoding="UTF-8"?>
<SupportedGenies>
    <Project name="PLS_Include">
This string has to be changed to the new included project name.

 

G3200 using IEC61850 - How to detect if Modbus Slaves are offline

Goals and Symptoms

G3200 and PowerSCADA (or any IEC61850 Client Software): How to detect if the Modbus Slave is Offline to prevent invalid values?

Facts and Changes

Having G3200 Firmware v1.4, PM820 meter connected to G3200 over RS485 as a Modbus Slave, PowerSCADA (as IEC61850 Client) connected to G3200 on Ethernet port.
If the communication between the G3200 and the PM820 is broken, then the values (last values of the PM820) are still available over the G3200.
In this case, would be better to have all PM820 data become invalid or to have a way to trigger an alarm about this, wouldn't be?
Is there a possibility to change this in the CID file or in the G3200 firmware, or what is the solution?

Causes and Fixes

Current firmware implementation in G3200 doesn't support updating IEC 61850 data structure when the connected device (Modbus Slave) is offline.
PowerSCADA (or any other IEC61850 Client software) connected to G3200 should check the values of LLN0 and LPHD Logical Nodes under each Modbus Slave device defined in the CID file.
If It finds LLN0.ST.Mod = 5(OFF) then it should trigger an Advanced Alarm for that Modbus Slave device.

LLN0 and LPHD are the two logical nodes dedicated for physical device health and status.

Case1: When Modbus Slave device is "Online"
LPHD1.ST.PhyHealth = 1(OK)
LLN0.ST.Mod = 1(ON)

Case2: When Modbus Slave device is "Offline"
LPHD1.ST.PhyHealth = 3(Alarm)
LLN0.ST.Mod = 5(OFF)



G3200 updates the whole IEC 61850 data structure of the device if, and only if, the device is Online.
Then, it reads the data from device using Modbus functions and updates the IEC 61850 data structures.
If devices get disconnected, Measures, Quality and Timestamp won't be updated. However, the above mentioned nodes: "LPHD1.ST.PhyHealth" and "LLN0.ST.Mod" are updated and their values could serve as device status monitoring.

                                            
Created on 13th MAY 2013 by
Adrian Dicea
PowerSCADA Product Prime @ Expert Level - Global Technical Support

Related ranges: G3200, PowerSCADA, IEC61850, Modbus

PowerSCADA Operation 8.2: "DLL call timed out" when trying to open Advanced Reports


Applies to:
PowerSCADA Operation (PSO) v8.2 (and version updates) with compatible Advanced Reports & Dashboarding (AR&D) module.
By version updates are understood any PSO Service Releases, PSO Service Packs, PSO Updates or PSO Hotfixes applied on the base PSO release version.


Issue:
Cannot display Advanced Reports in PSO Runtime. When opening the web report page the "DLL call timed out" error pops up:




Among of the identified possible root causes of this issue were:
Either a missing SSO Password or a wrong SSO Password encryption.


The above causes have these symptoms:
In Advanced Config Utility (ACU) tool there is an empty field "SSO Password".
To see this, in ACU tool > "Security" section > "Single Sign On" > "Application: Advanced Reporting" > Editing the existing user opens up the "Edit User" window, which shows empty field "SSO Password" for the corresponding "SSO User":



This happens if the ACU tool is not able to decode the encrypted SSO Password string, or the SSO Password was manually deleted and re-encrypted as empty string.
It is not possible, through ACU not to enter a SSO Password, because the "Edit User" window will not validate this situation.
Another possiblity, although not tested, could be that the project was created on a different machine and/or in a lower PSO version, then restored on the current PSO machine.


The fix for this is:
In ACU tool a valid "SSO Password" has to be re-entered for the "SSO User".
The changes have to be saved after closing the "Edit User" window.
There are no other operations necessary (like CoreServiceHost service restart or PSO runtime restart).


 

Created on December, 21st 2017 by
Adrian Dicea
PowerSCADA Product Prime @ Expert Level - Global Technical Support

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