Kepware setup on redundant Aspect+Connectivity Servers

We have redundant Aspect+connectivity servers and kepware is installed on both servers to communicate over Modbus TCP to PLCs. Initially everything looked good but after some time network started to slow down and then suddenly it hanged.

What would have caused the network to slow down and choke?

Is this the write setup to install kepware on both servers to have PLCs data available to Operators when primary server switches to secondary or is down?

Please suggest if there is some better way or guideline of doing so.

Thanks.

Comments (0) New comment

aneelbaig Rank: 2583

Asked 3 years ago

Answer this question Follow

Answers

Sorry. I have too little knowledge in active use of Kepware to be of any better help here.

The "network" is often incorrectly blaimed when there is a general problem; what makes you believe "network to slow down"?

If the network *really* slowed down the problem is not due to ABB, nor Kepware and you should contact the vendor of the network equipment to have the switches, cables, etc. investigated.

I would begin examining the output from the OPC DA Connector statistics operations to see if there is something abnormal with the OPC traffic in/out of the Kepware OPC servers. Google "abb aks afwapplogviewer advdsopcconnector statistics" etc for examples. You may have to tune the search a bit - I know I have submitted detailed examples in some past threads.

Have you checked if Kepware keep some logfile or diagnostic? Maybe it was the network - then you should redirect your concern to who installed the network and what equipment (hardware) is used.

Comments (0) New comment