How do I run Application Layer tests wirelessly via an AP? (HTS 4.0)

Please update your HTS (HART Test System) if the version of Kit-192 on it is older than v4.0. The procedure on this page is not applicable to older systems.

Application Layer tests are run wirelessly only on WirelessHART devices. If your device is not a WirelessHART device, do not try to run these tests wirelessly. Please note that in addition to passing the Application Layer tests when run wirelessly, WirelessHART devices must also pass the Application Layer tests run via FSK.

Follow the procedure outlined below to run the Application Layer tests wirelessly via an Access Point (AP).

1. Device Provisioning

To set up your HTS to run the Application Layer tests wirelessly via an AP, first provision your WirelessHART device with the following values using the provision tool installed on your HTS:

Network ID : 8765

Join Key : 00008765 00000000 00000000 00000000

Long Tag : <irrelevant to tests run via the AP - may be left blank or set to any ASCII value of your choice>

Polling Address : <irrelevant to wireless tests - may be left as is or set to any value between 0-10>

The Network ID and Join Key to be entered are hexadecimal values (e.g., the above Network ID value is typed for Network ID 0x8765 but the preceding '0x' must not be typed).

Power cycle the device after provisioning it. Please make sure that only one WirelessHART device has been provisioned with the above values. If other devices have the same Network ID and Join Key values, they must be kept powered off while tests are run on one device.

2. Component Connections

Connect one AP to one of the USB ports of the HTS.

3. Device Join and Test Setup

Wireless Application Layer tests to be run via the AP use the HART-IP Server (hipserver) and the Server Application (hipnmgw), both of which are installed on the HTS. Before starting any Application Layer test to be run via the AP, whether invoking it directly by typing the test name on the terminal or via hartmenu, make sure that hipserver and hipnmgw have started and the device has joined the network as described below.

The 'GettingStarted.txt' file on the Desktop of the HTS provides guidance about how to keep the test logs organized by running them from appropriate directories.

To run an Application Layer test via the AP, use the mouse to open the directory/folder where you wish to collect your test logs. Then, right-click on a blank spot in the window of the directory just opened and select "Open Terminal Here" from the displayed options. Once your current working directory in the Linux terminal is where you wish to keep your wireless Application Layer test logs, type runnmgw. This will launch a separate terminal and start hipserver+hipnmgw in it. Several network configuration steps will follow and the corresponding messages will be displayed in the terminal. Then the Network Manager (NM) will wait for the device to join the network. No user action is required during this time.

If the AP is connected to the HTS, the device is provisioned with the values given above and powered up, it should join the WirelessHART network of the NM in the HTS without user intervention. Once the device joins and is successfully configured by the NM, the following will be printed on the terminal:

Hello from hipnmgw!
Connected to: hipnmgw

4. Test Execution

Once the Hello message from the hipnmgw is seen, wireless Application Layer tests may be run individually (by typing CALWxxx or UALWxxx) or via the batch scripts (runcalw or runualw) which are already installed on the HTS. The test name may be typed directly at the terminal shell prompt or may be selected via hartmenu. 

Once the device has joined the network and the hipnmgw window is up and running, individual tests may be run one after the other directly from the terminal or via hartmenu without interfering with the hipnmgw window. As long as the device remains connected to the network and no errors are seen in the hipnmgw window, runnmgw must not be started again in between tests.

If the hipnmgw window is not seen, make sure that it is not hidden behind another window. Errors encountered by hipnmgw, if any, are printed in the 'hipnmgw_log.txt' file which is generated in the directory from where runnmgw is invoked. If hipnmgw is no longer running (check by typing showhipapp in the terminal), sometimes, repeating steps 2-4 (after re-inserting the USB cable of the AP into the HTS) can solve the problem.

The hipnmgw window displays status information whenever any commands are sent/received by hipnmgw to/from the hipserver or the device. Please remember that the hipserver+hipnmgw window stays up till it is terminated by typing a <Ctrl-C> in it, or some error occurs. To close the hipnmgw window, always press <Ctrl-C> in it, do not click on the X on the window bar.

Test logs are separate from the 'hipnmgw_log.txt' and are named for the respective test, e.g. 'calw000.qa.log' for CALW000 and 'ualw007.qa.log' for UALW007.