IEC 62386-303:2017

Digital addressable lighting interface - Part 303: Particular requirements - Input devices - Occupancy sensor

IEC 62386-303:2017 specifies a bus system for control by digital signals of electronic lighting equipment which is in line with the requirements of IEC 61347, with the addition of DC supplies.
This document is only applicable to IEC 62386-103:2014 and IEC 62386-­103:2014/AMD1:— input devices that deliver occupancy information to the lighting control system through movement or presence sensing.

Interface d'éclairage adressable numérique - Partie 303: Exigences particulières - Dispositifs d'entrée - Capteur de présence

L'IEC 62386-303:2017 spécifie un système à bus pour la commande par signaux numériques des appareils d’éclairage électroniques conformes aux exigences de l'IEC 61347, en ajoutant les alimentations en courant continu.
Le présent document s'applique uniquement aux dispositifs d'entrée couverts par l'IEC 62386-103:2014 et l'IEC 62386-103:2014/AMD1:—, qui fournissent des informations de présence au système de commande de l'éclairage par le biais de la détection de mouvement ou de présence.

General Information

• Status: Published
• Publication Date: 09-Apr-2024
• ICS: 29.060.10 - Wires
• ICS: 29.140.50 - Lighting installation systems
• ICS: 29.140.99 - Other standards related to lamps
• Technical Committee: SC 34C - Auxiliaries for lamps
• Drafting Committee: WG 11 - TC 34/WG 11
• Current Stage: PPUB - Publication issued
• Start Date: 19-May-2017
• Completion Date: 26-May-2017

Relations

• Amended By: IEC 62386-303:2017/AMD1:2024 - Amendment 1 - Digital addressable lighting interface - Part 303: Particular requirements - Input devices - Occupancy sensor
• Effective Date: 05-Sep-2023

Overview

IEC 62386-303:2017 (consolidated with AMD1:2024) defines particular requirements for input devices - occupancy sensors within the Digital Addressable Lighting Interface (DALI) family. It specifies how occupancy and presence information is delivered over the DALI bus to lighting control systems, complements the general control-device rules in IEC 62386‑103, and aligns with lamp-control requirements in IEC 61347. The consolidated edition (Edition 1.1, 2024) updates the 2017 publication and clarifies behavior for movement and presence sensing devices, including support for DC supplies on the interface.

Key Topics

• Scope and applicability: Applies to input devices that provide occupancy information by movement or presence sensing and is used in conjunction with IEC 62386‑103 (2014) and its amendment.
• Bus system and power: Defines the DALI bus transmission structure, timing, electrical specification and interface power-supply considerations (including DC).
• Input signal mapping: Specifies mapping for movement sensors and presence sensors, including state diagrams and the meaning of inputValue for events.
• Event handling and encoding: Rules for event generation (occupancy/vacancy), priority usage, bus usage, encoding and event filtering.
• Timers and configuration: Standardized timers and configuration mechanisms such as hold timer, report timer, deadtime timer, and settings for sensitivity and detection range.
• Commands and queries: Declares device and instance commands (e.g., INPUT NOTIFICATION, POWER NOTIFICATION), configuration instructions (SET EVENT FILTER, SET HOLD TIMER, SET SENSITIVITY), and queries for instance capabilities and error reporting.
• Error and exception handling: Defines behavior for sensor failure modes, manufacturer-specific errors and how error values are reported.

Applications

IEC 62386‑303 is intended for:

• Sensor and lighting device manufacturers designing DALI-compliant occupancy/presence sensors.
• Lighting control system integrators and specifiers implementing occupancy-based control strategies.
• Facility managers and architects specifying energy-efficient and automated lighting for offices, retail, schools and industrial spaces.
• Test labs and certification bodies verifying compliance with DALI input-device behavior and interoperability.

Practical uses include occupancy-based lighting control for energy savings, automated vacancy detection, daylight-linked control integrations, and retrofits to DALI networks where presence/movement data must be standardized.

Related Standards

• IEC 62386 series - Digital Addressable Lighting Interface (general framework)
• IEC 62386‑101 - General requirements for system components
• IEC 62386‑103 - General requirements for control devices (applicability reference)
• IEC 61347 - Requirements for lamp control gear

Keywords: IEC 62386-303:2017, DALI, occupancy sensor, digital addressable lighting interface, input devices, presence sensing, movement sensor, lighting control.

Standards Content (Sample)

IEC 62386-303 ®
Edition 1.1 2024-04
CONSOLIDATED VERSION
INTERNATIONAL
STANDARD
colour
inside
Digital addressable lighting interface –
Part 303: Particular requirements – Input devices – Occupancy sensor

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Secretariat Tel.: [phone]
3, rue de Varembé [e-mail]
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews, graphical symbols and the glossary.
committee, …). It also gives information on projects, replaced With a subscription you will always have access to up to date
and withdrawn publications. content tailored to your needs.

IEC Just Published - webstore.iec.ch/justpublished
Electropedia - www.electropedia.org
Stay up to date on all new IEC publications. Just Published
The world's leading online dictionary on electrotechnology,
details all new publications released. Available online and once
containing more than 22 500 terminological entries in English
a month by email.
and French, with equivalent terms in 25 additional languages.

Also known as the International Electrotechnical Vocabulary
IEC Customer Service Centre - webstore.iec.ch/csc
(IEV) online.
If you wish to give us your feedback on this publication or need

further assistance, please contact the Customer Service
Centre: [e-mail].
IEC 62386-303 ®
Edition 1.1 2024-04
CONSOLIDATED VERSION
INTERNATIONAL
STANDARD
colour
inside
Digital addressable lighting interface –
Part 303: Particular requirements – Input devices – Occupancy sensor
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 29.140.50; 29.140.99 ISBN 978-2-8322-8753-8
REDLINE VERSION – 2 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 8
4 General . 9
4.1 General . 9
4.2 Version number . 9
4.3 Insulation . 9
5 Electrical specification . 9
6 Interface power supply . 9
7 Transmission protocol structure . 10
8 Timing . 10
9 Method of operation . 10
9.1 General . 10
9.2 Instance type . 10
9.3 Input signal and value . 10
9.3.1 General . 10
9.3.2 Input signal mapping for movement sensors . 10
9.3.3 Input signal mapping for presence sensors . 14
9.4 Events . 16
9.4.1 Priority use . 16
9.4.2 Bus usage . 16
9.4.3 Encoding . 16
9.4.4 Event configuration . 17
9.4.5 Event generation . 18
9.4.6 Movement trigger and catching . 18
9.5 Configuring the input device . 19
9.5.1 Using the hold timer . 19
9.5.2 Using the report timer . 19
9.5.3 Using the deadtime timer . 19
9.5.4 Setting the timers . 19
9.5.5 Manual configuration . 20
9.5.6 Occupancy sensor capabilities . 21
9.5.7 Configuring the sensitivity and range . 21
9.6 Exception handling. 22
9.6.1 Physical sensor failure . 22
9.6.2 Manufacturer specific errors . 22
9.6.3 Error value . 22
10 Declaration of variables . 22
11 Definition of commands . 23
11.1 General . 23
11.2 Overview sheets . 23
11.2.1 General . 23
11.2.2 Standard commands . 24
11.3 Event messages . 24

