User Manual

for

SL7000
SMART
Commercial & Industrial Meter
Configuration software

DINO+

Last update :

jj/12/13

jchauvin jj/12/13

TABLE OF CONTENTS

1. INTRODUCTION.....................................................................................................................6
1.1. PURPOSE....................................................................................................................................................... 6
1.2. CONTENTS..................................................................................................................................................... 6

2. PRODUCT FEATURES.........................................................................................................7
2.1. PRODUCT FUNCTIONS................................................................................................................................. 7
2.2. USER PROFILE.............................................................................................................................................. 8
2.3. CONSTRAINTS............................................................................................................................................... 8
2.4. ARCHITECTURE OF A COMPLETE SYSTEM .............................................................................................9

3. DINO+ VERSIONS................................................................................................................10
3.1. OVERVIEW................................................................................................................................................... 10
3.2. PREDEFINED VERSIONS............................................................................................................................ 11
3.2.1. READING VERSION (Evaluation)............................................................................................................ 11
3.2.3. PERMISSION LIST FOR PREDEFINED VERSION..................................................................................13
3.3. USER CONFIGURABLE VERSION.............................................................................................................. 14
3.3.1. Description................................................................................................................................................ 14
3.3.2. Logon......................................................................................................................................................... 14
3.3.3. Permissions list........................................................................................................................................ 14

4. SOFTWARE INSTALLATION...............................................................................................15
5. SOFTWARE PROTECTION.................................................................................................15
5.1. OVERVIEW................................................................................................................................................... 15
5.2. MOVING LICENSE........................................................................................................................................ 16

6. FUNCTIONS.........................................................................................................................18
6.1. USER INTERFACE FUNCTIONS................................................................................................................. 18
6.2. SYSTEM START........................................................................................................................................... 19
6.3. LOGON.......................................................................................................................................................... 20

7. MENU STRUCTURE............................................................................................................21
7.1. FILE MENU.................................................................................................................................................... 22
7.1.1. Import........................................................................................................................................................ 22
7.1.2. Export........................................................................................................................................................ 26
7.1.3. exit.............................................................................................................................................................. 29
7.2. CONFIGURATION MENU............................................................................................................................. 29
7.2.1. Empty configuration................................................................................................................................. 29
7.2.2. New............................................................................................................................................................ 30
7.2.3. Close.......................................................................................................................................................... 30
7.2.4. Open List................................................................................................................................................... 31
7.2.5. Close List.................................................................................................................................................. 32
7.2.6. Save........................................................................................................................................................... 32
7.2.7. Save As...................................................................................................................................................... 33
7.2.8. Save as Default......................................................................................................................................... 33
7.2.9. Delete......................................................................................................................................................... 34
7.2.10. Print.......................................................................................................................................................... 34

jchauvin jj/12/13

7.3. DATA............................................................................................................................................................. 35
7.3.1. Open.......................................................................................................................................................... 35
7.3.2. Close.......................................................................................................................................................... 37
7.3.3. Delete......................................................................................................................................................... 37
7.4. COMMUNICATION MENU............................................................................................................................ 39
7.4.1. Connect..................................................................................................................................................... 39
7.4.2. Disconnect................................................................................................................................................ 42
7.4.3. Read........................................................................................................................................................... 43
7.4.4. Write........................................................................................................................................................... 46
7.4.5. Clock.......................................................................................................................................................... 50
7.4.6. Action......................................................................................................................................................... 51
7.4.7. Configuration sequence.......................................................................................................................... 53
7.5. TOOLS MENU............................................................................................................................................... 55
7.5.1. User management..................................................................................................................................... 55
7.5.2. User Groups.............................................................................................................................................. 57
7.5.3. Permissions.............................................................................................................................................. 58
7.5.4. Meter management................................................................................................................................... 59
7.5.5. Meter Initialisation.................................................................................................................................... 62
7.5.6. Field download......................................................................................................................................... 62
7.5.7. Current Transformer/Voltage Transformer correction .........................................................................63
7.5.8. Set-up........................................................................................................................................................ 65
7.5.9. Localize..................................................................................................................................................... 69
7.5.10. Database repair....................................................................................................................................... 69
7.6. HHU............................................................................................................................................................... 70
7.6.1. Typical read operation............................................................................................................................. 70
7.6.2. Interaction of the packages.................................................................................................................... 71
7.6.3. HHU function in DINO+............................................................................................................................ 72
7.6.4. Job file management................................................................................................................................ 73
7.6.5. Job file editing.......................................................................................................................................... 74
7.6.6. Import Data from HHU.............................................................................................................................. 76
7.6.7. Automatic objects selection.................................................................................................................... 76
7.6.8. HHU Setup................................................................................................................................................. 77
7.6.9. Permission list.......................................................................................................................................... 77
7.7. HELP............................................................................................................................................................. 78
7.7.1. Dino+ Help................................................................................................................................................. 78
7.7.2. About DINO+............................................................................................................................................. 78

8. CONFIGURATION FOR SL7000 SMART C&I METER ....................................................102

8.1. OVERVIEW................................................................................................................................................. 102
8.2. CONFIGURATION PARAMETERS............................................................................................................. 102
8.3. USER INTERFACES................................................................................................................................... 105
8.3.1. Configuration tree.................................................................................................................................. 106
8.3.2. Quantity selection.................................................................................................................................. 108
8.3.3. Resources............................................................................................................................................... 109
8.3.4. Client level............................................................................................................................................... 112
8.3.5. Identification........................................................................................................................................... 114
8.3.7. Metrology................................................................................................................................................. 116
8.3.8. Auxiliary I/O............................................................................................................................................. 119
8.3.9. Energy Calculation................................................................................................................................. 126
8.3.10. Demand calculation ............................................................................................................................. 130
8.3.11. Load profile........................................................................................................................................... 137
8.3.12. RTC (real time clock)............................................................................................................................ 140
8.3.13. Time of Use........................................................................................................................................... 141
8.3.14. End of Billing........................................................................................................................................ 147
8.3.15. Display................................................................................................................................................... 150
8.3.16. Monitoring............................................................................................................................................. 156
8.3.17. Logging / Alarms.................................................................................................................................. 159
8.3.18. Communication..................................................................................................................................... 161

jchauvin jj/12/13

9. CONFIGURATION FOR SL7000 SMART C&I METER, TYPES SL762XXX....................167

9.2. OVERVIEW................................................................................................................................................. 167
9.2.1. Resource................................................................................................................................................. 167
9.2.2. Load Profile............................................................................................................................................. 167
9.2.3. Communication...................................................................................................................................... 167

10. READING OF DATA.........................................................................................................169

10.1. TOTAL ENERGY REGISTERS:................................................................................................................ 170
10.2. ENERGY RATE REGISTERS:.................................................................................................................. 170
10.3. DEMAND REGISTERS............................................................................................................................. 170
10.4. MAXIMUM DEMAND REGISTERS........................................................................................................... 170
10.5. HISTORICAL DATA................................................................................................................................... 171
10.6. PARTIAL READ OF LOAD PROFILE....................................................................................................... 171
10.7. DATE AND TIME, METER ID................................................................................................................... 171
10.8. LOG BOOK................................................................................................................................................ 171
10.9. INSTANTANEOUS DATA.......................................................................................................................... 171
10.10. NETWORK HISTORY............................................................................................................................. 172
10.11. METER HISTORY................................................................................................................................... 172
10.12. VOLTAGE QUALITY DATA..................................................................................................................... 172
10.13. TAMPERING DATA................................................................................................................................. 172
10.14. METER STATUS..................................................................................................................................... 172

11. DATA DISPLAY.................................................................................................................173

11.1. TOTAL ENERGY REGISTERS................................................................................................................. 174
11.2. ENERGY RATE REGISTERS................................................................................................................... 175
11.3. DEMAND REGISTERS............................................................................................................................. 176
11.4. MAXIMUM DEMAND REGISTERS........................................................................................................... 178
11.5. HISTORICAL DATA................................................................................................................................... 179
11.6. PARTIAL READ OF LOAD PROFILE....................................................................................................... 180
11.7. DATE AND TIME / METER ID................................................................................................................... 181
11.9. LOG BOOK................................................................................................................................................ 183
11.10. INSTANTANEOUS DATA........................................................................................................................ 184
11.11. NETWORK HISTORY............................................................................................................................. 185
11.12. METER HISTORY................................................................................................................................... 186
11.13. VOLTAGE QUALITY DATA..................................................................................................................... 187
11.14. TAMPERING DATA................................................................................................................................. 189
11.15. METER STATUS..................................................................................................................................... 190

12. ANNEXE : PERMISSION LIST FOR PREDIFINED VERSION........................................191

13. ANNEXE : PERMISSION LIST FOR CONFIGURABLE VERSION.................................195
14. ANNEXE : CLIENT ACCESS TO OBJECTS...................................................................200
15. ANNEXE : CLIENT ACCESS TO ACTIONS....................................................................201

jchauvin jj/12/13

16. ANNEXURE : CLIENT ACCESS TO OBJECTS..............................................................203

17. ANNEXE : CLIENT ACCESS TO OTHER FUNCTIONS.................................................204
18. ANNEXE : DISPLAY ON LCD OF ERROR CODE...........................................................206

jchauvin jj/12/13

1. INTRODUCTION
1.1.

Purpose

The objective of this document is explain the functions of the software tool DINO+ for SL7000 SMART C&I
Meters and to be used as a manual.
The software tool DINO+ permits to configure SL7000 SMART C&I Meters, to read data from the devices, to
format and to display these. The functions are controlled by a comprehensive user management module,
distributing different access rights to different users.
The main functions are divided in several groups :

1.2.

Configuration : to define a configuration, download it into a meter or read it from a meter.

Reading : to read data from a meter and display them.

Meter management: to keep a database of meters with all necessary information.

User management: to define and maintain user access rights and passwords.

Contents

The contents are divided in the following paragraphs:

1 Introduction.
2 Product features.
3 Dino+ versions.
4 Software installation.
5 Software protection.
6 Functions.
7 Menu structure.
8 Configuration for SL7000 SMART meter SL761.
9 Configuration for SL7000 SMART meter SL762.
10 Reading of data.
11 Data display.

jchauvin jj/12/13

2. PRODUCT FEATURES
2.1.

Product functions

The software DINO+ is a reading and programming application for SL7000 SMART C&I Meters, type
SL761xxxx and SL762xxxx .
It manages two types of data :

Configuration parameters which are readable and programmable (All of them define the meter
configuration). The control of configuration coherence is implemented in the tool.

Reading data which are only readable (data created by the meter)

The application can send some commands to the meter (trigger an End Of Billing (reset Maximum Demands),
start or stop measurement, clear non fatal alarms .)
The application manages a data base for all the parameters and keeps all reading data in specific files in a
directory structure.
The software is single-user, with resources to handle several configurations and several meters.
The usage of the software is facilitated by an interface which is similar to Windows Explorer, with use of mouse,
option buttons, drop-down boxes/menus and tree-like selection windows for complicated choices.
The meters are accessible by different communication modes :

Direct connection on RS232 link;

Connection through RS232 to a bus structure (e.g. optical ring, RS485 bus, Intranet, );

Remote connection on modem link;

IR-Communication according to the new Mode E in the next release of IEC 61107 (for
SL761xxxx);

IR-communication using a plain COSEM link (for SL762xxxx) .

The software supports the following main features:

User management (passwords and access rights);

Configuration management (create, modify, or delete global or partial configuration);

Meter management (create, modify or delete meter dependent information);

Reading a meter (configuration or data);

Downloading a configuration (global or partial) into a meter;

Launching tests on a meter;

Import / Export user management data;

Import / Export configurations;

Import / Export meter management data;

Display and report of Reading Data ;

Administration of database (purge).

Option: Provide the necessary interface to control a handheld unit management software
PRACDIS, designed and manufactured by ALSI.

jchauvin jj/12/13

2.2.

User Profile

The software tool DINO+ has been designed to be used by a user who may configure a meter and read
its data in a direct connection with a meter. It is also designed to generate meter configurations offline
to a meter, to be downloaded later into different meters. It also supports the needs of users who will
generate configurations, meter data or user data to be transferred into other installations of DINO+.

2.3.

Constraints

