When installing an IFM AL1322 IO-Link Master Module on a 1756-EN2T Ethernet Card connected to a 1756-L82E Controller, you may encounter a difference in the input and output data structure. Instead of an array named 'Data', the file contains individual tags such as Input_Data1, Input_Data2, etc., all of type UINT. However, when the same module is added to a 1769-L30ER Compact Logix Controller, the expected array tag 'Data' is present in the input file. Unfortunately, the Input_Data1 format is not compatible with the AOI from IFM. How can you ensure that the module generates the 'Data' Array on the L82E Controller? Refer to the image for a visual comparison of the input data structures on both controllers.
I have encountered the same problem with the latest versions of the studio software. Although I'm unsure of the solution, reverting back to v33 through flashing may rectify the issue with the data type, irrespective of the controller series. If you discover a permanent solution, kindly share it with us!
One effective method is to perform a Copy Operations (COP) or preferably, a Copy Struct (CPS) since it involves input/output data, to transfer the data into a custom User-Defined Type (UDT) with the appropriate format. Afterwards, you can easily reference this UDT within the Add-On Instruction (AOI).
If you are using Studio 5000 versions 34, 35, or 36, you may be experiencing difficulties with Studio 5000 Logix Designer updating EDS AOP module tags.
ASF suggests utilizing a simple Copy-on-Write (COP) or preferably a Copy-on-Share (CPS) operation for transferring I/O data into a custom User-Defined Type (UDT) structure. This UDT can then be referenced in the Add-On Instruction (AOI). COP() is recommended when the destination data is solely utilized within the same task where COP() was executed. If ensuring the atomicity of data shared across multiple tasks is crucial, then CPS() is the preferred option.
It is advisable to use CPS when dealing with I/O data, as the I/O updates independently of the program scan. If a section of the process data is a REAL and needs to be split into two INTs before being recombined at the PLC end, there is a risk of the I/O updating during a COP operation. This could result in data corruption, leading to a #Q.NAN error in your REAL data for a single scan. CPS helps to prevent the I/O image from being updated until the copying process is finished. For more information, refer to Knowledgebase Article ID: QA3295 (techconnect access required).
From my experience, the difference in input and output data structures between these two configurations is largely due to the different PLCs they are connected to. 1756-L82E controller is a part of ControlLogix series whereas the 1769-L30ER belongs to CompactLogix series, both by Rockwell Automation. I think the discrepancies might have to do with how these two series handle I/O data. It seems like you may need to manually modify the data structure in the 1756-L82E controller to make sure it generates 'Data' array. Alternatively, you might consider reaching out to IFM's technical support or checking if there's a firmware update available that resolves this issue.
That's an interesting issue! It seems like the difference in data structure between the L82E and the Compact Logix is really causing some headaches. One way to tackle this would be to check if the configuration settings for the AL1322 module in Studio 5000 are set correctly on the L82E. Sometimes, there are properties or settings that dictate how the data is structured, and ensuring those match what you had in the Compact Logix might help. Additionally, consider reaching out to IFM support to see if they can provide a specific workaround or firmware update that might address this compatibility problem with the AOI. Good luck!
It sounds like you're running into a common issue with the data structure when switching between controllers. One way to ensure that the IFM AL1322 module generates the 'Data' array on the L82E is to double-check your module's configuration in the I/O setup. Make sure that the settings align with the expected data structure used in the AOI. Sometimes, reconfiguring the module's tags in the controller's I/O configuration can help to standardize the data output. Additionally, consider reaching out to IFM's technical support; they often have insights or specific firmware versions that can resolve these incompatibilities.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The data structure differences arise due to variations in how the controllers handle the input and output data arrays.
Answer: - To ensure the generation of the 'Data' Array on the 1756-L82E Controller, you may need to check the configuration settings and possibly make adjustments to align with the expected format.
Answer: - If the Input_Data1 format is not compatible, you may need to explore potential solutions such as adjusting data structures, configurations, or seeking support from IFM for guidance on compatibility issues.
Answer: - When working with data arrays and modules on ControlLogix controllers, it is essential to be aware of potential variations in data structures across different controllers and to ensure compatibility between modules and the controller's data handling mechanisms.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.