Hello everyone, I am seeking guidance on extracting data from equipment with RS-232 communication to a 1756-L73 ControlLogix 5570 Controller. I am exploring the use of an RS232 to POE Ethernet adapter from Waveshare for this purpose. The specific equipment I am working with is an ADR-50D Universal Closure Monitor, commonly referred to as dud detectors in the canning industry. This equipment utilizes simplex communication, where it only transmits data without receiving any. While reviewing the communication setup outlined in the equipment manual (see IMG 1), it appears that a non-standard protocol is being used. Will this require formatting adjustments on the receiving end? I have also included a screenshot of the web configuration page for the converter I am using (see IMG 2). Here, the serial settings can be configured to match the equipment and set up the IP address. I am unsure about the appropriate selection in the Work Mode dropdown (highlighted in blue in IMG 2), which includes options like TCP Server, TCP Client, UDP, and UDP Group. I am uncertain which option is suitable for my setup and whether this converter is compatible with my objectives. Is it possible to retrieve the serial information to my controller with the converter's known IP address and the expected data packet format? I am seeking confirmation if I am on the right track or if an alternative approach should be considered. Please let me know if further clarification or additional details are needed. Thank you for your assistance in advance!
It seems like a common occurrence for overseas developers to include a misspelled word in every interaction. This device appears to be a serial server that requires a software component on a computer to access. TacticalSoftware offers a solution that I personally utilize, but there are other options available as well. To integrate a PLC with this device, a custom Socket message may be necessary.
I have been relying on ProSoft devices for a long time, but I have not had the chance to try out the EtherNet/IP to ASCII gateway from ProSoft Technology, Inc. This communication gateway enables fast and efficient data exchange between EtherNet/IP-enabled PACs and ASCII devices like weigh scales and barcode readers. The EtherNet/IP protocol driver supports explicit messaging, while the gateway can be configured as both a client and a server. This device is compatible with ControlLogix processors and ensures seamless integration for your industrial automation needs. -Alan
Discover the RTA Ascii gateways460ETC - a straightforward method for linking ASCII devices with an Allen Bradley PLC. Easily connect your ASCII devices directly to the data table of your Allen-Bradley PLC with this innovative solution. Visit rtautomation.com to learn more.
Increase your search engine rankings with RTA gateway devices! Give a thumbs up for RTA gateways to enhance your network connectivity.
Opt for a different gateway instead of the waveshare device to simplify the process. The waveshare device only supports TCP/IP or ModbusTCP protocols, requiring socket programming in the Logix or downloading AOIs for programming. Consider using a "Serial to EtherNet/IP" gateway for a more efficient solution.
Hey there, your project seems quite in-depth, but you've approached it methodically which is good to see. To establish data retrieval from the ADR-50D, your choice of RS232 to Ethernet converter seems appropriate. When it comes to the non-standard communication protocol, some adjustments may indeed be necessary. However, without knowing the specifics of the format, it's hard to say definitively. Regarding the Work Mode of your converter, TCP Server looks like the most likely option given you are setting up for simplex and not duplex communication. The server option would wait for the 'dud detector' to establish the connection before transmitting data. And yes, typically, with the IP address of your converter, routing data to your controller should be possible. Just ensure the specific data format expected by the controller matches what's originating from your device. Hope this provides you with some direction - keep us posted!
Hi there! From your description, it sounds like you're pretty familiar with the setup. My primary advice concerning the RS232 to Ethernet adapter would be to check if the signal levels are compatible with your ADR-50D closure monitor. As for the non-standard protocol issue, unfortunately, there could be a need to modify the data at the receiving end or develop some code/script that will interpret the data correctly. Regarding the Work Mode, typically speaking, if your controller is intended to initiate the connection, TCP Client would be appropriate. Conversely, if the controller is waiting for the device to make the connection, TCP Server might be best. Always refer to your specific controller and device documentation to be safe. The goal is definitely to retrieve the serial information with the converter's IP. Ethernet to serial converters are designed to make this possible, so you're heading in the right direction. If any compatibility issues arise, it might be worth exploring other converters. Hope this helps, and best of luck with your project!
✅ 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: - The equipment manual indicates the use of a potentially non-standard protocol. Adjustments may be necessary on the receiving end to interpret and process the data correctly.
Answer: - The options provided in the Work Mode dropdown menu, such as TCP Server, TCP Client, UDP, and UDP Group, need to be understood to determine the suitable choice for the RS-232 communication setup.
Answer: - Confirming if the chosen converter and setup will allow for the transfer of serial information to the controller or if an alternative approach may be more appropriate is crucial for successful data extraction.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.