search

volkszaehler / mbmd

ModBus Measurement Daemon - simple reading of data from ModBus meters and grid inverters
BSD 3-Clause "New" or "Revised" License
241 stars 84 forks source link

Bad readings since midnight 28/12 #332

Closed speeskeek closed 10 months ago

speeskeek commented 11 months ago

hello all

first thank you for the good work. I'm using a few months now (since january 2023) an Orno 3-phase reader. I'm then grabbin the info from the api and visualizing it in metern (great thin, where I also have my solar panels an my gas readings).

my link

there was a problem when my electric car was charging (8kW) the readings didn't come trough very well. i think the Orno can't handle this power OR the communication-cable to my USB is getting interference.

anyways. very happy with it but since midnight 28/12 the readings over modbut are all wrong 😢 when I check the display of the Orno - these look okay - but over modbus it is shit. All values are 236. So 236V, 236A, 236 cosinus 236Hz 🤣 so I guess that is wrong

what can I do ? or is the Orno defective? I tried the last version of MBMD but, problem stays.

root@Z800:~# mbmd -v run -a /dev/netstroom -d ORNO3P:1 --comset 8E1 2023/12/29 09:35:03 mbmd 0.13 (fa6b574) 2023/12/29 09:35:03 config: creating RTU connection for /dev/netstroom (9600baud, 8E1) 2023/12/29 09:35:03 config: declared device ORNO3p:1.0 2023/12/29 09:35:03 httpd: starting api at 0.0.0.0:8080 2023/12/29 09:35:03 initialized device ORNO3p1.1: {ORNO3p ORNO3p ORNO WE-516 & WE-517 0} 2023/12/29 09:35:05 device ORNO3p1.1 L1: 0.0V 0.0A 0.0W 0.0cos | L2: 0.0V 0.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 0.0A 0.0W 0.0cos | L2: 0.0V 0.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 0.0cos | L2: 0.0V 0.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 0.0V 0.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 0.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 236.0A 0.0W 0.0cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 236.0A 0.0W 236.00cos | L3: 0.0V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 236.0A 0.0W 236.00cos | L3: 236V 0.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 236.0A 0.0W 236.00cos | L3: 236V 236.0A 0.0W 0.0cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 0.0W 236.00cos | L2: 236V 236.0A 0.0W 236.00cos | L3: 236V 236.0A 0.0W 236.00cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 0.0W 236.00cos | L3: 236V 236.0A 0.0W 236.00cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 0.0W 236.00cos | 236Hz 2023/12/29 09:35:05 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz 2023/12/29 09:35:06 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz 2023/12/29 09:35:06 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz 2023/12/29 09:35:06 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz 2023/12/29 09:35:06 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz 2023/12/29 09:35:06 device ORNO3p1.1 L1: 236V 236.0A 236000W 236.00cos | L2: 236V 236.0A 236000W 236.00cos | L3: 236V 236.0A 236000W 236.00cos | 236Hz

speeskeek commented 11 months ago

when I was fiddeling around a bit more - I noticed too that I have (in the CSV-files) two readings.

00:00,35748.900,10,70129887,,,, 00:00,35748.900,10,70129887,,,, 00:05,35748.960,10,70129887,,,, 00:05,35748.960,10,70129887,,,, 00:10,35748.980,10,70129887,,,, 00:10,35748.980,10,70129887,,,, 00:15,35749.000,10,70129887,,,, 00:15,35749.000,10,70129887,,,, 00:20,35749.000,10,70129887,,,, 00:20,35749.000,10,70129887,,,, 00:25,35749.000,10,70129887,,,, 00:25,35749.000,10,70129887,,,, 00:30,35749.000,10,70129887,,,

this is messing up the graphs. I'm manually cleaning up. Maybe there is a dboule instance running?

speeskeek commented 11 months ago

yup .. multiple instances messed up.

but the problem of the modbus reading of the Orno is still there.

speeskeek commented 10 months ago

I made a connection with the software of the Orno website and this is working fine. Same usb-rs485 adapter - didn’t change the wiring …

IMG_3516 IMG_3515 IMG_3514 IMG_3513

speeskeek commented 10 months ago

So this is proof the hardware is okay … so there must be something wrong with mbmd suddnly?

speeskeek commented 10 months ago

Okay - fixed 🙄 Plugged it back in (other usb maybe) and everything works 🙄