Current Released Version

Release 3.5 - October 2017 The following CRs were resolved in this release:
CR Number Summary Affected Components
3630
Does not send parity errors
DLL028
5407
Private Label Distributor value from Command 0
DLL032
5608
FP1012 should allow Success or Conflict
DLL045B
5792
Test logs show incorrect HW version
All DLL Tests
3775
Classification conflict with Command 9
UAL012
3999
Cannot compare NAN values
UAL011b
5624
FP 3262 fails on equal NaN values
UAL011B
5649
Send consistent number of dvars
UAL011B
5737
Failure point 3258 on NaN loop current value
UAL011B        
5748
Fails due to ConfigChangedCounter check
UAL009
5789
Test logs show incorrect HW version
All UAL Tests
5797
FP 3224 is redundant
UAL011A
5804
Does not xOr bytes
UAL006
5606
Tests can get caught in an endless loop
CAL523C
5686
Update message at FP 7890
CAL523B
5717
Script expecting incorrect map code on command 524 response
CAL524B
5720
extra map codes are being sent failure point 11014
CAL524B
5729
FP11001 is checking wrong map code
CAL524A
5737
Failure point 3258 on NaN loop current value
UAL011B
5791
Test logs show incorrect HW version
All CAL Tests
5815
Update for quickly bursting devices
DLL028
5829
FP 3249 testing incorrect variable
UAL011B
5834
UDP not behaving correctly according to test spec
All UAL & CAL Tests
     Known issues 
#5604
.OUT file does not match test log
UAL000
#5617
Test results confusing for wireless device
CAL071B
#5619
Test case gives a false Pass
CALU526F
#5620
Test case causes subsequent tests not to be executed
CALU526F
#5598
Move continue test question
DLL040
#5256
Failure point 702 valid check byte inadvertently sent in message
DLL009
#5841
Need new message object
CheckForCommand library function
#5599
FP 508 Not Following Test Specification
DLL033C
     Operational issues
#5741
Command 104 Needs to use LTL & UTL
DLL045C



Previous Released Versions


Patch for Release 3.3 - June 2017
The following CRs were resolved in this patch:

  • #5597 - CAL526D: FP 11153 is a duplicate
  • #5648 - Review UAL009 FP 2987
  • #5656 - DLL044B test automation trigger units incorrect
  • #5675 - FindNextDeviceVariable skips of dvar with dvar.Units == 251 or 253
  • #5685 - CAL524B: Is not sending map codes 0x07, 0x03
  • #5691 - CAL526C: Test is not sending Command 48
  • #5705 - UAL038A: FP 3472 Test writing original message
  • #5716 - CAL526C: Typo in FP Message (RE: DEVICE_STATUS_SIMULATED, FP11145)


References:
  • HCF_TEST-001, FCG TT20001 [Revision 3.1]
  • HCF_TEST-003, FCG TT20005 [Revision 4.1]
  • HCF_TEST-004, FCG TT20004 [Revision 5.0]
Known issues to be resolved in the next release include:

HART Technology WG has reviewed and concurred that Command 8 must align with precedent in Command 9.

Dynamic Variables not supported by the device need to return 0 "Not Yet Classified" for Command 8.

UAL012 fails when SV or TV (correctly) return zero in the Command 8 response when SV or TV are not supported by the device.  Command 8 response will require manual verification.

See CR#3775 and #3275. 


Release 3.3 - March 2017
The following changes are included in this release:
  • Installation of version 3.3 requires the existing installed version to be v3.0 or higher.
  • Improved Token-Passing Data-Link test automation
  • Improved Universal Command test automation
  • Improved Common Practice Command test automation
  • New (beta) Condensed Status Tests
  • Improved HSniffer utility
  • New Scripts added


Slave Token-Passing Data-Link Layer Tests
New Tests:
  • DLL033D
  • DLL045A (verify the compliance Command 103)
  • DLL045B (verify the compliance Command 104)
  • DLL045C (verify the compliance Smart Publishing)
 Updated Tests:
