Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

 Products: ACR9000, 9030,9040,9600,9630,9640, Aries Controller (AR-xxCE)

If ACR-View6 becomes unresponsive or freezes, you can usually recover by killing the ComACRserver.

The ComACRserver manages communications between ACR-View and the controller. If there is a problem with the connection the ComACRserver will throw a Watchdog Timeout error in ACR-View and stop polling the controller for information. When the connection is re-establish (for example, power cycle of the controller) the ComACRserver will alert ACR-View with a Watchdog Timeout Reconnect Event, allowing ACR-View to continue polling.

It is possible for a connection to get lost without a Watchdog tripping. This can result in ACR-View getting very slow trying to handle ComACRserver background error messages. When this happens it becomes difficult or impossible do anything with ACR-View. Rather than killing ACR-View thru Windows task manager and possibly losing unsaved data in your project, you can simply stop the ComACRserver which will free up ACR-View. You will need to Save the project, then Open the project again to launch the ComACRserver and enable communication with the controller.

When you open an ACR-View project you should see a ComACRserver icon in the Windows system tray. If its not visible in Windows7 you will need to change the setting as shown below.

Clicking on the ComACRserver icon will allow you to Kill the server and stop communications. The priority should not be changed.

 

jw 13-feb-2013

  • No labels