LT6149 Rev 12May 201834The Device Simulator allows you to easily simulate sensor and module behaviour when testing or developing a fire alarm system It reduces the costs associated with the use of ph ID: 870942
Download Pdf The PPT/PDF document "Contents10Introduction 411Required Hardw..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1 LT-6149 Rev. 1.2May 2018 3 Contents1.0In
LT-6149 Rev. 1.2May 2018 3 Contents1.0Introduction 41.1Required Hardware ........................................................................................................ 1.2Components ................................................................................................................... 2.0Connections 42.1Ethernet ......................................................................................................................... 2.2USB ................................................................................................................................ 2.3Power the Hub ..............................................................................................................2.4Port 1 ............................................................................................................................. 2.5Power the Port .........................................................
2 ........................................
...................................................... 2.6Switches and LEDs ........................................................................................................ 3.0Web Interface 73.1Getting Started ............................................................................................................... 3.2Uploading a Configuration File ....................................................................................... 3.3Monitoring and Changing Device States ........................................................................ 4.0Configuration File 124.1Info ................................................................................................................................. 4.2Sensors and Modules .................................................................................................... 4.3Switches ....................................................................
3 ........................................
..................................................... 4.4LEDs .............................................................................................................................. 4.5Events ............................................................................................................................ 5.0Network Card Settings on Windows7 186.0Troubleshooting 226.1Configure the Device Simulators IP Information ........................................................... 7.0 Supported Devices 237.1Sensors .......................................................................................................................... 7.2Modules ......................................................................................................................... 8.0Sample Configuration File 288.11 Sensor and 1 Module ..........................................................................................
4 ........ 9.0Electrical Specifications 29
........ 9.0Electrical Specifications 2910.0Warranty and Warning Information 30 4 The Device Simulator allows you to easily simulate sensor and module behaviour when testing or developing a fire alarm system. It reduces the costs associated with the use of physical devices and allows for more test scenarios to be run.1.1Required HardwareIn order to configure and use the Device Simulator the following hardware is required:ComputerEthernet cableUSB cable (optional)12-24V DC Power Supply (optional)1.2ComponentsFigure 1Device Simulator frontFigure 2Device Table 1 Components Picture SIMU-MGC-11 Loop Device SimulatorIncludes power supply and Ethernet cable Unused USBPort 1 Port 1 Unused Hub Power Connections 2.1EthernetThe Ethernet connection is for configuration by a computer. See section 3.0on page7.2.2USBUse the USB port for power (section 2.3) or troubleshooting (section 6.0).2.3Power the HubThe hub runs the web interfa
5 ce that lets you configure the Device Si
ce that lets you configure the Device Simulator. You must power both the hub and the port in order to access the web interface and configure the simulated After the Device Simulator is configured, the fire alarm control panel powers the port, and the hub does not require power.There are 3 ways to power the hub.Terminal block - for 12-30 VDC power. Use either pair of terminals.Power barrel - for 12-30 VDC power.Figure 3Terminal block and power barrel2.4Port 1Port 1 in Figure2 is a loop simulator. Connect this port to a device loop on a fire alarm control panel. Use only one of the power options at a time. Ground +24V Power terminal Power barrel i Connections 2.5Power the PortDuring normal operation, the fire alarm control panel powers the port.While you are configuring the Device Simulator, power the port in one of two ways:from the physical loop on the fire alarm control panel, orfrom the power terminal block as shown
6 in Figure4.Figure 4Powering the port fr
in Figure4.Figure 4Powering the port from the power terminal block during configuration2.6Switches and LEDsThe 2 switches and 4 programmable LEDs are numbered as shown in Figure5.Figure 5Switch and LED numbersThe switches let you simulate events on the device loop (for example, sensor goes into alarm or trouble). 12 24 VDC 0 V sw1 sw2 7 Web Interface3.1Getting Started1.See section 5.0on page18 for instructions on configuring your computers network to connect to the Device Simulator.2.Open Chrome, type 192.168.10.128 in the address bar, and then press Enter.The Device Simulator main page appears.Figure 6Device Simulator main page If you cannot access the web interface, see section 6.0.Table 2 Web page menu description Menu Name DescriptionHomeHome page.DatabaseShows the current status of the port and the version of its database.ConfigShows the current configuration file or lets you upload a new one.MonitorAllows you
7 to monitor the current state of the devi
to monitor the current state of the devices.DiagnosticsFor factory use only.ScriptsYou can type in scripts to be executed on the Device Simulator.FirmwareShows the current status of the port and which firmware version it is running.SetupDevice Simulator network settings.DebugFor factory use only. i Web Interface 3.2Uploading a Configuration FileCheck the ports status1.Click Databaserow, the Status must show Mircom CRAB Database and the Port Statemust be OnlineIf the port is not online, check the power to the port (section 2.5).Figure 7Database pageUpload a configuration file1.Click ConfigFigure 8Config page2.Select menu.3.Click , then navigate to the configuration file.4.Click Web Interface The contents of the configuration file appear in the middle of the window.Figure 9Config page showing configuration file5.Click If there are no errors, a summary of the configured devices appears at the bottom of the window.Figur
8 e 10Config page showing summarySee the c
e 10Config page showing summarySee the current configuration file1.Click 2.Click The currently loaded configuration file appears. Web Interface Edit the current configuration file1.Click Config2.Click The currently loaded configuration file appears.3.Make changes to the configuration file.4.Click Write5.Click If there are no errors, a summary of the configured devices appears at the bottom of the window.Erase the current configuration file1.Click Config2.Click The currently loaded configuration file is erased. The port is now unconfigured.3.3Monitoring and Changing Device StatesUse the Monitor tab to monitor and change the status of the devices.The Monitor tab shows sensors and modules separately. Use the Device type menu to switch between sensors and modules.Figure 11Monitor tab showing sensorsFigure 12Monitor tab showing modules Web Interface Change the state of devices1.Select either Sensor or ModuleDevice type menu
9 .2.Click the checkboxes to select the de
.2.Click the checkboxes to select the devices whose state you want to change.3.Select a value in the Alarm or Trouble menu. This number must be either zero or one of the allowable values for the state. Section 7.0 lists the allowable values for each device.4.Click The display changes to show the current state of the devices.Figure 13Monitor tab showing 1 sensor in alarmFor example, assume that the sensor at address 1 in Figure13 is a 2251B. To put this sensor into alarm, select the sensor, then select 1, 2, or 3 in the Alarm menu, then click To put it into trouble, select 1 in the Trouble menu.To put the sensor back into its normal state, select 0 in the menu and 0 in the Troublemenu. 12 The configuration file must be in JSON format (http://json.org/). The easiest way to create a configuration file is to edit the example file in section 8.0.Each sensor, module, and switch is an object consisting of key-value pairs. Th
10 e entire script must begin and end with
e entire script must begin and end with curly brackets { }.4.1Info"info": {"author" : "Bob","tag" : "full_photo_monitor", "desc" : "Fully loaded loop (photo + monitor)", "version" : [0, 1, 0]: The files author.: A short description of the configuration.: A full description of the configuration.: The version of the configuration.4.2Sensors and ModulesDevices can be either sensors or modules. Section 7.0 lists the supported devices.In the following example, the sensor 2251B has address 1 and is associated with LED 1. The module M500M has address 1 and is associated with LED 3. Both devices are connected."sensor" : { "rem" : "Photo 1","model" : "2251B","enabled" : true,"ledno" : 1,"addr" : [ 1 ]"module" : { "rem" : "Input Module 1","model" : "M500M","enabled" : true,"ledno" : 3,"addr" : [ 1 ] or : This value must be or depending on the device in the line. For example if the model is 2251B, then the value must be . If
11 the model is M500M, then the value must
the model is M500M, then the value must be Configuration File This value is a reminder for you. It can be anything.: This value must be one of the models listed in section 7.0.: The device is connected.: The device is not connected. The fire alarm control panel will report it as missing.: The LED number associated with the device (optional). This LED will follow the : The devices address. You can enter more than one address, separated by commas, to simulate more than one device. For example, the following lines simulate 5 2251B sensors with the addresses 11, 12, 13, 14, and 15."addr" : [ 11, 12, 13, 14, 15 ]4.3SwitchesThis section of the configuration file lets you put devices into trouble or alarm by flipping the switches. The switch numbers are shown in Figure5.There are two switches, and . In the following example, the sensor at address 1 goes into trouble when Switch 1 is up, and it goes into alarm when Switch 1
12 is down. When Switch 1 is off (in the m
is down. When Switch 1 is off (in the middle position), then the sensor is normal (neither in trouble or alarm)..'sensor[1].trouble = 1;',1;','sensor[1].trouble = 0;','sensor[1].alarm = 0;',0;','sensor[1].alarm = 1;', Configuration File Figure 14 shows the elements that define the devices state.Figure 14Device statekind of device: This value is either sensor or . It is assigned in section 4.2.address: The devices address, which is assigned in section 4.2.state: The devices state. This must be either or alarm. Section 7.0 lists the states for each device.value: This number must be one of the allowable values for the state. Section 7.0 lists the allowable values for each state.For example, according to section 7.0, the sensor 2251B has 1 trouble state and 3 alarm states. Assuming that this sensor has been configured with address 1, the following line puts it into its trouble state.'sensor[1].trouble = 1;',The follow
13 ing line puts the sensor into its second
ing line puts the sensor into its second alarm state, Smoke Alarm 2.'sensor[1].alarm = 2;',If you use a number higher than the maximum value listed in section 7.0, the Device Simulator uses the highest allowable value. For example, this line puts the 2251B sensor into the state Smoke Alarm 3.'sensor[1].alarm = 5;',To put a device into its normal state, set both trouble and to zero.'sensor[1].trouble = 0;','sensor[1].alarm = 0;', kind of deviceaddressstate value Configuration File 4.3.1 Controlling more thanYou can assign more than one device to a switch. In the following example, the sensors with addresses 1 and 2 and the modules with the addresses 3 and 4 go into trouble when Switch 2 is up, and go into alarm when Switch 2 is down..},"module" : { "rem" : "Input Module 1",le 1",},"sw2": { "up" : [ 'sensor[1].trouble = 1;','sensor[2].trouble = 1;','module[3].trouble = 1;''module[4].trouble = 1;'1;''sensor[1].troubl
14 e = 0;','sensor[1].alarm = 0;','sensor[2![e = 0;','sensor[1].alarm = 0;','sensor[2](870942/e-0-sensor-1-alarm-0-sensor-2-trouble-0-.jpg "e = 0;','sensor[1].alarm = 0;','sensor[2")
e = 0;','sensor[1].alarm = 0;','sensor[2].trouble = 0;','sensor[2].alarm = 0;','module[3].trouble = 0;','module[3].alarm = 0;','module[4].trouble = 0;','module[4].alarm = 0;',0;','sensor[1].alarm = 3;','sensor[2].alarm = 3;','module[3].alarm = 1;','module[4].alarm = 1;', Configuration File 4.3.2 LoopsTo reduce the size of the configuration file, create loops. In the following example, 30 modules go into trouble when Switch 1 is up, and go into alarm when Switch 1 is down.Put a single straight quotation mark () at the beginning and end of each line of script, and put a comma at the end of each line."up" : [ 'var j; for(j = 1; j j = j + 1) {','module[j].trouble = 1; }','led[2].on = true;',"off" : [ 'var j; for(j = 1; j j = j + 1) {','module[j].alarm = 0;','module[j].trouble = 0; }','led[1].on = false;','led[2].on = false;',"down" : ['var j; for(j = 1; j j = j + 1) {','module[j].alarm = 1; }','led[1].on = true;',4.4LEDsTh
15 e switches can be configured to illumina
e switches can be configured to illuminate 1 or more LEDs. The LED numbers are shown in Figure5.In the following example, LED 2 is on when Switch 1 is up, and LED 1 is on when Switch 1 is down. When Switch 1 is off (in the middle position), both LEDs 1 and 2 are off."up" : [ 'led[2].on = true;'"off" : [ 'led[2].on = false;','led[1].on = false;'"down" : [ Configuration File ],},Figure 15Controlling LEDsUse square brackets [ ] to indicate the LED number. Use true to turn the LED on and to turn the LED off.4.5EventsThe events object is optional.al.'printf("\n----------------------\n");','printf("This text appears when the script is compiled\n");','printf("----------------------\n");' LED numbertrue or false 18 Windows71.Click Start, then click Control PanelFigure 16Start menu2.Click Network and InternetFigure 17Control Panel Network Card Settings on Windows7 3.Click Network and Sharing CenterFigure 18Network and Internet4
16 .Click Change adapter settingsFigure 19N
.Click Change adapter settingsFigure 19Network Sharing Center Network Card Settings on Windows7 5.Right click the network interface you want to use, then select PropertiesFigure 20Network Connections6.Select Internet Protocol Version 4 (TCP/IPv4), then click Figure 21Local Area Connection Properties7.Select Use the follow IP address8.Enter the following values:IP address: 192.168.10.30Subnet mask: 255.255.255.09.Click Make sure to save your previous settings if you have only one network adapter. You may lose your Internet connection after completing these steps. i Network Card Settings on Windows7 Figure 22Internet Protocol Version 4 (TCP/IPv4) Properties 22 Troubleshooting6.1Configure the Device Simulators IP InformationThe Device Simulator has the following IP information by default:IP address: 192.168.10.128Network mask: 255.255.255.0Gateway address: 192.168.1.254DHCP: disabledIf you want to change the IP address,
17 follow the instructions below.1.Connect
follow the instructions below.1.Connect a computer to the USB port of the Device Simulator with a USB A to B male 2.On the computer, open a terminal program such as Tera Term.3.Select the serial port that the USB cable is connected to.When the terminal is connected to the Device Simulator, the [CRAB]$ prompt appears.4.At the [CRAB]$ prompt, type and then press Enter.5.The Device Simulator displays its IP information.Figure 23Device Simulator IP configuration utilityPress Enter after each line to leave the information unchanged.To change the IP address, enter a new IP address on the IP addr line, then press enter after each line until you see the message Configuration savedFigure 24Change the IP address to 192.168.10.55 23 7.1SensorsTable 3:SensorsModelDescriptionDevice StateState in Configuration Value in Configuration 1251Ionization Smoke DetectorLow Chambertrouble1High Chambertrouble2Smoke Alarm 1alarm1Smoke Alar
18 m 2alarm2Smoke Alarm 3alarm31251BIonizat
m 2alarm2Smoke Alarm 3alarm31251BIonization Smoke DetectorLow Chambertrouble1High Chambertrouble2Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm32251Photoelectric Smoke DetectorTroubletrouble1Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm32251BPhotoelectric Smoke DetectorTroubletrouble1Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm32251BRPhotoelectric Smoke DetectorTroubletrouble1Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm32251TPhotoelectric Smoke DetectorTroubletrouble1Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm3Thermal Alarm (60°C)alarm4 Supported Devices 2251TBPhotoelectric Smoke Troubletrouble1Smoke Alarm 1alarm1Smoke Alarm 2alarm2Smoke Alarm 3alarm3Thermal Alarm (60°C)alarm45251BHeat DetectorTroubletrouble1Alarm, 60°Calarm1Alarm, 70°Calarm2Alarm, 80°Calarm3Alarm, 90°Calarm45251RBHeat DetectorTroubletrouble1Alarm, 60°Calarm1Alarm, 70°Calarm2Alarm, 80°Calarm3Ala
19 rm, 90°Calarm45251HHeat DetectorTroublet
rm, 90°Calarm45251HHeat DetectorTroubletrouble1Alarm, 60°Calarm1Alarm, 70°Calarm2Alarm, 80°Calarm3Alarm, 90°Calarm45251PHeat DetectorTroubletrouble1Alarm, 60°Calarm1Alarm, 70°Calarm2Alarm, 80°Calarm3Alarm, 90°Calarm45251THeat DetectorTroubletrouble1Alarm, 60°Calarm1Alarm, 70°Calarm2Alarm, 80°Calarm3Alarm, 90°Calarm4Table 3:Sensors (Continued)ModelDescriptionDevice StateState in Configuration FileValue in Configuration File Supported Devices 2251TMSmoke DetectorLow Chamber Troubletrouble1Maintenance Urgent/Drift Limittrouble2Maintenance Alerttrouble3Level 1 Alarm - 1% ftalarm1Level 2 Alarm - Acclimate 1% - 2%alarm2Level 3 Alarm 3% 2%/ft.alarm3Level 4 Alarm - Acclimate 2% - 4%alarm4Level 5 Alarm 4%/ftalarm5Level 6 Alarm - Thermal Alarm (60°C, 135° Heat)alarm6Table 3:Sensors (Continued)ModelDescriptionDevice StateState in Configuration Value in Configuration Supported Devices 2251 COPTIRMulticriteria Smoke CO trouble (se
20 nsor life has expired)trouble1Thermistor
nsor life has expired)trouble1Thermistor/CO/IR/Freeze Warningtrouble2Maintenance Urgent / Drift Limittrouble3Maintenance Alert: 80% drift limittrouble4CO trouble (6 months of sensor life trouble5IR light saturation trouble699% drift (80% drift trouble7Alarm 1 1%/ft no delaysalarm1Alarm 2 2%/ft no delaysalarm2Alarm 3 3%/ft no delaysalarm3Alarm 4 3%/ft with 10 minutes delayalarm4Alarm 5 4%/ft with 10 minutes delayalarm5Alarm 6 Heatalarm6Table 3:Sensors (Continued)ModelDescriptionDevice StateState in Configuration FileValue in Configuration File Supported Devices 7.2ModulesTable 4:ModulesModelDescriptionDevice StateState in Configuration Value in Configuration M500SSupervised Control ModuleOpentrouble1Shortalarm1SC-66x Supervised Control ModuleOpentrouble1Shortalarm1M501MFreestanding MinimodOpentrouble1Shortalarm1M500MMonitor ModuleOpentrouble1Shortalarm1M500DMDual Monitor ModuleOpentrouble1Shortalarm1IM-1010 Input Module
21 Opentrouble1Shortalarm1M500M-4-20500 Ser
Opentrouble1Shortalarm1M500M-4-20500 Series 4-20mA Input DevicePower 12Vtrouble1M502MConventional Zone Interface ModuleOpentrouble1Short, Alarmalarm1Six Up Conventional Zone Interface ModuleOpentrouble1Short, Alarmalarm1 28 8.11 Sensor and 1 Module"author" : "Iliia","tag" : "1", "desc" : "2 Photo and 2 Monitor", "version" : [0, 3, 0]"sensor" : { "rem" : "Photo 1","model" : "2251B","enabled" : true,"ledno" : 1,"addr" : [ 1 ]"module" : { "rem" : "Input Module 1","model" : "M500M","enabled" : true,"ledno" : 3,"addr" : [ 1 ][ 1 ]'sensor[1].trouble = 1;',"off" : [ 'sensor[1].trouble = 0;','sensor[1].alarm = 0;',"down" : ['sensor[1].alarm = 1;',].alarm = 1;','module[1].trouble = 1;'"off" : [ 'module[1].trouble = 0;','module[1].alarm = 0;',"down" : ['module[1].alarm = 1;',"events": { "init" : ['printf("\n----------------------\n");','printf("Config 1\n");','printf("----------------------\n");' 29 Electrical Specifications Com
22 munications HubCharging current limit: 2
munications HubCharging current limit: 200 mACurrent consumption @24V:Minimum: 32 mAMaximum: 60 mAInput Voltage:Minimum: 12 VDCMaximum: 30 VDC Simulation PortCharging current limit:Current consumption @24V:Minimum: 1.4 mAMaximum: 2.6 mAInput Voltage:Minimum: 12 VDCMaximum: 30 VDC 30 Warranty and Warning InformationPlease read this document CAREFULLY, as it contains important warnings, life-safety, and practical information aboutall products manufactured by the Mircom Group of Companies, including Mircom and Secutron branded products, ut limitation all fire alarm, nurse call, building automation and access control and card access products (hereinafter individually or collectively, as applicable, referred to as Mircom System).NOTE TO ALL READERS:Nature of Warnings. The within warnings are communicated to the reader out of an abundance of caution and create no legal obligation for Mircom Group of Companies, whatsoever.
23 Without limiting the generality of the
Without limiting the generality of the foregoing, this document shall NOT be construed as in any way altering the rights and obligations of the parties, governed by the legal documents that apply in any given circumstance.Application. The warnings contained in this document apply to all Mircom System and shall be read in conjunction with:a.the product manual for the specific Mircom System that applies in given circumstances;b.legal documents that apply to the purchase and sale of a Mircom System, which may include the companys standard terms and conditions and warranty statements; c.other information about the Mircom System or the parties rights and obligations as may be application to a given circumstance. Security and Insurance. Regardless of its capabilities, no Mircom System is a substitute for property or life insurance. Nor is the system a substitute for property owners, renters, or other occupants to act
24 prudently to prevent or minimize the har
prudently to prevent or minimize the harmful effects of an emergency situation. Building automation systems produced by the Mircom Group of Companies are not to be used as a fire, alarm, or life-safety system.NOTE TO INSTALLERS:All Mircom Systems have been carefully designed to be as effective as possible. However, there are circumstances where they may not provide protection. Some reasons for system failure include the following. As the only individual in contact with system users, please bring warning to the attention of the users of this Mircom System. Failure to properly inform system end-users of the circumstances in which the system might fail may result in over-reliance upon the system. As a result, it is imperative that you properly inform each customer for whom you install the system of the possible forms of failure:Inadequate Installation. All Mircom Systemsmust be installed in accordance with all the ap
25 plicable codes and standards in order to
plicable codes and standards in order to provide adequate protection. National standards require an inspection and approval to be conducted by the local authority having jurisdiction following the initial installation of the system and following any changes to the system. Such inspections ensure installation has been carried out properly.Inadequate Testing. Most problems that would prevent an alarm a Mircom System from operating as intended can be discovered by regular testing and maintenance. The complete system should be tested by the local authority having jurisdiction immediately after a fire, storm, earthquake, accident, or any kind of construction activity inside or outside the premises. Warranty and Warning Information The testing should include all sensing devices, keypads, consoles, alarm indicating devices and any other operational devices that are part of the system.NOTE TO USERS:All Mircom Systems have be
26 en carefully designed to be as effective
en carefully designed to be as effective as possible. However, there are circumstances where they may not provide protection. Some reasons for system failure include the following. The end user can minimize the occurrence of any of the following by proper training, testing and maintenance of the Mircom Systems: Inadequate Testing and Maintenance. imperative that the systems be periodically tested and subjected to preventative maintenance. Best practices and local authority having jurisdiction determine the frequency and type of testing that is required at a minimum. Mircom System may not function properly, and the occurrence of other system failures identified below may not be minimized, if the periodic testing and maintenance of Mircom Systems is not completed with diligence and as required. Improper Operation. It is important that all system users be trained in the correct operation of the alarm system and that
27 they know how to respond when the syste
they know how to respond when the system indicates an alarm. A Mircom Systemmay not function as intended during an emergency situation where the user is unable to operate a panic or emergency switch by reason of permanent or temporary physical disability, inability to reach the device in time, unfamiliarity with the correct operation, or related circumstances.Insufficient Time. There may be circumstances when a Mircom System will operate as intended, yet the occupants will not be protected from the emergency due to their inability to respond to the warnings in a timely manner. If the system is monitored, the response may not occur in time enough to protect the occupants or their belongings.Carelessness or Safety Hazards. Moreover, smoke detectors may not provide timely warning of fires caused by carelessness or safety hazards such as smoking in bed, violent explosions, escaping gas, improper storage of flammable ma
28 terials, overloaded electrical circuits
terials, overloaded electrical circuits or children playing with matches or arson.Power Failure. Some Mircom Systemcomponents require adequate electrical power supply to operate. Examples include: smoke detectors, beacons, HVAC, and lighting controllers. If a device operates only by AC power, any interruption, however brief, will render that device inoperative while it does not have power. Power interruptions of any length are often accompanied by voltage fluctuations which may damage Mircom Systems or other electronic equipment. After a power interruption has occurred, immediately conduct a complete system test to ensure that the system operates as intended.11.Battery Failure. If the Mircom System or any device connected to the system operates from batteries it is possible for the batteries to fail. Even if the batteries have not failed, they must be fully charged, in good condition, and installed correctly. Som
29 e Mircom Systems use replaceable batteri
e Mircom Systems use replaceable batteries, which have a limited life-span. The expected battery life is variable and in part dependent on the device environment, usage and type. Ambient conditions such as high humidity, high or low temperatures, or large temperature fluctuations may reduce the expected battery life. Moreover, some Mircom Systems do not have a battery monitor that would alert the user in the event that the battery is nearing its end of life. Regular testing and replacements are vital for ensuring that the batteries function as expected, whether or not a device has a low-battery monitor.Physical Obstructions. Motion sensors that are part of a Mircom System must be kept clear of any obstacles which impede the sensors ability to detect movement. Signals being communicated by a Mircom System may not reach the receiver if an item (such as metal, water, or concrete) is placed on or near the radio path.
30 Deliberate jamming or other inadvertent
Deliberate jamming or other inadvertent radio signal interference can also negatively affect system operation. Warranty and Warning Information 13.Wireless Devices Placement Proximity. Moreover all wireless devices must be a minimum and maximum distance away from large metal objects, such as refrigerators. You are required to consult the specific Mircom System manual and application guide for any maximum distances required between devices and suggested placement of wireless devices for optimal functioning. 14.Failure to Trigger Sensors. Moreover, Mircom Systems may fail to operate as intended if motion, heat, or smoke sensors are not triggered. a.Sensors in a fire system may fail to be triggered when the fire is in a chimney, walls, roof, or on the other side of closed doors. Smoke and heat detectors may not detect smoke or heat from fires on another level of the residence or building. In this situation the c
31 ontrol panel may not alert occupants of
ontrol panel may not alert occupants of a fire. b.Sensors in a nurse call system may fail to be triggered when movement is occurring outside of the motion sensors range. For example, if movement is occurring on the other side of closed doors or on another level of the residence or building the motion detector may not be triggered. In this situation the central controller may not register an alarm signal.15.Interference with Audible Notification Appliances. Audible notification appliances may be interfered with by other noise sources such as stereos, radios, televisions, air conditioners, appliances, or passing traffic. Audible notification appliances, however loud, may not be heard by a hearing-impaired person.16.Other Impairments. Alarm notification appliances such as sirens, bells, horns, or strobes may not warn or waken a sleeping occupant if there is an intervening wall or door. It is less likely that the oc
32 cupants will be alerted or awakened when
cupants will be alerted or awakened when notification appliances are located on a different level of the residence or premise.17.Software Malfunction. Most Mircom Systems contain software. No warranties are provided as to the software components of any products or stand-alone software products within a Mircom System. For a full statement of the warranties and exclusions and limitations of liability please refer to the companys standard Terms and Conditions and Warranties. 18.Telephone Lines Malfunction. Telephone service can cause system failure where telephone lines are relied upon by a Mircom System. Alarms and information coming from a Mircom System may not be transmitted if a phone line is out of service or busy for a certain period of time. Alarms and information may not be transmitted where telephone lines have been compromised by criminal tampering, local construction, storms or earthquakes.19.Component Fa
33 ilure. Although every effort has been m
ilure. Although every effort has been made to make this Mircom System as reliable as possible, the system may fail to function as intended due to the failure of a component.20.Integrated Products. Mircom System might not function as intended if it is connected to a non-Mircom product or to a Mircom product that is deemed non-compatible with a particular Mircom System. A list of compatible products can be requested and obtained.WarrantyPurchase of all Mircom products is governed by:https://www.mircom.com/product-warrantyhttps://www.mircom.com/purchase-terms-and-conditionshttps://www.mircom.com/software-license-terms-and-conditions © Mircom 2018Printed in Canada Subject to change without prior notice CANADA - Main Office25 Interchange WayVaughan, ON L4K 5W3Tel: (905) 660-4655(888) 660-4655Fax: (905) 660-4113U.S.A4575 Witmer Industrial Estates Niagara Falls, NY 14305Tel: (905) 660-4655(888) 660-4655Fax: (905) 660-4113