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.
Forums
I am trying to connect via DLMS over TCP (in Wrapper mode) to a WFET-1600 (Wasion) device.
http://www.wasion.com/EN/pro/468.html
Communication is not established at the authorization stage, while the manufacturer's test software (also with DLMS) is working normally.
Here is the test software authorization request:
[09:05:04 962] S: 00 01 00 01 00 01 00 44 60 42 A1 09 06 07 60 85 74 05 08 01 01 A6 0A 04 08 57 53 45 00 00 00 00 01 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 0A 80 08 30 30 30 30 30 43 37 32 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F 00 00
Here is the Gurux request:
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 30 30 30 30 30 30 30 30 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF
The difference is that the test software contains the following set of bytes:
A6 0A 04 08 57 53 45 00 00 00 00 01
What is this set of bytes for, and how you can activate device polling through the DLMS Director.
If required, I can provide access to the device (it is available via a static IP).
https://drive.google.com/file/d/1IyaWWLxBSDKUGuLG61EKDwrjIwCc7Xm_/view?…
I attach the polling log of the test utility and Director.
Hi,
Hi,
You try to connect using Low-level authentication. Another application is using HighGMac authentication. Change authentication level and set correct keys to the "Secured connections" -tab.
BR,
Mikko
Clarified the parameters,
Clarified the parameters, registered. The settings are the same as in the screenshot.
Now the request is being formed:
00 01 00 01 00 01 00 44 60 42 A1 09 06 07 60 85 74 05 08 01 02 A6 0A 04 08 57 53 45 00 00 00 00 01 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 0A 80 08 30 30 30 30 30 43 37 32 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 1C 03 20 FF FF
But the device resets it anyway.
I am attaching a new log
https://drive.google.com/file/d/1G_h_wefazClFi5E624B6fppajW_wT14L/view?…
Hi,
Hi,
You need to check "Logical Name Referencing" from the "Device Settings" tab. Wasion has started to use Logical Name Referencing for the newer meters.
BR,
Mikko
I started to get the
I started to get the association and immediately failed with an error. I am attaching the log.
Is there an error in the device?
https://drive.google.com/file/d/1G_h_wefazClFi5E624B6fppajW_wT14L/view?…
Hi,
Hi,
The good thing is that your settings are correct. You can make the connection to the meter.
The meter is returning ciphered error and that is strange. Your message looks like the same as another application generates.
Try to add clock object manually. Select "Add Object..." from "Edit" menu. Select Clock as object type and set "0.0.1.0.0.255" to logical name. Press OK. Make connection to the meter and try to read clock object. If you can read it, your meter is not supporting association view and you need to add all objects manually. If you can't read it, try to connect using Secured Connection. Change Security to "AuthenticationEncryption" from "Secured Connections" tab.
BR,
Mikko
I tried to read the time - it
I tried to read the time - it gave an error "Invalid Command"
Log:
https://drive.google.com/file/d/1G_h_wefazClFi5E624B6fppajW_wT14L/view?…
Hi,
Hi,
Select "Supported services" tab in Device settings. Un-check Access and try again.
BR,
Mikko
Hi,
Hi,
I believe that you can connect only with the ciphered connection because the meter returns a ciphered error.
BR,
Mikko
In the log generated by the
In the log generated by the test utility - in what mode is the time reading? Authenticated and encrypted or not? P.S. Сannot see this in the utility itself.
Hi,
Hi,
In your picture above the Security is None. Try to change it to AuthenticationEncryption. Reading time depends on the meter model and how it's configured. You can usually read the time without authentication or ciphered connection, but it might be that the meter is configured in that way that only ciphered connections are allowed.
BR,
Mikko
I meant what type of
I meant what type of connection to the log from the test software (in which the time is read).
From it you can understand what is used - Authentification, Encryption or Authentification and Encryption?
Hi,
Hi,
There is only AARQ message that you added to the first post. It's not using the ciphered connection, but I don't know if that changed later. Can you read your meter totally with another application and add the trace to the Google drive and I can check the correct parameters for you.
BR,
Mikko
Do you mean to do
Do you mean execute the command GetAssociation?
I did not see such an opportunity in this software - there is immediately a ready-made list of variables that can be read.
I can read energies or current values - is that enough?
Hi,
Hi,
Current values are enough.
BR,
Mikko
Attached is a log file.
Attached is a log file.
Can you understand the connection parameters from it?
https://drive.google.com/file/d/12W2BkCNMvykBSuZOGmvhaIh5OQ79930B/view?…
Hi,
Hi,
You need to ask for block cipher and authentication keys from the meter manufacturer. Messages are encrypted.
BR,
Mikko
They sent me a document like
They sent me a document like this:
https://drive.google.com/file/d/1VR7qVsKjPNwmIYTsvuYSFPRME7MsUpu1/view?…
EK - Block cipher key?
AK - authentication key?
Dedicated key what is in this document?
System title- it says that the last 5 digits are the serial number for the server. Is it being asked somewhere in Dlms Director?
Hi,
Hi,
EK is the block cipher key and AK is the authentication key. Leave the dedicated key empty. Basically, you should be able to use any client system title, but use what they have proposed: WSE00001
Don't set meter system title. It's updated when the connection is established.
BR,
Mikko
What to put in a challenge?
What to write in a challenge?
Hi,
Hi,
You should be able to leave it empty. Then it's generated for each connection.
BR,
Mikko
Installed as in the
Installed as in the screenshot - the device does not respond at all.
Answer:
00 01 00 01 00 01 00 5F 60 5D A1 09 06 07 60 85 74 05 08 01 03 A6 0A 04 08 57 53 45 30 30 30 30 31 8A 02 07 80 8B 07 60 85 74 05 08 02 05 AC 12 80 10 04 61 12 49 4A 00 52 66 6C 5A 1C 35 56 70 37 1C BE 23 04 21 21 1F 10 00 00 00 00 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF F6 2A FC 46 8A 39 AC 9F 70 D8 8B 88
The manufacturer gave the wrong keys?
Hi,
Hi,
I just notest that the meter is not using ciphering when the connection is established. It's starting to use ciphering when the first read is made. This is not correct. Even ciphering is used all the time or then it's not used at all.
You need to ask for the new firmware from the meter manufacturer where this is fixed.
BR,
Mikko