I4.0 extension based on BaSys4IPPS #445
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of the R&D project BaSys4IPPS, an active asset administration shell was created based on the this SDK. The active AAS uses the VDI/VDE 2193 standardized I4.0 language for communication. This communication is carried out via a MQTT broker. The extension published here includes classes to enable the aforementioned communication.
It is possible to establish a connection to a MQTT broker, send and receive I4.0 messages. The so-called I4.0 extension additionally contains classes to create a Java object of an I4.0 message.
An I4.0 message consists of a frame and interactionElements. The interactionElements represent the content of the message. The content can either be a list of AAS submodels or a list of key-value pairs. This is represented by the abstract superclass "Message" through subclasses SubmodelMessage and GenericMessage.
This extension allows an active AAS to be implemented, as well as to send and receive standardized messages.