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. Janz B280 Acess Goup D Data.

Janz B280 acess Goup D data.

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 cablekiller , 5 February, 2020
Forums
DLMSDirector

I Mister Miko

I'am try to connect a Janz B280 ussing a optical probe & i have read all data except Group D, data.
I try to change the Xml in the manufacturer option but en press apply, some errors appear.
I testwith defaul Gurux XML and the errors are the same.
Funny.
I Have some of XML from Janz/Contar and i like to test them. Send latter to your email
Can you help me to gain access to Group D Obis codes?
I find VT ratio for this device is VT=210 but since new and blank devices are VT=300. Funny.

Tanks in advance & sory for my English

Profile picture for user Kurumi

Kurumi

6 years 4 months ago

Hi,

Hi,

Have you tried to read the meter with GXDLMSDirector? If not, download it and select Janz as meter manufacturer and read.

BR,
Mikko

cablekiller

6 years 3 months ago

Hi Mister Mikko

Hi Mister Mikko

Tanks for the replay.
I download Gurux Director & i install them and try it.
I Have read the meter data, association & register. But can write or modiffi any values.
I'am doing someting wrong? or Gurux Director are not corrected instalaled?
I use a Rs232 Optical prove : And i try in a Sagem CX 2000-9 whit Gurux Manufactor and same results.
I try to reinstal Gurux director but serve give me a error, ( Cannot establish a secure SSL/TTl conection, and no have Manufactors data and Gurux Director d'ont work.
I do something wrong or are some issues in Gurux server?
Sorry for the inconvenience.

Read this on Gurux Location and Version.

.NET Framework 3.5 SP 1 3.5.30729.5420 C:\Windows\Microsoft.NET\Framework\v3.5\
.NET Framework 4.0 4.6.01590 C:\Windows\Microsoft.NET\Framework\v4.0.30319\
GXDLMSDirector 8.2.2002.1202 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\GXDLMSDirector.exe
Gurux.MQTT 8.1.1910.2201 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.MQTT.dll
Gurux.Common 8.1.2001.2404 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.Common.dll
Gurux.DLMS.AMI.UI 8.1.2002.1001 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.DLMS.AMI.UI.dll
Gurux.DLMS 9.0.2002.1201 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.DLMS.dll
Gurux.DLMS.UI 9.0.2002.1202 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.DLMS.UI.dll
Gurux.Net 8.1.2002.1001 C:\Users\Lenovo\AppData\Local\Apps\2.0\6ZWKKVHB.XYC\3Q5T16WA.CZD\gxdl..tion_fac3cc4fecb816b3_0008.0002_1fc3bd69e2bbf812\Gurux.Net.dll
And this in Janz meter conection.

<?xml version="1.0" encoding="UTF-8"?>

-<Objects>

-<GXDLMSClock>

<LN>0.0.1.0.0.255</LN>

<Description>Ch. 0 Clock object #1</Description>

</GXDLMSClock>

-<GXDLMSAssociationLogicalName>

<LN>0.0.40.0.0.255</LN>

<Description>Ch. 0 Current association</Description>

-<ApplicationContextName>

<JointIsoCtt>2</JointIsoCtt>

<Country>16</Country>

<CountryName>756</CountryName>

<IdentifiedOrganization>5</IdentifiedOrganization>

<DlmsUA>8</DlmsUA>

<ApplicationContext>1</ApplicationContext>

<ContextId>1</ContextId>

</ApplicationContextName>

-<XDLMSContextInfo>

<DlmsVersionNumber>6</DlmsVersionNumber>

</XDLMSContextInfo>

-<AuthenticationMechanismName>

<JointIsoCtt>2</JointIsoCtt>

<Country>16</Country>

<CountryName>756</CountryName>

<IdentifiedOrganization>5</IdentifiedOrganization>

<DlmsUA>8</DlmsUA>

<AuthenticationMechanismName>2</AuthenticationMechanismName>

</AuthenticationMechanismName>

<SecuritySetupReference>0.0.0.0.0.0</SecuritySetupReference>

</GXDLMSAssociationLogicalName>

-<GXDLMSAssociationLogicalName>

<LN>0.0.40.0.1.255</LN>

<Description>Ch. 0 Association #1</Description>

<ClientSAP>16</ClientSAP>

<ServerSAP>1</ServerSAP>

-<ApplicationContextName>

<JointIsoCtt>96</JointIsoCtt>

<Country>133</Country>

<CountryName>116</CountryName>

<IdentifiedOrganization>5</IdentifiedOrganization>

<DlmsUA>8</DlmsUA>

<ApplicationContext>1</ApplicationContext>

<ContextId>1</ContextId>

</ApplicationContextName>

-<XDLMSContextInfo>

<Conformance>4116</Conformance>

<MaxReceivePduSize>284</MaxReceivePduSize>

<MaxSendPduSize>284</MaxSendPduSize>

<DlmsVersionNumber>6</DlmsVersionNumber>

</XDLMSContextInfo>

-<AuthenticationMechanismName>

<JointIsoCtt>96</JointIsoCtt>

<Country>133</Country>

<CountryName>116</CountryName>

<IdentifiedOrganization>5</IdentifiedOrganization>

<DlmsUA>8</DlmsUA>

<AuthenticationMechanismName>2</AuthenticationMechanismName>

</AuthenticationMechanismName>

<AssociationStatus>2</AssociationStatus>

<SecuritySetupReference>0.0.0.0.0.0</SecuritySetupReference>

</GXDLMSAssociationLogicalName>

-<GXDLMSSapAssignment>

<LN>0.0.41.0.0.255</LN>

<Description>Ch. 0 SAP Assignment</Description>

<SapAssignmentList/>

</GXDLMSSapAssignment>

-<GXDLMSData>

<LN>0.0.42.0.0.255</LN>

<Description>Ch. 0 COSEM Logical device name</Description>

<Value Type="9">4A 43 45 42 32 38 30 20 20 20 20 20 20 20 20 20</Value>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.0.255</LN>

<Description>Ch. 0 Device ID 1, manufacturing number</Description>

<Value Type="9">31 35 31 36 30 34 38 36 32 30</Value>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.1.255</LN>

<Description>Ch. 0 Device ID #2</Description>

<Value Type="10">00 65 10 00 07 DF</Value>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.2.255</LN>

<Description>Ch. 0 Device ID #3</Description>

<Value Type="10">meterDLMS0101 </Value>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.3.255</LN>

<Description>Ch. 0 Device ID #4</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.4.255</LN>

<Description>Ch. 0 Device ID #5</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.5.255</LN>

<Description>Ch. 0 Device ID #6</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.6.255</LN>

<Description>Ch. 0 Device ID #7</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.8.255</LN>

<Description>Ch. 0 Device ID #9</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.96.1.9.255</LN>

<Description>Ch. 0 Device ID #10</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.0.0.2.0.255</LN>

<Description>Ch. 0 Active firmware identifier</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.0.0.2.8.255</LN>

<Description>Ch. 0 Active firmware signature</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.0.0.9.1.255</LN>

<Description>Ch. 0 Local time</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.0.0.9.2.255</LN>

<Description>Ch. 0 Local date</Description>

<Value Type="26">01/31/2020</Value>

</GXDLMSData>

-<GXDLMSData>

<LN>1.1.0.2.0.255</LN>

<Description>Ch. 1 Active firmware identifier</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.1.0.2.8.255</LN>

<Description>Ch. 1 Active firmware signature</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.2.0.2.0.255</LN>

<Description>Ch. 2 Active firmware identifier</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>1.2.0.2.8.255</LN>

<Description>Ch. 2 Active firmware signature</Description>

</GXDLMSData>

-<GXDLMSData>

<LN>0.0.0.94.35.31</LN>

<Description>Invalid</Description>

</GXDLMSData>

</Objects>

And comformance test

07:25:19 Send SNRM request.
TX: 7E A0 07 03 21 93 0F 01 7E
07:25:19
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:19 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 00 1E 1D FF FF C5 E4 7E
07:25:19
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 10 14 01 1C 00 07 47 80 7E
07:25:19 HDLC test #1. Disconnect request
TX: 7E A0 07 03 21 53 03 C7 7E
07:25:19
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:19 HDLC test #1. SNRM request
TX: 7E A0 20 03 21 93 7D D9 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:19
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:19 HDLC test #1. Receiver Ready
TX: 7E A0 07 03 21 11 15 A6 7E
07:25:19
RX: 7E A0 07 21 03 11 15 00 7E
07:25:19 HDLC test #1. Disconnect request
TX: 7E A0 07 03 21 53 03 C7 7E
07:25:19
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:19 HDLC test #1. Disconnect request
TX: 7E A0 07 03 21 53 03 C7 7E
07:25:19
RX: 7E A0 07 21 03 1F 6B E9 7E
07:25:19 HDLC test #2. SNRM request
TX: 7E A0 20 03 21 93 7D D9 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:24
Data send failed. Try to resend 1/3
07:25:25
RX: 7E A0 20 21 03 73 73 98 81 80 14 05 02 01 1C 06 02 01 1C 07 04 00 00 00 01 08 04 00 00 00 01 C0 C4 7E
07:25:25 HDLC test #2. Illegal frame.
TX: 7E A0 07 03 21 53 03 C7
07:25:30
Data send failed. Try to resend 1/3
07:25:35
Data send failed. Try to resend 2/3

Tanks an sorry for the troubles

Dino

Profile picture for user Kurumi

Kurumi

6 years 3 months ago

Hi Dino,

Hi Dino,

If you want to write values to the meter you need to change the authentication level and client address.
Without the authentication you can only read.

You have tried to run DLMS conformance tests for the meter and it seems meter didn't pass those tests.

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