Software shutdown caused by the COOPS 10060 error.

This knowledge article will help diagnose intermittent or complete software shutdowns that result in a COOPS 10060 error on 493 / 494 controllers running 793 system software.  Coops 10060 codes are a general communication failure error that could be caused by many things. The end result is a controller to PC connection that has been dropped because of a network failure or because the peer system (the PC) failed to respond. 


Here are some things to check:

 

  1. Make sure you are not connected to a corporate network that may be pushing down updates, running security scans, or other scheduled processes during the test.  This can cause too much memory utilization and a delay in the PC sending information to the controller leading to a timeout error.  Try disconnecting from your corporate network for a while to see if the COOPS errors stop.  If they do you will need to work with your I.T. Department to figure out what they are doing that is causing the COOPS errors before reconnecting.  

 

  1. Make sure you are using PCI slot installed network card provided by MTS with the PC and not the motherboard NIC, wireless, or USB dongle type adapters.  

 

  1. Remove any antivirus software that may be interfering with the communication.

 

  1. Check network card settings in case programs have been installed to run periodically that auto-detect network settings and reconfigure them to conform with security protocols.   Sometimes the network card settings may work but not be optimized and can lead to poor communication reliability.    In some cases even after the network settings have been corrected the program that was installed on the PC will automatically run on a schedule and reconfigure the network settings again causing the COOPs 10060 error to return even after the PC has been removed from a corporate network.  The program must be identified and removed.  In some cases MTS Field Service Engineers have had to reinstall Windows to fix the problem.  

 

For network card settings refer to:  Start > All Programs > MTS 793 Software > Service Tools > Troubleshooting Network Problems.  Pay close attention to the network card duplex and speed settings.   Unreliable network communication can result if these settings are not correct. 

 

Tip:  If you need to see an example of how to change the duplex and link speed you can go to link below. 

 

https://www.linksys.com/us/support-article?articleNum=132174

 

 

You can use the tables below to identify which to use.  You can identify your processor model by looking at the thumb tabs on the back of the module.

 

 

Figure – Location of Processor Model Number

 

 

 

 

Model Number

Duplex

Speed (Mbps)

498.93-1

Half

10

Table 1 – Very Old Processors

 

 

Model Number

Duplex

Speed (Mbps)

498.94-1

Half

100

498.96-1

Half

100

498.96-2

Half

100

498.96-3

Half

100

498.96-4

Half

100

Table 2 – Old Processors

 
 
 

 

Model Number

Duplex

Speed (Mbps)

494.96-1A

Auto Negotiate

Auto Negotiate

494.96-1B

Auto Negotiate

Auto Negotiate

494.96-1C

Auto Negotiate

Auto Negotiate

494.96-2A

Auto Negotiate

Auto Negotiate

494.96-2B

Auto Negotiate

Auto Negotiate

494.96-2C

Auto Negotiate

Auto Negotiate

494.96-3A

Auto Negotiate

Auto Negotiate

494.96-4A

Auto Negotiate

Auto Negotiate

498.96-5

Auto Negotiate

Auto Negotiate

498.96-5B

Auto Negotiate

Auto Negotiate

498.96-7

Auto Negotiate

Auto Negotiate

494.96-5B

Auto Negotiate

Auto Negotiate

498.96-5D

Auto Negotiate

Auto Negotiate

494.96-5E

Auto Negotiate

Auto Negotiate

494.96-5F

Auto Negotiate

Auto Negotiate

494.96-7

Auto Negotiate

Auto Negotiate

494.96-7B

Auto Negotiate

Auto Negotiate

494.96-7C

Auto Negotiate

Auto Negotiate

494.96-7D

Auto Negotiate

Auto Negotiate

494.96-8A

Auto Negotiate

Auto Negotiate

494.96-9A

Auto Negotiate

Auto Negotiate

Table 3 – Newer Processors

 

 

Note: If you are using a switch set the Link Speed and Duplex to Auto Negotiate.

Figure - Example of a Network switch

  

 

  1. Try a new Ethernet Cable.  If using a communication switch/hub bypass it by connecting the cable directly between the controller and PC.          With the exception of the TestStar IIS controller MTS controllers require crossover Ethernet cables.  

 

  1. Reinstall the network card driver.

 

  1. Check the controller power supply or processor.        If you can’t recover from the error and reestablish controller communication it is a sign of hardware failure like the power supply or controller processor.  


If none of the above suggestions result in a successful resolution of the COOPS 10060 error, you may have other hardware or software issues with the controller or the controller PC. Please contact MTS service to schedule a site visit from your assigned FSE to further diagnose root cause and resolve the communications issues.

 

 

R
Robert is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.