© IEC 2024
11.3.1 INPUT NOTIFICATION (device/instance, event) . 24
11.3.2 POWER NOTIFICATION (device) . 24
11.4 Device control instructions . 24
11.5 Device configuration instructions . 24
11.6 Device queries . 25
11.7 Instance control instructions . 25
11.7.1 General . 25
11.7.2 CATCH MOVEMENT . 25
11.7.3 CANCEL HOLD TIMER . 25
11.8 Instance configuration instructions . 25
11.8.1 General . 25
11.8.2 SET EVENT FILTER (DTR0) . 25
11.8.3 SET HOLD TIMER (DTR0) . 25
11.8.4 SET REPORT TIMER (DTR0) . 25
11.8.5 SET DEADTIME TIMER (DTR0) . 26
11.8.6 SET DETECTION RANGE (DTR0) . 26
11.8.7 SET SENSITIVITY (DTR0) . 26
11.9 Instance queries . 26
11.9.1 General . 26
11.9.2 QUERY INSTANCE ERROR . 26
11.9.3 QUERY DEADTIME TIMER . 26
11.9.4 QUERY HOLD TIMER. 26
11.9.5 QUERY REPORT TIMER . 26
11.9.6 QUERY CATCHING . 27
11.9.7 QUERY INSTANCE CAPABILITIES . 27
11.9.8 QUERY DETECTION RANGE . 27
11.9.9 QUERY SENSITIVITY . 27
11.10 Special commands . 27
Bibliography . 28

Figure 1 – IEC 62386 graphical overview . 6
Figure 2 – State diagram for movement based sensor. 13
Figure 3 – State diagram for presence sensor . 15

Table 1 – Meaning of “inputValue” . 10
Table 11 – Presence sensor state transitions . 16
Table 2 – Occupancy and vacancy events . 17
Table 3 – Event filter . 18
Table 4 – Event timer setting . 20
Table 5 – “manualCapabilityInstance3xx” values . 21
Table 12 – "occupancyCapabilities" values . 21
Table 6 – “instanceErrorByte” values . 22
Table 7 – Declaration of device variables . 22
Table 8 – Restrictions to instance variables defined in IEC 62386-103:2014 and
IEC 62386-103:2014/AMD1:— IEC 62386-103:2022 . 23
Table 9 – Declaration of instance variables . 23
Table 10 – Standard commands . 24

REDLINE VERSION – 4 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DIGITAL ADDRESSABLE LIGHTING INTERFACE –

Part 303: Particular requirements – Input devices –
Occupancy sensor
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC
Publication(s)"). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s),
which may be required to implement this document. However, implementers are cautioned that this may not
represent the latest information, which may be obtained from the patent database available at
https://patents.iec.ch. IEC shall not be held responsible for identifying any or all such patent rights.
This consolidated version of the official IEC Standard and its amendment has been
prepared for user convenience.
IEC 62386-303 edition 1.1 contains the fifth edition (2017-05) [documents 34C/1313/FDIS
and 34C/1333/RVD] and its amendment 1 (2024-04) [documents 34/1013/CDV and
34/1078A/RVC].
In this Redline version, a vertical line in the margin shows where the technical content
is modified by amendment 1. Additions are in green text, deletions are in strikethrough
red text. A separate Final version with all changes accepted is available in this
publication.
© IEC 2024
International Standard IEC 62386-303 has been prepared by subcommittee 34C: Auxiliaries
for lamps, of IEC technical committee 34: Lamps and related equipment.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
This Part 303 of IEC 62386 is intended to be used in conjunction with:
• Part 101, which contains general requirements for system components;
• Part 103, which contains general requirements for control devices.
A list of all parts in the IEC 62386 series, published under the general title: Digital
addressable lighting interface, can be found on the IEC website.
The committee has decided that the contents of this document and its amendment will remain
unchanged until the stability date indicated on the IEC website under webstore.iec.ch in the
data related to the specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
REDLINE VERSION – 6 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
INTRODUCTION
IEC 62386 contains several parts, referred to as series. The 1xx series includes the basic
specifications. Part 101 contains general requirements for system components, Part 102
extends this information with general requirements for control gear and Part 103 extends it
further with general requirements for control devices.
The 2xx parts extend the general requirements for control gear with lamp specific extensions
(mainly for backward compatibility with Edition 1 of IEC 62386) and with control gear specific
features.
The 3xx parts extend the general requirements for control devices with input device specific
extensions describing the instance types as well as some common features that can be
combined with multiple instance types.
This first edition of IEC 62386-303 is to be used in conjunction with IEC 62386-101:2014,
IEC 62386-101:2014/AMD1:— IEC 62386-101:2022, IEC 62386-103:2014 and IEC 62386-
103:2014/AMD1:— IEC 62386-103:2022. The division of IEC 62386 into separately published
parts provides for ease of future amendments and revisions. Additional requirements will be
added as and when a need for them is recognized.
The setup of the standards is graphically represented in Figure 1 below.
2xx 2xx 2xx 2xx 2xx 3xx 3xx 3xx 3xx 3xx
102 General requirements - 103 General requirements -
Control gear Control devices
101 General requirements -
System components
IEC
Figure 1 – IEC 62386 graphical overview

© IEC 2024
This document, and the other parts that make up the IEC 62386-300 series, in referring to any
of the clauses of IEC 62386-1XX, specifies the extent to which such a clause is applicable;
the parts also include additional requirements, as necessary.
Where the requirements of any of the clauses of IEC 62386-1XX are referred to in this
document by the sentence “The requirements of IEC 62386-1XX, Clause “n” apply”, this
sentence is to be interpreted as meaning that all requirements of the clause in question of
Part 1XX apply, except any which are clearly inapplicable.
The standardization of the control interface for control devices is intended to achieve
compatible co-existence and multi-master operation between electronic control gear and
lighting control devices, below the level of building management systems. This document
describes a method of implementing occupancy sensors.
All numbers used in this document are decimal numbers unless otherwise noted. Hexadecimal
numbers are given in the format 0xVV, where VV is the value. Binary numbers are given in
the format XXXXXXXXb or in the format XXXX XXXX, where X is 0 or 1; “x” in binary numbers
means “don't care”.
The following typographic expressions are used:
Variables: “variableName” or “variableName[3:0]”, giving only bits 3 to 0 of “variableName”.
Range of values: [lowest, highest]
Command: “COMMAND NAME”
REDLINE VERSION – 8 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
DIGITAL ADDRESSABLE LIGHTING INTERFACE –

