Skip to content

Design Considerations

Matthias Dornaus edited this page May 2, 2024 · 8 revisions

This pages collects design consideration fro the new OPCUA Mqtt Gateway under several Aspects.

State of Current Developement

This section contains the capabilities of the current OPC UA Cloudpublisher.

Pubish Nodes with fixed NodeId

It is possible to publish Nodes identified by their NodeId.

Save/Load NodeIds for Publishing

It is possible to save/load a configuration of NodeIds that are to published to Mqtt.

Web UI for configuration

The OPC UA Cloud Publisher allready delivers a simple Web-Interface for configuration.

Online Connection

Missing Features (Missing in current State)

This section contains Features that might be interresting to have in a MqttGateway.

Missing possibility to call OPC UA Methods

In future it might be beneficial to implement a protocol that enables the call of OPC UA Methods and return their ouputarguments as well as the status of the call. It is necessary to implement JobControl and other Method-orientated specifications.

Software Architecture

Usability

Maintainability

Implementation effort

Politics

Bugs and Instabilities

This Section deals with Bugs and instabillities.

Invalid MQtt Adress leads to crash of the program

This is anoying because the mqtt Adress is stored some where, so it is difficult to change it back.

Subscribuing to all variables via command leads to error.

Clone this wiki locally