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.
By ale282, 13 July, 2015
Hi Mikko,
we should retrieve data from a Kamstrup Omnipower 3phase smart meter. We asked to Kamstrup some descriptions about their DLMS implementation and we obtained this information for the low level access (to read electrical runtime values and load profiles)
Primary Module interface Association with Low Level security (Password protected)
- Client SAP: 18
- Server SAP: 16
- Context name: Logical name addressing
- Mechanism name: Low Level security. Password default is ‘12345’
- Conformance: GET, Block transfer with GET, SET, ACTION, SELECTIVE ACCESS
Optical interface Association with Low Level security (Password protected)
- Client SAP: 19 1
- Server SAP: 16
- Context name: Logical name addressing
- Mechanism name: Low Level security. Password default is ‘12345’
- Conformance: GET, Block transfer with GET, SET, ACTION, SELECTIVE ACCESS
Association used from Module_Port_2 interface:
CCC Module interface Association with Low Level security (Password protected):
- Client SAP: 20 2
- Server SAP: 16
- Context name: Logical name addressing
- Mechanism name: Low Level security. Password default is ‘12345’
- Conformance: GET, Block transfer with GET, SET, ACTION, SELECTIVE ACCESS
We succeed reading public values with the configuration that you suggest (client 16 server 1 no password) but with the settings suggested by Kamstrup it's impossible to connect to the meter. This is the DLMSDirector log (version 7.0.47.1).
Log created 10:20:41
10:20:51 Initializing Network connection.
10:20:52 Send SNRM request.
7E A0 20 01 25 93 A5 0B 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
10:20:57 Failed to receive reply from the device in given time.
Have you experience with this smart meter?
Thank you
BR
Kamstrup Omnipower 3Phs
Hi,
Check your settings. It seems that Client and server IDs are wrong. In trace your values are following:
Server ID: 0x0
Client ID: 0x49
BR,
Mikko