Protection & Control
Schneider Electric support forum about Protection Relays, Substation Controllers & RTUs, Arc Flash Devices & Systems in Medium Voltage and Low Voltage. A place to get support on product selection, installation, commissioning and troubleshooting.
Link copied. Please paste this link to share this article on your social media post.
I am trying to create a configuration for an HUe RTU that will act as a 61850 server. and will eventually communicate with a PowerSCADA Operation system. The RTU will have local acquisition modules and will also communicate to downstream IEDs using Modbus TCP/IP.
I have configured the 61850 server node in Easergy Builder with logical nodes, datasets and report control blocks so that local acquisition data can be published upstream, but I'm not sure what I need to add in order to support the monitoring and control of the downstream IEDs.
Any advice will be greatly appreciated.
Link copied. Please paste this link to share this article on your social media post.
The general steps are :-
- Use the Easergy Builder IEC 61850 plugin, ICD editor to create a new ICD with the Logical Nodes to hold the data for each type of Modbus device.
- In the IEC61850 plugin, use the new ICD to create a new Logical Device (and NOT a physical device) This updates the SCL but not the variables.
- In Easergy Builder, create the remote Modbus device(s) and create their variables as usual
-- For status and analogs, set the source addresses for Modbus, and the i61 bin controller as the destination.
-- For commands, the i61 bin controller is the source and the Modbus device is the destination
- Set up / extend the report control blocks and datasets for data from the Logical Device(s).
(I find CET850 is much easier to use for this than Easergy Builder)
If the remote device is a Schneider product, please let me know.
I may be able to find a suitable ICD, and/or I have an experimental Excel tool that generates an ICD file from a list of variables.
Link copied. Please paste this link to share this article on your social media post.
The general steps are :-
- Use the Easergy Builder IEC 61850 plugin, ICD editor to create a new ICD with the Logical Nodes to hold the data for each type of Modbus device.
- In the IEC61850 plugin, use the new ICD to create a new Logical Device (and NOT a physical device) This updates the SCL but not the variables.
- In Easergy Builder, create the remote Modbus device(s) and create their variables as usual
-- For status and analogs, set the source addresses for Modbus, and the i61 bin controller as the destination.
-- For commands, the i61 bin controller is the source and the Modbus device is the destination
- Set up / extend the report control blocks and datasets for data from the Logical Device(s).
(I find CET850 is much easier to use for this than Easergy Builder)
If the remote device is a Schneider product, please let me know.
I may be able to find a suitable ICD, and/or I have an experimental Excel tool that generates an ICD file from a list of variables.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.