lostcontrol
Lifetime Supporting Member
Is this possible?
Recently on a machine connected to an InTouch SCADA, we have been losing comms from the DASABTcp driver, & to a certain extent, does not recover very well.
I have tried disabling the IO Server to allow the port to timeout/disconnect etc, but when re-enabling the server does not recover, the same errors are still present.
The only fix that seems to work is cycling the PLC. For obvious reasons, this is not ideal
When I look at the Enet LED on the CPU, it is blinking intermittently, but not at the same rate when things have been functioning correctly.
So, a couple of questions I guess:
1. What could be causing this
2. Is there anything that I should be looking at in the PLC (Peripheral Servicing?)
3. is there any status words that if I connect via serial I can check if & when this happens again?
4. From 3, can I initiate an Ethernet port restart programatically?
It is possible that it is the CPU/Enet port is failing due to age, but surely this can be monitored?
Recently on a machine connected to an InTouch SCADA, we have been losing comms from the DASABTcp driver, & to a certain extent, does not recover very well.
I have tried disabling the IO Server to allow the port to timeout/disconnect etc, but when re-enabling the server does not recover, the same errors are still present.
The only fix that seems to work is cycling the PLC. For obvious reasons, this is not ideal
When I look at the Enet LED on the CPU, it is blinking intermittently, but not at the same rate when things have been functioning correctly.
So, a couple of questions I guess:
1. What could be causing this
2. Is there anything that I should be looking at in the PLC (Peripheral Servicing?)
3. is there any status words that if I connect via serial I can check if & when this happens again?
4. From 3, can I initiate an Ethernet port restart programatically?
It is possible that it is the CPU/Enet port is failing due to age, but surely this can be monitored?