There could be several reasons for .OUT file not being created by the HSniffer. First, make sure that the two RS-232 HART modems for the HART Master and HSniffer are connected snugly on their designated serial ports and there are no loose connections between the modems and the DUT. Then perform the following steps to help eliminate possible user oversights and pinpoint the cause of the problem -


Open a terminal on the HART Test System and start a DLL test (e.g., type "DLL005" without quotes on the command line and press <Enter> to run this short DLL test). Then take the appropriate action as stated below based on the behavior you see in the following possible scenarios:


1. DLL Test Messages seen on the terminal

If, a few seconds after invoking the DLL test, the request and response bytes between the DLL test commands and the DUT are seen on the terminal from which the DLL test was invoked, it means the test is running. At this time, if nothing is seen in the HSniffer terminal window automatically opened by the DLL test, no .OUT file will be created. Verify that both modems are functioning correctly by swapping them, i.e., connect the modem from serial port 0 to serial port 1 and vice versa. Then run DLL005 again as specified above. 

  • If the request and response bytes between the test and the DUT are seen on the DLL test terminal, but nothing is seen again in the HSniffer window opened by the DLL test, no .OUT file will be created. In this case, the serial port designated for the HSniffer is most likely defective. Please open a Support Ticket (select Product Support, HART Test System) for further assistance. Include the Serial Number or Service Tag number of your HART Test System in your ticket for faster resolution. You may be entitled to an RMA if the Test System is enrolled in the Product Service Program.
  • If the request and response bytes between the test and the DUT are not seen on the DLL test terminal, the test is not running, so no .OUT file will be created by HSniffer. In this case, the RS-232 modem currently connected to the HART Master serial port is most likely defective (or loose). The modem functionality can be verified by sending single commands to the device and seeing if the device responds instead of running the whole test.


2. DLL Test Messages not seen on the terminal

If, a few seconds after invoking the DLL test, the request and response bytes between the DLL test commands and the DUT are not seen on the terminal from which the DLL test was invoked, it indicates that the test is not running. No .OUT file will be created by HSniffer in this situation. Verify that both modems are functioning correctly by swapping them, i.e., connect the modem from serial port 0 to serial port 1 and vice versa. Then run DLL005 again as specified above.

  • If the request and response bytes between the test and the DUT are seen on the DLL test terminal now, but nothing is seen in the HSniffer window opened by the DLL test, no .OUT file will be created. In this case, the RS-232 modem currently connected to the HSniffer serial port is most likely defective. The modem functionality can be verified by sending single commands to the device instead of running the whole test and seeing if the device responds .
  • If the request and response bytes between the test and the DUT are still not seen on the DLL test terminal, the test is not running, so no .OUT file will be created by HSniffer. In this case, the device is most probably not responding to the short frame Command 0 that identifies the device before sending any test commands. If the DUT has passed the physical layer tests, check the device response by sending single commands to the device instead of running the whole test.


Please note that only one instance of the HART Master can be running on the HART Test System at a time.