I believe that your meter is using Logical name referencing. Try to remove -r sn parameter. If it still fails, download GXDLMSDirector and try to connect with that. It will help you to get the correct parameters.
DLMS meters have different parameters that depend on the meter manufacturer. If one of them is wrong, the connection fails.
The sequence of the parameters doesn't affect this. Who is the manufacturer of the meters?
Can you add the first command that GXDLMSDirector sends so I can check what might cause this?
i am using genus meter , through Gurux director i am successfully communicate with client 16 & client 32. but through command line i can communicate only client 16 but not 32.
the command from Gurux director for cmd line is :-
-S COM9:9600:8NoneOne -c 32 -a Low -P 1A2B3C4D -C Encryption -T 3132333435363738 -A 736573636F656B616B33346167323631 -B 736573636F656B616B33346167323631 -D 736573636F656B616B33346167323631 -w 1 -f 128 -t Verbose
and i am using for cmd line that cmd is :
./bin/gurux.dlms.client.bin -S /dev/ttyUSB0 -c 32 -s 1 -a Low -P 1A2B3C4D -C Encryption -T 3132333435363738 -A 736573636F656B616B33346167323631 -B 736573636F656B616B33346167323631 -D 736573636F656B616B33346167323631 -g 1.0.0.2.0.255:2
but i am getting this error
cl_getObjectsRequest failed Deciphering error.
The original problem was that the meter returns "AARQRequest failed Rejected permanent" error.
Now the problem is that the meter returns "cl_getObjectsRequest failed Deciphering" error.
Can you add a hex trace so I can check the byte stream what is happening?
my this error removes when i used -o command, but i am not able to understand what file name i have to use with -o and where that file create.
can you help me out form this.
Your meter is returning an error when the association view is read. Can you read the association view with GXDLMSDirector? You can read it if you select "File" and "Refresh".
I am reading profile generic parameters,but unable to read from command line .
for that is i have to use -o parameter.
if yes than what file name & path i have to use.
The client example reads association view (list of objects that the meter can offer). That is needed to know what kind of objects the meter can offer. I believe that it might be useful if you play with GXDLMSDirector and get an idea of what DLMS meter can do and how to communicate with them.
yes i can properly communiate my meter with gurux director,i can read profile generic parameters & data with that.
but through Gurux CLI i can read only few parameters like RTC, Meter voltage , Meter current etc. but unable to read instanteneous data , Load profile, daily load, Billing etc.
i am using gurux C code and my command is :-
sudo ./bin/gurux.dlms.client.bin -h 2401:4900:4022:f9e2::2 -p 4059 -i WRAPPER -c 32 -a Low -P 1A2B3C4D -C Encryption -T 474F453030303030 -A 5470446C456B416B7470433136376162 -B 5470446C456B416B7470433136376162 -D 6565736C686C737567616C3036616263 -g 1.0.94.91.0.255:2
Connecting to 2401:4900:4022:f9e2::2:4059
close
InitializeConnection
GetAssociationView
-------- Reading Object ProfileGeneric 1.0.94.91.0.255
ReadObject failed ProfileGeneric 1.0.94.91.0.255:2 Invalid parameter.
Failed to read object ProfileGeneric 1.0.94.91.0.255 attribute index 2
All items are read.
Leave -g 1.0.94.91.0.255:2 out and the client application reads all the objects (all data) from the meter. You can modify the source code for your needs.
Hi,
Hi,
I believe that your meter is using Logical name referencing. Try to remove -r sn parameter. If it still fails, download GXDLMSDirector and try to connect with that. It will help you to get the correct parameters.
DLMS meters have different parameters that depend on the meter manufacturer. If one of them is wrong, the connection fails.
BR,
Mikko
I already tried with gurux
I already tried with gurux director.
for confirm my Auth keys etc.
it is working perfectly , i can connect & read data.
Hi,
Hi,
You can see the command line arguments when you select the device in GXDLMSDirector. Use them to establish the connection.
BR,
Mikko
yes i followed the same cmd
yes i followed the same cmd line arguments but still connection not establish, is there is issue with sequence of the parameters in cmd line.
Hi,
Hi,
The sequence of the parameters doesn't affect this. Who is the manufacturer of the meters?
Can you add the first command that GXDLMSDirector sends so I can check what might cause this?
BR,
Mikko
hi, thanks for your reply!!
hi, thanks for your reply!!
i am using genus meter , through Gurux director i am successfully communicate with client 16 & client 32. but through command line i can communicate only client 16 but not 32.
the command from Gurux director for cmd line is :-
-S COM9:9600:8NoneOne -c 32 -a Low -P 1A2B3C4D -C Encryption -T 3132333435363738 -A 736573636F656B616B33346167323631 -B 736573636F656B616B33346167323631 -D 736573636F656B616B33346167323631 -w 1 -f 128 -t Verbose
and i am using for cmd line that cmd is :
./bin/gurux.dlms.client.bin -S /dev/ttyUSB0 -c 32 -s 1 -a Low -P 1A2B3C4D -C Encryption -T 3132333435363738 -A 736573636F656B616B33346167323631 -B 736573636F656B616B33346167323631 -D 736573636F656B616B33346167323631 -g 1.0.0.2.0.255:2
but i am getting this error
cl_getObjectsRequest failed Deciphering error.
please help
Hi,
Hi,
Can you read the meter if you don't use "-g 1.0.0.2.0.255:2" parameter?
BR,
Mikko
no same error without OBIS
no same error without OBIS
hi ,
hi ,
any update about my query, its urgent.
Hi,
Hi,
The original problem was that the meter returns "AARQRequest failed Rejected permanent" error.
Now the problem is that the meter returns "cl_getObjectsRequest failed Deciphering" error.
Can you add a hex trace so I can check the byte stream what is happening?
BR,
Mikko
Hi sir,
Hi sir,
please find the logs
sudo ./bin/gurux.dlms.client.bin -S /dev/ttyUSB0 -c 32 -r ln -s 1 -a Low -P 1A2B3C4D -C Encryption -T 3132333435363738 -A 736573636F656B616B33346167323631 -B 736573636F656B616B33346167323631 -D 736573636F656B616B33346167323631 -i HDLC -t Verbose
InitializeConnection
TX: 7E A0 07 03 41 93 5A 64 7E
RX: 7E A0 20 41 03 73 3E 9D 81 80 14 05 02 01 00 06 02 01 00 07 04 00 00 00 01 08 04 00 00 00 01 69 6D 7E
TX: 7E A0 68 03 41 10 D4 F9 E6 E6 00 60 5A A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 31 32 33 34 35 36 37 38 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 31 41 32 42 33 43 34 44 BE 28 04 26 21 24 20 00 00 00 00 98 70 77 FC 87 11 05 63 A8 68 5B 96 43 4B 3C E0 78 A9 FA AD 59 6B 11 9D D9 BA 77 BC DC 54 DA 06 CC 7E
RX: 7E A0 56 41 03 30 7E FC E6 E7 00 61 48 A1 09 06 07 60 85 74 05 08 01 03 A2 03 02 01 00 A3 05 A1 03 02 01 00 A4 0A 04 08 47 4F 45 00 00 53 EF 04 BE 23 04 21 28 1F 30 00 00 17 BA 83 33 87 DA 3B 6A 2E F9 64 71 E5 5B 99 DC 85 0B B4 6C B0 C4 5E EF 26 63 F6 9C CB 0E 7E
GetAssociationView
TX: 7E A0 2C 03 41 32 9F 9F E6 E6 00 D0 1E 30 00 00 00 01 8C 2B 4F 4B BD 60 60 F4 2E C1 C1 E7 12 D9 17 F8 C2 36 D0 AC 0D 4C 69 DE 2E 58 A3 7E
RX: 7E A0 1A 41 03 52 E9 3D E6 E7 00 CC 82 00 0A 20 00 00 17 BB 6D DE F3 00 2B 5F 62 7E
cl_getObjectsRequest failed Deciphering error.
TX: 7E A0 07 03 41 53 56 A2 7E
RX: 7E A0 07 41 03 73 4C 45 7E
Deciphering error.
hi ,
hi ,
my this error removes when i used -o command, but i am not able to understand what file name i have to use with -o and where that file create.
can you help me out form this.
Thanks
Hi,
Hi,
Your meter is returning an error when the association view is read. Can you read the association view with GXDLMSDirector? You can read it if you select "File" and "Refresh".
BR,
Mikko
yes i can read with gurux
yes i can read with gurux director but the same coomand on command line is not working.
I am using gurux c code , do you have any idea.
Hi,
Hi,
Can you add a hex trace from GXDLMSDirector so I can compare the logs and check what is the difference?
BR,
Mikko
hi sir ,
hi sir ,
can you please tell me what is the role of outputFile in gurux Client C code,is thia file is created some where or what is the purpose of it.
waiting for your response.
thanks
Hi,
Hi,
If that is used the association view is saved for this file. In that way, you don't need to read it from the meter every time and reading is faster.
BR,
Mikko
hello sir,
hello sir,
Thanks for you response !
I am reading profile generic parameters,but unable to read from command line .
for that is i have to use -o parameter.
if yes than what file name & path i have to use.
pls suggest.
Thanks
hi ,
hi ,
is this parameter necessary for profile generic read.
what i have to use.
printf(" -o \t Cache association view to make reading faster. Ex. -o C:\\device.bin");
Hi,
Hi,
The client example reads association view (list of objects that the meter can offer). That is needed to know what kind of objects the meter can offer. I believe that it might be useful if you play with GXDLMSDirector and get an idea of what DLMS meter can do and how to communicate with them.
BR,
Mikko
yes i can properly communiate
yes i can properly communiate my meter with gurux director,i can read profile generic parameters & data with that.
but through Gurux CLI i can read only few parameters like RTC, Meter voltage , Meter current etc. but unable to read instanteneous data , Load profile, daily load, Billing etc.
i am using gurux C code and my command is :-
sudo ./bin/gurux.dlms.client.bin -h 2401:4900:4022:f9e2::2 -p 4059 -i WRAPPER -c 32 -a Low -P 1A2B3C4D -C Encryption -T 474F453030303030 -A 5470446C456B416B7470433136376162 -B 5470446C456B416B7470433136376162 -D 6565736C686C737567616C3036616263 -g 1.0.94.91.0.255:2
Connecting to 2401:4900:4022:f9e2::2:4059
close
InitializeConnection
GetAssociationView
-------- Reading Object ProfileGeneric 1.0.94.91.0.255
ReadObject failed ProfileGeneric 1.0.94.91.0.255:2 Invalid parameter.
Failed to read object ProfileGeneric 1.0.94.91.0.255 attribute index 2
All items are read.
pls suggest what wrong in the command
Hi,
Hi,
Leave -g 1.0.94.91.0.255:2 out and the client application reads all the objects (all data) from the meter. You can modify the source code for your needs.
BR,
Mikko
hello sir,
hello sir,
if i am trying without -g i am getting segmentation fault. that is why i am using -g
sudo ./bin/gurux.dlms.client.bin -h 2401:4900:4022:f9e2::2 -p 4059 -i WRAPPER -c 32 -a Low -P 1A2B3C4D -C Encryption -T 474F453030303030 -A 5470446C456B416B7470433136376162 -B 5470446C456B416B7470433136376162 -D 6565736C686C737567616C3036616263
Connecting to 2401:4900:4022:f9e2::2:4059
close
InitializeConnection
Segmentation fault
Hi,
Hi,
Can you add -t Verbose argument and add hex trace here so I can check what is happening from the bytes?
BR,
Mikko