aasx-Packages not usable by Eclipse-BaSyx and AASX-Server

[efiege]

Hello,

I am trying to get he generated aasx-packages to work with the latest AASX-Server and Eclipse-BaSyx 1.4.0, but they seem not to be loadable.

Are they even supposed to be used with those servers? Is there any documentation I am missing?

It would be great, if someone could give me a pointer of how to use them.

Thanks in advance!

[jacewski-bosch]

There might be a mismatch between AASX versions implemented by BaSyx (aasx 2.01) and the generated artifacts (aasx 3.0.0) @tom-rm-meyer-ISST can you help?

[tom-rm-meyer-ISST]

I checked on the implemented specification used to generate the artifacts.

• According to this documentation, the SAMM CLI should generate the aasx package according to specification 3.0.0 RC1. According to @bs-jokri, the cli tool generating the artifacts (such as the aasx package) should generate the aasx packages according to specifciation version 3.0.0 (no release candidate).
• According to the Basyx repository, the Basyx version 1 is compliant to AAS part 1 specification version 2.0.1.

The Basyx repository mentions a branch implementing the specification version 3.0.0. Please do check, if it still does not work using this branch. If it still does not work,

• the error could exist on both sides.
• please comment here which artefact you used. (we could then check the used specification again)

Please note that the specifications in version 3.0.0 are not differentiated in parts anymore. They are further separated into multiple documents and are now provided by the International Digital Twin Association (IDTA).

I raised an issue for the SAMM-SDK so that they can look into their documentation to mention which specification version they are supporting.

[efiege]

Thanks for the responses!

As @tom-rm-meyer-ISST said, there is currently not a released version of basyx, which supports AAS version 3: https://wiki.eclipse.org/BaSyx_/_Releases_and_Features#Java_Release_2.0

[tom-rm-meyer-ISST]

@efiege, I had a discussion with my IOSB collegues regarding the FA3ST Service.

The Specification 3.0 is not yet fully implemented. Mainly the OPC UA parts are open. The serialization, the datamodel and nearly everything of the API should be done. According to my colleagues the AAS Package Explorer branch (either this branch or or maybe this release) should work with their FA3ST Service branch. Therefore: If you don't rely on OPC UA, you might already use it.

@bs-jokri, maybe this information is also interesting for you.