Some end users have reported the following scenario: 

They invoke a Universal or Common Practice test case (ex: UAL000) and the test case reports 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 hipserver and connected app would also terminate if a device is not connected to the HTS (HART Test System). An Application Layer test cannot run unless the hipserver and app are running.

The two methods to fix this situation are described below. First, make sure that you have connected a registered RS-232 HART modem between the HTS serial port designated for the HART Master and your device. Then follow these steps -

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 HTS.
  2. After the system has rebooted and you have logged back in, open a Linux terminal.
  3. Rerun the test case.

If this does not fix the problem, make sure that you are able to communicate with your device by sending a single HART command. If the device cannot be identified, nothing else will work. Make sure you quit from htest after sending single HART commands before you run any other tests.

Please make sure that only one instance of the HART Master is running on the HTS at a time. If a test is hung, abort it before trying to send a single HART command.