Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve description and example of data storage endpoint #146

Open
roesekoSICKAG opened this issue Oct 14, 2024 · 2 comments
Open

Improve description and example of data storage endpoint #146

roesekoSICKAG opened this issue Oct 14, 2024 · 2 comments
Assignees

Comments

@roesekoSICKAG
Copy link
Collaborator

It is not clear how and if the header information should be into the data storage object. Please improve the description in that regards.

@roesekoSICKAG
Copy link
Collaborator Author

Discussion in WG meeting (2024-11-04):

  • Please remove the iolinkRevision property from the datastorage object since it is useless. (For Datastorage it is mandatory to have IO-Link revision 1.1)
  • Add functionID (see Table G.2 of IO-Link Interface and System Specification Version 1.1.4 June 2024)

@roesekoSICKAG
Copy link
Collaborator Author

roesekoSICKAG commented Nov 27, 2024

Discussion in WG meeting (2024-11-27):

  • the current solution is not very suitable for empty data storage objects
  • furthermore the header information are also part of the base64 content

Decision:

  • remove header from POST request payload -> two schemas for GET and POST
  • change the content of the "empty data storage object" to be a 12 byte long data stream base64 encoded
  • deviceId, vendorId, functionId, checksum should be 0 (basically the same information returned by the SMI)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants