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. Node
  3. Inhemeter

Inhemeter

By Frank G , 7 October, 2026
Forums
DLMSDirector

Hi Mikko,
I am having a connection issue with this meter (Identification: IHM5\2Inhe Meder). The SNRM frame (03 03) is correct and works fine in other software.
The communication log reveals the exact problem during the IEC Mode E handshake:
1. Gurux sends the baud rate change command: 06 32 35 32 0D 0A
2. Gurux closes and reopens the COM port to change settings from 7E1 to 8N1 (takes ~110ms).
3. The Bug: After reopening the port, Gurux waits exactly 1000ms before sending the SNRM request:
• Log: 13:40:35.502 Info Open
• Log: 13:40:36.510 Sent 7E A0 07 03 03 93 8C 11 7E
4. This 1-second delay is too long for the meter. It times out and returns to sleep mode.
InactivityTimeout and FrameDelay are already set to 0.
Is there a hidden parameter or a way to eliminate this hardcoded 1000ms delay after the port reopen, so the SNRM can be sent immediately?
Best regards,
Frank
here the Log:
13:40:31 01:40:31.378 Info Opening
13:40:31 01:40:31.378 Info Einstellungen für die serielle Schnittstelle: Portname: COM19 Baudrate: 300 Daten Bits: 7 Parität: Even Stopp-Bits: One Ablaufsteuerung: None Eop: None
13:40:31 01:40:31.388 Info Open
13:40:32 01:40:32.399 Sent 2F 3F 21 0D 0A
13:40:32 01:40:32.736 Received 2F
13:40:32 01:40:32.784 Received 2F
13:40:32 01:40:32.816 Received 49
13:40:32 01:40:32.848 Received 48
13:40:32 01:40:32.880 Received 4D
13:40:32 01:40:32.912 Received 35
13:40:32 01:40:32.944 Received 5C
13:40:32 01:40:32.976 Received 32
13:40:33 01:40:33.008 Received 49
13:40:33 01:40:33.041 Received 6E
13:40:33 01:40:33.072 Received 68
13:40:33 01:40:33.105 Received 65
13:40:33 01:40:33.137 Received 20
13:40:33 01:40:33.184 Received 4D
13:40:33 01:40:33.216 Received 65
13:40:33 01:40:33.248 Received 74
13:40:33 01:40:33.280 Received 65
13:40:33 01:40:33.312 Received 72
13:40:33 01:40:33.344 Received 0D
13:40:33 01:40:33.344 Sent 06 32 35 32 0D 0A
13:40:35 01:40:35.358 Info Closing
13:40:35 01:40:35.486 Info Closed
13:40:35 01:40:35.486 Info Opening
13:40:35 01:40:35.486 Info Einstellungen für die serielle Schnittstelle: Portname: COM19 Baudrate: 9600 Daten Bits: 8 Parität: None Stopp-Bits: One Ablaufsteuerung: None Eop: None
13:40:35 01:40:35.502 Info Open
13:40:36 Send SNRM request.
TX: 7E A0 07 03 03 93 8C 11 7E
13:40:36 01:40:36.510 Sent 7E A0 07 03 03 93 8C 11 7E
13:40:41 Failed to receive reply from the device in given time.
13:40:41 Send Disconnect request.
TX: 7E A0 07 03 03 53 80 D7 7E
13:40:41 01:40:41.519 Sent 7E A0 07 03 03 53 80 D7 7E
13:40:46 Failed to receive reply from the device in given time.
13:40:46 01:40:46.531 Sent 01 42 30 03 0D 0A

Profile picture for user Kurumi

Kurumi

16 hours 45 min ago

Hi, This one second works…

Hi,

This one second works with most meters, and it's not currently configurable. The new version is under construction, but it's essentially a new product, so I can't say exactly when it will be released.

In the meantime, you can change this in the source code.

Regards,
Mikko

  • Log in or register to post comments
  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 09/22/2026 - 14:02
    Gurux.DLMS.Net 9.0.2609.2201
  • Mon, 09/21/2026 - 10:18
    Gurux.DLMS.Net 9.0.2609.2101
  • Wed, 08/26/2026 - 09:04
    Gurux.DLMS.Python 1.0.203
  • Mon, 08/17/2026 - 11:28
    Gurux.DLMS.Python 1.0.202
  • Mon, 08/17/2026 - 09:47
    gurux.dlms.cpp 9.0.2608.1701

New forum topics

  • Inhemeter
  • DLMS Server - Profile Generic - can't add too many items to profile generic capture object - how to set maximum profile entries
  • HDLC Frames sequencing
  • Security vulnerability report — request for a private contact (GuruxDLMS.c / ANSI C)
  • Topic: Insufficient Memory Error When Reading Class 7 Profile Generic Objects
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin