No values reported

[jonesPD]

Hi Niels,
I'm trying to masquerade my ESMR5 smart meter as a Import/Export meter. SetApp shows a working connection ('OK') but no values are indicated, and I can't read them back through the TCP_MODBUS interface as well (which I also use to read out the production).

My implementation is as follows: I receive an MQTT message from the smart meter (actually via Beeclear), this is parsed by a Node-Red flow to an MQTT message (the flow was largely already there):

{"Vmains":233,"Imains":2.1,"Pin":404.7,"Pin_min":401,"Pin_max":411,"Pout":0,"Pout_min":0,"Pout_max":0,"Ein":0.0011298999,"Eout":0,"sumEin":4785344,"sumEout":3958941,"Po":404.7,"En":0.0011298999,"timestamp":"1614979040701"}

Some of these values are used in the return DICT from the 'values' call. I don't get any errors running the scripts.
All this is running on a Raspberry with an RS485 connection to the SolarEdge inverter.

What I am doing wrong?

jonesPD_metering_proxy_0305.zip

[jonesPD]

dump_all_modbus_registers_export+import2.txt

Wondering if there is an Endian issue, since the serial number shows up wrong. Conf file is at default setting 987654, reading back via Modbus shows 18176...

[nmakel]

Looks like I had a typo in the configuration examples. serial_numer instead of serial_number. Fix that and see if the serial number shows up correctly.

I will have a longer look at your code tomorrow. My first thought is that the number of values you provide might be less than what is required. Have you tried matching the number of fields to that of the sdm120 example? Even filling them with dummy data can give you an idea of whether the entire pipeline is working or not...

[jonesPD]

Hi Niels, Thanks for your reply. And thanks for offering to have a look at the code, that’s really great. I’ve corrected the typo, but no difference. In fact, for some reason the serial number now reports as 0 (zero). I’ve also added (realistic dummy) numbers for the field I hadn’t used yet (following your sdm120 example), but also this doesn’t seem to make a difference. I’ll tinker around with other values to see if that makes a difference. Do the values provided in the DICT need to be a specific type? (float/int/…) Do the values provided in the DICT need to comply to a specific sign convention? I use negative numbers for power when it is delivered to the grid, positive when drawing from it. How is ‘demand power’ defined? Related question in a different direction, when configuring in SetApp I didn’t know what to set the CT to, so I just left it with the proposed default (5 I believe). Do I need to use that number anywhere? Thanks for your help.

[nmakel]

I’ve corrected the typo, but no difference. In fact, for some reason the serial number now reports as 0 (zero). I’ve also added (realistic dummy) numbers for the field I hadn’t used yet (following your sdm120 example), but also this doesn’t seem to make a difference.

That's weird.

Can you set your config to log_level = DEBUG? Here are the setValues that happen in my situation:

block_1601:

[1234, 0, 5, 5, 5, 5, 0, 0, 0, 15, 1, 10000, 10000, 10000, 64536, 64536, 64536, 1500, 120, 0, 0, 20000, 0]

block_1651:

[0, 2, 4, 0, 0, 5]

block_1701:

