When you create an instance of a device from an EDS file in your RSLogix 5000 environment; the EDS file provides a Module Defined Data Type for the inputs and outputs of the device. This Module Defined Data Type’s name is automatically generated by the EDS file creation’s software and is based upon (among other things) a checksum of the items in the file. This often creates a somewhat cryptic alpha-numeric string for the name.

In situations where you may inherit an existing program and your RSLogix 5000 environment is missing the EDS file used for this program; you will need to determine which version of EDS file was used and then go find it on our Pulseroller.com web site. Similarly, you may also have the situation where you need to be able to match your AOI version to its correct EDS file. The following chart cross references the most common EDS files, AOI files, and Module Data Types

EDS File Module Mode AOI File Module Data Type
ConveyLinx-Eco_v1_1.eds ZPA Mode ConveyLinxEco_ZPA.L5X Input: _055C:ECO_D4234560:I:0
Output: _055C:ECO_3015BAF1:O:0
ConveyLinxEco_ZPA_Reduced.L5X Input: _055C:ECO_F8CE6F45:I:0
Output: _055C:ECO_8769D2C2:O:0
PLC I/O Mode ConveyLinxEco_PLCIO.L5X Input: _055C:ECO_C92675D8:I:0
Output: _055C:ECO_7DDD1BFA:O:0
ConveyLinxEco_PLCIO_Reduced.L5X Input: _055C:ECO_1CE0FE4B:I:0
Output: _055C:ECO_19B04D77:O:0

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment