Hi. I'm trying to create a simple C# Meter client, but after the connection configuration I have an error on GetAssociationView request. The message exception returned it's the seguent:
Gurux.DLMS.GXDLMSException: Access Error : Device reports a unavailable object.
in Gurux.DLMS.Reader.GXDLMSReader.ReadDLMSPacket(Byte[] data, GXReplyData reply) in ...
There might be a few reasons for this.
1. If you are using the pre-established connection, Italy meters don't always support Association View.
You must know what you want to read.
2. Association View is not implemented to the meter.
3. Some Italy meters don't implement "Current Association View" OBIS code 0.0.40.0.0.255. This is breaking DLMS standard, but for this reason, you can give OBIS code to GetObjectsRequest as a parameter. Change * in 0.0.40.0.*.255 to authentication level index number what you are using.
There are no conformance tests for the Italy standard. This is causing that there are variations between meter manufacturers.
Thanks Mikko: you are right. Association view isn't implemented into italian meter.
In my case, I don't need the association view.
Now I have another problem: I tried to read a specific OBIS using my C# software; the meter answered "Invalid command", but if I try to read that OBIS using GXDLMSDirector, It works correctly.
I checked the DLMS messages printed into the GXDLMSDirector log and compared them with the ones generated by my software, and I found a little bit difference. I used the Gurux read method, the same used by the Director, with the same objects, but the message is different.
- This is the messages generated by the Director
7E A0 2D 03 03 10 E2 F4 E6 E6 00 DB 00 1E 30 00 00 00 01 D3 9D D6 A2 8B 50 C8 44 E6 9C BA DA 1F 6A 84 0B 59 0F 11 15 1C 6C 93 42 10 C7 C7 7E
- This is the messages generated by my program
7E A0 2D 03 03 10 E2 F4 E6 E6 00 DB 00 1E 30 00 00 00 01 D3 9D D6 A2 85 50 C8 44 E6 9C BA DA 1F 67 84 0C E6 27 85 FD A4 43 5F 90 0D CB 86 7E
Do you have any suggestion?
Thanks for your support.
Check following settings: System Title, Block Cipher Key, Authentication key and ServerSystemTitle.
Encrypted data is the same in both of the messages. Authentication part if different.
Hi,
Hi,
What meter did you try to read?
BR,
Mikko
Hi MIkko, thanks for your
Hi MIkko, thanks for your answer.
The meter model is: MESURA G4 PRODIGI, based on italian standard meter units11291.
BR
MatteoS
Hi,
Hi,
There might be a few reasons for this.
1. If you are using the pre-established connection, Italy meters don't always support Association View.
You must know what you want to read.
2. Association View is not implemented to the meter.
3. Some Italy meters don't implement "Current Association View" OBIS code 0.0.40.0.0.255. This is breaking DLMS standard, but for this reason, you can give OBIS code to GetObjectsRequest as a parameter. Change * in 0.0.40.0.*.255 to authentication level index number what you are using.
There are no conformance tests for the Italy standard. This is causing that there are variations between meter manufacturers.
BR,
Mikko
Thanks Mikko: you are right.
Thanks Mikko: you are right. Association view isn't implemented into italian meter.
In my case, I don't need the association view.
Now I have another problem: I tried to read a specific OBIS using my C# software; the meter answered "Invalid command", but if I try to read that OBIS using GXDLMSDirector, It works correctly.
I checked the DLMS messages printed into the GXDLMSDirector log and compared them with the ones generated by my software, and I found a little bit difference. I used the Gurux read method, the same used by the Director, with the same objects, but the message is different.
- This is the messages generated by the Director
7E A0 2D 03 03 10 E2 F4 E6 E6 00 DB 00 1E 30 00 00 00 01 D3 9D D6 A2 8B 50 C8 44 E6 9C BA DA 1F 6A 84 0B 59 0F 11 15 1C 6C 93 42 10 C7 C7 7E
- This is the messages generated by my program
7E A0 2D 03 03 10 E2 F4 E6 E6 00 DB 00 1E 30 00 00 00 01 D3 9D D6 A2 85 50 C8 44 E6 9C BA DA 1F 67 84 0C E6 27 85 FD A4 43 5F 90 0D CB 86 7E
Do you have any suggestion?
Thanks for your support.
BR
MatteoS
Hi,
Hi,
Check following settings: System Title, Block Cipher Key, Authentication key and ServerSystemTitle.
Encrypted data is the same in both of the messages. Authentication part if different.
BR,
Mikko