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
Hello,
Appreciate your support in order to know what is wrong in the below log, as the error appears as Read Write denied.
I increased the invocation counter each time I accessed the meter.
The Meter SN: DZG20208330011975
system title "445A473830011975"
Enc key "42443030323530303130303030343030"
Auth Key "42353730344535303133443041443030"
ClientId : 12
Auth mode: 5
Security Mode: 3
Security Suite:0
--- Code to set parameters ------------------------
if(mSecurity==Security.AUTHENTICATION_ENCRYPTION) {
_mClient.getCiphering().setSystemTitle(GXCommon.hexToBytes("5358450000229359"));
_mClient.getCiphering().setAuthenticationKey(gurux.dlms.internal.GXCommon.hexToBytes(_mDevice.getAuthenticationKey()));
_mClient.getCiphering().setBlockCipherKey(gurux.dlms.internal.GXCommon.hexToBytes(_mDevice.getBlockCipherKey()));
_mClient.getCiphering().setSecurity(Security.AUTHENTICATION_ENCRYPTION);
_mClient.getCiphering().setSecuritySuite(SecuritySuite.AES_GCM_128);
_mClient.getCiphering().setInvocationCounter(10);
}
---The log as below:---------------------------
<- ١٥:٣٦:٣٨.٢٤١ 2F 3F 21 0D 0A
->١٥:٣٦:٣٩.٥١٧ 2F 44 5A 47 35 5C 32 31 30 32 30 30 48 44 31 31 46 57 32 30 30 0D 0A
<- ١٥:٣٦:٣٩.٥٢٦ 06 32 35 32 0D 0A
<- ١٥:٣٦:٤٦.٠٧٩ 7E A0 0A 00 02 1E 8F 19 93 ED CE 7E
-> ١٥:٣٦:٤٦.٢١٣ 7E A0 23 19 00 02 1E 8F 73 AF B0 81 80 14 05 02 01 74 06 02 01 84 07 04 00 00 00 01 08 04 00 00 00 01 E4 C7 7E
<- ١٥:٣٦:٥٠.٤٢٩ 7E A0 6E 00 02 1E 8F 19 10 8D B3 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 44 5A 47 38 30 01 19 75 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 6B 69 54 41 29 3C 2C 33 3B 6C 70 19 17 68 76 00 BE 23 04 21 21 1F 30 00 00 00 01 CA 67 5E 5B C3 80 C8 33 91 99 D2 7F 99 A3 3C 75 13 1B 9D E0 7C E1 9C 88 80 F6 1C 26 7E
-> ١٥:٣٦:٥١.١٣٣ 7E A0 7A 19 00 02 1E 8F 30 C6 F3 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 44 5A 47 38 30 01 19 75 88 02 07 80 89 07 60 85 74 05 08 02 05 AA 12 80 10 6C 69 54 41 29 3C 2C 33 3B 6C 70 19 17 68 76 00 BE 23 04 21 28 1F 30 00 00 00 01 C3 67 58 04 DA DB D7 37 89 84 CD 36 66 5B FF B8 96 AB 52 30 11 1F 19 C9 5E 5F 5A 27 7E
<- ١٥:٣٧:٢٤.٥٣٥ 7E A0 42 00 02 1E 8F 19 32 84 63 E6 E6 00 CB 31 30 00 00 00 01 08 66 9F 5B CA DF D7 1F 91 99 33 63 67 55 B2 CF C9 47 14 C6 74 FB 13 58 EA 7E F1 2D A6 70 93 D8 51 B4 8A 95 C4 8C 46 BC 61 F3 8E FE F3 9E 7E
-> ١٥:٣٧:٢٥.١٨٩ 7E A0 15 19 00 02 1E 8F 52 A3 0E E6 E7 00 C7 01 C1 03 01 00 93 3B 7E
Hello,
Hello,
Can you try to read this with GXDLMSDirector?
If read failed, select "Secured connections" tab and then set "Read automatically" and the Logical name of the Frame Counter. You can see the frame counter data object if you connect without authentication for the meter.
BR,
Mikko
Hello,
Hello,
thank you for your swift replay
I didn't have a USB prop to use on a PC only I have a prop connected to an android device.
if you asked about InvocationCounter I read it with noun security and then increased it.
so if there is anything can check using android SDK?
BR
Hi,
Hi,
InvocationCounter number is 1 in your hex trace. Try to read it with authentication level None. Then increase it. I hope it helps. There are multiple parameters and if one of them is wrong, the connection fails.
You can also try to change security from AUTHENTICATION to AUTHENTICATION_ENCRYPTION.
BR,
Mikko
Hello,
Hello,
I change the security and make sure the invocation counter to send correctly but I faced the same error message.
here is below the trace log
<- ٢٠:١٧:١٧.١١٥ 2F 3F 21 0D 0A
->٢٠:١٧:١٨.١٥٩ 2F 44 5A 47 35 5C 32 31 30 32 30 30 48 44 31 31 46 57 32 30 30 0D 0A
<- ٢٠:١٧:١٨.١٦٨ 06 32 35 32 0D 0A
<- ٢٠:١٧:٢٠.٣٥٠ 7E A0 0A 00 02 1E 8F 19 93 ED CE 7E
-> ٢٠:١٧:٢٠.٦١٥ 7E A0 23 19 00 02 1E 8F 73 AF B0 81 80 14 05 02 01 74 06 02 01 84 07 04 00 00 00 01 08 04 00 00 00 01 E4 C7 7E
<- ٢٠:١٧:٢٠.٦٥٩ 7E A0 6E 00 02 1E 8F 19 10 8D B3 E6 E6 00 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 44 5A 47 38 30 01 19 75 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 35 6D 3B 3E 13 29 58 31 0A 60 3C 10 29 67 0A 43 BE 23 04 21 21 1F 30 00 00 00 08 5B 1D FE 31 87 1C F0 B1 0C D5 CD 12 73 A2 B3 43 3A D2 8D 88 72 35 9D 6D 75 8E E8 BD 7E
-> ٢٠:١٧:٢١.٣٤٩ 7E A0 7A 19 00 02 1E 8F 30 C6 F3 E6 E7 00 61 69 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 0E A4 0A 04 08 44 5A 47 38 30 01 19 75 88 02 07 80 89 07 60 85 74 05 08 02 05 AA 12 80 10 36 6D 3B 3E 13 29 58 31 0A 60 3C 10 29 67 0A 43 BE 23 04 21 28 1F 30 00 00 00 08 52 1D F8 6E 9E 47 EF B5 14 C8 D2 5B 8C 5A 70 8E BF 62 42 58 1F CB 18 2C AB 27 11 B5 7E
<- ٢٠:١٧:٢٨.٢٣٢ 7E A0 42 00 02 1E 8F 19 32 84 63 E6 E6 00 CB 31 30 00 00 00 08 99 1C 3F 31 8E 43 EF 9D 0C D5 2C 0E 8D 54 F4 77 48 8E EE 1B 39 D5 D6 93 9B E3 FD FD C6 17 F3 EE 02 8C 62 9E 80 7D CC B9 BD 88 5B 0C FA 18 7E
-> ٢٠:١٧:٢٨.٧٨٧ 7E A0 15 19 00 02 1E 8F 52 A3 0E E6 E7 00 C7 01 C1 03 01 00 93 3B 7E
Exception Access Error : Device reports Read-Write denied.
gurux.dlms.GXDLMSException: Access Error : Device reports Read-Write denied.
Hi,
Hi,
I believe that one of your DLMS settings is different from what the meter expects. Do you have the application from the meter manufacturer? If you do, can you get the hex trace from the messages? If you can get it I can get the correct settings for you from the bytes.
BR,
Mikko