The M-Bus OPC Server supports “Variable Data Structure” and it handles both primary and secondary addresses. The OPC-Server makes it possible to read object values such as Value, Vib, Unit, Tariff, Storage, Function, Data type, Record etc from M-Bus meters. Information that can be read from “the Header” is for example ID number, Manufacturer, Version, Medium, Access number, Status and Signature.
The OPC-Server is what is called a thin server, meaning that the server and the OPC Interface are completely secluded. The server calls and reads the configuration file as the server starts. This gives benefits like the fact that you can configure another configuration file at the same time as your OPC server communicates with your M-Bus meters. So for example you can work with a backup of the configuration file or another project’s configuration file without the communication being interrupted. If you want the server to use another configuration file instead, you will stop the OPC server and set the preferred configuration file as active.
The figures below illustrate how the OPC server is used in different cases.
