| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008599 | 30120: IO-Link | Documentation Errata | public | 2023-01-13 09:44 | 2024-02-16 09:27 |
| Reporter | Martin Lang | Assigned To | Deepak Yadav | ||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | V1.01 | ||||
| Summary | 0008599: Datatype for Variable with gradient in IODD Menu | ||||
| Description | If an IODD variable from type integer or uinteger will be represented in IODD Menu (commissioning, observer, specialist), the variable can be extended with gradient and offset to provide the variable with a specific unit -> for example IODD variable “temperature” can be displayed with temperature unit °C or °F. | ||||
| Tags | No tags attached. | ||||
|
|
From word document "meeting notes", served by Joachim Stilt, translated by Deepl. (Last german version in meeting notes from 13.01.2023) 1) NodeID for Structure-DataType generated from RecordT (chapter 12.3.2) We found out that a RecordT does not necessarily have an ID and therefore we said that you should always use the ID of the variable or ProcessData. If a RecordT has an ID, it means that it comes from the DataTypeCollection and is then probably used several times in variables/ProcessData. If you now always take the ID of the variable/ProcessData, the DataType is created anew each time. This is redundant. So you should first check if the RecordT has an ID and if so, use it. Then the type is created only once. If it has no ID, the ID of the variable/ProcessData is used. This corresponds then also to the intention in the IODD. 2) Sub-Variables for Record Types (Chapter 12.3.2 and 7.3.6) The problem is that in the IODD records can have subindexAccessSupported=false and these are then nevertheless referenced in the menus with RecordItemRef and SubIndex. Then the sub-variable is not created and the link in the menus goes nowhere. One could solve this in such a way that the sub-variables are only created when they are referenced in menus. Then you can't access the device with index/subindex (because subindexAccessSupported=false), but you always have to read the whole dataset (SubIndex=0) and then extract the value for the sub-variable yourself. But that's the way it's meant to be, at least with ProcessDataInput. The question is, if this should be done for all variables or if an exception should be made for ProcessDataInput and DeviceAccessLocks. These are the two variables where I noticed that subindexAccessSupported=false and is still referenced via RecordItemRef from menus. Translated with www.DeepL.com/Translator (free version) |
|
|
Additional information was added that a calculated value from gradient + offset is always from OPC UA DataType float: 00085999.JPG (42,411 bytes) |
|
|
WG meeting: Agreed, incorporate change a shown in note before. |
|
|
Merged the changes into the main document : OPC 30120 - UA Companion Specification for IO-Link 1.01.00 Draft V00.02 |
|
|
WG review ok. |
