Installation and Operation Manual
LT-6149 Rev. 1.2
May 2018
SIMU-MGC-1
1 Loop Device Simulator
3
Contents
1.0 Introduction 4
1.1 Required Hardware ........................................................................................................ 4
1.2 Components ................................................................................................................... 4
2.0 Connections 4
2.1 Ethernet ......................................................................................................................... 5
2.2 USB ................................................................................................................................ 5
2.3 Power the Hub ............................................................................................................... 5
2.4 Port 1 ............................................................................................................................. 5
2.5 Power the Port ............................................................................................................... 6
2.6 Switches and LEDs ........................................................................................................ 6
3.0 Web Interface 7
3.1 Getting Started ............................................................................................................... 7
3.2 Uploading a Configuration File ....................................................................................... 8
3.3 Monitoring and Changing Device States ........................................................................ 10
4.0 Configuration File 12
4.1 Info ................................................................................................................................. 12
4.2 Sensors and Modules .................................................................................................... 12
4.3 Switches ......................................................................................................................... 13
4.4 LEDs .............................................................................................................................. 16
4.5 Events ............................................................................................................................ 17
5.0 Network Card Settings on Windows 7 18
6.0 Troubleshooting 22
6.1 Configure the Device Simulator’s IP Information ........................................................... 22
7.0 Supported Devices 23
7.1 Sensors .......................................................................................................................... 23
7.2 Modules ......................................................................................................................... 27
8.0 Sample Configuration File 28
8.1 1 Sensor and 1 Module .................................................................................................. 28
9.0 Electrical Specifications 29
10.0 Warranty and Warning Information 30
4
1.0 Introduction
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.1 Required Hardware
In order to configure and use the Device Simulator the following hardware is required:
• Computer
• Ethernet cable
• USB cable (optional)
• 12-24V DC Power Supply (optional)
1.2 Components
2.0 Connections
Figure 1 Device Simulator front
Figure 2 Device Simulator back
Table 1 Components
Picture Model Description
SIMU-MGC-1
1 Loop Device Simulator
• Includes power supply and
Ethernet cable
Unused
USB Port 1
Ethernet
Port 1
Unused
Hub Power
12
5
Connections
2.1 Ethernet
The Ethernet connection is for configuration by a computer. See section 3.0 on page 7.
2.2 USB
Use the USB port for power (section 2.3) or troubleshooting (section 6.0).
2.3 Power the Hub
The hub runs the web interface 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
devices.
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.
• USB
• Terminal block - for 12-30 VDC power. Use either pair of terminals.
• Power barrel - for 12-30 VDC power.
Figure 3 Terminal block and power barrel
2.4 Port 1
Port 1 in Figure 2 is a loop simulator. Connect this port to a device loop on a fire alarm control
panel.
Note: Use only one of the power options at a time.
Ground
+24V
Power
terminal
block
Power
barrel
12
i
6
Connections
2.5 Power the Port
During 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, or
• from the power terminal block as shown in Figure 4.
Figure 4 Powering the port from the power terminal block during configuration
2.6 Switches and LEDs
The 2 switches and 4 programmable LEDs are numbered as shown in Figure 5.
Figure 5 Switch and LED numbers
The 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
3.0 Web Interface
3.1 Getting Started
1. See section 5.0 on page 18 for instructions on configuring your computer’s 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 6 Device Simulator main page
Note: If you cannot access the web interface, see section 6.0.
Table 2 Web page menu description
Menu Name Description
Home Home page.
Database Shows the current status of the port and the version of its database.
Config Shows the current configuration file or lets you upload a new one.
Monitor Allows you to monitor the current state of the devices.
Diagnostics For factory use only.
Scripts You can type in scripts to be executed on the Device Simulator.
Firmware Shows the current status of the port and which firmware version it is running.
Setup Device Simulator network settings.
Debug For factory use only.
i
8
Web Interface
3.2 Uploading a Configuration File
Check the port’s status
1. Click Database.
In the Port 1 row, the Status must show Mircom CRAB Database and the Port State
must be Online.
If the port is not online, check the power to the port (section 2.5).
Figure 7 Database page
Upload a configuration file
1. Click Config.
Figure 8 Config page
2. Select Port 1 in the Simulator menu.
3. Click Browse, then navigate to the configuration file.
4. Click Upload.
9
Web Interface
The contents of the configuration file appear in the middle of the window.
Figure 9 Config page showing configuration file
5. Click Compile.
If there are no errors, a summary of the configured devices appears at the bottom of the
window.
Figure 10 Config page showing summary
See the current configuration file
1. Click Config.
2. Click Read.
The currently loaded configuration file appears.
10
Web Interface
Edit the current configuration file
1. Click Config.
2. Click Read.
The currently loaded configuration file appears.
3. Make changes to the configuration file.
4. Click Write.
5. Click Compile.
If there are no errors, a summary of the configured devices appears at the bottom of the
window.
Erase the current configuration file
1. Click Config.
2. Click Purge.
The currently loaded configuration file is erased. The port is now unconfigured.
3.3 Monitoring and Changing Device States
Use 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 11 Monitor tab showing sensors
Figure 12 Monitor tab showing modules
11
Web Interface
Change the state of devices
1. Select either Sensor or Module in the Device type menu.
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 Set.
The display changes to show the current state of the devices.
Figure 13 Monitor tab showing 1 sensor in alarm
For example, assume that the sensor at address 1 in Figure 13 is a 2251B. To put this sensor
into alarm, select the sensor, then select 1, 2, or 3 in the Alarm menu, then click Set.
To put it into trouble, select 1 in the Trouble menu.
To put the sensor back into its normal state, select 0 in the Alarm menu and 0 in the Trouble
menu.
12
4.0 Configuration File
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. The entire script
must begin and end with curly brackets { }.
4.1 Info
"info": {
"author" : "Bob",
"tag" : "full_photo_monitor",
"desc" : "Fully loaded loop (photo + monitor)",
"version" : [0, 1, 0]
},
• author: The file’s author.
• tag: A short description of the configuration.
• desc: A full description of the configuration.
• version: The version of the configuration.
4.2 Sensors and Modules
Devices 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 ]
},
• sensor or module: This value must be sensor or module, depending on the device
in the model line. For example if the model is 2251B, then the value must be sensor. If
the model is M500M, then the value must be module.
13
Configuration File
• rem: This value is a reminder for you. It can be anything.
• model: This value must be one of the models listed in section 7.0.
• enabled:
• true: The device is connected.
• false: The device is not connected. The fire alarm control panel will report it as
missing.
• ledno: The LED number associated with the device (optional). This LED will follow the
device.
• addr: The device’s 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.
"sensor" : {
"rem" : "Photo 1",
"model" : "2251B",
"enabled" : true,
"addr" : [ 11, 12, 13, 14, 15 ]
},
4.3 Switches
This section of the configuration file lets you put devices into trouble or alarm by flipping the
switches. The switch numbers are shown in Figure 5.
There are two switches, sw1 and sw2. 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 is down. When Switch 1
is off (in the middle position), then the sensor is normal (neither in trouble or alarm).
"sw1": {
"up" : [
'sensor[1].trouble = 1;',
],
"off" : [
'sensor[1].trouble = 0;',
'sensor[1].alarm = 0;',
],
"down" : [
'sensor[1].alarm = 1;',
],
},
14
Configuration File
Figure 14 shows the elements that define the device’s state.
Figure 14 Device state
• kind of device: This value is either sensor or module. It is assigned in section 4.2.
• address: The device’s address, which is assigned in section 4.2.
• state: The device’s state. This must be either trouble 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 following 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 alarm to zero.
'sensor[1].trouble = 0;',
'sensor[1].alarm = 0;',
'sensor[1].trouble = 1;',
kind of device address state
value
15
Configuration File
4.3.1 Controlling more than 1 Device from 1 Switch
You 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.
"sensor" : {
"rem" : "Photo 1",
"model" : "2251B",
"enabled" : true,
"ledno" : 1,
"addr" : [ 1 , 2 ]
},
"module" : {
"rem" : "Input Module 1",
"model" : "M500M",
"enabled" : true,
"ledno" : 3,
"addr" : [ 3 , 4 ]
},
"sw2": {
"up" : [
'sensor[1].trouble = 1;',
'sensor[2].trouble = 1;',
'module[3].trouble = 1;'
'module[4].trouble = 1;'
],
"off" : [
'sensor[1].trouble = 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;',
],
"down" : [
'sensor[1].alarm = 3;',
'sensor[2].alarm = 3;',
'module[3].alarm = 1;',
'module[4].alarm = 1;',
],
},
16
Configuration File
4.3.2 Loops
To 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.
"sw1": {
"up" : [
'var j; for(j = 1; j < 31; j = j + 1) {',
'module[j].trouble = 1; }',
'led[2].on = true;',
],
"off" : [
'var j; for(j = 1; j < 31; 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 < 31; j = j + 1) {',
'module[j].alarm = 1; }',
'led[1].on = true;',
],
},
4.4 LEDs
The switches can be configured to illuminate 1 or more LEDs. The LED numbers are shown in
Figure 5.
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.
"sw1": {
"up" : [
'led[2].on = true;'
],
"off" : [
'led[2].on = false;',
'led[1].on = false;'
],
"down" : [
17
Configuration File
'led[1].on = true;'
],
},
Figure 15 Controlling LEDs
Use square brackets [ ] to indicate the LED number. Use true to turn the LED on and false
to turn the LED off.
4.5 Events
The events object is optional.
"events": {
"init" : [
'printf("\n----------------------\n");',
'printf("This text appears when the script is compiled\n");',
'printf("----------------------\n");'
],
}
'led[1].on = true;',
LED number true or false
18
5.0 Network Card Settings on
Windows 7
1. Click Start, then click Control Panel.
Figure 16 Start menu
2. Click Network and Internet.
Figure 17 Control Panel
19
Network Card Settings on Windows 7
3. Click Network and Sharing Center.
Figure 18 Network and Internet
4. Click Change adapter settings.
Figure 19 Network Sharing Center
20
Network Card Settings on Windows 7
5. Right click the network interface you want to use, then select Properties.
Figure 20 Network Connections
6. Select Internet Protocol Version 4 (TCP/IPv4), then click Properties.
Figure 21 Local Area Connection Properties
7. Select Use the follow IP address.
8. Enter the following values:
• IP address: 192.168.10.30
• Subnet mask: 255.255.255.0
9. Click OK.
Note: 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
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
