P
As someone who has very little knowledge of the Modbus protocol you will have to bear with me on this one.
Does anyone know of any instances where a DCS would effectively turn off a port to a RTU but think it is still running? That is, all drives on the DCS are showing green and running, but in reality the RTU has lost all its TX and RX between itself and the DCS, and the drives have stopped.
We have changed all the hardware possible. RTU hardware and cabling, Modbus comms boards in the DCS (including the board carrier), we have even failed the processor over so that the back up becomes the primary, etc. The setup is pretty standard - DCS (Master) RTU (Slave/Master) Motor Manager (slave).
The DCS we are using is an ABB ADVANT. RTUs are Kingfisher PC-1 processor and MC-11 multi-communication module.
Any thoughts would be well received.
Does anyone know of any instances where a DCS would effectively turn off a port to a RTU but think it is still running? That is, all drives on the DCS are showing green and running, but in reality the RTU has lost all its TX and RX between itself and the DCS, and the drives have stopped.
We have changed all the hardware possible. RTU hardware and cabling, Modbus comms boards in the DCS (including the board carrier), we have even failed the processor over so that the back up becomes the primary, etc. The setup is pretty standard - DCS (Master) RTU (Slave/Master) Motor Manager (slave).
The DCS we are using is an ABB ADVANT. RTUs are Kingfisher PC-1 processor and MC-11 multi-communication module.
Any thoughts would be well received.
