>>Message imported from previous forum - Category:Communications Products <<
User: mchartrand, originally posted: 2018-10-25 17:52:13 Id:260
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.
CID and ICD file creation.
Hi, I have a system that is using a PowerLogic G3200 to convert Allen Bradley MicroLogix 1100 Modbus to IEC 61850, but I am lost when it comes to creating an ICD / CID file.
Does anyone have any experience in doing this?
I have no help from Schneider technical support, they say the G3200 is not supported.
Thanks in advance.
ave you read the user manual?
It also looks like the software tool you are after for easier editing/creating of the ICD/CID is:
CET850 IEC 61850 configuration tool V2.1
Yes, I have read the user guide and I have the software.
It seems overly complicated.
I'm going to re-read the user guide again this morning in case I've missed something, but I doubt it._**
IEC 61850 is complicated.
You couldn't just use Modbus to get the data into the SCADA system?
If you post your ICD file then perhaps we can help.
NOTE: You are not trying to talk to a Micrologic... This is not the setting you should be trying to use. Schneider Micrologic != Allen-Bradley MicroLogix
No, the existing system is already implementing IEC61850.
I assume that Modbus and 61850 are not compatible with each other without a gateway?
I do not have an ICD file, that is the problem...._**
Using CET850 software, the only options available are for schneiders own branded IEDs.
I can create a .cid file for a generic component, but my confidence in this actually communicating on the 61850 is low. It seems very simple compared to Scheiders very complicated .cid files for simple IEDs like a breaker or motor._**
You will need to make your own ICD file, which seems painful, but far from impossible.
You should know the Modbus registers that you are interested in.
So... you start with Device Characteristics (like the example given in the user guide)
... Insert additional Modbus Tables required to be polled, don't include registers below that aren't scanned here
And then define the logical node (i.e. the Modbus device instance)
... each 61850 data point to be exported, along with it's quite complicated data formatting descriptor