Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Forums
  3. Issue With Protocol 'EMH Metering GmbH' With Longer Time Periods

Issue with protocol 'EMH metering GmbH' with longer time periods

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By JBouman , 21 March, 2019
Forums
Gurux.DLMS

Hello,

We have issue with protocol EMH metering GmbH in the DLMS (Connection: TCP)

Please follow my explanation.
We have a strange problem when we read the Profile. In most of the cases it works good. We get the data with no problems. But sometimes when we choose a longer period, for example one day it gives problems. For example we get good results when we read the profile for 12-march- 2019 00:00 till 12-march- 2019 14:15 and get good results when we read the profile for 12-march- 2019 12:00 till 12-march- 2019 23:55. But we don’t get any results when we ask for the period 12-march- 2019 00:00 till 12-march- 2019 14:30.

This call doesn’t work in the C# GURUX DLMS code we use but also doesn’t work in de GXDLMSDirector. In both situations the same problem arises.

In the C# code, in the function GetHdlcData the ‘Gurux.DLMS.GXDLMSException: Invalid data format.’ Is thrown.

There are multiple frames received, but one of the frames gives a problem. The received frame is strange, because there is a 7E not at the end or beginning of the frame.

RECEIVED FRAME:
7E A8 8C 41 00 02 6A 55 3E 53 D8 01 02 08 09 0C 07 E3 03 0C 02 0E 00 00 FF 00 00 00 06 00 80 00 00 06 00 27 DD 0A 06 00 00 00 00 06 00 04 A7 D3 06 00 00 00 A2 06 00 00 00 01 06 00 00 00 01 02 08 09 0C 07 E3 03 0C 02 0E 0F 00 FF 00 00 00 06 00 80 00 00 06 00 27 DE 41 06 00 00 00 00 06 00 04 A7 F5 06 00 00 00 A2 06 00 00 00 01 06 00 00 00 01 02 08 09 0C 07 E3 03 0C 02 0E 1E 00 FF 00 00 00 06 00 80 00 00 06 00 27 DF 7E A0 0A 00 02 6A 55 41 93 06 07 7E

Multiple different meters seem to have this problem. Thus it is not only one meter.

Is there anyone who could help with such issue? I can't find anything in documentation.
For any help, great thanks in advance,

JBouman

Profile picture for user Kurumi

Kurumi

7 years 2 months ago

Hi,

Hi,

I can't say the reason without I have all the data what meter sends. Can you send GXDLMSDirector log from failed read to me by email? You can get my email address here:
https://www.gurux.fi/AboutUs

BR,

Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 06/09/2026 - 11:16
    gurux.dlms.java 4.0.95
  • Tue, 06/09/2026 - 10:03
    Gurux.DLMS.Python 1.0.199
  • Mon, 06/08/2026 - 13:39
    gurux.dlms.cpp 9.0.2606.0801
  • Mon, 06/01/2026 - 10:15
    gurux.dlms.cpp 9.0.2606.0101
  • Thu, 05/28/2026 - 16:06
    gurux.dlms.java 4.0.94

New forum topics

  • Error reading L&G Meter
  • Pass a TCP Client to GXNet
  • Australian EDMI Mk10D (Essential Energy area)
  • Strange mix of data notificiation vs get response
  • DLMS Connection
More

Who's new

  • Tuanhgg
  • Adel
  • charnon
  • Paddles
  • Miguel Ángel
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin