The assets2036net library and package supports .NET developers in participating in the assets2036 MQTT-based communication. It depends on M2MqttDotNetCore for MQTT communication.
For a very basic usage see take a look into the CLI project SimplePropertyAndOperation. Herein an asset is created and equipped with some properties and operations. Then an asset proxy is created which reads the properties and calls the asset's operation.
The used submodel descriptions are
Those submodels are very simple / basic and offer only simple datatypes in properties and operation parameters. In the unit tests project you will find a sufficient set of all imaginable use cases, parameter types, return types.
The focus in assets2036 is simplicity and leanness - this also aplies to the librares. This is why in some places one might miss a more clean separation of concerns in the implementation.
- There is only one set of classes for Submodel and the submodel elements (Properties, Events, Operations) in the library. They are used for the serialization and deserialization of the JSON submodel descriptions (JSON model files read from submodel repository) as well as for the access to the submodel elements at runtime. This might lead to some confusion and sometimes made it impossible to strictly hide unneccessary aspects of the API from the developer.
- log4net 2.0.13 Apache-2.0
- MQTTNet 4.3.2.930 MIT
- Microsoft.NET.Test.Sdk 17.0.0 MIT
- xunit 2.4.1 MIT
- xunit.runner.visualstudio 2.4.3 MIT
- log4net 2.0.13 Apache-2.0
Apache-2.0 License
Thanks to Daniel Ewert for the inspiration, conceptual work and preliminary python library.