All WirelessHART devices must also pass wired HART tests, i.e., tests run via the maintenance port of the WirelessHART device. Before starting to run wireless tests, make sure that you have the latest released version of the HTS (HART Test System) and your device passes the following tests run via the maintenance port in this order:

  1. Physical Layer Tests
  2. Data Link Layer Tests (DLL)
  3. Application Layer Tests (UAL - Universal Commands)
  4. Application Layer Tests (CAL - Common Practice Commands)

After the above tests have passed [*], make sure that you have the latest version of the WirelessHART Test System. Then, do the following:

  1. Send Cmd 0 via the maintenance port using htest and check the response bytes to ensure that all values are set correctly for your specific device category.
  2. Provision your device to set up valid values for Network ID, Join Key, Long Tag and Polling Address. Some wireless tests do the necessary provisioning for the test environment, others require the device to be provisioned by the user before tests are run. But for default, always set some legal values for these parameters before starting any testing (the sample values in this article are legal).
  3. Run a TML Join Test to make sure that the device can join a WirelessHART network. This can be done by following the procedure outlined in this article and executing TML102A, which is a simple join test. After the test is complete, open the linux log ('tml102a_testlog.txt') generated on the HTS by the test and look for "Error" and "Non-Compliant". If those terms are found, address the cause of the error or non-compliance before continuing further testing. If the device joins successfully, the phrase "Device Nickname: 0x0004" would be found in the log. Sometimes, the device is able to join the network but has other errors or compliance issues which must be addressed.

Once the above have been completed and no errors seen, consider your device to be ready for running other wireless tests.

[*] - CAL tests that expect burst messages via the maintenance port will fail since WirelessHART devices do not publish burst messages over FSK. This is a known issue in Kit-192 v3.6 and will be addressed in future revisions where such tests would abort when run on WirelessHART devices. Until the test automation is updated, the following failures in WirelessHART devices may be ignored -

CAL103B - FP 5110

CAL103C - FP 5110
CAL104B - FP 5110
CAL107A - FP 5110
CAL108B - FP 5110
CAL109A - FP 5110

CAL109C - FP 5110

Additionally, CAL103A may fail with FP 1070 due to a radio limitation. The failure may be ignored for now.