I have an application with 2 robots and several other devices using Modbus TCP/IP. I'm using Robot #1 as the Modbus Server. All devices need to be able to update a register in Robot #1 for handshaking purposes. The functionality I'm trying to implement is for all devices to look at that register, and if it a certain value, complete their current cycle then stop.If I set the address to a "Register Input" on Robot 1, Robot 1 can't update the value. However, if I set it to "Register Output", it will keep the value to the last value it knows on ALL devices. For example, if the value is 0 and another device sets it to 1, Robot 1 (the server) will immediately overwrite it to 0 again. In effect, preventing other devices from changing it. Maybe I've been lucky/lazy. But on other devices I've used in the past, if I set the address to output on both sides of the communication, it works as expected. I.E. either side can change the value and the last message is honored on both devices.Is there a way to make UR act as I expect, or do I have a misunderstanding of how Modbus works? Running the latest 5.9 on several UR5Es. Running Integration-Objects OPC->Modbus on my Windows PCs.