BS EN IEC 62386-104:2019
$198.66
Digital addressable lighting interface – General requirements. Wireless and alternative wired system components
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 58 |
The IEC 62386 series specifies a bus system for control by digital signals of electronic lighting equipment. This part of IEC 62386 applies to a system with wireless or alternative wired communication between its units, instead of a wired bus system, where the meaning of “wireless or alternative wired communication”, or in short “telecommunication”, is any type of communication network different from the wired system described in IEC 62386-101.
Where the electronic lighting equipment is covered by the scope of IEC 61347 (all parts), it is in line with the requirements of IEC 61347 (all parts), with the addition of DC supplies.
NOTE the definition of “telecommunication” applies only to this document and differs from the IEC Electropedia term in IEC 60050-701:1988, 701-01-05.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | National foreword |
| 5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
| 7 | English CONTENTS |
| 11 | FOREWORD |
| 13 | INTRODUCTION Figures Figure 1 – IEC 62386 graphical overview |
| 15 | 1 Scope 2 Normative references 3 Terms and definitions |
| 16 | 4 General 4.1 Purpose |
| 17 | 4.2 Version number 4.3 System structure and architecture Tables Table 1 – System components |
| 18 | 4.4 System information flow Figure 2 – Telecommunication system structure example |
| 19 | 4.5 Command types 4.6 Telecommunication units 4.6.1 General 4.6.2 Telecommunication transmitters and receivers in telecommunication units Figure 3 – Example of communication between telecommunication units |
| 20 | 4.6.3 Control gear 4.6.4 Input device Table 2 – Transmitters and receivers in telecommunication units |
| 21 | 4.6.5 Single master application controller 4.6.6 Multi-master application controller 4.6.7 Sharing an telecommunication interface 4.7 Power interruptions at telecommunication units |
| 22 | 5 Electrical specification 6 Telecommunication unit power supply Figure 4 – Start up timing example Table 3 – Start-up timing Table 4 – Power on timing |
| 23 | 7 Transmission protocol structure 7.1 General 7.1.1 Frame types 7.1.2 Transaction type 7.1.3 Source address Table 5 – Telecommunication frame types |
| 24 | 7.2 Control gear forward frame 7.2.1 General 7.2.2 Frame format (control gear forward frame) 7.2.3 Payload (control gear forward frame) 7.3 Control gear backward frame 7.3.1 General Table 6 – Control gear forward frame Table 7 – Control gear backward frame |
| 25 | 7.3.2 Frame format (control gear backward frame) 7.3.3 Payload (control gear backward frame) |
| 26 | 7.4 Control device forward frame 7.4.1 General 7.4.2 Frame format (control device forward frame) 7.4.3 Payload (control device forward frame) Table 8 – Control device forward frame |
| 27 | 7.5 Control device backward frame 7.5.1 General 7.5.2 Frame format (control device backward frame) 7.5.3 Payload (control device backward frame) Table 9 – Control device backward frame |
| 28 | 7.6 32-bit forward frame 7.6.1 General 7.6.2 Frame format (32-bit forward frame) 7.6.3 Payload (32-bit forward frame) Table 10 – 32-bit forward frame |
| 29 | 7.7 32-bit reply frame 7.7.1 General 7.7.2 Frame format (32-bit reply frame) 7.7.3 Payload (32-bit reply frame) 8 Timing 9 Method of operation 9.1 Dealing with frames and commands Table 11 – 32-bit reply frame |
| 30 | 9.2 Collision avoidance, collision detection and collision recovery 9.3 Transactions 9.3.1 General 9.3.2 Transactions of forward frames 9.3.3 Transactions of backward frames 9.4 Send-twice forward frames and send-twice commands 9.5 Command iteration |
| 31 | 9.6 Usage of a shared interface 9.6.1 General 9.6.2 Backward frames 9.6.3 Forward frames 9.7 Addressing 9.8 Frame decoding and command execution 9.8.1 General |
| 32 | 9.8.2 Decoding and execution of control gear forward frames 9.8.3 Decoding of control gear backward frames 9.8.4 Decoding and execution of control device forward frames |
| 33 | 9.8.5 Decoding of control device backward frames 9.8.6 Decoding and execution of 32-bit forward frames 9.8.7 Decoding and execution of 32-bit backward frames 9.9 System failure 10 Declaration of variables |
| 34 | 11 Definition of commands 11.1 Additional commands for telecommunication control gear 11.2 Additional commands for telecommunication control devices Table 12 – Declaration of variables Table 13 – Additional commands for telecommunication control gear Table 14 – Additional commands for telecommunication control devices |
| 35 | 11.3 Configuration instructions 11.3.1 General 11.3.2 SET POWER ON DELAY (DTR0) (telecommunication control gear only) 11.4 Queries 11.5 Special commands 11.5.1 QUERY SYSTEM ADDRESS |
| 36 | 11.5.2 PROGRAM SYSTEM ADDRESS (data) 11.5.3 DELAY SYSTEM FAILURE (data) |
| 37 | Annex A (informative) Examples of telecommunication frames A.1 Control gear forward frames Table A.1 – Example of control gear forward frame |
| 38 | A.2 Control gear backward frames Table A.2 – Examples of control gear backward frames |
| 39 | A.3 Control device forward frames Table A.3 – Example of control device forward frame |
| 40 | A.4 Control device backward frames Table A.4 – Example of control device backward frame Table A.5 – Example of control device backward frame (continued) |
| 41 | Table A.6 – Example of control device backward frame Table A.7 – Example of control device backward frame (continued) |
| 43 | Annex B (normative)Underlying telecommunication protocols B.1 General B.2 Bluetooth® Mesh B.2.1 Overview B.2.2 System addresses B.2.3 Transactions and frames |
| 44 | B.2.4 Hardware address B.2.5 Receive signal strength indicator (RSSI) B.2.6 System failure B.3 VEmesh™ B.3.1 Overview B.3.2 System addresses |
| 45 | B.3.3 Transactions and frames B.3.4 Address allocation B.3.5 Receive signal strength indicator (RSSI) B.3.6 System failure detection B.4 Distributed PLC bus (DPB) B.4.1 Overview B.4.2 System addresses |
| 46 | B.4.3 Transactions and frames B.4.4 Hardware address B.5 User datagram protocol (UDP) B.5.1 Overview B.5.2 UDP port number |
| 47 | B.5.3 Forward data packet structure B.5.4 Backward data packet structure Table B.1 – UDP forward data packet Table B.2 – UDP backward data packet |
| 48 | B.5.5 Simple acknowledgement packet structure Table B.3 – ADU error codes Table B.4 – UDP simple acknowledge packet |
| 49 | B.5.6 System addresses B.5.7 Transactions and frames B.5.8 Hardware address B.5.9 System failure |
| 50 | B.5.10 Security |
| 51 | Annex C (informative)Example of address allocation C.1 Overview C.2 Discover all used system addresses C.3 Allocate short addresses |
| 53 | Annex D (informative)Examples of telecommunication system architectures D.1 Single application controller D.2 Multiple application controllers Figure D.1 – Example of a telecommunication system with a single application controller and control gear |
| 54 | D.3 Multiple subnets Figure D.2 – Example of an architecture with multiple application controllers |
| 55 | Figure D.3 – Example of an architecture with multiple subnets |
| 56 | Bibliography |
