1. OSID by Xtralis How To Perform An Effective OSID Demonstration

2. Objective The purpose of this presentation is to show how to set up and conduct an effective OSID Demonstration. This is meant to be a guide to review in preparation for OSID presentations to:  Channel Partners  System Integrators  Consultants and Engineers  End Users

3. Content  OSID demo kit  Required items  Physical set-up  Using OSID Diagnostic Tool  Demo using OSID Diagnostic tool  Special requests  What to do in real smoke tests

4. OSID Demo Kit Part No. VKT-301 Demo Kit, consists of the following:  1 x OSI-90, imager 90°  2 x OSE-SPW, emitter standard power wired  2 x 9 VDC alkaline batteries wired in OSE-SPW  3 x support for imager and emitters  Alignment laser screw driver  Alarm Filter  FTDI cable  Alignment aid reflector  Cleaning cloth  Philips screwdriver  Robust carry case  Extra space for Talcum powder container, spare batteries, screwdriver …  OSID Diagnostic tool (downloadable from OSID website)

5. Required items OSI-90 OSE-SPW x 2 Support x3 Active USB extender (optional) FTDI cable Talcum powder Filter 50% Laptop PC or other

6.  Ideally put OSI-90 in a corner  Use 2 or 3 x OSE-SPW or OSE-SP  Show 3-D feature  Install OSE-SP(W) within the 80° FOV of the imager and respect minimum and maximum distances  If distance is shorter than 6 m (20 ft) use decals to reduce power  Install OSE-SP(W) at different heights  Demonstrate ‘rough’ alignment  Point out that OSID does not need power to align and set up, as opposite to (some) other beams! Physical Setup

7. 80° max Max 30 m (98 ft) Max 34 m (111 ft) Top view Min 6 m (20 ft)

8.  Connect FTDI cable between imager and PC  If > 1.5 m is required, use active USB extension cable(s)  Max total distance Imager-PC is 30 m  Start OSID Diagnostic tool  If PC does not find the imager, start FTDI driver separately with the Imager connected to the PC  You are now ready to start Physical Setup

9. Using OSID Diagnostic Tool Example with 2 emitters

10. Connecting to PC  View of OSID Diagnostic tool connected to an imager with early hardware and/or software  Exchange imager or contact Xtralis Support

11. OSID Diagnostic tool Firmware upgrade  If OSID Diagnostic tool version and Firmware version are incompatible the program will propose to upgrade  Proceed with the upgrade, follow instructions on screen

12. OSID Diagnostic tool Firmware upgrade  Proceed with the upgrade, follow instructions on screen  Password: 1413

13. OSID Diagnostic tool Firmware upgrade  When cycling the power (switching power off and on again) make sure that both the 24 Vdc and the USB connection are disconnected  Upgrade by using the USB connection, re-connect 24 Vdc after upgrading

14. OSID Diagnostic tool Firmware upgrade  Upgrading process evolution

15. Start up screen (after upgrade)

16. Initialization screens – view from imager  Depending on the number of emitters, the Training Mode will take between 3 to 7 minutes  During this ‘long’ period, - show what the Imager sees  Explain the difference between a CMOS imaging chip/CCD camera i.e. ‘what the imager is seeing’ and a simple photo receiver  1 photocell versus several 100.000 pixels Photo cell CCD camera Simplistically put…. Click on camera icon

17. Continuing Initialization  When there are reflective surfaces in the demo room ; shiny surfaces, windows, mirrors, you can initially have many candidates (10+) – do not worry, you’re lucky!  Explain the process how OSID will eliminate reflected candidates with same signature/code but less energy.  You will end up with the exact amount of emitters that are really in the room

18. Initialization finalized  The image will now show the location of the various emitters with a green icon and a number  Numbering of the emitters is from left to right from the position of the imager  If any faults now occur, the Emitter icon(s) will be yellow. Type of fault will show top right of screen and next to the Emitter # n location  For demo purposes, a fault can be forced by blocking the beam  For a new image click ‘Acquire’ button, the image does not refresh automatically  Now you are OK to demo Imager alignment could have been better ! Fault descriptions, if any

