Release 1.7.1 - July 2025
This release reflects the following Specifications:
New features or components in this release:
Device Model Services bugs addressing endless loops reading device data
EDD Engine correction to date/time display in FF EDD templates
This release contains the following versions of components. Not all licenses will include all of these components:
Component | Version |
EDD Engine | 12.0.2 |
DMS | 1.7.1.3365 |
The following CRs were resolved in this release:
Device Model Services (DMS)
CR/Bug Number | Summary |
4299 | RRTE hangs and occupies 100% CPU when the user navigates to other root menus like Diagnostics, Maintenance, etc. for SIMOCODE device |
4037 | DMS exception when accessing missing function block |
4479 | Schema for Semantic map should be clearly numbered |
4433 | RRTE freezes when Command 50 returns codes not supported in DD. |
4274 | Variables used in graph are read 6 times during graph initialization |
4083 | REGRESSION: Test H-3.1-038 fails for FF and HART in .NET RUIP when executed in 1.6.0 build 601 (failing host test) |
4457 | RRTE Enhancement: Command 9 must different values in all slots for Device Variables greater than 8 |
3780 | CFF file [VFD 2 "x" Block Defaults] not properly supported for Bit String Variable Types |
4485 | Integrate .NET6 into delivery build process |
4395 | Write to HART device results in endless loop if device is already disconnected |
3841 | Difference of a variable outside of up/download or offline menu causes useless error message |
4454 | DMS not able to support EDD path longer than MAX_PATH characters |
3036 | RRTE stops responding during method |
1929 | PB/PN HTK FDI_H_4_18_001_PA and others - Big float and double values are not accepted |
EDD Engine
CR/Bug Number | Summary |
3199 | FF HTK TC_TEMP_001, TC_TEMP_002 - FF Date / Time datatypes in a DD5 EDD Template are not correctly displayed in RRTE |
Known Issues
Known issues at the time of release are included below. If additional notable issues are found with this version of the product, they will be added to this log for reference with the date they were reported.
CR/Bug Number | Component | Summary | Reported Date (MM/DD/YY) |