Our user manjey73 develops M-Bus driver. This is a complex protocol, and manjey73 needs additional info to implement different use-cases. Who has such information, please share it with manjey73.
1. Device model and manual.
2. Request and response examples.
3. Communication log. There is a useful application PiiGAB M-Bus Wizard to get log.
Thanks for the links. But the problem I have is not with the description of the Protocol, and with real data from the devices. The Protocol gives a greater freedom of choice of data transmission, which of them will choose the manufacturer only knows. I would like to see different types of data transmission from different manufacturers. At the moment I have only two devices and both transmit Variable data Structure.
At the moment I have implemented the processing of Variable Data Structure in the response.
There is also a problem with scanning devices, not all manufacturers lay this functionality. For example, Wesser Heat Meter does not have this functionality and does not even have an address provided by the Protocol. It has only ID and only it can be used to run a survey.
Hope just for those who have devices with m-Bus. At least it is planned to make free drivers that work with a specific device on the logs of requests and responses of the device. It is not difficult, as little changes there.