Part 303: Particular requirements – Input devices –
Occupancy sensor
1 Scope
This part of IEC 62386 specifies a bus system for control by digital signals of electronic
lighting equipment which is in line with the requirements of IEC 61347, with the addition of DC
supplies.
This document is only applicable to IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—
input devices that deliver occupancy information to the lighting control system through
movement or presence sensing.
NOTE Requirements for testing individual products during production are not included.
This part of IEC 62386 is applicable to input devices that provide occupancy information to
the lighting control system through movement or presence sensing.
This document is only applicable to input devices complying with IEC 62386-103:2022.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC 62386-101:20142022, Digital addressable lighting interface – Part 101: General
requirements – System components
IEC 62386-101:2014/AMD1:—
IEC 62386-103:20142022, Digital addressable lighting interface – Part 103: General
requirements – Control devices
IEC 62386-103:2014/AMD1:—
IEC 62386-333:— 2018, Digital addressable lighting interface – Part 333: Particular
requirements for control devices – Manual configuration (feature type 33)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62386-101 and
IEC 62386-103 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
_____________
Under preparation. Stage at the time of publication: IEC ACDV 62386-101/AMD1:2017.
Under preparation. Stage at the time of publication: IEC ACDV 62386-103/AMD1:2017.
Under preparation. Stage at the time of publication: IEC CCDV 62386-333:2017.

© IEC 2024
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
instance
movement or presence input signal processing unit of an input device
[SOURCE: IEC 62386-101:20142022, 3.29, modified – "movement or presence input" added]
3.2
movement sensor
instance based on movement detection only where occupancy is implied by movement and
vacancy is concluded from the absence of movement during a specified amount of time
Note 1 to entry: Movement sensing is typically done using a passive infra-red detector combined with Fresnel
optics.
3.3
presence sensor
instance based on means other than only movement detection where occupancy and vacancy
can be concluded immediately and where, in some cases, movement can also be detected
Note 1 to entry: Presence sensing may be implemented using for example camera based systems.
4 General
4.1 General
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022, Clause 4 apply, with the restrictions, changes and additions identified below.
4.2 Version number
In 4.2 of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-103:2022, “103”
shall be replaced by “303”, “version number” shall be replaced by “extended version number”
and “versionNumber” shall be replaced by "extendedVersionNumber".
4.3 Insulation
According to IEC 61347-1 applicable safety standards, it might can be required that the input
device has at least supplementary insulation to accessible parts. This depends on the
connected components. In this case special attention should be paid with respect to the
sensor(s) being used.
NOTE IEC-62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-103:2022 requires system components
to have at least basic insulation.
5 Electrical specification
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022, Clause 5 apply.
6 Interface power supply
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022 IEC 62386-103:2022, Clause 6 apply.

REDLINE VERSION – 10 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
7 Transmission protocol structure
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022, Clause 7 apply.
NOTE Subclause 9.4 provides detailed event information applicable to instances.
8 Timing
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022, Clause 8 apply.
9 Method of operation
9.1 General
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— IEC 62386-
103:2022, Clause 9 apply, with the following restrictions and additions.
9.2 Instance type
The instance type (“instanceType”) shall be equal to 3.
9.3 Input signal and value
9.3.1 General
The input “resolution” shall be equal to 2.
NOTE 1 A “resolution” of 2 implies that “inputValue” is a single byte variable with possible values limited to 0x00,
0x55, 0xAA and 0xFF.
NOTE 2 Since “inputValue” is a single byte variable, the instance will answer NO to “QUERY INPUT VALUE
LATCH”.
“inputValue” shall reflect the occupancy state in the area covered by the sensor, as shown in
Table 1.
Table 1 – Meaning of “inputValue”
“inputValue” Area state Movement
0x00 Vacant No
0x55 Vacant Yes
0xAA Occupied No
0xFF Occupied Yes
9.3.2 Input signal mapping for movement sensors
For movement sensors, the input signal shall directly map onto movement (only). Depending
on the type of sensor used, it is possible that a very short pulse can be produced only when
movement is first detected, or a longer signal can be produced whilst movement continues to
be detected. In any case, the instance shall change "inputValue" to 0xFF immediately if
movement is detected, remaining in this state for at least 1 s, thus reporting an occupied area
state as well. See Figure 2.
© IEC 2024
NOTE 1 This means that an instance receiving a rapid succession of movement signals which are less than 1 s
apart, will remain in the occupied and movement state, and will create a movement event only at the time it entered
this state.
A movement sensor shall support a hold timer, with timeout value T , which shall be
hold
(re)started each time movement is detected. A transition of "inputValue" to 0x00 shall only
take place at the moment the hold timer expires or is cancelled. In such a case the "vacant"
trigger shall be generated. (Re)starting the hold timer means: "discard any remaining hold
time and start timing a new hold time period".
While the area is occupied, the “inputValue” shall change between 0xFF and 0xAA depending
on momentary movement detection only.

REDLINE VERSION – 12 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
Movement based sensor
Vacant
0x55: Vacant and movement
Report
0x00: Vacant and no movement
timer
State never reached
expired /
entry / (Re-)trigger report timer
'Repeat'
trigger
Hold timer expired or cancelled /
Movement detected /
'Vacant' trigger
'Movement' and 'Occupied' trigger

Occupied
Report
0xFF: Occupied and movement
timer
expired /
entry / (Re-)trigger report timer,
'Repeat'
(Re-)trigger hold timer
trigger
No movement detected / Movement detected /
'No movement' trigger 'Movement' trigger
Report
0xAA: Occupied and no movement timer
expired /
entry / (Re-)trigger report timer
'Repeat'
trigger
IEC
© IEC 2024
Figure 2 – State diagram for movement based sensor
NOTE 12 An input value of 0x55 is not applicable, since movement implies occupancy.
NOTE 23 Vacancy and occupancy can be concluded from “inputValue” only.
NOTE 4 "Stop hold timer" means the hold timer is frozen. "(Re-)start hold timer" means the hold timer is re-
started with the full hold time T .
hold
REDLINE VERSION – 14 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
9.3.3 Input signal mapping for presence sensors
Presence sensors shall report the movement state and area state as quickly as possible. If a
presence sensor is not able to detect motion, it shall report no movement and shall not enter
states 0x55 or 0xFF. See Figure 3.
NOTE This means that the hold timer in a presence sensor will never be started.
If a presence sensor is not able to detect motion without this also causing occupancy, then
the presence sensor shall not enter state 0x55.
EXAMPLE For a presence sensor that is not able to detect motion without this also causing occupancy, example
state transitions are as follows: Starting in state 0x00, a person moving into the area is detected, causing
simultaneous movement and occupancy triggers and entry to state 0xFF. Without the movement stopping, the
person exits the area causing movement and presence to simultaneously end, causing a return to state 0x00. If,
instead, the person entering the area then pauses (ceases movement) for a while, this would cause a state change
to 0xAA. From this state, a return to 0x00 or 0xFF are both possible.

