I am trying to write data into meter having Indian standard manufacturer.
Following are the configuration :
Security: High
Authentication level : AuthenticationEncryption
Action : AuthenticatedReadWrite
I have written data into meter for 0.0.96.13.1.255 obis code for attribute index 2. After the power cycle, I am able to read the same data which was written.
Now I am removing device and added same device again into the GXDLMDIrector application and trying to read the same attribute but did not get written value.
This sounds strange. Are you restart the meter? Can you do this without authentication and post write messages here? Don't post anything else than write. I can check what is happening from the bytes.
I can write attribute value only when the authentication level is high.
If I keep authentication level none then only able to read attribute value not able to write.
I can connect a meter having an authentication level as AuthenticationEncryption only. Also from the log, I can see that in association response ApplicationContextName Value is "LN_WITH_CIPHERING".
So, all the messages were ciphered.
For other options, it gives the "Applicatoin Unsupported Context" error.
Let me know if you want any other details from which you can check.
When I write any data, I just get the notification of Value changed, but no updates in logs.
After write data, I have read the same and the following are the logs from the trace window.
Hi,
Hi,
This sounds strange. Are you restart the meter? Can you do this without authentication and post write messages here? Don't post anything else than write. I can check what is happening from the bytes.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I can write attribute value only when the authentication level is high.
If I keep authentication level none then only able to read attribute value not able to write.
Hi,
Hi,
Sorry, use authentication level high, but don't use ciphering. In that way, messages are not ciphered and I can check what is the problem.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I can connect a meter having an authentication level as AuthenticationEncryption only. Also from the log, I can see that in association response ApplicationContextName Value is "LN_WITH_CIPHERING".
So, all the messages were ciphered.
For other options, it gives the "Applicatoin Unsupported Context" error.
Let me know if you want any other details from which you can check.
Hi,
Hi,
Can you select "View" | "Trace" | "PDU" and "Comments". Then write data and post trace from trace window here.
BR,
Mikko
Hi Mikko,
Hi Mikko,
When I write any data, I just get the notification of Value changed, but no updates in logs.
After write data, I have read the same and the following are the logs from the trace window.
12:45:11
<!--Decrypt data: C4 01 81 00 09 06 00 00 60 0D 01 FF
<GetResponse>
<GetResponseNormal>
<InvokeIdAndPriority Value="81" />
<Result>
<Data>
<!--0.0.96.13.1.255-->
<OctetString Value="0000600D01FF" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
-->
<glo_GetResponse Value="30000008FEA31C34981DCE294F8629A1058E384D82FD541ABE63517EB8" />
Let me know if you require more details on it.
Hi Mikko,
Hi Mikko,
I changed the value and then write a value to the device, that got an access error.
Following are the logs from the trace window for the same.
15:58:14
<!--Decrypt data: C1 01 C1 00 01 00 00 60 80 00 FF 02 00 0A 04 31 32 33 34
<SetRequest>
<SetRequestNormal>
<InvokeIdAndPriority Value="C1" />
<AttributeDescriptor>
<!--Data-->
<ClassId Value="0001" />
<!--0.0.96.128.0.255-->
<InstanceId Value="0000608000FF" />
<AttributeId Value="02" />
</AttributeDescriptor>
<Value>
<String Value="1234" />
</Value>
</SetRequestNormal>
</SetRequest>
-->
<glo_SetRequest Value="300000000D9CD3225932A8D9CEF409389D1A28EEA4F87EEDA0F2AA6203D6F8F40C5CE6C8" />
15:58:14
<!--Decrypt data: C5 01 81 0B
<SetResponse>
<SetResponseNormal>
<InvokeIdAndPriority Value="81" />
<Result Value="UnavailableObject" />
</SetResponseNormal>
</SetResponse>
-->
<glo_SetResponse Value="3000000A1E958AF42C975690CFB8FACE4FE192EBE6" />
Hi,
Hi,
For some reason, the data type is a string. GXDLMSDirector tries to write a string value to the meter.
That causes the error.
Can you try to re-read the association view again? I believe it handles the problem.
BR,
Mikko