Hi,
Currently I am using GuruxDLMS.c for my dvelopment.
I have initialized MR Association with password, BLOCK_CIPHER_KEY, AUTHENTICATION_KEY. Here connection is successful but read request gets failed. Can you please help to indetify the root cause?
Below are the logs attached. I have attached Screenshot for your reference.
------------------------------------------------ MR Association---------------------------------------------------------
Initialize Connection
Send AARQ request
DLMS Tx Data = 00 01 00 20 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 48 50 4C 32 37 30 31 32 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 12 80 10 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 BE 23 04 21 21 1F 30 59 6B 21 54 1A FE B4 50 8C F4 F8 6B CD 4C 50 70 8D 27 87 72 25 31 77 08 96 4C 9D F4 01 E0
Successfully usart_tx length=103
DLMS Rx Data = 00 01 00 01 00 20 00 4A 61 48 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 00 A4 0A 04 08 48 50 4C 00 00 00 69 84 BE 23 04 21 28 1F 30 00 00 00 00 BA 7D C9 05 9D 18 F7 3F 1A A0 2B B9 41 0B 28 E0 04 69 82 1D C9 E5 79 73 9C DA
Connection success
Read Attribute Time of Object Clock
DLMS Tx Data = 00 01 00 20 00 01 00 20 C8 1E 30 59 6B 21 55 4D 1B 34 64 63 2F F4 85 57 C4 71 CF 65 EC 66 E1 40 7B F5 92 CE A0 DF 37 0A
Successfully usart_tx length=40
DLMS Rx Data = 00 01 00 01 00 20 00 17 2E 15 30 00 00 00 01 C1 F9 AD E5 29 73 16 42 8F 4F 8C B7 CF A3 B3 CEReadObject failed Clock 0.0.1.0.0.255:2 Invalid parameter.
Thanks,
Jigar
Hi Jigar, It looks like you…
Hi Jigar,
It looks like you can establish the connection for the meter, but the meter returns a ServiceUnsupported exception when you try to read the clock object.
Check that you can see the clock object in the association view e.g. with GXDLMSDirector and try to read it. There is no reason why you can't read it.
BR,
Mikko
Hi Mikko, Yes I am able to…
Hi Mikko,
Yes I am able to see and get the clock object using GXDLMSDirector Tool from meter using MR Association.
Below are the scenario
With Director Tool
1. GXDLMSDirector ----- PC-Association ----- Meter : Working
2. GXDLMSDirector ----- MR-Association ----- Meter : Working
With Library GuruxDLMS.c
1. GuruxDLMS.c ----- PC-Association ----- Meter : Working
Read Clock Object : Success
2. GuruxDLMS.c ----- MR-Association ----- Meter : NOT WORKING
Read Clock Object : Shows previous given error
Can you help to find if i am missing something?
Thanks,
Jigar
Hi, Please, don't add…
Hi,
Please, don't add pictures. Reading bytes is hard to read and plain text is better.
You haven't read the invocation counter. I believe that is the problem.
Try to read the invocation counter before you establish the ciphered connection.
BR,
Mikko
Hi, I have read invocation…
Hi,
I have read invocation counter for MR-Association. Steps to get data in MR from meter are followed as below
1. PC-Connection - working
2. PC-Read Invocation Counter of MR - working
3. PC-Disconnect - working
4. MR-Connection - working
5. MR-Read Time - NOT WORKING
Below is the data sent/received from meter for step 4 and step 5.
Initialize MR-Connection
Send AARQ request
DLMS Tx Data = 00 01 00 20 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 48 50 4C 32 37 30 31 32 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 12 80 10 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 BE 23 04 21 21 1F 30 59 6B 21 54 1A FE B4 50 8C F4 F8 6B CD 4C 50 70 8D 27 87 72 25 31 77 08 96 4C 9D F4 01 E0
Successfully usart_tx length=103
DLMS Rx Data = 00 01 00 01 00 20 00 4A 61 48 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 00 A4 0A 04 08 48 50 4C 00 00 00 69 84 BE 23 04 21 28 1F 30 00 00 00 00 BA 7D C9 05 9D 18 F7 3F 1A A0 2B B9 41 0B 28 E0 04 69 82 1D C9 E5 79 73 9C DA
Connection success
Read Attribute Time of Object Clock
DLMS Tx Data = 00 01 00 20 00 01 00 20 C8 1E 30 59 6B 21 55 4D 1B 34 64 63 2F F4 85 57 C4 71 CF 65 EC 66 E1 40 7B F5 92 CE A0 DF 37 0A
Successfully usart_tx length=40
DLMS Rx Data = 00 01 00 01 00 20 00 17 2E 15 30 00 00 00 01 C1 F9 AD E5 29 73 16 42 8F 4F 8C B7 CF A3 B3 CEReadObject failed Clock 0.0.1.0.0.255:2 Invalid parameter.
Thanks,
Jigar