N-TEC Access

SIMPLEX 4100U Interface - Product Specification and Manual

Version 1.0 - 25 September 2006

Support Options
For support on this product contact Mr. Jason Crouch
General Manager, Tyco Fire & Integrated Solutions - MEAR
Middle East, Europe, Africa and Russia
Email : jcrouch@tycoint.com
Web : www.simplex.n-tec.biz
FTP Site : www.grostech.com/N-TEC

1
SIMPLEX 4100U Interface.
IP-Gateway Setup
Serial:
The network interface for the 4100U Fire Panel is called an IP-Gateway and can be configured via a
standard serial port using the settings 57600-8-N-1 and when connected and powered on you
should see this screen:
----------------------------
Grosvenor Technology Ltd.
----------------------------
Device Type: Simplex 4100U
Firmware Version: V1.0.0
Boot Time: 00/00/00 00:00:00
----------------------------
10 Mbps Half-Duplex Link established
DHCP OK
Initializing network stack...
IF IP addr Def Gtway state type H/W addr
0 100.1.100.39 100.1.1.107 UP Ethernet 0:50:C2:59:11:1
Login:
The default for the device is to boot via DHCP. If a DHCP host can't be found the board will assign
it’self an address via the Link-Local protocol (RFC 3927), for example:
----------------------------
Grosvenor Technology Ltd.
----------------------------
Device Type: Simplex 4100U
Firmware Version: V1.0.0
Boot Time: 00/00/00 00:00:00
----------------------------
10 Mbps Half-Duplex Link established
...DHCP Failed
Initializing network stack...
IF IP addr Def Gtway state type H/W addr
0 169.254.100.200 169.254.1.1 UP Ethernet 0 :50:C2:59:11:1
Login:
When the device boots for the first time, if you let it sit for a few seconds you will see the following
warning messages logged on the console such as:
WARNING - Unable to connect to N-TEC comms
WARNING - Panel rejected configured password.
To allow the device to function correctly, you will need to configure the device. To do this you must
logon with the default username and password which is ‘admin’ and ‘password’. Once you are
logged on, at the command prompt you need to run the command ‘setup’. The following
parameters need to be set to allow the interface to function correctly:
Device Name

2
 IP-Gateway Setup

Enable DHCP
IP Address
Subnet Mask
Default Gateway
Local Password
Panel Password
N-TEC Server IP
N-TEC User Name
N-TEC User Password

Device Name:
This acts a unique identifier for this panel, the default is ‘SIMPLEX01’. This name will be used as a
prefix when elements are defined in N-TEC later in the configuration process.

Enable DHCP:
This option enables or disables DHCP. If DHCP is disabled you will be given the option to set static
IP parameters.

IP Address:
Set the device’s IP address. This option is only available if DHCP is disabled, otherwise it is
ignored.

Subnet Mask:
Sets the device’s subnet mask. This option is only available if DHCP is disabled, otherwise it is
ignored.

Default Gateway:
Sets the devices default gateway. This option is only available if DHCP is disabled, otherwise it is
ignored.

Local Password:
This password is the password that you use to log on to the device; it is also used when you
attempt to configure the device remotely.

Panel Password:
Some of the commands that the interface can send to the panel require elevated privileges on the
panel so you must supply a password that will allow the interface to raise it’s privilege level on the
computer port. If the password is invalid on the panel you will see the following message reported
on the console:
WARNING - Panel rejected configured password.
If the configured password is valid but does not have sufficient privileges on the panel to execute
the command you will see the following message indicating that you need to change the password
to one with higher privileges.
WARNING - Panel password has insufficient access for last command.

N-TEC Server IP Address:

This is the IP address of the N-TEC server. The Interface will open a socket connection to this host
on port 9878.

N-TEC User Name & N-TEC User Password:

The Interface must be configured with a valid N-TEC user account to enable it to change the state
of any elements that are configured within N-TEC, this is required to support panel command
buttons protected by sections in the N-TEC database. If the username/password configured is not
valid on the N-TEC server you will see the following message logged to the console:
WARNING - N-TEC is rejecting the configured Username/Password.
Once the configuration has been changed the device will save the changes and reboot. Changes
will not take effect until the device has rebooted.

3
 Simplex 4100U - N-TEC Interface

Other Supported Commands