Host station : The software is able to run on PC ( desktop or laptop ) with any Windows version equal
or higher than Windows 95 (NT 4.0 (95, 98, millennium, 2000 and NT4.0). The User
Interfaces have been designed so that they are fully visible with a screen resolution of
1024*768 pixel.
Installation :

Automatic installation from a CD-ROM, (or from a file), to a PC running a version of

Windows as defined above, with 64MB RAM or more, 200 MHz or more.

Protection:

The software is delivered with a free 60 days read only access. All other kind of access
requires a license.

Language :

The default user interface language is English. Additional languages are available right
now (French, Russian, Spanish) or under development (Polish, Italian). Other languages
can be added.

DataBase :

No special license is needed for the database.

Target meter : SL7000 SMART C&I METER version SL761xxxx and SL762xxxx
Modem :

Modem compliant to HAYES standard (tested and recommended modems will be

announced through application notes)

Optical Head : The Software is designed for a specific optical head to be provided by Actaris.
Regional settings : The date separator has to be /.

jchauvin jj/12/13

2.4.

Architecture of a complete system

The software is designed to work in a stand alone PC, as well as in a PC with network connections.

printer
RS232
COSEM
modem
RS232

database

COSEM

modem

NB: The direct connection can be done either through the RS232 line, or my means of the optical head,
connected on the RS232 port on PC side.

jchauvin jj/12/13

3. DINO+ VERSIONS
3.1.

OVERVIEW

This chapter describes 2 different versions of DINO+, which are available for the user, depending on the
license level.
The customer can order a configurable version (Full version) or a predefined version (evaluation version)
of DINO+.

Evaluation version (or Reading version) : This software shall allow to get familiar with the handling of it,
but does not allow to use it for maintenance with a meter

Full version: This version provides the full functionality of the package, and can be configured to set up
different access rights for user groups managed by passwords.

The different versions are created using the permission feature of DINO+, and are handled through the
license level which limits the functionality to the declared volume. No administrative user can modify these
rights (beside the hidden default user). No modification to the application can be done.

10

jchauvin jj/12/13

3.2.

PREDEFINED VERSIONS
3.2.1.

READING VERSION (Evaluation)

3.2.1.1. Description

This version is a training tool for prospective users, or a tool to investigate the possibilities of the
software package and the meter.
According to the communication, only configuration reading and data reading are possible (no
programming and no action to the meter).
The user permissions cant be imported or exported.
The HHU and meter initialisation functions are not included in this version.
Except Engineer all other Clients
accessible.

( Electricity Utility Laboratory, Electricity Utility Field ) are

All Logical devices (Management, Electricity ) are accessible.

All Configuration features are accessible (import, export, edit )

This version ensures the user cannot download anything into a meter.

3.2.1.2. Logon

The database contains one user only. To logon the software the user has to enter USER as the name,
and EVALUAT as password. These user permissions are defined in a permission list table in annex 11. The
user cant modify them . The access rights are defined in the column labelled evaluate.

11

jchauvin jj/12/13

3.2.2.

12

jchauvin jj/12/13

3.2.3.

PERMISSION LIST FOR PREDEFINED VERSION

The permission list for predefined version is detailed in annexe 12.

O means the function is accessible, N means the functions is not accessible for the user.
O for configuration items means the user can modify the value.
This list is hard coded and cant be modified.
Example :
Version reading in Menu features :
the user cant import a user permission file
The user can export a configuration file
See the corresponding annex.

13

jchauvin jj/12/13

3.3.

USER CONFIGURABLE VERSION

3.3.1.

Description

This version is the most complete version of the tool . This version needs an administrator, which is
member of the user group ADMINISTRATOR. All permissions are accessible to this user group.
The administrator can create user groups (up to 4) and define the permissions for each one.
By default, four user groups are proposed to the administrator (see the permission list table in chapter
4.4.3: user groups Laboratory, Field, Download & Reading).
The administrator can change the name of the users group and the associated permissions.
He is the only person to use the permission function (Edit, Import & export). The administrator can
delete himself from the user list, that means this configurable complete version becomes a customer predefined
version.

3.3.2.

Logon

The database may contain many users as administrator (0,1 or several), and users created by the
administrator for the corresponding group. To logon the software the first time the user has to enter
MANAGER as the name, and MANAGER as password.
Then once users are created, each can logon the software with his name and password defined by the
administrator. The user can change his own password.

3.3.3.

Permissions list

See annex 12.

14

jchauvin jj/12/13

4. SOFTWARE INSTALLATION
The DINO+ software package is delivered in a CDROM. Insert the CDROM into the CD Reader. An
automatic procedure is launched for the installation.
Dont forget to read the Readme.txt file to get information. To launch the installation procedure
manually, the user has to execute the setup.exe program from the CDROM. A sequence of screens
appears to the user to personalise the installation procedure.
An uninstall procedure is included automatically on installation step.

5. SOFTWARE PROTECTION
5.1.

OVERVIEW

DINO+ software is a protected against illegal usage or copying.

DINO+ manages several versions of software : Reading, Download, Field, and Full.
The DINO+ software is distributed with a build-in trial period (60 days). The build-in trial version corresponds to
the Reading (Evaluation) version of DINO+.
During the build-in trial period, every time the user launches the DINO+ application, a small window is displayed
(5s) showing the number of days left for the trial period.

Once the trial period is finished, a license is required to use one of the available version of the
software.

DINO+

If the user doesnt wait until the end of the trial period to order a License of DINO+, he has to press the Enter
button to display the License configuration window.

15

jchauvin jj/12/13

Actaris Sales

The customer has to contact the local RBU (Regional Business Unit) to order the DINO+ License. He has to
precise which version and send him the Side Code. The RBU sends him back the Site Key which will be entered
by the user to get the definitive license. To read the Side code click on the Display side code button.
Once the Site Key is validated, the unlimited version of DINO+ is ready to use.

5.2.

Moving License

Floppy disk license transfers require a floppy disk, an authorized copy of your product installed on the source
PC, and an unlicensed copy of your product on the target PC.
The transfer process does not jeopardize your license in any way and is completely secure because the floppy
disk is registered to a specific PC in a specific location. This ensures the license can only be transferred to the
target PC you specify.

Actaris Sales

16

jchauvin jj/12/13

If you want to transfer a license from PC 1 to PC 2 the procedure is :

1- Ensure you meet the stipulations outlined : Floppy disk license transfers require a floppy disk, an authorized
copy of your product installed on the source PC, and an unlicensed copy of your product on the target PC.

2- Start the program on PC 2, and select Transfer Into Computer. Supply the floppy disk path. The program
imprints its registration on the disk.
3- Remove the floppy disk from PC2, and insert it into PC1.4- Start the program on PC1, and select Transfer
Out of computer. Supply the floppy disk path. The program reads the registration imprint file and writes a
matching file to the floppy, decrementing the license count at the source or discontinuing it (in case of a single
user license).
4- Remove the floppy disk from PC 1, and return it to PC 2.
5- Click Transfer Into Computer to complete the transfer and discard the intermediate imprint files.

17

jchauvin jj/12/13

6. FUNCTIONS
This chapter describes all meter type independent functions of the software tool DINO+.

6.1.

User interface functions

The user interface has a Windows Explorer like style and uses Tags to switch between different items of a
selection.
Moving within the different screens is be performed with mouse operations as it is usual in Microsoft softwares.
Menu items can be activated by single button keystrokes.
Within a screen the progress from field to field is possible with the TAB key or by clicking into the desired field.
The operation of tags is possible by simultaneous activation of the ALT key and one context specific key.
Each Window contains information related to one topic and provides all necessary fields to fully operate this
topic.
Within each field, where a limited list of entries is possible, those are presented in a drop-down manner and are
selectable by mouse click.
Within each field, where a range is allowed, the range is selectable by the means of spin buttons. The scrolling
is limited to the range.
Where a few choices of possibilities are available and the related text needs more space, the selection is done
with option buttons.
Where the selection comes from a choice, which is complicated or tree-like, the selection is made by navigating
through a separate window and clicking on the desired option.
Where the selection requires to enable / disable an option this is done by a toggle button.
Some selections require to insert data by the keyboard.
Where appropriate, all fields are initialised with the default values according to a stored default configuration.
Each operation which is not allowed in the system is commented by an error message, which includes details in
order to help overcoming the problem.

18

jchauvin jj/12/13

6.2.

System start

When the software is started from the desktop it displays a welcome screen. To proceed from this screen, the
user has to click into the image. Alternatively, the software tool DINO+ will proceed automatically after 5
seconds waiting time.

19

jchauvin jj/12/13

6.3.

Logon

This feature is automatically activated, when the application proceeds from the welcome screen. Every time
DINO+ is run, the system will display a dialog box that will ask for a username (User ID) and password to be
entered. If this doesnt match one of the entries defined within the user management inside DINO+, permission
to start the application will be denied.

After 3 unsuccessful attempts the application is closed.

The entry of the User ID is not case sensitive.
The entry of the Password is case sensitive. For security reasons the entered characters are displayed as * .
Using the OK button will terminate the logon.
Depending on the access rights given to the user who is identified by the User ID, functionality will be limited
accordingly.
When the software is installed for the first time, and according to the software version (read/evaluation version,
configuration download version, field configuration version, or full version), a single user is authorised, with
specific rights:

Full version (administrator rights):

User ID:
Manager
Password: MANAGER
The Manager, (like any other user), has the rights to modify his own password, thus preventing non
authorised further accesses to the software (see Tools, User Management).

Field configuration version

User ID: User
Password: FIELD
This user is assigned to a group called field.
This version is to be used in applications, where a local office is allowed to modify configurations, with the
ability to download them into a meter, with metrology seals attached.

Configuration download version

User ID: User
Password: DOWNLOAD
This user is assigned to a group called download.
This version is used for applications where a central office creates configurations and distributes them to
local offices. Those local offices can import them and download them into a meter, provided the coherency
checks between the meter and the configuration pass. From Configurations, only the item transformer
ratio can be accessible to the local office.

Evaluation version or Reading version

User ID: User
Password: EVALUAT
This user is assigned to a group called "evaluation".
This version allows to investigate the possibilities of the package and the meter. Nothing can be
downloaded to the meter

20

jchauvin jj/12/13

7. MENU STRUCTURE
The navigation through the system is guided with a menu line on top of the application, which allows to open
sub-menus. Several menu levels are available, depending on the chosen function.

The overall structure is:

File
import
configuration
user permission
meter
export
configuration
user permission
meter
exit

Configuration
Empty
New
Close
Open List
Close List
Save
Save As
Save as Default
Delete
Print

Reading
Open
Close
Delete

Communication
Connect
Disconnect
Read
configuration
data
Write
configuration
password
physical address
logical addresses
clock
Action

Tools
User management
Permissions
Meter
management
Meter Group
Meter
Meter
initialisation
Log
Set-up
Localize

HHU
Job file management
Import HHU Results
Select configuration
items for HHU

Database repair

Each menu item, which is not accessible for a user, or which is not functional in the current context of the
application is shaded and not selectable.
The following chapters explain the usage of the menu items.

21

jchauvin jj/12/13

?
Help
About

7.1.

File menu

This Menu item deals with all import/export possibilities of the system and allows to Exit the program.

7.1.1.

Import

This menu item allows to import data, which are coming from other systems. The typical usage is the transfer of
configurations or of system database components between different installations of DINO+.
The menu item allows to import configurations, the user permissions database or meter setup data.
All import actions are reading ASCII files with a pre-defined format into the database of the system.

22

jchauvin jj/12/13

7.1.1.1. Import configuration

When selecting this menu item, a user interface appears, which allows to select a file containing a
configuration.

It is possible to browse all available drives on the machine, local and network. The file browser is starting in that
directory which was defined as the default directory for Import/Export of configurations in the software setup
(see chapter 7.5).Only those files are presented, which have a type according to DINO+ configuration
(extension .cfg). Even if it is possible to change the extension from .cfg to another, the system will not accept
files with different extensions.
If a configuration is selected (by single mouse click) the comment stored with this configuration and the client
definition is displayed in the UI (user interface). A configuration can be imported by either double clicking it or
by selecting it and activation of the Open button.
When a configuration is imported, but one with the same identification is already existing in the database, a
user interface allows to continue or cancel the operation. Selecting Yes will overwrite the existing
configuration, selecting No will allow to store the imported configuration with a new name, selecting Cancel
will terminate the import.
The imported configuration is appended to the database if it is coherent, but not opened. When it is incoherent,
it shall be opened and not saved.
When Activating the Cancel button the dialog is closed without opening a configuration tree.
The imported configuration is appended to the database, but not opened.

23

jchauvin jj/12/13

7.1.1.2.

Import user permissions

A dialog allows to select a file containing a user permission data set.

It is possible to browse all available drives on the machine, local and network. Only those files are accepted,
which have a type according to DINO+ permissions (Extension .prm).
When a permissions files is selected a security dialog warns about the implications coming from this feature.

User permissions can be imported by either double clicking it or by selecting it and activation of the Open
button. When user permissions are imported, the existing permission settings are overwritten. The imported
user permission becomes active after the next start of the application.
When Activating the Cancel button the dialog is closed without importing user permissions.

24

jchauvin jj/12/13

7.1.1.3. Import meter

When selecting this menu item, a user interface appears, which allows to select a file containing meter
identification data.
It is possible to browse all available drives on the machine, local and network. Only those files are presented,
which have a type according to DINO+ meter (Extension .mtr).
Meter can be imported by either double clicking it or by selecting it and activation of the Open button. When
Activating the Cancel button the dialog is closed without importing user permissions .When user meter data
are imported, they are always appended to the existing meter data base.
If a meter is imported, but one with the same meter number is already existing in the database, a user interface
allows to cancel the operation or to overwrite the existing meter.

If Yes is chosen, this meter is overwriten. If Cancel is chosen, this meter is not imported.
If No is chosen, another dialog asks for a new name to store

The imported meters are appended to the database and are available immediately.
If the group of the meter doesnt exist in the database, it is added before the meter is added.
For import, the maximum speed of the settings concerning modem communication override the entry in the
meter data, if those show a higher communication speed, to avoid inconsistent data in the system.

25

jchauvin jj/12/13

7.1.2.

Export

As a complement to the Import feature, an Export feature allows to create files, to transfer them to other

systems.
7.1.2.1. Export configuration
This menu item is only available, when a configuration is opened.
When selected, it opens a user interface which allows to define the location for storage and the file name.
All local and network drives can be browsed.

The file extension is created automatically and cannot be modified.

If a file with the same name already exists in the selected directory, a security dialog asks for confirmation and
the old file shall be overwritten.

After exporting a dialog informs about the successful operation.

26

jchauvin jj/12/13

7.1.2.2. Export user permission

This menu item allows to export the user group permissions.

When selected, it opens a user interface which allows the user to define the location for storage and the file
name.
All local and network drives can be browsed.
The file extension is created automatically and cannot be modified.
If a file with the same name already exists in the selected directory, a security dialog asks for confirmation and
the old file shall be overwritten.

After exporting a dialog informs about the success of the operation.

27

jchauvin jj/12/13

7.1.2.3. Export meter

This menu item allows to export a single meter, or several meters from the meter data base. The selection is
possible for meters, complete meter groups or meters selected separately. The selection dialog allows to select
meter by meter by clicking on the meter number of the desired meter (using the click/shift-click/control-click
feature as in the Windows Explorer).

When the export button is selected, it opens a user interface which allows the user to define the location for
storage and the file name.

All local and network drives can be browsed.

The file extension is created automatically and cannot be modified.
The created file for meter export contains passwords in encrypted format.
If a file with the same name already exists in the selected directory, a security dialog asks for confirmation.

After exporting a dialog informs about the success of the operation: export completed.

28

jchauvin jj/12/13

7.1.3.

exit

When selected the application is closed.

This menu item has the same functionality as the Close button in the headline of the application. If a
configuration is open and If this open configuration was modified since the opening, when activating this item, a
security request will ask if the open configuration shall be stored.

7.2.

Configuration menu

A configuration is a complete set of configuration objects, which defines the behaviour of a meter. It is
composed of a defined set of configuration parameters.

A configuration can be modified, regardless from where it is loaded (meter, external, database) or can be made
from new.
For this operation it is possible to store a default configuration which is automatically loaded when the
operation new is activated. When accessing configuration data screens the selection is made in a WindowsExplorer like window, which presents a tree of all available choices. Selecting a choice will open a window
where the related screen(s) are presented.
7.2.1.

Empty configuration

This Menu item is only available, when no configuration is open. This menu item, when selected, opens a
configuration tree, which is filled with a default configuration according to the behaviour of a meter after first
power up

29

jchauvin jj/12/13

7.2.2.

New

This Menu item is only available, when no configuration is open. This menu item, when selected, opens a
configuration tree, which is filled with a default configuration, retrieved from the database.
On system installation a default configuration is available, according to the behaviour of a meter after first
power up.

7.2.3.

Close

This menu item is only available when a configuration is open.

30

jchauvin jj/12/13

This menu item, when selected, closes the open configuration. If the open configuration was modified since the
opening and all dependencies are resolved, the UI displays a security request to ask if the open configuration
shall be stored.

If Yes is selected, the menu item branches to the menu item Error: Reference source not found, if the
configuration was retrieved from the database before (has already a name) or to Error: Reference source not
found, otherwise. After performing the Save or Save As operation, the configuration is closed. If the Error:
Reference source not found or Error: Reference source not found operation is cancelled, the configuration is
not closed. (like selecting Cancel in this dialog)
If No is selected the configuration is closed without saving. If Cancel is selected the application returns to the
position before activating the menu item. It is not allowed to store an inconsistent configuration.
If the configuration has unresolved dependencies, it cannot be stored in the database. In this case a security
request will ask if the configuration shall be discarded or not. If Yes is selected the configuration is closed
without saving. . If Cancel is selected the application returns to the position before activating the menu item.
7.2.4.

Open List

This Menu item is only available, when no configuration is open and at least one user configuration was already
stored in the system.
This menu item allows to select a previously stored configuration from the database. A tree presents all stored
configurations in the system

By selecting a configuration (single click), the comment, client definition and the date of last storage are
displayed. This dialog also have an Open and a Cancel button.

31

jchauvin jj/12/13

When Activating the Cancel button the dialog is closed without opening a configuration tree.
Opening a configuration is done either by double-clicking it in the tree or by activation of the Open button in the
comment dialog. A configuration tree is opened, filled with the selected configuration.
7.2.5.

Close List

This Menu item is only available, when configuration List is open. This menu item allows to close the tree of
configurations.
7.2.6.

Save

This menu item is only available when a configuration is open, and if this configuration was previously retrieved
from the database (already has an identification) and all dependency checks are passed.
This menu item, when selected, opens a security dialog, to confirm that the previous version of this
configuration shall be replaced and allows to edit the comment, stored with the configuration.

If Yes is selected, the existing configuration with the same identification is replaced in the database. The
stored comment is displayed and it is possible to modify it.

If No is selected, the menu item branches to the item Error: Reference source not found.
If Cancel is selected the application returns to the position before activating the menu item.
After the Save operation the configuration is not closed.

32

jchauvin jj/12/13

7.2.7.

Save As

This menu item is only available when a configuration is open and all dependency checks are passed.
This menu item, when selected, opens a dialog, to allow to enter the identification of the configuration and a
comment.

It also has 2 buttons: Save As and Cancel.

The Configuration name is mandatory, the comment is optional.
The identification will be rejected, if a configuration with the same identification is already stored in the
database.
If Save As is selected, the configuration is added to the database, but not closed.
If Cancel is selected, the application returns to the position before activating the menu item.
7.2.8.

Save as Default

This menu item is only available when a configuration is open and all dependency checks are passed.
It allows to save the current configuration as the default configuration (there is only one default configuration). It
is stored with a default identification. The default configuration has no comment stored.

The operation uses the same security dialog as the Save operation but without the possibility to edit a
comment.
The operation does not close the current configuration tree.

33

jchauvin jj/12/13

7.2.9.

Delete

This menu item is only available when no configuration is open.

This menu item allows to select a previously stored configuration from the database. It opens a dialog which
presents the stored configurations in the system.
This dialog has 2 buttons: Delete and Cancel.
This dialog lists the existing configurations with their identification. When a configuration is marked by a mouse
click, the comment stored together with this configuration and the date of last storage is displayed. A
configuration can be selected for deletion by either double clicking or by marking and activation of the Delete
button.
After selection a security dialog is opened, which asks a confirmation for the delete operation.
Any deleted configuration is removed from the system and cannot be recovered.
When Activating the Cancel button the dialog is closed without other activity.

7.2.10.

Print

This menu item is available only when a configuration is open and all dependency checks are passed.
It will print the current configuration to the default printer as defined in Windows, or save it as an excel
spreadsheet.

34

jchauvin jj/12/13

7.3.

Data

This menu contains all operations to handle reading data, which were read from a meter.
(See in the tools / setup / Other setups menu to choose your directory data storage).

Readings are stored in a directory structure inside the system, which uses meter number, reading date and
reading data contents as identifiers.
7.3.1.

Open

This Menu item is accessible, when no reading is open yet.

This menu item allows to select a previously stored reading from the directory structure. It opens a tree which
presents the meters, which have stored readings in the system and exist in the meter management. For each
meter a sub-tree can display the dates for which readings are available.
Selection of a meter will display a dialog showing the fields Meter type, Group, Name, Address, and Address 1,
from the meter management.

This dialog shows 2 buttons: List Data and Close Meter

List Data will open the sub-tree of the selected meter.

35

jchauvin jj/12/13

Close meter will delete the dialog box showing the meter management data of the selected meter.
Activating the button List data displays a tree, containing all dates, for which readings of the selected meter
are available in the database.
Selected days can be expanded by clicking the + sign or by double clicking the date.

After selection a data tree is opened, filled with the available reading items. (reading files, each corresponding
to one reading set, with date and time information). For a given data several reading files for the same reading
set can be available.
Selecting an item in the tree or activating the Open button will activate its display. The UI which is activated
depends on the meter type and on the nature of the selected reading. . (see 10 Reading)
When Activating the Close Data button, the dialog is closed without opening a reading.
The Close button closes the whole user interface for Open Data.

36

jchauvin jj/12/13

7.3.2.

Close

This menu item is only available when the screen for selecting the reading is open.
It will close the display of a reading tree.
Activating the close button in the headline of the reading or the Close button on the UI of the reading has the
same result.
7.3.3.

Delete

This menu item is only available when no reading is open.

It allows selection of previously stored reading or sets of readings from the database, to be deleted.
It opens a tree which presents the meters, which have stored readings in the system and exist in the meter
management. For each meter a sub-tree can display the dates for which readings are available.
Selection of a meter will display a dialog showing the fields Meter type, Group, Name, Address, and Address 1,
from the meter management.

This dialog has 2 buttons: List Data and Close Meter.

List Data opens the sub-tree of the selected meter.
Close meter will delete the dialog box showing the meter management data of the selected meter.

37

jchauvin jj/12/13

Activating the button List Data displays a tree, containing all dates, for which readings of the selected meter
are available in the database.
Selected days can be expanded by clicking the + sign or by double clicking the date.

After selection, a data tree is opened, filled with the available reading items (reading files, each corresponding
to one reading set, with date and time information). For a given data, several reading files for the same reading
set can be available.
On each level of the tree, it can be selected if the stored data shall be deleted.
When Activating the Delete button, the whole tree below the selected item is deleted.
A security request will ask for confirmation, naming the item to be deleted. Activating the Yes button deletes
the selected reading data. The No button closes the whole user interface for Delete Reading.
Deleted meter readings can be recovered using the file recovery tools (if available) of the operating system.
Activating the Close Data button closes the dialog without deleting anything.
The Close button closes the whole user interface for Delete Data.

38

jchauvin jj/12/13

7.4.

Communication menu

This menu contains all actions required to communicate all the different data used for configuration, reading
and action commands.

7.4.1.

Connect

This menu item is only available, if no connection to a meter is already active.

A user Interface allows to select the meter to which a connection shall be made. It supports all connection types
as supported by the meter, taking all necessary data for the connection from the meter data base.
Activating the Select button allows to select a meter from the meter management.
Activating the Last button provides a list of the last 5 meters which where connected.

39

jchauvin jj/12/13

The selection of the meter can be done by double clicking in the line, which describes the meter, or by marking
it and activating the Select button.
Activating the New button leads to the user Interface, which allows to add a new meter.
After selection of a meter the UI shows the meter management data of this meter.
The UI allows to select the physical communication channel (Optical, direct, modem). After selection of the
meter this field is updated with the corresponding information in the meter management data base. The
possible choice of physical channel depends on the meter type.
The UI provides a list of possible Clients and a list of possible Logical Devices. Only those are presented, where
the user, logged on to the system, has access rights for.
All necessary parameters for the connection come from the meter management.
The UI has 2 buttons, Connect and Cancel
The Connect button is only available after selection of the meter, the client and the logical device. Activating
it, establishes a COSEM connection to the selected device and closes the user interface. During the attempt to
establish the connection both buttons are disabled. A progress window lists the main steps of the connection
procedure (like dialling, waiting for answer, physical connection, logical connection...).

40

jchauvin jj/12/13

A successful connection is marked in the bottom line of the software by a telephone symbol.

If the connection fails, a error message explains the problem and the user interface remains open.

Activating the Cancel Button will close the user interface without establishing a connection.

Firmware release of the meter

The behaviour of DINO+ versus the firmware release of the meter is as follows:
If the firmware release of the meter is known by the software, all actions for which the user
has the rights are possible.
If the firmware release of the meter is unknown by the software, a warning message is sent to
the user, and the programmed actions are possible under the control of the user.

41

jchauvin jj/12/13

7.4.2.

Disconnect

This menu item is only available, if a connection to a meter is active.

A user interface, identical to the one for connection after selecting all necessary parameters, reminds about the
meter which is connected. It provides 2 buttons, Disconnect and Cancel.

Activating Disconnect closes the logical and physical connections to the meter and closes the user interface.
Activating the Cancel button closes the user interface but preserves the connection to the meter.
Driven by the timeout defined in the Set-up, an automatic disconnection can happen. This will not open the user
interface, but place a message on the desktop.

If a disconnection happens for any other reason (e.g. loss of Carrier), the UI is not opened, but a message is
placed on the desktop, saying Connection lost and, if possible giving the reason.

42

jchauvin jj/12/13

7.4.3.

Read

This menu item allows to read configuration and reading data from the meter into the system.

This item, and all daughter items, are only available if a connection to a meter is active.
7.4.3.1. Configuration
This menu item allows to read back the configuration data from a meter. It is only available, if no configuration
is open. A dialog confirms the meter to be read :

By activating the menu item the full configuration from a meter is read.

During the reading of the objects (about one minute for a complete configuration), a progress report is visible. If
connection to another logical device in the meter is necessary, it is handled automatically, and after finishing,
the initial logical device is re-connected. All data are fulfilled into the a new configuration. After finishing the
data transfer, the configuration is opened automatically but not saved. (see Error: Reference source not found
Open) Error: Reference source not found
The UI has a Cancel button which allows to interrupt the current communication. By this, the connection to the
meter stays active, and previously read data are discarded.

43

jchauvin jj/12/13

7.4.3.2. Data
This menu item allows to read the measurement data from a meter. If a reading is open when this menu item is
selected, it is closed automatically.
The system supports the reading of predefined data groups, depending on the meter type.
The system presents a dialog, containing all available data (batches). The contents of the dialog depend on the
meter type the connection was made to. One or several objects could be marked. (full and partial reading of
the meter).
When selecting historical data the amount of sets needs to be specified.
When selecting load profile the specification of the requested time period is needed.

The UI presents 3 buttons: Start Reading , Stop Reading and Cancel.

The Start Reading button is only available after selection of the objects to read. Activating it will execute the
reading of the objects.
The Stop Reading button is only available after launching Start reading. It stops the data readings.
The Cancel button closes this user interface.

44

jchauvin jj/12/13

The bottom bar is giving a progress report during the operation, successfully read objects are marked blue in
the dialog, unsuccessfully read objects are marked red.

After finishing the data transfer, each reading set is stored as a single file in the directory structure for readings.
The file name contains the identification of the reading set, the meter number and date and time of the reading.
The user interface remains active, with the read button inactive and the object selection still there. At this point
another object could be selected or the UI closed.
If connection to different logical devices in the meter is necessary, it is handled automatically, and, after
finishing, the initial logical device is re-connected.

45

jchauvin jj/12/13

7.4.4.

Write

This group of menu items allows to transfer information from the system to a meter.
This item, and all daughter items are only available, if a connection to a meter is active.

7.4.4.1. Configuration
Definition : a saved configuration is a configuration for which all depending tests are successfully passed.
This item is only available, if a configuration is open and saved
The user has to choose the object(s) to configure :

Either with the buttons select all or unselected all.

Or by clicking the checkbox to be transferred for the wished structures of each wished object.

The UI presents the identification of the configuration, its comment, the list of objects to configure, and 2
buttons: Configure and Cancel. At this stage the amount and selection of objects to download into the meter
are predefined by the configuration itself. They cannot be changed.

46

jchauvin jj/12/13

When Configure is activated the system checks if the user rights, the hardware and firmware resources,
version and all dependent objects in the meter, are in compliance with the selected objects and their contents.
The list of objects which can be transferred with the client are read before and checked with the item client
access right of the configuration. If the check passes, the selected objects are configured into the meter. If
connection to different logical devices in the meter is necessary, it is handled automatically, and after finishing,
the initial logical device is re-connected. The user interface is not closed automatically.
During communication a progress window is visible.
After a successful communication for all objects, the Configure button is disabled.
Any non-pass on a dependency check aborts the complete operation with a clear message, indicating in which
objects the non-pass was found. In this case, no data are downloaded to the meter at all.
The Cancel button closes the user interface without data transfer.
If any data necessary for the next connection with the meter (like utility port speed or customer port speed) is
changed in a meter, it is automatically updated in the meter management system and is available for the next
logon.
7.4.4.2. Password
This UI is used to configure the Client access points into a single meter.

The fields for Password never show the password in readable text, but only ******* . The length of password
must be between 5 and 8, and the password is case sensitive.
It is possible to select all Clients to whom the user which is logged on to the system has access, and to enter the
password-information.
The UI provides 2 buttons: Configure and Cancel.
The Configure button is available as soon as, for at least one Client, a password is entered and confirmed.
Each usage of the "Configure" button communicates the new password information (for all Clients, as selected)
to the connected meter.
If this communication was successful, the meter database is automatically updated regarding passwords (they
will be needed for the next logical logon to the meter). The UI stays open.
The progress of the communication can be monitored by a progress bar.
Cancel closes the UI without data transfer.

47

jchauvin jj/12/13

7.4.4.3. Physical Address

This menu item allows to configure the addresses of a single meter.

The user interface allows to enter the needed address, starting from default data.
The default for the physical address is coming from the Set-up of the system.
If the physical addresses is changed in a meter it will be updated in the meter management system as well (to
provide correct information for the next logon).
The physical address ranges from 16 to 16382.
During configuration of the address a progress bar is shown.

48

jchauvin jj/12/13

7.4.4.4. Logical address

This menu item allows to configure the logical addresses of a single meter.

The UI provides 2 buttons: Configure and Cancel.

The user interface allows to enter the needed address, starting from default data.
The default for the logical address is coming from the Set-up of the system.
If the logical addresses is changed in a meter, it will be updated in the meter management system as well (to
provide correct information for the next logon).
The logical address ranges from 2 to 16382.
During configuration of the address a progress bar is shown.
After a successful programming, Dino+ re-connect itself to the meter with the new address.

49

jchauvin jj/12/13

7.4.5.

Clock

This menu item allows to set the date and time (to the second) of the meter.
It opens a UI in which the clock synchronisation can be specified.

Following possibilities are available:

transfer PC-time.

specification of a user time.

specification if transferred time is summer time or normal time.

The UI provides 3 buttons: Configure, Cancel and Read.

The Configure button is available as soon as the time selection is made. After transferring the time the UI is
closed automatically.
Read updates the screen with the meter time.
Cancel closes the UI without data transfer.

50

jchauvin jj/12/13

7.4.6.

Action

Several commands can be sent to a meter to influence its normal operation. (example: Reset MDI, start some
tests). Action commands are accessible from a tree, similar to configuration parameters. This menu item is
only accessible if a connection to a meter is established and the current user has enough rights to perform at
least one action.
Each action command is secured by a confirmation request user interface.

When selected, each group of action from the tree displays a set of operational buttons, which allows to execute
a single action.
MDI Reset :

:
This action will perform an end of billing action in the connected meter. The full amount of operations in the
meter is dependent on its type.
Clear Error :

This action will clear all pending, non fatal errors in the meter, depending on the meter type.

51

jchauvin jj/12/13

Management actions :

This screen allows the execution of several actions, which typically are only accessible to the operator, when
the metrological seal of the meter is broken.
Test actions :

This screen offers a choice of test actions, which are dependent on the meter type.
Only those actions are selectable, where the user has the right to operate them. Some actions are also
restricted by the type of connection to the meter.
Activating an action button, the user is prompted for security reasons:

When Yes is selected, the action will be executed on the connected meter, and a progress bar allows to follow
the operation.

52

jchauvin jj/12/13

When click on Start Test I/O, the following screen is proposed to launch the selected test with the button
Read or Prog :

7.4.7.

Configuration sequence

This Menu item is available, when a meter is connected in Manufacturer or Laboratory ; a configuration must be
opened.
It launches an automatic sequential execution of a set of the following commands :

write clock,

stop measurement,

reset meter,

reset load profiles,

write opened configuration,

reset non fatal errors,

reset fatal errors,

start measurement.

During actions reset, stop, start and clear, the internal laboratory switch must be pressed.

53

jchauvin jj/12/13

54

jchauvin jj/12/13

7.5.

Tools menu

The features in this group allow to manage system parameters of the installed software, the access rights of the
installed users and the management of the installed meters.

7.5.1.

User management

For the Full version of DINO+:

This feature allows to define users and assign them to access groups. Each access group has an individual set
of access rights to the different functions of the software.
This feature provides 5 levels (access groups) of security. The highest level is called Administrator. The
names of the lower levels are user define-able.
Each member of the access group Administrator can create users with unique names and passwords and
assign them to one of the access groups. Once a user account is created with a password, the user can use that
password to log onto the system and modify his own password. That is the only function a non Administrator
will be able to perform in this application.
To access this feature, a second login dialog needs to be filled, which requires the new login for the user
management function. Access is only granted, if the new login is made for a user, known to the system and the
password check passes.

55

jchauvin jj/12/13

To Edit, Add or Delete an entry, it is necessary to use the buttons at the bottom of the dialog, to double click or
click with the right mouse button and to select from a context specific menu. Add and Delete are only available
for users of the group Administrator.
If Edit is chosen by a user, which is not member of the access group Administrator only the modification of
his own password is allowed.
Upon installation of a new system only one user exists.
It is strongly recommended to change the default password of the user.
For the other versions of Dino+:
If Edit is chosen by the user only the modification of his own password is allowed. That is the only function in
the other versions of DINO+.

56

jchauvin jj/12/13

7.5.2.

User Groups

This possibility is only for the Full version of DINO+. It is accessible by click on the button in the User
Management screen.
It is possible to give individual names to the 4 user-definable groups, when activating the button User Group
Names

The names defined in this screen will be used in all other screens, where reference to a user group is made.

57

jchauvin jj/12/13

7.5.3.

Permissions

This menu is only for the Full version of DINO+.

The user groups access rights are defined in "permissions" in the software. This lists the possible access of
a user to "write" (modify) into each "object" of a configuration into the PC database, and to access the various
"action" commands. The access to modify this feature is controlled by the access rights of the user, which is
logged into Dino+. Only users of group Administrator have access.
The "Permissions" menu in the "Tools" menu allows to define the access rights within the software for user
groups.
For each defined group, there is a column, in which each single access right can be granted (by marking) or can
be denied (by leaving the field blank).
The permission list contains parameters regarding the communication: Client and Logical Device permission.
these control which access rights a user can get to a meter.
The permission list contains all menu items, as they are described in this manual. This allows to restrict the
possibilities of some user groups regarding the functions of the software package.
The permission list contains all single configurable parameter-objects of the configuration of a meter (meter
type dependent). By this, for each user group, it can be controlled which parameter is allowed to be modified in
a given configuration or in a meter. When a permission for a certain object is missing the user will not be able to
download a configuration into a meter, which will write to this object.
A user of the group Administrator has always all user rights enabled. This cannot be changed.

Modifications to the permissions are done in the UI directly, by selecting a function and afterward ticking or unticking the permission in the column of the user group. The function list itself cannot be modified.
If a complete row or column is selected by clicking into the headline or into a function description, all fields in
the selected area can be de/selected automatically by using the Select/Unselect button.

58

jchauvin jj/12/13

7.5.4.

Meter management

This feature allows the system users to keep track of meters, which are installed in the system, to sort them into
groups and to import/export them. The feature allows all necessary data definitions for the operation of the
whole system.

The application provides 2 user interfaces: Meter Groups and Meter

7.5.4.1. Meter Group

It is possible to create meter groups, which are used to group several meters.
This user interface allows to Add, Edit or Delete a meter group (group name and comments).
A meter group consists of a name and an optional comment.
If a name is entered it is only accepted if it is unique in the data base.
If a meter group is deleted, all assignments of meters to this group are cleared. (a warning window with the
possibility to cancel the operation is provided). The meters themselves remain in the database of the system,
without reference to a group.

59

jchauvin jj/12/13

7.5.4.2. Meter
Each meter, which is installed in the system is represented by a set of data comprising all necessary
parameters to select the meter and communicate with it. It is also necessary to have a meter in the database to
be able to display readings of this meter.
The user interface allows to Add, Edit, View or Delete a meter.
The user interface lists the configured meters in tabular form.
It is possible to sort the list in an alphanumerical way, based on each column.
A meter in the list can be highlighted, by clicking on it. Selecting the Edit function from the menu, double
clicking or activating a context menu by clicking with the right mouse button opens a detailed dialog.
The Delete function is controlled by an additional security dialog.

When Add is activated, a blank meter definition dialog is opened, which allows to specify the necessary data
of this meter. Some fields are pre-filled by the information coming from the set-up feature of the system.

60

jchauvin jj/12/13

The set-up feature of DINO+ allows to specify several parameters, which are used when adding a meter to the
database: the default connection type, the default speed for a modem communication, the default passwords for
the different clients and the default addresses for the different devices.
Each time a new meter is configured, the default values are pasted into the corresponding fields, but can be
modified.

61

jchauvin jj/12/13

7.5.5.

Meter Initialisation

This feature is used to download default addresses and passwords, as defined in the Set-up of the system, into
a meter. It only works if the connected meter has not been modified for those parameters after manufacturing.
For the typical usage of the system, this feature allows to adapt meters, which are delivered from the factory, to
the default communication parameters of the system user, by this allowing easy integration into the system
It first displays a screen, which allows to select a meter type (the proposed value is coming from set-up), a
physical channel for connection, and the necessary parameters (speed, telephone number if connection with
modem). The Choice of Communication Type depends on Meter Type (See Connect Error: Reference source
not found).

If the initialisation is launched, it uses these parameters to log on to a meter and download default addresses
and passwords, as defined in the Set-up of the system.
Then it opens the meter management feature for adding a meter, with the data which are programmed in the
meter (password, addresses), and the choice of meter type, speed and telephone.

7.5.6.

Field download

This function permits to change the firmware source code included in the meter on site. This function is
accessible on menu Tool only when no connection exists currently.
This function could be disabled by software security module if specified.
Only the external firmware (firmware located in the external Flash) can be upgraded. So, it is mandatory that
the new firmware version is compliant with the internal firmware (firmware in the C mask)
If the new firmware version database is compliant with the old one, the meter is able to restarts after the field
download as after a power failure. Otherwise, all metering data (current and historical), status and histories are
lost.
Modem access is not requested for the field download (local action)
The firmware download is performed through the customer or the utility port at 19200 bds

7.5.6.1. Procedure
The download procedure is the following :
1) Read metering data from the meter

62

jchauvin jj/12/13

2) Switch off the meter in order to trigger a current data saving (Useful in case of download of a data
compliant firmware version)
3) Power up the meter
4) Open the meter cover and connect both straps on the J2 connector (1-11 and 9-12)
5) Cosem connexion in the Electricity Laboratory / Management logical device context (allowed also for the
Manufacturer client)
6) Read the meter variant (SL761, 762 ) and the firmware versions to check the compatibility of the new
version to download
7) If the new version is compliant, send the new Cosem script ENTER_DOWNLOAD_MODE to the meter. A
message must be displayed by the tool to indicate to the user if an erase all is mandatory or not
8) Close the Cosem communication. So, the script is taken into account by the meter
9) The manufacturer parameters are saved in Flash and then the meter stops to reset the watch dog in order
to trigger a restart of the application and to allow the entry in the download mode.The choice between an
erase all and an erase code is done following the state of the laboratory switch (activated = erase all,
released = erase code). The meter display ERASE CODE or ERASE ALL following the choice. The ERASE
ALL function erases all the flash code and data, excepted the sector used for manufacturer parameters
saving
10) When the message DOWNLOAD is displayed, the meter is ready for the code loading (see protocol
specifications). During the loading, the meter displays FRAME OK
11) Remove the straps before the end of the loading. If it is not done, the meter will restart again in download
mode and the code must be reloaded
12) When the loading is completed (<10 @19200 bds), the message RESET is displayed and the meter
restarts in normal mode
13) If the meter detects a first power up (case of the erase all), the manufacturer parameters are loaded from
the Flash memory (after a coherency check). All parameters (customer and manufacturer) are saved in
Flash

7.5.7.

Current Transformer/Voltage Transformer correction

The meter is calibrated in factory by programming the Reference Calibration parameters. The Reference
Calibration parameters are automatically copied into the Customer Calibration parameters which are the
parameters used by the meter.
The CT/VT error compensation, phase and amplitude, is performed by reading the meter Reference Calibration
parameters, applying the correction required by the customer and programming the Customer Calibration
parameters into the meter . The Reference Calibration parameters are not modified.

63

jchauvin jj/12/13

64

jchauvin jj/12/13

7.5.8.

Set-up

This menu item allows to configure some important parameters for the system itself. After the first installation,
default values are used, until the user modifies and saves them.
7.5.8.1. Set-up for communication
This feature allows to specify separately the communication ports of the PC:
for IR-communication,
direct links,
and modem connection.

The "initialisation strings" allow to define initialisation parameters, which will be sent by the PC to the modem,
prior to dialling, in order to prepare communications.
The TimeOutResponse parameter controls how long the system is waiting for when establishing a modem
communication.

65

jchauvin jj/12/13

7.5.8.2. Set-up for DLMS/COSEM communication

This feature allows to modify the default parameters used in the PC application, for the Dlms/Cosem
communication.

66

jchauvin jj/12/13

7.5.8.3. Default values for meter

This feature allows to modify the default parameters, in the meter, used for the Dlms/COSEM communication.
The values shown in this screen are not used for a communication with the meter, other than the meter
initialisation feature. They are used as the default values filled in the fields of the meter definition screens, when
adding a new meter to the database.

67

jchauvin jj/12/13

7.5.8.4. Other Set-ups

This feature allows to specify standard directories for the different import/export features.

permission import/export

meter import/export

data import/export

configuration import/export

It specifies the storage of reading data.

It allows to specify the roll off time for the log file and for the communication history.
A new field can be added. The dates format may be changed. The first time, it is the format defined for the
language (in database) if found or English format otherwise (month/day/year). These data are taken in account
at the next login. The three available formats are dd/mm/yy or mm/dd/yy or yy/mm/dd

68

jchauvin jj/12/13

7.5.8.5. HHU setup

This feature allows to specify standard directories where to export Job files and from where to import Results.

7.5.9.

Localize

This function enables you to change the language of the software. It is accessible only when all the screens are
closed.

7.5.10.

Database repair

This function enables you to repair the database.

69

jchauvin jj/12/13

7.6.

HHU

The HHU is a mobile data collection equipment used to read SL7000 data on site. This function could be
disabled by software security module if specified.
The complete system is based on 2 existing packages:
DINO+ which allows to configure and to read all relevant data in the SL7000 Smart Commercial &
Industrial Meter. It contains a meter management feature, a configuration creation and management
feature and a reading/data display feature
PRACDIS/GT-R, which allows to get route files for reading of electricity meters according to jobs,
related to each meter, by the means of handheld units. The reading results are interpreted to be sent back
to a supervising software (typically a billing system). The package allows to influence the performance of
the reading at every level. This system is not described in this manual.
7.6.1.

Typical read operation

In a typical read operation, a billing system is exporting a route file, which contains several meters, from
which the billing information shall be collected and returned to the billing system.
The collection of the information of one meter is controlled by a job file. Different job files may be
required for different meters in a route file.
The route file contains all necessary information to find and identify a meter and a reference to the job
file to be used with this meter.
The route file may be influenced on PRACDIS/GT-R level to allow to move meters from the allocation
from one individual HHU to another. It may also be influenced to modify the job file reference of a
meter.
A job file contains all necessary commands to be performed, while reading a meter. Those commands can be
reading commands only, but may also be commands to influence the behaviour of the meter or to re-configure
it. All needed job files for the operations on meters type SL7000 are created on DINO+ and exported from there
to PRACDIS/GT-R. On PRACDIS/GT-R level there is no possibility to modify a job file.
In PRACDIS/GT-R the combination of route and job files is loaded into the targeted HHU. This HHU is
able to interpret the route file to identify a meter and to allow to find it physically. When the reading
operation is triggered on the HHU it is performed according to the operations described in the job file,
which is referenced for the connected meter. An automatic check shall assure, that the connected meter
is verified against the meter active in the route file. In each job file the first instruction set shall deliver
the necessary data for this verification.
The data, read according to the job file, is stored in the HHU in slightly interpreted format, which allows
to extract a few of the data according to the last instruction set in the job file and to display them locally
on the HHU.
In case of not working communications the HHU is able to store manual data entries for pre-defined data items.
When the HHU is re-connected to PRACDIS/GT-R it is possible to upload all data to this package.
PRACDIS/GT-R can interpret the necessary data to fill the data needed for the billing system. The
identification of those data is done based on OBIS codes.
PRACDIS/GT-R can transmit all those data to the controlling billing system.
It can also export the stored data files in the data file format to DINO+ for the local display and post
processing of data in this package. The major use is for non-billing data.

70

jchauvin jj/12/13

7.6.2.

Interaction of the packages

The following figure illustrates the data flow between the different modules of the whole system:

Billing System
route file

billing data

job files

PRACDIS/GT-R

DINO+

reading data

meter data
route
file
reading data

job file

HHU

configuration data

reading data

Meter

The connection to the billing system may be omitted and replaced by local generation of route files on
the surface of PRACDIS/GT-R.

71

jchauvin jj/12/13

7.6.3.

HHU function in DINO+

This menu is composed of 3 items :

-

Jobfile management (including export jobfile)

Import Results (data read by the HHU)

Select configuration items for HHU (Automatic Selection of writtable objects)

72

jchauvin jj/12/13

7.6.4.

Job file management

This windows is displayed when user clicks on Job File management. The existing Job Files in the data base
are displayed. From the screen the user can add, delete, view, edit and export a selected Job File.
The meter type and firmware version parameters have to be known according to specific version.
Export file : Before the file export, a control is done to check the selected objects of the configuration. If the
configuration is not compatible according the HHU authorised objects a specific message is displayed :

73

jchauvin jj/12/13

7.6.5.

Job file editing

This screen appears once the user edits or adds a Job File. This screen summarises the authorised
objects to read or program via a HHU.

Job definition :The meter type and firmware version have to be define for each Job File. The values will
be placed in the header of each Job File as a comment.
Two specifics Get commands are mandatory in the Job File: Get Metertype and GetFirmwareversion.
These informations will be used by the HHU software to control the connection with the good meter type.
Meter type and Firmware version will be placed in the header of each result data files.
Data reading is selected from this list :
Total Energy registers
Energy rate registers
Demand registers
Maximum registers
Historical data
Partial load profiles
Date and time, meterID
Logbook
Instantaneous data
Network history
Meter history
Voltage quality data
Tampering data
Meter status

74

jchauvin jj/12/13

Configuration parameters:

The configuration is selected from the existing one in data base.

Once the Job File is editing it has to be saved. Before the saving a control is done to verify the
configuration objects selected are authorised for HHU communication. If at least one object is not
authorised a warning message will be display to the user .
Once the Job File is correct it is saved in data base, ready to be exported.
The reference of the configuration will put in the Job File. To write a configuration the client profile has to
be Electricity Field. A validate command is mandatory after a set command.

Set Date & Time : The date & time to program in the meter will be taken from the HHU. The clock
synchronisation is up to the system manager. A validate command is mandatory after a set command.
Action : A validate command is mandatory after an execute command.
Only 3 actions are authorised to the user :
Reset the max demand before the data reading
Reset the max demand after the data reading
Reset the non fatal errors

To connect to a meter the HHU has to know its specific parameters (password, physical address ).
The user has to export a meter file which collects the parameters for all the meters to connect with the
HHU. The Pracdis package will take the connection informations from this file.

75

jchauvin jj/12/13

7.6.6.

Import Data from HHU

The corresponding feature in the menu is Import Results. This action permits to import the meters
references and the associated data read with the HHU.
The process is divided in two phases :
1- Read at the beginning of each Job File the MeterType & FirmwareVersion with Get command. The
MeterName will be given with the name of the File including these objects (MeterId). With these
informations the local database for the meters will be updated. If existing reference a message is
displayed to the user.
2- Then as the meter references are known, the corresponding tree view can be displayed and the
data viewed.

7.6.7.

Automatic objects selection

This action is useful to select automatically in an open configuration, all the authorized objects for HHU
function. A tick appears in front of each concerned object.

76

jchauvin jj/12/13

7.6.8.

HHU Setup

This screen is used to validate the path where to export jobfiles and from where to import
meterfiles & reading files.

7.6.9.

Permission list

If the HHU function selected, the permission list has to include the new HHU functions :
HHU/Job : Add, Edit
HHU/Job : Delete
HHU/Export Job file
HHU/Import Results

77

jchauvin jj/12/13

7.7.

Help
7.7.1.

Dino+ Help

The context sensitive help displays a message indicating the User manual file to open. The file is a word
document placed in the application directory.
7.7.2.
About DINO+
A screen allows to identify the used version of the software package.