DLL001A DLL001B DLL001C DLL001D DLL001E DLL001F DLL002 DLL003 DLL004  DLL005 DLL006 DLL007 DLL009 DLL010 DLL011 DLL012 DLL014 DLL015 DLL016 DLL017 DLL018 DLL019 DLL020 DLL021 DLL022 DLL023 DLL024A DLL024B DLL024C DLL025 DLL026 DLL027 DLL028 DLL029 DLL030 DLL032 DLL033A DLL033B DLL033C DLL034 DLL035 DLL036A DLL036B DLL036C DLL036D DLL037A DLL037B DLL037C DLL037D DLL038 DLL039A  DLL039B DLL040  DLL041 DLL042 DLL043A DLL043B DLL044A DLL044B

Issues Resolved:
#3618 #3634 #3799 #4098 #4130 #4266 #4348 #4352 #4389 #4436 #4585 #4625
#4714 #4921 #4979 #5033 #5056 #5057 #5058 #5069 #5075 #5076 #5148 #5160
#5161 #5182 #5191 #5192 #5193 #5209 #5248 #5251 #5256 #5259 #5261 #5264
#5282 #5305 #5308 #5316 #5317 #5359 #5386 #5397 #5398 #5399 #5400 #5401
#5402 #5403 #5404 #5406 #5410 #5412 #5413 #5415 #5418 #5426 #5429 #5450
#5461 #5465 #5486 #5533 #5554 #5556 #5565 #5566 #5567 #5570 #5587 #5588

Universal Command Tests
Updated Tests and Scripts:
UAL000 UAL001 UAL005 UAL006 UAL007 UAL008 UAL009 UAL010 UAL011A UAL011B UAL012 UAL013 UAL038A UAL038B UAL048A UAL048B

Issues Resolved:
#2737 #2667 #2790 #3775 #3886 #4037 #4131 #4263 #4581 #4603 $4659 #4708
#4715 #4764 #5169 #5170 #5195 #5199 #5201 #5210 #5250 #5298 #5357 #5432
#5439 #5440 #5447 #5451 #5463 #5506 #5507 #5528 #5534 #5542 #5543 #5546
#5548 #5560 #5563 #5571 #5575 #5576 #5577 #5578 #5581 #5585

Common Practice Tests 
New Tests:
CAL523A CAL523B CAL523C CAL524A CAL524B CAL524C CAL524D CAL524E CAL524F CAL526A CAL526B CAL526C CAL526D CAL526E CAL526F

A total of fifteen new test cases that test Condensed Status functionality have been added. The CAL523, CAL524, CAL526 series tests are in a Beta state. If an issue is encountered please file a change request at the following URL: http://www.hcftracker.net


Updated Tests:
CAL000 CAL033 CAL034 CAL035 CAL036 CAL037 CAL040 CAL041 CAL042 CAL043 CAL044 CAL045 CAL046 CAL047 CAL049 CAL050 CAL051 CAL052 CAL053 CAL054 CAL055 CAL056 CAL071A CAL071B CAL072 CAL073 CAL074A CAL074B CAL074C CAL074D

Issues Resolved:
#3191 #4132 #4371 #4551 #4796 #5072 #5150 #5154 #5184 #5198 #5214 #5225
#5272 #5304 #5358 #5438 #5447 #5449 #5451 #5462 #5470 #5491 #5494 #5512
#5518 #5522 #5527 #5528 #5529 #5534 #5535 #5542 #5543 #5545 #5546 #5560
#5590 #5614


HSniffer
Issues Resolved:
#5454 #5531 #5532 #5550



Known issues to be resolved in the next release include:


#5617 - CAL071B results confusing for wireless device

#5606 - CAL523C endless loop
  • If the device replies with RC 0x02 the test will continue in an endless loop. To manually override the test execution, press CTRL+C to continue. 
  • Manual inspection required to verify results

