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.
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.
issue in reading secure premier 300 meter
Hi
We have a issue in reading Secure meter (model: premier 300).
Gurux GXDLMSDirector: 8.0.1708.1801
Manufacture settings:
Flag ID:EHL
Name: Secure meter
Using logical name referencing: checked
keepinterval: 40
start protocol: DLMS
Addressing:
authenticatoin:none
client address
address(hex):10
server address
address type:Default
serial number formula
physical:1
logical:0
Device properties:
name:secure
manufacture:Secure meter
Logical name referencing:checked
start protocol:DLMS
media:serial
authentical:none
password:
waittime:7
client address: 10
address type:default
physical address:1
logical address:0
settings
serial port:COM11
Optical probe head with USB (IEC62056-21)
on Tool-->Read we are only getting the following values
AssociationLogicalname
0.0.40.0.0.255 Ch 0 current association
0.0.40.0.1.255 Ch 0association #1
Data
1.0.0.0.6.255 Ch. 0 Electricity ID #7
1.0.96.160.0.255 Man. specific
1.0.0.0.1.255 Ch. 0 Electricity ID #2
0.0.96.1.0.255 Ch. 0 Device ID 1, manufacturing number
0.0.42.0.0.255 Ch. 0 COSEM Logical device name
clock
0.0.1.0.0.255 ch 0 clock object #1
as per the manufacture the default authentication is ABCD001
but could not able to establish high or low level connection to the meter with the given default password.
GXDLMSDirector 8.0.1708.1801
Log created 16:07:01
16:07:06 Initializing serial connection.
16:07:06 Send SNRM request.
7E A0 14 03 21 93 63 E7 81 80 08 05 02 02 00 06 02 02 00 43 B0 7E
16:07:06 Received data
7E A0 20 21 03 73 73 98 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
16:07:06 Parsing UA reply.<CR><LF>81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01
16:07:06 Parsing UA reply succeeded.
16:07:06
7E A0 2B 03 21 10 FB AF 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 60 1E DE FF FF 88 A0 7E
16:07:06 Received data
7E A0 37 21 03 30 6C 7C 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 00 10 02 00 00 07 1C EA 7E
16:07:06 Parsing AARE reply succeeded.
16:07:21 Read object type AssociationLogicalName index: 2
7E A0 19 03 21 32 6F D8 E6 E6 00 C0 01 C1 00 0F 00 00 28 00 01 FF 02 00 2A 4F 7E
16:07:22 Received data
7E A2 03 21 03 52 EE 14 E6 E7 00 C4 01 C1 00 01 08 02 04 12 00 0F 11 00 09 06 00 00 28 00 00 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 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 01 04 02 02 0F 01 03 00 02 02 0F 02 03 00 02 02 0F 03 03 00 02 02 0F 04 03 00 02 04 12 00 0F 11 00 09 06 00 00 28 00 01 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 01 00 02 03 0F 07 16 00 00 02 03 0F 08 16 01 00 01 04 02 02 0F 01 03 00 02 02 0F 02 03 00 02 02 0F 03 03 00 02 02 0F 04 03 00 02 04 12 00 01 11 00 09 06 01 00 00 00 06 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 01 11 00 09 06 01 00 60 A0 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 01 11 00 09 06 01 00 00 00 01 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 01 11 00 09 06 00 00 60 01 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 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 08 11 00 09 06 00 00 01 00 00 FF 02 02 01 09 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 00 00 02 03 0F 04 16 00 00 02 03 0F 05 16 00 00 02 03 0F 06 16 00 00 02 03 0F 07 16 00 00 02 03 0F 08 16 00 00 02 03 0F 09 16 00 00 01 06 02 02 0F 01 03 00 02 02 0F 02 03 00 02 02 0F 03 03 00 02 02 0F 04 03 00 02 02 0F 05 03 00 02 02 0F 06 03 00 09 4A 7E
16:07:22 Read object type Data index: 2
7E A0 19 03 21 54 5F DE E6 E6 00 C0 01 C1 00 01 01 00 00 00 06 FF 02 00 59 E6 7E
16:07:22 Received data
7E A0 19 21 03 74 5D 59 E6 E7 00 C4 01 C1 00 09 07 45 53 4C 2D 30 30 32 8F 8F 7E
16:07:22 Read object type Data index: 2
7E A0 19 03 21 76 4F DC E6 E6 00 C0 01 C1 00 01 01 00 60 A0 00 FF 02 00 B6 C0 7E
16:07:22 Received data
7E A0 53 21 03 96 58 57 E6 E7 00 C4 01 C1 00 01 05 02 02 09 06 01 00 01 08 00 FF 12 00 DD 02 02 09 06 01 00 05 08 00 FF 12 00 D9 02 02 09 06 01 00 08 08 00 FF 12 00 DA 02 02 09 06 01 00 09 08 00 FF 12 00 D8 02 02 09 06 01 00 94 08 00 FF 12 00 D4 56 0F 7E
16:07:22 Read object type Data index: 2
7E A0 19 03 21 98 3F D2 E6 E6 00 C0 01 C1 00 01 01 00 00 00 01 FF 02 00 78 B1 7E
16:07:22 Received data
7E A0 19 21 03 B8 3D 55 E6 E7 00 C4 01 C1 00 09 07 4D 32 58 37 47 30 37 D6 0F 7E
16:07:22 Read object type Data index: 2
7E A0 19 03 21 BA 2F D0 E6 E6 00 C0 01 C1 00 01 00 00 60 01 00 FF 02 00 89 A0 7E
16:07:23 Received data
7E A0 1A 21 03 DA E4 30 E6 E7 00 C4 01 C1 00 09 08 58 43 34 33 36 37 38 33 1A 46 7E
16:07:23 Read object type Data index: 2
7E A0 19 03 21 DC 1F D6 E6 E6 00 C0 01 C1 00 01 00 00 2A 00 00 FF 02 00 12 80 7E
16:07:23 Received data
7E A0 1B 21 03 FC 6B 68 E6 E7 00 C4 01 C1 00 09 09 45 48 4C 45 33 54 78 78 78 B9 E5 7E
16:07:23 Read object type Clock index: 2
7E A0 19 03 21 FE 0F D4 E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E
16:07:23 Received data
7E A0 1E 21 03 1E 20 C2 E6 E7 00 C4 01 C1 00 09 0C 07 E1 09 05 02 10 07 11 FF 80 00 00 C1 09 7E
Regards
Anand
Reading from SECURE Premier 300 meter
Hi,
Select Indian Standard as meter manufacturer. Your Client address is wrong.
With Low authentication it must be 32 (0x20).
BR,
Mikko
Hi
Hi
selected indian manufacture
client address set to 32.
Trace:
<- 17:13:27 7E A0 14 03 65 93 65 C6 81 80 08 05 02 02 00 06 02 02 00 43 B0 7E
-> 17:13:27 7E A0 20 65 03 73 64 FD 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
<- 17:13:27 7E A0 43 03 65 10 C1 F2 E6 E6 00 60 35 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 09 80 07 41 42 43 44 30 30 31 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 40 1E 1C FF FF 2E 34 7E
-> 17:13:27 7E A0 37 65 03 30 7B 19 E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 01 A3 05 A1 03 02 01 0D BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 14 02 00 00 07 AF 3C 7E
Log:
GXDLMSDirector 8.0.1708.1801
Log created 17:13:31
17:16:48 Initializing serial connection.
17:16:48 Send SNRM request.
7E A0 14 03 41 93 36 82 81 80 08 05 02 02 00 06 02 02 00 43 B0 7E
17:16:48 Received data
7E A0 20 41 03 73 3E 9D 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
17:16:48 Parsing UA reply.<CR><LF>81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01
17:16:48 Parsing UA reply succeeded.
17:16:48
7E A0 43 03 41 10 92 B6 E6 E6 00 60 35 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 09 80 07 41 42 43 44 30 30 31 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 40 1E 1C FF FF 2E 34 7E
17:16:48 Received data
7E A0 37 41 03 30 21 79 E6 E7 00 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 01 A3 05 A1 03 02 01 0D BE 10 04 0E 08 00 06 5F 1F 04 00 00 10 14 02 00 00 07 AF 3C 7E
17:16:48 Disconnect request
Gurux.DLMS.GXDLMSException: Connection is permanently rejected. Authentication failure.
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)
even checked with meter manual for password. it say the same
13.1 Active mode
In active mode, half-duplex asynchronous communication is supported through two communication ports – IEC 1107 port and RS-232. While the default baud rate for is 9600 baud, Premier 300 supports only the DLMS protocol for communication in active mode. A secure link must be first established between the server (Premier 300 in this case) and the client (like BCS). All communication is standard OBIS code profile based where a client queries for required information in the form of standard OBIS codes. The server then responds to those OBIS codes in a standard profiles.
Default password for meter readings is ABCD001
Reading from SECURE Premier 300 meter
Hi,
Your meter is returning AuthenticationFailure error. Check your password from meter vendor and is High authentication supported. Password can be different than Low authentication.
BR,
Mikko
Reading from SECURE Premier 300 meter
Hi
We were able to get a password for HIGH authentication for access.
But, Now we are getting the following error while establishing the connection
Error:
:service Error write exception. service unsupported."
Trace:
GXDLMSDirector 8.0.1708.1801
Log created 13:33:54
13:33:57 Initializing serial connection.
13:33:57 Send SNRM request.
7E A0 14 03 61 93 05 A1 81 80 08 05 02 02 00 06 02 02 00 43 B0 7E
13:33:57 Received data
7E A0 20 61 03 73 05 9E 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
13:33:57 Parsing UA reply.<CR><LF>81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01
13:33:57 Parsing UA reply succeeded.
13:33:57
7E A0 4C 03 61 10 58 27 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 63 1B 03 09 5A 61 1F 4C 06 56 13 66 1D 5E 16 51 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 60 5E DE 02 00 9F 6B 7E
13:33:57 Received data
7E A0 58 61 03 30 07 51 E6 E7 00 61 4A 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 66 25 EC 7B 66 25 EC 7B 66 25 EC 7B 66 25 EC 7B A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E BE 10 04 0E 08 00 06 5F 1F 04 00 00 18 1C 02 00 00 07 E7 72 7E
13:33:57 Authenticating
7E A0 2B 03 61 32 8D EB E6 E6 00 C3 01 C1 00 0F 00 00 28 00 00 FF 01 01 09 10 C0 F8 51 1E CD 9A 1B 51 38 B6 D2 84 14 0C B4 A0 46 FA 7E
13:33:57 Received data
7E A0 10 61 03 52 7C E2 E6 E7 00 0E 06 03 02 91 24 7E
Gurux.DLMS.GXDLMSConfirmedServiceError: ServiceError Write exception. Service Unsupported
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)
Can we know the possible cause?
Regards
SECURE Premier 300 meter
Hi,
It seems that your meter is not supporting High authentication. Contact your meter vendor and ask if there is a new firmware available where it's added.
BR,
Mikko
ServiceError Write exception. Service Unsupported
Hi
after getting the HIGH level authentication from the meter manufacture i am getting the following error
Trace:
GXDLMSDirector 8.0.1708.1801
Log created 18:05:08
18:05:10 Initializing serial connection.
18:05:10 Send SNRM request.
7E A0 14 03 61 93 05 A1 81 80 08 05 02 02 00 06 02 02 00 43 B0 7E
18:05:10 Received data
7E A0 20 61 03 73 05 9E 81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01 6F EF 7E
18:05:10 Parsing UA reply.<CR><LF>81 80 14 05 02 02 00 06 02 02 00 07 04 00 00 00 01 08 04 00 00 00 01
18:05:10 Parsing UA reply succeeded.
18:05:10
7E A0 4C 03 61 10 58 27 E6 E6 00 60 3E A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 02 AC 12 80 10 16 1F 00 25 41 20 68 45 30 53 60 0B 73 1B 02 1B BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 40 1E 1C 02 00 0D 46 7E
18:05:10 Received data
7E A0 58 61 03 30 07 51 E6 E7 00 61 4A 88 02 07 80 89 07 60 85 74 05 08 02 02 AA 12 80 10 EA F8 12 B8 EA F8 12 B8 EA F8 12 B8 EA F8 12 B8 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 0E BE 10 04 0E 08 00 06 5F 1F 04 00 00 18 1C 02 00 00 07 4E FF 7E
18:05:10 Authenticating
7E A0 2B 03 61 32 8D EB E6 E6 00 C3 01 C1 00 0F 00 00 28 00 00 FF 01 01 09 10 73 14 6B 50 1F E9 1C 19 B1 60 71 63 45 AA CA C8 82 D6 7E
18:05:10 Received data
7E A0 10 61 03 52 7C E2 E6 E7 00 0E 06 03 02 91 24 7E
Gurux.DLMS.GXDLMSConfirmedServiceError: ServiceError Write exception. Service Unsupported
at GXDLMSDirector.GXDLMSDevice.InitializeConnection()
at GXDLMSDirector.MainForm.Connect(Control sender, Object[] parameters)
Regards
Reading from SECURE Premier 300 meter
Hi,
You should ask new firmware from the meter manufacturer.
BR,
Mikko
Unable to read data
Hi,
I am using premier 300 energy meter, and i am trying to read data from GURUX DLMSDirector tool, but unfortunately in the manufacture section there is no option for SECURE METER, so i am trying with Indian Standard. Still not able to read the data from the meter. Can Anyone suggest how to do the same.
Thank you.
Reading data from Secure 300 meter
Hi,
I have established low level authentication connection using the password ABCD0001.
I could see all instantaneous parameters such as I, V, KW, but I could not get the Energy(Kwh) values.
Pls. inform whether getting the energy value in low level authentication is supported and if so help me how to get the same.
Thank you.
Hi
Hi
you will get the value of KWH under the Profile Generic in low authentication ( if you haven't checked yet)
Though its not the instantaneous value, it might be helpful.
Under profile Generic:
1.0.98.1.0.225--->1.0.148.8.0.225
Regards
Anand
Connecting Secure 300 data with HES
Hi,
Thanks for the reply.
I am able to read the KWH data under the profile generic using Gurux dlms client.
Inorder to integrate with Head end System (Wisdom make), I need the meter to initialize the communication with the server. Because, our HES doesnt initialize the communication. The meter is first required to connect the HES using Sl.No. of meter.
How to make this happen. Can somebody help me.
Regards,
velan
Hi,
Hi,
I believe, the request needs to come from the Head end system(HES) first, if i am not wrong. As the meter needs to authenticate the request before providing the access to its values,especially if you need KWH values. If ,your HES doesn't initialize, then you might need to put a IoT gateway in-between the Meter and HES. This kind of setup is the most basic of all smart grids and IoT based Energy Management System(EMS) solution architecture.
Also, you may take a look at this site (https://www.icube.ch/) for some solutions for meter reading.
Regards
Connecting Secure 300 data with HES
Hi,
Meters can also start the communication. Server address is defined on "Auto Connection".
When meter starts the connection, you need to read "Logical Device Name" to identify the meter.
Then you can read the needed data.
BR,
Mikko
Connecting Secure 300 data with HES
Hi,
Thank you Mr. Anandasundaraman for your reply. As u said, if the HES do not initialize communication, we may need IoT Gateway like solutions.
Mikko Sir as you mentioned that Meters can also start the communication, pl. inform whether in HDLC connection with TCP/IP wrapper is possible as per DLMS standards.
Thankyou
Connecting Secure 300 data with HES
Hi,
I don't know is Secure 300 supporting WRAPPER, but if it's you can use our libraries to read it.
BR,
Mikko
Hello,
Hello,
Is there a way to parse this data? If there is a Hex response what does each byte stand for?
Ambimat.
Hi Ambimat.,
Hi Ambimat.,
Please, if you have a new question, create a new topic.
https://gurux.fi/forum
I'll answer your question there.
BR,
Mikko
Hi Velane23,
Hi Velane23,
Could you please share the wiring diagram of rj11 to rs232 which you used for premier 300. It will be really helpful, my communication with different wiring has been failing, I am really frustrated changing so many things. Please share which work for premier 300. Thanks in advance.
Thanks,
Gopi Krishna M
Pin details of RJ11 of Secure
Pin details of RJ11 of Secure meter
Pin 1is RX - to be connected to Pin 3 of Rs-232
Pin 2 is TX - to be connected to Pin 2 of RS-232
Pin 3 is Gnd - to be connected to pin 5 of RS 232
Pin 4 is RTS - to be connected to Pin 7 &8 (shorting 7&8) of RS-232