I am looking to switch the connection of my device from a UR 10 robot with a UR Cap to an Allen Bradley CompactLogix 5069-L306ER PLC in order to use it with multiple robots. The device communicates via Ethernet TCP/IP and I have its IP address and native protocol details. I am new to device communication and have been attempting to send specific commands like "Get_State" (0x00 02) and "Register_Client" (0x00 03) using the MSG instruction with CIP read and CIP generic, but encountering difficulties. Any assistance on how to properly set up the communication between the device and the PLC would be greatly appreciated.
Utilize the CIP Card to convert HEX into Decimal before sending the equivalent decimal values. Analyze the CIP Command outputs using Wireshark on TCP/IP, adjusting settings until the correct messages are received. Compare data between the Robot and PC as well as the Robot and PLC for reference. While it may take some time to decipher the commands, setting up Wireshark on a spare PC with a network HUB (not a Switch) between the PLC and Robot can help capture data effectively. Ensure the PLC, Robot, and PC are on the same network range (e.g. 192.168.1.xxx with mask 255.255.255.000) for successful data capture.
Mad4x4 suggested using the CIP Card for converting HEX to Decimal and sending the decimal equivalent. By utilizing Wireshark to analyze the CIP Command outputs on TCP/IP, one can modify them as needed to receive the correct messages. Cross-referencing between the Robot, PC, and PLC is essential in this process. While it may require some time to decipher the commands, setting up Wireshark on a spare PC with a network HUB (not a Switch) between the PLC and Robot allows for data capture. It is crucial for the PLC, robot, and PC to be on the same network range (e.g., 192.168.1.xxx with a 255.255.255.000 mask). This approach proved successful for one user who appreciated the innovative idea and plans to utilize it for future debugging purposes.
Easily achievable! Learn how with this guide on Ethernet IP for collaborative robot support - 18712.
It sounds like an interesting project and I can understand the challenges you're facing as a newcomer to device communication. In the scenario with the CompactLogix 5069-L306ER PLC, it seems you're on the right track with using the MSG instruction. However, one thing you might be missing is setting up the network routing correctly. Your PLC needs to know the path to your device. This typically involves setting up your Ethernet port. I'd recommend looking into the network settings of your PLC and ensuring they match with your device's details. Once the correct routing path is set, your MSG commands should work correctly. For dealing with specific commands, you might want to consider creating your own function blocks for each command, as this would simplify the process of communicating with your device in the long run. Hope this leads you in the right direction!
It sounds like you're on the right track with using the MSG instruction for CIP. However, setting up the communication might take a bit of trial and error if you're new to this. Make sure that you're using the correct syntax for commands; sometimes a simple mistake can lead to connectivity issues. For the CompactLogix PLC, the Ethernet IP protocol would use the TCP/IP communication, so ensure that you've configured the ethernet port of your PLC correctly and that it matches the settings of your device. You may also want to check if there are any specific commands for Allen Bradley PLCs in your device's documentation. Lastly, the Rockwell Automation website has great resources and tutorials on setting up device communication that might also be of help.
I can understand that setting up a device-PLC communication can be quite challenging especially for beginners. The key to successful communication lies in proper configuration of the MSG instruction in CompactLogix. Ideally, for Ethernet/IP devices, you'd want to use the CIP Data Table Write or CIP Data Table Read. You just need to make sure that the Service Type matches the operation that you're trying to conduct. As for sending specific hex commands like "Get_State" or "Register_Client", these should be placed in the Message Data array and the array length would be adjusted accordingly. If the communication is still not working, you might want to check the network path in the instruction to see if it reflects the target device's setup. Lastly, don't forget to factor in the timing and triggering of these instructions because PLCs work based on scan cycles. I hope this helps to steer you in the right direction. Happy troubleshooting!
It sounds like you're diving into a complex but rewarding project! Since you're working with Ethernet TCP/IP and using Allen Bradley's MSG instruction, make sure you've configured your port settings correctly and are using the right connection type—CIP Ethernet, in your case. For the commands you're trying to send, double-check that your MSG instruction parameters match the expected format for the device’s protocol. It might also help to review any documentation you have for the device and compare it with sample code or examples in the CompactLogix manuals. If you haven’t already, testing with a simple, known command before moving to the "Get_State" and "Register_Client" can also help isolate any issues. Good luck, and don't hesitate to share what you've tried; the community can offer more specific guidance!
It sounds like you're navigating a complex setup, but it's definitely achievable! Since you're using the MSG instruction with CIP protocol, make sure that your packet structure aligns with what the device expects; sometimes those command bytes can be finicky. Double-check your MSG configuration to ensure you've set the correct service type for the CIP commands, and that you're targeting the right object and instance numbers specified in the device's protocol documentation. Also, try using a tool like Wireshark to capture the communication; it can provide great insight into what’s happening on the network and help you troubleshoot further. Don't hesitate to break down your process and share any error messages you're getting—sometimes the community can spot something that might have been overlooked!
✅ 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 establish the connection, ensure you have the IP address and native protocol details of the UR 10 robot. Use the MSG instruction with CIP read and CIP generic to send specific commands like "Get_State" and "Register_Client" from the PLC to the robot.
Answer: - Some common issues users face include difficulties in sending specific commands, such as "Get_State" and "Register_Client," using the MSG instruction with CIP read and CIP generic. Troubleshoot by checking the configuration settings, IP addresses, and ensuring proper communication protocols are followed.
Answer: - Ensure proper setup of the communication parameters, such as IP addresses and native protocols, for each robot. Use the appropriate instructions, like MSG with CIP read and CIP generic, to send commands effectively between the PLC and the robots. Regularly test and troubleshoot the communication setup to ensure smooth operation.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.