© IEC 2024
Presence sensor
Report
Report
Occupancy detected /
timer
timer
0x55: Vacant and movement
'Occupied' trigger 0xFF: Occupied and movement
expired /
expired /
'Repeat'
'Repeat'
entry / (Re-)trigger report timer entry / (Re-)trigger report timer
trigger
trigger
Vacancy detected /
'Vacant' trigger
Movement detected / No movement detected / Movement detected / No movement detected /
'Movement' trigger 'No movement' trigger 'Movement' trigger 'No movement' trigger
Report
Report
Occupancy detected /
timer
timer
0x00: Vacant and no movement 0xAA: Occupied and no movement
'Occupied' trigger
expired /
expired /
'Repeat'
entry / (Re-)trigger report timer entry / (Re-)trigger report timer 'Repeat'
trigger
Vacancy detected / trigger
'Vacant' trigger
IEC
Figure 3 – State diagram for presence sensor
Table 11 shows the state transitions with the conditions for exiting each state, and the action
upon exit.
REDLINE VERSION – 16 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
Table 11 – Presence sensor state transitions
Initial state Exit condition Action on exit New state
Movement detected "Movement" trigger 0x55: Vacant and movement
0xAA: Occupied and no
Occupancy detected "Occupied" trigger
0x00: Vacant and no
movement
movement
Occupancy and movement "Occupied" and 0xFF: Occupied and
detected "movement" triggers movement
No movement detected "No movement" trigger 0x00: Vacant and no
movement
0x55: Vacant and Occupancy detected "Occupied" trigger 0xFF: Occupied and
movement movement
Occupancy and no "Occupied" and "no 0xAA: Occupied and no
movement detected movement" triggers movement
Movement detected "Movement" trigger 0xFF: Occupied and
movement
0xAA: Occupied and no Vacancy detected "Vacant" trigger 0x00: Vacant and no
movement movement
Vacancy and movement "Vacant" and "movement" 0x55: Vacant and movement
detected triggers
No movement detected "No movement" trigger 0xAA: Occupied and no
movement
0xFF: Occupied and
Vacancy detected "Vacant" trigger 0x55: Vacant and movement
movement
Vacancy and no movement "Vacant" and "no 0x00: Vacant and no
detected movement" triggers movement

9.4 Events
9.4.1 Priority use
9.4.1.1 General
The default “eventPriority” shall be priority 4. Since the application controller needs a timeslot
to respond, “eventPriority” should not be set to 2.
9.4.1.2 Periodic events
The periodic “INPUT NOTIFICATION” message to report the occupancy confirmation event
(still vacant or still occupied) shall always be sent with priority 5.
NOTE This makes “eventPriority” inapplicable for this event only.
9.4.2 Bus usage
9.4.2.1 Instance level
Multiple events from an instance shall not be sent in a transaction. There is a configurable
delay T that shall be taken into account. See 9.5.3 for more information.
deadtime
9.4.2.2 Device level
On device level, events from different instances may be sent in a transaction.
9.4.3 Encoding
Occupancy and vacancy events shall be encoded as shown in Table 2.

© IEC 2024
Table 2 – Occupancy and vacancy events
Event name Event information Description
No movement 00 0000 ---0b No movement detected. Corresponding trigger is the ‘No movement’
trigger.
Movement 00 0000 ---1b Movement detected. Corresponding trigger is the ‘Movement’ trigger.
Vacant 00 0000 -00-b The area has become vacant. Corresponding trigger is the ‘Vacant’ trigger.
Still vacant 00 0000 -10-b The area is still vacant. The event occurs at regular intervals as long as
the vacant condition holds. Corresponding trigger is the ‘Repeat’ trigger.
Occupied 00 0000 -01-b The area has become occupied. Corresponding trigger is the ‘Occupied’
trigger.
Still occupied 00 0000 -11-b The area is still occupied. The event occurs at regular intervals as long as
the occupied condition holds. Corresponding trigger is the ‘Repeat’ trigger.
Presence sensor 00 0000 0---b The current event is triggered by a presence based sensor.
Movement sensor 00 0000 1---b The current event is triggered by a movement based sensor.
1x xxxx xxxxb Reserved.
01 xxxx xxxxb
00 1xxx xxxxb
00 01xx xxxxb
00 001x xxxxb
00 0001 xxxxb
NOTE 1 In order to save bus bandwidth, the application controller has the possibility to inhibit event notifications
that it does not need, as is described in 9.4.4.
The event shall be reported in one “INPUT NOTIFICATION” by bitwise OR-ing the event
information values. In order to perform the OR-ing, every bit that is marked with “-“ for the
listed event names shall be assumed 0.
The information contained in bit 3 can be used by the application controller to determine
whether the sensor already applied a hold timer or not (movement based sensor).
NOTE 2 Every enabled event leads to a complete event, reporting both the movement and occupancy information.
9.4.4 Event configuration
The application controller may not need all the event triggers mentioned in 9.4.3. The
instance shall allow the application controller to set the “eventFilter” (see IEC 62386-
103:2014 and IEC 62386-103:2014/AMD1:—, 9.7.4) to inhibit those event triggers that the
application controller does not need. For this document, “eventFilter” shall be reduced to one
byte.
Events shall be enabled or disabled according to the value of "eventFilter". For this document,
"eventFilter" shall be reduced to one byte.
NOTE Inhibiting event triggers increases the effective bus bandwidth availability.
The “eventFilter” shall have the definition as given in Table 3:

REDLINE VERSION – 18 – IEC 62386-303:2017+AMD1:2024 CSV
© IEC 2024
Table 3 – Event filter
Bit Description Value Default
0 Occupied event enabled? "1" = "Yes" 1
1 Vacant event enabled? "1" = "Yes" 1
2 Repeat event enabled? "1" = "Yes" 0
3 Movement event enabled? "1" = "Yes" 0
4 No movement event enabled? "1" = "Yes" 0
5 Reserved 0 0
6 Reserved 0 0
7 Reserved 0 0
The filter can be set via “SET EVENT FILTER (DTR0)” and be queried using
“QUERY EVENT FILTER 0-7”, see IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—
IEC 62386-103:2022 for details.
If the ‘repeat’ event is enabled, on expiration of the report timer the ‘still vacant’ event shall be
sent if the ‘vacant’ event is enabled, and the ‘v still occupied’ event shall be sent if the
‘occupied’ event is enabled.
Disabling an event shall not cancel transmission of an event that has already occurred and is
waiting to be sent due to the deadtime timer or bus unavailability.
9.4.5 Event generation
An event shall be generated on every change of “inputValue” or when the report timer expires.
In case a new event occurs before the current event is being sent, the new event shall replace
the current event. This could be caused for example by bus unavailability or the deadtime
timer.
9.4.6 Movement trigger and catching
The event filter can be adjusted to enable or disable the "movement" event. Care should be
taken when enabling the ‘movement’ event, as it is likely to flood the bus.
NOTE 1 Application controllers can consider the need to enable the "movement" event as this can result in
flooding the bus.
If the movement event is disabled, the application controller can explicitly ask for the event to
be sent once (setting “catching”), and the variable "catching" is TRUE, then a movement
trigger shall cause an "INPUT NOTIFICATION" event to be sent. "catching" is set using the
command "CATCH MOVEMENT". Each "INPUT NOTIFICATION" that was triggered by
movement, shall clear "catching", which implies that "CATCH MOVEMENT" is a single-
notification request. The instruction shall not change the event filter.
If the "movement" event is disabled and the "CATCH MOVEMENT" command is executed
whilst in the "occupied and movement" state, "catching" shall be set to TRUE but an "INPUT
NOTIFICIATION" shall not be triggered until the next change from a "no movement" to a
"movement" state.
If the movement event is enabled the “CATCH MOVEMENT” instruction shall be ignored
discarded and "catching" shall be set to FALSE.
NOTE 2 Another "CATCH MOVEMENT" has no effect if a command has not (yet) led to a notification.

