Hello everyone, I am currently facing a challenge while integrating an RFID reader into our operational workflow. Our system is equipped with a bus capable of supporting 2 RFID read/write heads, and it has Ethernet connectivity. Each station is equipped with one RFID read/write head. The issue arises when attempting to add them to the IO tree. The RFID bus serves as the link to the switch in the control panel, which is connected to our local network. Integrating the bus into the IO tree of the first processor was successful, allowing for seamless communication and data transfer with the head. However, when trying to add the bus to the second processor's IO tree, I encountered error code 16#031b: Rack Connection Refused. Given that each head has its own channel and associated tags in the EDS file, I assumed that each press could utilize a channel. Could this assumption be incorrect? Has anyone else faced a similar issue before? I would greatly appreciate any assistance or guidance on this matter. Thank you!
In most cases, a CIP node can only be controlled by one processor at a time. While you can establish connections with multiple processors, only one can actively write data while the others can only receive data. To enable bi-directional communication between processors, messaging between the two is necessary.
Hey there! It sounds like you're really close to getting everything set up, but error code 16#031b can be tricky. One possibility is that the second processor might not be recognizing the bus due to a configuration issue or an incorrect EDS file setup. Make sure that the parameters for each RFID reader are defined properly in both processor's settings and that there’s no overlap in the network assignments. It might also help to verify if the Ethernet IP settings for the second processor are correctly configured or if there are any physical issues with the cabling or connections. If you've gone through all that and still face the error, checking the documentation for any specific bus limitations or reaching out to the manufacturer for insights could be worthwhile as well. Good luck!
It sounds like you're encountering a pretty common issue with networked devices in multi-processor setups! The "Rack Connection Refused" error often indicates a problem with how the bus is configured or recognized by the second processor. Since you've successfully integrated it with the first, double-check that the second processor’s settings are aligned with the bus configuration and that it's pointing to the correct Ethernet settings. Also, make sure the bus is enabled for multiple connections, as some systems have limitations on how many can connect simultaneously. It could be worth reviewing the EDS file to ensure each head is defined properly and no address conflicts exist. Have you tried rebooting the entire system after changes? Sometimes a fresh restart can clear lingering communication issues. Hope you get it sorted out!
✅ 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: - Error code 16031b: Rack Connection Refused in Studio 5000 typically indicates a problem with adding a device, such as an RFID bus, to the IO tree of a processor. It may suggest issues related to network connectivity or configuration.
Answer: - To troubleshoot error code 16031b when adding an RFID bus to the IO tree of a processor, you can check the network connections, verify the configuration settings, ensure proper channel allocation for each RFID head, and review any relevant EDS files for compatibility.
Answer: - Yes, to ensure seamless communication and data transfer, it is recommended to assign a separate channel for each RFID head when integrating them into the IO tree of processors. This helps avoid conflicts and ensures proper functionality.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.