#5597 - CAL526D FP 11153 is a duplicate and will be replaced with FP 11163.

#5619 - CALU526F gives a false Pass

#5620 - CALU526F causes subsequent tests not to be executed due to the device not being alive on the network.
 
#5599 - DLL033C FP 508 Not Following Test Spec
 
#5598 - DLL040 Move continue test question
  • User should select "y" to continue the test, else the test exists prematurely

#5604 - UAL000 .out file does not match test log


Release 3.2 - December 2015
The following changes are included in this release:
  • All QA/QC processes on this HART Test System are complete, including regression tests confirming proper operation of each Failure Point (FP) in corresponding HART Test Specifications.
     
  • Detailed lists of updated test automation and improved scripts for Slave Token-Passing Data-Link Layer, Universal Command, and Common Practice Command tests are listed below.


Slave Token-Passing Data Link Layer Tests
Improvements to the Token-Passing Data Link Layer tools include the resolution of the following HCFTracker change requests were resolved: #3268, #3760, #4164, #4171, #4268, #4269, #4283, #4295, #4296, #4359, #4360, #4586, #4594, #4651, #4687, #4741, #4766, #4805, #4806, #4816, #4867, #4905, #4981, #5002, #5005, #5014, #5023, #5053, #5125, #5133.  Resolution of these change requests resulted in improvements to the following tests: DLL002, DLL010, DLL016, DLL019, DLL022, DLL024B, DLL024C, DLL026, DLL027, DLL029, DLL035, DLL037D, DLL039A, DLL039B, DLL040, DLL043A, DLL043B, and DLL045.  Improvements were also made to testdll and testdlludp.

In addition, improvements to HSniffer were made to optimize performance and enhance integration with the HART Test System.

Universal Command Tests
Improvements to the Universal Command Tests  include the resolution of the following HCFTracker change requests: #4636, #4681, and #4689.  Resolution of these change requests resulted in improvements to the following tests: UAL000 and UAL009.  Improvements were also made to testual and testualudp.

Common Practice Command Tests
Improvements to the Common Practice Command Tests include the resolution of the following HCFTracker change requests : #3168, #4248, #4329, #4551, #4559, #4574, #4575, #4591, #4592, #4656, #4666, #4667, #4684, #4701, #4719, #4738, #4743, #4794, #4796, #4801,  #4917, #4962, #5027, #5079, #5096, #5104, #5105, #5118, and #5167. Resolution of these change requests resulted in improvements to the following tests: CAL000, CAL040, CAL042, CAL044, CAL045, CAL046, CAL047, CAL050, CAL053, CAL054, CAL055, CAL056, CAL071A, CAL071B, and CAL072.  Improvements were also made to testcal and testcaludp.



Known issues to be resolved in the next release include:


#4714 - DLL033C not properly testing Loop Current, Command 6
  • Send Command 6 with 1 data byte to change Polling Address to 0 --> Loop Current Mode must be set to 0x01. This is currently manually tested.


#4979, #5357, #5358, #5407 - Need to parse all Command 0 fields
  • Private Label code is not verified via automation. Must not be 0x0000. Must match Manufacturer ID unless it is private labeled product. This is currently manually tested.
  • Device Profile code is not verified via automation. Must not be 0x00. Must use Device Profile Code from Common Tables. This is currently manually tested.

#5298 - UAL038A should poll for device like UAL010

#5304 - CAL033, CAL052 - CAL056 Macro findNextDeviceVariable
  •  findNextDeviceVariable must update to the Slave Common Practice Command Test Specification (HCF_TEST-004 r4.1).


#5305 - DLL035 does not correctly handle RC == 8
  • Command 59 request with value 21 preambles or greater must receive a device response with Response Code of error "Passed Parameter Too Large" (RC == 3) or warning "Set To Nearest Possible Value" (RC == 8). If the DUT responds with the warning it can be mistakenly failed with "Faildll035354DLL035, Insufficient STX's detected. Failure Point==354".