© IEC 2024
NOTE 3 "catching" does not affect event generation due to the "no movement" trigger.
The query "QUERY CATCHING" can be used to verify that no "movement" notification has
been sent yet ("catching" has been set).
9.5 Configuring the input device
9.5.1 Using the hold timer
The hold timer is only implemented for movement based sensors. The model in Figure 2
shows how the hold timer is used to derive occupancy.
The hold timer can be cancelled using “CANCEL HOLD TIMER”. This forces a transition to the
vacant state.
If the hold timer is running, then "CANCEL HOLD TIMER" shall cancel the hold timer and
force a transition to the "vacant" state.
Both cancellation of the hold timer and expiration of the hold timer shall generate a ’vacant’
trigger.
9.5.2 Using the report timer
If the report timer is set, it shall generate a ‘repeat’ trigger every T even if the “inputValue”
report
has not changed. The report timer shall be restarted every time an event is sent.
The report timer shall be started,
• at power-on: if enabled, immediately after the receiver has started up, with the time to the
s;
first trigger recommended to be shortened to a random time between 0 s and T
report
• otherwise immediately after enablement.
This implies that the first "INPUT NOTIFICATION" message due to the report timer is sent at
a maximum time of T after starting. This may be delayed by other "INPUT
report
NOTIFICATION" messages, or by bus availability.
NOTE If multiple devices have the report timer enabled, they might send out conflicting data controlling used by
application controllers to control the same control gear. Depending on the application, care needs to be taken when
enabling the report timer. Application controllers can avoid this problem by enabling only the required report
timer(s).
9.5.3 Using the deadtime timer
If the deadtime timer is set, the instance shall not send out an event until the deadtime timer
has expired. If an event was suppressed due to the deadtime timer, then the latest event shall
be sent on expiry of the deadtime timer. The deadtime timer shall be restarted every time an
event is sent.
NOTE 1 The following example demonstrates this: The event filter is configured with only the movement event
enabled. The deadtime timer is currently running due to a previous INPUT NOTIFICATION from this instance. A
new movement trigger occurs. The transmission of a new INPUT NOTIFICATION is supressed because the
deadtime timer is still running. Next, the "occupied and movement" state ends, with the instance changing to the
"occupied and no-movement" state. Next, the deadtime timer expires. Owing to the supressed event during the
deadtime, a new INPUT NOTIFICATION is now sent. This will indicate "no movement" and "occupied" because
these are the current states.
NOTE 2 The purpose of the deadtime timer is to increase the effective bus bandwidth availability. It is not
intended to be used as a hold timer.
9.5.4 Setting the timers
Event Deadtime, hold and report timers shall be pr
...

IEC 62386-303 ®
Edition 1.0 2017-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Digital addressable lighting interface –
Part 303: Particular requirements – Input devices – Occupancy sensor

Interface d'éclairage adressable numérique –
Partie 303: Exigences particulières – Dispositifs d'entrée – Capteur de présence

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: [e-mail].
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Catalogue IEC - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
Application autonome pour consulter tous les renseignements
Le premier dictionnaire en ligne de termes électroniques et
bibliographiques sur les Normes internationales,
électriques. Il contient 20 000 termes et définitions en anglais
Spécifications techniques, Rapports techniques et autres
et en français, ainsi que les termes équivalents dans 16
documents de l'IEC. Disponible pour PC, Mac OS, tablettes
langues additionnelles. Egalement appelé Vocabulaire
Android et iPad.
Electrotechnique International (IEV) en ligne.

Recherche de publications IEC - www.iec.ch/searchpub
Glossaire IEC - std.iec.ch/glossary
65 000 entrées terminologiques électrotechniques, en anglais
La recherche avancée permet de trouver des publications IEC
en utilisant différents critères (numéro de référence, texte, et en français, extraites des articles Termes et Définitions des
comité d’études,…). Elle donne aussi des informations sur les publications IEC parues depuis 2002. Plus certaines entrées
projets et les publications remplacées ou retirées. antérieures extraites des publications des CE 37, 77, 86 et

CISPR de l'IEC.
IEC Just Published - webstore.iec.ch/justpublished

Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications IEC. Just
Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur cette
Disponible en ligne et aussi une fois par mois par email. publication ou si vous avez des questions contactez-nous:
[e-mail].
IEC 62386-303 ®
Edition 1.0 2017-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Digital addressable lighting interface –

Part 303: Particular requirements – Input devices – Occupancy sensor

Interface d'éclairage adressable numérique –

Partie 303: Exigences particulières – Dispositifs d'entrée – Capteur de présence

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 29.140.50; 29.140.99 ISBN 978-2-8322-4343-5

– 2 – IEC 62386-303:2017 © IEC 2017
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 8
2 Normative references . 8
3 Terms and definitions . 8
4 General . 9
4.1 General . 9
4.2 Version number . 9
4.3 Insulation . 9
5 Electrical specification . 9
6 Interface power supply . 9
7 Transmission protocol structure . 9
8 Timing . 10
9 Method of operation . 10
9.1 General . 10
9.2 Instance type . 10
9.3 Input signal and value . 10
9.3.1 General . 10
9.3.2 Input signal mapping for movement sensors . 10
9.3.3 Input signal mapping for presence sensors . 12
9.4 Events . 12
9.4.1 Priority use . 12
9.4.2 Bus usage . 12
9.4.3 Encoding . 13
9.4.4 Event configuration . 13
9.4.5 Event generation . 14
9.4.6 Movement trigger and catching . 14
9.5 Configuring the input device . 14
9.5.1 Using the hold timer . 14
9.5.2 Using the report timer . 15
9.5.3 Using the deadtime timer . 15
9.5.4 Setting the timers . 15
9.5.5 Manual configuration . 16
9.6 Exception handling. 16
9.6.1 Physical sensor failure . 16
9.6.2 Manufacturer specific errors . 16
9.6.3 Error value . 16
10 Declaration of variables . 17
11 Definition of commands . 18
11.1 General . 18
11.2 Overview sheets . 18
11.2.1 General . 18
11.2.2 Standard commands . 18
11.3 Event messages . 19
11.3.1 INPUT NOTIFICATION (device/instance, event) . 19
11.3.2 POWER NOTIFICATION (device) . 19

11.4 Device control instructions . 19
11.5 Device configuration instructions . 19
11.6 Device queries . 19
11.7 Instance control instructions . 19
11.7.1 General . 19
11.7.2 CATCH MOVEMENT . 19
11.7.3 CANCEL HOLD TIMER . 19
11.8 Instance configuration instructions . 20
11.8.1 General . 20
11.8.2 SET EVENT FILTER (DTR0) . 20
11.8.3 SET HOLD TIMER (DTR0) . 20
11.8.4 SET REPORT TIMER (DTR0) . 20
11.8.5 SET DEADTIME TIMER (DTR0) . 20
11.9 Instance queries . 20
11.9.1 General . 20
11.9.2 QUERY INSTANCE ERROR . 20
11.9.3 QUERY DEADTIME TIMER . 20
11.9.4 QUERY HOLD TIMER. 20
11.9.5 QUERY REPORT TIMER . 20
11.9.6 QUERY CATCHING . 21
11.10 Special commands . 21
Bibliography . 22