19. Fault codes - General  All dip switches are default set to ‘0’  When changing any dip switch setting(s), the system must be recommissioned by disconnecting power to the Imager for at least 10 seconds.  The USB FTDI jack plug cable must also be disconnected as this cable provides power to the Imager via the computer USB port.

20. Fault code - System – DIP Switch config bad  DIP switches are set incorrectly (alarm level is not set, number of Emitter(s) are not set, more than one Emitter is set for an OSID 10 degree Imager)

21. Fault codes – Number of emitters  Too few Emitter(s) found compared to the configured number set using the DIP switches  Too many Emitter(s) found compared to the configured number set using the DIP switches

22. Fault code - Imager Saturation or Incorrect Emitter Power  When the Emitter(s) are installed at distances closer than those specified in OSID Product Guide

23. Fault code - System – Signal too Low and Emitter at edge of field  When the Emitter(s) are incorrectly aligned or installed at distances further than those specified in OSID Product Guide  When Emitter(s) are commissioned such that they are just within the field of view of the Imager and not in an acceptable position.  The picture screenshot will confirm the emitter(s) incorrect location

24. Fault codes - Alignment drift  When the installed Emitter(s) have physically shifted through severe building movement, poor mounting or external displacement forces  When the installed Imager has physically drifted through severe building movement, poor mounting or external displacement forces

25. Fault codes - Object intrusion and Emitter obscured  Occurs when there are blockage(s) of the light beam between the Emitter and the Imager that are not smoke types that are sustained for a short period and cause a large (almost total) attenuation. An Imager or Emitter severely displaced with misalignments larger than the tolerated amount as specified in OSID Product Guide may also cause an object intrusion fault.  Occurs when there are blockage(s) of the light beam between the Emitter and the Imager that are not smoke types, sustained for a certain period and cause a medium attenuation

26. Fault code - Reference Level drifted low/high  When the signal received by the Imager has reduced to a level that is deemed unacceptable due to build up of dust on front window surfaces of an Imager or Emitter installed for a long time period  To resolve a reference level drifted low problem, the front windows of the Imager and Emitters need to be wiped clean with a damp non-scratching cloth  A reference level drifted high problem can occur if an emitter was poorly aligned and the alignment gets better through building movement. Alternatively if a system gets commissioned in a dusty and dirty environment and the dust drops one can expect this ‘high’ fault. In dusty environments the initialisation should b e done when the dust levels are low.

27. Fault code - Reference Level not set  Upon setting the reference level, if there are occasional obstructions, the Imager will not set the levels.  Imager looks for 50 consecutive pulses that are not interrupted to obtain as accurate a sample of the reference as possible as this is used for all measurements going forward. Very exceptional fault

28. Fault code – Imager card version conflict  This can happen if the imager card is pulled out of socket; i.e. if an imager gets dropped while out of its protective box Very exceptional fault

29. Local Disk (C:) SunshineLog 20110913.dat Creating log files  A data log file,’date’.dat, is created automatically in the C: directory when OSID Diagnostics is started up  The program takes 2 data samples per second  Data can be analyzed by Xtralis support engineers  File size can depending on the configuration be several 100 Mb/day

30. Demo OSID using OSID Diagnostic tool

31. Controls Choose event log location Shows event list Log on/off Save system configuration Firmware upgrade System restart/re-initialization Reset alarm relay (if Alarm Latched was chosen) Mute alarm buzzer

32. OSID Diagnostic tool screenshots  This screen shows all emitter signals at the same time  This not ideal for demo’s as the ‘action’ is harder to follow  Using a single emitter graph shows a clear distinction between the IR and the UV signal  This very important as the difference between UV and IR signals is key to the nuisance alarm free operation of OSID!  With this screen on you can now start your live demo Click on graph icon Time line % Attenuation Select an emitter Select Scroll option Select Scroll width

33. What to demo?  Basic demo includes  Alarm using the filter  Object intrusion  ‘WOW’ demo includes  Spider simulation  Dust - talcum powder  Vibration  Building movement  Water spray if possible  Special requests  Glass  Plastic bags, ….

