Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84667members
354058posts

[Imported] CID and ICD file creation

Remote Operations Forum

Collaborate and share knowledge on the extensive range of remote systems and devices, including SCADA radios and RTUs, on the Schneider Electric Exchange Remote Operations (formerly SCADA & Telemetry) forum. From commissioning SCADA integration devices and software, to enhancing existing installations or troubleshooting, connect with a global community of experts and users. Subscribe today.

sbeadle
Janeway Janeway
Janeway
0 Likes
0
847

[Imported] CID and ICD file creation

>>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.

_______

**_ST3000:
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.
Steve_**

______________

bevanweissP:

ave you read the user manual?
[https://www.schneider-electric.com/resources/sites/SCHNEIDER_ELECTRIC/content/live/FAQS/285000/FA285... "https://www.schneider-electric.com/resources/sites/SCHNEIDER_ELECTRIC/content/live/FAQS/285000/FA285...")

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
[http://download.schneider-elec...20configuration%20tool](http://download.schneider-elec...20configur... "http://download.schneider-elec...20configuration%20tool")

__________________

**_ST3000:
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._**

________________

bevanweiss:
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

_________________

**_ST3000:
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...._**

___________________

**_ST3000:
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._**

___________________

bevanweiss:
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)


_MyModbusDevice.icd
100
MyModbusDevice
MyModbusDeviceFamily
MyModbusDeviceApplication
UNK:MyModbusDevice
MODBUS
1
{TABLE1_CONF_HERE}
{TABLE2_CONF_HERE}
{TABLE3_CONF_HERE}_


... 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)

T:MV;m:1100:u1;R:3209;L:P:32

1

... each 61850 data point to be exported, along with it's quite complicated data formatting descriptor