Figure 1 – IEC 62386 graphical overview . 6
Figure 2 – State diagram for movement based sensor. 11
Figure 3 – State diagram for presence sensor . 12

Table 1 – Meaning of “inputValue” . 10
Table 2 – Occupancy and vacancy events . 13
Table 3 – Event filter . 14
Table 4 – Event timer setting . 15
Table 5 – “manualCapabilityInstance3xx” values . 16
Table 6 – “instanceErrorByte” values . 17
Table 7 – Declaration of device variables . 17
Table 8 – Restrictions to instance variables defined in IEC 62386-103:2014 and
IEC 62386-103:2014/AMD1:— . 17
Table 9 – Declaration of instance variables . 18
Table 10 – Standard commands . 18

– 4 – IEC 62386-303:2017 © IEC 2017
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DIGITAL ADDRESSABLE LIGHTING INTERFACE –

Part 303: Particular requirements – Input devices –
Occupancy sensor
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62386-303 has been prepared by subcommittee 34C: Auxiliaries
for lamps, of IEC technical committee 34: Lamps and related equipment.
The text of this standard is based on the following documents:
FDIS Report on voting
34C/1313/FDIS 34C/1333/RVD
Full information on the voting for the approval of this International Standard can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
This Part 303 of IEC 62386 is intended to be used in conjunction with:

• Part 101, which contains general requirements for system components;
• Part 103, which contains general requirements for control devices.
A list of all parts in the IEC 62386 series, published under the general title: Digital
addressable lighting interface, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC 62386-303:2017 © IEC 2017
INTRODUCTION
IEC 62386 contains several parts, referred to as series. The 1xx series includes the basic
specifications. Part 101 contains general requirements for system components, Part 102
extends this information with general requirements for control gear and Part 103 extends it
further with general requirements for control devices.
The 2xx parts extend the general requirements for control gear with lamp specific extensions
(mainly for backward compatibility with Edition 1 of IEC 62386) and with control gear specific
features.
The 3xx parts extend the general requirements for control devices with input device specific
extensions describing the instance types as well as some common features that can be
combined with multiple instance types.
This first edition of IEC 62386-303 is to be used in conjunction with IEC 62386-101:2014,
IEC 62386-101:2014/AMD1:—, IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:— The
division of IEC 62386 into separately published parts provides for ease of future amendments
and revisions. Additional requirements will be added as and when a need for them is
recognized.
The setup of the standards is graphically represented in Figure 1 below.
2xx 2xx 2xx 2xx 2xx 3xx 3xx 3xx 3xx 3xx
102 General requirements - 103 General requirements -
Control gear Control devices
101 General requirements -
System components
IEC
Figure 1 – IEC 62386 graphical overview
This document, and the other parts that make up the IEC 62386-300 series, in referring to any
of the clauses of IEC 62386-1XX, specifies the extent to which such a clause is applicable;
the parts also include additional requirements, as necessary.
Where the requirements of any of the clauses of IEC 62386-1XX are referred to in this
document by the sentence “The requirements of IEC 62386-1XX, Clause “n” apply”, this
sentence is to be interpreted as meaning that all requirements of the clause in question of
Part 1XX apply, except any which are clearly inapplicable.
The standardization of the control interface for control devices is intended to achieve
compatible co-existence and multi-master operation between electronic control gear and
lighting control devices, below the level of building management systems. This document
describes a method of implementing occupancy sensors.
All numbers used in this document are decimal numbers unless otherwise noted. Hexadecimal
numbers are given in the format 0xVV, where VV is the value. Binary numbers are given in

the format XXXXXXXXb or in the format XXXX XXXX, where X is 0 or 1; “x” in binary numbers
means “don't care”.
The following typographic expressions are used:
Variables: “variableName” or “variableName[3:0]”, giving only bits 3 to 0 of “variableName”.
Range of values: [lowest, highest]
Command: “COMMAND NAME”
– 8 – IEC 62386-303:2017 © IEC 2017
DIGITAL ADDRESSABLE LIGHTING INTERFACE –

Part 303: Particular requirements – Input devices –
Occupancy sensor
1 Scope
This part of IEC 62386 specifies a bus system for control by digital signals of electronic
lighting equipment which is in line with the requirements of IEC 61347, with the addition of DC
supplies.
This document is only applicable to IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—
input devices that deliver occupancy information to the lighting control system through
movement or presence sensing.
NOTE Requirements for testing individual products during production are not included.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC 62386-101:2014, Digital addressable lighting interface – Part 101: General requirements
– System components
IEC 62386-101:2014/AMD1:—
IEC 62386-103:2014, Digital addressable lighting interface – Part 103: General requirements
– Control devices
IEC 62386-103:2014/AMD1:—
IEC 62386-333:— , Digital addressable lighting interface – Part 333: Particular requirements
for control devices – Manual configuration (feature type 33)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62386-101 and
IEC 62386-103 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
_____________
Under preparation. Stage at the time of publication: IEC ACDV 62386-101/AMD1:2017.
Under preparation. Stage at the time of publication: IEC ACDV 62386-103/AMD1:2017.
Under preparation. Stage at the time of publication: IEC CCDV 62386-333:2017.

3.1
instance
movement or presence input signal processing unit of an input device
[SOURCE: IEC 62386-101:2014, 3.29, modified – "movement or presence input" added]
3.2
movement sensor
instance based on movement detection only where occupancy is implied by movement and
vacancy is concluded from the absence of movement during a specified amount of time
Note 1 to entry: Movement sensing is typically done using a passive infra-red detector combined with Fresnel
optics.
3.3
presence sensor
instance based on means other than only movement detection where occupancy and vacancy
can be concluded immediately and where, in some cases, movement can also be detected
Note 1 to entry: Presence sensing may be implemented using for example camera based systems.
4 General
4.1 General
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 4 apply,
with the restrictions, changes and additions identified below.
4.2 Version number
In 4.2 of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, “103” shall be replaced by
“303”, “version number” shall be replaced by “extended version number” and “versionNumber”
shall be replaced by "extendedVersionNumber".
4.3 Insulation
According to IEC 61347-1 it might be required that the input device has at least
supplementary insulation. This depends on the connected components. In this case special
attention should be paid with respect to the sensor(s) being used.
NOTE IEC-62386-103:2014 and IEC 62386-103:2014/AMD1:— requires system components to have at least basic
insulation.
5 Electrical specification
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 5 apply.
6 Interface power supply
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 6 apply.
7 Transmission protocol structure
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 7 apply.
NOTE Subclause 9.4 provides detailed event information applicable to instances.

