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.
Forums
Hi Mikko,
I am having trouble to communicate wth this meter.
I have received form the manufacturer only one long password, which makes me asume that this is a HLS meter using Authentication mechanism #2.
I got an association response value 00 but Gurux shows me a message in German (My pc is in German), which means somethinh like:
"The source array is not long enough. Check srcindex, the length and the lower bound of the array"
Would you please chech the log files and give me your comments?
Many Thanks
Frank
15:18:24
<HDLC len="1E" >
<TargetAddress Value="91" />
<SourceAddress Value="1" />
<FrameType Value="93" />
<PDU>
<Snrm>
<MaxInfoTX Value="117" />
<MaxInfoRX Value="116" />
<WindowSizeTX Value="1" />
<WindowSizeRX Value="1" />
</Snrm>
</PDU>
</HDLC>
15:18:24
<HDLC len="20" >
<TargetAddress Value="1" />
<SourceAddress Value="91" />
<FrameType Value="73" />
<PDU>
<Ua>
<MaxInfoTX Value="117" />
<MaxInfoRX Value="116" />
<WindowSizeTX Value="1" />
<WindowSizeRX Value="1" />
</Ua>
</PDU>
</HDLC>
15:18:24
<HDLC len="4C" >
<TargetAddress Value="91" />
<SourceAddress Value="1" />
<FrameType Value="10" />
<PDU>
<AssociationRequest>
<ApplicationContextName Value="LN" />
<SenderACSERequirements Value="1" />
<MechanismName Value="High" />
<CallingAuthentication Value="585438131E67076B6B2E12006E510E0B" />
<InitiateRequest>
<ProposedDlmsVersionNumber Value="06" />
<ProposedConformance>
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="Access" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Action" />
</ProposedConformance>
<ProposedMaxPduSize Value="FFFF" />
</InitiateRequest>
</AssociationRequest>
</PDU>
</HDLC>
15:18:24
<HDLC len="58" >
<TargetAddress Value="1" />
<SourceAddress Value="91" />
<FrameType Value="30" />
<PDU>
<AssociationResponse>
<ApplicationContextName Value="LN" />
<AssociationResult Value="00" />
<ResultSourceDiagnostic>
<ACSEServiceUser Value="0E" />
</ResultSourceDiagnostic>
<ResponderACSERequirement Value="1" />
<MechanismName Value="High" />
<RespondingAuthentication Value="31333537353337303537353135333334" />
<InitiateResponse>
<NegotiatedDlmsVersionNumber Value="06" />
<NegotiatedConformance>
<ConformanceBit Name="GeneralProtection" />
<ConformanceBit Name="GeneralBlockTransfer" />
<ConformanceBit Name="BlockTransferWithGetOrRead" />
<ConformanceBit Name="BlockTransferWithSetOrWrite" />
<ConformanceBit Name="BlockTransferWithAction" />
<ConformanceBit Name="MultipleReferences" />
<ConformanceBit Name="DataNotification" />
<ConformanceBit Name="Get" />
<ConformanceBit Name="Set" />
<ConformanceBit Name="SelectiveAccess" />
<ConformanceBit Name="Action" />
</NegotiatedConformance>
<NegotiatedMaxPduSize Value="0140" />
<VaaName Value="0007" />
</InitiateResponse>
</AssociationResponse>
</PDU>
</HDLC>
Image
Hi,
Hi,
Can you share the log as raw hex data so I can check what is causing this from the bytes?
BR,
Mikko
Hi Mikko,
Hi Mikko,
15:16:18 Send SNRM request.
TX: 7E A0 1F 02 23 03 93 A2 F0 81 80 12 05 01 75 06 01 74 07 04 00 00 00 01 08 04 00 00 00 01 88 99 7E
15:16:18
RX: 7E A0 21 03 02 23 73 AA C4 81 80 14 05 02 00 75 06 02 00 74 07 04 00 00 00 01 08 04 00 00 00 01 65 1B 7E
15:16:18 Send AARQ request.
TX: 7E A0 4D 02 23 03 10 DB 25 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 2F 07 37 55 65 44 75 3E 70 77 4E 0A 36 70 08 5B BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF 8F 04 7E
15:16:18
RX: 7E A0 59 03 02 23 30 E6 FB E6 E7 00 61 4A A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 33 32 34 34 33 34 38 36 31 39 36 33 37 34 32 33 BE 10 04 0E 08 00 06 5F 1F 04 00 60 1E 9D 01 40 00 07 BB 7B 7E
Many Thanks
Frank
Hi Frank,
Hi Frank,
What version you are using from GXDLMSDirector? I tested this with the simulator using your data and it worked without problems.
BR,
Mikko
Hi Mikko,
Hi Mikko,
the version is 8.1.2109.3001
BR
Frank
Hi,
Hi,
Update to the latest version so we can make sure that this is not any version issue.
Let me know if you have problems and we try to test with the German version from Windows.
Are you using Windows 7, 10, or 11?
BR,
Mikko
hi Mikko,
hi Mikko,
there is no updates available. I am using windows 10.
How can we be sure that the autentication mechanism is the #2?
I am trying using the others, for example #3, and get the answer "Device reports unmachted type"
What is the srcindex?
Many Thanks
Frank
Hi Frank,
Hi Frank,
Remove your app and install the latest version. You are using the old version for .Net 3.5. That is available only for legacy reasons.
srcindex is coming from Windows.
I believe that your meter is using High authentication because it replies for that without problems,
The meter manufacturers can decide what authentication levels are supported and they should be defined on the meter documentation.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I have done it. Unfortunately, I am getting the same error (srcindex)
09:09:49 Send SNRM request.
TX: 7E A0 1F 02 23 03 93 A2 F0 81 80 12 05 01 75 06 01 74 07 04 00 00 00 01 08 04 00 00 00 01 88 99 7E
09:09:49
RX: 7E A0 21 03 02 23 73 AA C4 81 80 14 05 02 00 75 06 02 00 74 07 04 00 00 00 01 08 04 00 00 00 01 65 1B 7E
09:09:49 Send AARQ request.
TX: 7E A0 4D 02 23 03 10 DB 25 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 16 44 60 61 6F 32 4A 6E 36 2D 1B 07 39 13 18 03 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF 1B 42 7E
09:09:49
RX: 7E A0 59 03 02 23 30 E6 FB E6 E7 00 61 4A A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 39 33 39 30 37 32 39 30 39 35 31 32 33 34 37 37 BE 10 04 0E 08 00 06 5F 1F 04 00 60 1E 9D 01 40 00 07 DF 9E 7E
09:09:50
RX: 7E A0 21 03 02 23 73 AA C4 81 80 14 05 02 00 75 06 02 00 74 07 04 00 00 00 01 08 04 00 00 00 01 65 1B 7E
BR
Frank
Hi Frank,
Hi Frank,
I did try this and it worked without problems. Before the German version from Windows is installed, can you tell if this error coming when you establish the connection for the meter or is it coming in the DLMS translator?
BR,
Mikko
Hi Mikko,
Hi Mikko,
I press connect and then i see in the log that the AA is accepted. After that I see the error message. Also the error is comming by establish the conection. Not in the translator.
Many Thanks
Frank
Hi,
Hi,
Can you run this and let me know what .Net version you are using?
dotnet --version
Are you using Windows 7, 10, or 11?
When this is tested with your data all works like expected as the log below shows.
BR,
Mikko
08.56.25 Send SNRM request.
TX: 7E A0 1F 02 23 03 93 A2 F0 81 80 12 05 01 75 06 01 74 07 04 00 00 00 01 08 04 00 00 00 01 88 99 7E
08.56.25
RX: 7E A0 21 03 02 23 73 AA C4 81 80 14 05 02 00 75 06 02 00 74 07 04 00 00 00 01 08 04 00 00 00 01 65 1B 7E
08.56.25 Send AARQ request.
TX: 7E A0 4D 02 23 03 10 DB 25 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 0A 39 12 47 64 5B 4A 5E 27 5E 12 77 14 11 31 72 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 20 1E 5D FF FF 8C F4 7E
08.56.25
RX: 7E A0 59 03 02 23 30 E6 FB E6 E7 00 61 4A A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 33 32 34 34 33 34 38 36 31 39 36 33 37 34 32 33 BE 10 04 0E 08 00 06 5F 1F 04 00 60 1E 9D 01 40 00 07 BB 7B 7E
Hi Mikko,
Hi Mikko,
Dontnet version 5.0.406
Windows version 10
Thanks
Frank