Help
Lists the available commands. If used in the form ‘help <command>’ then description of the
requested command will be printed. ? is an alias for help.

Arp
Prints out the contents of the arp cache. This maps IP addresses to physical MAC address.
Diagnostics use only.
IP address H/W address
100.1.90.46 0:C:29:66:BC:91

Gettime
Prints out the current system time. The system time is synced with N-TEC when ever a connection
is established.
--- , 20 Sep 2006 15:25:10

Ifstat
This commands lists the current ip address assigned to the network interface. Diagnostics use only.
IF IP addr Def Gtway state type H/W addr
0 100.1.100.39 100.1.1.107 UP Ethernet 0 :50:C2:59:11:1

Netstat
Lists all the active network connections and their current state. Diagnostics use only.
FD SStat Type Oport fds lds STATE tosend recvd srcport
dstport srcip dstip
0 Used TCP 0 0 -1 ESTB 0 0 1024
9878 100.1.100.39 100.1.90.46
1 Bind UDP 1701 0 0
2 Listn TCP 9600 0 0 LISTEN 0 0 0 0
0.0.0.0 0.0.0.0
3 Used TCP 0 3 2 LISTEN 0 0 9600 0
0.0.0.0 0.0.0.0
4 NA

Ping
Sends an echo request to another device to test network connectivity.
ZTP2.0.0(C) ZiLOG Inc. [ping utility]
PING#1, Reply from 100.1.90.46 :rtt < 50 ms
PING#2, Reply from 100.1.90.46 :rtt < 50 ms
PING#3, Reply from 100.1.90.46 :rtt < 50 ms
PING#4, Reply from 100.1.90.46 :rtt < 50 ms
Ping Stats:
Sent:4
Recvd:4
Success:100%
Avg RTT(Approx):0.00 sec

Reboot
This command will reset the device.

4
SIMPLEX 4100U Interface.
IP-Gateway Remote Configuration
As well as configuring the interface via the console port it is possible to configure it remotely over
the network. When started, the remote device manager will send out a broadcast message looking
for any local devices, details of which will be displayed in the main window:

Configure Device
It is simply a matter of clicking on the device that you want to configure and click on ‘Connect’. This
will connect to the device and retrieve its configuration.
Because the devices are password protected, the first time you connect you will be prompted for a
password. This password is only saved while the application is running; it will not be saved when
the application is closed.

The device configuration is displayed on three tabs and the items match those described above

5
Simplex 4100U - N-TEC Interface

Once you have made all the change you wish, click on OK and the changes will be sent to the
device and the device will reboot.

6
 IP-Gateway Remote Configuration

Change Device Password

To change the devices password remotely select the device from the Device Manager, right click
and select ‘Change Password’:

You will be prompted to confirm the current password and to enter a new password:

Clicking OK will validate the passwords and send the changes to the remote device; the device will
then reboot for the changes to take affect.

7
SIMPLEX 4100U Interface.
Configuring N-TEC
For the interface to do anything useful, targets must be configured within N-TEC to match the
elements defined within the panel.
When an alarm is triggered the SIMPLEX 4100U panel sends N-TEC a message via the IP-
Gateway interface. These alarms/events include the node address of the sensor that caused the
alarm to be triggered. The interface will translate this message into a form that N-TEC can
recognise and will prefix the address with the device name of the IP-Gateway interface. This allows
multiple SIMPLEX panels to be connected to a single N-TEC system.
For N-TEC to do anything with these events they must be configured as Elements within N-TEC.

Installing N-TEC
You will need a V4.0 or higher of N-TEC before the IP-Gateway can communicate with N-TEC.

Patching V4.0 Install

Because the 4100U interface was released after N-TEC 4.0, you must update
several N-TEC files to get the correct level of functionality for the IP-Gateway.
Later versions of N-TEC will not have to do this.
 Close all N-TEC applications on all machines
 Delete DR.* and DRC.* files from \winjan\sys and copy in the
replacements from the patch

 Run Syncwin32 and click on TableStructure->Update. When complete,

close syncwin

 Run the DB import program to load in the extra records needed. For a
complete list of changes see ‘N-TEC DB Update for Simplex.xls’

 Run Syncwin32 and click on TableStructure->Update, when it’s

complete, close syncwin
 Run N-TEC Comms Cold, click yes to all options and then start and log
onto N-TEC Database as an installer

Creating an Alarm Element

