Architectural Review Emergency Lighting Systems

1. Architectural Review
Emergency Lighting
Systems

2. Monitored Emergency Lights… a growing trend
 Safety
 Security
 Litigation
 Government requirement
2

3. Monitored Emergency Lights… a growing trend
 Stanilite - Australia ( Thomas and Betts) 12 years
 Clevertronics - Australia - 4 years
 White Lite – Australia - 4 years
 Hocen - China – 1 year
 Chinese customer number 2 – In development
3

4. Business rationale
 In many countries Emergency Lighting & Exits Signs
require testing of the Bulb (to see if it is working) and the
Battery (must be able to light the Emergency Light / Exit
Sign for 90 minutes)
 Typically test every 6 months. (This is part of
AS/NZS2293.3. for example in Australia)
 Monitored Emergency Lighting & Exits Signs system is
normally installed in buildings which require more than 100
Emergency Lighting / Exits Signs.
4

5. Typical Product Line supported
 Emergency Lights & Exit Signs.
5

6. What should I use for my network ?
 Wired solution
 RF
 Powerline
6

7. Preferred Architecture
 Use LonWorks PL to connect to the Monitored Emergency
Lights & Exit Signs,
 Use Twisted Pair ( TP) as backbone
 The use of PL greatly reduces need for wiring cost and
lowest installation time and cost
 Better security of power cables than signal cables
 High data rates are not required
 Price performance of transceivers
7

8. Typical Lonworks Architecture
 LonWorks Power Line to the Emergency Lights & Exit Signs.
 LonWorks Twisted Pair (FT10) as a Backbone. Use 3-phase
PL to FT-10 Routers to pass information from one level to
the next. Generally one per each floor of a building.
 Smart Server, to gather all data in the system and send to
corporate MIS system
8

9. Typical LonWorks Architecture
9

10. Benefits of PL for Emergency lighting
 No new wires …. Simplified installation
 If the lights work, the network does too
 Can have large networks and bandwidth fine as appliaction
is not speed intensive
10

11. Questions….
 What are the local requirements ?
 What do I need to get started ?
11

12. Echelon Products Required
 Development
Product Part Number
NodeBuilder 3.1 10020-31-273
Power Line DSK 17050R-20-272
LNS Application Developer's Kit/Turbo Edition 34309
LNS Redistribution Kit/Turbo Edition 34312
Echelon Software License Generator/Turbo 34311
Edition
PLCA-22 Power Line Analyzer 58022-3
LonScanner Protocol Analyzer 33110-301
12

13. Echelon Products Required
 Production
Product Part Usage
Number
PL-3120 Smart Transceiver 15311R-1000 Communication to Emergency Light /
Exit Sign
FT-3120 Smart Transceiver 14212R-500 Communication to Emergency Light /
Exit Sign
PL-3150 Smart Transceiver 15321R-960 Router
FT-3150 Smart Transceiver 14230R-450 Router
Router IP Firmware Router
FT-10 PCLTA-21 74501R PC Internet Server Network Interface
U10 FT-10 USB Network Interfaces 75010R PC Internet Server Network Interface
U20 PL USB Network Interfaces 75021 PC Internet Server Network Interface
i.LON 100e3 72101-300 Internet Server
LNS Server License Network Management
LNS Administrator Device Credit 34410 Network Management
13