# Change Log

### Release 1.1.0

DD-STAT builds in a CI/CD pipeline are now supported.

DD-STAT and FDI IDE now share the same license manager.

The installer removes the previous installation before installation (does not affect user files or licenses).

These formerly manual test cases are now automated: TFP911\_001, TFP816\_003, TFP816\_004

DD-STAT now retrieves information from previously registered packages in the FDI package repository.

HART test log ual11b.qa.log is now required with the submission.

Multiple failures in test cases on the range TFP814\_\* are corrected.

HART 6 DDs now find the manufacturer ID correctly.

TFP1211\_002 removes redundant reporting and improves the messaging. False failures are repaired.

TFP712\_001 uses correct macros for HART 6 devices.

TP1011\_004 improves the assessment of conditional device variable codes.

TFP612\_004 false passing is repaired.

TFP816\_004 false failure is repaired.

Multiple TFPs now evaluate as not applicable instead of inconclusive as appropriate.

### Release 1.0.2

The automation now requires CAL073.qa.log. This log reveals whether command 73 is supported by the device or not.

For device revisions and DD revisions, the automation now requires the registered encoded .fma file from the previous revision. The source for the previous DD is still required, but it is not tokenized.

Testcases 1211\_002 and 1211\_003 are now automated tests.

The automation is updated to allow IDE versions up to 1.7.0.2.

The 'ddstat init' command is enhanced to allow user to add a folder name as an argument. When no argument is provided, the command behaves as before, initializing in the current working directory. User can add a optional path name as an argument. The automation will create a new folder at that path and initialize it.

A false failure is prevented in the case where a device contains a device-specific command that is not listed in the EDD.

A false failure is prevented in the case where commands are defined in the symbols.txt file but not referenced in the EDD.

Improvements in the automation caused the Sample\_HART7 EDD that ships with the product to fail. This is repaired.

Resolved an issue where older HART Test System logs failed to parse.

Resolved an issue where the MANUFACTURER line in some DD's was not recognized.

In test case TFP814\_014, it is permitted to REDEFINE TYPE INDEX.

### Release 1.0.1

<table><thead><tr><th width="97" align="right">ID</th><th width="204">Test Point</th><th width="299">Summary</th><th>Released Version</th></tr></thead><tbody><tr><td align="right">1794</td><td>TFP811_004</td><td>false failure, delete is permitted</td><td>1.0.0</td></tr><tr><td align="right">1904</td><td>TFP711_005</td><td>DD needs to be marked “skipped” or “passed”, not inconclusive</td><td>1.0.0</td></tr><tr><td align="right">1908</td><td>TFP715_002</td><td>False pass - no AG10101 macros are referenced</td><td>1.0.0</td></tr><tr><td align="right">1917</td><td></td><td>new IDE 1.7.0 macro parameter for IMPORT_PV2_3_BASE is not supported</td><td>1.0.0</td></tr><tr><td align="right">1938</td><td>TFP811_00</td><td>Universal is redefined and common practice is not, requires analysis</td><td>1.0.0</td></tr><tr><td align="right">1940</td><td></td><td>Fatal while getting command 9 byte count from UAL011a</td><td>1.0.0</td></tr><tr><td align="right">2043</td><td>TFP813_007 </td><td>False pass - Redefinition macro  may only be used when the command 48 bytes do not match</td><td>1.0.0</td></tr><tr><td align="right">2044</td><td>TFP813_002</td><td>wrong macro name is identified</td><td>1.0.0</td></tr><tr><td align="right">2045</td><td>TFP813_008 </td><td>items shown are not actually VARIABLEs with definitions in the Universal IMPORT</td><td>1.0.0</td></tr><tr><td align="right">2046</td><td>TFP712_001</td><td>Remove check for commands 524 and 525 from IMPORT_TABLES_CONDENSED_STATUS and move them to IMPORT_CONDENSED_STATUS_MAP_WRITE</td><td>1.0.0</td></tr><tr><td align="right">2052</td><td>TFP813_007 </td><td>move command 48 output from TFP1011_002 to TFP813_007</td><td>1.0.0</td></tr><tr><td align="right">2053</td><td>TFP712_001</td><td>command 48 parameter issue is not detected</td><td>1.0.0</td></tr><tr><td align="right">2058</td><td></td><td>Some DD searches should be done on .i not .ddl</td><td>1.0.0</td></tr><tr><td align="right">2107</td><td>TFP813_007</td><td> error message is not clear</td><td>1.0.0</td></tr><tr><td align="right">2111</td><td>TFP621_005 </td><td>device specific command number range issue</td><td>1.0.0</td></tr><tr><td align="right">2112</td><td>TFP911_001 and TFP911_002  </td><td>not showing passed when errors Tok 859/860 are not present</td><td>1.0.0</td></tr><tr><td align="right">2120</td><td>TFP814_016 </td><td>review/rework</td><td>1.0.0</td></tr><tr><td align="right">2126</td><td></td><td>Using defines as arguments for macro parameters instead of numbers should be a failure</td><td>1.0.0</td></tr><tr><td align="right">2141</td><td></td><td>HART Sample DDs</td><td>1.0.0</td></tr><tr><td align="right">2162</td><td>TFP715_011 </td><td>Commands 72, 73, 74 and 75 having nothing to do with IMPORT_MISC_LOCK</td><td>1.0.0</td></tr><tr><td align="right">2163</td><td>TFP814_023</td><td>False Errors</td><td>1.0.0</td></tr><tr><td align="right">2164</td><td>TFP814_013</td><td>failure assigned to the wrong TFP</td><td>1.0.0</td></tr><tr><td align="right">2165</td><td>TFP814_014 </td><td>has no macro</td><td>1.0.0</td></tr><tr><td align="right">2181</td><td>TFP1111_008 </td><td>switch from manual to automation</td><td>1.0.0</td></tr><tr><td align="right">2196</td><td>TFP813_008 </td><td>false failure - should not fail as long as they are not REDEFINING the CLASS or HANDLING</td><td>1.0.0</td></tr><tr><td align="right">2198</td><td>TFP511_005 </td><td>false failure - need to use .i file</td><td>1.0.0</td></tr><tr><td align="right">2199</td><td>TFP811_004 </td><td>false failure - The reason for the failure is missing for TFP811_004 in the report</td><td>1.0.0</td></tr><tr><td align="right">2201</td><td>TFP621_009 </td><td>should be tokenizer not manual</td><td>1.0.0</td></tr><tr><td align="right">2202</td><td>TFP612_004 </td><td>false pass - report fails to capture tok error 694</td><td>1.0.0</td></tr><tr><td align="right">2260</td><td>TFP715_005 </td><td>false failure - should be marked “Passed” with a INFO(warning) in the details</td><td>1.0.0</td></tr><tr><td align="right">2261</td><td>TFP1211_001 </td><td>revised</td><td>1.0.0</td></tr><tr><td align="right">2264</td><td>TFP715_005, TFP715_007, TFP715_009, TFP715_010, TFP715_011 and consider adding TFP715_001 and TFP715_013</td><td>revised</td><td>1.0.0</td></tr><tr><td align="right">2265</td><td>TFP715_002, TFP715_006, TFP715_008, TFP715_012 </td><td>revised</td><td>1.0.0</td></tr><tr><td align="right"></td><td></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fieldcommgroup.org/dd-stat-documentation/help/change-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.