View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000861530120: IO-LinkFeature Requestpublic2023-01-13 10:412023-08-04 08:37
ReporterMartin Lang Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target VersionV1.01 
Summary0008615: Change IOLink-ObjectTypes parent type (Changes by Part 100 (DI)
Description

Due to updated Part 100 information model move all ObjectType IOLinkMasterType, IOLinkPortType and IOLinkDeviceType from ParentNode TopologyElementType to ComponentType.

TagsNo tags attached.

Relationships

related to 0006531 assignedDeepak Yadav Add interfaces IVendorNamePlate und ITagNameplate 
related to 0007416 confirmedDeepak Yadav Support for IO Link Wireless Extensions 

Activities

Martin Lang

2023-02-10 14:39

manager   ~0018701

WG decision: We will use IVendorNamePlate und ITagNameplate and NOT move the ObjectType below ComponentType.

New descision required: Where should the wireless ObjectTypes be located.

Martin L. will ask Wolfgang Mahnke again.

Martin Lang

2023-02-14 15:24

manager   ~0018709

Last edited: 2023-03-10 13:50

WM 23.08.2022: So, with the ComponentType, it only adds optional, in that it's not really clean, but shouldn't break anything.
The question is why you would want to do that. As far as I can remember, it was about using some DI properties like serial number. There are interfaces for that in DI now (IVendorNameplateType or something). So I would recommend to make explicit in an update of the specification that these interfaces are implemented. Then you don't need to touch anything in the type hierarchy.
Translated with www.DeepL.com/Translator (free version)

Martin Lang

2023-02-14 15:26

manager   ~0018710

Last edited: 2023-08-03 13:46

New descision required: Where should the wireless ObjectTypes be located.
Imho the new added types shall also be located below the TopologyElementType.
WG decision required.

Martin Lang

2023-08-03 13:47

manager   ~0019787

WG decision required.

Martin Lang

2023-08-04 08:37

manager   ~0019817

WG decision: We reject this issue. Will be solved by linked issues.

Issue History

Date Modified Username Field Change
2023-01-13 10:41 Martin Lang New Issue
2023-02-10 14:36 Martin Lang Relationship added related to 0006531
2023-02-10 14:39 Martin Lang Note Added: 0018701
2023-02-10 14:40 Martin Lang Assigned To => Martin Lang
2023-02-10 14:40 Martin Lang Status new => assigned
2023-02-10 14:40 Martin Lang Status assigned => confirmed
2023-02-10 16:55 Martin Lang Relationship added related to 0007416
2023-02-10 18:49 Martin Lang Target Version => V1.01
2023-02-14 15:24 Martin Lang Note Added: 0018709
2023-02-14 15:26 Martin Lang Note Added: 0018710
2023-02-14 15:38 Martin Lang Status confirmed => assigned
2023-03-10 13:50 Martin Lang Note Edited: 0018709
2023-08-03 13:46 Martin Lang Note Edited: 0018710
2023-08-03 13:47 Martin Lang Status assigned => feedback
2023-08-03 13:47 Martin Lang Note Added: 0019787
2023-08-04 08:37 Martin Lang Assigned To Martin Lang =>
2023-08-04 08:37 Martin Lang Status feedback => closed
2023-08-04 08:37 Martin Lang Resolution open => fixed
2023-08-04 08:37 Martin Lang Note Added: 0019817