printer
RS232
COSEM
modem
RS232

database

COSEM

78

jchauvin jj/12/13
modem

79

jchauvin jj/12/13

Each menu item, which is not accessible for a user, or which is not functional in the current context of the
application is shaded.
The following chapters explain the usage of the menu item.
File
This Menu item deals with all import/export possibilities of the system and allows to Exit the program.

80

jchauvin jj/12/13

81

jchauvin jj/12/13

Error: Reference source not foundError: Reference source not foundError: Reference source not foundError:
Reference source not found

Error: Reference source not found

Each menu item, which is not accessible for a user, or which is not functional in the current context of the
application is shaded.
The following chapters explain the usage of the menu item.
File
This Menu item deals with all import/export possibilities of the system and allows to Exit the program.

82

jchauvin jj/12/13

83

jchauvin jj/12/13

84

jchauvin jj/12/13

Reading

85

jchauvin jj/12/13

Error: Reference source not found

86

jchauvin jj/12/13

Reading

87

jchauvin jj/12/13

88

jchauvin jj/12/13

Error: Reference source not found

89

jchauvin jj/12/13

90

jchauvin jj/12/13

91

jchauvin jj/12/13

92

jchauvin jj/12/13

93

jchauvin jj/12/13

route file

Billing System billing data

job files

PRACDIS/GT-R

DINO+

reading data
meter data

route
file

reading data

job file

HHU

configuration data

reading data

94

Meter

jchauvin jj/12/13

95

jchauvin jj/12/13

96

jchauvin jj/12/13

97

jchauvin jj/12/13

98

jchauvin jj/12/13

Error: Reference source not found

Error: Reference source not found

99

jchauvin jj/12/13

100

jchauvin jj/12/13

101

jchauvin jj/12/13

8. CONFIGURATION FOR SL7000 SMART C&I METER

8.1.

Overview

The configuration is a set of parameters to run the meter according to the customer context. A configuration is
readable and programmable.
The configuration parameters are viewed as a tree with main branch and sub-branches.
Each branch of the tree has a connected user interface, which allows to see/modify the values defined for each
field.
Upon reading the configuration of a meter all fields are filled with the data read back from the meter.
Upon opening a configuration from the database, all fields are filled with the corresponding values from the
database.
Access to change the values of fields is limited by 2 factors:
-

The access is limited to those fields, which can be modified inside the meter, according to the
connection to the meter, which is foreseen (see chapter Client).

The access is limited to those fields, which are given access rights for the user group of the
software, the current user belongs to (see chapter Permissions).

Each time a field content is modified, the software will propose to download this modified field into the meter.
This is indicated by activating the button to be transferred for the relevant object. All fields which belong to
one object will be downloaded at the same time (if modified or not). Fields which form one object are identified
on the screen by a frame.
A general check for consistency will be carried out each time a screen is swapped to another. The result of this
consistency check will be indicated in the tree window.

8.2.

Configuration parameters

The different User Interfaces and the corresponding configuration objects are listed in table below.

First level
Resources

Tags

Client selection
Identification

Metrology

Connection
Secondary metrology

Auxiliary I/O

Control lines
External tariffication
Pulse inputs
Pulse outputs

102

Configuration objects
Meter Type
Hardware resources (7K - installed I/O boards)
Firmware resource level
Firmware version
none
Utility IDs (9 comment registers for free usage)
Programming ID and related data
Initialisation ID and related data
Manufacturer ID
Serial number
Meter connection
Network
Transformer ratio
Energy calculation
Power calculation
Control Input physical parameters
Control Output physical parameters
Control Input parameters
Pulse Input parameters
Pulse Input weight
Pulse output parameters
Pulse output weight

jchauvin jj/12/13

First level
Energy calculation

Tags
Total energy
Summation
Energy rates
Excess energy
Parameters
Demand rates
Excess demand

Demand calculation

Load profile
RTC

Time of use

Index parameters
Future Calendar

Special days
Current Calendar

End of billing

Parameters
Control

Display

Parameters
Display/readout table
Voltage monitoring

monitoring

Power failure
Battery monitoring
Logging/alarms

Logbook control
Alarm control
Optical port (SL761xxxx )

Communication

IEC870 (SL762xxxx )
Utility port

Customer port

103

Configuration objects
Total energy parameters
Summation definition and parameters
Energy channel parameters
Excess Energy
Demand parameters
Demand channel parameters
Demand Quantity and Rates
Demand Threshold
Parameters
Channel parameters
Clock setting parameters
Clock base
Synchronisation parameters
DST parameters
Programmed DST parameters
Generic DST parameters
General parameters
Index parameters
Calendar Name
Seasons
Week profiles
Day profiles
Activation date (due date and time)
Special days
Calendar name
Seasons
Day profile
Week profile
Init parameters
Action parameters (Time out control)
Programmed dates
Generic dates
Periodic dates
Display List
Display and readout table
Voltage threshold parameters
Network survey parameters
Long power failure
Battery threshold parameters
Battery end of life parameters
Logging parameters
Alarm parameters
Device address
Proposed baudrate
Response time
IEC1107 data parameters
Laboratory switch enabled
Data Link Address
Application Address
Password
Communication speed
Transmit window size
Inter character time out
Inactivity time out
Communication speed
Transmit window size
Inter character Time out
Inactivity time out

jchauvin jj/12/13

First level

Tags
Modem parameters
Modem set-up

Configuration objects
Talking mode
Listening window
Number of calls
Communication speed
Initialisation string
modem profile

Tree entries which are not accessible are marked by a lock icon.
-

104

jchauvin jj/12/13

8.3.

User interfaces

The screens for configuration is divided into 3 parts:

On the upper left corner is a window which contains a picture of the configuration tree. This window gives
primary information about the accessibility of tree element, of consistency between elements of different tree
branches and if components inside a tree branch are marked for download into a meter.
The right part of the screen contains special user interfaces (UI) for every tree branch, when selected in the tree
window. Each of those UI, defining configuration objects, have a tick box indicating the contents to program to
the meter (exception : Client selection, resources which are not programmable). If an object is downloaded to a
meter, all fields of this object are transferred.
In each of those user interfaces, the headline, indicating an object is greyed out, if the object is not accessible in
the current session. In this case no field of the object can be modified, but the fields show the value currently
configured for it. Every test of consistency will take those values into account.
Each of those UI contains navigation buttons, which allow to switch between branches of the configuration tree:
-"Previous" : will automatically save and close the current UI and activate the first UI of the previous
tree branch.
-"Next" : will automatically save and close the current UI and activate the first UI of the next tree
branch.
Both buttons will not switch between tags inside a configuration tree branch.
The displayed screen is highlighted in the configuration tree.
Switching can also be performed by clicking on a tree entry. This closes the current UI and opens the first tag
of the selected tree branch.
Changing between tags of a tree branch can only be done by clicking on the tag identified at the top of the UI.
DINO+ manages coherence between all the parameters of the configuration. When the settings of a UI create
an incoherence with one or more other branches of the configuration tree, all concerned branches are marked
by a warning icon
on the tree. Using the Previous or Next buttons in a UI is only possible if the
actual UI does not belong to an inconsistency. The closing of a UI which is part of an inconsistency is only
possible using the Cancel button or the Close icon, unless the reasons for inconsistency are cleared before.
If there are inconsistent branches on the configuration tree, a third window appears below the tree window,
listing all encountered inconsistent items together with information which allows to resolve those
inconsistencies.
Closing a window is like operating the Cancel button: the changes done on the data are not taken into account
for this screen.
Saving or Opening a new configuration is done through the menu structure of DINO+.

105

jchauvin jj/12/13

8.3.1.

Configuration tree

After opening a configuration, a tree is presented which contains the main parameter groups of a configuration.

Two buttons, "Select ALL" and "UnSelect ALL", permit to remove or select objects to be transferred to the
meter, and the related coherency checks.
The configuration is composed of two types of parameters for the meter :

The parameters which are programmable in operational mode

The parameter which are programmable in non-operational mode. A stop measurement has to be
done before this programming and a start measurement must be done after (by menu
Communication > Write >Action > Management Actions, while the internal switch (laboratory
switch) of the meter is depressed).

Here below the list of objects to be programmed in non-operational mode (restricted access) :

Input Pulse Parameters,

Output Pulse Parameters

Energy Parameters,

Total Energy,

Demand Parameters,

Demand channels,

Load profile parameters,

Load profile Channels,

Summation,

Billing Period Parameters,

Readout,

106

jchauvin jj/12/13

Index Manager, Index.

107

jchauvin jj/12/13

8.3.2.

Quantity selection

The meter processes a large basic measurement quantities. Whenever necessary to select a quantity for a
configuration parameter, a tree containing all available quantities is accessible. The selection is made by
clicking on the quantity item in the tree.
Quantities for pulse inputs are presented as Wh, varh, or VAh aggregate (agg) or per phase (ph1, ph2, ph3), for
import (+), export (-), and "ext". "ext." Is only possible for quantities based on pulse inputs. It means that the
actual energy direction is determined by a the level of a control input (in positive logic, a voltage presence on
the control input is determining an "import" direction of energy for the pulse input).

Keeping a previously defined quantity for a configuration object can be achieved by closing the quantity
selection window with the close icon in its headline.

108

jchauvin jj/12/13

8.3.3.

Resources

This screen summaries the hardware meter configuration (I/O board, meter type) and firmware
meter configuration (firmware version, resource level). These parameters have to be defined by the
customer before to order meters.
This will limit the availability of the parameters in the following screens. The resources are checked
against a real meter when transferring the configuration.
DINO+ does not allow to program the resources level in a meter.

I/O board : The selection of hardware resources is done by a list box, which presents the available I/O
boards. The selection list is detailed in the next table :
I/O board

Physical board

Additional board
Utility Port

Customer Port

Full I/O

Full I/O

Full I/O Com 232

Full I/O

Full I/O Com 232 + 232

Full I/O

RS 232

RS 232

Full I/O Com 232 + 485

Full I/O

RS 232

RS 485

Light I/O Com 232

Light I/O RS 232 Utility

Light I/O Current Loop

Light I/O Current Loop Utility

RS 232

No I/O

109

jchauvin jj/12/13

Full I/O board

Light I/O board

Number of Control Inputs

Number of Control Outputs

Number of Pulse Inputs

Number of Pulse Outputs

Resources level :The Firmware resources are organised in levels (level0/level1//level4).

Level 0
Energy
Demand

Level 1

Level 2

Level 3

Level 4

Channels

10

Rates

10

24

24

32

Channels

10

Rates

15

18

24

Load Profiles Channels

The resource level has to be selected manually if a configuration is created offline. When a
configuration is modified, the resource should not be modified, otherwise a lot of configuration
parameters will be invalid.
When a configuration is read back from the meter the correct resource information is set automatically.
DINO+ does not allow to modify the firmware resources available in a meter.
As soon as a resource level is selected, the firmware displays details about available Energy-, Demandand Load Profile Channels/Rates for information. This information cannot be modified.
When the configuration is downloaded into an actual meter, the resources are checked against the
settings in this screen and will inhibit the configuration transfer, if there is no match, where it is needed
to create a consistent configuration.

Voltage quality resource : The availability of this firmware resource is identified by a tick.
Meter Type : DINO+ software is designed to manage several meter types (SL761 for IEC1, IEC2, IEC3
and SL762 for IEC1+). According the meter type the configuration parameters could be different.
Firmware version : Its an information to identify the external firmware version. According to the
firmware version the configuration parameters could be different.
Some configuration objects or access rights to some objects may depend on this value.
The firmware version has to be selected manually, if a configuration is created offline. When a
configuration is modified, the version should not be modified, otherwise a lot of configuration
parameters could become invalid.
When a configuration is read back from the meter, the correct version information is set automatically.
DINO+ does not allow to modify the firmware version in a meter.
When the configuration is downloaded into an actual meter, the firmware version of the meter is
checked against the setting in this screen and will inhibit the configuration transfer, if that could lead to

110

jchauvin jj/12/13

create an inconsistent configuration. In other words, the consistency checks depth depend on the
firmware version.

111

jchauvin jj/12/13

8.3.4.

Client level

8.3.4.1.
The client level defines which user level is needed to authorise the configuration programming.
According the client level, the access rights to program the configuration objects could be various.
These configuration objects access rights are hard coded in the meter.
The hierarchy of Clients is (from highest level of permissions to lowest):

Electricity Utility Laboratory (technical Utility people in Utility labs);

Electricity Utility field (technical Utility people for field operations, like meter
commissioning);

any reader (electricity, gas & water reader),

end customer,

engineer (Maintenance personnel, with read-only access to all objects, allowing

effective troubleshooting).

A configuration will be accessible to the current user only if the client level of the configuration
is at least the same level as the current user.
Example : the client level defined for the configuration is Electricity Utility Field, a current user could
be Electricity Utility Laboratory or Electricity Utility Field. A current user end customer has no access
rights to program this configuration.
T

he UI defining the Client contains only 1 dialog area.

112

jchauvin jj/12/13

113

jchauvin jj/12/13

8.3.5.

Identification

This UI allows to set/read 9 separate comment fields called identification ("ID") in the meter.

Utility comments (1 to 9)
These are data fields (up to 8 characters each) that can be programmed or read in a meter.
Their content has no influence of the meter behaviour.
They can be used to register some parameters, relevant for the utility, into the meter memory.
The contents of those fields can be read from a meter for reference purposes, or can be
displayed on the display of the meter.
Programming Summary :
Number of programming : This value can only be read from a meter, or from the database if
the relevant configuration was stored after reading it from a meter. The value is incremented
automatically by the meter at each successful parameter programming (any type) or each
ACTION.
Date of last programming : Date and time of the last event which caused to increment the
Number of programming counter. This field is updated by the meter itself, it cant be
programmed.
Programming Id :
Data fields (up to 8 characters) that can be programmed or read in a meter. Its content has no
influence of the meter behaviour. The usage is for reference only.
It could be programmed at the end of the configuration programming to identify the
configuration.
Initialisation Summary :
Number of Start Measurement: This value is incremented by the meter itself at each
successful "start measurement" action. This data cant be programmed in the meter.

114

jchauvin jj/12/13

Date of last Initialisation: Date and time of the last event, which caused to increment the
Number of Start Measurement counter. This data cant be programmed in the meter.
Initialisation Id :
Data field (up to 8 characters) that can be programmed or read in a meter. Its content has no
influence of the meter behaviour. The usage is for reference only.
It could be programmed at the end of a configuration programming, requiring a stop
measurement, to identify a particular set of parameters
Manufacturer ID
This value can only be read from a meter, or from the database if the relevant configuration was
stored after reading it from a meter. This value is stored into a meter by the manufacturer.
Serial Number
This value can only be read from a meter, or from the database if the relevant configuration was
stored after reading it from a meter. This value is stored into a meter by the manufacturer. The
serial number has 8 possible digits and is shown like it is written in the meter dialplate.

115

jchauvin jj/12/13

8.3.6.

8.3.7.

Metrology

This branch of the configuration tree allows to define the configuration of the meter regarding the functionality of
the metrology. It contains 2 user interfaces, one called Connection to define the connection parameters of the
meter, and the other called Secondary Metrology for the settings to define the energy and demand calculation
method.
8.3.7.1. Connection
This UI allows to configure the connection parameters regarding connection type and values.

Meter connection: This parameter is set by Manufacturing into the meter. It will be read back
each time a meter configuration is read. It can be modified on the screen, but will never be
downloaded into a meter. It will be used to check the consistency of a configuration with the
type of a connected meter.

116

jchauvin jj/12/13

Within the screen the connection type (3 or 4 wires) and the transformer ration shall only be
configurable, when the meter connection transformer is selected.Auxiliary Power Supply is a
new field to configure for GENIEC2 and GENIEC3 only.
Network : The connection type can be chosen between 3 wire and 4 wire network.
With 3 wire configuration the meter will work as a 2-element meter, any current driven through
the phase 2 element will be discarded. This is the setting for connection of the meter to an
installation with 2 current transformers. This selection is not available if the meter is defined to
be for direct connection.
With 4 wire configuration the meter will consider the current of all 3 elments for the calculation
of energy and power. This is the setting for connection to installations with 3 current
transformers and for direct connection.
The nominal frequency can be chosen according to the network frequency the meter shall
The Current Rating is just reminded here. If meter connection is transformer, the current rating
list is: 1/2A, 1/5A, 1/10A, 1.5/6A, 5/6A, 5/10A. The current rating list for a direct meter
connection is: 5/6A, 10/60A, 10/80A, 5/120A, 10/120A, 15/90A, 20/120A.
The nominal current is just reminded here. If the current rating is a/b A then the nominal
current must be strictly higher than a and less than or equal to b. The max instantaneous
power is calculated using nominal current entered by the user.
The nominal voltage list for a 3 wires connection type is : 100V, 110V, 220V, 230V, 400V, 415V
the nominal voltage list for a 4 wires connection type is : 57.7/100V, 63.5/110V, 127/ 220V,
220/380V, 230/400V, 240/415V.
As the meter is fully auto-ranging with regard to voltage, this value is just entered for reference
and has no direct effect in the meter behaviour.
Transformer ratio : For a CT meter, all "energy" related values are presented in primary
values, i.e. the measured values (secondary values) are multiplied by the transformer ratio that
is defined here.
Auxiliary power supply : The meter is able to manage an auxiliary power supply to allow the full
functionality of the meter whatever the behavior of the mains network. This parameter is done to
use the auxiliary power supply or not (if the meter includes this function).

117

jchauvin jj/12/13

8.3.7.2. Secondary Metrology

This UI defines the calculation modes for energy and power.

Energy calculation
All energy rate registers have a common behaviour regarding time integral:
In cumulative mode the energy is accumulated from the "start measurement" of the meter,
without any reset at the end of each billing period.
In reset at EOB mode energy is accumulated from the beginning of a billing period until the
end of the billing period, and will be reset, after storage in historical values, prior to start a new
billing period.
This parameter has no influence on the Total Energy Registers. Those always work in
cumulative mode
Power calculation
The Apparent Power (kVA) calculation mode is only relevant if apparent demand or energy is
used. It can be calculated according to one of the following method:
"Arithmetic": the apparent power is calculated as S = U rms . Irms (true apparent power, will give
good results above Ib/10);
"Vectorial": the apparent power is calculated as S = P 2 + Q2 (this method is more precise than
the other, specially at low current, but will show higher susceptibility to harmonics contents in
the meter).
The aggregate energy calculation mode allows (for the 4-wire 3-element meters) to determine
how the per phase energies are combined to calculate the aggregate energy:

Algo1 :Net values: Pagg is calculated by adding the energies of the phases which are
importing, and subtracting the energies of the phases which are exporting.

Pagg = Ph1 imp energy + Ph2 imp energy + Ph3 imp energy (Ph1 exp energy + Ph2
exp energy + Ph3 exp energy)

118

jchauvin jj/12/13

if Pagg > 0 Pagg is stored in P+agg , P-agg = 0

if Pagg < 0 Pagg is stored in P-agg, P+agg = 0

Algo2 : Sum of positive phases: P+agg is calculated by adding the energies of the phases
which are importing, P-agg is calculated by adding the energies of the phases which are
exporting. Only the bigger one is counted, the other one is set to 0.

Algo3 : Simultaneous calculation in two directions: P+ agg and P-agg are calculated.

8.3.7.3.

8.3.8.

Auxiliary I/O

This set of UIs allows to configure all Input/Output lines.

It is composed of 4 Tags : Control lines , External tariffication , Pulse inputs , Pulse
outputs .
The availability of lines is controlled from the hardware resource object.
8.3.8.1. Control lines
This UI controls the allocation of input/output control lines to the meter.

119

jchauvin jj/12/13

For each input or output, the active level is programmable (voltage present or not / contact closed or
open).
For I/O variants of the meter where the terminal numbering is not continuous, the control output
numbering follows the physical terminal numbering.
Control Input Lines
According to hardware resources, control inputs are available (1 for Light I/O, 2 for Full I/O),
and can be individually configured:

If not used, the line can be defined as "Not Allocated".

Clock Synchro : this function allows to synchronise the internal clock from an external
source by sending a pulse on the dedicated input. The internal clock is synchronised to the
nearest round hour. Only one pulse is accepted during an acceptance window of +/- 1
minute around the round hour.

Alarm : the meter will register the occurrence (and disappearance) of an alarm signal from
the outside environment, and can take some actions (record the event in the log book,
trigger a control output alarm, display a warning sign (triangle) on the LCD display). The
behaviour is defined in logging/Alarm feature.

EOB (End of billing) : this function will trigger an End Of Billing, providing EOB from control
input if authorised. The function requires either 1 control input (EOB) - single contact-, or 2
control inputs (EOB1 and EOB2) - change over contact.
"Change over contact" is used to prevent double pulse acceptance in error conditions: in
this case, a transition on an input is only accepted if the previous transition was accepted
before on the other input.

End of integration : this function will trigger an end of integration period; This event from the
auxiliary input will override the internal integration period timer and will add an additional
period.

Pulse Input x Direction : this function allows to define the direction (import or export) of a
pulse input, which was defined to have an external direction signal.
One control input can determine the direction of one pulse input. In positive logic, a voltage
present on the input defines the import direction.

Index bx : this function allows to determine the tariff rates applied to the energy and
demand channels, and possible activation of control outputs, according to the pattern of
control inputs that is applied.
The activation of an authorised pattern (see the tag "external tariffication"), will trigger the
corresponding index (and consequently the tariff rate).
As 50 index are possible (1 to 50), an individual activation of any index would require 6 bits
in binary (b0 to b5), or 6 control inputs. As in Light I/O there is only one control input, and in
Full I/O there are only 2, the possible activations are limited.
According to the chosen bit(s), the corresponding index will be activated.

Exemple 1: if one control input is used and configured as "index b0", with
"positive active level", the detection of a voltage on this input will activate
the index 2 (20+1=2), while its disappearance will trigger the index 1, or if
not authorised (see next screen), restore the internal TOU index (overlay).

Exemple 2: if 2 control inputs are used and configured as "index b0" and
"index"b1", with "positive active level", the detection of a voltage on any of
these inputs will activate the corresponding index (index 1 for b0=0 and
b1=0, index 2 for b0=1 and b1=0; index 3 for b0=0 and b1= 1; index 4 for
b0=1 and b1=1) .

Note: instead of activating b0 or b1, one can select to activate another bit,
for example the activation of b5 (alone) will trigger index 2 5+1=33

Change of day profile : same principle as above with up to 5 control inputs (day profile b0 to
day profile b4), allowing to trigger day profile 1 to 24.

120

jchauvin jj/12/13

Change of season : same principle as above with up to 4 control inputs (season b0 to

season b3), allowing to trigger season 1 to 12.

Control output lines

According to hardware resources, control outputs are available (2 for Light I/O, 4 for Full I/O),
and can be individually configured in a similar way as the control inputs (in the examples taken
below, a "positive active level" logic is assumed):

If not used, the line is defined as "Not Allocated".

Clock Synchro : this function will close the contact (for 1 second) on the dedicated output, in
order to synchronise an external equipment. The action is performed either every round
hour, or once a day at a programmed hour.

Alarm : if configured in "alarm control", the meter will output an internal alarm signal
(contact closed) during the occurrence of an alarm situation, as configured in
"Logging/alarms" - "Alarms control" : EXTERNAL ALARM.

Excess Demand : The relay will close when (and as long as) an "excess demand" is
detected by the meter on any demand rate (refer to "Demand", Excess Demand").

Phase cut : The relay will close when (and as long as) a phase cut situation is detected by
the meter on any phase. The threshold is defined in Monitoring feature, voltage
Monitoring : Cut Threshold.

EOB (End of billing) : this setting will force the meter to close the contact for 1 second at an
End Of Billing in the meter. The function requires either 1 control output (EOB) - single
contact-, or 2 control outputs (EOB1 and EOB2) - change over contact.
"Change over contact" is used to prevent double pulse acceptance by the receiving
equipment in error conditions: in this case, a transition on an input is only accepted if a valid
transition was accepted before on the other input.

End of Integration : this function outputs the information (close the contact for 1 second) of
an end of integration period in the meter;

Pulse output x : it is possible to output energy pulses on control outputs, if the required
voltage for the pulse transmission exceeds the limits of the pulse outputs.
This function can be activated if one has selected under the "pulse output" tag: "Emit on
CO" - "with CO n" (n = 1 to 2 for Light I/O and 1 to 4 for Full I/O). Then the corresponding
information need to be entered in the tag "control output": for example "pulse output 1". The
Ton and Toff timings of the contact are those defined within the "pulse output tag".

Logic Control Output (1 to 8) : this function will close the contact, according to activation
orders defined in "Time of Use" - "Index parameters" . Refer to the corresponding chapter
for a further explanation.

8.3.8.2. External tariffication

If control inputs (external signals) are not used to define the tariffication, this screen is not relevant, and all
fields are greyed in the screen.
This screen allows to eventually restrict the effect of control inputs on the tariffication (if selected in the previous
screen).
If control inputs are assigned to the function Index bx or Day Profile bx or Season bx, this screen will show all
possible index numbers which can be reached by this assignment. This is done by painting a white square
below the index/profile/season number. If this square is activated, it will be indicated by a tick. This will activate
the feature such that if the pattern defining this square is applied to the inputs, this index/profile/season will be
active irrespective the internal tariffication calculation. A square which is not enabled will have no influence
even if the corresponding pattern is applied to the inputs, the internal tariffication will be active.
Exemple 1 :
If, for example 1 control input is used for tariff control, and configured (in the previous screen) as "index b0",
theoretically this allows to select index 1 (if no voltage on the input), or index 2 (if a voltage is detected on the
input). This is shown on the screen by making white the "fields" for index 1 and index 2 - see below.

121

jchauvin jj/12/13

When the fields are white, it is possible to actually activate (or disallow) the corresponding possibility of an
index activation by ticking (or not) the field.
If there is a tick, the corresponding index will be applied when the input has the corresponding status. In the
example of the screen below, index 2 will be activated if there is a voltage on the input, but index 1 will not be
activated when there is no voltage, as the field is not ticked. When this happens, the internal TOU structure will
take over and be applied, until an authorised control input pattern is applied again.

Example 2 :
If, for example 2 control inputs are used for tariff control, and configured (in the previous screen) as "index b0"
and "index b1", theoretically this allows to select index 1, 2, 3, or 4 (depending on voltage conditions on the 2
inputs). Accordingly, the corresponding fields are whitened (this providing the corresponding index are existing refer to "Time of Use" - "index parameters".
It is then possible to select by ticking/unticking, which index will actually be triggered by the control input
patterns. In the example below, pattern for b0, b1 equal 1,0 will trigger index 2; and pattern 0,1 will trigger index
3; other patterns (0,0 and 1,1) will be ignored and restore the internal TOU structure.

122

jchauvin jj/12/13

Example 3: it is possible to select many index numbers from (1 or 2) control inputs (providing the index exist refer to "Time of Use" - "index parameters").
As any index number (from 1 to 50) can be represented in binary with six bits (index_b0 to index_b5), one just
need to choose the appropriate binary weight(s).
For example, for index 11 alone : 11 = 23 + 21 + 1 (+1 is required, as index start from 1, not from 0).
It requires the activation of index_b3 and index_b1, which will be selected in the control input definition screen.
Then in the authorisation screen, one will tick 11 only.

The behaviour for activation of day profile (24 codes on 5 bits) and season (12 codes on 4 bits) are similar.

123

jchauvin jj/12/13

8.3.8.3. Pulse inputs

This screen allows to configure the behaviour of the input pulse lines.

Depending on the hardware selection in the Resource User Interface, each available pulse input can be
configured individually. For each input the quantity and the pulse weight are needed.
The Quantity is selectable from a list button, giving following choices :
-

electricity (active, reactive, apparent);

fluid (gas or water) .

If No Qty is selected, the pulse input will be inactive.

If (and only if) the input direction is given by a Control Input, the quantity with extension "ext" should be selected
(see below).

The pulse weight is configured stating units per input pulse (e.g. 1000 Wh per pulse). The value can be entered
as a fraction, if it is not a simple integer.

124

jchauvin jj/12/13

8.3.8.4. pulse outputs

This screen allows to configure the pulse output functionality.

The number of output lines is defined by the hardware selection in the Resources screen. Available Control
outputs to transmit pulses need to be allocated before in the Control Lines user interface.
There is a maximum of 6 pulses outputs for the full I/O board, and 2 for the Light I/O board.
Each pulse output is defined by a quantity type and the pulse weight (unit -as defined in the screen / pulse).
If "No_Qty" is assigned as quantity, the output is not active.
On each pulse output, it is possible to select a control output to retransmit the pulse (with CO1, etc), with the
same timings as defined here.
The pulse duration and the time between 2 successive pulses shall be >30ms, which corresponds to a
maximum frequency of 16 Hz.
The pulse output weights, defined in unit/pulse (for example Wh/pulse for active energy) in primary values,
must be selected carefully, in order not to exceed the maximum frequency which will result from the choice of
Ton and Toff above.

125

jchauvin jj/12/13

8.3.9.

Energy Calculation

This UI allows to configure the energy calculation and registration. It contains 3 tags :
Total Energy , Summation , Energy Rates .
8.3.9.1. Total Energy
This UI allows to configure the scaler (divider) for the internal energy quantities. The unit and fluid type are
provided for information.

A scaler "Unity" means the meter will store Total Energy data with a resolution of 1 unit (e.g. 1Wh)

A scaler kilo means the meter will store Total Energy data with a resolution of 1.000 units (e.g.
1kWh)reminds of the type of quantity, for example Wh or varh, or Vah;

A scaler Mega" means the meter will store Total Energy data with a resolution of 1.000.000 units (e.g.
1MWh). The resolution cannot be increased later. It shall be correlated with the needed resolution on the
display and for communication. (e.g. if kWh shal be displayed with one decimal, the storage needs to use
the Unity scaler).

Storage range (active energy) for scaler "Unity": 0 Wh to 999 999 999 Wh
Same on display if no decimals and Wh.
If 3 decimals are used, with kWh: 0.000 kWh to 999 999. 999 kWh
If 3 decimals are used, with MWh: 0.000 MWh to 999. 999 MWh

Storage range (active energy) for scaler "kilo": 0 kWh to 999 999 999 kWh
Same on display if no decimals and kWh.
If 3 decimals are used, with Wh: 0.000 Wh to 999 999. 000 Wh
If 3 decimals are used, with MWh: 0.000 MWh to 999 999. 999 MWh

Storage range (active energy) for scaler "Mega": 0 MWh to 999 999 999 MWh
Same on display if no decimals and MWh.
If 3 decimals are used, with Wh: 0.000 Wh to 999 000. 000 Wh
If 3 decimals are used, with kWh: 0.000 kWh to 999 999. 000 kWh

126

jchauvin jj/12/13

Pulse input and summation results share the parameters in pairs according to the relative channel number.

127

jchauvin jj/12/13

8.3.9.2. Summation
This UI allows to configure the 4 available sums.
In a sum definition, all components need to have the same "unit" and "fluid definition.
For each sum it is possible to select an internal quantity and from 1 up to 4 pulse inputs (external quantities) to
be part of the summation. The summation can only be positive (the subtraction is not supported).

For external quantities it is possible to assign import or export quantities, as defined.

For example if "Pulse input 1" (external 1) is assigned to kWh+ (import active aggregate energy): a tick in "1+"
will include the input in the sum, while a tick in "1-" will have no effect.
The list of external quantities in this screen is controlled by the Pulse Input, and is for reference only.

128

jchauvin jj/12/13

8.3.9.3. Energy rates

This UI allows to configure the energy channels (Quantity, scaler (divider), and number of rates).
Depending on the resource level, up to 10 independent energy channels can be selected from all 52 available
energy quantities. Tariffs are applied to these channels with a maximum of 8 rate registers per channel, and an
overall total of 32 rate registers.
It is possible to have a different rate configuration in each energy channel (for example 4 rates for active
energy, and 2 rates for reactive energy).
It is possible to assign one energy quantity to more than one energy channel, to have different tariffs on those.
In this case, the identification of the energy will be completed with an usage label.
If no tariff is applied to an energy quantity (single rate operation), it is not necessary to use an energy channel
for it, as energy register information is fully available in the "total energy" registers (those are dedicated to store
total consumption in one register, independently of tariffs).

The resolution for the rate registers is defined (Scaler: Unity, Kilo, Mega), as for the "total energies", with the
same limitations.
Unit and Fluid type are set automatically, depending on the selected quantity.
A scroll box allows to configure, for each channel, how many rate registers will be available.

129

jchauvin jj/12/13

8.3.10.

Demand calculation

This UI defines the functionality of the demand calculation and the assignment of demand rate registers.
3 Tags are available : Parameters , Demand rates , Excess demand

8.3.10.1. Demand Parameters

This UI allows to configure the main functionality of the demand calculation :

Sliding demand
Mode Block period (Number of subinterval = 1)
The rising value is calculated by integrating the energy cumulated since the beginning of the period over the
total duration of the integration period.
When a new integration period is triggered, the energy cumulated is reset, so the calculation of rising value
starts from zero.
r is in g
v a lu e

B lo c k p e r io d

a c tu a l
dem and

T : T o t a l I n te g r a t io n p e r io d

Mode sliding period (Number of subinterval > 1)

130

jchauvin jj/12/13

The rising value is calculated by integrating the energy cumulated since the beginning of the sliding period
over the total duration of the sliding period.
When a new subinterval period is triggered, the energy cumulated over this subinterval period is reset, so
the calculation of rising value starts from the average of the (n-1) subinterval period demands over the total
duration of the sliding period.
r is in g
v a lu e

S lid in g p e r io d

a c tu a l
dem and

s lid in g p e r io d
( 5 in th is e x a m p le )

S = Subinterval period

s lid in g p e r io d

Subinterval period
Subinterval period is programmable from 1 to 60 minutes, and is common for all channels. The
registers are refreshed every second.
Maximum demands are available as cumulative values and net values, and are date and time stamped.
During the same billing period, the meter stores the four highest peaks of each demand register, the
minimum average aggregate power factor, and the average aggregate power factor.
Number of Subintervals
The total integration period can be split with a maximum of 15 sub-intervals.

Power Up mode : Integration period restart mode

It is possible to configure the behaviour of the meter after power up with regards to the integration period:
Restart mode: a new integration period starts after power up. This will normally leave one
incomplete period for the time before the power down (The integration period timer is reset after
power up).
Resume: the period which was interrupted by power failure continues after power up, in order to
keep a complete integration period (The integration period timer is stopped by the power failure and
restarted without reset after power up).
Synchronise: the integration period is always synchronised with the round hour (The integration
period timer continues to count during the power failure).

Clock modification threshold

This threshold (defined as a % of the integration period - for example for 15 minutes, 4% = 36 seconds),
represents the maximum difference of time, in case of setting the time of the meter, that will not trigger an
end of integration period. In the above example the resulting period might then be maximum 36s shorter or
longer than the theoretical 15 minutes .
This function is mainly used not to trigger unwanted End of Integration when the internal clock is
synchronised every day (or every hour) from an external source through a control input. This has to be
configured according to the global specifications of the application. In IEC standards the precision of an
integration period shall be at least 1%.

Incomplete period mode

The demand calculated for an incomplete integration period may be:
Neglected: the value is not taken into account for maximum demand calculation, and excess
demand control;
Used: the value is taken into account;

131

jchauvin jj/12/13

The same rule applies to power factor, except that the calculation is performed on the real duration of the
integration period; in other cases, the theoretical duration of the billing period is used for average value
calculation.

Excess Demand Control mode

Up to 10 Demand rate registers can be defined as "excess demand" registers.
Excess Demand control can be carried out:
Comparison every second of the rising demand with a threshold ("Rising Value" mode);
Comparison every second of the demand extrapolation to the end of the period, with a threshold.
This comparison is automatically inhibited during the first 30% of the period ("Projection" mode);
Control at the end of the integration period to a threshold ("End of Integration Period" mode).
An "excess demand" event can trigger (according to the configuration): a record in the log book of event, a
warning sign on the LCD display or the activation of a control output.

Power Factor calculation limit

The definition of the power factor PF = cos =

[P]
P2 + Q2
If there is no reactive energy (Q=0), and if the active energy is different from zero, then PF = 1.
As this value is not meaningful, when P is too small, a threshold can be configured, below which the
calculation of the power factor is suppressed. The value configured here uses the same scaler as the P+
(or P- agg is this has a higher scaler).
This function is valid only if P+ agg or P- agg is defined as input to a demand channel.

agg

Demand calculation algorithm

This field is reserved for future use to accommodate specific algorithms for demand calculation.,
The default "standard" demand calculation algorith: an energy type quantity is accumulated in a register, in
order to to process an average value (or a cumulated value) over an integration period.

132

jchauvin jj/12/13

8.3.10.2. Demand rates

This UI allows to configure the demand channels (Quantity, scaler (divider), decimals and number of
rates).

Quantity
According to resource level, up to 10 independent demand channels can be selected from the list of 52
energy quantities (refer to the Technical Brochure). . The quantity is selected from a tree listing all
available energies. They are the same as pulse output (active, reactive, apparent, external and
summation).
The aggregate power factor is assigned to an 11th demand register (without tariffs).
It is possible to assign one energy quantity to more than one demand channel. In this case, the
identification of the demand will be completed with an usage label.

Scaler and decimals

The "scaler" and "decimals" defines the resolution of the data stored in the meter memory (register).
The basic resolution from the meter metrology is 0.1 W (multiplied by transformer ratio). The resolution
for storage is defined by the user.
Caution: the meter will output the corresponding data with a resolution that cannot be better than the
resolution of the storage.

Storage range (active demand) for scaler "Unity", and zero "decimals":
0 W to 65535 W, resolution 1W

Storage range (active demand) for scaler "Unity", and one "decimals":
0 W to 6553.5 W, resolution 0.1W

Storage range (active demand) for scaler "kilo", and zero "decimals":
0 kW to 65535 kW, resolution 1 kW

Storage range (active demand) for scaler "kilo", and one "decimals":
0 kW to 6553.5 kW, resolution 0.1 kW

133

jchauvin jj/12/13

Storage range (active demand) for scaler "kilo", and two "decimals":
0 kW to 655.35 kW, resolution 0.01 kW

Storage range (active demand) for scaler "kilo", and three "decimals":
0 kW to 65.535 kW, resolution 0.001 kW

Storage range (active demand) for scaler "Mega", and zero "decimals":
0 MW to 65535 MW, resolution 1 MW

Storage range (active demand) for scaler "Mega", and one "decimals":
0 MW to 6553.5 MW, resolution 0.1 MW

Storage range (active demand) for scaler "Mega", and two "decimals":
0 MW to 655.35 MW, resolution 0.01 MW

Storage range (active demand) for scaler "Mega", and three "decimals":
0 MW to 65.535 MW, resolution 0.001 MW

Registers overflow warning

The maximum value for Demand is checked to avoid the value to overflow or to be used with low
resolution. Each time the Demand is configured, the memory usage is displayed (in percent). A
comparison is done between the max demand value and the selected storage range.

In case of overflow, a warning is displayed but does not inhibit the use of this configuration. The
user has to verify the parameters before to program it. The meter does any control on its side.
To evaluate the max demand value, the PMAX value has to be calculated and displayed. It
depends of the meter type (DC or CT) :
1- DC meter

4 wires : Pmax = Inominal x Usimple

2- CT meter

3 wires : Pmax = Inominal x Tc x Ucomposed /sqr(3) x Tp

4 wires : Pmax = Inominal x Tc x Usimple x Tp

The max demand value depends on the quantity too : if the quantity is aggregate, the PMAX is
multiplied by 3 (phases).

134

jchauvin jj/12/13

Examples : Meter CT 3 wires 110V, TP=100 (11KV system)

transformer)

I nominal =10A TC=10 (50/5A

Quantity= Wh_ph1+, Total integration period = 15, scaler "unit", and zero "decimals":
PMAX (1 phase)= 110V * 100 * 10A * 10 / sqr(3)= 635 085W
Max demand = PMAX / 4= 158 771W
% Memory Usage= 158 771 / 65535 = 242%
Warning
So change scaler to kilo and 2 decimals
% Memory Usage= 158 771 / 655350 = 24,2%

OK

Quantity= Wh_agg+, Total integration period = 15, scaler "mega", and 2 "decimals":
PMAX (1 phase)= 110V * 100 * 10A * 10 / sqr(3)= 635 085W
Max demand = 3 * PMAX / 4 = 476313 W

% Memory Usage= 476313/ 655350000 = 0,00072%

Bad resolution

So change scaler to kilo and 3 decimals

% Memory Usage= 476313/ 65535 = 726%

Warning

So change scaler to kilo and 2 decimals

% Memory Usage= 476313/ 655350 = 72,6%

OK

Number of rates
According to resource level, tariffs are applied to the channels with a maximum of 8 rate registers
per channel, and an overall total of 24 rate registers.
It is possible to have a different rate configuration in each demand channel (for example several
rates for active demand, and one single rate for reactive demand). At any time, it is possible to
have several rates active for the same demand channel.

135

jchauvin jj/12/13

8.3.10.3. Excess demand

This UI allows to configure the thresholds for excess demand calculation.

Quantity
Up to 10 Demand rate registers can be defined as "excess demand" registers (see "Demand
parameters). The quantity will be selected among a list of the selected demand channels. It is
possible to select no Quantity to indicate no allocation.

Rate
The rate register on which excess control is applied is selected according to the number of rates
defined for the selected channel.

Threshold
The value of the threshold needs to be entered for each excess demand register.

Scaler, unit, decimals

The scaler, unit and decimals of the threshold are displayed automatically with the same definition
as the channel.

136

jchauvin jj/12/13

8.3.11.

Load profile

Load profiling allows to record continuously periodical data into a load profile array (8 channels max).

Parameters
Each quantity allocated to a load profile is integrated over a period of time called the "Recording Interval".

137

jchauvin jj/12/13

This value is unique for all the load profiles and can be chosen between 1 to 60 minutes. It is independent
from the period which is configured for maximum demand calculation.
The recording interval of the load profiles is always synchronised to each round hour.
A "clock modification threshold" (defined as a % of the recording interval - for example for 15 minutes, 4%
= 36 seconds), represents the maximum difference of time, in case of setting the time of the meter, that will
not trigger an end of interval. The resulting interval might then be maximum 36s shorter or longer than the
theoretical 15 minutes .
This function is mainly used not to trigger unwanted End of Interval when the internal clock is synchronised
every day from an external source through a control input.
The value of Clock Modification Threshold shall be between 0% to 5% for SL761xxxx and 0% to 15% for
SL762xxxx (Specific meter variant for Spain).
Load profile channel scaler definition as 2 n is possible. The configuration is common to all load profile
channels, excepted for the channels configured with power factor, Urms or Irms for which the scaler is fixed
and always 10n. An table gives some details on format value definition.

Channel parameters
According to resource level, up to 8 independent demand channels can be selected from the list of 52
energy quantities the meter can measure, plus the power factors, and the average RMS currents and
voltages (secondary values) - (refer to the Technical Brochure).
The quantity selection is done from a tree listing all available energies.
The "scaler" define the resolution of the data that is stored in the meter memory. For the energy type
quantities, its range is from 10E-1 to 10E+6 .
Caution: the meter will output the corresponding data with a resolution that cannot be better than the

138

jchauvin jj/12/13

resolution of the storage.

Maximum value in register before roll out to zero (for active demand):

Storage range (active demand) for scaler "10 E-1": 0 W to 3276.7 W -resolution 0.1W

Storage range for scaler "10E0": 0 W to 32767 W -resolution 1W

Storage range for scaler "10E+1": 0 kW to 327.67 kW -resolution 0.01 kW

Storage range for scaler "10E+2": 0 kW to 3276.7 kW -resolution 0.1 kW

Storage range for scaler "10E+3": 0 kW to 32767 kW -resolution 1 kW

Storage range for scaler "10E+4": 0 MW to 327.67 MW -resolution 0.01 MW

Storage range for scaler "10E+5": 0 MW to 3276.7 MW -resolution 0.1 MW

Storage range for scaler "10E+6": 0 MW to 32767 MW -resolution 1 MW

The Urms values are stored as secondary values. Only the value 10 E-1 scaler is available.
The I rms values are also stored as secondary values. For Direct connected meters, only the scaler 10
E-2 is available, and for transformer connected meters, only the scaler 10 E-3 is available.
For the power factor, only the scaler 10 E-4 is available for data storage.
For the "energy type" quantities, the working mode might be chosen either as averaging or as
cumulative, while for the other quantities, the Working Mode is always Averaging.
The parameter Interval recording factor is added for SL762xxx (Specific version for Spain). The value
is between 1 to 60. (This represents the multiplier defining a second recording interval T2 = k x T 1 ,
where T1 is the first recording interval defined previously).
-

Registers overflow warning

139

jchauvin jj/12/13

See the Demand chapter.

8.3.12.

RTC (real time clock)

Clock setting parameters :

The "Threshold per minute" parameter (expressed in seconds, 0 to 29), is the maximum authorised change
(or sum of changes) of the meter time (internal clock) per minute, following any time change.
It is used to smoothen the time transition from a wrong time to the new value.
If this function is not used, the parameter is left to zero (recommended).
The "threshold per billing period" (expressed in minutes, 0 to 60) has a similar function, applied to a billing
period. 0 if not used.

Synchronisation parameter
This parameter is used to open synchronisation windows when synchronisation pulses are expected: either
once a day at a specified hour, or every hour. The synchronisation window is +/- 1 minute (synchronisation
accepted from xh59min00s to (x+1)h01min00s, if (x +1) is the synchronisation hour). This parameter is
displayed only if a Control Input and/or a Control Output is defined for this function.

Clock Base : The internal clock of the meter can be synchronised either to the mains frequency, or to the
internal crystal. In the second case, a temperature correction algorithm is applied to compensate for
temperature variations, and keep the accuracy within IEC1162 limits.

DST Parameters (Day Light Saving Time): the selectable values are : No DST, Generic, Programmed,
Generic with Season and Programmed with Season:
For generic (repetitive), a couple of dates are defined with different change type (to summer or to winter).
For programmed (fixed dates, non repetitive), 5 couples of dates can be defined with different change
type, each couple concerning the same year. By default, the european rule is proposed.
If With season are defined for the DST mode, the seasons are 1 and 2. The hour of change shall be set to
avoid a change of day, linked to the DST activation.
For the days definition, 1 is the first, 2 the second, etc 0 is the last, -1 is the one before last, etc

140

jchauvin jj/12/13

8.3.13.

Time of Use

In the SL7000 meter, rate switching can be achieved through different ways:

From the internal tariff structure (internal time switch);

From Control Inputs (to activate a season, or a daily profile, or a pattern of rates (called "index");

Or from a combination of the above (with priority to the control inputs).

The meter time switch possibilities are extremely wide and offer large flexibility.
The tariff structure is described in terms of "seasons", of "day profiles", and of "index" (patterns of applicable
rates at a given time. "Exclusion days" complete the definition.

Seasons
"Seasons" are defined as calendar periods where the same "day profiles", separately for each day
of the week, are applicable. Up to 12 seasons can be defined over a January-to-December period.
A "season" is identified by its identification number (starting from 1 on January the 1 st, and up to
12), and is characterised by its starting date. It is applicable until the starting date of the next
season.
If "season" activation is linked to the DST dates (see in "RTC"), then there will be 2 seasons: the
first one (winter for the northern hemisphere) from the 1 st of January until the first DST date, then
the second one (summer for the northern hemisphere) until the second DST date, then the last
period is considered as a season equal to the first one (winter for the northern hemisphere) until the
end of the year.

Day profiles
"Day profiles" might be defined as days where the same rate switching schedule is applicable. Up to
24 different day profiles might be defined (if necessary) within the different seasons. Within each
day profile, a maximum of 16 change of rates is allowed, with an overall maximum of 100 for all
day profiles.

Index (patterns of rates)

Up to 50 applicable rate patterns can be defined within the day profiles. A rate pattern definition
(index parameters) include:

For each energy channel : the applicable rate (from 1 to 8), as only one rate can
be active at any given time;

For the demand channels : whether each demand rate register is active or not, as
several rate registers can be active at the same time;

For the Control Outputs : whether each Control Output line (2 for Light I/O, and 4
for Full I/O) - (is activated or not).

Specific or exclusion days

In addition to the above permanent time switch structure, one is able to assign particular day
profiles to specific days (fixed or moveable holidays, religious holidays, etc). Up to 100 specific
days can be defined, with either a fixed date, or as recurrent (generic) dates, like for example each
1st of January.

The programmed information contains a future and a current time switch structure. The date of change is
programmable. Coherency is checked with the future and the current time switch structure.
8.3.13.1. Index parameters
The first operation to do when defining the TOU structure is to define the different index (patterns of rates) that
will be used.
The UI allows to configure the Index table of the meter, ie defines the active rates for the energy channels, the
demand channels, and the potential activation of control outputs.

141

jchauvin jj/12/13

General parameters

Index activation mode

Rate switching can be applied immediately as defined in the calendar schedule ("immediate"
mode), or can be delayed until the end of an active integration period, if the end of integration time
is not coincident with the switching time ("delayed" mode).

Default index in case of clock loss

A default index must be assigned to the situation where a "clock loss" event appears, as in this
case, the TOU schedule is not activated. Index 1 to 50 (as defined elsewhere) might be selected.

Index parameters
For each different set of rates (index), one should define :

For each defined energy channel, (and according to the number of rates previously
defined), the active rate; it is compulsory that at least one rate is activated for each index;

For each defined demand rate register, whether it is active or not (tick);

For each defined Control Output, whether it is active or not (tick) - (the activation will also
be dependent on the bit number assigned to the index output function of the Control
Output).

Add opens a definition screens and inserts a new index at the end of the list.
Delete marks an index as not used, the numbers of the following index is not changed.

142

jchauvin jj/12/13

All configured energy and demand channels are listed. Energy channels allow to select the active
rate, demand rates can be selected by tick-boxes, outputs can be selected by tick boxes.
Attention: When an index table is modified and downloaded to a meter, it will be
immediately active, even for the current calendar. It will not wait for the future calendar to
become active.
Advice: When a modification to an index table is needed, either new index should be added to
the list and used in the future calendar, or the current calendar has to be corrected by
downloading a future calendar with a due date in the past.

143

jchauvin jj/12/13

8.3.13.2. Future Calendar

This UI allows to configure the future switching behaviour of the meter.

Season
A season is a calendar period which will use the same day profile for the same day of the week, separately
configurable for each weekday.
Up to 12 seasons can be defined and will be used repetitively in the following years, until a new future
calendar is downloaded into the meter and activated.
The date field defining each season starting date gets a text field specifying day (00 to 31) and month (01 to
12). When clicking the first season, the date field shall automatically show 01/01.
The definition of this grid may be empty if the seasons are be defined with DST. So RTC needs to be edited
before Time of Use.

Day profile
A Day Profile is a list of switching points, at which the meter will activate a new index. Within each single
day profile up to 16 switching points can be defined. Across all 24 possible day profiles 100 switching points
can be defined. Each day profile can be used in several seasons 7 weekdays.
The definition requires that for each day profile (DP1, DP2, etc), an index (pattern of rates) is assigned to
each time period, which is defined by its starting time. When clicking the first entry in a day profile the time
field shall automatically be set to 00h00.

Week profile table

This tables defines which day profile (as previously defined) is active for each day of the week of each
defined season. A definition is made by highlighting the selected weekday in the selected season, activating
the desired day profile and selecting the Add feature. (This will override an existing setting) Multiple
selection of days and/or seasons as a block is supported.

144

jchauvin jj/12/13

For each defined season, a day profile for each day of the week is mandatory.

Calendar name
This field is a label (8 characters max), that can be used to identify a particular calendar in a meter.

Calendar due date

The calendar due date is the future date when the latent calendar structure loaded in a meter will replace
the previous one.
8.3.13.3. Special days

This UI allows to configure the special day list of the meter.

For each special day, one must define :

the day profile (from the list defined in "future calendar");

the date, either fixed (with day/month/year), or repetitive (with only day/month).

To add a special day, the requested day profile which shall be active on this day needs to be selected.
The date of the special day needs to be selected. If it is selected as repetitive, the field allows to enter day and
month. If it is selected to be fixed (not repetitive), the field requires to enter day, month and year. The software
will automatically sort the dates in chronological order.
Any day in the list can be highlighted and deleted.
Up to 100 entries in the list are supported.

145

jchauvin jj/12/13

8.3.13.4.

Current Calendar

This UI allows to display the reading of the current switching behaviour of the meter. All fields are shaded as no
inputs are possible. They are filled only by reading back a meter configuration.

The whole screen is only accessible if the configuration on the PC contains the reading of a current calendar.
The meaning of each field is equivalent to the corresponding field of Future Calendar.

146

jchauvin jj/12/13

8.3.14.

End of Billing

A billing period is the period of time between 2 successive maximum demand resets. At the time of reset, the
current values are stored in historical sets (up to 18).
This UI allows to configure the behaviour of the meter with regards to end of billing (EOB).
It contains 2 screens: parameters and control .

8.3.14.1. Parameters
This UI contains the fields to configure the principal behaviour of the function.

Init parameter
The billing period is the period of time between 2 successive maximum demand reset. At the time of reset,
the current values are stored in historical sets (up to 18).
The historical sets are identified by a number (from 0 to 99). The number of the next EOB after
configuration is programmable (0 to 99), then the subsequent EOB identification numbers will be
incremented at each reset.

Timeout control
Different sources of End Of Billing are possible and it is necessary to define which are authorised, and
which are disabled (by activating the "Function activated" field):

By communication
The source of EOB can be an "action command" sent using the COSEM protocol by Dino+ or
a similar software on a communication channel: COM port 1 (utility port), and/or COM port 2
(customer port), optical port. This command can be sent either locally, or remotely;

By push button
The source can be the "reset" button on the front plate.

147

jchauvin jj/12/13

It might be useful to authorise this mode, to manually trigger a reset at the time of meter
installation or commissioning.

From control input

If one (or 2 if change-over) control input is assigned to the EOB function, the activation still
needs to be authorised here.

By RTC (real time clock)

EOB can be programmed to occur at generic (repetitive) dates (for example every 1 st of each
month at 00h00), or at fixed dates, or according to a constant period.
EOB can alternatively be programmed to occur regularly after a specified number of hours of
use.
Details in the next tag ("controls").

A "Timeout" or "Lockout time", expressed in minutes (from 0 to 65535 minutes - more than 45 days) can be
activated following an EOB from each source. This timeout can be applied to any enabled source of EOB, and
will disallow a subsequent EOB from that source for a period of time equal to the timeout, after the initial EOB.
The non allowance can take different forms:

Total lock
Re-triggers a new "lockout time" for the category. Any EOB command from this category
during the lockout time is discarded.

Partial lock
Same as above, but the lock is cancelled after a 3-phase power failure on the meter.

Cancel
Cancels the "lockout time" of a category, if active. Otherwise, no action.

No action
No action on the "lockout time" of a category.

148

jchauvin jj/12/13

8.3.14.2. EOB Control

This UI controls the EOB function, when the source is RTC (real time clock).
A main switch allows to select either programmed or periodic mode (those modes are exclusive). Depending on
this switch the UI has different appearances.

Programmed EOB:
Used to trigger EOB at programmed dates: either repetitive (generic), or fixed (specific).
In each case, a list of up to 24 dates/times can be defined. A mix of both methods is allowed.

Special dates, which will be executed only once, can be entered into the field Specific EOB. The desired
date and time need to be selected in he fields Date and Hour and the Add feature needs to be selected.
The dates must be entered in chronological order !
Up to 24 specific EOB can be configured.
Generic dates, which describe a sort of formula for regular EOB can be entered in the field Generic EOB.
Only one definition is allowed.
To clear this field, the feature Delete needs to be activated.
In the fields Weekday, Day, Month, Year, Hour the desired information needs to be entered:
Weekday: Either a certain day (Monday .. Sunday) or a wildcard (*) can be selected.
Day: A certain day of the month (1..31) or back from the end of the month (0=last day of the month, -1=day
before last day ) or a wildcard can be selected.
Month: A certain month (January .. December) or a wildcard can be selected.
Year: A year can be defined by its year number, or a wildcard can be selected.

149

jchauvin jj/12/13

Hour: A fixed hour for the EOB needs to be selected.

This new date can be added by selecting the Add feature.
Example: weekday=*, day=1; month=*, year=*, hour= 00:00 will perform an EOB on the first day of each month
at 00:00 in the morning.

Periodical EOB
Used to trigger an EOB periodically, after a programmable number of hours of operation (from 1hour to 6
months).
The periodical EOB management is inhibited if "programmed" (instead of "periodical") is selected.

The value is entered as hours, the value for days is automatically displayed for information.

8.3.15.

Display

This UI allows the configuration of the control parameters for the LCD display function. It contains 2 screens :
Parameters and Display and readout table

8.3.15.1. Parameters
This UI contains all control parameters for the display function.

150

jchauvin jj/12/13

Leading Zeros
On the LCD, data information are presented on up to 9 digits, including up to 3 decimal digits. If the choice
is selected (tick), all 9 digits will be used, filled with 0 for the leading digits.
If not ticked, only significant digits will be displayed.
EOB confirmation
This information is only relevant if it is intended to activate EOB through the reset button (sealable push
button just below the display button). In this case, by activating the choice, it will be necessary to depress
the reset button 2 times before an actual EOB takes place: the first time a (configurable) warning message
will be displayed, like for example "EOB OK ?", then only if the reset button is depressed without delay a
second time, the actual EOB is performed.
It is recommended to use this feature, to avoid unwanted EOB, while the operator is trying to switch
between the "normal" display mode and the "alternate" display modes.
EOB confirmation string
The warning message, linked to the previously explained function is entered here, as a string of characters
(of up to 8 characters).
Separators display
Data information are identified by up to 10 characters, below the data field itself. Those 10 characters are
split into 6 groups: first group with 1 character, second with 2, then 2, then 2, then 1, then 2. With this
organisation, it is possible to use the identifiers defined by the OBIS standard. One is then allowed to use to
a separator (a dot) on the LCD to distinguish the groups between them, by clicking on the proposed tick box.
The identifiers in the 5 first groups can be the OBIS codes (by default - see next UI), or can be configured
by the user at his own choice. The last group is used identify historical data from each other on the LCD.
Timeout for ALT mode
The activation of the scrolling push button and the reset push button can activate different display modes:
from the "normal mode", active by default, one can switch to the "alternate long mode", by pushing on the
scrolling button while in LCD test, or to the "alternate short mode", by pushing on the reset button while in
LCD test. Different parameters can be displayed in the different lists, and the access to the "alternate short
mode" is restricted to authorised users, as it requires a push on the reset button, which is normally sealed
(only one push will not trigger an EOB).
Once in an "alternate mode", the LCD will remain in this mode for a period of time, before it automatically
returns to the normal auto-scrolling mode. This period of time is the "timeout for ALT mode" which can be
set in minutes from 1 to 60.

151

jchauvin jj/12/13

Timeout display test

While in "normal mode", a depression on the scrolling button will trigger an LCD test were all segments of
the LCD are on. The LCD will remain in this mode for a period of time, before it automatically returns to the
normal auto-scrolling mode. This period of time is the "timeout display test" which can be set in seconds
from 1 to 60.

Timeout for set mode

While in one of "alternate modes", and if displaying a parameter that can be set by push buttons (only the
date and the time in GenIEC1), a depression on the "reset" button will trigger the "set mode" where it is
possible to modify the value of those parameters.
The procedure is the following: the programming is performed digit by digit with the display push button (the
digit to be modified will blink), and move to the next digit with the reset button. When all digits are set, press
the reset button twice to activate the new values.
The LCD will remain in this mode for a period of time, before it automatically returns to the normal autoscrolling mode. This period of time is the "timeout for test mode" which can be set in seconds from 2 to 10.

Display on timeout
The LCD "normal mode" is active by default. All available parameters are auto-scrolling with a preprogrammed timeout between them.
The "display on timeout" is the value in seconds, from 1 to 10, during which the parameter is on the LCD.

Display off time out

The LCD "normal mode" is active by default. All available parameters are auto-scrolling with a preprogrammed timeout between them.
The "display off timeout" is the value in seconds, from 0 to 10, during which the LCD data fields remain
blank between two consecutive parameters .

Number of historical sets displayed in normal mode

In order to bill the customer for his consumption, a copy of the metering register information is performed at
time intervals called billing periods. Those historical data are stored in a circular buffer of 18 sets.
On the LCD, it is possible to view the current value of the parameters, and also the historical values. So it is
necessary to define how many historical values will be displayed, from 0 to 18.

Number of historical sets displayed in alternate modes

Same as above, respectively for the alternate long (ALT mode 2) and alternate short (ALT mode 1) modes.

End of list activated

The display list (see next UI), can contain up to 100 different parameters or data to display. If OBIS codes
are used for identification, it might be tricky to identify when the display sequence is actually completed
while scrolling in one of the alternate list.
An "End of list" message, of up to 8 characters, can be displayed when the list is completed, in order to
inform the user. This is activated by ticking the choice.
It must be noted that when an alternate list is completed, the displays returns to the "normal mode", if the
scrolling button is not further depressed.
End of list string
The end of list message, linked to the previously explained function is entered here, as a string of
characters (of up to 8 characters).
Time format
For of the time information on LCD: either 24h or am/pm.
Date format
Either dd:mm;yy, or mm:dd:yy, or yy:mm:dd.
Authorized EOB
This choice is only relevant if EOB activation by the reset button is allowed.
In this case, it allows to perform an EOB even while an "alternate" display list is active. If not selected, the
EOB will only be accepted while in the "normal" mode..

8.3.15.2. Display and Read-out table

This UI configures the display sequences (normal and alternate modes), and the data included in the IEC 61107
mode C optical readout.
A list of up to 100 parameters can be defined, sorted by order of appearance. For each parameter, one will
enter:

152

jchauvin jj/12/13

the identification code (the OBIS code is proposed by default, but can be replaced);

the scaler (1, 103, 106, 109);

the number of decimals (from 1 to 4);

the list in which the parameter or data is included (normal" list, "alternate long" or "alternate
short" list, optical readout list);

whether the parameter can be changed by push buttons (this field is only supported where
the meter version has the feature implemented. It is always available for date and time).

The UI allows to move parameters up or down, to insert above or below the current selection, to edit (modify),
to delete one or all parameters.
Each time an entry is defined or edited, it uses a definition UI :

153

jchauvin jj/12/13

The scaler and number of decimals are taken from the definitions screens of the concerned quantities.
When scaler and decimals are senseless (e.g. date) the fields are shaded.
The settable indicator is shaded where it is not possible to set.
When the identification code needs to be modified, the whole field entry shall be selected by clicking into the
field (allow direct over-write).
The following rules apply to the OBIS codes (identification code) - which are proposed by default:

group 1 (1 digit) is showing the Fluid (0 for general data, 1 for electricity data.)

group 2 (2 digits) is the channel number:

1 for internal metrology
2 to 5 for external inputs
6 to 9 for summation

group 3 (2 digits) specifies the quantity id, depending on definition of energy or demand channel, of
energy or demand rates, of external and summation. The quantity type defined for energy and demand
channel are moved in this digit. To distinguish channels with same quantities, this digit contains a value
from 77 to 85 (second channel with 77, third channel with 78,)

group 4 (2 digits) specifies the type of data (max demand, cumulative,)

group 5 (1 digit) specifies the rate for demand or energy rates.

Group 6 (2 digits) will identify the historical set source, as needed.

Note on OBIS code automatic generation

OBIS codes are generated automatically, taking into account the existing channel and rate definition (energy
and demand) at the moment of creation. Any subsequent change in the channel and rate definition will NOT be
cross-checked with the created OBIS codes which will remain unchanged and might then in some instance be
non coherent. The user need to be aware of this and update the OBIS codes after channels and rates are
definitively defined.

154

jchauvin jj/12/13

(The default value can always be re-constructed, if the label is re-assigned. This will reset the value in the
identification Code, but no other setting).

155

jchauvin jj/12/13

8.3.16.

Monitoring

This UI is used to configure the thresholds used for voltage quality, excess demand and battery operation
monitoring.
The UI contains 2 screens : Voltage monitoring , Battery monitoring.

8.3.16.1. Voltage Monitoring

This UI configures the thresholds for over/under voltage detection, network survey parameters, and detection of
voltage related tamper events.

Voltage Quality
For each phase, the meter detects voltage sags, voltage swells, and voltage cuts. Those events are based
on the comparison between the current value of the RMS voltage and a threshold. Two different thresholds
are used (High value and Low value, in volt with one decimal) to avoid multiple events in case the voltage
is floating closely around the threshold level (Hysteresis).
A calculation and a comparison with the thresholds of each phase voltage is performed every 40 ms (2
complete periods at 50 Hz), which allows to detect 100% of events with a duration larger than 80 ms.
If Voltage Quality is included in the Resource level of the meter, those events will be memorised: for sags,
swells, and cuts, per phase:

The total number of events;

The cumulated duration of the events;

The event with the longest duration in the billing period, with time stamp;

The event with the smallest detected duration in the billing period, with time stamp;

The last 10 events, with time stamp, duration, magnitude, phase.

If Voltage Quality is disabled, the voltage quality events (per phase defects (cut, sag, swell), are not
stored neither in the logbook, nor in the histories.

156

jchauvin jj/12/13

However, in case no auxiliary power supply is used:

"Power failure" (PwrFail) events (3-phase cuts longer than 1s) are still recorded, even if the VQ is
disabled.

The AcFail (detection of a 3-phase cut), PwrFail (3-phase cut longer than 1s), and PwrUp (meter
operational after a voltage return) entries in the logbook are still enabled

Any desired voltage can be entered into the fields of the different thresholds. If the low voltage is
defined higher than the high voltage, the entry is refused.
Activating the Default Values button will calculate proposed values based on the nominal voltage
defined in the Metrology Connection screen:
Cut threshold

High = 55%(Unom)

Low = 45%(Unom)

Sag threshold

High = 85%(Unom)

Low = 80%(Unom)

Swell threshold

High = 120%(Unom)

Low = 115%(Unom)

Network survey parameters

Some parameters can be monitored by the meter, in order to register an event, and eventually taking an
appropriate action when one of those parameters go out of limit.
Zero sequence voltage
The voltage of the neutral (normally zero) is calculated - for the 4-wire meters - (centre of
the phase voltages), and if higher than a pre-set threshold (expressed in volt, from 0 to
65535, with one decimal), an event will be detected.
Zero sequence current
The current in the neutral (normally zero) is calculated - for the 4-wire meters (sum of the
phase currents), and if higher than a pre-set threshold (expressed in Ampere, from 0 to
65535, with two decimals), an event will be detected.
Threshold for no consumption
The meter calculates the number of days without detected energy consumption, either from
internal measurement, or from external pulse inputs. An event is registered if this number
comes above a threshold (expressed in days, from 0 to 65535).

Power failure
Similarly to voltage events per phase (cuts, sags and swells), the meter can register the 3-phase power
failures, ie. when all phase voltages (and the auxiliary power supply if relevant), are below the "phase cut
detection level".
Power failure events are classified either as "short" power failures, or "long" power failures, depending on
their duration, compared to a threshold, expressed in seconds, from 0 to 255.

157

jchauvin jj/12/13

8.3.16.2. Battery Monitoring

This UI contains the parameters used for configuration of the battery functional monitoring.

Battery threshold parameters

A super-capacitor on the power supply board, and an optional Lithium battery (accessible for replacement
on the front plate), provide a continuity of use of the RTC. Those parameters are used to detect a "battery
error" situation. Once a battery error is detected, it is necessary to reprogram the "battery end of life date" to
erase it.

158

jchauvin jj/12/13

8.3.17.

Logging / Alarms

This UI allows to configure the behaviour of the meter for Logging and Alarm functionality (LCD icons and
general alarm icon).
The UI contains 2 screens : Logbook Control and Alarm Control

8.3.17.1. Logbook Control

This UI allows to configure which events shall be logged in the Logbook.

159

jchauvin jj/12/13

8.3.17.2. Alarm Control

This UI allows to configure, which alarm behaviour shall be initiated on the occurrence of an event.

160

jchauvin jj/12/13

8.3.18.

Communication

This UI allows to configure the different communication channels of the meter.

It contains up to 5 screens : Optical Port , Utility Port , Customer Port , Modem Parameters and
Modem Setup .
8.3.18.1. Optical Port IEC1107
This UI allows to configure the parameters, which control the behaviour of the optical port of the meter.

Device Address is used with the IEC 1107 standard readout. The meter will respond to a correct address, or an
opening without address. The field may be empty, maximum 32 characters.
Default Mode indicates the standard which is used on the optical port.
Proposed Baudrate defines which communication speed the meter will propose in the opening sequence.
Possible baud rates are
300, 600, 1200, 2400, 4800, 9600, 19200(not recommended).
Response Time allows to configure the time delay between request and answer (see IEC 62056-21 for details).
Possible values:20ms and 200ms.
IEC1107 Data Parameters allow to configure the data format with regards to the delimiters between the
identification code fields:
EDIS Separators: the separators between code fields are set as defined by IEC 62056-61, Annex A1
(example: 1-1:1.8.0*13)
Separators are Dots: All separators are represented by dots (example: 1.1.1.8.0.13).
No separator: the identification code fields are sent without delimiters (example: 1118013).

161

jchauvin jj/12/13

Number of historical sets For the IEC Data readout mode the number of historical sets for energy and
demand can be specified, which are sent automatically with the data protocol.
Configuration Security allows to enable the internal configuration switch to be automatically engaged. If this is
activated, the reconfiguration of the meter even for protected parameters does not require to open the meter.

162

jchauvin jj/12/13

8.3.18.2. Utility Port

The Utility Port of the meter supports only DLMS/COSEM protocol. It has a priority rule with the optical port,
being disabled if communication on the optical port is started. This port also provides the modem setup
communication.
This UI is accessible, depending on the hardware resource of the meter. It allows to configure the parameters
which control the behaviour of the utility port of the meter.

The Communication Speed has to match the speed which is used by a direct connected communication
device, different to a standard modem. Possible values are: 300, 600, 1200, 2400, 4800, 9600 bauds.
The Transmit Window Size allows to improve the data transfer rate, provided that the communication link
does not imply transmission errors.
The range for this value is 1..7, 1 to be used on poor communication lines, 7 to be used on good ones.
The Inter Character Timeout is a value which allows to determine the end of a transmission frame. This
parameter allows to adapt the meter to possible character delays, coming from data compression, error
correction or data packaging applications, which are part of the communication channel.
The range for this value is 20 .. 1000 ms. For transparent connections a value of 30ms is good, for typical
modem connections a value of 100ms is good, for connection with internet modems a value of 150ms has
proven to be suitable.
The Inactivity Timeout allows to define when the meter will disconnect a communication link which has no
more data transfer.

163

jchauvin jj/12/13

8.3.18.3. Customer Port

The Customer Port of the meter supports only DLMS/COSEM protocol.
This UI is accessible, depending on the hardware resource of the meter. It allows to configure the parameters,
which control the behaviour of the customer port of the meter.

See previous paragraph (Utility Port) for parameter explanations, for both port shave the same behaviour.

164

jchauvin jj/12/13

8.3.18.4. Modem Parameters

This UI allows to configure the parameters, which control the behaviour of a modem, connected to the utility
port of the meter.

Talking Mode allows to specify the principal behaviour of the modem connection:
Line dedicated to the device indicates that the telephone line to the modem is available at any time.
Limited number of calls allowed will inhibit the modem operation after a certain number of
communication attempts, regardless if those where successful or not.
Limited number of successful calls allowed will inhibit the modem operation after a certain number
of communication attempts, if those where successful.
Direct Line specifies that the port is not connected to a modem and no modem initialisation
communication shall be performed (mandatory setting for RS485 or other bus connections).
Number of calls contains the threshold for the talking modes with limited number of calls.
Listening Window allows to inhibit the modem operation outside defined time periods. Those periods are
defined by start and end time and are valid every day. Up to 5 periods can be configured. If no period is
configured the modem is always enabled.
The enable/disable of the modem is done via the DTR signal line to the modem.

165

jchauvin jj/12/13

8.3.18.5. Modem Setup

This UI allows to configure the parameters, which control the initialisation and the communication with a
modem, connected to the utility port of the meter.

The Communication Speed configured here is independent from the speed defined for the port itself.
Available values are 300, 600, 1200, 2400, 4800, 9600, 19200(not recommended) bits per second. This speed
is used to synchronise an external modem, and if this responds, the port is fixed to this speed, until a
disconnection of the modem is recognised.
The Initialisation Dialog allows to configure the strings, which need to be sent to the modem when the
connection of a modem is tested and verified. The setting allows to configure a dialog, where a message
coming back from the modem can be analysed and the progress may depend on this. If no answer string is
configured for a line (indicated by NOT USED), the meter will wait for the OK string of the modem.
Unused fields of the initialisation dialog shall be set to AT.
If no modem was already recognised on the port, the meter will try every minute to send an AT to the modem. If
a OK string is coming back, the meter will send a ATE0V1 command and afterwards the 5 lines are configured
in the set-up. After each line the corresponding answer string or a OK is expected. If this full sequence is
performed the meter will have recognised a modem and will not try to re-initialise until the end of the next data
communication or a period of 8 hours.
The Modem Profile allows to configure the answer strings of modems which are not exactly according to
HAYES commands.

166

jchauvin jj/12/13

9. CONFIGURATION FOR SL7000 SMART C&I METER, TYPES SL762XXX

9.1.
9.2.

Overview

This chapter lists those configuration parameters which are specific for the meter types SL762xxx.
9.2.1.

Resource

To create a configuration for SL762xxx meters, the meter type in this screen needs to be selected as SL762.
9.2.2.

Load Profile

The parameter Clock modification threshold has a range of 0..15%.

The parameter Internal recording factor represents the factor used to calculate a second recording interval
based on the primary one, which is defined by the parameter Recording interval (T2 = k x T 1). The range is
between 1 to 60.
9.2.3.

Communication

This UI allows to configure the different communication channels of the meter.

It contains 3 screens : IEC 870 Parameters , Optical Port , and Direct Link .
9.2.3.1. IEC 870 Parameters
This UI allows to configure the special parameters used in the IEC 870-5-102 protocol implementation. All of
them must be configured according to the needs of the data collection system.

167

jchauvin jj/12/13

The data of IEC870 are:

Data Link Address : a numeric value in the range 0 .. 65535.
Application Address : a numeric value in the range 0 .. 65535.
Password : a numeric value in the range 0 .. 4294967295.
9.2.3.2. Optical Port
This UI allows to configure the parameters which control the behaviour of the optical port of the meter for the
DLMS/COSEM protocol.
The optical port of a SL762xxx meter does not support IEC62056-21 communication. It supports IEC 870-5-102
and DLMS/COSEM communication.
The parameter settings are similar than for other SL76xxxx meters

9.2.3.3. Direct Link

This UI allows to configure the parameters which control the behaviour of the electrical port of the meter for the
DLMS/COSEM protocol.
The electrical port of a SL762xxx meter supports IEC 870-5-102 and DLMS/COSEM communication.
The parameter settings are similar than for other SL76xxxx meters

168

jchauvin jj/12/13

10. READING OF DATA

The reading of data is controlled by a dialog, containing sets of data, which are read as a whole. The contents of
the windows is dependent on the meter type. The load profile information & available historical data are read
first to know the meter configuration.
The sets of data to read for SL7000 SMART C&I METER contain the following entries:

Total Energy registers

Energy Rate registers

Demand registers

Maximum demand registers

Historical data

Partial read of load profile

Date and Time, Meter ID

Log book

Instantaneous Data

Network history

Meter history

Voltage quality data

Tampering data

Meter status

169

jchauvin jj/12/13

It is possible to select several items from this list and the reading process will execute them consecutively.

10.1. Total Energy registers:

This function reads the object AllTotalEnergies from the connected device. (refer to the display section for
details)

10.2. Energy Rate registers:

This function reads the object AllEnergyRates from the connected device. (refer to the display section for
details)

10.3. Demand registers

This function reads the AllDemands (current & previous) , the ExcessDemand (10) included threshold,
Occurrences, magnitude, duration, the excess energy is calculated as excess energy = cumulated excess
demand * Integration period / 60.

10.4. Maximum demand registers

This function reads the 24 available Maximum demand profiles from the connected device. (refer to the
display section for details)

170

jchauvin jj/12/13

10.5. Historical data

The number of stored sets of End Of Billing data is displayed to the user . The user has to select the number of
historical data to read. In case of no stored set the read is not selectable.
The historical data include total energy registers, energy rates registers, maximum registers, excess demand,
power factor, frequency, rms values, temperature and instantaneous network values. (refer to the display
section for details)

10.6. Partial read of load profile

The start date and the last date of the load profile stored in the meter are displayed to the user . In case of no
stored set the read is not selectable.
This function reads the load profile data object from the connected device. It allows to define the amount of
data to be read :

(refer to the display section for details)

10.7.

Date and Time, Meter ID

This function reads the Clock object, the serial number object, the firmware Id parameters object, the
resource ID and the AllChecksums object from the management device. (refer to the display section for
details)

10.8. Log book

This function reads the Logbook object from the management device. This object store the last 500 dated
events from the meter (refer to the display section for details).

10.9. Instantaneous data

This function reads the InstantaneousPower object, the Instantaneous power factor object, the all RMS
values object, the neutral object, the phase angles object. (refer to the display section for details)

171

jchauvin jj/12/13

10.10. Network history

This function reads the AllRMSMaxValues object, the AllFrequencies object, the AllConsumptions object,
the AllTemperatures object, the PowerFactor object. (refer to the display section for details)

10.11. Meter history

This function reads the WatchdogSummary object, the CalibrationSummary object, the Programming
Summary object, the ConfigurationSummary object and the Successfull CommunicationSummary object.
(refer to the display section for details)

10.12. Voltage quality data

this function reads following objects: SwellElement, SwellSummary, SagElement, SagSummary,
CutElement, CutSummary, Power failure, Power failure summary. (refer to the display section for details)

10.13. Tampering data

This feature reads following objects: current reversal elements, current reversal summary, cover opening
element, cover opening summary, seasons elements, seasons summary, day profiles elements, day
profiles summary, index elements, index summary. (refer to the display section for details)

10.14. Meter status

This functions read the objects Energy status, Fatal Alarms and Non Fatal Alarms, Total meter operating
time, Battery use time. (refer to the display section for details)

172

jchauvin jj/12/13

11. DATA DISPLAY

For each entry in the (meter type dependent) reading tree a module is available which allows to display and to
print the data.
All available reading data can be selected in a dialog, which allows to select the meter, the reading date and the
reading contents.

Each data set is represented by a file containing the name of the data set and the time stamp of reading.
A single data set is selected for display by double clicking on it, or by selecting and activating the button Open.
On each level of this dialog a Open and a Close button is available.

173

jchauvin jj/12/13

11.1. Total energy registers

All the 52 Total Energy registers of the meter are displayed:

energy type,

identification code (by default OBIS code),

instantaneous values read in the registers at the moment of the communication, and their unit.
The date and time of reading, and the meter number are reminded on the top of the screen.

It is possible to print those data ("print"), and to export them to a spreadsheet (EXCEL) - ("table"). In this case,
the EXCEL file is "shared", which prevents the generation of graphics. In order to recover the graphics function,
the file can be unshared : click on "tools", "share workbook", Editing, unclick "allow changes by more than one
user at the same time", then "OK".

174

jchauvin jj/12/13

11.2. Energy Rate registers

.
All the configured Energy rate registers are displayed:

register type,

identification code (by default OBIS code),

instantaneous values read in the registers at the moment of the communication, and their unit.

Operating times for each register (cumulative register).

The date and time of reading, and the meter number are reminded on the top of the screen.
It is possible to print those data ("print"), and to export them to a spreadsheet (EXCEL) - ("table"). In this case,
the EXCEL file is "shared", which prevents the generation of graphics. In order to recover the graphics function,
the file can be unshared : click on "tools", "share workbook", Editing, unclick "allow changes by more than one
user at the same time", then "OK".

175

jchauvin jj/12/13

11.3. Demand registers

All current and previous values of the configured demand channel registers are presented:

register name

identification code (by default OBIS code),

register values and unit.

The date and time of reading, and the meter number are reminded on the top of the screen.
N.B. The "current" values are the values in the demand registers at the moment of reading ("rising values").
The "previous" values are recorded at the end of the previous integration period.

176

jchauvin jj/12/13

177

jchauvin jj/12/13

11.4. Maximum demand registers

For each configured Maximum demand register, the 5 highest values in the billing period are displayed,
together with their corresponding time stamp:

register type,

identification code (by default OBIS code),

the current 5 highest values of the billing period, values read in the registers at the moment of the
communication, and their unit.

The date and time of occurrence of each event.

The date and time of reading, and the meter number are reminded on the top of the screen.

178

jchauvin jj/12/13

11.5. Historical data

The dialog allows to display data registered at the previous "End Of Billing" (end of month if programmed so):

Total Energy registers at the end of the selected billing period,

Energy Rate registers at the end of the selected billing period,

Maximum demand registers at the end of the selected billing period,

Power factor (min, and average during the selected billing period),

Frequency (min, max during the selected billing period),

RMS values of the 3 voltages and 3 currents (max during the selected billing period),

Temperature (min, max during the selected billing period),

For each of those data sets sub-branches indicate the available data sets by the date of reset.

179

jchauvin jj/12/13

11.6. Partial read of load profile

A dialog allows to display load profiled data in tabular form. Each line contains the value of all channels,
recorded at the same time including a time stamp and, if available, event information (occurrence of a change
of date/time, and total power failure).
Each screen contains all available data from one day.
To switch between days, the Next and Previous Buttons are used.
Data can be exported to a spreadsheet (EXCEL), using the "Table" button. In this case, the EXCEL file is
"shared", which prevents the generation of graphics. In order to recover the graphics function, the file can be
unshared : click on "tools", "share workbook", Editing, unclick "allow changes by more than one user at the
same time", then "OK".

180

jchauvin jj/12/13

11.7. Date and Time / Meter ID

181

jchauvin jj/12/13

11.8.

The information from the real time clock of the meter and some general meter ID data are displayed.

182

jchauvin jj/12/13

11.9. Log book

The Logbook of the meter is displayed, containing all events, which were configured to be registered, with their
date and time of occurrence, and their order number.

183

jchauvin jj/12/13

11.10. Instantaneous data

Separate tables allow to display instantaneous data:

Instantaneous values of the powers (active powers, reactive powers, apparent powers),

Power factors (by phase and three-phase),

RMS voltages and currents

Zero sequence voltage and current

Phase angles (between current and voltage for each phase, and between the voltages).

184

jchauvin jj/12/13

11.11. Network history

Separate tables allow to display the maximum and minimum values (since commissioning) of different
parameters, with time stamp:

RMS voltages and currents,

Network Frequency,

Temperature (internal temperature of the meter),

Power factor,

And the number of days without consumption (internal and from the pulse inputs).

185

jchauvin jj/12/13

11.12. Meter history

This dialog shows the major events in the behaviour and communication of the meter, and the date/time of the
last:

number of watchdog events,

number of calibrations,

number of programming,

number of configurations,

number of successful communications.

186

jchauvin jj/12/13

11.13. Voltage quality data

Several dialogs display the stored history of voltage quality events, if the meter was configured to store them.
Voltage Quality events are detected if their minimum duration is 80 ms. Below 80 ms, they are ignored.
For the voltage swells, the voltage sags, and the phase cuts - for each phase :

minimum duration, with date and time of occurrence,

maximum duration, with date and time of occurrence,

total duration, and total number of occurrences.

Details on the 10 last events.

187

jchauvin jj/12/13

For the power failures (simultaneous phase cut on the 3 phases) :

minimum duration, with date and time of occurrence,

maximum duration, with date and time of occurrence,

total duration,

number of occurrences of small duration power failures,

number of occurrences of long duration power failures,

details on the 10 last power failures.

188

jchauvin jj/12/13

11.14. Tampering data

Several tables display the data, which are stored to track tampering events:

the last occurrences (with time stamp) - (up to 100) of current reversals from import to export, or the other
way), and the total number of reversals for each phase;

the last occurrences (with time stamp) - (up to 100) of cover opening detections, and the total number of
such events;

the last occurrences (with time stamp) - (up to 100) of season change (TOU) detections, and the total
number of such events;

the last occurrences (with time stamp) - (up to 100) of day profile change detections, and the total number
of such events;

the last occurrences (with time stamp) - (up to 100) of index change detections, and the total number of
such events;

189

jchauvin jj/12/13

11.15. Meter status

Two tables display the actual status of the meters behaviour and the list of recorded alarms.

190

jchauvin jj/12/13

12. ANNEXE : PERMISSION LIST FOR PREDIFINED VERSION

The permissions are the permissions maximum for each level. But these permissions also depend on
the customers (for the objects of configuration) and on the users (for the Full level). For example, at the Full
level, only the user administrator can import the File/import: user permission. In the same way, at the Full
level, with customer Utility field, the object " EOB/Control " of configuration is not accessible.

DINO+ LEVEL
NomFonction

Field

Download

Reading

Electricity Utility Laboratory

Electricity Utility Field

Electricity Reader

Gas Reader

Water Reader

End Customer

Engineer

Management

Electricity

Gas

Water

File/import: configuration

File/import: user permission

File/import: meter

File/export: configuration

File/export: user permission

File/export: meter

Client permission for write

Device permission for write

Menu features:

191

jchauvin jj/12/13

Configuration: Empty, New

Configuration: Open

Configuration: Save, Save As, Save as Default

Configuration: Delete

Configuration: Print

Reading: Open

Reading: Delete

Communication/Read: configuration

Communication/Read: reading

Communication/Write: configuration

Communication/Write: password

Communication/Write: logical address

Communication/Write: physical address

Communication/Write: clock

Communication: Action

Communication: Sequence

Tools/Meter Group : Add, Edit

Tools/Meter Group : Delete

Tools/Meter : Add, Edit

Tools/Meter : Delete

Tools: Meter initialisation

Tools: Setup

Tools: Database repair

HHU/Job : Add, Edit

HHU/Job : Delete

HHU/Export Job File

HHU/Import Results

Configuration items
Resources

192

jchauvin jj/12/13

Client Selection

Identification: Client ID

Identification: Program ID

Identification: Configuration ID

Metrology/Connection: Network

Metrology/Auxiliary Power

Metrology/Connection: Transformer ratio

Metrology/Secondary metrology: Energy Calculation

Metrology/Secondary metrology: Power Calculation

Auxiliary I/O/Control Lines:Control Input lines

Auxiliary I/O/Control Lines:Control Output lines

Auxiliary I/O/External Tariffication

Auxiliary I/O/Input Pulses: Input Pulse Parameters

Auxiliary I/O/Input Pulses: Input Pulse Weight

Auxiliary I/O/Output Pulses: Output Pulse Parameters

Auxiliary I/O/Output Pulses: Output Pulse Weight

Energy Calculation: Total Energy Parameters

Energy Calculation: Summation definition

Energy Calculation: Energy Rates Parameters

Demand Calculation: Parameters

Demand Calculation: Demand Rates Parameters

Demand Calculation/Excess Demand: Rate definition

Demand Calculation/Excess Demand: Thresholds

Load Profile: Parameters

Load Profile: Channel Parameters

RTC: Clock Setting Parameters

RTC: Synchronization Parameters

RTC: Clock Base

RTC: DST Parameters

TOU/Index Parameters: General Parameters

TOU/Index Parameters: Index Parameters

193

jchauvin jj/12/13

TOU:Future Calendar

TOU: Special Days

EOB/Parameters: Init Parameters

EOB/Parameters: Timeout Control

EOB/Control

Display: Parameters

Display: Display and Readout Table

Monitoring/Voltage Monitoring:Network Survey Parameters

Monitoring/Voltage Monitoring:Power Failure

Monitoring/Battery Monitoring: Battery Threshold Parameters

Monitoring/Battery
Parameters

Logging/Alarms: Logbook Control Parameters

Logging/Alarms: Alarm Control Parameters

Communication/Optical port: Device Address

Communication/Optical port: Proposed Baudrate

Communication/Optical port: Response Time

Communication/Optical port: IEC 1107 Data Parameters

Communication/Optical port: LaboratorySwitch

Communication/IEC870 Data Link Address

Communication/IEC870 Application Address

Communication/IEC870 Password

Communication/Utility port: Communication Speed

Communication/Utility port: Transmit Window size

Communication/Utility port: Inter Char. Time Out

Communication/Utility port: Inactivity Time Out

Communication/Customer port: Communication Speed

Communication/Customer port: Transmit Window size

Communication/Customer port: Inter Char. Time Out

Communication/Customer port: Inactivity Time Out

Communication/Modem Parameters: Talking Mode

Communication/Modem Parameters: Number of Calls

Monitoring/Voltage
Parameters

Monitoring:Voltage

Monitoring:

194

Battery

Threshold

End

of

Life

jchauvin jj/12/13

Communication/Modem Parameters: Listening Window

Communication/Modem Setup: Communication Speed

Communication/Modem Setup: Initialisation Dialog

Communication/Modem Setup: Modem Profile

13. ANNEXE : PERMISSION LIST FOR CONFIGURABLE VERSION

The permissions are the permissions maximum for each level. But these permissions also depend on
the customers (for the objects of configuration) and on the users (for the Full level). For example, at the Full
level, only the user administrator can import the File/import: user permission. In the same way, at the Full
level, with customer Utility field, the object " EOB/Control " of configuration is not accessible.
LEVEL
NomFonction

Laborato
ry

Field

Download

Reading

Electricity Utility Laboratory

Electricity Utility Field

Electricity Reader

Gas Reader

Water Reader

End Customer

Engineer

Management

Electricity

Gas

Water

File/import: configuration

File/import: user permission

Client permission for write

Device permission for write

Menu features:

195

jchauvin jj/12/13

File/import: meter

File/export: configuration

File/export: user permission

File/export: meter

Configuration: Empty, New

Configuration: Open

Configuration: Save, Save As, Save as Default

Configuration: Delete

Configuration: Print

Reading: Open

Reading: Delete

Communication/Read: configuration

Communication/Read: reading

Communication/Write: configuration

Communication/Write: password

Communication/Write: logical address

Communication/Write: physical address

Communication/Write: clock

Communication: Action

Communication: Sequence

Tools/Meter Group : Add, Edit

Tools/Meter Group : Delete

Tools/Meter : Add, Edit

Tools/Meter : Delete

Tools: Meter initialisation

Tools: Setup

Tools: Database repair

HHU/Job : Add, Edit

HHU/Job : Delete

196

jchauvin jj/12/13

HHU/Export Job File

HHU/Import Results

Resources

Client Selection

Identification: Client ID

Identification: Program ID

Identification: Configuration ID

Metrology/Connection: Network

Metrology/Auxiliary Power

Metrology/Connection: Transformer ratio

Metrology/Secondary metrology: Energy Calculation

Metrology/Secondary metrology: Power Calculation

Auxiliary I/O/Control Lines:Control Input lines

Auxiliary I/O/Control Lines:Control Output lines

Auxiliary I/O/External Tariffication

Auxiliary I/O/Input Pulses: Input Pulse Parameters

Auxiliary I/O/Input Pulses: Input Pulse Weight

Auxiliary I/O/Output Pulses: Output Pulse Parameters

Auxiliary I/O/Output Pulses: Output Pulse Weight

Energy Calculation: Total Energy Parameters

Energy Calculation: Summation definition

Energy Calculation: Energy Rates Parameters

Demand Calculation: Parameters

Demand Calculation: Demand Rates Parameters

Demand Calculation/Excess Demand: Rate definition

Demand Calculation/Excess Demand: Thresholds

Load Profile: Parameters

Load Profile: Channel Parameters

Configuration items

197

jchauvin jj/12/13

RTC: Clock Setting Parameters

RTC: Synchronization Parameters

RTC: Clock Base

RTC: DST Parameters

TOU/Index Parameters: General Parameters

TOU/Index Parameters: Index Parameters

TOU:Future Calendar

TOU: Special Days

EOB/Parameters: Init Parameters

EOB/Parameters: Timeout Control

EOB/Control

Display: Parameters

Display: Display and Readout Table

Monitoring/Voltage Monitoring:Network Survey Parameters

Monitoring/Voltage Monitoring:Power Failure

Monitoring/Battery Monitoring: Battery Threshold Parameters

Monitoring/Battery
Parameters

Logging/Alarms: Logbook Control Parameters

Logging/Alarms: Alarm Control Parameters

Communication/Optical port: Device Address

Communication/Optical port: Proposed Baudrate

Communication/Optical port: Response Time

Communication/Optical port: IEC 1107 Data Parameters

Communication/Optical port: LaboratorySwitch

Communication/IEC870 Data Link Address

Communication/IEC870 Application Address

Communication/IEC870 Password

Communication/Utility port: Communication Speed

Communication/Utility port: Transmit Window size

Communication/Utility port: Inter Char. Time Out

Monitoring/Voltage
Parameters

Monitoring:Voltage

Monitoring:

198

Battery

Threshold

End

of

Life

jchauvin jj/12/13

Communication/Utility port: Inactivity Time Out

Communication/Customer port: Communication Speed

Communication/Customer port: Transmit Window size

Communication/Customer port: Inter Char. Time Out

Communication/Customer port: Inactivity Time Out

Communication/Modem Parameters: Talking Mode

Communication/Modem Parameters: Number of Calls

Communication/Modem Parameters: Listening Window

Communication/Modem Setup: Communication Speed

Communication/Modem Setup: Initialisation Dialog

Communication/Modem Setup: Modem Profile

199

jchauvin jj/12/13

14. ANNEXE : CLIENT ACCESS TO OBJECTS

First level

Resources

Client
Identification

Metrology

Auxiliary I/O

Energy calculation

Demands

Load profiles
RTC

Time Of Use

End of Billing

Display
Monitoring

Logging and alarms

Communication

Objects

Meter type
I/O board (hardware option)
firmware release
resource level
client
Utility Id Comments (1 to 9)
Program Id Comment
Initialization Id Comment
meter connection (DC/CT)
Network (3w/4w, f, V)
Transformer ratio
Aggregate energy calculation mode
Apparent power calculation mode
Control input lines
Control output lines
External tariffication
Pulse inputs quantity and definition
Input Pulse weights
Pulse outputs quantity and definition
Output Pulse weights
Total energy scalers
Summation (scalers)
Summation definition
Energy channels definition
General parameters (int.period, )
Demand channels definition
Excess demand channel and rate
Excess demand thresholds
General parameters (int.period, )
Channels definition
Clock setting parameters
Clock base
DST parameters
Generic DST
Programmed DST
General parameters (act. mode, )
Index definition
Future calendar - season
Future calendar - day profile
Future calendar - week profile
Future calendar - name
Future calendar - due time
Future calendar - special days
Current calendar
Init parameters
Source and time-out
EOB (periodical or programmed dates)
Generic EOB dates
Specific EOB dates
Display parameters
Display table
Voltage thresholds
Network survey
Power failure
Battery thresholds
Battery end of life
Logbook record
Alarm control (LCD & output)
Optical port - device address
Optical port - proposed baud rate
Optical port - response time
Optical port - IEC1107 parameters
Utility port - baud rate

200

Stop *

Laboratory
Read Write

Potential accessibility with Dino+

Elec Field
Elec Reader
End customer
Read Write Read Write Read Write

jchauvin jj/12/13

Engineer
Read Write

15. ANNEXE : CLIENT ACCESS TO ACTIONS

First level

Actions

MDI
Clear errors
Management actions

MDI reset (EOB)

Clear non fatal errors
Reset meter
Stop measurement
Reset Load profiles
Reset passwords
Start measurement
Clear fatal errors
Tests 1 to 10
Stop tests

Test actions
Clock programming
Write "Lab" password
Write "Field" password
Write "Reader" password
Write "End Cust."password
Write "Eng." password
Write physical address

201

Lab. sw.
pressed

Stop *

Laboratory

Potential accessibility with Dino+

Elec Field
Elec Reader End customer

Engineer

jchauvin jj/12/13

First level

Resources

Client
Identification

Metrology

Auxiliary I/O

Energy calculation

Demands

Load profiles
RTC

Time Of Use

End of Billing

Display
Monitoring

Logging and alarms

Communication

Objects

Meter type
I/O board (hardware option)
firmware release
resource level
client
Utility Id Comments (1 to 9)
Program Id Comment
Initialization Id Comment
meter connection (DC/CT)
Network (3w/4w, f, V)
Transformer ratio
Aggregate energy calculation mode
Apparent power calculation mode
Control input lines
Control output lines
External tariffication
Pulse inputs quantity and definition
Input Pulse weights
Pulse outputs quantity and definition
Output Pulse weights
Total energy scalers
Summation (scalers)
Summation definition
Energy channels definition
General parameters (int.period, )
Demand channels definition
Excess demand channel and rate
Excess demand thresholds
General parameters (int.period, )
Channels definition
Clock setting parameters
Clock base
DST parameters
Generic DST
Programmed DST
General parameters (act. mode, )
Index definition
Future calendar - season
Future calendar - day profile
Future calendar - week profile
Future calendar - name
Future calendar - due time
Future calendar - special days
Current calendar
Init parameters
Source and time-out
EOB (periodical or programmed dates)
Generic EOB dates
Specific EOB dates
Display parameters
Display table
Voltage thresholds
Network survey
Power failure
Battery thresholds
Battery end of life
Logbook record
Alarm control (LCD & output)
Optical port - device address
Optical port - proposed baud rate
Optical port - response time
Optical port - IEC1107 parameters
Utility port - baud rate

202

Stop *

Laboratory
Read Write

Potential accessibility with Dino+

Elec Field
Elec Reader
End customer
Read Write Read Write Read Write

jchauvin jj/12/13

Engineer
Read Write

16. ANNEXURE : CLIENT ACCESS TO OBJECTS

203

jchauvin jj/12/13

17. ANNEXE : CLIENT ACCESS TO OTHER FUNCTIONS

First Level

Lab
stop
swt.
pressed

Potential accessibilty with Dino+

Laboratory

Elec Field

Client permission (Write)

Electricity Utility Laboratory
Electricity Utility Field
Electricity Reader
Gas Reader
Water reader
End Customer
Engineer

Logical device permission (write)

Management
Electricity
Gas
Water

Menu features
File/Import : Configuration
File/Import : User permissions
File/Import : meter

File/Export : Configuration
File/Export : User permissions
File/Export : meter

Configuration : New, Empty

Configuration : Open
Configuration : Save, Save As, Save As Default
Configuration : Delete
Configuration : Print

Data : Open
Data : Delete

204

jchauvin jj/12/13

Elec reader

End custo.

Engineer

Communication/Read : Configuration
Communication/Read : Data

Communication/Write : Configuration
Communication/Write : Password
Communication/Write : Logical Addresses
Communication/Write : Physical Address

Communication : Clock
Communication : Action
Communication : Configuration Sequence

Tools/Meter Group : Add, Edit

Tools/Meter Group : Delete
Tools/Meter : Add, Edit
Tools/Meter : Delete
Tools : Meter Initialization
Tools : Setup
Tools : Database repair

HHU/Job : Add, Edit

HHU/Job : Delete
HHU/Export Job File
HHU/Import Results

205

jchauvin jj/12/13

18. ANNEXE : DISPLAY ON LCD OF ERROR CODE

DATA

Functions which detects the

alarm

Errors
(9 digits : 9 nibbles)

Onthe first line :Nonfatal alarms

current unbalance betweenphases (1-2)
current unbalance betweenphases (2-3)

Diagnostic & Tamper

Diagnostic & Tamper

nibble 0: Bit 0 1, 3, 5, 7
nibble 0: Bit 1 2, 3, 6, 7

current unbalance betweenphases (1-3)

not used

Diagnostic & Tamper

-

nibble 0: Bit 2 4, 5, 6, 7
-

voltage isolation (phase 1)

voltage isolation (phase 2)

Diagnostic & Tamper

Diagnostic & Tamper

nibble 1: Bit 0 1, 3, 5, 7, 9, B, D, F
nibble 1: Bit 1 2, 3, 6, 7, A, B, E, F

voltage isolation (phase 3)

cover opening

Diagnostic & Tamper

Diagnostic & Tamper

nibble 1: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 1: Bit 3 8, 9, A, B, C, D, E, F

External alarm
Configuration incoherence

Control input
Anyfunction

nibble 2: Bit 0 1, 3, 5, 7
nibble 2: Bit 1 2, 3, 6, 7

Non volatile memory

not used

Memorymanager
-

nibble 2: Bit 2 4, 5, 6, 7
-

No internal consumption

Diagnostic & Tamper

nibble 3: Bit 0 1, 3, 5, 7, 9, B, D, F

No external consumption

Diagnostic & Tamper

nibble 3: Bit 1 2, 3, 6, 7, A, B, E, F

Zero sequence U
Zero sequence I

Diagnostic & Tamper

Diagnostic & Tamper

nibble 3: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 3: Bit 3 8, 9, A, B, C, D, E, F

voltage cut (phase 3)

Qualimetry

nibble 4: Bit 0 1, 3, 5, 7, 9, B, D, F

voltage sag (phase 3)

Qualimetry

nibble 4: Bit 1 2, 3, 6, 7, A, B, E, F

voltage swell (phase 3)

current reversal (phase 2)

Qualimetry
Diagnostic & Tamper

nibble 4: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 4: Bit 3 8, 9, A, B, C, D, E, F

voltage cut (phase 2)

voltage sag (phase 2)

Qualimetry
Qualimetry

nibble 5: Bit 0 1, 3, 5, 7, 9, B, D, F
nibble 5: Bit 1 2, 3, 6, 7, A, B, E, F

voltage swell (phase 2)

current reversal (phase 2)

Qualimetry
Diagnostic & Tamper

nibble 5: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 5: Bit 3 8, 9, A, B, C, D, E, F

voltage cut (phase 1)

voltage sag (phase 1)

Qualimetry
Qualimetry

nibble 6: Bit 0 1, 3, 5, 7, 9, B, D, F
nibble 6: Bit 1 2, 3, 6, 7, A, B, E, F

voltage swell (phase 1)

current reversal (phase 1)

Qualimetry
Diagnostic & Tamper

nibble 6: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 6: Bit 3 8, 9, A, B, C, D, E, F

communications error
programming incoherence

Communications
Communications

nibble 7: Bit 0 1, 3, 5, 7, 9, B, D, F
nibble 7: Bit 1 2, 3, 6, 7, A, B, E, F

clockloss
external clockincoherence

Event Manager
RTC

nibble 7: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 7: Bit 3 8, 9, A, B, C, D, E, F

watchdog activity.
batteryalarm

Diagnostic & Tamper

Diagnostic & Tamper

nibble 8: Bit 0 1, 3, 5, 7, 9, B, D, F
nibble 8: Bit 1 2, 3, 6, 7, A, B, E, F

neutral loss
temperature

Diagnostic & Tamper

Diagnostic & Tamper

nibble 8: Bit 2 4, 5, 6, 7, C, D, E, F
nibble 8: Bit 3 8, 9, A, B, C, D, E, F

Onthe secondline (fatal error)

RAM error.
programmemoryerror.
checksumerror ona memory area.
Several external clockincoherence

Diagnostic & Tamper

Diagnostic & Tamper
Diagnostic & Tamper
RTC

nibble 0: Bit 0
nibble 0: Bit 1
nibble 0: Bit 2
nibble 0: Bit 3

206

1, 3, 5, 7, 9, B, D, F
2, 3, 6, 7, A, B, E, F
4, 5, 6, 7, C, D, E, F
8, 9, A, B, C, D, E, F

jchauvin jj/12/13