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

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

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

Item Number: DI-MA

Retail
N/A
RRP (Inc. GST)

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Product brand

Clipsal

Range of product

DALI Infinity

Sustainable offer status

Green Premium product

Physical

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

Others

Package 1 Weight

0.05 kg

Package 1 Height

15 mm

Package 1 width

50 mm

Package 1 Length

50 mm
Show all specifications

Frequently Asked Questions

hide show

What current can the DI-SS carry?

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

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, PSO 9.0 - main versions and all their cummulative updates

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

Cause:
1) 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.
2) If the main project uses only custom genies and there are no GenieTypes those genies are defined in a different.
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.

 
Show More