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. Insufficient Memory

Insufficient memory

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 utkarsh , 14 November, 2019
Forums
DLMSDirector

Hi,

I am new to DLMS meter. I have taken gurux.dlms.server.example2.java as meter and DLMS Director as client.

I am trying to connect meter in secure mode with settings as shown in attached screenshot. But I am getting below error.

23:20:32
<WRAPPER len="67" >
<TargetAddress Value="30" />
<SourceAddress Value="1" />
<PDU>
<AssociationRequest>
<ApplicationContextName Value="LN_WITH_CIPHERING" />
<CallingAPTitle Value="7177657274797569" />
<SenderACSERequirements Value="1" />
<MechanismName Value="High" />
<CallingAuthentication Value="51580D4A782852052A2509241F032845" />
<glo_InitiateRequest Value="3000000000F20CD2063D2249B7339079AA79315529A372CA2AAB1DC10B2496" />
</AssociationRequest>
</PDU>
</WRAPPER>

23:20:37
<HDLC len="20" >
<TargetAddress Value="30" />
<SourceAddress Value="1" />
<!--S frame.-->
<!--Invalid I Frame: 97. Expected: 0-->
<FrameType Value="97" />
<PDU>
Insufficient memory to continue the execution of the program.

23:20:42
<HDLC len="20" >
<TargetAddress Value="30" />
<SourceAddress Value="1" />
<!--S frame.-->
<!--Invalid I Frame: 97. Expected: 0-->
<FrameType Value="97" />
<PDU>
Insufficient memory to continue the execution of the program.

23:20:42
<HDLC len="20" >
<TargetAddress Value="30" />
<SourceAddress Value="1" />
<!--S frame.-->
<!--Invalid I Frame: 97. Expected: 0-->
<FrameType Value="97" />
<PDU>
Insufficient memory to continue the execution of the program.

Logs:
GXDLMSDirector 8.2.1910.3102
Log created 11:20:27 PM
23:20:31 Initializing Network connection.
11:20:32 PM Send AARQ request.
00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 51 58 0D 4A 78 28 52 05 2A 25 09 24 1F 03 28 45 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
Data send failed. Try to resend 1/3
11:20:37 PM Data send failed. Try to resend 1/3
00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 51 58 0D 4A 78 28 52 05 2A 25 09 24 1F 03 28 45 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
Data send failed. Try to resend 2/3
11:20:42 PM Data send failed. Try to resend 2/3
00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 51 58 0D 4A 78 28 52 05 2A 25 09 24 1F 03 28 45 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
Data send failed. Try to resend 3/3
11:20:47 PM Data send failed. Try to resend 3/3
00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 51 58 0D 4A 78 28 52 05 2A 25 09 24 1F 03 28 45 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
11:20:52 PM Failed to receive reply from the device in given time.
7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
11:20:52 PM
7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
System.TimeoutException: Failed to receive reply from the device in given time.
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)

Image
Profile picture for user Kurumi

Kurumi

6 years 7 months ago

Hi,

Hi,

From the trace, it looks like you have select WRAPPER as an interface type, but the meter is using HDLC.
Try to change WRAPPER to HDLC. It's interesting that meter is answering at all.

BR,

Mikko

utkarsh

6 years 7 months ago

Thanks for you prompt reply.

Thanks for you prompt reply. I want meter to be WRAPPER as an interface type. Please let me know the place to configure this in guru.dlms.server.example2.java codebase.

Profile picture for user Kurumi

Kurumi

6 years 7 months ago

Hi,

Hi,

Set the interface type to wrapper after you have set meter settings.

BR,

Mikko

utkarsh

6 years 7 months ago

Meter is listening at 4063.

Meter is listening at 4063. And I see code is
GXDLMSServerLN_47.java
super(new GXDLMSAssociationLogicalName(), InterfaceType.WRAPPER);

Profile picture for user Kurumi

Kurumi

6 years 7 months ago

Hi,

Hi,

Yes, that is correct.

BR,
Mikko

utkarsh

6 years 7 months ago

Director has interface as

Director has interface as WRAPPER and meter is also having interface as WRAPPER. Then what is the issue ?

Profile picture for user Kurumi

Kurumi

6 years 7 months ago

Hi,

Hi,

Data what meter is returning is using HDLC framing, not WRAPPER.

BR,

Mikko

utkarsh

6 years 6 months ago

I have not change any code

I have not change any code meter side from the example server 2. Is it issue with DLMS library ?
I enabled the tracing at meter side. below is the trace.

Client Connected.
<- 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
Data length is 95and there are 301 bytes.
-> 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
<- 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
-> 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
<- 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
-> 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
<- 00 01 00 30 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 71 77 65 72 74 79 75 69 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 6E 72 67 74 3C 02 47 2B 2F 40 32 21 25 0F 1E 02 BE 23 04 21 21 1F 30 00 00 00 00 F2 0C D2 06 3D 22 49 B7 33 90 79 AA 79 31 55 29 A3 72 CA 2A AB 1D C1 0B 24 96
-> 7E A0 21 61 03 97 94 23 61 00 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 01 A3 05 A2 03 02 01 25 BE 7E
Client Disconnected.

Profile picture for user Kurumi

Kurumi

6 years 6 months ago

Hi,

Hi,

I tested this by my self. I started gurux.dlms.server.example2 project. Then I selected "Indian Standard" to meter manufacturer and changed Interface from HDLC to WRAPPER. Then I set correct TCP/IP address and port number to 4063. Meter reply as expected.

Check that you have not made any changes to the source code. Nobody else has this problem.

BR,
Mikko

utkarsh

6 years 6 months ago

Hi Mikko,

Hi Mikko,

I checked it again. Issue is occurring when security is set to "AuthenticaionEncryption". I have set SystemTile
BlockCipherKey
Authentication Key
as well.

Can you pls share your Security settings if it is working fine.

Regards,
Utkarsh

  • 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