In this example we will create an element that corresponds to a smoke alarm configured in the
SIMPLEX panel. The sensor address is 2-1-0, and is called ‘Wing A South Area Smoke’. The
SIMPLEX interface board is configured with a device name of ‘SIMPLEX01’
Logon to the N-TEC Database application with an installer level account, and open the Element
configuration dialog Open • System • Element • Element... and click on New. Enter the values as
below:

8
 Configuring the Access System

The Element UID is the address as translated by the IP-Gateway interface board. This is just the
interface’s device name concatenated with ‘: ‘ and the sensor address.
The Element Type UID is INPUT, there are other element types that will be described later.
The Description can be any English descriptor, it does not have to match the description on the
panel. This is the name that will be displayed in the N-TEC Report/Guard Screen when the alarm is
triggered.
The Section value should be left blank.

Adding a Sensor to a Graphics Map

Logon to the Report/Guard Screen with an installer level account and enable graphics. Navigate to
the map that you wish to add the sensor to and press Ctrl-E to enter the Graphics Edit Mode. Left
click on the background and select Add Input Icon…

Select the element created in the steps above.

Select an icon that matches the sensor you’re adding.

9
 Simplex 4100U - N-TEC Interface

Then using the right mouse button drag the icon into position on the map and press Ctrl-E to exit
the Graphics Edit Mode.

You can now click on the icon to get status information and isolate the alarm from N-TEC if needed.

This isolation is ONLY within N-TEC. It does not affect the 4100U fire panel.

If you trigger the alarm on the panel, you will now see the icon go into an alarm state. It will show up in
system but you will not get the events appearing in the Report/Guard Screen, which is the subject of the
next section.

10
Configuring the Access System

11
SIMPLEX 4100U Interface.
Element Reporting
If you want to generate acknowledgeable alarms and messages within the Report/Guard Screen a
few more steps must be completed.
An Element can generate a different report as each of its properties enters a different state. For
example, the INPUT element we are dealing with has the following properties each with several
states:

Property Property No. State State No. Report No.

Reset 0 1
Alarm 0
Activated 1 0
OK 0 3
Circuit 1
Fault 1 2

To start creating the required records use the pull-down menu; Open • System
• Element • ElemRpt and click on the New button.

The first task is to create the required Reporting Groups. Click in the green
text box for Report Group and click on the Choices button

Click on the Add button to add appropriate Report Groups which we will add
the following:
 Fire Alarm Active
 Fire Alarm Reset
 Trouble Active
 Trouble Reset
These names are not fixed, you can change them to any English descriptor.
Next is to create the actual ElemRpt records that link the State Change
Events to the Report Groups. Create four entries, one for each item (row) in
the table above, for example the first row would look like this:

The Description field is optional, if you supply a value for this it will be used instead of the state
name (in the table above) when the report is displayed in the Report/Guard Screen. For example,

12
 Element Reporting

for the entry associated with a circuit fault, you might want to include the description Detector Head
Missing as the cause of a circuit fault when the detector head is removed or failed.

Once you have created the Element Reports, we now need to tell N-TEC how and where to route
the reports. This is done in the same way as any other report routing within N-TEC: via the
Reporting Destinations dialog Open • Reporting • Destinations... An example is shown below:
(See also an extract from the main N-TEC manual Reporting and Routing of System Events -
An Overview)

If you want you can attach a message to appear in the report screen.

13
Simplex 4100U - N-TEC Interface

Once the Reporting Destinations have been configured, reports will appear in the Report/Guard
Screen as below.

As you can see, the Trouble Alarms are using a Custom Description rather than the default
Element State Name.
For each sensor that you want to monitor within N-TEC, you must configure an Element Record
and an Element Report Record for each state that you want to monitor (normally all four).

14
Reporting and Routing of System Events - An Overview
Reporting Categories
N-TEC system events can be sent to Screen, File, Printer, Email, SMS Messaging; or any
multiple of these Devices.
System controllers, IDCs and IPCs attached to the system, report information to the main
PC/server, for example a Box/Controller may report that the mains power has failed or a
door connected to it is wedged open. The main PC/server needs to know what to do with this
information and what priority to allocate to it. This is done by a pre-defined set of rules
known by the system as a Reporting Category.
Every Box/Controller, Door, Reader and Input is allocated a Reporting Category. System
defaults include Normal Box Reporting, Normal Door Reporting, Normal Reader Reporting
and Normal Input Reporting. These are typical for most systems but others can be
composed to suit your needs.
Each of these hardware elements (Box, Door, Reader, Input), has a range of conditions
that when ‘triggered’ the condition is conveyed to the main PC/server for example Input
conditions can be Activated, Reset, Circuit Fault, Circuit Fault Clear, Tamper, and
Tamper Reset as shown in the Input Reporting record.

