Some end users have reported the following scenario: They will invoke a Universal or Common Practice test case (ex: UAL000) and the test case will report a start time along with the connection but then seems to hang up. It may take several minutes before the user sees a failure point message indicating that the test system cannot connect to the device.

When an Application Layer test case is executed, the hipserver and connection app is launched before the test case starts running. When the reported scenario occurs, it is because these two programs (hipserver and connection app) have unexpectedly terminated or closed. This is rare but when it occurs, it is due to the server window being closed by the user or a zombie process running in the background that prevents the server and communication app from running.

The two methods to fix this situation are described below.

Method 1:

  1. Open a Linux terminal.
  2. Type the following command: terminateserver
  3. Rerun the test case.

If this does not fix the problem, continue to Method 2. 

Method 2:

  1. Reboot the HART Test System.
  2. After the system has rebooted and you have logged back in, open a Linux terminal.
  3. Rerun the test case.