View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000446810000-008: Data AccessSpecpublic2018-11-21 15:472023-10-24 13:13
ReporterWolfgang Mahnke Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
Summary0004468: Description of allowed EngineeringUnits
Description

Remark: Not sure if this should be addressed in Part 8 or Part 3. As EngineeringUnits originates from Part 8 I assigned it to Part 8.

Currently we have defined a Property for EngineeringUnits providing information about the unit of a Variable.
Potentially the unit can be configurable, e.g. by making the EngineeringUnits property writable. However, in that case we have no standardized way to expose the allowed settings. For example, for a temperature sensor you might set the EngineeringUnits to "°K", "°C", or "°F", but not to "m", "kg", etc.

We could for example define another property with the list of allowed EngineeringUnits. A SelectionListType cannot be applied since EngineeringUnits is a Property.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004403 closedKarl Deiretsbacher Engineering Unit not complete 

Activities

Goetz Goerisch

2022-06-15 05:45

reporter   ~0016844

@Karl, ist this going to be address with the upcoming Part 8 revision and the proposed updates from VDMA?

Jim Luth

2023-08-01 16:56

administrator   ~0019766

Wlofgang,

Is this solved by the Quantity enhancement to Part 8?

Wolfgang Mahnke

2023-08-02 06:06

developer   ~0019768

The new content of Part 3 may help, but do not really solve the issue.

If you reference to all temperature units the server supports, it may be more than the specific measurement point / device supports.

Potentially, you may also completely change what is measured (e.g. from temperature to flow). In this case, I would assume, you are not just changing the engineering unit but have some other mechanisms.

P.S. Not sure about the workflow, I changed it to "new"

Jim Luth

2023-09-26 15:23

administrator   ~0020057

This may be "solved" by FLC as they need these types of constraints for off-line engineering.

Issue History

Date Modified Username Field Change
2018-11-21 15:47 Wolfgang Mahnke New Issue
2018-12-04 17:06 Jim Luth Relationship added related to 0004403
2018-12-04 17:08 Jim Luth Assigned To => Karl Deiretsbacher
2018-12-04 17:08 Jim Luth Status new => assigned
2020-12-02 07:59 Karl Deiretsbacher Status assigned => acknowledged
2020-12-02 08:00 Karl Deiretsbacher Assigned To Karl Deiretsbacher =>
2022-06-15 05:45 Goetz Goerisch Note Added: 0016844
2023-08-01 16:56 Jim Luth Note Added: 0019766
2023-08-01 16:56 Jim Luth Status acknowledged => feedback
2023-08-02 06:06 Wolfgang Mahnke Status feedback => new
2023-08-02 06:06 Wolfgang Mahnke Note Added: 0019768
2023-09-26 15:23 Jim Luth Assigned To => Jim Luth
2023-09-26 15:23 Jim Luth Status new => acknowledged
2023-09-26 15:23 Jim Luth Note Added: 0020057
2023-10-24 13:13 Jim Luth Assigned To Jim Luth =>