#5308 - DLL044A Failure Point == 951 BACK Count
  • Increase tolerance to 5% (i.e. ABS(cmd9 - cmd3) < 5 = PASS)


#5316 - DLL035: Failure Point == 888 fails a DUT with the correct Byte Count
  • Command 59 request with value 1 in the data field must receive a device response with Response Code of error"Passed Parameter Too Small" (RC == 4) or warning"Set To Nearest Possible Value" (RC == 8). If the device returns RC == 8 then the preamble count must be 5. However, the automation fails a device that responds with 5 preambles.


#5317 - DLL026: Failure Point == 408 Fails DUT when it returns Command 2, RC == 8
  • Add RC == 8 (Update Failure) to the list of accepted response codes that will not trigger Failure Point == 408.


#5320 - DLL033C: Add verification the correct "Loop Current Mode" is set based on the POLL_ADDRESS that was written.


#5391 - DLL033C: Verify command 7 matches command 6 response
  • The test must send command 7 to verify the Loop Current Mode matches between command 6, command 7, and the device status. These three items must remain consistent. This is currently manually tested.


#5438 - CAL071B: Does not properly exit for Response Code "Command Not Implemented" RC == 64
  • Test must abort if it encounters Failure Point 5125 or 5126 


Release 3.0 - August 2014
Major revision update
Release 2.3 - March 2014
Last minor version update before Release 3.0
Release 2.1 - June 2012
Hardware processor change (Atom)        
Release 1.5 - March 2010 Summary of changes over previously released version (bug #s are listed
where applicable):

