ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
Description of the Engineering Data Exchange Excel Template
Engineering Data Exchange Template for BACnet
Systems
“Description of the EDE Data Fields“ Version of
th
Layout: 2 Release Date: February, 9 2004
Issue: 09-Feb-2004
© Copyright 2004, BACnet Interest Group Europe e.V.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
1/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
SPÉCIFICATIONS CHUV
3
PURPOSE
4
GENERAL FORMAT
4
FORMAT OF THE SHEET “EDE“
4
THE DATA POINT COLUMNS
5
KEYNAME
DEVICE-OBJECT-INSTANCE
OBJECT-TYPE
OBJECT-INSTANCE
DESCRIPTION
PRESENT-VALUE-DEFAULT
MIN-PRESENT-VALUE
MAX-PRESENT-VALUE
COMMANDABLE
SUPPORTS COV
HI-LIMIT
LOW-LIMIT
STATE TEXT REFERENCE
UNIT-CODE
VENDOR-SPECIFIC-ADDRESS
5
5
6
6
6
6
6
6
7
7
7
7
7
7
8
FORMAT OF THE SHEET “STATE-TEXTS“
8
FORMAT OF THE SHEET “UNIT-TEXTS“
8
FORMAT OF THE SHEET “OBJECT-TYPES“
8
ATTENTION!
9
TEXTES D'ÉTAT STANDARD
10
TEXTES UNITÉS STANDARD
12
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
2/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
MODIFICATIONS AU TEXTE DE LA SPÉCIFICATION EDE BIG DE MANIÈRE À CORRESPONDRE AUX
IMPÉRATIFS DU CHUV
1) Les champs de renseignement suivants marqués pour certains comme optionnels dans la
spécification sont obligatoires dans le document EDE CHUV (voir exemple sous 600-7).
•
•
•
•
•
•
•
•
•
•
•
•
description
present-value-default
min-present-value
max-present-value
commandable
supports COV
hi-limit
low-limit
state text reference
unit-code
Fonction ISO 7-1
Fonction ISO 7-2
2) Le champ "description" doit pouvoir comprendre 128 caractères au minimum tant dans la feuille
EDE que pour l’ensemble des objets BACnet qui y sont référencés.
3) Les textes et unités standard sont donnés à titre indicatif, et correspondent à la spécification EDE
référencée, en langue anglaise. Toutefois, les textes mis en place dans le cadre des projets du
CHUV seront en langue française, ils seront choisis, dans la mesure où ils existent, dans les
textes standards indiqués dans la présente annexe. A défaut, des textes spécifiques au besoin
du projet seront soumis pour validation à l’Atelier GTB joint aux soumis.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
3/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
PURPOSE
In a multi vendor system engineering data need to be exchanged between the interacting parties. From
the native BACnet point of view it is not really required to have data point lists, because data of object
properties from any device can be discovered online using the appropriate BACnet services. But
depending on the BACnet functionality supported by server device or client device, it may be necessary
to have this information in form of an offline description. This also is required, if the client needs to be
set-up before the server device is operational on the network.
The Engineering Data Exchange (EDE) template shall help to exchange engineering data, such as data
point types, data point addresses and special data point presentation information in a standardized
form.
When integrating multi-vendor systems using the BACnet protocol, the actual protocol is described
in the BACnet Standard. The extent of implementation is described in the PICS (Protocol Implementation
Conformance Statement) of a BACnet device.
BACnet data point objects have various object properties that can help in setting-up the engineering data
which may be required for the configuration of a Supervisory Station or an Automation Station. However,
many of these object properties are not mandatory on either the client side or on the server side.
Also many clients (Supervisory Stations or Automation Stations) require ‘offline engineering’ of their
databases.
The Engineering Data Exchange template shall provide a common means to describe the objects of a
data point server in the form of a Microsoft ® Excel spreadsheet. The actual storage format of the
spreadsheet and the different Excel versions can be negotiated between the multiple vendors for the
project.
GENERAL FORMAT
The actual Excel workspace consists of four different sheets :
1. The sheet “EDE“ contains project information and also the list of data points chosen for
interoperation.
2. The sheet “State-Texts“ contains information about the state texts being used for binary objects
and multi state objects. The sheet “EDE“ refers or “points“ to entries in the sheet “State Texts“
3. The sheet “Unit-Texts“ contains a list of supported BACnetEngineeringUnits being used for
analog objects. The sheet “EDE“ refers or “points“ to entries in the sheet “Unit-Texts“. Proprietary
units can be added as required, according to the rules defined in the BACnet Standard.
4. The sheet “Object-Types” contains a list of supported BACnet Object Types. The sheet “EDE“
refers or “points“ to entries in the sheet “Object-Types“. Proprietary object-types can be added
as required, according to the rules defined in the BACnet Standard.
Once the assignment between the keyname, object-name, object-type and object-instance had been
communicated to the integration partner, this assignment shall not be changed. New objects should be
added with instance numbers that were not yet used for that device (added at the end). Especially the
assignment should not change between subsequent versions of the reference file.
The preferred Excel format is the Comma Separated Value (CSV) format. As this format does not
support multiple sheets in parallel, the CSV-converted form of each sheet leads to a separate file which’s
name has a common part identifying the project and a specific part relating to the specific table (e.g.
EDE2example_EDE.csv or EDE2example_Units.csv).
It is part of the negotiation, which separators are being used and which country settings are to be used.
All vendors should use the same settings for their common project.
Comment lines may be included in the sheets. A comment line starts with the ANSI character ‘#’.
Additional optional columns may be added if necessary.
Format Of The Sheet “EDE“
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
4/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
THE HEADER
Project_Name
This field shall contain the project name and the location of the project.
Version_Of_Reference_File
This field shall contain the version of the reference file. This actually means the version of the data point
list.
Time_Stamp_Of_Last_Change
This is the date and time of the last change of this document.
Author_Of_Last_Change
The full name of the author who did the last change to the document.
Version_Of_Layout
This is the version of the sheet layout that is used. The version of the layout should not change during a
project. The description you are just reading is valid for layout version 2.
Limited_Resources
This is an optional comment field that should list all limitations such as: Maximum string length for
keynames, descriptions and texts.
Restrictions on address ranges (device object instances etc)
Special timing requirements
THE DATA POINT COLUMNS
keyname
The keyname is the system wide unique name of the data object, as it will be displayed on the client’s
user interface.
In best case the keyname is identical to the object-name, but in some cases these two
names also may be different. Differing names may be necessary for example, if an operator wants to
see a special structured keyname that is longer than the supported length of the object-name, or, in
cases where there are many devices with identical object-names on the same network (e.g. AI1, BO1).
This field is mandatory.
device-object-instance
This is the instance-number of the device, in which the data object described in that table-entry is
located. BACnet device object instances must be unique within all connected BACnet networks. If there
is a multi vendor system with many vendors, a range of device instances should be assigned to each of
them by the responsible system integrator.
The device object instance is represented as a decimal value. It is the lower 22 bits (bit 0 through 21) of
the BACnet Device Object Identifier
This field is mandatory. object-name
This is the name of the described object and identical to the property Object_Name. Object names have
to be unique within a BACnet device. The object-name of the device-object itself has even to be unique
within the entire BACnet internetwork.
This field is mandatory.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
5/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
object-type
This field contains a decimal value, that represents the BACnetObjectType code, as it is used as value in
every object’s property Object_Type.
In sheet “Object-Types” the text descriptors for all supported
object-types can be found as readable text.
This information is also content of the BACnet property
Object_Identifier (most significant 10 bits i.e. bit 22 through 31).
As the EDE document is aimed to describe especially BACnet objects useful for dataexchange between
BACnet partners, objecttypes like “program“ may be omitted in the ”EDE”-sheet. On the other side
should proprietary objects be included, if they are used for datainterchange with other parties.
This field is mandatory.
object-instance
This field contains the instance-number of the object as a decimal value. It covers the lower 22 bits (bit 0
through 21) of the BACnet property Object_Identifier. Within a BACnet-device, different objects of the
same object-type are distinguished by their instance numbers. The object instance therefore has to be
unique for each possible object-type in a specific device.
This field is mandatory.
description
This information text should deliver more detailed description of the data point and its function.
It is often
required for offline engineering work.
The BACnet property Description is optional for a BACnet device,
but should be identical to this entry, if present. Usually this text comes from the points list ( EN ISO
16484-3) and is given by the planning papers.
This field is optional.
present-value-default
The default value for the present value as from the BACnet property Relinquish_Default.
This field is optional.
min-present-value
The minimum value for the BACnet property Present_Value.
For matters of data consistency this field
shall only be present if the object does not support the BACnet property Min_Pres_Value to be written or
to be changed.
The field should always be filled in, if the server doesn’t support that property at all, to
give an advice for avoiding BACnet write accesses with values lower than this restriction.
This field is optional.
max-present-value
The maximum value for the “Present_Value” property.
For matters of data consistency this field shall
only be present if the object does not support the BACnet property Max_Pres_Value to be written or to
be changed.
The field should always be filled in, if the server doesn’t support that property at all, to give
an advice for avoiding BACnet write accesses with values higher than this restriction.
This field is optional.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
6/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
commandable
This optional field indicates, whether the present value can be written or not. The letter ‘Y’ means
commandable the letter ‘N’ means not commandable.
If the field is empty the client will assume that the
value may be read and written. If write access is not permitted, the server will respond with the
appropriate error “WriteAccessDenied“.
This field is optional.
supports COV
This optional field indicates, whether the object supports COV or not. The letter ‘Y’ or an empty field
indicates, that the object supports COV, the letter “N” means COV is not supported.
This field is optional.
hi-limit
This is the upper alarm limit.
For matters of data consistency this field shall only be present if the device
does not support the BACnet property High_Limit to be written or to be changed.
This field should be
filled in, if the server doesn’t support High_Limit at all and the data point should be monitored from
outside for alarm conditions.
This field is optional.
low-limit
This is the lower alarm limit.
For matters of data consistency this field shall only be present if the device
does not support the BACnet property Low_Limit to be written or to be changed.
This field should be
filled in, if the server doesn’t support Low_Limit at all and the data point should be monitored from
outside for alarm conditions.
This field is optional.
state text reference
This field is valid for binary object types and multi-state object types only. The decimal values in this
column are used as reference numbers refering to entries in the sheet “State-Text“. Each entry within the
“State-Text” sheet, identified by its reference number, offers an enumeration of state-texts which
correspond directly with the possible values of the Present_Value property of the referencing object.
Different objects listed in “EDE”- sheet may refer to the same entry in “State-Text”-sheet (use the same
reference number), when their textual representation of Present_Values are identical.
This field is optional.
unit-code
This field is valid for analog object types and loop objects only.
The field contains a decimal value that
represents the BACnetEngineeringUnits code taken from the corresponding BACnet property Units.
In
the “Unit-Text”-sheet, the text descriptors for all supported unit codes can be found as readable text.
This field is optional.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
7/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
vendor-specific-address
This field may be used for specific addresses as they are used in the server device (like terminal
numbers). This field can help to find the mapping to BACnet Objects for non-native BACnet server
devices.
This field is optional.
FORMAT OF THE SHEET “STATE-TEXTS“
This sheet consists of a number of rows, each identified by its reference number, listing an enumeration
of state texts for multi-state objects (Text 1 ...Text n) or for binary objects (only Inactive-Text and ActiveText). Multi-State- and Binary-Texts may not be mixed under one reference number i.e. in the same row.
The row contains therefore either the list “Inactive-Text, Active-Text” or “Text1, Text2, Text3,...”.
The values of the reference numbers identifying the rows, can be freely chosen by the creator of the
document, but have to be unique in this sheet (e.g. any consecutive, monotonous increasing numbers or
company specific text-identifiers or what else).
For unused or not supported states the appropriate column is left empty. The “State-Text”-sheet may
contain more rows than actually referenced in a project, to allow reuse of this sheet in other projects.
The sheet “EDE“ refers to entries in the sheet “State-Texts“, identified by their specific reference
numbers. The sheet “EDE“ and the sheet “State-Texts“ must be maintained in a consistent manner.
FORMAT OF THE SHEET “UNIT-TEXTS“
This sheet contains the unit texts for all BACnetEngineeringUnits codes and for all proprietary units
being used in the project. The first column contains the unit code, the second column contains the
associated text.
The sheet “EDE“ refers to the unit code as indicated in the first column of the sheet “Unit-Texts“. Unit
codes below 256 match with the official ASHRAE unit-codes from the BACnet Standard. Due to
considerations in ASHRAE SSPC135 regarding an expansion of official unit-codes up to a value of 511,
proprietary unit-codes should start at values >511 (if possible). The sheet “EDE“ and the sheet “UnitTexts“ must be maintained in a consistent manner (in “EDE”-sheet referenced units have to be present
in “Unit-Texts”-sheet).
FORMAT OF THE SHEET “OBJECT-TYPES“
This sheet contains the object types for all BACnet Standard objects and for all proprietary objects being
used for interaction between different parties in this project. The first column contains the object-type
code, the second column contains the associated text.
The sheet “EDE“ and the sheet “Object-Types“ must be maintained in a consistent manner (for
proprietary object-types).
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
8/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
ATTENTION!
Numbers in the sheets “Unit-Texts” and “Object-Types” within the ASHRAE-reserved ranges shall not be
changed. These codes are identical to the standard BACnet enumerations and may be used for
automatic configuration purposes.
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
9/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
TEXTES D’ÉTAT STANDARD
STATE TEXT
REF.NUMBER
0201
0202
0203
0204
0205
0206
0211
0212
0221
0222
0231
0232
0233
0234
0235
0241
0242
0243
0244
0251
0252
0253
0254
0255
0261
0262
GTB_ANNEXE
CHUV/DAF/CIT
BINARY OBJECT
INACTIVE
1
No
Off
Closed
Close
Stop
Starting position
Passive
Manual
Reset
Back
Down
Bottom
Left
Direct
Slow
Night operation
Heating
Winter
Gas
Normal
Normal
Normal
Normal
Normal
Normal
Normal
ACTIVE
2
Yes
On
Open
Set
Open
Start
End pos.
Active
Auto
Forward
Up
Top
Right
Reverse
Fast
Day operation
Cooling
Sumer
Oil
Danger
Alarm
Fault
Maintenance
Abnormal
Initialization
Optimization
V 2.0 du 06.03.2015
10/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
STATE TEXT
REF.NUMBER
301
302
303
304
311
321
322
323
324
331
332
341
351
361
401
411
501
511
601
701
801
901
1001
GTB_ANNEXE
CHUV/DAF/CIT
MULTIPLE STATE OBJECT
1
2
3
4
5
6
7
8
9
10
Off
Closed
Starting position
Back
Bottom
Left
Left
Left
Left
Heating
Sustained mode
Normal
Slow
Off
Off
Emergency Off
Off
Off
Off
Off
Off
Off
Off
Auto
Open
End pos.
Forward
Top
Right
Right
Right
Right
Cooling
Heating mode
Alarm
Fast
Stage 2
Stage 2
On
Stage 2
Controller
Stage 2
Stage 2
Stage 2
Stage 2
Stage 2
Stage 3
Frost protection
Stage 3
Min. limit.
Stage 3
Stage 3
Stage 3
Stage 3
Stage 3
Stage 4
Max. limit.
Stage 4
Stage 4
Stage 4
Stage 4
Stage 4
Stage 5
Stage 5
Stage 5
Stage 5
Stage 5
Stage 6
Stage 6
Stage 6
Stage 6
Stage 7
Stage 7
Stage 7
Stage 8
Stage 8
Stage 9
Manual
Center position
Center position
Center position
Center position
Center position
Start position
Neutral position
Off
Zero energy
Setback mode
Maintenance
Medium
Stage 1
Stage 1
Off
Stage 1
On
Stage 1
Stage 1
Stage 1
Stage 1
Stage 1
V 2.0 du 06.03.2015
11/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
TEXTES UNITÉS STANDARD
Encoding of BACnet Engineering Units
Code
Unit Text
3
AMPERES
167
AMPERES-PER-METER
168
AMPERES-PER-SQUARE-METER
169
AMPERES-SQUARE-METERS
55
BARS
20
BTUS
50
BTUS-PER-HOUR
24
BTUS-PER-LB-DRY-AIR
117
BTUS-PER-POUND
179
CANDELAS
180
CANDELAS-PER-SQUARE-METER
118
CENTIMETERS
60
CENTIMETERS-OF-MERCURY
57
CENTIMETERS-OF-WATER
79
CUBIC-FEET
84
CUBIC-FEET-PER-MINUTE
142
CUBIC-FEET-PER-SECOND
80
CUBIC-METERS
135
CUBIC-METERS-PER-HOUR
165
CUBIC-METERS-PER-MINUTE
85
CUBIC-METERS-PER-SECOND
105
CURRENCY1
114
CURRENCY10
106
CURRENCY2
107
CURRENCY3
108
CURRENCY4
109
CURRENCY5
110
CURRENCY6
111
CURRENCY7
112
CURRENCY8
113
CURRENCY9
25
CYCLES-PER-HOUR
26
CYCLES-PER-MINUTE
70
DAYS
65
DEGREE-DAYS-CELSIUS
66
DEGREE-DAYS-FAHRENHEIT
90
DEGREES-ANGULAR
62
DEGREES-CELSIUS
91
DEGREES-CELSIUS-PER-HOUR
92
DEGREES-CELSIUS-PER-MINUTE
64
DEGREES-FAHRENHEIT
93
DEGREES-FAHRENHEIT-PER-HOUR
94
DEGREES-FAHRENHEIT-PER-MINUTE
63
DEGREES-KELVIN
GTB_ANNEXE
CHUV/DAF/CIT
V 2.0 du 06.03.2015
12/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
Code
181
182
14
120
121
170
33
77
76
38
28
155
154
133
171
27
51
71
158
81
86
32
61
58
16
183
127
23
128
147
157
39
186
44
43
42
129
122
17
151
125
149
75
54
9
12
6
19
48
138
GTB_ ANNEXE
CHUV/DAF/CIT
Unit Text
DEGREES-KELVIN-PER-HOUR
DEGREES-KELVIN-PER-MINUTE
DEGREES-PHASE
DELTA-DEGREES-FAHRENHEIT
DELTA-DEGREES-KELVIN
FARADS
FEET
FEET-PER-MINUTE
FEET-PER-SECOND
FOOT-CANDLES
GRAMS-OF-WATER-PER-KILOGRAM-DRY-AIR
GRAMS-PER-MINUTE
GRAMS-PER-SECOND
HECTOPASCALS
HENRYS
HERTZ
HORSEPOWER
HOURS
HUNDREDTHS-SECONDS
IMPERIAL-GALLONS
IMPERIAL-GALLONS-PER-MINUTE
INCHES
INCHES-OF-MERCURY
INCHES-OF-WATER
JOULES
JOULE-SECONDS
JOULES-PER-DEGREE-KELVIN
JOULES-PER-KG-DRY-AIR
JOULES-PER-KILOGRAM-DEGREE-KELVIN
KILO-BTUS
KILO-BTUS-PER-HOUR
KILOGRAMS
KILOGRAMS-PER-CUBIC-METER
KILOGRAMS-PER-HOUR
KILOGRAMS-PER-MINUTE
KILOGRAMS-PER-SECOND
KILOHERTZ
KILOHMS
KILOJOULES
KILOJOULES-PER-DEGREE-KELVIN
KILOJOULES-PER-KG
KILOJOULES-PER-KG-DRY-AIR
KILOMETERS-PER-HOUR
KILOPASCALS
KILOVOLT-AMPERES
KILOVOLT-AMPERES-REACTIVE
KILOVOLTS
KILOWATT-HOURS
KILOWATTS
KWATT-HOURS-PER-SQUARE-FOOT
V 2.0 du 06.03.2015
13/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
Code
137
82
136
88
87
36
37
148
130
126
152
150
140
139
10
13
7
146
49
123
31
164
163
74
166
78
2
134
30
59
162
161
145
159
124
132
72
68
153
160
187
188
95
172
4
97
96
53
98
143
GTB_ ANNEXE
CHUV/DAF/CIT
Unit Text
KWATT-HOURS-PER-SQUARE-METER
LITERS
LITERS-PER-HOUR
LITERS-PER-MINUTE
LITERS-PER-SECOND
LUMENS
LUXES
MEGA-BTUS
MEGAHERTZ
MEGAJOULES
MEGAJOULES-PER-DEGREE-KELVIN
MEGAJOULES-PER-KG-DRY-AIR
MEGAJOULES-PER-SQUARE-FOOT
MEGAJOULES-PER-SQUARE-METER
MEGAVOLT-AMPERES
MEGAVOLT-AMPERES-REACTIVE
MEGAVOLTS
MEGAWATT-HOURS
MEGAWATTS
MEGOHMS
METERS
METERS-PER-HOUR
METERS-PER-MINUTE
METERS-PER-SECOND
METERS-PER-SECOND-PER-SECOND
MILES-PER-HOUR
MILLIAMPERES
MILLIBARS
MILLIMETERS
MILLIMETERS-OF-MERCURY
MILLIMETERS-PER-MINUTE
MILLIMETERS-PER-SECOND
MILLIOHMS
MILLISECONDS
MILLIVOLTS
MILLIWATTS
MINUTES
MONTHS
NEWTON
NEWTON-METERS
NEWTON-SECONDS
NEWTONS-PER-METER
NO-UNITS
OHM-METERS
OHMS
PARTS-PER-BILLION
PARTS-PER-MILLION
PASCALS
PERCENT
PERCENT-OBSCURATION-PER-FOOT
V 2.0 du 06.03.2015
14/15
ANNEXE DIRECTIVE 600
600-10 SPÉCIFICATION EDE
Code
144
99
29
131
100
101
56
40
46
45
119
15
102
103
184
104
73
173
174
116
1
115
0
185
175
21
22
41
156
52
83
89
8
11
5
176
177
18
47
190
34
35
189
141
178
69
67
GTB_ ANNEXE
CHUV/DAF/CIT
Unit Text
PERCENT-OBSCURATION-PER-METER
PERCENT-PER-SECOND
PERCENT-RELATIVE-HUMIDITY
PER-HOUR
PER-MINUTE
PER-SECOND
POUNDS-FORCE-PER-SQUARE-INCH
POUNDS-MASS
POUNDS-MASS-PER-HOUR
POUNDS-MASS-PER-MINUTE
POUNDS-MASS-PER-SECOND
POWER-FACTOR
PSI-PER-DEGREE-FAHRENHEIT
RADIANS
RADIANS-PER-SECOND
REVOLUTIONS-PER-MINUTE
SECONDS
SIEMENS
SIEMENS-PER-METER
SQUARE-CENTIMETERS
SQUARE-FEET
SQUARE-INCHES
SQUARE-METERS
SQUARE-METERS-PER-NEWTON
TESLAS
THERMS
TON-HOURS
TONS
TONS-PER-HOUR
TONS-REFRIGERATION
US-GALLONS
US-GALLONS-PER-MINUTE
VOLT-AMPERES
VOLT-AMPERES-REACTIVE
VOLTS
VOLTS-PER-DEGREE-KELVIN
VOLTS-PER-METER
WATT-HOURS
WATTS
WATTS-PER-METER-PER-DEGREE-KELVIN
WATTS-PER-SQUARE-FOOT
WATTS-PER-SQUARE-METER
WATTS-PER-SQUARE-METER
WATTS-PER-SQUARE-METER-DEGREE-KELVIN
WEBERS
WEEKS
YEARS
V 2.0 du 06.03.2015
15/15