Italiano
English
- Support
- Technical Support
- Support Forum
- PRODOTTI
- MARCOM
- GATEWAY DLMS / IEC
- Strange readings from GW-DLMS via ModbusTCP
Strange readings from GW-DLMS via ModbusTCP
- FR
-
Topic Author
30 Aug 2018 23:24 #1439
by FR
Strange readings from GW-DLMS via ModbusTCP was created by FR
I'm trying to read values from a Landis+Gyr E650 using a GW-DLMS-485-LG. Unfortunately, I've got difficulties interpreting the values I receive using ModbusTCP. Some seem to be outdated and are never refreshed, some seem to be available at different addresses than the webinterface says. I've checked all values against the counter itself and the webinterface shows the correct values.
These are the (float) values from the top table (column "website" is value from website, column "modbus" is value as I polled it via ModbusTCP)
As far as I can see, those values don't refresh at all (e.g. counter 4x40024) and/or don't fit to the data they should show (e.g. time 4x40016, date 4x40018)
The Integer variants are current, but seem to have an address offset of 2 bytes:
Do you have any idea what's wrong here and how it can be fixed? If you need further information for debugging this I'll be happy to assist.
These are the (float) values from the top table (column "website" is value from website, column "modbus" is value as I polled it via ModbusTCP)
| index | address | obis | website | modbus |
| 0 | 4x40016 | 0.9.1 | 214724 | 246366 |
| 1 | 4x40018 | 0.9.2 | 180830 | 184589 |
| 2 | 4x40020 | 0.0.0 | 381197 | 327680 |
| 3 | 4x40022 | 0.1.0 | 75.00 | 75.03687286376953 |
| 4 | 4x40024 | 1.8.0 | 17929.44 | 17961.990234375 |
| 5 | 4x40026 | 1.8.0* | 17705.99 | 17695.48046875 |
| 6 | 4x40028 | 1.8.1 | 12111.74 | 12156.8603515625 |
| 7 | 4x40030 | 1.8.1* | 11964.86 | 11955.400390625 |
| 8 | 4x40032 | 1.8.2 | 5817.70 | 5805.1298828125 |
| 9 | 4x40034 | 1.8.2* | 5741.13 | 5728.0 |
| 24 | 4x40064 | 5.8.0 | 2759.80 | 2755.2900390625 |
| 25 | 4x40066 | 5.8.0* | 2739.29 | 2741.780029296875 |
| 26 | 4x40068 | 5.8.1 | 1546.89 | 1545.4000244140625 |
| 27 | 4x40070 | 5.8.1* | 1537.40 | 1540.9000244140625 |
| 28 | 4x40072 | 5.8.2 | 1212.90 | 1209.8900146484375 |
| 29 | 4x40074 | 5.8.2* | 1201.89 | 1200.0 |
| 54 | 4x40124 | 8.8.0 | 16.24 | 16.1299991607666 |
| 55 | 4x40126 | 8.8.0* | 15.69 | 15.729999542236328 |
| 56 | 4x40128 | 8.8.1 | 15.23 | 15.242500305175781 |
| 57 | 4x40130 | 8.8.1* | 14.68 | 14.642499923706055 |
| 58 | 4x40132 | 8.8.2 | 1.01 | 1.0099999904632568 |
| 59 | 4x40134 | 8.8.2* | 1.01 | 1.0078125 |
| 64 | 4x40144 | 1.6.1 | 0.70 | 0.7015312314033508 |
| 65 | 4x40146 | 1.6.1* | 0.68 | 0.6796875 |
The Integer variants are current, but seem to have an address offset of 2 bytes:
| index | address | obis | website | value |
| 4x41044 | 17929 | |||
| 0 | 4x41046 | 1.8.0 | 17929 | 17705 |
| 1 | 4x41048 | 1.8.0* | 17705 | 0 |
| 2 | 4x41050 | 2.8.0 | 0 | 0 |
| 3 | 4x41052 | 2.8.0* | 0 | 2759 |
| 4 | 4x41054 | 5.8.0 | 2759 | 2739 |
| 5 | 4x41056 | 5.8.0* | 2739 | 0 |
| 6 | 4x41058 | 6.8.0 | 0 | 0 |
| 7 | 4x41060 | 6.8.0* | 0 | 0 |
| 8 | 4x41062 | 7.8.0 | 0 | 0 |
| 9 | 4x41064 | 7.8.0* | 0 | 16 |
| 10 | 4x41066 | 8.8.0 | 16 | 15 |
| 11 | 4x41068 | 8.8.0* | 15 | 0 |
| 12 | 4x41070 | 3.8.0 | 0 | 0 |
| 13 | 4x41072 | 3.8.0* | 0 | 0 |
| 14 | 4x41074 | 4.8.0 | 0 | 0 |
| 15 | 4x41076 | 4.8.0* | 0 | 0 |
Do you have any idea what's wrong here and how it can be fixed? If you need further information for debugging this I'll be happy to assist.
Reply to FR
- marcom
-
- Offline
31 Aug 2018 14:37 #1447
by marcom
Marcom S.r.l.
via della Metallurgia, 11
37139 - Verona (VR)
Replied by marcom on topic Strange readings from GW-DLMS via ModbusTCP
Dear
usually this is a problem of bad modbus register reading; modbus addresses on the web pages are base 1, so if your modbus master/software is base 0 the correct address for your system is address -1. For example: 4x40016 -1 = 4x40015.
If this not solve, please try to swap words in modbus readings.
Regards
usually this is a problem of bad modbus register reading; modbus addresses on the web pages are base 1, so if your modbus master/software is base 0 the correct address for your system is address -1. For example: 4x40016 -1 = 4x40015.
If this not solve, please try to swap words in modbus readings.
Regards
Marcom S.r.l.
via della Metallurgia, 11
37139 - Verona (VR)