Hi there,
First and foremost, I'd like to thank you for your kind answers.
I'm trying to connect to an ITRON ACE6000, through serial and optical interfaces. I've tried all the configs I could find for DLMSDirector, as well as command line parameters, but so far no luck.
What I have gathered so far:
* Serial interface:
- configured to (2400, 8, N, 1)
- Issues AT at startup and every minute or so
- Responds to "I" (identification COSEM message) with : ACT,ACE6K_MK2_R2
- However only responds to "I" when I respond "OK(\CR)(\LF)" to three AT commands
* Optical interface :
- configured to (300, 7, E, 1)
- Always responds to "I" with the same as serial : ACT,ACE6K_MK2_R2
Both interfaces:
- No response to the interrogation frame at the correct baud rate : "/?!(\CR)(\LF)" yields no response
- Any other config I tried (HDLC, HDLCwithE, WRAPPER) at any combination with or without the password (ABCDEFGH) yields no answer
That is all I could gather so far. Any help is greatly appreciated.
Many thanks!
You should receive a reply for "/?!(\CR)(\LF)" when you use the optical probe. Is there a DLMS label on the meter? I know that there are models from SL7000 that don't use DLMS. Let's check this first.
The meter features the DLMS logo as can be seen on the attached photo. Its datasheet specifies that the optical port is compatible with the IEC62056-21.
For whatever reason, my previous attempts were failing to yield an answer but I just got an answer to the /?!(\CR)(\LF) command.
The answer is the following : 0x2f 0x41 0x43 0x45 0x35 0x5c 0x32 0x41 0x43 0x45 0x36 0x4b 0x5f 0x4d 0x4b 0x32 0x5f 0x52 0x32 0xd 0xa
Yielding, if I am not mistaken :
- Manufacturer : "ACE"
- Baud rate and mode : 9600, mode C
- Identification : ACE6K_MK2_R2
- Enhanced identification character : 2 (0x32)
Knowing all this, I retried to connect with HDLCwithE, but the connection couldn't be established.
Update : I've done some tests through the Python library with HdlcWithModeE as interface.
After the identification response, the Gurux Python client correctly sends the following frame :
06 32 35 32 0D 0A, i.e. in mode C, proceed to HDLC binary mode at 9600bd.
The response of the meter to that is a single byte : "7F". I'm not sure what this response points to.
The Gurux Python client then sends the HDLC frame encoding the provided client and server addresses and all the good stuff. The meter never responds to that.
Example :
Tx : 06 32 35 32 0D 0A
Rx : 7F
Tx : 7E A0 07 23 21 93 34 02 7E
--> Data send failed.
Hope this gives a bit more insight to what is going on.
Hi Mikko,
Thank you for the reply.
I've got a bit further since, through pure HDLC via serial port.
With help of the address resolver (thank you for bugfixing btw), I managed to get the client/server addresses supported.
I did tests with both GXDLMSDirector and the Python DLMS client library.
* GXDLMSDirector : After connecting, I get this message prompt : "You need to read Association view to see all objects what the meter can offer. Do you want to do it now?" After clicking OK, I get :
- Data : 0.0.42.0.0.255 COSEM Logical device name
- AssociationLogicalName : 0.0.40.0.16.255 Ch. 0 Association #16
But nothing more. I try to do a Read aftewards, but always the same Timeout error.
I still haven't been able to resolve this problem. At this point it definitely points to lack of access, although it is odd that reading data is not possible without a password.
I have tried the default password (ABCDEFGH) and it definitely didn't work.
Many thanks!
You see only logical device name when you connect without authentication. Try to connect using a different authentication level, for example, "Electricity Laboratory". The default password has been ABCDEFGH, but it should be on the meter documents.
Hi, You should receive a…
Hi,
You should receive a reply for "/?!(\CR)(\LF)" when you use the optical probe. Is there a DLMS label on the meter? I know that there are models from SL7000 that don't use DLMS. Let's check this first.
BR,
Mikko
Hello Mikko, Many thanks for…
Hello Mikko,
Many thanks for your reply.
The meter features the DLMS logo as can be seen on the attached photo. Its datasheet specifies that the optical port is compatible with the IEC62056-21.
For whatever reason, my previous attempts were failing to yield an answer but I just got an answer to the /?!(\CR)(\LF) command.
The answer is the following : 0x2f 0x41 0x43 0x45 0x35 0x5c 0x32 0x41 0x43 0x45 0x36 0x4b 0x5f 0x4d 0x4b 0x32 0x5f 0x52 0x32 0xd 0xa
Yielding, if I am not mistaken :
- Manufacturer : "ACE"
- Baud rate and mode : 9600, mode C
- Identification : ACE6K_MK2_R2
- Enhanced identification character : 2 (0x32)
Knowing all this, I retried to connect with HDLCwithE, but the connection couldn't be established.
Thank you again! You seem to bring me luck \o/
Kind regards
Update : I've done some…
Update : I've done some tests through the Python library with HdlcWithModeE as interface.
After the identification response, the Gurux Python client correctly sends the following frame :
06 32 35 32 0D 0A, i.e. in mode C, proceed to HDLC binary mode at 9600bd.
The response of the meter to that is a single byte : "7F". I'm not sure what this response points to.
The Gurux Python client then sends the HDLC frame encoding the provided client and server addresses and all the good stuff. The meter never responds to that.
Example :
Tx : 06 32 35 32 0D 0A
Rx : 7F
Tx : 7E A0 07 23 21 93 34 02 7E
--> Data send failed.
Hope this gives a bit more insight to what is going on.
Hi, The request looks…
Hi,
The request looks correct, but this 7F looks a little bit strange. Can you try to read the meter with GXDLMSDirector and let me know what happened?
BR,
Mikko
Hi Mikko, Thank you for the…
Hi Mikko,
Thank you for the reply.
I've got a bit further since, through pure HDLC via serial port.
With help of the address resolver (thank you for bugfixing btw), I managed to get the client/server addresses supported.
I did tests with both GXDLMSDirector and the Python DLMS client library.
* GXDLMSDirector : After connecting, I get this message prompt : "You need to read Association view to see all objects what the meter can offer. Do you want to do it now?" After clicking OK, I get :
- Data : 0.0.42.0.0.255 COSEM Logical device name
- AssociationLogicalName : 0.0.40.0.16.255 Ch. 0 Association #16
But nothing more. I try to do a Read aftewards, but always the same Timeout error.
* Python DLMS client library : I get the similar handshake :
-------------------------------------------------------------------------
gurux_dlms version: 1.0.140
gurux_net version: 1.0.19
gurux_serial version: 1.0.20
Authentication: Authentication.NONE
ClientAddress: 0x10
ServerAddress: 0x8011-
Standard: Standard.DLMS
-------------------------------------------------------------------------
TX: 17:36:39 7E A0 0A 00 04 00 23 21 93 80 4A 7E
RX: 17:36:39 7E A0 23 21 00 04 00 23 73 6C 8E 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 CE 6A 7E
TX: 17:36:39 7E A0 2E 00 04 00 23 21 10 E6 F0 E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF B3 E2 7E
RX: 17:36:40 7E A0 3A 21 00 04 00 23 30 03 0A E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 1D 21 34 00 07 89 9B 7E
TX: 17:36:40 7E A0 1C 00 04 00 23 21 32 07 13 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 00 FF 02 00 91 53 7E
RX: 17:36:41 7E A0 85 21 00 04 00 23 52 B4 03 E6 E7 00 C4 01 C1 00 01 02 02 04 12 00 01 11 00 09 06 00 00 2A 00 00 FF 02 02 01 02 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 01 00 02 04 12 00 0F 11 00 09 06 00 00 28 00 10 FF 02 02 01 08 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 00 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 01 00 B9 5B 7E
-------- Reading 1 0.0.42.0.0.255 Ch. 0 COSEM Logical device name
TX: 17:36:41 7E A0 1C 00 04 00 23 21 54 37 15 E6 E6 00 C0 01 C1 00 01 00 00 2A 00 00 FF 01 00 7A AA 7E
RX: 17:36:41 7E A0 1B 21 00 04 00 23 74 75 F2 E6 E7 00 C4 01 C1 00 09 06 00 00 2A 00 00 FF C0 57 7E
Index: 1 Value: 0.0.42.0.0.255
TX: 17:36:41 7E A0 1C 00 04 00 23 21 76 27 17 E6 E6 00 C0 01 C1 00 01 00 00 2A 00 00 FF 02 00 12 80 7E
RX: 17:36:41 7E A0 25 21 00 04 00 23 96 02 66 E6 E7 00 C4 01 C1 00 0A 10 41 43 45 36 36 31 4D 41 36 33 31 32 35 32 38 38 DB A2 7E
Index: 2 Value: ACE661MA{SNIPPED}
-------- Reading 15 0.0.40.0.16.255 Ch. 0 Association #16
TX: 17:36:41 7E A0 1C 00 04 00 23 21 98 57 19 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 01 00 58 BA 7E
RX: 17:36:42 7E A0 1B 21 00 04 00 23 B8 15 FE E6 E7 00 C4 01 C1 00 09 06 00 00 28 00 10 FF 27 FB 7E
Index: 1 Value: 0.0.40.0.16.255
TX: 17:36:42 7E A0 1C 00 04 00 23 21 BA 47 1B E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 02 00 30 90 7E
RX: 17:36:42 7E A0 85 21 00 04 00 23 DA F4 0B E6 E7 00 C4 01 C1 00 01 02 02 04 12 00 01 11 00 09 06 00 00 2A 00 00 FF 02 02 01 02 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 01 00 02 04 12 00 0F 11 00 09 06 00 00 28 00 10 FF 02 02 01 08 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 00 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 01 00 B9 5B 7E
Index: 2 Value: 0.0.42.0.0.255 Ch. 0 COSEM Logical device name, 0.0.40.0.16.255 Ch. 0 Association #16
TX: 17:36:42 7E A0 1C 00 04 00 23 21 DC 77 1D E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 03 00 E8 89 7E
RX: 17:36:43 7E A0 1A 21 00 04 00 23 FC E0 65 E6 E7 00 C4 01 C1 00 02 02 0F 10 12 00 01 EB 3C 7E
Index: 3 Value: 16, 1
TX: 17:36:43 7E A0 1C 00 04 00 23 21 FE 67 1F E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 04 00 E0 C4 7E
RX: 17:36:43 7E A0 24 21 00 04 00 23 1E 97 F1 E6 E7 00 C4 01 C1 00 02 07 11 02 11 10 12 02 F4 11 05 11 08 11 01 11 01 3A 58 7E
Index: 4 Value: 2 16 756 5 8 1 1
TX: 17:36:43 7E A0 1C 00 04 00 23 21 10 17 11 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 05 00 38 DD 7E
RX: 17:36:43 7E A0 2E 21 00 04 00 23 30 BC D0 E6 E7 00 C4 01 C1 00 02 06 04 18 00 30 1D 12 FF FF 12 21 34 11 06 0F 00 09 08 00 00 00 00 00 00 00 00 7B 72 7E
Index: 5 Value: Conformance.ACTION|SELECTIVE_ACCESS|SET|GET|BLOCK_TRANSFER_WITH_GET_OR_READ|ATTRIBUTE_0_SUPPORTED_WITH_GET 65535 8500 6 0 00 00 00 00 00 00 00 00
Attribute6 is not readable.
Attribute7 is not readable.
TX: 17:36:43 7E A0 1C 00 04 00 23 21 32 07 13 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 10 FF 08 00 40 6D 7E
RX: 17:36:44 7E A0 15 21 00 04 00 23 52 60 30 E6 E7 00 C4 01 C1 00 16 02 01 23 7E
Index: 8 Value: 2
DisconnectRequest
TX: 17:36:44 7E A0 0A 00 04 00 23 21 53 8C 8C 7E
RX: 17:36:44 7E A0 0A 21 00 04 00 23 73 D6 AC 7E
Ended. Press any key to continue.
-------------------------------------------------------------------------
That is all that is output. Some Attributes are not readable, I'm not sure what it means. I'm unable to read any concrete meter data.
Many thanks, Mikko!
Kind regards
I still haven't been able to…
I still haven't been able to resolve this problem. At this point it definitely points to lack of access, although it is odd that reading data is not possible without a password.
I have tried the default password (ABCDEFGH) and it definitely didn't work.
Many thanks!
Hi, You see only logical…
Hi,
You see only logical device name when you connect without authentication. Try to connect using a different authentication level, for example, "Electricity Laboratory". The default password has been ABCDEFGH, but it should be on the meter documents.
BR,
Mikko