Hello:
Normally EDS files are created by EtherNet/IP, DeviceNet, vendors. The ODVA has the so-called EZ-EDS (pronounced "Easy EDS") which is a Windows tool for the edition of EDS files. It is available for download free of charge.
To answer your question, it is possible to create assemblies that are composed of different data types, just like you describe. There is also an EDS specification which is part of the ODVA specification, but this has to be purchased from the ODVA. The easiest way to do what you want is to start from an existing EDS file. You need to change the revision of the EDS file so LogixDesigner will let you register it if you have already registered the original EDS. (Note: Something like Rev 3.0 will not cause syntax check in EZ-EDS, but you will get an error when you attempt to register with Logix. You should use something like 3.2, or 5.6 (5 for major and 6 for minor, but never 0 for minor revision).
For the change you mention, first create (or edit) the list of parameters in the parameter section. You create the parameter and assign the data type to each parameter. Then you create the assembly, assign the assembly instance and at the end add the parameters that constitute the assembly in the order they must reside within the assembly. Finally you go to the Connection session and create the IO connection. For this you need familiarity with CIP path, but if you using an existing EDS file, this section should not be changed.
The link for the EZ-EDS is below.
https://www.odva.org/subscriptions-services/software/ez-eds-download/
Can you please post the link for this Rockwell manual? I need to have a look at it so I can understand what you mean. Also, i am confused about the statement of trying to decode the HEX. Do you mean the HEX in the LK5 project?
If you let me know the HEX data, maybe I can help you. Is it something like 20 04 20 64 30 03? If so this would be the CIP path for the assemblies that contain the data for produced and consumed data. I can explain the syntax for the CIP path in this case.
Welcome to the PLCTalk Forum Community !
Let's take a step back. Are you building a new CIP networked device ? On which network (Componet, DeviceNet, ControlNet, EtherNet/IP) ? Is your employer a member of ODVA ?
Or are you trying to modify or improve the way another device interacts with Studio 5000, RSNetworx, or another tool ?
I think what you're asking for is an explanation of the sections of an EDS that describe the I/O assemblies so that Studio 5000 can create a complex module-defined datatype associated with the device. That is part of the "EDS base Add On Profile" feature whose reference manual you linked to.
An additional tool you should probably have is "EZ-EDS" software from ODVA, which does hex decoding and EDS verification far better than I can do it by hand.
So here are a few examples of the data types being referenced in the EDS:
0xC8 = ?
0xD2 = ?
0xC7 = ?
ETC.
There must be some key or something that tells you what the different ones are, but not that I can find in the manual anywhere.
Hello:
Normally EDS files are created by EtherNet/IP, DeviceNet, vendors. The ODVA has the so-called EZ-EDS (pronounced "Easy EDS") which is a Windows tool for the edition of EDS files. It is available for download free of charge.
To answer your question, it is possible to create assemblies that are composed of different data types, just like you describe. There is also an EDS specification which is part of the ODVA specification, but this has to be purchased from the ODVA. The easiest way to do what you want is to start from an existing EDS file. You need to change the revision of the EDS file so LogixDesigner will let you register it if you have already registered the original EDS. (Note: Something like Rev 3.0 will not cause syntax check in EZ-EDS, but you will get an error when you attempt to register with Logix. You should use something like 3.2, or 5.6 (5 for major and 6 for minor, but never 0 for minor revision).
For the change you mention, first create (or edit) the list of parameters in the parameter section. You create the parameter and assign the data type to each parameter. Then you create the assembly, assign the assembly instance and at the end add the parameters that constitute the assembly in the order they must reside within the assembly. Finally you go to the Connection session and create the IO connection. For this you need familiarity with CIP path, but if you using an existing EDS file, this section should not be changed.
The link for the EZ-EDS is below.
https://www.odva.org/subscriptions-services/software/ez-eds-download/