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. Hexing HXE115-KP

Hexing HXE115-KP

By dbrandy , 3 August, 2025
Forums
DLMSDirector

Good afternoon Kurumi,

I'm trying to connect to Hexing HXE115-KP with Gurux GXDLMSDirector Version 9.0.2506.2601.

The IEC62056-21 protocol handshake is executed successfully.

Hereunder the communication Log:
17:17:11 Send SNRM request.
TX: 7E A0 07 03 21 93 0F 01 7E
17:17:12
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 00 C8 06 02 00 C8 07 04 00 00 00 01 08 04 00 00 00 01 0B 87 7E
17:17:12 Send AARQ request.
TX: 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 1E 5D FF FF 88 55 7E
17:17:12
RX: 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 18 1F 00 C8 00 07 26 16 7E
17:19:02 Send Keep Alive
TX: 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 01 00 F9 79 7E
17:19:07 Failed to receive reply from the device in given time.
17:19:07 Disconnect request
TX: 7E A0 07 03 21 53 03 C7 7E
17:19:12 Failed to receive reply from the device in given time.

Proposed Conformance:
GeneralProtection, GeneralBlockTransfer, DeltaValueEncoding, BlockTransferWithGetOrRead, BlockTransferWithSetOrWrite, BlockTransferWithAction, MultipleReferences, Access, Get, Set, SelectiveAccess, Action

Negotiated Conformance:
BlockTransferWithGetOrRead, BlockTransferWithSetOrWrite, Get, Set, SelectiveAccess, EventNotification, Action

Command line parameters:
-S COM12:9600:8NoneOne -i HdlcWithModeE -w 1 -f 128 -t Verbose

I need to request from the meter:
Voltage
Usage
Credits
etc.

Can you kindly assist with the above?

Profile picture for user Kurumi

Kurumi

10 months 1 week ago

Hi, The inactivity timeout…

Hi,

The inactivity timeout is 120 seconds. Try to decrease it, for example to 60 seconds. You can find it from the Advanced tab.

BR,
Mikko

dbrandy

10 months 1 week ago

Good morning, I changed…

Good morning,

I changed inactivity timeout to 60sec - symptoms stays the same.

Hereunder the logs:

08:24:02 Send SNRM request.
TX: 7E A0 07 03 21 93 0F 01 7E
08:24:02
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 00 C8 06 02 00 C8 07 04 00 00 00 01 08 04 00 00 00 01 0B 87 7E
08:24:02 Send AARQ request.
TX: 7E A0 2B 03 21 10 FB AF E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 62 1E 5D FF FF 88 55 7E
08:24:02
RX: 7E A0 37 21 03 30 6C 7C E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 18 1F 00 C8 00 07 26 16 7E
08:25:02 Send Keep Alive
TX: 7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 01 00 F9 79 7E
08:25:07 Failed to receive reply from the device in given time.
08:25:07 Disconnect request
TX: 7E A0 07 03 21 53 03 C7 7E
08:25:12 Failed to receive reply from the device in given time.

It is as if we're sending the wrong OBIS code to meter, hence it does not respond.

I also did some tests on the same meter with EZReader software (https://icube.ch/) which requests the Object list from meter. Meter responds with ObjectUnavailable

Hereunder the logs captured:

READING object_list (Default Association)
0'25.110 +64 Opened
0'25.147 +36 /?!<CR><LF>
0'25.981 +834 /HXE5\2HXE12<CR><LF>
0'25.981 +0 <ACK>252<CR><LF>
0'26.297 +315 --- baud changeover 9600 ---
0'27.338 +1041 7EA0070321930F017E
0'27.588 +249 7EA0202103737398818014050200C8060200C80704000000010804000000010B877E
REQUEST:
<AssociationRequest>
<ApplicationContextName Value="LN" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="Action" />
<ConformanceBit Name="EventNotification" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Access" />
<ConformanceBit Name="DataNotification" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="Attribute0SupportedWithGet" />
<ConformanceBit Name="PriorityMgmtSupported" />
<ConformanceBit Name="Attribute0SupportedWithSet" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="GeneralProtection" />
</ProposedConformance>
<ProposedMaxPduSize Value="FFFF" />
</InitiateRequest>
</AssociationRequest>
0'27.599 +0 7EA02B032110FBAFE6E600601DA109060760857405080101BE10040E01000000065F1F040060FEDFFFFFDE4E7E
0'27.907 +308 7EA0372103306C7CE6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181F00C8000726167E
RESPONSE:
<AssociationResponse>
<ApplicationContextName Value="LN" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>
<ACSEServiceUser Value="00" />
</ResultSourceDiagnostic>
<InitiateResponse>
<NegotiatedDlmsVersionNumber Value="06" />
<NegotiatedConformance>
<ConformanceBit Name="Action" />
<ConformanceBit Name="EventNotification" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
</NegotiatedConformance>
<NegotiatedMaxPduSize Value="00C8" />
<VaaName Value="0007" />
</InitiateResponse>
</AssociationResponse>
REQUEST:
<GetRequest>
<GetRequestNormal>
<InvokeIdAndPriority Value="C1" />
<AttributeDescriptor>
<ClassId Value="000F" />
<InstanceId Value="0000280000FF" />
<AttributeId Value="02" />
</AttributeDescriptor>
</GetRequestNormal>
</GetRequest>
0'27.920 +0 7EA0190321326FD8E6E600C001C1000F0000280000FF020091537E
0'28.171 +250 7EA011210352B1F8E6E700C40141010BD7027E
RESPONSE:
<GetResponse>
<GetResponseNormal>
<InvokeIdAndPriority Value="41" />
<Result>
<DataAccessError Value="ObjectUnavailable" />
</Result>
</GetResponseNormal>
</GetResponse>
0'28.173 +0 7EA00703215303C77E
0'28.390 +216 7EA00721217382507E
0'28.391 +1 Closed

Any further suggestions will greatly be appreciated.

Profile picture for user Kurumi

Kurumi

10 months 1 week ago

Hi, It seems that the…

Hi,

It seems that the inactivity timeout is less than 60 seconds. The main problem is that your meter doesn't implement AssociationLogicalName, and that is mandatory.

I found the certificate test for this meter. This test is very old (2015) and only MODE_E is tested. COSEM objects are tested at all.

https://www.dlms.com/DataExchange/certificate/pdf/Cert_HXE_HXE115-KP_15…

You need to establish the connection to the meter and read values, and close the connection. Because the meter doesn't implement AssociationLogicalName you need to add COSEM objects manually.

Perhaps it's best to forget this meter and get the better one.

BR,
Mikko

dbrandy

9 months ago

Good day, Thank you for your…

Good day,

Thank you for your response.

I managed to get hold of a Hexing HXE130 smart meter - with pretty much same results.

Can you possibly find a certificate for this meter?

Profile picture for user Kurumi

Kurumi

9 months ago

Hi, One of your settings is…

Hi,

One of your settings is different from what the meter expects. The settings vary between meter models, but the correct settings should be in the meter documentation.

All the meter certificates are available in the link I shared.

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
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin