> For the complete documentation index, see [llms.txt](https://docs.fieldcommgroup.org/dd-stat-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldcommgroup.org/dd-stat-documentation/help/known-issues.md).

# Known Issues

### Release 1.2.0

#### Remain Manual

The following test point procedures remain manual in this release.

**TFP813\_009** -- Verify Command 48-byte descriptions do not contain user-defined conditional pre-processors (#if, #ifdef).

**TFP817\_004** -- For devices not supporting Command 50 and 51, verify primary\_variable\_code, secondary\_variable\_code, tertiary\_variable\_code or quaternary\_variable\_code are redefined as specified in 'Using the HART Standard DD', and contain constant values (i.e. in the range of 0-239) (Referred to as Fixed mapping).

**TFP1211\_003** -- Verify no new Variables, Enumerations, or Commands were added when compared to the last registered EDD and the corresponding registered device.

**TFP1211\_004** -- Verify the device is HART-Registered or currently under test.

#### False Passing

The following test point procedures are **known to produce false-passing results** in DD-STAT v1.2. These tests may report a passing result when a validation issue is actually present. Results for these TFPs should be verified manually.

**TFP711\_014** -- Verify latest released \_WIRELESS IMPORT revision is defined in the by matching the HART protocol version of the device as specified in 'Using the HART Standard DD', Table 2. (Note: Applicable only to WirelessHART devices). DDSTAT incorrectly indicates “Not Applicable (Skipped)” when this standard is imported for “wired HART devices” when the correct response is “Failed”. A status of “Skipped” must only occur for a wired device when this standard DD is not implemented.

**TFP711\_015** -- Verify the older Standard DDs released in FDI-IDE 1.4.2 and earlier are not imported and combined with the imports specified in 'Using the HART Standard DD', Table 2. DDSTAT incorrectly duplicates the errors reported for TFP711\_010 through TFP711\_014. This TFP does not fail only when an older, unsupported Standard DD (i.e., \_COMMON\_PRACTICE, DEVICE\_REVISION 9, DD\_REVISION) is used.

**TFP712\_001** -- Verify the IMPORT of \_TABLES DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' section 7.13.1. (Verify against the device test logs). DDSTAT incorrectly duplicates the errors reported for TFP711\_010 through TFP711\_014. This TFP does not fail only when an older, unsupported Standard DD (i.e., \_COMMON\_PRACTICE, DEVICE\_REVISION 9, DD\_REVISION) is used.

**TFP712\_006** -- Verify the only DD Items imported individually (not using an import macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'Additional items' section 7.13.1.29. DDSTAT incorrectly indicates a non-ERROR on some individual items imported which are not listed as an optional import item in the “Additional items” section of AG10101.

**Device Variable Imports**

**TFP715\_002** -- Verify the IMPORT of \_COMMON\_PRACTICE\_DEVICE\_VARIABLES DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' sections 7.4.1.1 - 7.4.1.6 (Verify against the device test logs, test is not applicable if the device does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the HART commands are not currently supported in the device for that device.

**TFP715\_003** -- Verify the only DD Items imported individually (not using an import macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'Additional items' section 7.4.1.7. DDSTAT incorrectly indicates a non-ERROR on some individual items imported which are not listed as an optional import item in the “Additional items” section of AG10101.

**Analog Channel Imports**

**TFP715\_005** -- Verify the IMPORT of \_COMMON\_PRACTICE\_ANALOG\_CHANNELS DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' section 7.5.1.1 (Verify against the device test logs, test is not applicable if the device does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the HART commands are not currently supported in the device for that device.

**TFP715\_006** -- Verify the only DD Items imported individually (not using an import macro) are those explicitly identified as an available option in 'Using the HART Standard DD' 'Additional items' section 7.5.1.2. DDSTAT incorrectly indicates a non-ERROR on some individual items imported which are not listed as an optional import item in the “Additional items” section of AG10101.

**Condensed Status Imports**

**TFP715\_007** -- Verify the IMPORT of \_COMMON\_PRACTICE\_CONDENSED\_STATUS DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' sections 7.6.1.1 - 7.6.1.2 (Verify against the device test logs, test is not applicable if the device does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the HART commands are not currently supported in the device for that device.

**TFP715\_008** -- Verify the only DD Items imported individually (not using an import macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'Additional items' section (if it exists). DDSTAT incorrectly indicates a non-ERROR on some individual items imported which are not listed as an optional import item in the “Additional items” section of AG10101.

**Burst Value Array Imports**

**TFP715\_009** -- Verify the IMPORT of \_COMMON\_PRACTICE\_BURST\_VAL\_ARRAY DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' section 7.7.1.1 - 7.7.1.5 (Verify against the device test logs, test is not applicable if the device does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of  “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the  HART commands are not currently supported in the device for that device.

DDSTAT incorrectly indicates a non-ERROR on many Burst Reference Array items imported when AG10101 does not list them as an option to be imported independently.

**Burst Reference Array Imports**

**TFP715\_010** -- Verify the IMPORT of \_COMMON\_PRACTICE\_BURST\_REF\_ARRAY DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' sections 7.8.1.1 - 7.8.1.6 (Verify against the device test logs, test is not applicable if the device does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of  “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the  HART commands are not currently supported in the device for that device.

DDSTAT incorrectly indicates a non-ERROR on many Burst Value Array items imported when AG10101 does not list them as an option to be imported independently.

**Misc Imports**

**TFP715\_011** -- Verify the IMPORT of \_COMMON\_PRACTICE\_MISC DD uses the import macros defined in macros2.h as specified in 'Using the HART Standard DD' sections 7.11.1.1 - 7.11.1.8 (Verify against the device test logs because test is not applicable if the DD does not support this feature). DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the HART commands are not currently supported in the device for that device.

**TFP715\_012** -- Verify the only DD Items imported individually (not using an imported macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'Additional items' section 7.11.1.9. DDSTAT incorrectly indicates a non-ERROR on some macros that are either not permitted due the use of “user-defined macros”, conditional AG10101 macros, not used in accordance with AG10101 and/or the HART commands are not currently supported in the device for that device.

**TFP811\_016** -- Verify that ENUMERATED and BIT\_ENUMERATED variables do not DELETE their enumerations when HANDLING is READ, and it is as an available option in 'Using the HART Standard DD'. DDSTAT incorrectly indicates a non-ERROR on some individual items being redefined and they are not explicitly called out in AG10101 as being permitted.

**TFP813\_002** -- Verify Command 8 matches the response as specified in 'Using the HART Standard DD' section 7.1.3.2. (Verify against the device test logs). DDSTAT incorrectly indicates a non-ERROR on occasions when Command 3 is evaluated incorrectly (inconsistent results) .

**Universal Redefinitions**

**TFP813\_007** -- Verify Command 48 matches the response bytes as using only 1 redefinition macro (per HART protocol revision) as specified in 'Using the HART Standard DD' section 7.1.3.4 (HART 5), 7.1.3.5 (HART 6) or 7.1.3.6 (HART 7). (Verify against the device test logs).

There are 3 macros can be applied depending on the HART version:

HART 5 -> REDEFINE\_H5\_COMMAND\_48\_TRANSACTIONS

HART 6 -> REDEFINE\_H6\_COMMAND\_48\_TRANSACTIONS

HART 7 -> REDEFINE\_H7\_COMMAND\_48\_TRANSACTIONS

Currently, a False Passing is issued if the macro is applied using the wrong HART version.

**TFP813\_008** -- Verify the only universal command Variables redefined individually (not using a redefinition macro) are defined as specified in 'Using the HART Standard DD', sections 7.1.3.7-7.1.3.10. DDSTAT incorrectly indicates a non-ERROR on some individual items being redefined and they are not explicitly called out in AG10101 as being permitted. Universal commands and variables can only be redefined using a designated AG10101 macro.

**TFP813\_009** -- Verify Command 48-byte descriptions do not contain user-defined conditional pre-processors (#if, #ifdef). DDSTAT incorrectly indicates a non-ERROR on conditional #if/#else "strings" applied to the enumerated description and/or enumerated help. Note: Currently, this TFP is evaluated manually.

**Device Variable Redefinitions**

**TFP814\_013** -- Verify the \_COMMON\_PRACTICE\_DEVICE\_VARIABLES DD uses the redefinition macros defined in macros2.h as specified in 'Using the HART Standard DD' 'REDEFINITIONS' section 7.4.3 (Verify against the device test logs, test is not applicable if the device does not support this feature).

**TFP814\_014** -- Verify the only DD Items redefined individually (not using a redefinition macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'REDEFINITIONS' section 7.4.3. DDSTAT incorrectly indicates a non-ERROR on some individual items being redefined and they are not explicitly called out in AG10101 as being permitted. Common Practice commands can only be redefined using designated AG10101 macro; they cannot be redefined individually.

**Condensed Status Redefinitions**

**TFP814\_018** -- Verify the COMMON\_PRACTICE\_CONDENSED\_STATUS DD uses the redefinition macros defined in macros2.h as specified in 'Using the HART Standard DD' 'REDEFINITIONS' sections 7.6.3.1 - 7.6.3.2 (Verify against the device test logs, test is not applicable if the device does not support this feature).

**TFP814\_019** -- “Verify the only DD Items redefined individually (not using a redefinition macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'REDEFINITIONS' section 7.6.3.3. DDSTAT incorrectly indicates a non-ERROR on some individual items being redefined and they are not explicitly called out in AG10101 as being permitted.

**Burst Reference Array Redefinitions**

**TFP814\_023** -- Verify the only DD Items redefined individually (not using a redefinition macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'REDEFINITIONS' sections 7.8.3.8 - 7.8.3.15. There are known instances where DDL items are permitted to be redefined individually according to AG10110, but the redefinition does not match the techniques that are explicitly stated to be performed. DDSTAT is incorrectly indicating “Passed” when it must be marked as “Failed”.

**PV1 and PV2 Redefinitions**

**TFP817\_002** -- Verify the only DD items redefined individually (not using a redefinition macro) are those explicitly identified as an available option in 'Using the HART Standard DD', 'REDEFINITIONS' section 7.2.3.2 - 7.2.3.8 (PV 1) or 7.3.3.1 - 7.3.3.9. (PV 2). DDSTAT incorrectly indicates a non-ERROR on some individual items being redefined and they are not explicitly called out in AG10101 as being permitted.

**TFP817\_004** -- For devices not supporting Command 50 and 51, verify primary\_variable\_code, secondary\_variable\_code, tertiary\_variable\_code or quaternary\_variable\_code are redefined as specified in 'Using the HART Standard DD', and contain constant values (i.e. in the range of 0-239) (Referred to as Fixed mapping). DDSTAT incorrectly indicates a non-ERROR on some individual items which are permitted to be redefined, but the redefinition does not match the techniques that are explicitly stated to be performed when command 50 is not supported.

**TFP911\_001** -- Verify all mandatory root\_menu(s) are implemented. root\_menu, device\_root\_menu, process\_variables\_root\_menu, diagnostic\_root\_menu. The Device Description Language Specification currently requires the following root menus; however, they may be excluded from HART EDDs: offline\_root\_menu maintenance\_root\_menu

**TFP1011\_004** -- Verify that Device Variable Codes 0-239, 242-245 are the only acceptable codes defined in the ARRAY OF COLLECTION deviceVariables. DDSTAT incorrectly indicates a non-ERROR on some individual FDI only items not being removed via **TOKVER** >= 1000.

#### Other Known Issues

The following test point procedures have known open issues that may affect test results. These are distinct from false-passing issues and may include false failures, crashes, or other unexpected behavior.

**TFP511\_005** -- A known false failure occurs on every device and EDD revision and is a high priority for the next release.

**TFP631\_004** -- Multiple false failure issues: incorrect flagging of device variables that do not support trimming, incorrect flagging of items not required when Command 534 is unsupported, and trim member validation errors for device variables not in the trimDeviceVariables list.

**TFP711\_012** -- False failure for devices that support Common Practice "Multiple Analog" commands.

**TFP713\_001** -- IMPORT\_UNIVERSAL\_EVENT\_VAL\_ARRAY() macro is not being evaluated correctly. Error messages are displaying for the wrong test point in HART 5 devices.

**TFP713\_009** -- HART 5 individual import exceptions need to be allowed.

**TFP714\_001** -- False "Skipped" result with two or more analog outputs.

**TFP714\_002** -- Test case is incorrectly present; TFP714\_002 is marked "Reserved."

**TFP714\_006** -- The additional item list for PV is not programmed into DD-STAT.

**TFP811\_016** -- False failure on loop alarm code and write protect redefine errors. Inconsistent behavior observed.

**TFP811\_017** -- False failures: Fixed Mapping permits FCG macros that are not being recognized. Items incorrectly flagged as not being FCG-defined macros. Burst Variables are not being detected as containing user-defined macros.

**TFP813\_001** -- Issue with extra braces in validation.

**TFP813\_003** -- False failure in test validation.

**TFP814\_015** -- Test is marked as "Manual" but the detail log correctly reports it as skipped.

**TFP814\_021** -- False failure for DELETE on MEMBER items BURST\_VALUE and BURST\_REF.

**TFP814\_022** -- Excessively repetitive output for information that only needs to be displayed once.

**TFP817\_017** -- New approved macros for standard variables need to be added.

**TFP911\_002** -- Open issue in test validation.

**TFP911\_003** -- Multiple issues: some menus shared inappropriately with FDI offline root menu, false failure errors on methods not on the offline\_root\_menu, false failures on certain MENUs, logic not finding real issues with METHODs, and missing validation logic.

**TFP1011\_003** -- Invalid project file handling issue.

**TFP1211\_002** -- Failing to detect that data references were changed.

### Release  1.1.0

<table><thead><tr><th width="114">Version</th><th>Description</th></tr></thead><tbody><tr><td>Beta-2</td><td>Add a progress indicator to the Run button</td></tr><tr><td>1.0.2</td><td>TFP715_006 Common Practice Commands (in Wired HART) are never required</td></tr><tr><td>1.0.2</td><td>TFP511_005 device type names not matching</td></tr><tr><td>1.0.2</td><td>TFP715_012 is fails for a missing COMMAND squawk which is actually implemented in the device</td></tr><tr><td>1.1</td><td>TFP814_021 and 023 False Failure for DELETE on MEMBER items BURST_VALUE and BURST REF</td></tr><tr><td>1.1</td><td>TFP811_004 "False Passed" Verify that ENUMERATED and BIT_ENUMERATED variables do not DELETE their enumerations when HANDLING is READ</td></tr><tr><td>1.1</td><td>TFP813_008 TFP712_001 "False Passed" Command 48 is being individually redefined</td></tr><tr><td>1.1</td><td>TFP511_005 False Failure error comparing the device type</td></tr><tr><td>1.1</td><td>TFP813_008 False Passed Command 48 is not permitted to be redefined</td></tr><tr><td>1.1</td><td>SET_DEFAULT may be used on any standard variable for any IMPORT</td></tr><tr><td>1.1</td><td>TFP814_018 False Failure IMPORT condensed status map write macro parameter matching is incorrect</td></tr><tr><td>1.1</td><td>TFP813_009 False Skipped Command 48 is being redefined by their own user-defined macro</td></tr><tr><td>1.1</td><td>TFP611_006 False Passed The use of company specific #defines, macros within IMPORTs is prohibited.</td></tr><tr><td>1.1</td><td>TFP811_004 False Passed VARIABLE write_protect and loop_alarm_code should fail for HANDLING READ.</td></tr><tr><td>1.1</td><td>TFP816_004 False Failure This appears to be "case sensitive issue".</td></tr><tr><td>1.1</td><td>TFP1011_004 Verify that Device Variable Codes 0-239, 242-245 are the only acceptable codes defined in the ARRAY OF COLLECTION deviceVariables</td></tr><tr><td>1.1</td><td>TFP1211_002 False Failure after redefinition of default values</td></tr><tr><td>1.1</td><td>TFP712_001 False Failure (HART 6 Device) IMPORT_TABLES_LOCK() macro is explicitly stated in AG10101 as being support by HART 6 devices</td></tr><tr><td>1.1</td><td>TFP911_003 False Failure All three MENUs which live in the FMA only space are encapsulated with TOKVER >= 1000 and should not be failing</td></tr><tr><td>1.1</td><td>TFP814_014: Items False Passed "Redefinitions" should not be allowed because the items which are redefined are identical to the original</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.fieldcommgroup.org/dd-stat-documentation/help/known-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.