34. Smoke alarm  A Filter is included in the demo kit  3 rd party filters might alarm – but don’t bank on it  The filter will highlight the alarm mechanism  I.e., the larger the difference between IR and UV the faster the alarm will be accepted and detected  There is always more UV than IR signal  UV detects smaller particles than IR  The detector will remain in alarm for a short while after the alarm is gone (hysteresis)

35. Smoke alarm  Canned spray used for photo-electric spot/point detectors will not generate an alarm  In most cases some ‘noise’ will be detected  Smoke pellets/fogger  If customers wants to use smoke pellets or foggers, etc make sure that existing smoke alarms (spots or other) are isolated  Make customer aware that an alarm is not guaranteed!  You will only have an alarm if the generated smoke or fog behaves like true smoke i.e. enough differentiation between UV and IR. The graphs will clearly show

36. Object intrusion  IR and UV are both fully obscured. IR signal ‘hidden’ behind UV. UV or IR is selectable  Fault signal but no alarm  Obscuration needs to last, around 9 sec for 3+ emitters and around 30 sec for a single emitter, to have a fault signal  When obscuration is removed signal will drop back to normal

37. Spider simulation  Make (or tame!) a spider Bits of string work well  Wave it around in front of the Imager lens  You will get ‘spikes’  Alarm should not occur.  Competitive beams are easily put in alarm like this as they ‘average’ out the IR signals at and over the sensitivity level

38. Reflected light  Use torch lamp, camera flash, laser screw driver, laser pointer,…  Shine into the imager from a distance  You should register no change and no faults  You can bring the light source close(r) to the imager provided you do not ‘blind’ the imager. Watch the graphs  With the light source on you can demo an alarm with the filter

39. Dust simulation  Blow/spray talcum powder in the beam path – but test first  You will need ‘a lot’ to get to some reasonable peak  There will be no alarm  Invite customer to have a go – fun but messy !

40. Vibration  Insert the laser screwdriver in any emitter as if you were aligning it.  With the laser turned on, gently tap the support to which the emitter is fastened  The laser spot will make figures similar to lissajou figures  The graph will show just some noise, no alarm nor fault  Traditional beams do not ‘like’ such treatment….

41. Building movement  Make sure the Large Particle Alarm (Dust rejection) Dip sw. 7 is set to “on”  Insert the laser screwdriver in any emitter as if you were aligning it.  With the laser turned on, rotate the emitter +/- 1° out of its normal alignment in one direction  Wait 30s and give it another 1° and so on until about 5 °  You will see a ‘step function’ as in this graph  Stop at 5 °. Point made!

42. Building movement - continued  Explain that the action in previous slide 1°/ 30 sec does not represent true building movement  OSID will compensate for slow building movement like in real life when the sun heats up a building and causes the walls to flex  Slow movement 0.1°/30 sec gives this graph

43. Water spray  Spray fine water droplets in front of the imager in the beam path  It is not a problem if some of the droplets hit the imager (see picture)  The result is similar to dust – no alarm  BUT – keep an eye on the UV & IR trend

44. Special requests Customers tend to get really excited and may come up with requests of their own. If you are forced to take up the ‘challenge’ and it is one that was never tried before make sure you are prepared for the possible outcome. OSID is not immune to every possible test  A typical request is putting a glass pane in the beam path  ‘Standard’ glass will not alarm and may create a fault (object intrusion) – no issue to explain here  Leave the glass and re-start with the glass in front. OSID should start up without faults and operate normal – what a great product!  Another typical request is putting a plastic bag in the beam path  Try to avoid this one. Many plastic bags have a different effect on UV than on IR. It is very likely you will get an alarm!

45. What to do with real smoke?  Sometimes you may have the opportunity to demo real smoke  If so make sure that existing smoke alarms (spots or other) are isolated, management is aware and consenting  Make sure the local fire brigade (if existing) is present and supporting the demo  Make sure extinguishing equipment is at hand and operational  Save the Sunshine logs for PD purposes. Note maximum of info about the site (dimensions, etc), firmware version, serial numbers etc

46. Good luck….

47. End