Any change in these conditions may need to be reported to several Devices for example an
Input Activated may wish to be sent to a Report/Guard Screen and a History File.

Reporting Groups
In this example we are following an Input Reporting Category but all Reporting
Categories are constructed in the same way.
Within the Input Reporting Category, each condition is assigned a suitable Reporting
Group. A Reporting Group can inform multiple Device destinations when a condition
changes. In this example called 'Normal Input Reporting', if the Input is Activated the
Reporting Group called 'Input Activated' will be applied.

Reporting Destinations
Reporting Groups are defined in the Reporting Destinations record which is found on the
pull-down menu Open • Reporting • Destinations.
For each Device destination a separate Reporting Destination record must be completed.
In the two examples shown, the first defines that the Reporting Group 'Input Activated'
shall go to Screen 1 with an event priority of 5. The second record shows that the same

15
Simplex 4100U - N-TEC Interface

Reporting Group of Input Activated will go to the History File with a priority of 99.
If the Mode and Time Zone fields are left blank, the Reporting Destination for each
instance will trigger at all times and during all Mode settings.

In Summary
 Each hardware element such as a Box/Controller, Door, Reader, Input, has a
range of conditions that when ‘triggered’ the condition is conveyed to the main
PC/server.
 Changes in these conditions need to be reported to various Devices, for example
Screen, File, Printer, Email, SMS Messaging. This is done by a pre-defined set
of rules known by the system as a Reporting Category.
 A Reporting Category record contains Reporting Groups that define which
Devices the conditions will be reported to.
 Reporting Groups are defined in the Reporting Destinations record and can
have multiple instances to allow multiple Devices to be included in the condition
announcement
 By including Time Zones and system Modes in the Reporting Destinations
record, you can control when these rules apply by day/time/and system Mode.

16
SIMPLEX 4100U Interface.
Panel Commands
The final component that needs to be set up is the ability to send commands to the panel. The
SIMPLEX 4100U interface V1.0.0 supports the following commands:

Description Command

System Reset SysReset

Alarm Silence AlarmS
Acknowledge Fire ACK F
Acknowledge Supervisory ACK S
Acknowledge Trouble ACK T
Acknowledge Priority 2 ACK P
Acknowledge Next Alarm AckNext

To configure a command you need to create an Element Type of PANELCTRL. As with the other
commands the Element UID must be prefixed with <devicename>: for example, this is the
command for a system reset:

To make use of this command you need to add a Panel Control Icon to a Graphics Map. When
this icon is clicked, it will send a command request to the IP-Gateway and the icon will change to an
hour glass. If the command is recognised by the interface it will send a Command Acknowledge
and the hour glass will be reset.
Using these commands it is possible to configure a Virtual Control Panel, for example:

17
Simplex 4100U - N-TEC Interface

In this example each of the red buttons has a cloaked Panel Control Icon placed over it. There is
also a Panel Monitor Icon shown on the left hand side that is currently in alarm state. In the screen
shot below you can see the same Panel Control Icon having been clicked and waiting for the
interface to respond.

18
SIMPLEX 4100U Interface.
Panel Monitors
It is possible to set up a monitor that will generate an Acknowledgeable Alarm if the network
connection to the IP-Gateway is lost or the interface loses it serial link to the SIMPLEX panel.
The steps to configure this monitor are similar to the steps required for a sensor. The monitor works
not by polling the panel as is done with an IDC, but requires the interface to reset a Special
Element at least once per minute. If the Element State is not reset within a minute it is moved to
an Alarm State.
The Element Type used is the PANELMON type:

Property Property No. State State No. Report No.

Panel OK 0 0
0
Communications Fault 1 1

IP-Gateway OK 0 2
1
Communications Fault 1 3

When configuring the monitor it must be named <devicename>: Monitor and is shown in the
example below:

Next you need to configure the Element Reporting and Reporting Destinations.

19