We have been having ongoing issues with the anybus communicator. I programmed the unit which is communicating with 8 different devices on the RS485 network. Data occasionally becomes transposed with other data and/or there are failures in the response. I believe the root cause is that the anybus gateway module is interrupting responses from other devices with the next request. When this occurs a response to a query may end up in the wrong response registers.
I was hoping that cyclical communication would mean that each request is made one after the other only after a valid and complete response from the slave device. I initially had programmed the device with default times and slower baud rate. This is when I discovered the problem. Despite my effort to increase transactions per second and analyzing responses and setting times the issue seems to be persistent.
By speeding up comms at least the issue of transposed data is resolved with the next transaction of that type. I’ve also toggled the “Freeze” option for data which is corrupt so that it doesn’t wipe the registers of interrupted responses. This has helped slightly.
Here is a screen capture of an event. I’ve also attached the log for this particular event and the running configuration.
ATT00001.htm (869 Bytes)
ATT00002.htm (2.55 KB)
cp3-abc1-running.cfg (16 KB)
ATT00003.htm (230 Bytes)
Log.txt (27.8 KB)
ATT00004.htm (189 Bytes)