M-Bus to M-Bus ASCII with PiiGAB M-Bus 900S
By using PiiGAB’s own protocol it is possible to read M-Bus meters even though software/hardware for M-Bus, Modbus or OPC is missing. The values from the M-Bus meters are read as M-Bus ASCII via the PiiGAB M-Bus 900S instead. The answer is then decoded inside the current M-Bus ASCII client. M-Bus ASCII is an open and OS independent protocol.
Plants that are missing M-Bus, Modbus, or an OPC-Client can use the PiiGAB M-Bus 900S as an alternative to read M-Bus meters. The M-Bus driver and the M-Bus ASCII software inside the PiiGAB M-Bus 900S handles all the conversions from the M-Bus meters to M-Bus ASCII. The M-Bus ASCII client is connected to a slave port on the PiiGAB M-Bus 900S via TCP, UDP, RS232 or RS485. The client asks the PiiGAB M-Bus 900S with M-Bus ASCII questions and the gateway answers the questions by in turn asking the M-Bus meters. The remaining slave ports on the PiiGAB M-Bus 900S can still be used for M-Bus, QuickPost and Modbus clients.
The configuration itself from M-Bus to M-Bus ASCII is handled via a reference file created in the PiiGAB M-Bus Explorer software. The configuration of the file is done in the same way the M-Bus OPC server is configured in the PiiGAB M-Bus Explorer. The objects to be read from the M-Bus meters are set as strings and can in that way be interpreted by M-Bus ASCII. The reference file is then uploaded to the web interface in the PiiGAB M-Bus 900S. The master port in the PiiGAB M-Bus 900S is tied together with the reference file in the web interface.
The M-Bus ASCII is implemented in the client according to the document ”Description of M-Bus ASCII protocol” that can be downloaded from our website. The document describes in detail how the M-Bus ASCII protocol should be interpreted. M-Bus ASCII is an open and OS independent protocol.