– 10 – IEC 62386-303:2017 © IEC 2017
8 Timing
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 8 apply.
9 Method of operation
9.1 General
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 9 apply,
with the following restrictions and additions.
9.2 Instance type
The instance type (“instanceType”) shall be equal to 3.
9.3 Input signal and value
9.3.1 General
The input “resolution” shall be equal to 2.
NOTE 1 A “resolution” of 2 implies that “inputValue” is a single byte variable with possible values limited to 0x00,
0x55, 0xAA and 0xFF.
NOTE 2 Since “inputValue” is a single byte variable, the instance will answer NO to “QUERY INPUT VALUE
LATCH”.
“inputValue” shall reflect the occupancy state in the area covered by the sensor, as shown in
Table 1.
Table 1 – Meaning of “inputValue”
“inputValue” Area state Movement
0x00 Vacant No
0x55 Vacant Yes
0xAA Occupied No
0xFF Occupied Yes
9.3.2 Input signal mapping for movement sensors
For movement sensors, the input signal shall directly map onto movement (only). The
instance shall change “inputValue” to 0xFF immediately if movement is detected, thus
reporting an occupied area state as well. See Figure 2.
A movement sensor shall support a hold timer, with timeout value T , which shall be
hold
(re)started each time movement is detected. A transition of “inputValue” to 0x00 shall only
take place at the moment the hold timer expires or is cancelled. In such a case the ‘vacant’
trigger shall be generated.
While the area is occupied, the “inputValue” shall change between 0xFF and 0xAA depending
on momentary movement detection only.

Movement based sensor
Vacant
0x55: Vacant and movement
Report
0x00: Vacant and no movement
timer
expired / State never reached
entry / (Re-)trigger report timer
'Repeat'
trigger
Hold timer expired or cancelled /
Movement detected /
'Vacant' trigger
'Movement' and 'Occupied' trigger

Occupied
Report
0xFF: Occupied and movement
timer
expired /
entry / (Re-)trigger report timer,
'Repeat'
(Re-)trigger hold timer
trigger
No movement detected / Movement detected /
'No movement' trigger 'Movement' trigger
Report
0xAA: Occupied and no movement timer
expired /
entry / (Re-)trigger report timer
'Repeat'
trigger
IEC
Figure 2 – State diagram for movement based sensor
NOTE 1 An input value of 0x55 is not applicable, since movement implies occupancy.
NOTE 2 Vacancy and occupancy can be concluded from “inputValue” only.

– 12 – IEC 62386-303:2017 © IEC 2017
9.3.3 Input signal mapping for presence sensors
Presence sensors shall report the movement state and area state as quickly as possible. If a
presence sensor is not able to detect motion, it shall report no movement. See Figure 3.
NOTE This means that the hold timer in a presence sensor will never be started.
Presence sensor
Report
Report
Occupancy detected /
timer
timer
0x55: Vacant and movement 'Occupied' trigger 0xFF: Occupied and movement
expired /
expired /
'Repeat'
'Repeat'
entry / (Re-)trigger report timer entry / (Re-)trigger report timer
trigger
trigger
Vacancy detected /
'Vacant' trigger
Movement detected / No movement detected / Movement detected / No movement detected /
'Movement' trigger 'No movement' trigger 'Movement' trigger 'No movement' trigger
Report
Report
Occupancy detected /
timer
timer
0x00: Vacant and no movement 'Occupied' trigger 0xAA: Occupied and no movement
expired /
expired /
'Repeat'
'Repeat'
entry / (Re-)trigger report timer entry / (Re-)trigger report timer
trigger
trigger
Vacancy detected /
'Vacant' trigger
IEC
Figure 3 – State diagram for presence sensor
9.4 Events
9.4.1 Priority use
9.4.1.1 General
The default “eventPriority” shall be priority 4. Since the application controller needs a timeslot
to respond, “eventPriority” should not be set to 2.
9.4.1.2 Periodic events
The periodic “INPUT NOTIFICATION” message to report the occupancy confirmation event
(still vacant or still occupied) shall always be sent with priority 5.
NOTE This makes “eventPriority” inapplicable for this event only.
9.4.2 Bus usage
9.4.2.1 Instance level
Multiple events from an instance shall not be sent in a transaction. There is a configurable
delay T that shall be taken into account. See 9.5.3 for more information.
deadtime
9.4.2.2 Device level
On device level, events from different instances may be sent in a transaction.
9.4.3 Encoding
Occupancy and vacancy events shall be encoded as shown in Table 2.
Table 2 – Occupancy and vacancy events
Event name Event information Description
No movement 00 0000 ---0b No movement detected. Corresponding trigger is the ‘No movement’
trigger.
Movement 00 0000 ---1b Movement detected. Corresponding trigger is the ‘Movement’ trigger.
Vacant 00 0000 -00-b The area has become vacant. Corresponding trigger is the ‘Vacant’ trigger.
Still vacant 00 0000 -10-b The area is still vacant. The event occurs at regular intervals as long as
the vacant condition holds. Corresponding trigger is the ‘Repeat’ trigger.
Occupied 00 0000 -01-b The area has become occupied. Corresponding trigger is the ‘Occupied’
trigger.
Still occupied 00 0000 -11-b The area is still occupied. The event occurs at regular intervals as long as
the occupied condition holds. Corresponding trigger is the ‘Repeat’ trigger.
Presence sensor 00 0000 0---b The current event is triggered by a presence based sensor.
Movement sensor 00 0000 1---b The current event is triggered by a movement based sensor.
1x xxxx xxxxb Reserved.
01 xxxx xxxxb
00 1xxx xxxxb
00 01xx xxxxb
00 001x xxxxb
00 0001 xxxxb
NOTE 1 In order to save bus bandwidth, the application controller has the possibility to inhibit event notifications
that it does not need, as is described in 9.4.4.
The event shall be reported in one “INPUT NOTIFICATION” by bitwise OR-ing the event
information values. In order to perform the OR-ing, every bit that is marked with “-“ for the
listed event names shall be assumed 0.
The information contained in bit 3 can be used by the application controller to determine
whether the sensor already applied a hold timer or not (movement based sensor).
NOTE 2 Every enabled event leads to a complete event, reporting both the movement and occupancy information.
9.4.4 Event configuration
The application controller may not need all the event triggers mentioned in 9.4.3. The
instance shall allow the application controller to set the “eventFilter” (see IEC 62386-
103:2014 and IEC 62386-103:2014/AMD1:—, 9.7.4) to inhibit those event triggers that the
application controller does not need. For this document, “eventFilter” shall be reduced to one
byte.
NOTE Inhibiting event triggers increases the effective bus bandwidth availability.
The “eventFilter” shall have the definition as given in Table 3:

