In an attempt to establish communication between a 1769-L16 PLC and a Beckhoff EL6652 EtherNet/IP Master, I require 8 integer and 2 floating-point data types. Generating EDS files for both data types individually in TwinCAT software is successful. However, when generating an EDS file for both integer and floating-point data types simultaneously, the module in Studio 5000 shows a fault. Has anyone encountered this issue when working with both floating-point and integer data types simultaneously?
We have successfully completed this process in the past, although it has been a while and some specifics may be hazy. One important detail to remember is inputting the precise total size of data being transferred between systems. This specification is crucial on the TwinCAT platform, as the byte value entered must match the exact number of bytes being exchanged. It is essential to avoid setting a higher value than necessary. Additionally, it is recommended to use a DINT on the RS Logix side if an INT is being used on the TwinCAT side. For further guidance on sharing data between RA PLC and TwinCAT, refer to the documentation for TF6281 provided. This document includes a step-by-step walkthrough of the process.
It seems to me like you could be having a problem with how the software handles data type compatibility when both are used simultaneously. TwinCAT might be getting confused when more than one data type is presented, especially considering the complexity difference between integer and floating-point types. I would recommend checking the PLC-Beckhoff connection setup. Also, review the specifications to ensure they can function with both data types together. You can separate the types into different EDS files too, then merge them in Studio 5000, ensuring they retain their individual properties.
This indeed appears to be a common issue, and it seems to be connected to how Studio 5000 and TwinCAT software manage different data types. They may be interpreting the combined EDS file differently, and thus causing a fault. A potential workaround could be splitting your communication into two sections - one for integers and the other for floating-points. While this may not be the most elegant solution, it could at least keep your operation running smoothly while you troubleshoot the issue further. I'd also advise reaching out to the software vendors for extended technical support on this one as there may be patches or updates available that address this problem.
I've run into similar issues before when trying to mix data types in EDS files. It's possible that the fault you’re seeing in Studio 5000 could be due to a mismatch in how the data types are defined or how they are handled in the communication protocol. Sometimes, specific configurations or parameters need to be set up correctly to accommodate both types. I would recommend checking the data type alignment in your EDS file and ensuring compatibility with the PLC. Also, sometimes separating them into different modules or instances can help alleviate the issue. Good luck, and I hope you find a solution!
✅ 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: Answer: To generate EDS files for integer data types in TwinCAT 3, you can follow the steps outlined in the TwinCAT software documentation specific to EDS file generation.
Answer: Answer: To establish communication between a 1769-L16 PLC and a Beckhoff EL6652 EtherNet/IP Master, you need to ensure proper configuration settings for both devices and compatible communication protocols.
Answer: Answer: Generating EDS files for floating-point data types in TwinCAT 3 involves similar steps to generating EDS files for integer data types. Refer to the TwinCAT software documentation for specific instructions.
Answer: Answer: The fault in Studio 5000 when generating an EDS file for both data types simultaneously could be due to compatibility issues, conflicting configurations, or errors in the EDS file generation process. Troubleshooting these aspects can help identify the root cause of the fault.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.