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. Different Response On DLMSDirector & Android App

Different Response on DLMSDirector & Android App

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 p1j , 3 November, 2022
Forums
Gurux.DLMS

Just starting with a dive in DLMS world, and its just the beginning.. Trying connecting to a Common meter (Genus Power) using the common optical probe (FT232) with the android based app (using .net & Xamarin) and with the provided GxDLMSDirector App and getting different results.. Android App is showing length one less in bytes and has a different output [in octetstring] and not decimal. Not sure what I am missing & what params need to be changed for identical information [Director app is getting it right]

The Android App has following Rx and Tx

Rx:7E A0 19 03 41 54 0A BB E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E

Tx: 7E A0 1E 41 03 74 31 0B E6 E7 00 C4 01 C1 00 09 0C 07 E6 0B 03 04 10 20 1B FF 01 4A 00 F8 70 7E

and the outcome PDU
<HDLC len="29" >
<TargetAddress Value="32" />
<SourceAddress Value="1" />
<!--I frame.-->
<FrameType Value="74" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="193" />
<Result>
<Data>
<!--2022-11-03 16:32:27-->
<OctetString Value="07E60B030410201BFF014A00" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>

The Director app is getting the correct results

Rx:7E A0 19 03 41 FE 5A B1 E6 E6 00 C0 01 C1 00 01 00 00 60 01 00 FF 02 00 89 A0 7E

Tx: 7E A0 1F 41 03 1E D6 DB E6 E7 00 C4 01 C1 00 0A 0D 20 20 20 20 20 31 30 39 31 34 37 35 34 86 09 7E

PDU
<HDLC len="30" >
<TargetAddress Value="32" />
<SourceAddress Value="1" />
<!--I frame.-->
<FrameType Value="1E" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="193" />
<Result>
<Data>
<String Value=" 10914754" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>

Profile picture for user Kurumi

Kurumi

3 years 7 months ago

Hi,

Hi,

With android app you try to read clock object attribute index #2
http://gurux.fi/Gurux.DLMS.Objects.GXDLMSClock

and with GXDLMSDirector you try to read data object attribute index #2.
http://gurux.fi/Gurux.DLMS.Objects.GXDLMSData

That is the reason why the result is different.

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