Hello, I am facing challenges in getting an ArmorBlock, 1732E-16CFGM12QCR, to respond to Ethernet/IP (EIP) outputs with my Panasonic FP0H-C32ET PLC. I have correctly registered the EDS provided by Rockwell Automation for this module but have been unsuccessful in establishing a connection, particularly focusing on the Open, Exclusive Owner connection type. Despite trying various connection configurations and testing with and without the Power Status, I have only been able to successfully operate the inputs in the DataView while online with the PLC. The module is configured as Open, Exclusive Owner, which results in inputs and outputs being interpreted as two words instead of one in the EDS. In the DataView, the input shows as ON but attempting to activate the output does not produce the desired results. I have connected a 0.5VA LED light as a load device as per the module instructions, but neither the module LED nor the load LED illuminate when the output bit is triggered in the user program. This issue persists even when testing with other outputs on the module. I have verified the wiring and followed the module instructions accurately, but the expected response is not occurring. I am unsure of what the missing piece might be.
Issue Resolved! Upon investigation, I found that there should be TWO EMPTY WORDS between the input and output words in PLC addresses. The mechanism by which the PLC recognizes these words remains a mystery to me. While there are various methods to rectify this, it seems that the EDS file should have addressed this. Opting for Logix Exclusive Owner over Open Exclusive Owner is one solution. By selecting Logix, three input words are required instead of just one, enabling the auto addresser to function properly. Alternatively, choosing Open and deactivating the auto addresser while maintaining two blank words between the PLC addresses is another option. Personally, I have set mine to Logix to automatically include the necessary "dud" words, whilst deactivating the auto addresser allows me to select WR memory areas instead of LD memory areas. This configuration allows me to configure the DUT as an Array of BOOL with 16 BOOLS, facilitating individual mapping to inputs and outputs without the need for BOOLS_TO_WORD and WORD_TO_BOOLS conversions. Best regards, Nevin
Hey there, it indeed sounds like you're in a tricky spot. You've mentioned extensively about the connection configurations, but have you given thought to the EIP protocol itself? Panasonic PLCs often do not work flawlessly with Ethernet/IP - despite having the correct EDS files. Secondly, it's also worth checking the firmware version of your ArmorBlock. An outdated version can occasionally halt proper communication. I'd recommend seeking firmware update options if you haven't done so yet. Lastly, be sure that your PLC programs are accommodating outputs as two distinct words in alignment with the Exclusive Owner configuration. Hope this leads you to a solution. Good luck!
You've provided a thorough breakdown of your process, and it's clear that you've been meticulous with your configurations. With issues like this, it's often something minute that can be easily overlooked. One aspect I think might be worth examining would be the setup of the consumption and production instances in your Panda-Net communication settings. It seems like the issue might lie in the I/O sizes and the data mapping, considering the inputs are working but the outputs aren't. Also, double-check your RPI settings for both input and output and make sure that it's set correctly to communicate with the PLC. Keep in mind to apply your changes to both the module properties and also the I/O connection in RSLogix. If everything looks good, it might be a good idea to try a different module or PLC to rule out hardware issues. Good luck with your troubleshooting!
It sounds like you've done a thorough job of troubleshooting so far. In my experience, these kind of issues usually come down to one of two things: hardware faults or addressing concerns. Have you tried checking if your PLC is compatible with this Rockwell Automation module? Just cross verify the compatibility once. Furthermore, try swapping out the module with a similar one, if available, to see if it's a hardware issue. Also, ensure that the I/O messaging in your PLC program lines up with the exact I/O of the 1732E module you are using. If the addresses are offset or mismatched, you might not see your outputs react as expected. I hope this is helpful!
It sounds like you've done a thorough job troubleshooting so far. Given the problems you're describing, my immediate suspicion is that there may be an issue with the Node Address configuration on your 1732E-16CFGM12QCR. Keep in mind that even if the EDS file registered successfully, mismatched addresses can prevent successful communication over Ethernet/IP. Double check that the device's Node Address matches what you've got configured in your PLC. Additionally, confirm that your network infrastructure (switches, cables, etc.) is fully operational. Finally, you mentioned that you're using an Open, Exclusive Owner connection. This setting may not be appropriate if other devices also need to communicate with your ArmorBlock. Perhaps try a Listen Only or Input Only connection to see if that helps.
✅ 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: To troubleshoot connectivity issues, ensure that the EDS provided by Rockwell Automation is correctly registered, try different connection configurations, verify the module is configured correctly (Open, Exclusive Owner), and check the wiring as per the module instructions.
Answer: If the inputs and outputs are interpreted as two words in the EDS, it may be due to the configuration settings or communication setup. Check the configuration settings to ensure they align with the expected behavior.
Answer: The LED light not illuminating could be due to issues with the module configuration, wiring, or the load device itself. Check the wiring connections, verify the module configuration, and ensure the load device is functional.
Answer: If the expected response is not occurring, despite proper wiring and following instructions, consider checking the communication settings
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.