[4614, 15, 0, 0, 0, 0, 0, 25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

block_1001:

[27441, 17880, 22036, 17761, 27441, 17880, 22036, 17761, 62259, 50059, 62259, 50059, 0, 0, 0, 0, 58982, 17260, 58982, 17260, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 52429, 16967]

block_1101:

[27441, 17880, 0, 0, 0, 0, 22036, 17761, 0, 0, 0, 0, 32846, 17743, 32846, 17743, 32846, 17743, 0, 0, 0, 0, 24946, 17941, 24946, 17941, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 13705, 48852, 13705, 48852, 0, 0, 0, 0, 42598, 50201, 42598, 50201, 0, 0, 0, 0, 56372, 17448, 56372, 17448, 0, 0, 0, 0, 12059, 16453, 0, 0, 0, 0, 26152, 17480, 0, 0, 13366, 17745, 0, 0, 26152, 17480, 0, 0, 0, 0]

I’ll tinker around with other values to see if that makes a difference. Do the values provided in the DICT need to be a specific type? (float/int/…) Do the values provided in the DICT need to comply to a specific sign convention? I use negative numbers for power when it is delivered to the grid, positive when drawing from it. How is ‘demand power’ defined?

A working example is worth a thousand words, here are my meter values this morning with +-280W being fed back into the grid:

{
    'voltage': 236.89999389648438,
    'current': 3.0810000896453857,
    'power_active': -279.8999938964844,
    'power_apparent': 675.440673828125,
    'power_reactive': -614.5999755859375,
    'power_factor': -0.41447094082832336,
    'phase_angle': 0.0,
    'frequency': 49.95000076293945,
    'import_energy_active': 3605.3798828125,
    'export_energy_active': 3320.01904296875,
    'import_energy_reactive': 0.09000000357627869,
    'export_energy_reactive': 9560.271484375,
    'total_demand_power_active': 801.59619140625,
    'maximum_total_demand_power_active': 3347.26318359375,
    'import_demand_power_active': 122.04130554199219,
    'maximum_import_demand_power_active': 3347.26318359375,
    'export_demand_power_active': 679.5548706054688,
    'maximum_export_demand_power_active': 2310.420654296875,
    'total_demand_current': 4.683725833892822,
    'maximum_total_demand_current': 14.968546867370605,
    'total_energy_active': 6925.39892578125,
    'total_energy_reactive': 9560.361328125,
    'energy_active': 6925.39892578125,
    'import_energy_active': 3605.3798828125,
    'power_active': -279.8999938964844,
    'p1_power_active': -279.8999938964844,
    'voltage_ln': 236.89999389648438,
    'p1n_voltage': 236.89999389648438,
    'frequency': 49.95000076293945,
    'p1_energy_active': 6925.39892578125,
    'p1_import_energy_active': 3605.3798828125,
    'export_energy_active': 3320.01904296875,
    'p1_export_energy_active': 3320.01904296875,
    'energy_reactive': 9560.361328125,
    'p1_energy_reactive': 9560.361328125,
    'power_factor': -0.41447094082832336,
    'p1_power_factor': -0.41447094082832336,
    'power_reactive': -614.5999755859375,
    'p1_power_reactive': -614.5999755859375,
    'power_apparent': 675.440673828125,
    'p1_power_apparent': 675.440673828125,
    'p1_current': 3.0810000896453857,
    'demand_power_active': 801.59619140625,
    'maximum_demand_power_active': 3347.26318359375,
    'p1_demand_power_active': 801.59619140625
}

Related question in a different direction, when configuring in SetApp I didn’t know what to set the CT to, so I just left it with the proposed default (5 I believe). Do I need to use that number anywhere?

The current transformer (CT) value has no discernible impact as far as I'm aware. I have mine set to 50A (in SetApp), in case some sort of output limiting happens based on this value.

If you suspect an endianness issue, you can play around with the byteorder and wordorder parameters on line 161, 186 and 195 of your semp-rtu.py file.

[jonesPD]

Thanks for responding. Using the meter data you provided, I’ve checked the block setValues and they match up. Attached is zip are two log files. One using your meterdata (non-changing message), and one using my own livedata. Also there are a few setapp screenshots, all showing an ‘ok’ connection to the meter, but with varying serial number (for some reason, I didn’t play with it). Hope you have suggestion where else to look. Thanks for your time.

[nmakel]

Attached is zip are two log files.

I think you forgot the attachment.

[jonesPD]

Mmmm…my outlook shows they’ve been included. Let’s just try again. Did you get the pictures?

[nmakel]

Mmmm…my outlook shows they’ve been included. Let’s just try again. Did you get the pictures?

No. Be aware these replies are being posted to github, including your actual e-mail address.

[jonesPD]

Indeed. Removed that.
Did you get the zip file? The images are just to show setapp indicates the connection to meter is ok although no values are being shown (na)

[nmakel]

Did you get the zip file?

The first zip file, yeah. After that, nothing.

[jonesPD]

jonesPD_metering_proxy_0306-2.zip

[nmakel]

Can you provide a bit more details about your installation? What inverter do you have, are there any other devices connected to the RS485 ports? Is the meter configured as described in the readme?

Looking at your log -- in which you provide the values I gave you -- the inverter looks to be doing its thing. Requesting values, and the responses look right.

[jonesPD]

I have a SolarEdge SE5000H inverter (no display), the 'meter' is the only thing connected to the RS485 bus. I've toggled the RS485-1 switch inside the inverter, and also added the termination resistor on the RS485Pi board mounted on top of the RPi 3. I've followed your configuration instructions for the inverter. The connection only seems to work at 9600baud.
Attached is the output of the '--json' switch of your solaredge_modbus script - obtained over TCP/IP.
dump_all_modbus_registers3.txt

As you can see in that file, serial-number is not listed, nor is any measurement. On the otherhand, in the two SetApp screen shots, the meter-version and serial number are shown correctly.

[nmakel]

As you can see in that file, serial-number is not listed, nor is any measurement. On the otherhand, in the two SetApp screen shots, the meter-version and serial number are shown correctly.

This actually looks pretty good. The meter is registering properly. Were the screenshots taken when you were supplying values through mqtt, or the dict I gave you?

I had similar issues with the Modbus TCP output -- I suspect the serial number, among other values, are not updated real time. Ignore that, and focus on getting values to show up in the SetApp interface. NA energy makes me suspect invalid or empty variables in your values dict.

[jonesPD]

It was when supplying live data through MQTT. Unfortunately switching back to your dict does not make it show them. It should show up more or less instantaneously I suppose?
I spend most of saturday evening replacing the RS485 cable, to ensure it is how it should be (CAT5e cable now), but alas, that didn't make any difference. I've also cut out all of my own code, making a special metertype that always returns your dict. After a night long sending your dict, SetApp still reports NA.
jonesPD_metering_proxy_0307.zip

Which pymodbus version are you on? Which inverter CPU version are you on?
Other suggestions?