Eaton Fire Addressable Site Monitor Software User Manual
Eaton Fire Addressable Site Monitor Software User Manual
Contents
INSTALLATION
Components....................................................................................................................................................... 3
Monitoring Service................................................................................................................................... 3
Desktop User Interface............................................................................................................................. 3
Web User Interface................................................................................................................................... 3
Requirements..................................................................................................................................................... 3
CONFIGURATION
Monitoring Service............................................................................................................................................. 4
Desktop User Interface...................................................................................................................................... 4
Web User Interface............................................................................................................................................ 4
Server Configuration Tool.................................................................................................................................... 4
ADMINISTRATION
Initial Setup and Login........................................................................................................................................ 5
Users .................................................................................................................................................................. 5
Networks............................................................................................................................................................ 5
Connection Types............................................................................................................................................. 6
Eco232...................................................................................................................................................... 6
Level 2 Pin Code....................................................................................................................................... 6
Panels............................................................................................................................................................... 6
Add Panel.................................................................................................................................................. 6
Find All Panels/Devices/Zones.................................................................................................................. 6
Sync with Site Installer............................................................................................................................. 6
Snoozing........................................................................................................................................................... 6
Adding an Eco232 Panel.................................................................................................................................. 6
Events................................................................................................................................................................. 6
Conditions........................................................................................................................................................ 7
Actions............................................................................................................................................................. 7
Reports............................................................................................................................................................... 7
Interface History.............................................................................................................................................. 7
Network History............................................................................................................................................... 7
NORMAL OPERATION
Main window...................................................................................................................................................... 8
Navigation................................................................................................................................................. 8
Devices............................................................................................................................................................... 8
Scanning Analogue Values.................................................................................................................................. 9
Enable / Disable.................................................................................................................................................. 9
Desktop Interface Only Features........................................................................................................................ 9
Tray Icon and Notifications............................................................................................................................... 9
Connecting to Multiple Sites........................................................................................................................... 9
1.1.1 Monitoring Service To use this component, a suitable ASP.Net enabled web
server must be installed. It is also important to note that
This component runs as a pair of Windows services in no web server is provided by the Site Monitor package.
the background while ever the PC is turned on, assuming However, you can use any ASP.Net 2 enabled web server,
the services are set to automatic start up. To change such as Microsoft IIS or UltiDev Cassini.
this behaviour please refer to the documentation for
your version of Windows for more details on service 1.2 Requirements
administration. This component is responsible for
providing the link from the PC to the panel network, All components require that Microsoft .Net v2.0 (or
event monitoring and the XML interface to clients. compatible) be installed. The monitoring service also
requires Microsoft SQL Server Compact v3.5 SP1 or
1.1.2 Desktop User Interface above and a Windows based PC capable of running
services (Microsoft Windows 2000 and above). For the
This is a dialog based Windows client suitable for connection to the network, your PC will also require at
connecting to the monitoring service via TCP for viewing least one available Serial or USB port. To use the web user
and configuring the network status and events. This client interface component, you must ensure a suitable ASP.
provides full access to all logged and real-time monitoring Net enabled web server is installed. This web interface
events as well as the ability to perform simple commands is designed for all standard compliant browsers, such
such as enable, disable and analogue value retrieval. Internet Explorer 6 and above, Mozilla, Opera, Safari...etc.
Depending on your edition, this software may require a
license key.
This will connect the client to the local service but by Disable Yes Yes Yes -
Commands
clicking on the spanner icon, you can edit the local server
settings and enter the appropriate network address if View Logs Yes Yes Yes Yes
required (please refer to section 2.2 for more details). View Status Yes Yes Yes Yes
Please note that passwords are case sensitive. Every time Generate Yes Yes Yes Yes
you load the graphical user interface, you will be required Reports
to re-login. Clear History Yes Yes Yes Yes
Log
>S
ystem Administrator: Full access for setup and
system management. The default account ‘admin’ is set
to this.
>N
etwork Administrator: Reduced access for setup and
network management.
>T
echnician: For the typical user who wishes to
view network status and logs, and to allow ‘Level 2’
equivalent control (e.g. enable/disable devices, global
reset, global silence... etc).
>V
iewer: Highly restricted user who can only view
network status.
The setting ‘RSS Auth Code’ is used only by the web user
interface and should be pre-filled with a cryptic value.
This enables RSS and Atom feeds to be supported by
compatible readers. We recommend that only unique and
3.2 Users in-guessable values be entered here. Additionally, if you
Site Monitor is designed to enable local and remote want to disable support for RSS and Atom feeds for this
access, and so to ensure security is maintained, access particular user, you can simply delete the value and leave
is restricted to specific username and passwords. There it blank.
are also four available access levels which users can be All users can change their own language and password.
assigned to. These ensure only the right individuals can We recommend that most systems have at least two
access the appropriate features of Site Monitor. The default System Administrators to protect against password loss.
‘admin’ account is configured to enable full access, and
so via that account you can create as many users as your 3.3 Networks
system requires.
A network represents a single connection to a panel
network. If the service PC has more than one serial/USB
port, then it is possible to connect and manage multiple
networks from a single PC. However, in almost all cases,
only a single network is required.
3.4 Events
Site Monitor is designed to run automatically and
continuously, ensuring network activity is logged and users
have a portal in which to quickly and remotely view the
status of the network. As it is almost certain that incidents
will occur while the a user is not observing, you can setup
automated actions to run when specific conditions are
met. A typical example is an email sent to a technician
whenever a panel detects a fault.
NNote: Only System Administrators can setup events.
3.5 Reports
To simplify monitoring of past events, you can quickly
generate HTML reports. When generating a report, you
will prompted for the report type and the start and end
times of the information included in the report. By default
the start and end times will be set to the last 24 hours.
You will then be asked to provide a location in which
to save the report. Please be patient once the report
generation as begun, as some systems which have been
running for a long time will contain a lot of data and it may
take a short period of time to generate and transfer the
report to your system. Once a report has been made, it
will automatically be opened and displayed.
3.5.1 Interface History
This represents all the messages stored by the service.
This will reflect information such as completed device/
zone scans, any detected problems (such as connection
issues, bugs or setup errors) and more.
3.4.1 Conditions 3.5.2 Network History
Any packet received from the network can be used has a This is a record of all packets received off the network.
condition. This means that actions can be triggered if any This is essentially a log of everything that has occurred
panel is manually reset, goes into alarm, detects a fault and includes information such as resets, faults, alarms,
and much more. enabled/disabled commands and much more. This report
3.4.2 Actions is very similar to the history log that appears in Desktop
and Web User Interfaces.
When a condition is met, its associated actions will be
processed. Presently you can only define a ‘Send Email’
action, which allows you to send a brief description of
the incident to a specific email address. To send the
email to multiple addresses, separate the addresses in
the ‘To’ field with ‘;’ characters (e.g. address1@domain.
com;address2@domain.com).