Please update your HTS (HART Test System) immediately if the version of Kit-192 on it is older than v3.6. The procedure described below 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.
For Test Systems that have Kit-193 v1.8, please follow the procedure outlined below to run Application Layer tests wirelessly via a Gateway (GW). Please update your Test System if you have an older version of Kit-193.
To set up your HTS to run the Application Layer tests wirelessly via a GW, connect an external commercial GW that supports WirelessHART to the Ethernet port of the HTS via an Ethernet router or hub. Commercial GWs are not supplied by FCG and all information about setup and configuration of the GW must be obtained from the vendor of the WirelessHART GW.
Provision your WirelessHART device with the same Network ID and Join Key as specified on the GW. The Network ID and Join Key values must match on the device and GW. They are irrelevant to the tests. Set the long tag of the device to 'HCF-DUT'. When the GW is running and the device is properly provisioned, configured and powered up, it should join the WirelessHART network of the GW without user intervention. Verify via the tools/methods supplied by the GW vendor that the device has joined the network.
Edit the 'gateway' file in user1's home directory and replace the placeholder values for the IP address and port number with the values required by, or configured for, the GW. If the 'gateway' file is missing for any reason, you can create it by typing mkgtwy on the command line and then edit the file to replace the placeholder values. If your GW has multiple port configurations, select the HART-IP UDP port number. The 'gateway' file (~user1/gateway) has the following line in it by default -
-a 255.255.255.255 -p 5094 -t on
If, for example, the IP address of the GW on your local network is 10.7.202.103 and the port number to use is 3456, modify the above line in the 'gateway' file so that it looks like this -
-a 10.7.202.103 -p 3456 -t on
The wireless Application Layer tests use the HART-IP Server (hipserver) and the Server Application (hipiosys), both of which are installed on the HTS. The best practice before starting any Application Layer test is to make sure that the hipserver and hipiosys start up and are able to detect your device. To do this, open a terminal and type runiosys. This will start hipserver+hipiosys and use the IP address in the gateway file mentioned above along with the other parameters to connect to the commercial GW. If hipiosys is able to detect the device, the following will be printed on the terminal:
hello from hipiosys! Connected to: hipiosys
Once you see the above, wireless application tests may be run from another terminal individually (by typing CALUxxx or UALUxxx) or via the batch scripts (runcaludp or runualudp) installed on the HTS. If the hello message from the hipiosys is not seen, please make sure that another copy of the hipserver is not forgotten/running in the background. Please double check that you have followed all the steps outlined above to get the device to join the WirelessHART network of the commercial GW.
Please remember that the hipserver+hipiosys window stays up till it is terminated with a <Ctrl-C> typed 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 hipiosys, if any, are printed in the 'hipiosys_log.txt' file which is generated in the directory from where runiosys is invoked.