Copy the attached zip file to the Desktop of the HART Test System (HTS) and unzip it. Read the readme file in the sample_htest_script_3_8 directory for information about the sample script (sample_htest_script.c) and how to execute it.
If you have any specific test needs, the sample_htest_script.c can be copied and renamed to something else (e.g., mytest1.c). Then, on the lines of the functions used in the sample_htest_script.c, other commands can be built and sent to the device. The usage and syntax of the function calls in sample_htest_script.c can be used as guidance to write your own test scripts.
Other htest API functions can also be also used, as appropriate, for your testing needs. The HTEST User Manual for Release 3.8 describes all the available API calls.
If you have two RS232 modems, using the HSniffer can help verify compliance. To do that, perform the following steps:
* Open a terminal (Ctrl-t) and cd into the directory where your test script (e.g., mytest1.c) resides.
* Type "hsniffer -m -o mytest1.OUT" (without the quotes).
This will launch a separate hsniffer window. Now, execute your test script (mytest1.c). HSniffer will record all the data in mytest1.OUT when mytest1.c is executed.
When mytest1.c finishes running, close the hsniffer window by pressing Ctrl-c in it.
Then, type the following commands on the terminal:
conv mytest1.OUT > mytest1.bm.txt
conv -t -d -f mytest1.OUT > mytest1.tdf.txt
This converts mytest1 .OUT file into two human readable text files that can help you analyze and debug.
If your test script is for a support ticket that you opened, make sure you zip up the whole directory (including your sample script, the .OUT file and all .log and .txt files) and attach the zip file to your ticket.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article