I am trying to set profile generic registers for load survey to a meter. What I mean is, I want, for example, 0.0.21.0.1.255 register includes only 1.0.1.8.0.255, 1.0.2.8.0.255, 1.0.5.8.0.255, 1.0.1.8.1.255, 1.0.2.8.1.255, 1.0.5.8.1.255. etc.
You need to connect using High authentication. Then you can write capture objects. I believe that best way to start is if you download GXDLMSDirector and change capture objects with that.
Thanks for your reply. I want it to be done programmatically so I have to use .net client and nuget library.
But as you said, I will try first with GXDLMSDirector. Is there any information where and how I can do it with .net library?
On the GXDLMSDirector settings, I've switched from low authentication to high and tried to connect with the same password. But it throws the attached exception.
I must say this you're doing a very great job by supporting us, beyond gurux itself. So many thanks for your support.
When I select meter brand, client address becomes 64 but I cannot connect with this setting.
I can connect it successfully with low authentication setting, on client address 1.
Changing it to High Authentication, client address changes to 64 again. Neither 64 nor 1 works.
Do you think there is a possibility that high authentication mode is disabled on the meter? Or the password is different?
And do I need to try every client address from 1 to 64 for high authentication?
I have been trying all the client addresses since yesterday, but it doesn't get connected with high authentication.
There is one thing.
It always drops to timeout unless the client address is 1. If it is 1, it gives the below error.
"Connection is permanently rejected. Authentication mechanism name not recognised."
Does it mean something other than incorrect client address?
I can set registers via the meter's own software (sep2 meterview). However, when I try it with low authentication, Gurux gives me an error saying "Access error:other reason."
If client address is 1, you need to use the authentication level. Change authentication from None to Low or High and set password.
You can set time using low authentication, but if you want to set something else you need to use High authentication level. This error is coming because you try to set value and your authentication level is wrong.
If you make a connection with Meterview using High authentication and add trace (the first line is enough) I can check the correct client address for you.
Differences are because the conformance bits are different, but it should not affect in any away.
You should be able to make connection using Low authentication with those settings.
Can you connect using High authentication with Meterview?
On Meterview, there is no authentication type like low, high etc. There are only password, md-5, sha1 and gmac types (please see the attached image). We're using password option and I can change registers (capture objects).
On GXDLMSDirector, I can make Low authentication connection with those settings, but I cannot capture objects.
You need to connect using Meterview. MD5, SHA-1 and GMAC are all High authentication types.
Connect with that usually use and add trace so I can check correct settings for your meter.
You are connecting using Low authentication. I believe that you can't write anything else than the clock.
The connection is re-established when you write something. I need first frame from that.
Hi,
Hi,
You need to connect using High authentication. Then you can write capture objects. I believe that best way to start is if you download GXDLMSDirector and change capture objects with that.
BR,
Mikko
Hi Kurumi,
Hi Mikko,
Thanks for your reply. I want it to be done programmatically so I have to use .net client and nuget library.
But as you said, I will try first with GXDLMSDirector. Is there any information where and how I can do it with .net library?
On the GXDLMSDirector
On the GXDLMSDirector settings, I've switched from low authentication to high and tried to connect with the same password. But it throws the attached exception.
Hi,
Hi,
There are several different settings. If one of them is wrong, the meter doesn't reply.
Try to connect first without authentication. If you change authentication you need also change the client address.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I must say this you're doing a very great job by supporting us, beyond gurux itself. So many thanks for your support.
When I select meter brand, client address becomes 64 but I cannot connect with this setting.
I can connect it successfully with low authentication setting, on client address 1.
Changing it to High Authentication, client address changes to 64 again. Neither 64 nor 1 works.
Do you think there is a possibility that high authentication mode is disabled on the meter? Or the password is different?
And do I need to try every client address from 1 to 64 for high authentication?
Hi,
Hi,
Try to change 64 to 0x40. I believe that the client address is wrong and that is the reason.
BR,
Mikko
Hi,
Hi,
Client Address is digit only area in GXDLMSDirector. So I can't type in 0x40.
Hi,
Hi,
Add 40. GXDLMSDirector uses hex values.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I have been trying all the client addresses since yesterday, but it doesn't get connected with high authentication.
There is one thing.
It always drops to timeout unless the client address is 1. If it is 1, it gives the below error.
"Connection is permanently rejected. Authentication mechanism name not recognised."
Does it mean something other than incorrect client address?
I can set registers via the meter's own software (sep2 meterview). However, when I try it with low authentication, Gurux gives me an error saying "Access error:other reason."
By the way, I can set the clock with Gurux.
Hi,
Hi,
If client address is 1, you need to use the authentication level. Change authentication from None to Low or High and set password.
You can set time using low authentication, but if you want to set something else you need to use High authentication level. This error is coming because you try to set value and your authentication level is wrong.
If you make a connection with Meterview using High authentication and add trace (the first line is enough) I can check the correct client address for you.
BR,
Mikko
Hi Mikko,
Hi Mikko,
Thanks in advance.
Sep2MeterView output:
00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 XX XX XX XX XX XX XX XX BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F FF FF
Gurux output:
00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 XX XX XX XX XX XX XX XX BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 1D FF FF
There are only two differences at the end, sep2mv is sending 7E 1F while gurux's is 1E 1D.
PS: XX contains the meter password
Hi,
Hi,
Differences are because the conformance bits are different, but it should not affect in any away.
You should be able to make connection using Low authentication with those settings.
Can you connect using High authentication with Meterview?
BR,
Mikko
Hi Mikko,
Hi Mikko,
On Meterview, there is no authentication type like low, high etc. There are only password, md-5, sha1 and gmac types (please see the attached image). We're using password option and I can change registers (capture objects).
On GXDLMSDirector, I can make Low authentication connection with those settings, but I cannot capture objects.
and this is the gurux
and this is the gurux settings.
Hi,
Hi,
You need to connect using Meterview. MD5, SHA-1 and GMAC are all High authentication types.
Connect with that usually use and add trace so I can check correct settings for your meter.
BR,
Mikko
Hi Mikko,
Hi Mikko,
I don't have Meterview.
I have Sep2 Meterview, if you mean this, below is trace log:
Log name: ALC_ME382_GPRS
--------------------
Events: 6, Bytes: 209
Requests: 3 (50.00%), Requests bytes: 106 (50.72%)
Answers: 3 (50.00%), Answer bytes: 103 (49.28%)
--------------------
1. Request: 13:55:48.295
--------------------
Size 64 B (30.62%)
--------------------
00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 .......8`6....`.
74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 t..........`.t..
02 01 AC 0A 80 08 XX XX XX XX XX XX XX XX BE 10 ......XXXXXXXX..
04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F FF FF ......._....~...
2. Answer: 13:55:48.691
--------------------
Size 51 B (24.40%)
--------------------
00 01 00 01 00 01 00 2B 61 29 A1 09 06 07 60 85 .......+a)....`.
74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 t...............
00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 7E 1F 05 ........_....~..
00 00 07 ...
3. Request: 13:55:48.692
--------------------
Size 21 B (10.05%)
--------------------
00 01 00 01 00 01 00 0D C0 01 40 00 08 00 00 01 ..........@.....
00 00 FF 02 00 .....
4. Answer: 13:55:48.987
--------------------
Size 26 B (12.44%)
--------------------
00 01 00 01 00 01 00 12 C4 01 40 00 09 0C 07 E4 ..........@.....
08 12 02 0D 37 31 00 FF 4C 80 ....71..L.
5. Request: 13:55:48.987
--------------------
Size 21 B (10.05%)
--------------------
00 01 00 01 00 01 00 0D C0 01 40 00 08 00 00 01 ..........@.....
00 00 FF 02 00 .....
6. Answer: 13:55:49.250
--------------------
Size 26 B (12.44%)
--------------------
00 01 00 01 00 01 00 12 C4 01 40 00 09 0C 07 E4 ..........@.....
08 12 02 0D 37 31 00 FF 4C 80 ....71..L.
Hi,
Hi,
You are connecting using Low authentication. I believe that you can't write anything else than the clock.
The connection is re-established when you write something. I need first frame from that.
BR,
Mikko
Hi,
Hi,
Yes it's true, I can only write the clock with GXDLMSDirector.
Sep2 Meterview write anything.
I believe I have sent the first frame for Sep2 Meterview and GXDLMSDirector above whic has 2 different bits at the end.
So here is the log for adding 1.0.1.7.0 register to 1.0.99.1.0.255 by using Sep2 Meterview.
Log name: ALC_ME382_GPRS
--------------------
Events: 8, Bytes: 316
Requests: 4 (50.00%), Requests bytes: 229 (72.47%)
Answers: 4 (50.00%), Answer bytes: 87 (27.53%)
--------------------
1. Request: 20:27:07.291
--------------------
Size 64 B (20.25%)
--------------------
00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 .......8`6....`.
74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 t..........`.t..
02 01 AC 0A 80 08 xx xx xx xx xx xx xx xx BE 10 ......XXXXXXXX..
04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F FF FF ......._....~...
2. Answer: 20:27:07.685
--------------------
Size 51 B (16.14%)
--------------------
00 01 00 01 00 01 00 2B 61 29 A1 09 06 07 60 85 .......+a)....`.
74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 t...............
00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 7E 1F 05 ........_....~..
00 00 07 ...
3. Request: 20:27:07.686
--------------------
Size 113 B (35.76%)
--------------------
00 01 00 01 00 01 00 69 C1 01 40 00 07 01 00 63 .......i..@....c
01 00 FF 03 00 01 05 02 04 12 00 08 09 06 00 00 ................
01 00 00 FF 0F 02 12 00 00 02 04 12 00 01 09 06 ................
00 00 60 0A 01 FF 0F 02 12 00 00 02 04 12 00 03 ..`.............
09 06 01 00 1F 07 00 FF 0F 02 12 00 00 02 04 12 ................
00 03 09 06 01 00 20 07 00 FF 0F 02 12 00 00 02 ...... .........
04 12 00 03 09 06 01 00 01 07 00 FF 0F 02 12 00 ................
00 .
4. Answer: 20:27:08.284
--------------------
Size 12 B (3.80%)
--------------------
00 01 00 01 00 01 00 04 C5 01 40 00 ..........@.
5. Request: 20:27:08.284
--------------------
Size 26 B (8.23%)
--------------------
00 01 00 01 00 01 00 12 C1 01 40 00 07 01 00 63 ..........@....c
01 00 FF 04 00 06 00 00 03 84 ..........
6. Answer: 20:27:08.783
--------------------
Size 12 B (3.80%)
--------------------
00 01 00 01 00 01 00 04 C5 01 40 00 ..........@.
7. Request: 20:27:08.783
--------------------
Size 26 B (8.23%)
--------------------
00 01 00 01 00 01 00 12 C1 01 40 00 07 01 00 63 ..........@....c
01 00 FF 08 00 06 00 00 4E 00 ........N.
8. Answer: 20:27:09.046
--------------------
Size 12 B (3.80%)
--------------------
00 01 00 01 00 01 00 04 C5 01 40 00 ..........@.