Fluksometer v2b with Landis + Gyr E350 DSMR 4

by Richard6666 on

Fluksometer v2b with Landis + Gyr E350 DSMR 4

Who has this setup working?

‹ Flukso 244 issues How to install the current clamp? ›
vringer's picture
vringer |

Last week I got my FLM02B.
I connected the FLM with an ethernetcable to the local network. This seems te work fime.
I also connected the FLM with the P1 of a Landis Gyr+ E350 meter.

Now I get only empty telegrams from the decoder ("Jan 17 12:12:01 flukso-35f4bf daemon.err parsed[1772]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram").

I tried to find out what I am doing wrong, but couldn't find it in this forum. The link of GEBHARDM is not concerning this problem.

Has anybody a solution or can anybody help?

bellyf's picture
bellyf |

Have you looked at this posting: Empty smart meter P1 telegrams

I had similar problems although with a different type Landis+Gyr smart meter. It may help you pinpoint your problem.

Success

vringer's picture
vringer |

Thanks for the suggestions.
- I have checked the wiring from the P1, that is ok.
- I did a full reset (>60 s on the toggle button)
- I did a restart from the FLM command line followed by a fp1
- But I still get less than the garbled telegram text after cat /dev/ttyS0. Each few seconds "▒" is added.

root@flukso-35f4bf:~# /etc/init.d/flukso restart
Daemon returned 0 as return value.
Daemon returned 0 as return value.
Daemon returned 0 as return value.
Daemon returned 0 as return value.
Daemon returned 0 as return value.
Daemon returned 0 as return value.
root@flukso-35f4bf:~# fp1
root@flukso-35f4bf:~#
root@flukso-35f4bf:~# cat /dev/ttyS0
▒▒▒▒▒

vringer's picture
vringer |

Still no solution. FLM is producing each hour tis hearbeat and only empty telegrams from the smart meter (see syslog)
Anybody a solution for me? Now I have spend a lot of money on a FLM with I cannot do anything.

Kees.

Jan 22 19:12:04 flukso-35f4bf user.info heartbeat[19147]: POST https://api.flukso.net/device/35f4bf9c7dced0c37f34875f0266c6dc: 200
Jan 22 19:14:23 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:15:01 flukso-35f4bf cron.info crond[575]: crond: USER root pid 19173 cmd /usr/bin/fcheck
Jan 22 19:17:22 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:20:02 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:22:44 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:25:28 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:28:24 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:30:01 flukso-35f4bf cron.info crond[575]: crond: USER root pid 19212 cmd /usr/bin/fcheck
Jan 22 19:31:04 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:33:57 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:36:46 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:39:44 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:42:33 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:45:01 flukso-35f4bf cron.info crond[575]: crond: USER root pid 19251 cmd /usr/bin/fcheck
Jan 22 19:45:30 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:48:24 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:51:09 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:53:46 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:56:32 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 19:59:36 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 20:00:01 flukso-35f4bf cron.info crond[575]: crond: USER root pid 19290 cmd /usr/bin/fcheck
Jan 22 20:02:38 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 20:05:27 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 20:08:08 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 20:10:48 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram
Jan 22 20:12:01 flukso-35f4bf cron.info crond[575]: crond: USER root pid 19323 cmd /usr/bin/heartbeat 0
Jan 22 20:12:03 flukso-35f4bf user.info heartbeat[19324]: POST https://api.flukso.net/device/35f4bf9c7dced0c37f34875f0266c6dc: 200
Jan 22 20:13:39 flukso-35f4bf daemon.err parsed[999]: /usr/sbin/parsed.lua:131: decoder returned an empty telegram

vringer's picture
vringer |

Thanks GEBHARDM. This helped. As mentioned in https://www.flukso.net/content/no-reading-p1-kamstrup
I forced the FLM to work with the DSMR 2.2 standard.

root@flukso-e5009c:~$ uci set flukso.main.dsmr=2.2
root@flukso-e5009c:~$ uci commit
root@flukso-e5009c:~$ /etc/init.d/flukso restart

Now I get good readings.
The Landis + Gyr E350 is no DSMR 4.0 meter??