– 14 – IEC 62386-303:2017 © IEC 2017
Table 3 – Event filter
Bit Description Value Default
0 Occupied event enabled? "1" = "Yes" 1
1 Vacant event enabled? "1" = "Yes" 1
2 Repeat event enabled? "1" = "Yes" 0
3 Movement event enabled? "1" = "Yes" 0
4 No movement event enabled? "1" = "Yes" 0
5 Reserved 0 0
6 Reserved 0 0
7 Reserved 0 0
The filter can be set via “SET EVENT FILTER (DTR0)” and be queried using
“QUERY EVENT FILTER 0-7”, see IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—
for details.
If the ‘repeat’ event is enabled, on expiration of the report timer the ‘still vacant’ event shall be
sent if the ‘vacant’ event is enabled, and the ‘v still occupied’ event shall be sent if the
‘occupied’ event is enabled.
9.4.5 Event generation
An event shall be generated on every change of “inputValue” or when the report timer expires.
In case a new event occurs before the current event is being sent, the new event shall replace
the current event. This could be caused for example by bus unavailability or the deadtime
timer.
9.4.6 Movement trigger and catching
The event filter can be adjusted to enable or disable the ‘movement’ event. Care should be
taken when enabling the ‘movement’ event, as it is likely to flood the bus.
If the movement event is disabled the application controller can explicitly ask for the event to
be sent once (setting “catching”), using the command “CATCH MOVEMENT”. Each “INPUT
NOTIFICATION” shall clear “catching”, which implies that “CATCH MOVEMENT” is a single-
notification request. The instruction shall not change the event filter.
If the movement event is enabled the “CATCH MOVEMENT” instruction shall be ignored.
NOTE Another “CATCH MOVEMENT” has no effect if a command has not (yet) led to a notification.
The query “QUERY CATCHING” can be used to verify that no movement notification has been
sent yet (“catching” has been set).
9.5 Configuring the input device
9.5.1 Using the hold timer
The hold timer is only implemented for movement based sensors. The model in Figure 2
shows how the hold timer is used to derive occupancy.
The hold timer can be cancelled using “CANCEL HOLD TIMER”. This forces a transition to the
vacant state.
Both cancellation of the hold timer and expiration of the hold timer shall generate a ’vacant’
trigger.
9.5.2 Using the report timer
If the report timer is set, it shall generate a ‘repeat’ trigger every T even if the “inputValue”
report
has not changed. The report timer shall be restarted every time an event is sent.
If multiple devices have the report timer enabled, they might send out conflicting data
controlling the same control gear. Depending on the application, care needs to be taken when
enabling the report timer.
9.5.3 Using the deadtime timer
If the deadtime timer is set, the instance shall not send out an event until the deadtime timer
has expired. The deadtime timer shall be restarted every time an event is sent.
NOTE The purpose of the deadtime timer is to increase the effective bus bandwidth availability. It is not intended
to be used as a hold timer.
9.5.4 Setting the timers
Event timers shall be programmable as is indicated in Table 4. The time can be calculated as
follows:
Time = T * multiplier
incr
Only on (re-)starting a timer the actual time shall be calculated based on the corresponding
variable. This implies that the times only change after any running timer has been retriggered,
cancelled or expired. The tolerance on the time shall be ±5 %.
Table 4 – Event timer setting
Time Multiplier Default value T T T T
incr default min max
T “tDeadtime” 2 50 ms 100 ms 0 s 12,75 s
deadtime
a
T “tHold” 90 10 s 15 min 1 s 42,3 min
hold
T “tReport”
20 1 s 20 s 1 s 4 min 15 s
report
a
Only applicable for movement based sensors.

The input device shall expose the following operations to set and observe the timer
multipliers:
• “SET HOLD TIMER (DTR0)”, “QUERY HOLD TIMER” to set or query “tHold”;
• “SET REPORT TIMER (DTR0)”, “QUERY REPORT TIMER” to set or query “tReport”;
• “SET DEADTIME TIMER (DTR0)”, “QUERY DEADTIME TIMER” to set or query “tDeadtime”.
“QUERY HOLD TIMER” shall answer MASK if the hold timer is not implemented, “tHold” if it is
implemented.
If the hold timer is implemented, “SET HOLD TIMER (DTR0)” shall set “tHold” to “DTR0”
unless “DTR0” equals MASK in which case the command shall be ignored. The minimum time
in case “tHold” equals 0 shall be 1 s.
“SET REPORT TIMER (DTR0)” shall set “tReport” depending on “DTR0“. If “tReport” is set to 0,
the report timer shall be disabled.

– 16 – IEC 62386-303:2017 © IEC 2017
“SET DEADTIME TIMER (DTR0)” shall set “tDeadtime” depending on “DTR0”. If “tDeadtime” is
set to 0, the deadtime timer shall be disabled.
If T < T , T shall be T (independent of the value of “tReport”).
report deadtime report deadtime
9.5.5 Manual configuration
If IEC 62386-333 is implemented, the instance level variables according to Table 5 may be
manually configured. QUERY MANUAL CONFIGURATION CAPABILITY 3xx (see
IEC 62386-333) shall return the byte as defined in Table 5:
Table 5 – “manualCapabilityInstance3xx” values
Bit Description Value
0 Manual configuration of “tReport” supported “1” = “Yes”
1 Manual configuration of “tHold” supported “1” = “Yes”
2 Manual configuration of “tDeadtime” supported “1” = “Yes”
3 Reserved “0”
4 Reserved “0”
5 Reserved “0”
6 Reserved “0”
7 Reserved “0”
9.6 Exception handling
9.6.1 Physical sensor failure
If a physical sensor failure is detected, the instance shall set “instanceError” to TRUE, from
the moment the failure is detected until the failure is resolved. While the error is detected, no
further events shall be sent.
9.6.2 Manufacturer specific errors
If a manufacturer specific error other than physical sensor failure is detected, the instance
shall set “instanceError” to TRUE, from the moment the error occurs until the error is gone.
9.6.3 Error value
“instanceError” can be observed via “QUERY INSTANCE STATUS”.
While “instanceError” is set, “QUERY INSTANCE ERROR” shall return “instanceErrorByte”
according to Table 6.
Table 6 – “instanceErrorByte” values
Bit Description Value
0 Physical sensor failure? "1" = "Yes"
1 Reserved “0”
2 Reserved “0”
3 Reserved “0”
4 Manufacturer specific error 1? "1" = "Yes"
5 Manufacturer specific error 2? "1" = "Yes"
6 Manufacturer specific error 3? "1" = "Yes"
7 Manufacturer specific error 4? “1” = “Yes”

If used, the meaning of bits [7:4] of “instanceErrorByte” shall be documented in the
manual/documentation. The impact on event generation shall also be documented.
10 Declaration of variables
The requirements of IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—, Clause 10
apply, with the following considerations.
Table 7 shows additions to the device variables.
Table 7 – Declaration of device variables
Variable Default value Reset value Power on value Range of Memory type
(factory) validity
“extendedVersion
2.0 no change no change 00001000b ROM
Number”
Table 8 shows restrictions to the instance variables.
Table 8 – Restrictions to instance variables defined
in IEC 62386-103:2014 and IEC 62386-103:2014/AMD1:—
Variable Default value Reset value Power on value Range of validity Memory type
(factory)
“instanceType”
3 no change no change 3 ROM
“resolution” 2 no change no change 2 ROM
a
b
“inputValue” no change no change 0x00, 0x55, RAM
0xAA,0xFF
“eventFilter” 0000 0011b 0000 0011b no change 000x xxxxb NVM
“eventPriority”
4 4 no change [2,5] NVM
a
Not applicable.
b
The value should reflect the actual situation as soon as possible.

Table 9 shows additions to the instance variables.

– 18 – IEC 62386-303:2017 © IEC 2017
Table 9 – Declaration of instance variables
Variable Default value Reset value Power on value Range of validity Memory type
(factory)
a
b
“instanceErrorByte no change 0 xxxx 000xb RAM
”
“tDeadtime” 2 2 no change [0,255] NVM
c
“tHold” 90 90 no change [0,254] NVM
“tReport” 20 20 no change [0,255] NVM
a
“catching” FALSE FALSE [
...