Struggling with setting up generic ethernet devices for your PLC like the 1756-L55 with a 1756-ENBT/A ethernet card? Despite numerous resources available, you may still encounter issues. A test PLC running revision 13.31 is in use, along with a static IP of 192.168.1.243. Connected to a Stratix 2000 8 port switch, with a PC having a static IP of 192.168.1.253. Additionally, a Cognex camera with firmware 6.02.01 at IP address 192.168.1.25 is involved. However, encountering "connecting" and "faulted" statuses repeatedly after adding the camera to the RSlogix controller tree can be frustrating. In Wireshark, seeing CIP I/O packets from the camera but with a confusing destination address like 239.192.4.16 can be perplexing. Have you tried integrating an AL1326 IO link Master from IFM as a generic ethernet device with similar outcomes? Unsure if you're missing a key step or if revisions need upgrading for everything to function smoothly? Your diligence in troubleshooting is appreciated.
During that period, unicast was not an option for the standard Ethernet device, making 239.192.4.16 a multicast address. In my experience with several Cognex cameras, Ethernet I/P is typically disabled by default and must be manually enabled using their software. Turn on Ethernet I/P for communication with Cognex cameras on your network.
During that time, selecting unicast for the generic Ethernet device was not an option, making your 239.192.4.16 a multicast address. In my experience with Cognex cameras, Ethernet I/P is typically disabled by default, requiring manual activation in their software. I have configured the "industrial Ethernet protocols" in the sensor network settings to Ethernet/IP, which should resolve any issues. Additionally, I observed that I can retrieve module information from the camera in the module properties dialog box, including vendor code, product code, and serial number. However, the IO tags are not functioning correctly. This issue resembles the AL1326, where I could successfully retrieve the vendor code using explicit messages with a "get single Attribute" service code, but the IO tags were not operational.
Which Cognex model is best for my needs?
Robertmee inquired about the specific model of Cognex machine. The machine in question is equipped with 7600 firmware version 6.02.01.
Instance 13 has been configured with 500 Bytes, as per the guidelines provided in the Cognex Manual. However, it is important to note that if you are using the EDS generated file, the limit is set at 496 bytes. To resolve this issue, consider updating the firmware on your PLC to version 15 or higher. This will allow you to access an Add-On Profile (AOP) that can simplify operation. For more information on integrating Cognex with RSLogix, please refer to the following link: https://www.cognex.com/support/downloads/ns/1/11/91/Integration-with-RSLogix-v1.pdf.
It sounds like you've done a lot of troubleshooting already! The "connecting" and "faulted" statuses can be frustrating. Have you checked the compatibility of the Cognex camera with the firmware version of your PLC? Sometimes, even small version mismatches can cause communication issues. Also, ensuring that your subnet masks are correctly set can help eliminate connectivity problems. The CIP I/O packets may be a multicast address, which can be normal for discovery purposes but can confuse the devices if not managed properly. It might be worth looking into any required configurations for the AL1326 IO Link Master as well, since dependencies may differ across devices. Keep at it; you're on the right track!
It sounds like you've done a thorough job setting up your network, but those connection issues can definitely be a headache! One thing to consider is checking your multicast settings—those CIP I/O packets with a destination like 239.192.4.16 suggest there might be some multicast traffic getting in the way, as some devices might not play nice with it depending on their settings. Also, have you verified that the camera is configured correctly in RSLogix? Sometimes, parameters like the IO connection size need to match the actual device capabilities. Updating the firmware on your devices could be a good idea, too, as compatibility issues can often be resolved with the latest revisions. Good luck, and keep us posted on your progress!
It sounds like you’re on the right track with your setup, but those "connecting" and "faulted" statuses can be a real headache! I’d suggest double-checking the subnet configurations and making sure all devices are on the same subnet, as mismatched subnet masks can cause communication issues. Also, the CIP I/O packets you're seeing might indicate that the devices are trying to communicate but are struggling due to address mismatches or routing issues. You might also want to check for any firmware updates not just on the camera but on the PLC and switch as well; sometimes, even minor version updates can improve compatibility. If you're still having trouble after these checks, consider segmenting the network temporarily to narrow down where the fault might be coming from. Good luck!
It sounds like you've done a solid job setting everything up, but those “connecting” and “faulted” statuses can really throw a wrench in the works! The strange destination address you’re seeing in Wireshark suggests that the camera might be broadcasting its packets, which could lead to issues with how the PLC recognizes it. Have you tried making sure that the network configuration on the camera aligns with the PLC, especially in terms of subnet masks? Also, it might be worth checking if the firmware versions of all devices are compatible; sometimes a small revision upgrade can resolve these pesky connection issues. If you haven't already, try isolating the devices; like connecting the camera directly to the PC to see if it communicates properly, which can help narrow down where the problem lies. Keep at it—you're definitely on the right track!
It sounds like you're dealing with a real headache there! Have you double-checked that all your devices are on the same subnet and that there's no IP address conflict? The 239.192.4.16 address you’re seeing in Wireshark is a multicast address often used for IO communication, which can get tricky if devices aren’t configured correctly to handle it. Also, ensure that your RSLogix is set to the right communication settings for all devices; sometimes a simple oversight in the configuration can throw everything off. If you haven't, updating the firmware on your devices can sometimes resolve compatibility issues as well. Good luck, and I hope you get everything running smoothly soon!
âś… 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: - This issue could be related to the configuration settings or network setup. Make sure the IP addresses are correctly assigned and check the communication parameters between the camera and the PLC.
Answer: - The destination address 239.192.4.16 indicates a multicast address. Ensure that your network configuration supports multicast traffic and that the devices are correctly configured to send and receive multicast packets.
Answer: - Integrating the AL1326 IO link Master may require specific configuration steps. Check the compatibility of the device with your PLC and ensure that the settings are correctly configured for seamless communication.
Answer: - It's possible that missing a crucial configuration step or using outdated firmware revisions could lead to communication issues. Verify the setup steps, firmware compatibility, and network settings to ensure proper functioning of the devices.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.