Usage as a testing tool for correct information model instantiation according to a companion specification
The following documentation describes a use case in which a local server with a companion specification shall be tested by using a locally deployed gateway and a MQTT Broker.
- A local OPC UA Server with an instance model according to a companion specification, which is supported by the Dashboard-OPCUA-Client. You can find an overview of all supported specification here: README
- Admin privileges
- Open port between OPC UA Server, Getaway and MQTT Broker.
- Deploy local MQTT broker.
- Prepare the
configuration.json
and configure MQTT according to your local deployment. - Deploy the client in Standalone or Container mode.
- Subcribe to your MQTT broker with a MQTT client
-
Open your OPC UA server with a generic client and show all values that shall be transmitted
-
Compare the values from the JSON and the values from the server:
- If all values are available and correct within the JSON, the OPC UA Server implementation and the OPC UA instances are correct.
- If some values are not correct or are shown at different places, please check the modelling and the naming of the values within the server.
- ExtensionObjects might create issues and the parsing logic needs to be adapted. Please open an issue pointing to your companion specification, if you run into this.