Actaris SL7000 DLMS Release Note.

doc
Page 1 of 7

Release notes for

com.energyict.protocolimpl.dlms.DLMSLNSL7000
Protocol Class supporting,
ACTARIS SL7000 Energy Meter

Copyright  2009 EnergyICT NV

Actaris SL7000 DLMS Release Note.doc
Page 2 of 7

1. Remarks - Compatibility

1 Tested SL7000 firmware versions: V1.7, V2.2, V2.3, V3.3, V3.5

2 Implements HDLC IEC 13239 protocol
3 Actaris DLMS uses long name referencing
4 Protocol version previous to 2009-05-26 see 10.4 (Additional information, part 4)

2. Revisions

Date Protocol Description Released in:

version
******** ****** Initial Release EICT EIServer v6
1/11/03 1.17 Default meter registers added EIServer v6.X
27/01/04 1.19 * Change to mechanism to handle power fails EIServer v6.X
* Serial number & Device ID will now be checked
08/11/04 1.24 Reengineered to use cosem package EIServer v6.X
17/11/04 1.25 Implemented logbook ProtocolImpl v6.7.1.5
Made HDLC layer more robust
23/03/05 1.29 * Improved registerreading ProtocolImpl V6.7.9.10
* Changed header to be compatible with protocol version
tool
31/03/05 1.30 Handle DatacontainerException ProtocolImpl V6.7.9.12
10/09/05 1.30.2.1 Bugfix historical maximumdemand registers ProtocolImpl V6.7.9.18
14/06/07 1.35 Compatibility fix for the addressing mode ProtocolImpl 7.1.17.32
25/04/08 1.38.2.2 Bugfix missing hour values with 10min profile interval Protocolimpl7.5.7.29
21/04/09 2009-04-21 Made register readings more robust for failures. Protocolimpl v8.1.28
Protocolimpl v8.3.7
26/05/09 2009-05-26 Fixed billing timestamp issue. Protocolimpl v8.1.30
29/06/09 2009-06-29 Fixed billing registers issue. Protocolimpl v8.1.31

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 (from the SL7000 Logbook), starting from
Events last reading
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
Actaris SL7000 DLMS Release Note.doc
Page 3 of 7

4. RTU Properties (AMR)

Fields Default Description

Address / DeviceID <none> The Serial number of the meter, eg. 30300000
Serial number <none> The Serial number of the meter, eg. 30300000
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 17 HDLC Logical device address
ServerLowerMacAddress 17 HDLC Physical device address
ClientMacAddress 1 HDLC client address (SAP –Association Objects)
SecurityLevel 1 Logon association level (only 1 is used, everything > 1 will
automatically default to 1)
FirmwareVersion ANY SL7000 firmware version (use in case of protocol problems)
Example: for firmware V1.7, it must be set to 1.7
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. This meter only supports 0,
because there is no timezone in the clock object of the
meter!
ExtendedLogging 0 0 = off, if 1, Extended logging can be used to get a list of
all possible registers configured in the meter.

6. Custom Properties (general)

Fields Default Description

Timeout 10000 Protocol timeout fail in msec
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.
Actaris SL7000 DLMS Release Note.doc
Page 4 of 7

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.
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.

7. Meter events

Meter Events read-out from the logbook

Logbook event Code Manufacturer’s Code Manufacturer’s Description
Other 0 1 Asynchronous end of interval
Billing action 17 2 Periodical end of billing
Billing action 17 3 Programmed end of billing
Billing action 17 4 Asynchronous end of billing
Other 0 5 Index DPM
Other 0 6 Restore internal index
Other 0 7 Index CI
Other 0 8 Day profile CL
Other 0 9 Restore internal day profile
Other 0 10 Day profile CI
Other 0 11 Season SM
Other 0 12 Restore internal season
Other 0 13 Season CI
Other 0 14 DST with season
Other 0 15 External sync and DST with season
Configuration 7 18 Association LN programming
change
Meter alarm 14 19 Excess energy above threshold ER
Meter alarm 14 20 Excess energy under threshold ER
Meter alarm 14 21 Excess energy above threshold LP
Meter alarm 14 22 Excess energy under threshold LP
Meter alarm 14 23 Non fatal alarm appearance
Meter alarm 14 24 Non fatal alarm disappearance
Fatal error 11 25 Fatal alarm appearance
Configuration 7 26 Parameters savings
change
Other 0 27 Clear non fatal alarms
Other 0 28 Clear fatal alarms
Set clock 6 29 Internal clock synchro
Set clock 6 30 External clock synchro
Set clock 6 31 Clock set
Before / After
Other 0 32 External sync and DST without
season
Other 0 33 DST without season
Other 0 34 AC fail appearance
Other 0 35 AC fail disappearance
Power down 1 36 Power fail appearance
Power up 2 37 Power up
Configuration 7 38 Programming CM
change
Configuration 7 39 Programming DI
change
Actaris SL7000 DLMS Release Note.doc
Page 5 of 7

Configuration 7 40 Cancel programming DI

change
Clear data 12 41 Reset measurement data
Other 0 42 Start measurement
Other 0 43 Stop measurement
Other 0 44 Start triggered tests
Other 0 45 Stop triggered tests
Other 0 46 End of current data saving
Clear data 12 47 Load profile reset
Other 0 48 Password restoration
Other 0 49 Index clock loss
Other 0 50 Successfull communication
Other 0 51 Communication with contract
Meter Events created from the interval status bits or other profile events
Logbook event Code Manufacturer’s Code Manufacturer’s Description
Watchdog reset 0x08 0x04 Watchdog reset
Shortlong 0x04 0x08 Daylight saving time
Shortlong 0x04 0x30 Clock set
Power up 0x02 0x40 Power failure
Power down 0x01 0x40 Power failure

8. Interval status

Interval Status bits read-out from the meter

Status bit Code Manufacturer’s Code Manufacturer’s Description
Watchdog reset 0x08 0x04 Watchdog reset
Shortlong 0x04 0x08 Daylight saving time
Shortlong 0x04 0x30 Clock set
Power up 0x02 0x40 Power failure
Power down 0x01 0x40 Power failure
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.
Actaris SL7000 DLMS Release Note.doc
Page 6 of 7

9. Meter registers

EIServer is using the Standard OBIS Codes (3) 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 3 D E F Reactive power+ all phases
1 1 4 D E F Reactive 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 9 D E F Apparent power+ all phases
1 1 10 D E F Apparent power- all phases
0 0 96 6 0 255 Battery use time counter
1 1 0 1 0 255 Billing counter
1 1 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 / 5 = last average / 4 = current average
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
(The SL7000 has 18 billing points for most electricity related registers)

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 Billing period event
register register timestamp (if billing is
used)
Actaris SL7000 DLMS Release Note.doc
Page 7 of 7

Remarks:
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 0x30 contains clock setting bits 0x10 OR 0x20 (External sync and clock setting).
3 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)

4 Since protocol version 2009-05-26, the billing timestamps are read and represented as they
appear in the meter itself. This means that device time zones and time zone related properties
have NO influence on the billing timestamp. The billing timestamps are following the internal
clock of the device. So if a billing date is for example 5 Jan 2009, 14:07:31 WET, this means
that the billing happened when the internal device clock was at 5 Jan 2009, 14:07:31 WET.