Please update your Test System immediately if the version of Kit-192 on it is older than v3.6. 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.
The procedure described in this article is not for Test Systems that have Kit-193 v1.8. For those systems, please follow the procedure for running these tests via a Gateway.
For Test Systems that have Kit-193 v1.9, please follow the procedure outlined below to run the Application Layer tests wirelessly via an Access Point (AP).
To set up your HART Test System to run the Application Layer tests wirelessly via an AP, first provision your WirelessHART device with the following values:
Network ID : 0x8765
Join Key : 0x00008765 00000000 00000000 00000000
The long tag of the device is irrelevant to the Application Layer tests run via the AP. It can be left blank or set to any long tag value of your choice.
Wireless Application Layer tests use the HART-IP Server (hipserver) and the Server Application (hipnmgw), both of which are installed on the Test System. The best practice before starting any test, whether invoking it directly by typing the test name on the terminal or via hartmenu, is to make sure that hipserver+hipnmgw have started and the device has joined the network. To do this, open a terminal, navigate (cd) to the directory where you wish to collect your test logs and type runnmgw. This will launch a separate terminal and start hipserver+hipnmgw in it with appropriate parameters. 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.
If the AP is connected to the Test System, the device is provisioned with the values given above and powered up, it should join the WirelessHART network of the NM in the Test System 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
Once the above is seen, wireless Application Layer tests may be run from another terminal individually (by typing CALWxxx or UALWxxx) or via the batch scripts (runcalw or runualw) which are already installed on the Test System. As before, navigate to the directory where you wish to collect your test logs and type the test name directly or select it via hartmenu. Once the Hello message from the hipnmgw is seen, the above procedure must not be repeated in between tests, i.e., runnmgw must not be started again in between tests. Tests are to be invoked one after the other once the device has joined the network and the hipnmgw window is up and running. If the Hello message is not seen and/or the hipserver+hipnmgw window disappears, it is because some error occurred. Please open the log file 'hipnmgw_log.txt' which is generated in the directory from which runnmgw was invoked to see the cause of the error. If hipnmgw is no longer running (check by typing showhipapp), sometimes, reinserting the USB cable of the AP into the Test System, then restarting runnmgw can solve the problem.
Unlike the windows for other HART-IP Server applications, the window for hipnmgw prints 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 (do not click on the X on the window bar to close it), or some error occurs. If the 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. Test logs are separate from the 'hipnmgw_log.txt' and are named for the respective test, e.g. 'calu000.qa.log' for CALW000 and 'ualu007.qa.log' for UALW007.