M-Bus problem solved!
Hi all I have a adfweb device (HD67024-B2-20) that worked fine to be a bridge to the M-Bus physical interface.
Using a USB (virtual com port) to M-Bus then just search for you device, and add test points from the list that the divese provides. All worked fine until I updated the Mango from 2.4 to 2.5 .
Now the start of Mango hangs and will not run !
Revert back and use backup was the only medicine.
I am now running a MangoES and the same thing there.
So right now I do not dare to bring in the source for the M-bus equipment.
It is now updated to new M-bus drivers but the search does not start at all ! It just states "error" and nothing happens.
I used to have Rxtx driver added, but I am using the build in support now could this be the root cause?
JoelHaggar last edited by
We've recently acquired some M-Bus equipment which isn't easy as it's not available in the US. We'll be doing some testing on this in the near future. Thanks.
Try removing the OpenV data source. I found that it has an outdated MBus library in it. I'll update that datasource but for now this should get you going.
The latest version of the MBus Data Source should not require RxTx as I've ported it to JSSC for Mango.
So neither M-Bus, Modbus or 1-Wire will require rxtx support in 2.7.0 ?
Could it be that rxtx even disrupt the functions?
1-Wire will still require RxTx but M-Bus and Modbus do not. RxTx shouldn't cause any problems. The problem was that there were 2 Mbus4J libraries with different versions running in Mango.
The MBus data source uses version 0.1.5
The OpenV data source was using an older version and this was causing the problem since it was being loaded into Mango first and causing the MBus data source code to break.
So when I now running the update to 2.7.2
I could expect this to be gone?
By the way M-bus worked with your tip with OpenV removal.!
If you upgrade to 2.7.2 you should be able to have both OpenV and M-Bus data sources installed with no conflicts.
Doing the update as we speak!