View Issue Details

IDProjectCategoryView StatusLast Update
000859030120: IO-LinkDocumentation Erratapublic2024-02-16 10:02
ReporterTobias Gürtler Assigned ToDeepak Yadav  
PriorityhighSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target VersionV1.01 
Summary0008590: Extend description for variable StoredInDevice
Description

Already listed in Internal Change Request List, to improve the description
https://opcfoundation.sharepoint.com/IO-Link/Work/Specifications/1.01%20Draft/Internal%20Change%20Request%20List.docx?d=w31389ad2f1844dbc97f216fac164f8a3
All three variables

  • ApplicationSpecificTag, ISDU Index 0x0018
  • FunctionTag, ISDU Index 0x0019
  • LocationTag, ISDU Index 0x001A
    are optional in an IO-Link Device.
    If the variable is supported, then the variable will be stored persistently in the IO-Link Device (See Common Profile Spec).
    Additionally an IO-Link Master cannot ask the IO-Link Device if the variable is stored persistently or not.
    Proposal here is to remove the sentence (here in red) in the spec to avoid confusion.
    „Note: If the ISDU Index 0x001X exists but its value is not permanently stored in the device, the server shall nevertheless not store the value persistently.”
Additional Information

Chapter 7.1.3 Components for ParameterSet Object and MethodSet Object Page 30

TagsNo tags attached.

Relationships

related to 0007416 confirmedDeepak Yadav Support for IO Link Wireless Extensions 

Activities

Martin Lang

2023-01-13 08:46

manager   ~0018470

JU: The named parameter shall be stored implicit within the IO-Link Device. These data are par of the IO-Link device Data Storage. Therefore this is a implicit IO-Link functionality.

Martin Lang

2023-01-13 08:46

manager   ~0018471

WG: Remove note from document.

Martin Lang

2023-01-13 12:16

manager   ~0018480

Last edited: 2023-02-10 18:41

Please remove „Note: If the ISDU Index 0x001X exists but its value is not permanently stored in the device, the server shall nevertheless not store the value persistently.” in companion specification documents V1.00.01 and V1.01.

Deepak Yadav

2023-11-22 11:13

developer   ~0020393

DY : Changes added into V1.01 document

Martin Lang

2024-02-16 09:57

manager   ~0020833

There was the WG decision in the past to not release a hotfix version 1.00.01 since no WG participant will require this update.

Martin Lang

2024-02-16 10:02

manager   ~0020834

WG review ok.

Issue History

Date Modified Username Field Change
2023-01-13 08:44 Martin Lang New Issue
2023-01-13 08:46 Martin Lang Note Added: 0018470
2023-01-13 08:46 Martin Lang Note Added: 0018471
2023-01-13 09:49 Martin Lang Additional Information Updated
2023-01-13 12:16 Martin Lang Note Added: 0018480
2023-01-13 14:36 Martin Lang Priority normal => high
2023-01-13 14:46 Martin Lang Assigned To => Deepak Yadav
2023-01-13 14:46 Martin Lang Status new => assigned
2023-01-16 07:04 Martin Lang Reporter Martin Lang => Tobias Gürtler
2023-02-10 17:00 Martin Lang Relationship added related to 0007416
2023-02-10 18:41 Martin Lang Target Version => V1.01
2023-02-10 18:41 Martin Lang Note Edited: 0018480
2023-11-22 11:13 Deepak Yadav Note Added: 0020393
2024-02-16 09:57 Martin Lang Note Added: 0020833
2024-02-16 10:02 Martin Lang Status assigned => resolved
2024-02-16 10:02 Martin Lang Resolution open => fixed
2024-02-16 10:02 Martin Lang Note Added: 0020834