Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.
doc
Page 1 of 6
Release notes for
com.energyict.protocolimpl.dlms.DLMSZMD
Protocol Class, supporting
Landis&Gyr / Siemens ZMD Dialog Meter
Copyright 2010 EnergyICT NV
Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.doc
Page 2 of 6
1. Remarks - Compatibility
1 Implements HDLC IEC 13239 protocol
2 Siemens DLMS uses short name referencing
3 Supports Siemens ZMD/ZFD dialog meters
4 Supports Siemens ZMQ meters (09/11/07)
2. Revisions
Date Protocol Description Released in:
version
******** ****** Initial Release EICT EIServer v6
1/11/03 1.15 Default meter registers added EIServer v6.X
* Change to mechanism to handle powerfails
27/01/04 1.18 EIServer v6.X
* Serial number & Device ID will now be checked
30/08/04 1.25 Add obis code mapping for register reading EIServer v6.7
Bugfix negative register values + More robust
08/11/04 1.29 ProtocolImpl v6.7.1.5
HDLC layer
28/01/05 1.30 Minor changes ProtocolImpl v6.7.9.1
Improved register reading
23/03/05 1.31 Changed header to be compatible with protocol ProtocolImpl v6.7.9.10
version tool
30/03/05 1.32 Improved register reading, configuration data ProtocolImpl v6.7.9.11
11/10/06 1.24.4.2 Add support for cumulative channels ProtocolImpl v6.9.5.18
14/06/07 1.31 Compatibility fix for the addressing mode ProtocolImpl v7.1.17.32
09/11/07 1.40.2.1 Extend to read ZMQ meter event log ProtocolImpl v7.1.17.32.15
14/11/07 1.42.2.1 Extend to read ZMQ meter event log ProtocolImpl v7.5.7.2
Added channel map to configure the cumulative
wrap value. Made register readings more robust.
27/03/09 1.42.2.1 ProtocolImpl v7.5.7.74
Major changes in the underlying dlms framework
(security, authentication, encryption, …)
Updated protocol version to new format: yyyy-
MM-dd. This version is the most up to date Protocolimpl 8.5.21
22/12/10 2010-12-22
protocol and contains all the previous mentioned Protocolimpl 8.9.4
changes.
Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.doc
Page 3 of 6
3. Communication Profile
Function Supported Notes
Read Meter Y Reads out the specified meter registers
Readings
Read Demand Y Performs a profile data readout starting from last reading
Values.
Read Meter Y Read the Meter events, starting from last reading
Events
Write Time Y Automatically set of time within boundaries (clock difference)
All Read N Not available
(Ad Hoc)
Initialize N Not available
(Ad Hoc)
Force Time Y Not available in EIServer (1)
(Ad Hoc)
Daisy Chaining Y Available, use ServerLowerMacAddress
4. RTU Properties (AMR)
Fields Default Description
Address / DeviceID <none> The ID of the meter eg. LGZ75000000
Serial number <none> The Serial number of the meter eg. 75000000
Password <none> Password (! should match the security-level)
NodeAddress <none> The address used in a multi-drop / handheld configuration
Remark:
The Password always need to be filled in, only NodeAddress, Address or Serial Number can be left
empty in case you don’t want to use/check them.
5. Custom Properties (protocol specific)
Fields Default Description
ServerUpperMacAddress 1 HDLC Logical device address
ServerLowerMacAddress 0 HDLC Physical device address
(Used in Multi Drop / Daisy chaining situations)
ClientMacAddress 32 HDLC client address
SecurityLevel 1 Logon association level
RequestClockObject 0 Only for testing.
RequestTimeZone 0 Requests the device time zone from meter. If set to 1, the
EIServer / Protocoltester specified device time zone is not
used for time calculation.
!!! If you’re not sure of the meter configuration, set it to 0.
ExtendedLogging 0 0 = off, if 1, Extended logging can be used to get a list of
all possible registers configured in the meter.
AddressingMode -1 1, 2 or 4 byte addressing mode. –1 means addressing mode
1 or 4 depending on the server upper and lower
addresses. This property should not be changed in normal
circumstances.
EventIdIndex -1 If different from –1, then EventIdIndex used as event id
Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.doc
Page 4 of 6
(from V1.40.2.1) index in the event log data structure. This is not needed in
normal circumstances.
ChannelMap <none> With the ChannelMap you can set a cumulative wrap value
for each channel individually.
Use a ‘+’ and a number of digits to indicate the overflow
value and use a colon to separate the channels.
Ex.: +9:+4:+7:+3
Overflow channel 1 : 1 000 000 000
Overflow channel 2 : 10 000
Overflow channel 3 : 10 000 000
Overflow channel 4 : 1 000
6. Custom Properties (general)
Fields Default Description
Timeout 10000 Protocol timeout fail
Retries 5 Max nr of protocol errors before end of communication
DelayAfterFail 3000 Delay in ms after a protocol error
Remark:
When using ProtocolTester, Edit->Protocol Properties also contains the general CommServer settings,
editable via the dialogs in EIServer. Following is a list of these settings.
RoundtripCorrection 0 Offset in ms to the get/set time
MinimumTimeDiff 5 Minimum difference between meter and system clock
before a write clock will happen.
MaximumTimeDiff 20 Maximum difference between meter and system clock. If
the difference > maximum difference, an exception will be
generated and the task will fail!
CorrectTime 1 Enable or disable the setting of the clock in the meter.
Set to 0 to avoid that the protocol will set the clock.
ProfileInterval 900 Integration time of the meter. This setting must be the
same as the setting read from the meter. If not, an
exception will be generated and the task will fail.
7. Meter events
Meter Events read-out from the logbook
Logbook event Code Manufacturer’s Code Manufacturer’s Description
Fatal error 11 0x00000001 Fatal error
Other 0 0x00000004 Corrupted measurement
Set clock 6 0x00000020 Time date adjusted
Power up 2 0x00000040 Power up
Power down 1 0x00000080 Power down
Other 0 0x00002000 Log cleared
Clear data 12 0x00004000 Load profile cleared
Meter Events created from the interval status bits or other profile events
Logbook event Code Manufacturer’s Code Manufacturer’s Description
Corrupted 0x20 0x00000004 Corrupted measurement
Shortlong 0x04 0x00000020 Time date adjusted
Power up 0x02 0x00000040 Power up
Power down 0x01 0x00000080 Power down
Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.doc
Page 5 of 6
8. Interval status
Interval Status bits read-out from the meter
Status bit Code Manufacturer’s Code Manufacturer’s Description
Corrupted 0x20 0x00000004 Corrupted measurement
Shortlong 0x04 0x00000020 Time date adjusted
Power up 0x02 0x00000040 Power up
Power down 0x01 0x00000080 Power down
Interval Status bits created from meter events
-> See “EIServer Events to Interval Status bit” document for more information.
Remark:
If more than one event occurs in the same interval, the interval status will be a combination of them.
9. Meter registers
EIServer is using the Standard OBIS Codes (2) to map registers to meter specific registers.
Not all OBIS codes will be supported by each protocol / meter configuration.
The following list displays an overview of all mappings made in EIServer for this protocol.
A : B : C : D : E : F Manufacturer Description – (Optional: Code)
1 1 1 D E F Active power+ all phases
1 1 2 D E F Active power- all phases
1 1 5 D E F Reactive power QI all phases
1 1 6 D E F Reactive power QII all phases
1 1 7 D E F Reactive power QIII all phases
1 1 8 D E F Reactive power QIV all phases
1 1 16 D E F Active power QI+QIV-QII-QIII all phases
1 1 0 4 3 255 Transformer ratio - voltage (General purpose)
1 1 0 4 2 255 Transformer ratio - current (General purpose)
0 0 96 6 0 255 Battery use time counter
1 1/0 0 1 0 255 Billing counter
1 1/0 0 1 2 F Billing point timestamp (0 <= F >= 99)
Remarks:
Actual registers fully depend on the meter configuration. The above configuration is just an example of
how the meter could be configured. To get more info, we advise to use ‘ExtendedLogging’.
If any value in group C to F contains a value between 128 and 254 the whole code is considered as
manufacturer specific.
If the OBIS code contains a letter, convert them using one or more of the following rules:
A field: (no rules)
B field: (no rules)
C field: (no rules)
D field: 8 = energy / 6 = maximum demand / 2 = cumulative maximum demand
E field: 0 = total value (In case of energy) / 1..N = tariff 1..N
F field: 255 = current value / 0 = last billing point / N = last–N billing point
Landis&Gyr_Siemens ZMD Dialog DLMS Release Note.doc
Page 6 of 6
Register group Value From time To time Event time
Energy registers, Value of the empty Billing period event empty
current and tariff register timestamp (if billing is
+ Rising demand used) else: read time
of the register
Maximum demand Value of the empty Billing period event Maximum demand
registers register timestamp (if billing is event timestamp
used) else: read time
of the register
Cumulative max. Value of the empty Billing period event empty
demand registers register timestamp (if billing is
used) else: read time
of the register
Billing period empty empty Billing period event Billing period event
timestamp timestamp timestamp
All other registers Value of the empty Read time of the End of billing period
register register (if billing is used)
Remark:
This table explains how the RTU Register Readings are calculated in EIServer.
10. Additional information
1 If needed, use protocoltester to force a clock setting in the meter.
2 OBIS codes are a combination of six value groups: A : B : C : D : E : F
Group A defines the characteristic of the data (electricity, gas, heat, water, …).
Group B defines the channel number, i.e. the number of the input (channel) of a metering
equipment having several inputs for the measurement of energy (default=channel 1).
Group C defines the abstract or physical data items: e.g. current, voltage, power, volume,
… The definitions are depending on group A.
Group D defines types, or the result of the processing of physical quantities identified with
the value groups A and C, according to various specific algorithms. The algorithms can
deliver energy and demand quantities as well as other physical quantities (e.g. time
integral).
Group E defines the further processing of measurement results identified with value groups
A to D to tariff registers, according to the tariff(s) in use. For abstract data or for
measurement results for which tariffs are not relevant, this value can be 0 = total value/no
tariff.
Group F defines the storage of data, identified by value groups A to E, according to
different billing periods. Where this is not relevant, this value group can be 255 = current
value.
More information can be found in the international standard (2002) IEC62056-61 (OBIS
Object Identification System)