Data Link Layer
* DLL019
  - (#2966) This test was terminating early, before sufficient BACK
     messages were acquired and incorrectly causing the device to fail.
* DLL032
  - (#3030) This test was checking the entire byte value, rather than
    the bit field. This could incorrectly fail a wireless device.
* DLL033a
  - (#2997) This test had an erroneous failpoint 350.
  - (#3146) A queue initialization error in the QAS script inhibited
    the command 6's from issuing properly.
* DLL033c
  - (#3038, 3090) The Loop Current Fixed bit from the Device Status
    byte was not detected correctly in the post processing.
  - (#2999,2995) The draft spec and the test automation had deficiencies
    related to logic for Loop Current Enabled handling, which have been
    thoroughly reviewed and fixed.
* DLL038
  - (#3141) The post processing for this test now checks the revision
    number correctly.
* DLL039a
  - (#3149) This test was updated to only emit 20,000 messages for a
    wireless device being tested over a maintenance port.
* DLL040
  - (#2889) The post processing on this multi-drop test now correctly
    handles cold start bit.

Application Layer (v1.5)

* All Tests
  - Token-Passing over FSK connections is enhanced.
  - New -v command line option prints test name and version.
* UAL000
  - (#2812) The processing of command 31 is corrected.
* UAL048
  - (#3126) The test is divided into two tests, UAL048a and b.
  - (#3127) Command 48 data handling corrected.
* CAL000
  - (#3091) Command 105 byte counts corrected
  - (#3030, #3031) Command 75 and 77 for wireless adapters via FSK
* CAL044
  - (#3157) PV Units code handling for codes 250 to 255
* CAL074d
  - (#2873) Command 94 not required

HTEST (v1.4)
* (#3003) Modified the library function script_sleep() to enable it to
  sleep for longer intervals.

HARTMENU (v1.4)
* (#3239) Modified to reflect updated UAL tests list.

Release 1.4 - October 2009 Summary of changes over previously released version (bug #s are listed
where applicable):

Data Link Layer
* All Tests
  - (#2589) DLL tests now support command 109 returning "Invalid Selection"
    for wireless devices bursting only on the TDMA channel.
* DLL001e, DLL033a
  - (#2726) These tests have been modified so that the DUT can use poll
    addresses other than 0.  Previously, these tests would fail the DUT
    unnecessarily.
* DLL003
  - This test requires devices to correctly frame messages that use
    expansion bytes.  The failures have been changed to warnings.
* DLL018, DLL024a, DLL026
  - (#2679) HART 7 devices may return response code 14 indicating warning
    that dynamic variables were used in place of device variables. The
    post processing has been corrected so that code 14 is allowed for
    HART 7 devices.
* DLL024c
  - (#2902) The error string for failure point 435 is now printing correctly.
* DLL038
  - (#2905) the HART spec allows a DUT to return a buffer overflow
    indication if a message it receives is too long for its buffers.
    This test uses command 22 to write a long tag to the DUT and one of
    the variations sends a long tag plus one data byte.  This can overflow
    the buffers on some devices.  The Test spec and automation have been
    corrected to allow "Buffer Overflow" in this situation.
  - (#2802) The test handles broadcast addressing correctly.
* DLL040
  - (#2590) The QAS script was updated to support 16-bit manufacturer id
    and expanded device types.  The post processing is now correctly
    counting the number of devices on the bus.  A defect remains that
    may keep a HART 7 device from passing the test.
* DLL042
  - (#2889) The post processing now correctly handles response codes
    "Success" and "Invalid Expanded Command Number" near failure point 243.

Application Layer (v1.4)
* All Tests
  - The operation of the Token-Passing has been enhanced.  It is possible
    to stop a running test with a Ctrl-C and to re-size a terminal window
    without killing the program inadvertantly.
* UAL000
  - (#2811, 2812) The processing of command 31 is added to the test.
* UAL001
  - (#2852) The test specification and automation program are corrected
    for the loop current on wireless devices.
* UAL007
  - (#2803) This test now examines the analog channel input flags.
* UAL011a
  - (#2912, 2913) Devices that return 0x00 for Max Device Variable
    supported (byte 13 of command 0 response) must respond to device
    variables 0, 1, 2, 3. (PV, SV, TV, QV).  The test now allows
    "Dynamic variables Returned for Device Variables" in this case.
  - (#2990) An "Invalid Selection" response is also accepted.
* UAL011b
  - (#2904) Floating point comparisons for the PV have been enhanced to
    use the upper and lower range limits as a context for the floating
    point comparison.
* UAL013
  - (#2837) The test now allows a buffer overflow status when command 22
    is issued with an extra data byte.
* UAL038b
  - (#2804) This test now aborts for hart 5 and 6 devices.  Earlier, the
    test was being incorrectly applied to such devices.
* CAL000
  - (#2833) The test vectors for this automation were upgraded for
    commands above command 90 for HART 5,6 and 7.
* CAL033
  - (#2957) This test now correctly counts device variables in some
    situations that it did not, previously. Floating point comparisons
    for the PV have been enhanced to use the upper and lower range limits
    as a context for the floating point comparison.
* CAL034
  - (#2935) The checking for recommended commands at the beginning of
    the automation has been corrected.
* CAL035
  - (#2702) This test now allows "Invalid Units" response code to be
    returned from command 35.
* CAL036
 - Floating point comparisons for the PV have been enhanced to use the
   upper and lower range limits as a context for the floating point
   comparison.
* CAL071b
  - (#2958) The test now processes a command 12 response correctly.
* CAL074a,b,c,d
  - (#2871) This test now aborts for adapter being tested on a TP network.
* CAL074d
  - (#2873) The test now aborts if command 94 is not implemented, as
    command 94 is recommended but not required for wireless adapter.

HTEST (v1.3)
* Added the following new library functions to enable easier retrieval
  of information from responses received from a device:
  - get_byte_count()
  - get_resp_code()
  - get_response()

* (#2892) Added signal handler to capture linux signal received when a
  terminal window is resized.

HARTMENU (v1.3)
* (#2909) Modified to reflect available test list correctly.

Release 1.3 - July 2009
Release 1.0  - February 2009
First automated test system available