Heatmeter M-Bus issue

Emoncms
1

Hi. Complete newbie here so any input appreciated.
I have linked my Sontex supercal 531 bus output to a Mbus to USB connecter and connected to a raspberry pi running with the preloaded SD card. When I power on, it seems to get readings from the heatmeter as I get the following inputs:

image
image1930×916 83.2 KB

However, after that, I don’t seem to get any updates. When I look at the log in emonhub, it just shows:

image
image1930×916 257 KB

I have checked the baud rate on the meter and the address, which show as 2400 and 0 respectively on the heatmeter display. I have added the following to the config from others who have used this meter:

[[MBUS]]
    Type = EmonHubMBUSInterfacer
    [[[init_settings]]]
        device = /dev/ttyUSB0
        baud = 2400
    [[[runtimesettings]]]
        pubchannels = ToEmonCMS,
        read_interval = 10
        validate_checksum = False
        nodename = MBUS
        [[[[meters]]]]
            [[[[[heatmeter]]]]]
                address = 0
                type = sontex531

Would appreciate any direction to look to get this working ok. I will be adding in an SDM120 electric meter later today when my electrician installs it, so I want to connect that too.

Thanks for any direction

2

My config settings are …

[[SDM120]]
    Type = EmonHubMinimalModbusInterfacer
    [[[init_settings]]]
        device = /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0
        baud = 9600
        parity = none
        datatype = float
    [[[runtimesettings]]]
        pubchannels = ToEmonCMS,
        read_interval = 10
        nodename = modbus
        [[[[meters]]]]
            [[[[[sdm120]]]]]
                address = 1
                registers = 0, 6, 12, 18, 30, 70, 72, 74, 76, 342
                names = V, I, P, VA, PF, FR, EI, EE, RI, TP
                precision = 2, 3, 1, 1, 3, 3, 3, 3, 3, 3

[[MBUS]]
    Type = EmonHubMBUSInterfacer
    [[[init_settings]]]
        device = /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0
        baud = 2400
    [[[runtimesettings]]]
        pubchannels = ToEmonCMS,
        read_interval = 10
        validate_checksum = False
        nodename = mbus
        [[[[meters]]]]
            [[[[[sontex]]]]]
                address = 0
                type = standard

I have an SDM120 and Sontex 749.

One of the devices needs the ‘page’ moving so you get the correct data sent - it’s documented somewhere but I can’t find it or remember which device it applies to!

1 Like
3

Found it - https://docs.openenergymonitor.org/emonhub/emonhub-interfacers.html#mbus-reader-for-electric-and-heat-meters

Implies the 531 doesn’t need this.

1 Like
4

Just to check, is it M-Bus or Modbus - they are not the same!

There are threads elsewhere re the USB adapter and I think some have been troublesome. @glyn.hudson is I think the right person for this.

Can I also ask that you paste log output as pre-formatted text (Ctl-E) and not screen shots.

On the log, if you restart emonhub and post the initial output where the interfacer is setup, that will help.

5

Thanks for the replies.
The SDM120 module is working ok. Still no joy on the Sontex.
I had assumed it is only Mbus on the Supercal meter. It says M-bus on the terminals, hadn’t thought it could be Modbus?

Could be the adapter! Is there a way to check if it is working?

6

I measured across the terminals on the adapter - it shows 28v. Is that normal?

7

I had real problems connecting mbus but Trystan sorted me out. Use their mbus reader worked perfectly with my sontex449.

8

That is fine, not everyone understands there is a difference :slight_smile:

Yes I think OEM have found that some adapters work better than others.

9

I have solved it. Probably an amateur error. But had to change the config to USB1 for the mbus adapter. It’s been working all night by the looks of it!

[[MBUS]]
    Type = EmonHubMBUSInterfacer
    [[[init_settings]]]
        device = /dev/ttyUSB1

Thanks for everyone’s input!

10

Yes it does tend to work when you are looking in the right place for the data :rofl: .

Glad it’s sorted.

11

Yep! I said it was amateur hour :grinning:

1 Like
12

That’s one reason to use a device path that won’t change as /dev/ttyUSBnn potentially will.

2 Likes