I am attempting to integrate Codesys with multiple Moxa ioLogik E1200 series DIO devices, specifically the E1210 and E1211 models. I have successfully configured Codesys to write to the E1211 DOs through the EtherNet/IP I/O Mapping interface. During testing, I have connected some of the DOs directly to DIs, allowing me to observe changes in the corresponding DIs when writing to a DO. The device itself reflects these changes in DI values. Wireshark captures the modified DI values transmitted to Codesys via an implicit message. However, the DI values do not update on the EtherNet/IP I/O Mapping screen for the E1210 DI device. I have utilized an EDS file provided by Moxa. Could it be possible that Codesys is anticipating a "32 bit run/idle header" in the message, despite the "Real time transfer format" being designated as "connection is pure data and is modeless" in EZ-EDS? This scenario would result in Codesys interpreting the initial 4 bytes of data as a header and utilizing the subsequent values as DI values. I am skeptical that this is the root cause. Are there any alternative suggestions or solutions that could be explored?
Have you ensured that the inputs you are using are properly mapped to tags? By default, if the values are not mapped, they will not be scanned. You can adjust this setting by selecting "always in bus cycle task" in the dropdown menu located at the lower right corner of the mapping screen. This will ensure that all inputs are included in the scanning process.
Dear Norm, thank you for your suggestions. I have successfully mapped the inputs to variables and have selected Enabled 1. When using Wireshark, I can see the Moxa device sending the IO values, however, the updated values are not appearing in Codesys.
Interesting troubleshooting challenge you've got there! Based on your description, there could be several causes to your issue, but let's rule out possible miscommunication first. Are you sure about the compatibility and communication settings between the Codesys platform and your E1210 and E1211 devices? Sometimes, devices have specific communication parameters which Codesys needs to recognize accurately for efficient mapping. Ensure that the firmware version of the DIs supports the Ethernet/IP protocol correctly, as any discrepancy might lead to incomplete or erroneous mapping. Beyond that, you could try to create a custom EDS file rather than using the provided one, since it's possible there could be an untackled bug or compatibility issue within the file. Keep us updated!
The fact that the DI values aren't updating on the EtherNet/IP I/O Mapping screen for the E1210 suggests a communication issue between the device and Codesys, and you seem to be onto something with your "32 bit run/idle header" suspicion. This could well be a protocol-specific parsing issue where the anticipated data format doesn't match the incoming data. While I don't think your skepticism is baseless, it might be worth checking if there's a firmware update available for your E1210 that could potentially address this discrepancy. Meanwhile, I would also test with another E1211 to see if the issue persists. Sometimes, even minor differences between models can cause such communication quirks. Rest assured, you're moving in the right direction with your troubleshooting.
It sounds like you've done a thorough job of troubleshooting. Connection mapping issues like these are quite common and often not very straightforward to resolve. Your hypothesis about the "32 bit run/idle header" could very well be valid, especially if Codesys is expecting this in the message and not receiving it. But another area you might want to look into is the EtherNet/IP scanner settings in Codesys. The EDS file should ensure the input/output data is correctly interfaced, but if the scanner settings are improperly configured, this might lead to inconsistent data reflection between the device and the I/O Mapping screen. Debugging EtherNet/IP communication issues can also be done by checking the connection status/quality. Ultimately, if everything fails, try reaching out to Moxa's support team for further help.
It indeed does sound like a complex situation you are dealing with. Your reasoning about Codesys possibly expecting a 32-bit run/idle header seems plausible at first glance, however, I believe it's worth going deeper into the EDS file. How about checking the consistency of the EDS file with the actual device features especially with regards to the structure of input data? This inconsistency might be leading to incorrect interpretation of data by Codesys. You could also examine the Moxa DIO device's settings to ensure that they match the parameters and the Real time transfer format that EZ-EDS has specified. If these actions don't yield results, you may need to contact Moxa's support team for further assistance. It's probable that they may have encountered and resolved similar situations.
It sounds like you're really diving deep into the integration! Your analysis regarding the possibility of Codesys misinterpreting the data is definitely worth considering, especially since EtherNet/IP can be a bit finicky with data formats. One approach you might try is double-checking the PDO mapping configuration in Codesys for the E1210 device—sometimes the parameters can be set up incorrectly, leading to missed updates. Additionally, it might be helpful to look at the timing of your messages; if there are any delays or mismatches, it could affect how the DI values are perceived by Codesys. Lastly, consider reaching out to Moxa's support; they might have encountered similar issues with other users and could offer insights specific to your EDS file or setup. Keep us posted on your progress!
✅ 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: 1. Question: Why are the DI values not updating on the EtherNet/IP I/O Mapping screen for the Moxa ioLogik E1210 device in Codesys? Answer: The issue might be related to the format of the message being sent by Codesys. Check if the "32 bit run/idle header" is expected by Codesys, despite the configuration in EZ-EDS. This could impact how Codesys interprets the data received.
Answer: Answer: Make sure that the devices are properly configured and that the communication protocols match between Codesys and the Moxa devices. Additionally, verify that the EDS file provided by Moxa is correctly implemented in the Codesys setup.
Answer: Answer: Verify the network settings, communication setup, and data format compatibility between Codesys and the Moxa devices. Consider checking for any errors in the configuration or potential mismatches in the data transmission formats.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.