40-08646-00rev000 QNet4100 User Manual

User Manual
QNet4100
Alarm and Event Management System
Document ID: 40-08646-00 Rev000
www.qualitrolcorp.com
Legal
Information in this document is subject to change without notice. This document is provided to purchasers of
Qualitrol products for use in the installation, operation and servicing of such products. No other use, nor any
reproduction, distribution or the making of any derivatives of this document is authorized, without the express
prior written permission of Qualitrol. Qualitrol endeavors to ensure the accuracy and quality of its published
materials; however, no warranty, expressed or implied, is provided. Qualitrol disclaims any responsibility or
liability for any direct or indirect damages resulting from the use of the information in this manual or products
described in it. Mention of any product or brand does not constitute an endorsement by Qualitrol of that product
or brand.
This document was originally composed in English and was subsequently translated into other languages. The
fidelity of subsequent translations cannot be guaranteed. In case of conflict between the English version and
another language version, the English version takes precedence.
© 2012 - Qualitrol Corporation LLC.
Contents
1 QNet4100 Console Interface

..........................................................................................................4
1.1 Maintenance Port
................................................................................................................................... 4
1.2 Port Groups
................................................................................................................................... 6
1.3 Access Control List (ACL)
................................................................................................................................... 7
1.4 Main ...................................................................................................................................
Menu 9
1.5 Sub...................................................................................................................................
Menus 10
1.6 Prompts
................................................................................................................................... 12
1.7 Terse Command Entry
................................................................................................................................... 12
1.8 Event Printout
................................................................................................................................... 14
1.9 Input Point Type (S,D,X,G)
................................................................................................................................... 15
1.10 Scope of Inputs (M, R, S)
................................................................................................................................... 16
1.11 Headers
................................................................................................................................... 19
1.12 Time...................................................................................................................................
Synchronization 19
1.13 Trained Oscillator
................................................................................................................................... 21
1.14 Time...................................................................................................................................
Quality 22
1.15 Equipment Configuration
................................................................................................................................... 23
1.16 XMODEM File Transfer
................................................................................................................................... 24
1.17 Console Commands (English)
................................................................................................................................... 25
1.17.1 ? Context Help 26
1.17.2 AR Adjust User Roles 26
1.17.3 AU Add New User 27
1.17.4 CH Clear History 28
1.17.5 CP Change Password 28
1.17.6 CW Clear Window States 29
1.17.7 DL Download Audit Log from QNet 30
1.17.8 DM Debug Mode 31
1.17.9 DN Download Configuration from QNet 35
1.17.10 DP Default System Password 36
1.17.11 DP Delete Port 37
1.17.12 DS Default System Configuration 37
1.17.13 DU Delete User 38
1.17.14 ED Enable/Disable DHCP 38
1.17.15 EI Enable/Disable IP Fowarding 39
1.17.16 EH Edit Host Table 40
1.17.17 EN Edit Network Interface 41
1.17.18 ER Edit Routing Table 41
1.17.19 ES Edit Name Servers (DNS) 42
1.17.20 ET Edit Time 43
1.17.21 EX Edit Exceptions 44
1.17.22 LA List Audit Log 45
1.17.23 LC List Configuration sub menu 46
1
Content
1.17.24 LG List Output Group Configuration 46

1.17.25 LI List Input Configuration 48
1.17.26 LL List Legends 49
1.17.27 LN List Network Configuration 50
1.17.28 LO List Output Assignments 51
1.17.29 LP List Port Configuration 52
1.17.30 LQ List QNet Configuration 53
1.17.31 LR List Relay Configuration 54
1.17.32 LV List Version Details 54
1.17.33 LW List Annunciator Windows 55
1.17.34 LU List Users 57
1.17.35 MA Modify Annunciator 57
1.17.36 MB Modify Base Point & Range 59
1.17.37 MC Modify Configuration sub menu 60
1.17.38 MG Modify Output Group Configuration 63
1.17.39 MI Modify Input Configuration 69
1.17.40 ML Modify Legends 70
1.17.41 MM Modify Miscellaneous Settings 72
1.17.42 MN Modify Network sub menu 75
1.17.43 MO Modify Output Assignments 75
1.17.44 MP Modify Ports sub menu 77
1.17.45 MP Modify Ports 78
1.17.46 MQ Modify QNet ID 85
1.17.47 MR Modify Relay Configuration 86
1.17.48 MS Modify Scanners 90
1.17.49 MT Modify Time Sync Configuration 91
1.17.50 MV Modify Vocabulary (Language) 94
1.17.51 MW Modify Annunciators sub menu 95
1.17.52 MW Modify Annunciator Windows 96
1.17.53 MZ Modify Time Zone 97
1.17.54 RA Report Alarm Summary 98
1.17.55 RH Report History 99
1.17.56 RI Report Input State 100
1.17.57 RQ Report QNet ID 100
1.17.58 RT Report Time 101
1.17.59 RU Report Update 101
1.17.60 RW Get Annunciator Report 102
1.17.61 RX Report Exceptions 103
1.17.62 SC Save Configuration Changes 103
1.17.63 SS Simulate Scanners 104
1.17.64 SW Send Configuration to Annunciator 104
1.17.65 TA Test Annunciators 105
1.17.66 TW Test Watchdog 106
1.17.67 TS Test Scanners 106
1.17.68 UL User Login 108
1.17.69 UO User Logout 109
1.17.70 UP Upload Configuration to QNet 109
1.17.71 XQ Reset QNet System 110
1.18 Modifications requiring a reboot
................................................................................................................................... 110
1.19 Frequently Asked Questions
................................................................................................................................... 111
1.19.1 How do i recover a lost password? 111
1.19.2 How do I change a users role? 111
2
2 Web Interface
..........................................................................................................112
2.1 History display
................................................................................................................................... 113
2.2 Exceptions display
................................................................................................................................... 117
2.3 Summary display
................................................................................................................................... 118
3 Java User Interface Configuration editor

..........................................................................................................119
3.1 System Configuration tab
................................................................................................................................... 122
3.2 Time Configuration tab
................................................................................................................................... 126
3.3 Network Configuration tab
................................................................................................................................... 128
3.4 Port Configuration tab
................................................................................................................................... 131
3.5 Scanner Configuration tab
................................................................................................................................... 133
3.6 Diagnostic Configuration tab
................................................................................................................................... 137
3.7 Group Configuration tab
................................................................................................................................... 140
3.8 Annunciator Configuration tab
................................................................................................................................... 144
4 Appendix A - Timezones
..........................................................................................................147
4.1 Region
................................................................................................................................... 147
4.2 Country (by Region)
................................................................................................................................... 148
4.3 Time zone (by Country and Region)
................................................................................................................................... 150
5 Coordinated Universal Time

..........................................................................................................162
6 Glossary
..........................................................................................................162
7 Copyright
..........................................................................................................162
Index
................................................................................................................165
3
QNet4100 User Manual
1 QNet4100 Console Interface

The 'Console' interface provides and intuitive and user friendly, plane language user interface with command
arranged in various menus for configuration and operation of the QNet4100.
The maintenance port (Port 0), at the front of the QNet4100 controller module, always provides a 'Console'
command interface, however, the 'Console' command interface can also be assigned to any of the other serial
ports or to TCP Network ports.
The maintenance port (Port 0) must be used for initial configuration of the system and also some special
commands for troubleshooting and maintenance of the system.
1.1 Maintenance Port

The maintenance port at the front of the QNet4100 controller module allow for initial configuration of the system
and both RS232 and a Universal Serial Bus (USB) connections are provided.
Communications to the maintenance port requires a VDU terminal or a PC running terminal emulation software
such as Hyperterminal (provided with Microsoft Windows XP and earlier versions of the Microsoft Windows
operating system) or PuTTy (available from http://www.putty.org).
Upload and Download of configuration and log to and from the QNet4100 requires terminal emulation software
that supports XMODEM file transfer. Files are transferred in GZip compressed format and can be decompressed
using most decompression utility software such as WinZip, WinRAR, 7Zip, etc.
For RS232 serial communications to a PC a standard DE9F (female - PC) to DE9M (male - QNet) or DB25M
(male - PC) to DE9M (male - QNet) cable is required. The following table shows the pin out for both types of
cables:
Maintenance Port (Port 0) RS232 Serial Connections

PC - DTE QNet4100 - DCE
Signal Name Pin (DE9F) Pin (DE25M) Direction Pin (DE9M) See Notes
Protective Ground - 1 <----> Shell note 3
Data Carrier Detect (DCD) 1 8 <---- 1 note 2 (+V)
Receive Data (RXD) 2 3 <---- 2
Transmit Data (TXD) 3 2 ----> 3
Data Terminal Ready (DTR) 4 20 ----> 4 note2 (N/C)
Signal Ground (GND) 5 7 <----> 5
Data Set Ready (DSR) 6 6 <---- 6 note 2 (+V)
Request To Send (RTS) 7 4 ----> 7 note 2 (N/C)
Clear To Send (CTS) 8 5 <---- 8 note 2 (+V)
Ring Indicator (RI) 9 22 <---- 9 note 2 (N/C)
Note:
1. This table applies to the maintenance port (Port 0) only. Port 0 is configured as a Data Communications
Equipment (DCE) connection whereas the other ports (Ports 1 thru 5) are configured as Data Terminal
Equipment (DTE) connections. Signal naming convention is with respect to the Data Terminal Equipment
(DTE) in this case the PC.
2. The maintenance port does not support any modem handshaking signals; only data transmit and receive
4
signals are provided. The Data Carrier Detect (DCD), Data Set Ready (DSR) and Clear To Send (CTS)
signals are connected to the to +V and are always asserted. The Data Terminal Ready (DTR), Request
To Send (RTS) and Ring Indicator (RI) signals are not internally connected at the QNet4100.
3. The protective ground is connected to the body of the connector at the QNet4100 chassis and should be
connected to the cable shield, however the shield should be connected at one end only, either at the PC
or at the QNet4100.
For Universal Serial Bus (USB) communications a standard USB-Type-A (PC) to USB-Type-B (QNet) cable is
required. A USB driver for Microsoft Windows is provided on the QNet4100 system CD. The driver will create a
virtual serial port ('COM' port) on your PC to allow for communications with the terminal emulation software.
The default configuration for the maintenance port is 38400 baud, 8 data bits, no parity and 1 stop bit (38400 8-
N-1), for all times in Coordinated Universal Time (UTC) and is assigned to port group 1.
These parameters may be changed using the 'MP Modify Ports' command.
Note:
The 'port name' for the maintenance port, used with the 'MP Modify Ports' command is 'Port0'. The
name is case sensitive and should be entered exactly as shown.
The maintenance port is always configured as Console interface. The Console interface provides commands
arranged in various menus for configuration and operation of the QNet4100. After initial configuration via the
maintenance port, any other serial ports or Network ports can established and configured for 'Console' protocol
and used for configuration and operation of the QNet4100, although for security reasons certain commands are
restricted to the maintenance port only!
For RS232 serial communications, using Port 1 through Port 5, to a PC a 'null modem' DE9F (female - PC) to
DE9F (female - QNet) or DB25M (male - PC) to DE9F (female - QNet) cable is required. The following table
shows the pin out for both types of cables:
Port 1 through Port 5 RS232 Serial Connections

PC - DTE QNet4100 - DCE
Signal Name Pin (DE9F) Pin (DE25M) Direction Pin (DE9M) See Notes
Protective Ground - 1 <----> Shell note 5
Data Carrier Detect (DCD) 1 8 <---- NC or 4 note 3
Receive Data (RXD) 2 3 <---- 3
Transmit Data (TXD) 3 2 ----> 2
Data Terminal Ready (DTR) 4 20 ----> 6 note 2
Signal Ground (GND) 5 7 <----> 5
Data Set Ready (DSR) 6 6 <---- 4 note 2
Request To Send (RTS) 7 4 ----> 8 note 2
Clear To Send (CTS) 8 5 <---- 7 note 2
Ring Indicator (RI) 9 22 <---- NC note 4
Note:
1. This table applies to Port 1 through Port 5 only. Port 0 is configured as a Data Communications
Equipment (DCE) connection whereas the other ports (Ports 1 thru 5) are configured as Data Terminal
Equipment (DTE) connections. Signal naming convention is with respect to the Data Terminal Equipment
(DTE) in this case the PC.
2. Port 1 through Port 5 provide support for modem handshaking signals for Data Set Ready (DSR), Data
Terminal Ready (DTR), Clear To Send (CTS) and Ready To Send (RTS) although the MP Modify
Ports command allows the DTR and RTS signals to be ignored.
5
3. The Data Carrier Detect (DCD) signal is an input to the QNet4100 and is provided to allow for the
QNet4100 to be connected directly to a modem. It should not be connected when using a serial port for
connection directly to another DTE device (such as a PC).If the PC software requires the DCD signal to
be asserted the should be connected to the Data Set Ready (DSR) from the QNet4100 (Pin 4).
4. The QNet4100 does not support the Ring Indicator (RI) signal. This signal is not connected in the
QNet4100.
5. The protective ground is connected to the body of the connector at the QNet4100 chassis and should be
connected to the cable shield, however the shield should be connected at one end only, either at the PC
or at the QNet4100.
The commands available to a 'Console' interface are controlled by the 'Access Control List'.
See also:
Port Groups
MP Modify Ports
Access Control List
HyperTerminal XMODEM File Transfer
1.2 Port Groups

Port groups are used to route inputs to a set of communications ports or to group a set of inputs for use with
output groups.
Inputs are mapped to a port group using the MO Modify Output Assignment command. And, when a
communications port is created using the MP Modify Ports command, the communications port is assigned
to a port group and all points assigned to the port group are routed to that communications port.
Port groups can also be used within input expression, filter expression or the output list of an output group. The
following table provides a list of macros that use the port group:
Macro Input/Output Function

C(x) Output Clear or reset alarms for a port group (x). (See also AdviSER Alarm Sequence)
K(x) Output Acknowledge alarms for a port group (x). (See also AdviSER Alarm Sequence)
N(x) Input Macro will be TRUE when any input to the port group (x) is in the unacknowledged
return-to-normal condition. (See also AdviSER Alarm Sequence)
O(x) Input Macro will be TRUE when any input to the port group (x) is in the unacknowledged
alarm condition. (See also AdviSER Alarm Sequence).
P(x) Input Macro will be TRUE when any input to the port group (x) is in the alarm condition.
Input macros can used as part of a output group, input or filter expression. For example:
The following configures output group, point 3 to respond when any input in port group 1 (P1) is in the alarm
condition and is used to initiate relay 1 (R1).
MC>MG<cr>
Modify Output Group Configuration
Output rule expression modifications are not in effect immediately.
Modifications will become effective after save and reboot only.
Multipoint, Range, Single (M,R,S)? S<cr>
Point (1..4096)? 3<cr>
3 Point is not configured
Input expression? []P1<cr>
6
Filter expression? []<cr>
Filter delay type (0,1,2,3)?[0]<cr>
Output list? R1<cr>
Multipoint, Range, Single (M,R,S)?<cr>
Modify Output Group Configuration complete
MC>
Output macros can can be used with in on output list to affect all points in a port group. For example:
The following configures output group, point 4 to acknowledge all points in the port group 1 (K1) when the
input expression becomes true. In this case the input expression is a single scanner point input (S157).
MC>MG<cr>
Modify Output Group Configuration
Output rule expression modifications are not in effect immediately.
Modifications will become effective after save and reboot only.
Point (1..4096)? 4<cr>
4 Point is not configured
Input expression? []S157<cr>
Filter expression? []<cr>
Filter delay type (0,1,2,3)?[0]<cr>
Output list? K1<cr>
Modify Output Group Configuration complete
MC>
See also:
MO Modify Output Assignment command
MP Modify Ports command
MG Modify Output Group Configuration command
1.3 Access Control List (ACL)

The Access Control List controls which commands are available to a user. Each user of the QNet4100 system
is allocated a 'role' and the commands that are available on the Main Menu for a role (and therefore the user)
can be ether enabled or disabled.
There are 5 predefined roles and 2 undefined roles:

Security: This role is intended for user(s) who will administer the security privileges of other users. By
default only the commands necessary to add and remove users and adjust user roles are
provided for the security user.
Legacy: This role is the 'all users' role. It defines which commands are available when the system is first
powered up or when no individual user is logged in to the QNet4100 system. Commands that are
available for the legacy role can also be protected by the system password (although we
recommend that user level security is implemented and 'privileged' commands are removed from
the legacy role such that an individual must login to use such commands).
Engineer: This role is intended for user(s) who will administer the system input and output parameters and
perform troubleshooting tasks. By default the user has access to the Modify and List
Configuration sub menus and the special maintenance commands.
Operator: This role is intended for day-to-day user(s) who may need to perform routine system tests as well
7
as having access to the system alarm and historical event reports. By default the user has
access to the
Monitor: This role is intended for day-to-day user(s) who only need having access to the system alarm
and historical event reports.
User1 & These roles are undefined and may be used customer specific user(s) needs.
User2:
The following table shows the default configuration for the Main Menu commands that are enabled or disabled
for each role:
Console Commands Security Legacy Password Engineer Operator Monitor
RA Report Alarm Summary Disabled Enabled Disabled Enabled Enabled Enabled

CP Change Password Enabled Enabled Enabled Enabled Enabled Enabled
RH Report History Disabled Enabled Disabled Disabled Enabled Enabled
TS Test Scanners Disabled Enabled Disabled Enabled Enabled Enabled
RU Report Update Disabled Enabled Disabled Disabled Enabled Enabled
TW Test Watchdog Disabled Enabled Enabled Enabled Disabled Disabled
RI Report Input State Disabled Enabled Disabled Enabled Enabled Enabled
RX Report Exceptions Disabled Enabled Disabled Enabled Enabled Enabled
EX Edit Exceptions Disabled Enabled Enabled Enabled Enabled Enabled
RT Report Time Disabled Enabled Disabled Enabled Enabled Enabled
TA Test Annunciators Disabled Enabled Disabled Enabled Enabled Enabled
RQ Report QNet ID Disabled Enabled Disabled Enabled Enabled Enabled
LC List Configuration sub menu Disabled Enabled Disabled Enabled Disabled Disabled
MC Modify Configuration sub Disabled Enabled Enabled Enabled Disabled Disabled
menu
CH Clear History Disabled Enabled Enabled Enabled Disabled Disabled
DP Default Password Disabled Enabled Disabled Enabled Disabled Disabled
DS Default System Disabled Enabled Enabled Enabled Disabled Disabled
SS Scanner Simulation Disabled Enabled Enabled Enabled Disabled Disabled
DM Diagnostic Mode Disabled Enabled Disabled Enabled Enabled Enabled
SH Shell Disabled Enabled Disabled Enabled Disabled Disabled
AR Adjust User Roles Enabled Disabled Disabled Disabled Disabled Disabled
LU List Users Enabled Disabled Disabled Disabled Disabled Disabled
AU Add New User Enabled Disabled Disabled Disabled Disabled Disabled
DU Delete User Enabled Disabled Disabled Disabled Disabled Disabled
Notes:
1. The User1 and User 2 roles are not defined and for the default configuration all commands are disabled.
2. The Password column in the above table applies to the system level password and the all users (legacy role)
only. Individual users each have their own password which must be entered at UL User Login command.
When a user has logged in they have assess to the Main Menu commands provided for their assigned role
without the need to enter the system level password or re-entry of their individual password.
3. The ? Context Help command is always to available to all users and appears on all menus.
4. The UL User Login command is always available on the main menu for the all users (legacy role).
5. The UO User Logout command is always available on the main menu for user roles other than the all
users (legacy role).
8
See also:
Security Role Main Menu commands
UL User Login command
UO User Logout command
1.4 Main Menu

With the exception of the context help, console commands are initiated with two keyboard characters plus a
carriage return (<cr>).
The commands available on the Main Menu are dependent on the role of the current user and the access rights
assigned for that users role via the Access Control List (ACL); some commands may be available to all user
(legacy role) while other commands may be privileged commands only available after a user login.
Using the ? Context Help command (?<cr>) at a command prompt will display the commands that are
currently available to the user.
Default all users (legacy role):
The factory default configuration provides for the following Main Menu commands available to all users
(legacy role):
? Context Help UL User Login

RA Report Alarm Summary CP Change Password
RH Report History TS Test Scanners
RU Report Update TW Test Watchdog
RI Report Input State
RX Report Exceptions EX Edit Exceptions
RT Report Time TA Test Annunciators
RQ Report QNet ID
LC List Configuration sub menu MC Modify Configuration sub menu
Port 0 only:
The following Main Menu commands are available only from the maintenance port (Port 0):
CH Clear History
DM Diagnostic Mode
DS Default System
DP Default System Password
SS Scanner Simulation
These are not shown on the Main Menu but can be accessed by typing the two letter command at the Main
Menu prompt (>).
Security Role:
The factory default configuration provides the following commands for maintenance of the access control
list.
These commands are only available to users with the Security Role after User Login:
9
? Context Help UO User Logout

CP Change Password
AR Adjust User Roles LU List Users
AU Add New User DU Delete User
UP Change User Password
System level password protected:

The factory default configuration provides system level security and some commands will prompt for the
system password to be entered before the command can be executed.
The requirement for entry of a system password for a command available to all users (legacy role) is also
controlled by the Access Control list (ACL) and the requirement can be added or removed for any
command.
The default configuration requires entry of the system password for the following commands:
CP Change Password
TW Test Watchdog
EX Edit Exceptions
MC Modify Configuration sub menu
CH Clear History
DS Default System Configuration
SS Scanner Simulation
The default 'system password' is QNET.
See also:
Access Control List (ACL)
1.5 Sub Menus

In addition to the commands provided at the Main Menu several sub menus are provided for the system
configuration:
Modify Configuration sub menu:
MQ Modify QNet ID LQ List QNet Configuration

MS Modify Scanners
MB Modify Base Point & Range
MZ Modify Time Zone
MT Modify Time Sync Configuration
MM Modify Miscellaneous Settings
MI Modify Input Configuration LI List Input Configuration
ML Modify Legends LL List Legends
MR Modify Relay Configuration LR List Relay Configuration
MG Modify Output Group Configuration LG List Output Group Configuration
MP Modify Ports sub menu LP List Port Configuration
MW Modify Annunciators sub menu LW List Annunciator Windows
MN Modify Network sub menu LN List Network Configuration
MO Modify Output Assignments LO List Output Assignments
MV Modify Vocabulary (Language)
10
SC Save Configuration Changes LA List Audit Log
UP Upload Configuration to QNet DN Download Configuration from QNet
XQ Reset QNet System DL Download Audit Log from QNet
ET Edit Time
MC>
Note:
The List Ports Configuration command is also available from the Modify Ports sub menu.
The List Network Configuration command is also available from the Modify Network sub menu.
The List Annunciator Windows command is also available from the Modify Annunciators sub menu.
Modify Ports sub menu:

DP Delete Port Configuration LP List Port Configuration
MP Modify Port Configuration
MP>
Modify Network sub menu:

ED Enable/Disable DHCP LN List Network Configuration
EI Enable/Disable IP Forwarding
ES Edit Named-Servers (DNS)
EN Edit Network Interface
EH Edit Host Table
ER Edit Routing Table
MN>
Modify Annunciators sub menu:

MA Modify Annunciator LW List Annunciator Windows
MW Modify Annunciator Windows
SW Send Configuration to Annunciators
RW Get Annunciator Report
CW Clear Window States
MW>
List Configuration sub menu:

LQ List QNet Configuration
LI List Input Configuration
LL List Legends
LR List Relay Configuration
LG List Output Group Configuration
LN List Network Configuration
LP List Port Configuration
LO List Output Assignments
LW List Annunciator Windows
LA List Audit Log
LV List Version Details
LC>
Note: All List Configuration sub menu commands are also available from the Modify Configuration sub
menu.
See also:
Access Control List
11
1.6 Prompts
The command prompt provided at for the main menu and each sub menu are unique and allows for easy
identification of the current menu level; pressing the carriage return key (<cr>) at a menu level will display the
prompt for that menu level:
Command Prompt Menu

> Main Menu
LC> List Configuration sub menu
MC> Modify Configuration sub menu
MP> Modify Ports sub menu
MN> Modify Network sub menu
MW> Modify Annunciators sub menu
Commands that require additional information respond with a prompt, normally in the form of a question followed
by a question mark (?). If the prompt is for a specific configuration parameter additional information will normally
be provided, such as the acceptable range for the parameter shown within parenthesis ('(' and ')') and the
existing setting shown within brackets ('[' and ']').
For example:
The MB Modify Base & Range command will display the following prompt: First scanner point
(0..28000)? [1].
The prompt indicates that the acceptable range for the value is a number between 0 and 28000:
(0..28000), and that the current value is 1: [1].
The user can either enter a new value or accept the existing value by entering a carriage return (<cr>)
alone.
See also:
? Context Help
1.7 Terse Command Entry

The QNet4100 Console interface allows for both prompted and terse command entry.
Responding to a prompt and pressing carriage return will normally cause the system to respond with the next
prompt. However, the terse mode allows the responses to preempt the prompts. For example:
The RH Report History command allows the user to request a report of historical events. The
command will prompt for 'Point numbers', Start date, Start time; End date, End time, Number of Historical
Events, and will report the events that match the criteria:
>RH<cr>
QNet4100
Station number: 1
3 Feb 2012 12:25:33
Report History
Point numbers (All, or up to ten points - S,D,X,G followed by number)? A<cr>
Start date (All, or MM/DD/YY)? 02/01/12<cr>
Start time (HH:MM:SS)? 00:00:00<cr>
End date (MM/DD/YY)? 02/03/12<cr>
12
End time (HH:MM:SS)? 23:59:59<cr>
Number of historical events (1..100000 or All)? 100<cr>
Events reported matching entered criteria
Report History complete
>
The following terse command line produces the same result:
>RH;A;02/01/12;00:00:00;02/03/12;23:59:59;100<cr>
QNet4100
Station number: 1
3 Feb 2012 19:35:58 f
Report History
Events reported matching entered criteria
>
The semi colon (;) is used to separate the responses and effectively represent the carriage return. The
system takes each entry in the command line and matches it with the next prompt. If the entry is valid it
will not display the prompt and will evaluate the next entry. If all entries are valid the command will execute
successfully.
If an entry is not valid the system will display 'invalid entry' and will display the prompt. If this occurs all
remaining characters of the terse command line will be ignored and the system will prompt for the remaining
entries.
Terse entry can also be used within commands. For example:
The 'MS Modify Scanners' command will prompt for 'Scanner(s) to enable' and 'Scanner(s) to disable':
MC>MS<cr>
Modify Scanners
Scanner(s) to enable (1..64)? [1 8]2<cr>
Scanner(s) to enable (1..64)? [1 2 8]5<cr>
Scanner(s) to enable (1..64)? [1 2 5 8]<cr>
Scanner(s) to disable (1..64)? [3 4 6 7 9..64]8<cr>
Scanner(s) to disable (1..64)? [3 4 6..64]<cr>
Modify Scanners complete
MC>
Here the user enabled scanners 2 and 5 and disabled scanner 8.
The following would have the same result;
MC>MS<cr>
Modify Scanners
Scanner(s) to enable (1..64)? [1 8]2;5;;
Scanner(s) to disable (1..64)? [3 4 6 7 9..64]8;;
MC>
13
In a command the requires a carriage return alone to terminate an entry list, two semi colons (;;) can be
used to signify the end of the entry list.
The same command could be entered as a single line terse command;
MC>MS;2;5;;8;;<cr>
Modify Scanners
MC>
The maximum numbers of characters that can be used in a terse command line is 255.
Passwords cannot be entered on a terse command line; user must explicitly enter password at the password
prompt followed by a carriage return.
1.8 Event Printout

All events are displayed and printed with the 'Status', 'Time', 'Point reference' followed by the 'Legend'.
'Status' is either one or two characters:
Status Characters
A The point changed state from the normal condition to the alarm condition.
N The point changed state from the normal condition to the alarm condition.
D The point was deleted from logging. (See 'Automatic Delete from and Restore to Logging').
L The point was restored to the logging condition.
FA The point failed the to enter the alarm condition during a scanner functional test, and is stuck
in the normal condition. (See 'Scanner Functional Test')
FN The point failed the to enter the normal condition during a scanner functional test, and is stuck
in the alarm condition. (See 'Scanner Functional Test')
'Time' is displayed in 24 hour, hh:mm:ss.nnn format as either Coordinated Universal Time (UTC) or Local
depending on the port configuration.
'Point reference' provides a unique identifier for each point in the system and is the point type (either S, D, X or
G) followed by a unique number (nnnn):
Point Reference
S#nnnn Hardware scanner input point.
Scanner points are normally in the range of 1 to 4096, with point 1 being the first input of the
first scanner. However, 'first scanner point' and 'last point' can be changed using the 'MB Modify
Base Point and Range' command and will change this range. (See 'MB Base Point & Range'
command).
D#nnnn Internal diagnostic alarm point representing various system status conditions. Diagnostic
alarms have a range from 1 to 232. (See 'Diagnostic Alarms').
X#nnnn A external input point captured by the system via a communications channel from another
system. External points can range from 1 to 4096 but the actual range will depend on the
external input service provider. (See 'External Input Services').
G#nnnn A group point, generated as a result of a Boolean expression. Group points can range from 1 to
4096. (See 'MG Modify Output Group Configuration' command).
14
'Legend' is a user defined description for each unique point. Each point has a separate description up to 60
characters in length, and if 'Separate-return-to-normal legends' is enabled, then a second description, also up to
60 characters in length, is available and will be displayed when the point returns to the normal condition. (See
'MM Modify Miscellaneous Settings' command)
The following is an example of a typical event printout:
A 16:14:52.625 S# 98 CONDENSER LEVEL HIGH

N 16:15:30.980 S# 98 CONDENSER LEVEL NORMAL
The above example shows that at 14 minutes and 52.625 seconds past 4 pm (16:14:52.625) scanner point
number 98 (S# 98) went into an alarm (A) condition. The alarm legend or description for scanner point 98 is
"CONDENSER LEVEL HIGH".
Then at 15 minutes and 30.980 seconds past 4 pm (16:15:30.980), scanner point 98 (s# 98) returned-to-
normal (N) condition. The return-to-normal legend or description for scanner point 98 is "CONDENSER LEVEL
NORMAL".
The Alarm event is indented 2 spaces; this allows Alarm and Return-to-normal events to be easily distinguished.
The 'Event Indent' setting of the 'MM Modify Miscellaneous Settings' command allows for either alarm or return-
to-normal events to be indented. (See 'MM Modify Miscellaneous Settings' command).
1.9 Input Point Type (S,D,X,G)

Commands that are used to modify or display information about system input points will prompt for the type of
input.
Alarm and event points can one of four types:
Point Type Description

Scanner (S) Input from one of the systems Scanner Modules.
Diagnostic (D) Internally generated event indicating system status.
External (X) Input from an external device communicated to the system via communications port.
Group (G) Internally generated event based on a Boolean or mathematical expression combining other
input.
When using commands to either configure or report inputs points the system will prompt for the input type as
follows:
Sc a n n e r , Di a g n o s t i c , Ex t e r n a l , Gr o u p ( S, D, X, G) ?
For example;
using the MI Modify Input Configuration command to change the input parameters:
MC>MI<cr>
Modify Input Configuration
Scanner, Diagnostic, External, Group (S,D,X,G)? S<cr>
...
Modify Input Configuration complete
15
MC>
using the RI Report Input State command to determine the current state of one or more inputs:
>RI<cr>
QNet4100
Station number: 1
13 Apr 2012 15:48:52 f
Report Input State
...
Report Input State complete
>
1.10 Scope of Inputs (M, R, S)

In many cases the system will prompt for the scope of input points to be reported or to be changed.
The system will prompt for the scope of input points as follows:
Multipoint, Range or single (M, R, S)?
Entering M<cr> in response to the Multipoint, Range or single (M, R, S)? prompt will allow
changes or reports for a series of points without having to re-enter the input point scope.
If the command is a report or list type command, the system will display the report for the point and will
then prompt for the next point. Entering a carriage return ('< c r > ') without first entering a point number will
terminate the multipoint list and prompt for the next input type:
LC>LI<cr>
List Input Configuration
Multipoint, Range or single (M, R, S)? M<cr>
Point (1..4096)? 37<cr>
point 37 report
...
Point (1..4096)? 48<cr>
point 48 report
...
Point (1..4096)? <cr>
Scanner, Diagnostic, External, Group (S,D,X,G)?
If the command is a modify type command, the system will prompt for any additional information required
and will then ask if that 'same data' applies to the subsequent points. If the same data applies to
subsequent points the system will prompt for the subsequent points to apply the data to. Entering a
carriage return ('< c r > ') without first entering a point number will terminate the multipoint list and prompt for
the next input type:
MC>MI<cr>
16
Point (1..4096)? 37<cr>
prompts for point 37 configuration information
...
Same data? Y<cr>
Point (1..4096)? 48<cr>
Point (1..4096)? <cr>
If the same data is not applied to the subsequent points the system will prompt again for the additional
information required:
MC>MI<cr>
Point (1..4096)? 37<cr>
...
Same data? N<cr>
Point (1..4096)? 48<cr>
...
Same data? N<cr>
Point (1..4096)? <cr>
Entering R<cr> in response to the Multipoint, Range or single (M, R, S)? prompt will allow
changes or reports for a contiguous range of input points.
If the command is a report or list type command, the system will prompt for the start point and end point
and will then display the report for the the entered range. After displaying the range the system will prompt
for the next input type:
LC>LI<cr>
Multipoint, Range, Single (M,R,S)? R<cr>
Start point (1..4096)? 1<cr>
End point (1..4096)? 10<cr>
point 1 through 10 report
and will then ask if that 'same data' applies to all points in the range. If the same data applies the system
will apply the data to all points in the range and will then prompt for the next input type:
MC>MI<cr>
Multipoint, Range or single (M, R, S) [S]? R<cr>
Start Point (1..4096)? 1<cr>
End Point (1..4096)? 10<cr>
prompt for point 1 configuration information
17
Same data (Y,N) [N]? Y<cr>

If the same data is not applied to the range the system will prompt again for the additional information
required for the next point in the range (point 2). This will continue until data has been entered for all point in
the range:
MC>MI<cr>
Multipoint, Range or single (M, R, S) [S]? R<cr>
Start Point (1..4096)? 1<cr>
End Point (1..4096)? 10<cr>
Same data (Y,N) [N]? N<cr>
prompt for next point configuration information
Same data (Y,N) [N]? N<cr>
...
prompt for last point configuration information
Entering S<cr> in response to the Multipoint, Range or single (M, R, S)? prompt will allow
changes or report for a single of input point.
If the command is a report or list type command, the system will prompt for the point number, will display
the report for that point and will then prompt for the next input type:
LC>LI<cr>
Point (1..4096)? 28<cr>
point 28 report
and apply the changes to the point and will then prompt for the next input type:
MC>MI<cr>
Multipoint, Range or single (M, R, S) [S]? S<cr>
Point (1..4096)? 28<cr>
Entering anything other than M<cr>, R<cr>, S<cr>, or <cr> in response to the Multipoint, Range or
single (M, R, S)? prompt will cause the system to re prompt for Multipoint, Range or single
(M, R, S) [S]? again until a valid response is received.
18
1.11 Headers
A header including the 'station name', station number, date and time is printed at the top of each report to allow
for the source of the printed reports to b easily identified.
The header is format as follows:

<station name>
Station number: <station Number>
DD MMM YYYY hh:mm:ss
Where
<station name> = the user programmed station name up to 60 characters in length, (See 'MQ Modify
QNet ID' command),
<station number> = the user programmed station number in the range of 1 to 255 (See 'MQ Modify
QNet ID' command),
DD = day of the month,
MMM = month in three letter form (Jan, feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec),
YYYY = year,
hh = hour,
mm = minutes,
and ss = seconds.
For example:
>RA<cr>
Fairport 235KV Substation
Station number: 3
12 Feb 2012 17:25:24
Report Alarm Summary
report
Report Alarm Summary complete
>
The above printout identifies the station as 'Fairport 235KV Substation', station number '3' with the printout
occurring on 12th February 2012 at 25 minutes and 24 seconds past 5 pm.
See also:
1.12 Time Synchronization

The controller module can accept a variety of precision time source synchronization input signals:
IRIG-B Time code:

The IRIG B time code was created by the Tele-Communications Working Group of the Inter-Range
Instrumentation Group, the standards body of the Range Commanders Council. The original standards were
released in 1960 and was revised and upgraded in 1970 and became IRIG Standard 200. Since 1970 IRIG
standard 200 has undergone several revisions the most recent of which was in 2004.
The IRIG Standard 200-89 standard was widely used in the power industry for time synchronization of various
'intelligent electronic devices' (IED's), and in 1995 the IEEE Standard 1344 for 'Synchrophasers for Power
Systems' was introduced. IEEE Standard 1344 included for 'extensions' to the IRIG B time code format to add
year, local to UTC time offset, time quality, leap second pending and daylight savings pending information.
19
In 2004 the IRIG Standard 200 was revised to include for year information as described in the IEEE Standard
1344-1995 standard but does not include for the additional local to UTC time offset, time quality, leap second
pending and daylight savings pending information.
The IRIG standard 200 includes for 'Pulse Width' un-modulated, Amplitude Modulated' and 'Manchester
Modulated' code. The QNet4100 does supports 'Pulse Width' un-modulated code in the form of a TTL signal or a
Fiber Optic signal, and Amplitude Modulated code. Manchester Modulated code is not supported.
The QNet4100 supports IRIG B code without Year information (per IRIG Standard 200-89), IRIG B code with
Year information (per IRIG standard 200-04) and IRIG B code with IEEE Standard 1344-1995 extensions.
While the IEEE standard defines the time as Coordinated Universal Time (UTC), the IRIG standard standard has
no such definition and the time can be either UTC or Local time.
NMEA:
The National Marine Electronics Association (NMEA) standard 0183 is a combined electrical and data
specification for communication between marine electronic devices including Global Positioning Satellite (GPS)
receivers.
The electrical standard that is used is EIA-422 although most hardware with NMEA-0183 output are able to drive
a single EIA-232 port. The standard also defines the communications parameters as 4800 b/s (bit per second
rate) with 8 bits of data, no parity and one stop bit (4800 8-N-1). The NMEA standard also calls for isolated
inputs and outputs although many devices do not adhere to this requirement.
The QNet4100 allows for a NMEA 0183 connection to either serial port 2, 3 4 or 5. (Ports 0 and 1 cannot be
used for the NMEA time synchronization).
The NMEA 0183 standard uses a simple ASCII, serial communications protocol that defines how data is
transmitted in a "sentence" from one "talker" (typically a GPS receiver), to multiple "listeners" (in this case the
QNet4100) at a time. many of the "sentences" defined by the standard include date and time information.
The QNet4100 supports three types of NMEA0183 "sentences"; the ZDA - Date and Time sentence, GGA - Fix
Information sentence and the RMC - Recommended Minimum Sentence. Of these only the ZDA sentence
provides the date information the other sentences include only the time.
The NMEA time is always defined as Coordinated Universal Time (UTC). The ZDA sentence includes the hour
and minute offset from UTC to Local time zone, however, this information is not used by the QNet4100; the
QNet4100 will calculate local time based on its current time zone setting. (See MZ Modify Time Zone
command).
The NMEA standard does not define a time marker associated with the sentence time although most GPS
receivers provide a pulse-per-second (PPS) marker corresponding the beginning of the sentence. The PPS
marker may be provided as a separate TTL output or as one of the EIA-232 modem signals (Data Carrier Detect
(DCD), Clear to Send (CTS) or Data Set Ready (DTR)). The time marker may also be defined as either the
leading edge or trailing edge of the PPS signal i.e. the rising or falling edge of a TTL signal or the assertion or
removal of the modem signal.
The QNet4100 allows for a PPS input via T1 (time synchronization input) for TTL type signal, or for any of the
modem signal for the port associated with the NMEA data.
PPS (pulse per second):

The precision time source may be defined as a PPS signal without an associated time. The time must be
20
initially manually set or set via one of the QNet4100 communication protocols.
The QNet4100 allows for a PPS input via T1 (time synchronization input) for TTL type signal and the time
marker may also be defined as either the leading edge or trailing edge of the PPS signal.
PPM (pulse per minute) or PPH (pulse per hour)

The precision time source may be defined as a PPM or PPH without an associated time. The time must be
initially manually set or set via one of the QNet4100 communication protocols.
The PPM or PPH input is connected via a scanner module input and the alarm event is considered as the
synchronizing event. For a PPM signal, the alarm event must be received within +/- 5 seconds window of the
expected time and for a PPH input the alarm event must be received within a +/- 5 minute window of the
expected time. An alarm event received outside of this window will be ignored and will not re synchronize the
QNet4100 time.
NTP Network Time Protocol

In addition to the precision time source the controller module may also be configured to use a network time
protocol (NTP) backup synchronization source, if the precision time source is not available the system will
synchronize to the defined NTP server or alternative server.
The resolution of time for NTP synchronization is very dependent on the network topology and availability of time
from the NTP server. An NTP server that is in the same network segment as the controller can give sub
millisecond resolution, however, if the NTP server is in another domain and is separated from the controller by
Ethernet switches, routers or other networking devices or is in a busy network the time resolution can be much
less accurate. It should also be noted that the NTP algorithms are not intended for step change type type
adjustments, if NTP is used the system will make small adjustments to attempt to align and maintain alignment
to the NTP sever time. The actual time resolution can only be determined by testing within the actual
installation environment.
1.13 Trained Oscillator

The trained oscillator uses the external time synchronization signal to calibrate the internal oscillator, such that
if the external time synchronization should fail the internal oscillator can take over and keep the system clock
accurate for at least a short period of time.
The trained oscillator can use either the PHY oscillator or the high stability (HS) oscillator if fitted as its internal
frequency source:
The PHY oscillator has a stability of +/-20 parts per million (ppm) over the temperature range of 0 to 70ºC,
resulting in a maximum drift of +/- 72 milliseconds per hour.
The HS oscillator has a stability of +/-0.1 parts per million (ppm) over the temperature range of 0 to 70ºC,
resulting in a maximum drift of +/- 0.36 milliseconds per hour.
The trained oscillator operates the same regardless of its clock source and has no knowledge of the stability of
the oscillator installed.
The nominal 25MHz signal from either the PHY or HS oscillator is divided down to provide a 1Hz (one pulse per
second) interrupt signal to the main CPU. This signal is compared to the one pulse per second signal derived
from the external time synchronization input source. The trained oscillator can be sped up or slowed down by
adjusting the divider chain; if the 1Hz signal from the trained oscillator is found to be fast the trained oscillator
divisor is increased and if the oscillator signal is found to be slow the trained oscillator divisor is reduced.
Initially the trained oscillator is set to divide by 25,000,000 (plus any offset programmed for the trained oscillator
value using the MT Modify Time Sync Configuration command). Increasing or decreasing divisor
21
allows for adjustment of the 1Hz in increments 1 part per 25 million or approximately +/- 40 nano seconds.
Typically, once trained, the trained oscillator will provide a stability of approximately 5 parts per 25 million (or
approximately 0.2 ppm), and, providing the system temperature is stable this will maintain the clock time to
within +/- 1 milliseconds per hour.
Note: The trained oscillator requires an external precision time synchronization signal via the T0 port.
This may be either an IRIG B or PPS signal (including a PPS associated with a NMEA signal).
See also:
Time Synchronization
MT Modify Time Sync Configuration command.
1.14 Time Quality

A time quality character may be displayed after the date and time in report headers and when the system does
an hourly time print. The time quality character represents the certainty (or uncertainty) of the displayed time
based on the last time the system received a time synchronizing input (either from an external time source or
user input). The following table lists the time quality character and the limits of uncertainty;
Character System Time Uncertainty

<1mS (System is synchronized to an external time source).
a >1mS but <10mS.
b >10mS but <100mS.
c >100mS but <1S
d >1S but <10S
e >10S but <100S
f >100S but <1,000s
g >1,000s but <10,000s
... (This table continues in powers of 10 up to the character z however 10 ^ 26 is a very large
number representing uncertainty of several hundred years!)
At system start up, when the 'ET Edit Time' command is used, or when a serial synchronization source
(such as NMEA without a 1PPS reference) is used, uncertainty is considered to be >100mS but <1S and a
time quality character of 'c' will be displayed. As soon as the system is synchronized to an external source the
time quality character will be cleared. The time quality character changes based on how long it has been since
the system was last synchronized (either from an external time source or user input). The taken for the
character to change is dependent on the calculated worst case drift and depends on the type of synchronization
and if the standard oscillator or the optional high stability oscillator is in use.
The controller module sends time to the scanner modules every thirty seconds, however, the controller module
does not have to be synchronized to an external source for the scanner module synchronization process to take
place.
22
1.15 Equipment Configuration
There is no set order for configuration of the system, however some configuration parameters affect the
execution of other commands:
Command Configuration Other Commands affected

Parameters
MV Modify Vocabulary (Language) Language All commands are affected!
MZ Modify Time Zone Local time zone ET Edit Time
MP Modify Ports UTC/Local time display ET Edit Time
RT Report Time
MB Modify Base Point First scanner point MI Modify Input Configurations
number and Max point ML Modify Legends
number. MG Modify Groups
MO Modify Output Assignments
EX Edit Exceptions
MM Modify Miscellaneous Settings Separate return legends ML Modify Legends
The factory default setting for the Local time zone is 'Amierica/UnitedStates/New_York'. Before using the 'ET
Edit Time' command it is recommended that the Local time zone be set appropriately for the system
installation location. However, it should also be noted that the factory default setting for the maintenance port
(P0) is for times be displayed and entered in Coordinated Universal Time (UTC). If desired, the maintenance port
(P0) may be changed to allow times to be displayed and entered using the Local time zone using. See 'MP
Modify Ports' command
'First scanner point number and 'Max point number' should be set using the before commands that modifying
the scanner input points and groups, output assignments. The factory default setting for 'First scanner point
number' is 1 and 'Max point number' is 64. The 'First scanner point number' setting will change the point
numbers assigned to the scanners and the 'Max point number' setting will restrict the points that can be
configured to those between the 'First scanner point number' and the 'Max point number'. See also 'First
scanner point number' and 'Max point number' for further explanation of these settings.
The 'Separate return legends' parameter should be set before modifying the scanner, external, group or
diagnostic legends. The system will provide either a common point description (legend) for both the alarm and
return-to-normal events or will uses separate descriptions for each.
A suggested sequence of configuring the equipment is as follows:
Step Modify Configuration commands

1 Disconnect the field inputs from the Scanner It is recommended that the field inputs and remote
Modules by removing the J2 and J3 points are disconnected to avoid input status
connectors. changes from interfering with the initial
2 Disconnect or disable Remote Point inputs configuration process.
from the communication ports.
2 Set the system language. MV Modify Vocabulary (Language)
3 Set the station name and number. MQ Modify QNet ID
23
Step Modify Configuration commands

4 Enable the installed scanners. MS Modify Scanners
5 Set the 'Base Point' and 'Maximum Scanner MB Modify Base Point & Range
Point'.
6 Set the local time zone. MZ Modify Time Zone
7 If desired, change the maintenance port to MP Modify Ports sub menu &
used Local Time. MP Modify Ports
8 Set the system time. ET Edit Time
9 Set the system external time synchronization. MT Modify Time Sync Configuration
10 Set the miscellaneous configurations. MM Modify Misc Settings
11 Set the network communication parameters. MN Modify Network sub menu &
12 Add other serial and network communications MP Modify Ports sub menu &
ports. MP Modify Ports
13 Set the port assignments. MO Modify Output Assignments
14 Set the scanner and remote point input MI Modify Input Configuration
configurations.
15 Set the scanner input legends ML Modify Legends
16 Set relay outputs. MR Modify Relay Configuration
17 Set group outputs for the relays and MG Modify Group Outputs
annunciator outputs
19 Set the annunciator parameters and window MW Modify Annunciators sub menu,
assignments. MA Modify Annunciator &
20 Test system configurations. SS Simulate Scanners,
Scanner Simulation software and Remote Point
Simulation software.
21 Set system security parameters. UL Use Login,
AU Add Users &
AR Adjust User roles
22 Clear the system history CH Clear History
23 Re-connect the field inputs to the scanner
modules and remote point communication
ports and put the system into service.
1.16 XMODEM File Transfer

Configuration for the QNet4100 controller module is complex and extensive! As a minimum we highly
recommend the backup of the configuration files to a PC after any significant configuration changes such that
they may be reloaded to a new controller should a failure of the QNet4100 controller module occur.
The configuration files can be downloaded from the controller module using the DN Download
24
Configuration from QNet command.
The QNet4100 configuration is split into 5 down-loadable files:
The System configuration (System)

Scanner Point configuration (Scanner)
External Point configuration (External)
Diagnostic Point configuration (Diagnostic)
Group Points configuration (Group)
Annunciator Window Configuration (Annunciator)
Each file provides a compressed Extensible Markup Language (XML) document containing a portion of the
QNet4100 configuration.
The QNet4100 uses an XMODEM file transfer, and requires terminal software that supports the XMODEM file
transfer protocol, such has HyperTerminal may be used to receive the file.
Compression is used to reduce transfer times; typically the files can contain several megabytes of data but
when compressed the files are reduced to only a fraction of their original size.The the QNet4100 uses the 'gzip'
file format as documented in RFC1952, (a gzip wrapped around a deflate stream).
The files can be saved in their original compressed state as a backup for later upload using the UP Upload
Configuration to QNet command. Or the files may also be extracted, edited, re-compressed and
uploaded to change the QNet4100 configuration.
A windows gzip utility is available from Free Software Foundation, Inc under GNU GENERAL PUBLIC LICENSE.
See http://gnuwin32.sourceforge.net/packages/gzip.htm)
The XML files are created using XML templates stored in the QNet4100. These templates, the xml tags used
and the data represented within the tags are described in the QNet4100 XML reference manual.
1.17 Console Commands (English)

With the exception of the context help, console commands are initiated with two keyboard characters followed
by a carriage return (<cr>).
The commands available on the Main Menu are dependent on the role of the current user and the access rights
assigned for that users role via the access control list (ACL); some commands may be available to all users
(legacy role) while other commands may be privileged commands only available after a user login.
Using the ? Context Help command at a command prompt will display the commands that are currently
available to the user.
See also:
Main Menu
Access Control List
Prompts
25
1.17.1 ? Context Help

The ? Context Help command provides additional help based on the current prompt.
Using the context help command at a command prompt will list the current commands that are available to the
user:
>?<cr>
? Context Help UL User Login
RA Report Alarm Summary CP Change Password
RH Report History TS Test Scanners
RU Report Update TW Test Watchdog
RI Report Input State
RX Report Exceptions EX Edit Exceptions
RT Report Time TA Test Annunciators
RQ Report QNet ID
LC List Configuration sub menu MC Modify Configuration sub menu
>
Using the context help command within a command will, in many cases, provide additional information about
the specific entry.
For example:
The MZ Modify Time Zone command will display the Region? prompt.Using the ? Context Help
command (?<cr>) will display a list of the acceptable values, and will re-prompt for the value:
Region? [America] ?<cr>

Africa America Antarctica Arctic
Asia Atlantic Australia Europe
India Pacific
Region? [America]
1.17.2 AR Adjust User Roles

The AR Adjust User Roles command allows for the main menu commands that available for each user
role to be enabled or disabled.
>AR<cr>
QNet4100
Station number: 1
15 Feb 2012 8:10:11
|||||||||(Security, Legacy, Password, Engineer, Operator, Monitor, User1,
User2)
VVVVVVVVV
-*-***-- RA Report Alarm Summary
******-- CP Change Password
-*--**-- RH Report History
-*-***-- TS Test Scanners
-*--**-- RU Report Update
-***---- TW Test Watchdog
-*-***-- RI Report Input State
-*-***-- R Report Exceptions
-*****-- E Edit Exceptions
26
-*-***-- RT Report Time
-*-***-- TA Test Annunciators
-*-***-- RQ Report QNet ID
-*-*---- LC List Configuration sub menu
-***---- MC Modify Configuration sub menu
-***---- CH
-*-*---- DP
-***---- DS
-***---- SS
-*-***-- DM
-*-*---- SH
*------- AR Adjust User Roles
*------- LU List Users
*------- AU Add New User
*------- DU Delete User
Enter command to modify: RA<cr>
Current: -***---- Enter new setting: ---***--
Enter command to modify: <cr>
ACL do not take effect until reboot
Adjust User Roles complete
>
An asterisk (*) in the role column enables the command while a dash (-) disables a command.
The 'Legacy' role is available to all users when the system is first powered up or when no individual user is
logged in to the QNet4100 system.
The 'Password' column applies to the system level password and the 'Legacy' role only; an asterisk (*) in this
column signifies that the command will ask for, and validate, the system level password before the command
can be used.
See also:
1.17.3 AU Add New User

The AU Add New User command allows user(s) to added to the QNet4100 system.
The command will prompt for the new users name, a password, role assignment and if the user has Web
access to the system.
>AU<cr>
QNet4100
Station number: 1
15 Feb 2012 10:37:39
Enter user name: JoeBloggs<cr>
Enter password: **********<cr>
Reenter password: **********<cr>
Enter user role (E)ngineer,(O)perator,(M)onitor,(S)ecurity,User(1),User(2):
O<cr>
Does this user have Web access? N<cr>
Creating new user file
Enter user name: <cr>
27
Add New User complete

>
See also:
AR Adjust User Roles
DU Delete User
LU List User
CP Change Password
1.17.4 CH Clear History

The CH Clear History command will permanently erase the event history from the QNet4100 system.
This command is only accessible through the maintenance port (Port0) at the controller module.
>CH<cr>
QNet4100
Station number: 1
18 Feb 2012 15:17:05
WARNING! This command will permanently erase the event history.
System will reboot after history is erased.
Do you wish to proceed (Y,N)? Y<cr>
xxxxxxxxxxxxxxxxxxxxxx
1.17.5 CP Change Password

The CP Change Password command allows the a user to change either the system password or user
specific password, depending on the context in which it is used:
If the command is available on the 'Main Menu' for all users ('legacy' role) then initiating the command will
allow for the system level password to be changed.
>CP<cr>
QNet4100
Station number: 1
13 Feb 2012 16:22:12
Enter password:****<cr>
Change Password
New password: *****<cr>
Re-enter password: *****<cr>
Change Password complete
>
If the command is available on the 'Main Menu' for a user with a role other than 'security' then initiating the
command will allow for that individual users password to be changed.
>CP<cr>
QNet4100
Station number: 1
13 Feb 2012 18:16:43
Change Password
28
Enter old password:********<cr>
Enter password: ********<cr>
Reenter password: ********<cr>
>
If the command is available on the 'Main Menu' for a user with the 'security role' then initiating the command
will allow for the password for any named user to be changed. (Used in this context, the CP Change
Password command also allows for the users role to be changed).
>CP<cr>
QNet4100
Station number: 1
13 Feb 2012 20:33:57
Change Password
Enter old password:********<cr>
Enter password: *******<cr>
Reenter password: ********<cr>
Enter user role (E)ngineer, (O)perator, (M)onitor, (S)ecurity, User(1), User
(2)):O<cr>
Does this user have Web access? Y<cr>
>
In all cases the CP Change Password command will prompt for the current system or user password before
allowing the password to be changed.
All passwords are case sensitive.

System level passwords can be any length, including zero length (or simply a carriage return (<cr>)).
User level passwords must be at least 8 characters in length.
The password can contain both upper and lower case letters, numbers, and symbols.
Passwords can not contain control characters.
If a password contains illegal or insufficient number of characters the 'Pas s wor d i s not ac c ept abl e'
message will be displayed and the system will prompt for the password to be entered again.
See also:
UL User Login
Lost password
1.17.6 CW Clear Window States

The CW Clear Window States command allows for a reset command to be sent to the annunciators
connected to the controller module via an annunciator configuration port.
To get to the CW command, enter MC from the main menu, then enter MW from the MC menu, then enter CW
from the MW menu.
After entering the CW command, a reset command is sent to the annunciators through the annunciator
configuration port. This clears the window states for all annunciators.
The following is displayed to the user after entering the CW command.
29
MW>CW<cr>
MW>
The reset command will set all windows to the 'idle' state and the horn to the 'off' state. The CW Clear
Window States command should be followed by a XQ Reset QNet System command. This will cause
the system to resend the current alarm conditions to the annunciator and re-establish the correct annunciator
window states.
For further assistance with resetting the system using the XQ command, please refer to the XQ Reset QNet
System command documentation found in this manual.
For further assistance with Annunciators or Annunciator Windows, please refer to the MW Modify
Annunciators sub menu command documentation found in this manual.
To return to the main menu:

1. Press the Enter key and type Y at this prompt: "Leave MW and return to MC menu (Y,N)?"
2. Press the Enter key again and 1 of 2 prompts will be displayed:
a. "Leave MC and return to main menu (Y,N)?" if changes have not been made to the
configuration.
- Enter Y to return to the main menu.
OR b. "Configuration has been modified. Save, Restore, or Continue (S,R,C)?"
- type S to save the configuration, R to restore the configuration to what it was before, or type C
to continue making changes to the confguration.
- If changes have been made to the system that require a reboot, the changes will be saved
and the system will be automatically restarted.
1.17.7 DL Download Audit Log from QNet

The DL Download Audit Log from QNet command allows the user to transfer all audit log entries from
the QNet 4100 to the user's PC using XModem file transfer..
The audit log is transferred as a GZip compressed XML file. The file can be decompressed using most
decompression software such as WinZip, WinRar, 7Zip, etc. Once decompressed the file can be imported to
either a Microsoft Access Database or Microsoft Excel Spread Sheet or can be viewed as a test or XML file.
MC>DL<cr>
Download Audit Log from QNet
Start XMODEM receiver
The terminal software must be configured to receive the XML file.
Download Audit Log from QNet complete
MC>
See also:
LA List Audit Log command
HyperTerminal XMODEM File Transfer
30
1.17.8 DM Debug Mode
The DM Debug Messages command allows for backplane communications with the scanner modules to be
monitored. This is useful for debugging scanner module communications in large distributed systems.
CAUTION The DM Debug Messages command is intended for troubleshooting and diagnostic use only and
: can have a significant effect on the efficiency of other system functions and processes.The system
should not be left in the debug messages mode for extended periods of time during normal operation.
>DM<cr>
QNet4100
Station number: 1
9 Aug 1970 17:12:16 f
Enable scanner debug message reporting (Y,N)? Y<cr>
complete
>
TX: 40.460 ff TIME 61950002
TX: 50.460 ff ST RQ
RX: 50.472 01 STREP 61960002 00 00 00 00 00 00 00 00
RX: 50.472 02 STREP 61960002 00 00 00 00 00 00 00 00
RX: 50.472 03 STREP 61960002 00 00 00 00 00 00 00 00
RX: 50.472 04 STREP 61960002 00 00 00 00 00 00 00 00
TX: 10.464 ff TIME 61980006
TX: 20.460 ff ST RQ
RX: 50.472 01 STREP 61990002 00 00 00 00 00 00 00 00
RX: 50.472 02 STREP 61990002 00 00 00 00 00 00 00 00
RX: 50.472 03 STREP 61990002 00 00 00 00 00 00 00 00
RX: 50.472 04 STREP 61990002 00 00 00 00 00 00 00 00
TX: 40.460 ff TIME 62010002
TX: 50.460 ff ST RQ
...
Debug messages are displayed in columns:
Typical Message: RX: 50.472 01 STREP 61960002 00 08 08 08 00 00 00

00
------ ------ -- ----- -------- -- -- -- -- -- -- --
--
Column number 1 2 3 4 5 6
The following describes the information in each column:
Column 1: Message direction

TX Message transmitted by the controller module to the Scanners Modules. Most
messages are Broadcast messages (See message type below.
RX Message received by the controller Module from a scanner modules.
Column 2: Relative timestamp
31
0 to 59.999 This is rolling 60 second timer that can be used to calculate relative time between
messages.(Note this timestamp is the time from the controller perspective; it is the
time that the message was transmitted or received.not the time time that the scanner
generated the message!)
Column 3: Scanner module number or broadcast (Hex byte)

01 thru 3F Scanners 1 thru 63.
00 Scanner 64
FF Broadcast type message from the controller module to all scanners.
Column 4: Message type

TIME Time synchronization broadcast message to all scanner modules. Normally the time
synchronization message is broadcast at 30 seconds intervals at approximately 0 and
30 seconds past the minute. However, the controller may broadcast additional time
synchronization messages if it needs to make a gross time correction. The time
synchronization message includes the 'Time' (column 5) but does not include a
'Payload' (column 6).
ST RQ Self test request message broadcast from the controller module to all scanner
modules. Normally the ST RQ message is broadcast at 30 seconds intervals at
approximately 10 and 40 seconds past the minute. The self test request message does
not includes a 'Time' (column 5) or 'Payload' (column 6).
FT RQ Functional test request message broadcast from the controller module to all scanner
modules. Normally the FT RQ message is broadcast every hour at approximately 5
seconds past the hour, or whenever a user initiates a TS Test Scanner command.
ADBNC Alarm debounce time configuration record from the controller module to a scanner
module. This is the first of three configuration records sent from the controller module
when the system first starts, when the scanner module configuration changes or when
the controller module needs to re-establish communications with a failed scanner.
RDBNC Return debounce time configuration record from the controller module to a scanner
module. This is the second of three configuration records sent from the controller
module when the system first starts, when the scanner module configuration changes
or when the controller module needs to re-establish communications with a failed
scanner.
POLEN Polarity and enable configuration record from the controller module to a scanner
module. This is the third of three configuration records sent from the controller module
when the system first starts, when the scanner module configuration changes or when
the controller module needs to re-establish communications with a failed scanner.
SCVER Scanner version request and report. Initially an scanner version request is is sent from
the controller module to a scanner module. Depending on the scanner module type and
the firmware installed in the scanner the scanner will respond with its installed firmware
version. The scanner Version request is normally sent after the three configuration
records (ADBNC, RDBNC and POLEN).
STREP Self test report message from a scanner module to the controller module. This
message is sent in response to a self test request (ST RQ) from the controller module.
FTREP Functional test report from a scanner module to the controller.This message is normally
sent in response to a functional test request (FT RQ) from the controller module. (See
TS Test Scanners command).
FTFAIL Functional tester failure from a scanner module to the controller module. This message
is sent in response to a functional test request (FT RQ) from the controller module if the
scanner functional test circuitry fails. (See TS Test Scanners command).
EVENT Event message sent from a scanner module to the controller module.
32
Column 5: Time
0 to 50999999 Time associated with the message in milliseconds since midnight UTC. The time is
included for all messages from the scanner module to the controller module but only for
the time synchronization message from the controller to the scanner modules.
Column 6: Payload
00 .... FF Data from other controller module to the scanner module or vice versa.
For messages from the controller module to the scanner module only the configuration
message (ADBNC, RDBNC and POLEN) include a payload;
The ADBNC and RDBNC configuration message each contain 128 bytes or 64 words
(2 bytes).
Byte Size
1-2 2 bytes = Debounce time for scanner Each word contains the debounce
1 word input 1 time value for the input 0 through
... ... FFFF (0 - 65,535 milliseconds).
127 -128 4 bytes Debounce time for scanner
input 64
The POLEN configuration message contains contains 154 bytes;

Byte Size
1-4 4 bytes = 'Trigger Mask' for the inputs 1 'Trigger mask' is not currently
1 long word through 32; implemented at the controller
Bit 0 (LSB) = Input 1 module and trigger bits will always
... be set to 0.
Bit 32 (MSB) = input 32
5-8 4 bytes = 'Trigger Mask' for the scanner
1 long word inputs 33 through 64;
Bit 0 (LSB) = Input 33
...
Bit 32 (MSB) = Input 64
9 - 72 64 bytes Automatic delete from and Time value is between 0 to 255
restore to logging time value; representing a time between 0 and
First byte = Input 1 3825 seconds in 15second
... increments.
Last byte = Input 64
73 - 136 64 bytes Automatic delete from and Count value is between 0 and 255
restore to logging count and represents number of changes
value; of state for input before the input is
First byte = Input 1 deleted from logging.
...
Last byte = input 64 See also 'Automatic delete from
and and restore to logging'.
137-138 2 bytes = Scanner enable.and transmit Value of &H0000 = disabled;
1 word mask Value of &H0003 = enabled with a
transmit interval of 4mS.
Value of &H0007 = enabled with a
Value of &H000F = enabled with a
33

138 - 142 4 bytes = Polarity inputs 1 through 32; A '0' in the bit position represents a
1 long word Bit 0 (LSB) = Input 1 normally closed (NC) input and '1'
... represents an normally open (NO)
Bit 32 (MSB) = input 32; input.
143 - 146 4 bytes = Polarity inputs 33 through 64;
1 long word Bit 0 (LSB) = Input 1 (Note: The word 'Normally' is used
... to represents the non-alarm
Bit 32 (MSB) = input 32; condition.)
147 - 150 4 bytes = Point Enable inputs 1 A '0' in the bit position represents a
1 long word through 32; disabled input and '1' represents an
Bit 0 (LSB) = Input 1 enabled input.
...
Bit 32 (MSB) = input 32;
151 - 154 4 bytes = Point Enable inputs 33
1 long word through 64;
Bit 0 (LSB) = Input 33
...
Bit 32 (MSB) = input 64;
Note: For DM command only the first 16 bytes of the ADBNC, RDBNC and POLEN
payload are displayed. See also 'Troubleshooting' and 'Diagnostic tools'.
-------------------------------------------------------------------------------------------------------
For the messages from the scanner module to the controller module, the payload
contains 8 bytes of data.
For the STREP, FTREP, FTFAIL and EVENT type messages the data representing the
status of the scanner module inputs:
Byte Size
1-4 4 bytes = Status for scanner module For the STREP, FTFAIL and
1 long word inputs 1 thru 32: EVENT type message, a '0' in the
Bit 1 (LSB) = Input 1 bit position represents a 'Normal'
... input and '1' represents an 'Alarm'.
Bit 32 (MSB) = Input 32
5-8 4 bytes = Status for scanner module For the FTREP type message, a '0'
1 long word inputs 33 thru 68: in the bit position represents a
Bit 1 (LSB) = Input 33 'Healthy' input and '1' represents a
... 'Failed' input.
Bit 32 (MSB) = input 64
For the SCVER type message, from the scanner to the controller module, only bytes 2
and 3 have meaning (all other bytes are set to zero);
34
Byte Size
1-2 2 bytes Always zero
3 1 byte Major firmware version; each nibble (4 bits) represents a binary
coded decimal (BCD) digit of the major firmware version.
4 1 byte Minor software version; each nibble (4 bits) represents a binary
coded decimal (BCD) digit of the minor firmware version.
5-8 4 bytes Always zero
For example:
The following diagnostic message is displayed:
RX: 50.472 06 EVENT 57705999 00 00 00 00 04 00 00 00
The RX indicates that this is a message received by the controller module from a scanner module.
The controller module time stamped the message 50.472. (Note: This is only relative to other messages).
The 06 indicates that the message was received from scanner module number 6.
The EVENT indicates that this was an event message from the scanner module.
The 57705999 indicates that the event occurred at 57705999 milliseconds past midnight UTC or
16:01:45.999 UTC.
(Note: Events are reported with the post debounce time and the debounce time must be subtracted to
establish the actual time of the event; for example if the debounce time for the input associated with
this event is 10mS then the actual event time was 16:01:45.989).
The 00 00 00 00 04 00 00 00 indicates that the bit 2 of byte 3 is '1' indicating that scanner point 59
is in the alarm condition. All other bits are '0' indicating that all other points are in the normal condition.
Assuming that prior to the event all inputs were in the normal condition then the event is reporting a new
alarm for scanner input point 59, and, since this is scanner number 6, this represents system scanner
input point 379.
To disable debug messages used the DM Debug Messages command again and enter 'No' at the 'Enable
scanner debug message reporting' prompt.
CAUTION: The the system should not be left in the debug messages mode during normal operation. The DM
Debug Messages command is intended for troubleshooting and diagnostic use only and can have a significant
effect on the efficiency of other system functions processes.
1.17.9 DN Download Configuration from QNet

The DN Download Configuration from QNet command allows the configuration file of the QNet4100 to
be saved to the user's PC for backup.
The file is transferred using the XMODEM file transfer protocol and requires terminal emulation software that
supports the XMODEM file transfer protocol, such as HyperTerminal.
Configuration for the QNet4100 controller module is complex and extensive and as a minimum we recommend
the backup of the configuration file to a PC after any significant configuration changes such that they may be
reloaded to a new controller should a failure of the QNet4100 controller module occur.
The file is a compressed Extensible Markup Language (XML) document containing all of the QNet4100
configuration. The XML file is compressed to reduce transfer times; typically the file can contain several
35
megabytes of data but when compressed the file is reduced to only a fraction of it's original size. The
QNet4100 uses the 'gzip' file format as documented in RFC1952, (a gzip wrapped around a deflate stream).
To start the download, type MC from the main menu, then type DN from the MC menu. The system displays
"please wait" while it generates the configuration file. This will take 1 to 2 minutes and depends on the
complexity of the configuration.
MC>DN<cr>
Download Configuration from QNet
Please wait: Generating XML for configuration
Start XMODEM receiver
When "Start XMODEM receiver" is displayed, the system is waiting for the user to start the XMODEM receiver.
If the user is using HyperTerminal, the user can select "Receive File" from the Transfer menu, set the receiving
protocol to Xmodem, select the folder to save the configuration file in, and give it an appropriate name.
After clicking the "Receive" button, the download will start. The download will take 1 or 2 minutes and again
varies depending on the complexity of the configuration file. When the download finishes the system displays
the message "Download Configuration from QNet complete".
To restore a downloaded configuration, use the UP command from the MC menu to upload and apply that
configuration.
To return to the main menu, press the Enter key at the MC prompt, then enter Y to return to the main menu.
1.17.10 DP Default System Password

The DP Default Password command allows the system level password to be reset to the factory default
('QNET').
>DP<cr>
QNet4100
Station number: 1
28 Jul 2011 15:20:14
>
****<cr>
complete
This command is only accessible through the Maintenance port (Port0) at the controller module.
The system will not provide a prompt for the entry and, will not provide feedback if an incorrect password is
entered; the system will responds the same way to a correct or incorrect default password entry by simply
responding with the 'complete' message. In the above example the default password is entered in reverse, i.e.
TENQ<cr>. This will cause the system level password to be reset to 'QNET'.
The DP Default Password does not allow for user level password to be reset.
See also:
Access Control List
CP Change Password
36
1.17.11 DP Delete Port
The DP Delete Port command allows the user to delete an existing port.
To get to the DP command, type MC from the main menu, MP from the MC menu, and DP from the MP menu.
MP>DP<cr>
Delete Port Configuration
Port name? newport1<cr>
Delete port (Y,N)?Y<cr>
In the example above, the port named "newport1" is being deleted with the DP command.
Enter "?" at the Port name prompt for a listing of all existing ports.
Port names are case sensitve. They must be entered exactly as they appear in the list.
After entering the port name, confirm port deletion by entering a "Y" at the "Delete port (Y,N)? prompt.
The user may enter another port to delete, or they may press the Enter key at the Port name prompt to exit the
command.
When the user exits the command they are returned to the MP prompt.

1. Press the Enter key and type Y at this prompt: "Leave MP and return to MC menu (Y,N)?"
configuration.
and the system will be automatically restarted. Deleting a port will require a restart of the system.
1.17.12 DS Default System Configuration

The DS Default System Configuration command allows the QNet4100 system to be reset to the
factory default configuration.
>DS<cr>
QNet4100
Station number: 1
9 Aug 1970 12:44:32 f
WARNING: This command will reset the system to the factory default settings.
This command is only accessible through the Maintenance port (Port0) at the controller module.
Resetting the to the default system configuration will not change the security settings for the system; only the
operational parameters for the system are reset.
After the default system configuration is installed the system will automatically reboot.
37
1.17.13 DU Delete User

The DU Delete User command allows for users to be removed from the QNet4100 system.
The command will prompt for the users name.
>DU<cr>
QNet4100
Station number: 1
15 Feb 2012 10:37:39
Enter user name: JoeBloggs<cr>
Enter user name: <cr>
Delete User complete
>
The command may also be entered in a terse fashion:
>DU;JoeBloggs;;<cr>
Delete User complete
>
Note the user of the double semi-colon to represent an empty entry.
See also:
AU Add New User
LU List User
CP Change Password
1.17.14 ED Enable/Disable DHCP

The ED Enable/Disable DHCP command allows for the Ethernet ports E0 and E1 to be set for Dynamic
Host Configuration Protocol (DHCP).
To get to the ED command, type MC from the main menu, MN from the MC menu, and ED from the MN menu.
MN>ED<cr>
Enable/Disable DHCP
Use DHCP for eth0 (Y,N)? [N]Y<cr>
Use DHCP for eth1 (Y,N)? [N]N<cr>
Enable/Disable DHCP complete
MN>
The example above enables DHCP for ethernet port 1 (eth0) and leaves DHCP disabled for ethernet port 2 (eth1)
.
When DHCP is enabled for a port the system will broadcast a query requesting necessary information from a
DHCP server. If a DHCP server is found the server will allocate the port an IP address and provide other
information to the system such as subnet mask and the default gateway.
If the DHCP is disabled, the system network parameters must be manually configured; as a minimum the
38
system must be provided with an IP address, subnet mask and default gateway routing.

1. Press the Enter key and type Y at this prompt: "Leave MN and return to MC menu (Y,N)?"
configuration.
and the system will be automatically restarted. Changes to networking require a reboot of the system.
See also:
EN Edit Network Interface command
ER Edit Routing Table command
1.17.15 EI Enable/Disable IP Fowarding

The EI Enable/Disable IP Fowarding command allows for the system to be configured to forward TCP
data packets between the two network ports, eth0 and eth1.
TCP data packets that are not destined for the system are routed between the two networks ports.
To get to the EI command, type MC from the main menu, MN from the MC menu, and EI from the MN menu.
MN>EI<cr>
Enable/Disable IP Forwarding
Allow IP forwarding (Y,N)? [N]Y<cr>
Enable/Disable IP Forwarding complete
MN>
In the example above, the user enables IP forwarding by entering a Y at the Allow IP forwarding prompt.
The user may also enter an N to disable IP forwarding. The current value for the setting is displayed in
brackets. In the example above, the current setting was [N]. The N means that IP forwarding was not
enabled. Pressing the Enter key would allow the user to accept the current value.
After responding to the prompt the user exits the command and is returned to the MN prompt MN>.

configuration.
and the system will be automatically restarted. Changes to IP Forwarding require a restart of the
39
system.
1.17.16 EH Edit Host Table

The EH Edit Host Table command allows the user to associate network Host names to their associated
IP addresses. After a host entry is entered into the host table, a connection to that server can be established
using the host name instead of being required to enter the IP address for that server.
To get to the EH command, type MC from the main menu, MN from the MC menu, and EH from the MN menu.
An example of entries in the Host table:
127.0.0.1 localhost
209.68.14.80 www.pcguide.com
216.92.177.143 www.desktopscenes.com
198.175.98.64 ftp.intel.com
MN>EH<cr>
Edit Host Table
Host name? newhost<cr>
newhost - Add new host entry (Y,N)? Y<cr>
IP address? []123.45.68.91<cr>
Host name?<cr>
Edit Host Table complete
MN>
The example above shows how a new entry would be added to the host table. Multiple Host entries can be
added by continuing to follow the prompts and entering appropriate data as required.
Existing entries may be deleted or modified. Enter the existing host name at the Host name? prompt. To see
a list of existing host entries, type a ? and all of the existing hosts will be displayed.
After a valid host name is entered, type a Y at the Delete this host entry (Y,N)? prompt to delete the
host. Entering an N instead at the same prompt will allow modification to that existing host entry. After finishing
editing the host table, press the Enter key at the Host name? prompt to exit the command and return to the
MN> prompt.
To see all of the network settings including the list of host entries in the Host table, use the LN command from
the MN menu.

1. Press the Enter key and type Y at this prompt: "Leave MN and return to MC menu (Y,N)?"
configuration.
40
and the system will be automatically restarted. Changes to the Host table require a restart of the
system.
1.17.17 EN Edit Network Interface

The EN Edit Network Interface command allows the user to configure either network interface.
To get to the EN command, type MC from the main menu, MN from the MC menu, and EN from the MN menu.
MN>EN<cr>
Edit Network Interface
Interface to edit (eth0,eth1)? eth0<cr>
Address type (IP,IPv6)? [IP]<cr>
IP address? [10.75.2.43]<cr>
Network mask? [255.255.255.0]<cr>
Broadcast IP address? [10.75.2.255]<cr>
Interface to edit (eth0,eth1)?<cr>
Edit Network Interface complete
MN>
The example above shows the prompts for setting up a network interface. In the example, the network interface
already had values for all of the settings, and all of the current settings were taken. No settings were changed.
The current value of each setting is displayed in brackets [] at the end of each prompt. The current settings will
be used if the user presses the Enter key. To change the setting, enter the desired value at the prompt.
The IP choice for the Address type prompt refers to IPv4. Refer to the network administrator for assistance with
network settings.
Press the Enter key at the Interface to edit (eth0,eth1)? prompt to exit the command and return to
the MN> prompt.
To see all of the network settings, use the LN command from the MN menu.

configuration.
and the system will be automatically restarted. Changes to the Network Interface require a restart of
the system.
1.17.18 ER Edit Routing Table

The ER Edit Routing Table command allows the user to edit the network routing table. The network
routing table governs how network traffic will be directed, and can include a default gateway for traffic destined
41
outside the local network.
To get to the ER command, type MC from the main menu, MN from the MC menu, and ER from the MN menu.
MN>ER<cr>
Edit Routing Table
Route destination? default<cr>
default - Add new route destination (Y,N)? Y<cr>
Gateway IP address? 123.45.67.1<cr>
Route destination?<cr>
Edit Routing Table complete
MN>
In the example above, the default gateway is defined as IPv4 address 123.45.67.1. Additional routes may be
added by typing a new name at the Route destination? prompt and entering an IP address for each route.
Existing entries may be deleted or modified. Enter the existing route destination name at the Route
destination? prompt. To see a list of existing route entries, type a ? and all of the existing routes will be
displayed. After a valid route destination name is entered, Enter a Y at the Delete this destination
(Y,N)? prompt to delete the route. If you type a N instead at the same prompt you will be able to modify that
existing route entry. Refer to the network administrator for assistance with network settings.
Press the Enter key at the Route destination? prompt to exit the command and return to the MN>
prompt.

configuration.
and the system will be automatically restarted. Changes to the Routing table require a restart of
the system.
1.17.19 ES Edit Name Servers (DNS)

The ES Edit Name-Servers (DNS) command allows the user to edit the Domain Name Server table. This
table contains the DNS servers available on the network. A DNS server will resolve hostnames to IP
addresses. These IP addresses are then used in network communications.
To get to the ES command, type MC from the main menu, MN from the MC menu, and ES from the MN menu.
MN>ES<cr>
Edit Name-Servers (DNS)
DNS domain suffix? myDomain.com<cr>
42
myDomain.com - Add new domain (Y,N)? Y<cr>
DNS server IP address? 123.45.67.89<cr>
123.45.67.89 - Add new DNS server (Y,N)?<cr>
DNS server IP address? 123.45.67.90
123.45.67.90 - Add new DNS server (Y,N)? y<cr>
DNS server IP address?<cr>
Edit Name-Servers (DNS) complete
MN>
In the example above, the domain suffix myDomain.com is added to the Domain Name Server table.
Subsequently, 2 DNS servers are added to that domain suffix. Note that multiple DNS servers can be added to
a domain suffix. Press the Enter key at the DNS server IP address? prompt, to return to the MN>
prompt. Additional domain suffixes may be added by invoking the ES command for each domain suffix.
Existing domain entries may be deleted or modified. Enter the existing domain suffix at the DNS domain
suffix? prompt. To see a list of existing domains, enter a ? and all of the existing domains will be
displayed. After a valid domain name is entered, enter Y at the Delete this domain (Y,N)? prompt to
delete the domain. Entering N at the same prompt will allow the user to modify that existing domain entry.
Similarly, DNS servers can be deleted or added to each domain. Enter an existing DNS server IP address at
the DNS server IP address? prompt, To see a list of existing DNS servers, enter a ? and all of the
existing DNS servers will be displayed. After a valid IP address is entered, enter a Y at the Delete this
DNS server (Y,N)? prompt to delete the server. Enter N instead at the same prompt to
add a new DNS server IP address.
Refer to the network administrator for assistance with network settings.
Press the Enter key at the DNS server IP address? prompt to exit the command and return to the MN>
prompt.

configuration.
and the system will be automatically restarted. Changes to the Name servers require a restart of
the system.
1.17.20 ET Edit Time

The ET Edit Time command allows the user to set up the date, and time on the system.
MC>ET<cr>
Edit Time
43
Date (MM/DD/YY)? [04/16/12] 04/15/12<cr>

Time (HH:MM:SS)? [14:44:17] 17:22:00<cr>
Edit Time complete
MC>
The date and time must be entered as Local or UTC time depending on the current setting for the Port being
used.
The date is entered in Month, Day, Year format separated by slashs i.e. MM/DD/YY.
The time is entered in Hour, Minute and Second separated by semi colons and in 24 hour clock format and i.e.
hh:mm:ss.
MC>ET;04/15/12;17:22:00<cr>
Edit Time complete
MC>
See also:
RT Report Time command
1.17.21 EX Edit Exceptions

The EX Edit Exceptions command allows the user to 'temporarily' disable and re-enable scanner module
input points.
>EX<cr>
QNet4100
Station number: 1
8 Aug 2012 14:14:03
Enter password: ****<cr>
Edit Exceptions
Point (1..64)? 12<cr>
12 CONDENSATE DRUM LEVEL HIGH, Enable or Disable (E,D)? [E] D<cr>
A 14:14:05.604 #D 133 Point Disabled
Point (1..64)? <cr>
Edit Exceptions complete
>
A diagnostic alarm is associated with scanner module inputs points that are disabled using the EX Edit
Exceptions command; the diagnostic alarm (D# 133) will be in the alarm condition when any point is
'temporarily' disabled and alarm will return to the normal condition only when all 'temporarily' disabled scanner
inputs are re-enabled.
This feature is intended to allow points to be disabled during maintenance. Scanner inputs that are disabled
using the EX Edit Exceptions command will return to the enabled condition if the system is reset.
The EX Edit Exceptions command cannot use the terse entry mode from the all users (legacy role) if the
system level password is required. However, terse entry can be used after a user loggin or if system level
password is not required:
>EX;12;D;;
Edit Exceptions complete
>
44
Scanner module inputs points may also be disabled in the system configuration using the MI Modify
Inputs command.
See also:
RX Report Exceptions command
MI Modify Inputs command
1.17.22 LA List Audit Log

The LA List Audit Log command displays a log of changes and errors at the QNet4100 system.
LC>LA<cr>
List Audit Log
20120404.log 20120410.log 20120411.log 20120412.log
Log file? 20120411<cr>
04/11/2012 13:09:43 No user Modify Time Sync Configuration
04/11/2012 13:51:04 System monitor System Restarted
04/11/2012 13:51:04 System monitor System language is english
04/11/2012 13:51:06 System monitor Primary
04/11/2012 13:54:01 System monitor mcom quit processing on port #1 at
11 A pr 2012 13:54:01 f UTC
04/11/2012 17:23:13 No user Modify Port Configuration
04/11/2012 17:39:24 Command Rebooting after save
configuration...
04/11/2012 18:14:01 System monitor mcom quit processing on port #1 at
11 A pr 2012 18:14:01 f UTC
List Audit Log complete
LC>
An audit log file is generated automatically when a recordable event such as an error, configuration change or
user login or logout occurs.
The log file naming convention is based on the year, month, and day (YYYYMMDD.log) that file was generated.
Each audit log entry provides:
- the date and time for the entry.
- the user;
- If the event is a change, the user that was logged on to make the change
- If the Modify Configuration command was accessed from the Legacy Mode the entry will show
'No user'.
- If the event is an error the user will be shown as System Moditor.
- the type of change or error.
45
See also:
Access control List (ACL)
DL Download Audit Log from QNet command
1.17.23 LC List Configuration sub menu

The LC List Configuration sub menu command takes the user to the LC sub menu. The LC sub
menu has serveral commands that will allow the user to view the current configuration of the QNet4100. These
commands are intended to be "Read only". A user with modify access will be able to modify the configuration
of the system from the MC sub menu.
To get to the LC command, type LC from the main menu.
All of the commands found on the LC sub menu can also be found on the MC Modify Configuration sub
menu for convenience. This allows the user the ability to quickly review changes made to the configuration
while still in the MC sub menu. For further assistance with the MC command, view the MC Modify
Configuration sub menu command documentation.
>LC<cr>
QNet4100
Station number: 1
10 Oct 2012 15:16:11 c
LC>?<cr>
LQ List QNet Configuration
LI List Input Configuration
LL List Legends
LR List Relay Configuration
LG List Output Group Configuration
LN List Network Configuration
LP List Port Configuration
LO List Output Assignments
LW List Annunciator Windows
LA List Audit Log
LV List Version Details
LC>
In the example above, note that the station name, station number, date and time are displayed after the user
types the LC command. Also note that all of the commands available to the current user on the LC sub menu
are displayed when the user enters a ? at the LC> prompt. For assistance with any of the commands
available on the LC sub menu, please refer to the documentation for that command in this manual.
1. Press the Enter key and type Y at this prompt: Leave LC and return to main menu (Y,N)?
1.17.24 LG List Output Group Configuration

The LG List Output Group Configuration allows the user to view the configuration of a single group
point, a series of single group points, or a range of group points. The input expression, filter, filter delay type
and output expression will be displayed for each group point.
46
To get to the LG command, enter LC from the main menu, then enter LG from the LC menu.
LC>LG<cr>
List Output Group Configuration
End point (1..4096)? 5<cr>
1 Expression: d1|d2|d3|d135|d136|d145|d147|d156
Filter:
No filter delay
Output(s): l2
2 Expression: f1|f2|d137|d138|d139|d140|d141|d142|d146|d155
Filter:
No filter delay
Output(s): l1
3 Expression: s1
Filter: s2
No filter delay
Output(s): r1
4 Expression: s3
Filter: s4
On delay: 30 Off delay: 10
Output(s): r2
5 Expression: s5
Filter: s6
Filter hold delay: 10
Output(s): r3
List Output Group Configuration complete
In the example above, the user requested to view the range of group points from 1 to 5. At the Start point
prompt, enter the first point of the range, and at the End point prompt, enter the last point of the range of
group points to be displayed. The system then displays the group points in the range requested. Note that the
input Expression, Filter, Filter delay type and Output expression are displayed for each group point.
For further assistance with the input or output expressions, or the filter and filter delay types, please refer to the
MG Modify Output Group Configuration command documentation found in this manual.
To view a single group point enter an S at the Multipoint, Range, Single (M,R,S)? prompt, followed
by the point of interest at the next prompt.
To view multiple single group points enter an M at the Multipoint, Range, Single (M,R,S)? prompt,
followed by the first point of interest at the next prompt, then the next point of interest at the next prompt etc.
When finished viewing multiple single group points, press the Enter key to exit the multiple group point
selection prompting.
When finished viewing group points, press the Enter key at the Multipoint, Range, Single (M,R,S)?
prompt to exit the LG command and return to the LC sub menu.
47
1.17.25 LI List Input Configuration

The LI List Input Configuration command allows the user to view the configuration of input points.
To get to the LI command, enter LC from the main menu, then enter LI from the LC menu.
After entering the LI command, the user can select the type of input points to view. The user may choose from
Scanner, Diagnostic, External or Group points. In the example below, Scanner points are chosen by entering
an S at the Scanner, Diagnostic, External, Group (S,D,X,G)? prompt.
Next, the user can choose the number of points to view. A Single point may be displayed by entering an S at
the Multipoint, Range, Single (M,R,S)? prompt. Multiple Single points may be displayed one at a
time if the user enters an M at the Multipoint, Range, Single (M,R,S)? prompt. Lastly, a Range of
points may be displayed at once by entering an R at the Multipoint, Range, Single (M,R,S)?
prompt. In the example below, a Range of points is requested.
In the last case where a Range of points is requested, the user will need to enter a Starting point and an Ending
point. In the example below, the starting point is 1 and the ending point is 5. The system then displays the
range of Scanner points from 1 through 5, showing all of the configurable settings for each Scanner input point.
LC>LI<cr>
End point (1..64)? 5<cr>
Point State Alarm Return Enable Critical Time Count AlarmSeq
1 NO 10 10 Y N 0 0 M
2 NO 10 10 Y N 0 0 M
3 NO 10 10 Y N 0 0 M
4 NO 10 10 Y N 0 0 M
5 NO 10 10 Y N 0 0 M
Scanner, Diagnostic, External, Group (S,D,X,G)?<cr>
List Input Configuration complete
The settings displayed include the following point information:
normally open/closed status of the point

alarm and return-to-normal delay time for the point
point is permanently disabled or enabled
point is designated as a critical alarm
auto delete/restore time for the point
auto delete/restore count for the point
alarm sequence
In the example above, the display indicates that the points are Normally Open, that points 1 through 5 are
enabled, and none of the points are assigned with a Critical Alarm. The listing also shows that the debounce
times for the Alarm and Return to normal events is 10 ms, the ADRL Time and Count settings for each point are
0, and the Alarm sequence involves a Manual reset for each point.
For further assistance with the input point settings, please refer to the MI Modify Input Configuration
48
command documentation found in this manual.
When the user is finished viewing points for a particular type of point, press the Enter key at the Multipoint,
Range, Single (M,R,S)? prompt to return to the point type prompt.
The user can continue viewing points by entering the letter representing whichever type of input points they
would like to see next. Enter D for Diagnostic, X for External, or G for Group. When the user is finished viewing
points, press the Enter key at the Scanner, Diagnostic, External, Group (S,D,X,G)? prompt to
return to the LC sub menu.
1.17.26 LL List Legends

The LL List Legends command allows the user to view device point legend data.
To get to the LL command, enter LC from the main menu, then enter LL from the LC menu.
After entering the LL command, the user can select the type of input points to view. The user may choose from
range of Scanner points from 1 through 5, showing the legends for each point.
LC>LL<cr>
List Legends
Scanner, Diagnostic, External, Group (S,D,X,G))? S<cr>
A 1 black Alarm Legend 1
N 1 black Return Legend 1
Scanner, Diagnostic, External, Group (S,D,X,G))?<cr>
List Legends complete
49
the type of legend, either Alarm or Normal

the point number
the background color associated with that legend
the legend text, 60 char max length
In the example above, the display indicates that the background color for all of the legends is black, and the
legend text is displayed for each point's Alarm condition and Return to Normal condition.
For further assistance with the legend settings, please refer to the ML Modify Legends command
documentation found in this manual.
When the user is finished viewing points for a particular type of points, such as Scanner points, pressing the
Enter key at the Multipoint, Range, Single (M,R,S)? prompt will return the user to the point type
prompt.
From that prompt the user can continue viewing points by entering the letter representing whichever type of
input points the user would like to see next. Enter D for Diagnostic, X for External, or G for Group. When the
user is finished viewing points, pressing the Enter key at the Scanner, Diagnostic, External, Group
(S,D,X,G)? prompt will return the user to the LC sub menu.
1.17.27 LN List Network Configuration

The LN List Network Configuration command allows the user to view the network information
associated with the QNet 4100.
To get to the LN command, enter LC from the main menu, then enter LN from the LC menu.
After entering the LN command, the system will display current network settings including: Ethernet settings, IP
forwarding and Routing table data.
LC>LN<cr>
List Network Configuration
eth0: DHCP enabled: No
Physical address: 00:19:C3:2C:CF:46
IP address: 10.75.2.42
Broadcast address: 10.255.255.255
Mask: 255.0.0.0
IPv6 address: fe80::219:c3ff:fe2c:cf46/64
eth1: DHCP enabled: No
Physical address: 00:19:C3:2C:CF:47
IP address:
Broadcast address:
Mask:
IPv6 address:
IP forwarding: No
DNS table:
Existing host entries:
50
Routing table:
Destination Gateway Mask
List Network Configuration complete
In the example above, the display indicates all of the network settings that are configureable from the MN
Modify Network sub menu.
For further assistance with the network settings, please refer to the documentation for the commands in the MN
Modify Network sub menu, or ask your network administrator for guidance.
1.17.28 LO List Output Assignments

The LO List Output Assignments command allows the user to see the output assignments of each
input point.
To get to the LO command, enter LC from the main menu, then enter LO from the LC menu.
After entering the LO command, the user can select the type of input points to view. The user may choose from
range of Scanner points from 1 through 5, showing all of the configurable settings for each Scanner input point.
LC>LO<cr>
List Output Assignments
Scanner points:
Port 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3
group 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
1 B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2 B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
3 B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
4 B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
5 B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
List Output Assignments complete
LC>
51
the scanner point number

the port groups each point is assigned to
the type of events sent to a particular port group. The choices are A for Alarm, N for return to Normal and B
for both Alarm and Normal.
In the example above, the display indicates that the points are all assigned to port group 1, and Both types of
events, Alarms and return to Normals, will be sent to port group 1. There are no other output assignments for
these 5 points. They are only assigned to port group 1.
For further assistance with output assignments of points, please refer to the MO Modify Output
Assignments command documentation found in this manual.
Pressing the Enter key at the Multipoint, Range, Single (M,R,S)? prompt will return the user to the
point type prompt. Pressing the Enter key at the Scanner, Diagnostic, External, Group (S,D,X,
G)? prompt will exit the command and return the user to the LC sub menu.
1.17.29 LP List Port Configuration

The LP List Port Configuration command allows the user to view the port configurations.
To get to the LP command, enter LC from the main menu, then enter LP from the LC menu.
After entering the LP command, the system will list the following configuration results for the existing Ports.
Port Name
Port assigned to what device
Network or Serial Port number
Protocol used (console, printer, colorprint, CRT, BPA, data annunciator, DNP)
Baud Rate
Data Bits (7 or 8)
Parity (Odd, Even, None)
Stop Bit rate for the assigned Baud Rate
Display Local or UTC time
LC>LP<cr>
List Port Configuration
Port group 1:
Port0: console Serial port 0, 38400, 8-N-1, UTC
List Port Configuration complete
In the example above, the port name is Port0, and the port is assigned to Port Group 1. This port uses serial
port 0, the console protocol, and is set to display UTC time. Also, the serial port settings for the port are a
baud rate of 38400, 8 data bits, 1 stop bit, and the Parity is set to None. If there were more ports configured in
the system, they would be listed in the LP listing along with Port0.
52
For further assistance with port configuration, please refer to the documenation for the commands on the MP
Modify Ports sub menu found in this manual.
1.17.30 LQ List QNet Configuration

The LQ List QNet Configuration command allows the user to view the values of some of the
QNet4100 system configuration settings.
To get to the LQ command, enter LC from the main menu, then enter LQ from the LC menu.
After entering the LQ command, the system will display a listing similar to the example below.
LC>LQ<cr>
List QNet Configuration
Station name: QNet4100
Station number: 1
Scanners enabled: 1
Base point: 1
Max point: 64
Local time zone: America/UnitedStates/New_York
Precision time source: None
Trained oscillator correction: 323
High stability oscillator: No
PPS on fiber: No
NTP Servers: None
Event indent: Alarm
Separate return legends: Yes
Hourly time print: Yes
Minute for hourly time print: 0
Alarm summary at midnight: No
Alarm summary on reset: No
Clear historical buffer on reboot: No
Time sorted port groups: None
List QNet Configuration complete
There is one configuration setting per line. The name of each configuration setting comes first, followed by a
colon ":", then the value of that setting is displayed to the right of the colon. For example the Station name in
the example above is "QNet4100" and the Station number is 1. There is no Precision time source and there
aren't any Time sorted port groups.
To set the Station name and Station number use the MQ command.
To set the enabled or disabled Scanners use the MS command.
To set the Base point and Max point use the MB command.
To set the Local time zone use the MZ command.
To set the Precision time source, High stability oscillator, PPS on fiber, and NTP Servers use the MT
command.
To set the Event indent, Separate return legends, Hourly time print, Minute for hourly time print, Alarm summary
at midnight, Alarm summary on reset and Clear historical buffer on reboot settings use the MM command.
53
To set port groups to Time sorted use the MO command.

For instructions on how to use the commands listed above, please see the documentation for each command in
this manual.
1.17.31 LR List Relay Configuration

The LR List Relay Configuration command allows the user to view the mode configuration of the 8
system Relays.
To get to the LR command, enter LC from the main menu, then enter LR from the LC menu.
After entering the LR command the system displays the current settings of the relays.
LC>LR<cr>
List Relay Configuration
R1 R2 R3 R4 R5 R6 R7 R8
HN -- -- -- -- -- -- --
Point for silence all relays is disabled
List Relay Configuration complete
The settings displayed include the following information:
the relay number - R1, R2 etc.

the mode that the relay is set to. HN for horn, CA for continuous alarm etc.
The Scanner point that will silence all relays
In the example above, the display indicates that Relay 1, R1, is set to HN, which is the Horn mode. The double
dashes, "--" indicate that no mode is set for that relay. Relays 2 through 8 are not set to a mode. There is
not a scanner point designated to silence all relays so the display states that the "Point for silence all
relays is disabled".
For further assistance with relay configuration, please refer to the MR Modify Relay Configuration
command documentation found in this manual.
1.17.32 LV List Version Details

The LV List Version Details command provides a listing of the current firmware installed on the
controller and connected scanner modules.
To get to the LV command, enter LC from the main menu, then enter LV from the LC menu.
After entering the LV command the system displays version numbers for the installed software. The listing will
look something like the example below.
54
LC>LV<cr>
List Version Details
Linux Image: Linux Kernel 2.6.34 Created date Oct 3, 2012
RAM Disk Image: Version: 2.1 Created Aug 4, 2011
Home Disk Image: Version: 2.2.2 Created Oct 3, 2012
WWW Image: Version: 2.2.2 Created Oct 03, 2012
QNet Image: Version: 2.2.2 Created Oct 03, 2012
Zoneinfo: Version: 2012f Created Sept 19, 2012
QNET 4100
Activate Process 2.2.2 Oct 3 2012
AdviSER Process 2.2.2 Oct 3 2012
Annunciator Process 2.2.2 Oct 3 2012
BPA Process 2.2.2 Oct 3 2012
Console Process 2.2.2 Oct 3 2012
DNP Process 2.2.2 Oct 3 2012
Data Link 2.2.2 Oct 3 2012
Event Process 2.2.2 Oct 3 2012
Event Process Sim 2.2.2 Oct 3 2012
Printer Process 2.2.2 Oct 3 2012
Time Manager Process 2.2.2 Oct 3 2012
XML Interface Process 2.2.2 Oct 3 2012
Event CGI program 2.2.2 Oct 3 2012
Firmware CGI program 2.2.2 Oct 3 2012
Scanner 01 Version 55.06

Scanner 02 Version 55.06
List Version Details complete

LC>
Note:
1. Scanner Module types 309120-xxx, 309121-xxx and 309199-xxx, and type 309288-xxx with firmware version
53.xx and older do not support the version command and will always show their firmware version as 0.00)
2. The first time that the LV List Version Details command is used during a session it must examine
each process module to determine the currently installed version; this may take several seconds.
Subsequently, if the module has not been restarted, the stored version details will be used and the command
will respond immediately.
1.17.33 LW List Annunciator Windows

The LW List Annunciator Windows command allows the user to display the configuration for an
annunciator pair. This configuration includes the unique configuration for each window in the annunciator pair, as
well as the general settings for that annunciator pair.
To get to the LW command, enter MC from the main menu, then enter MW from the MC menu, then enter LW
from the MW menu.
55
After entering the LW command, the system will prompt the user to enter the Annunciator pair number. The
user can enter the word All, or just an "A", upper or lowercase, to see the configurations of all of the annunciator
pairs, or they can select individual Annunciator pairs by entering either number of the annunciator pair. For
example, if the user enters 0 they will see the configuration of annunciator pair 0, 1. If the user enters 1, they
will still view the configuration of annunciator pair 0, 1.
After entering a value for an annunciator pair to view, the desired configuration is displayed. Below is a segment
of an example annunciator pair configuration. There are 64 Windows for each annunciator pair, and the
configuration of each one will be displayed.
MC>LW<cr>
List Annunciator Windows
Annunciator (All, or 0..63)? 1<cr>
Annunciator: 0 1
Pseudo test point: 1
Pseudo silence point: 1
Sequence group A B C D E
Sequence 1 1 1 1 1
Pseudo acknowledge 1 0 0 0 0
Pseudo reset 2 0 0 0 0
Pseudo FO Reset 3 0 0 0 0
Window 1: Sequence group: A Audible: 0
Points:
Points:
Points:
(Display edited)

Points:
Points:
Points:
The settings displayed for each annunciator pair include the following information:
Pseudo test point

Pseudo silence point
Sequence group configurations
a) the alarm operational sequence number for the Sequence group
b) the scanner input that acts as the Pseudo acknowledge point for the Sequence group
c) the scanner input that acts as the Pseudo reset point for the Sequence group
d) the scanner input that acts as the Pseudo "First Out" Reset point for the Sequence group
There are 5 Sequence Groups (A through E) for each Annunciator pair. An operational sequence number is
assigned to each sequence group. Sequence numbers have been pre-assigned to all available operational
sequences. Any combination of sequence assignments is allowed. For example, all groups may be assigned
sequence #1 (Sequence line), or each group may be assigned different sequence numbers.
56
In the example above, The information for Annunciator pair 0, 1 is being displayed. Scanner point 1 has been
assigned to be the Pseudo acknowledge point for Sequence group A, Scanner point 2 has been assigned to be
the Pseudo reset point for Sequence group A, and Scanner point 3 has been assigned to be the Pseudo FO
Reset point for Sequence group A. All of the windows that can be seen in the displayed segment have been set
to Sequence group A, and the alarms are not audible.
For further assistance with Annunciator windows, please refer to the documentation for the commands on the
MW Modify Annunciators sub menu found in this manual.
When finished viewing the Annunciator configurations, press the Enter key at the Annunciator (All, or
0..63)? prompt to return to the LC sub menu.
1.17.34 LU List Users

The LU List Users command provides a lists all users currently defined for the QNet4100 system, with their
role assignment and the availability of web access.
>LU<cr>
QNet4100
Station number: 1
15 Feb 2012 9:18:22
GSmith Security Web access
KBrown Engineer Web Access
DPerkins Engineer Web Access
LAnderson Operator
FairportUser Operator
CJohnson Operator
AWood Operator
List Users complete
>
See also:
Access control List (ACL)
AU Add New User
LU List User
1.17.35 MA Modify Annunciator

The MA Modify Annunciator command allows the user to modify the configuration for an annunciator pair.
To modify the configuration of the windows for an annunciator pair, please use the MW Modify Annunciator
Windows command, found in the MW Modify Annunciators sub menu.
The Annunciator pair settings are as follows:
Pseudo test point

Pseudo silence point
Sequence group configurations
57
a) the alarm operational sequence number for the Sequence group

b) the scanner input that acts as the Pseudo acknowledge point for the Sequence group
c) the scanner input that acts as the Pseudo reset point for the Sequence group
d) the scanner input that acts as the Pseudo "First Out" Reset point for the Sequence group
To get to the MA command, enter MC from the main menu, then enter MW from the MC menu, then enter MA
from the MW menu.
After entering the MA command, the system will prompt the user to enter the Annunciator pair number. Press
the Enter key at the Annunciator pair to modify (0..63)? prompt to exit the command and return
to the MW> prompt. To continue modifying an annunciator pair, enter one of the annunciator pair numbers. For
example, if the user enters 0 they will be modifying the configuration of annunciator pair 0, 1. Similarly, if the
user enters 1, they will still be modifying the configuration for annunciator pair 0, 1.
After entering a value for the previous prompt, the Pseudo test point (1..4096 or - to disable)?
[-] prompt is displayed. The value entered at this prompt indicates a scanner input point to act as the Pseudo
test button for this Annunciator pair. Whenever this scanner point goes into alarm, the system will behave as if
it received a button press from a physical Test button for this Annunciator pair.
After responding to the previous prompt, the Pseudo silence point (1..4096 or - to disable)?
[-] prompt is displayed. The value entered at this prompt indicates a scanner point to act as the Pseudo
silence button for this Annunciator pair. Whenever this scanner input point goes into alarm, the system will
behave as if it received a button press from a physical Silence button for this Annunciator pair.
After responding to the previous prompt, the Sequence group (A..E)? prompt is displayed. To go back to
the previous prompt, press the Enter key. To move forward with the annunciator pair configuration, enter a letter
from A to E for the sequence group to modify. Note that this same process can be repeated to configure any of
the other Sequence groups.
After entering a value for the sequence group, the Sequence number (1..12)? [1] prompt is displayed.
The Sequence number is a number that relates to a specific predetermined alarm sequence behavior. This
number is assigned to a sequence group, and the sequence group can be assigned to an annunciator window.
This action effectively assigns the alarm sequence behavior to that window.
After responding to the previous prompt, the Pseudo acknowledge point (1..4096 or - to
disable)? [-] prompt is displayed. The value entered at this prompt indicates a scanner point to act as the
Pseudo acknowledge button for this Annunciator pair. Whenever this scanner input point goes into alarm, the
system will behave as if it received a button press from a physical Acknowledge button for this Annunciator pair.
After responding to the previous prompt, the Pseudo reset point (1..4096 or - to disable)?
reset button for this Annunciator pair. Whenever this scanner input point goes into alarm, the system will
behave as if it received a button press from a physical Reset button for this Annunciator pair.
After responding to the previous prompt, the Pseudo FO reset point (1..4096 or - to disable)?
First Out reset button for this Annunciator pair. Whenever this scanner input point goes into alarm, the system
will behave as if it received a button press from a physical First Out Reset button for this Annunciator pair.
The user is now at the Sequence group prompt. Either configure another sequence group or return to the
Annunciator pair to modify prompt by pressing the Enter key.
58
MW>MA<cr>
Modify Annunciator
Annunciator pair to modify (0..63)? 0<cr>
Pseudo test point (1..4096 or - to disable)? [-]<cr>
Pseudo silence point (1..4096 or - to disable)? [-]<cr>
Sequence group (A..E)? A<cr>
Sequence number (1..12)? [1]<cr>
Pseudo acknowledge point (1..4096 or - to disable)? [-]<cr>
Pseudo reset point (1..4096 or - to disable)? [-]<cr>
Pseudo FO reset point (1..4096 or - to disable)? [-]<cr>
Sequence group (A..E)?<cr>
Annunciator pair to modify (0..63)?<cr>
Modify Annunciator complete
MW>
In the example above, The configuration for Annunciator pair 0, 1 is being modified. Sequence A is configured
to use Sequence number 1, and none of the Pseudo points are enabled for the annunciator pair.
Press the Enter key at the Annunciator pair to modify (0..63)? prompt to exit the command and
return to the MW sub menu.

configuration.
and the system will be automatically restarted. Changes to the Annunciator pairs do not require a
system restart.
1.17.36 MB Modify Base Point & Range

The 'MB Modify Base Point and Range' command allows for setting of the first and last scanner module
point for the system.
MC>MB<cr>
Modify Base Point & Range
First scanner point number (0..28000)? [1] 0<cr>
Max point number (0..4095)? [63] 4095<cr>
Modify Base Point & Range complete
MC>
MC>MB;0;4095<cr>
59
Modify Base Point & Range

Modify Base Point & Range complete
MC>
The 'First scanner point number' in the system allows for the scanner point numbers in the system to be offset.
In the past some manufacturers have used a 'First scanner point number' of 0 while others have used a 'First
scanner point number' of 1; to avoid the necessity to change plant drawings to match the QNet4100 point
numbering the QNet4100 allows the point numbers to be changed to match the plant!.
Also, when more than one system is installed at a single location it is often convenient to configured the
systems such that each has a unique range of scanner point numbers. For example if two systems are
installed each with 1024 points and the first has a 'First scanner point number' of 0, the second system may be
configured to have a 'First scanner point number' of 1024 such that the scanner point numbers do no overlap;
the first system will report events with point numbers 0 to 1023, while the second system will report events with
point numbers 1024 thru 2047.
The 'First scanner point number' can be set between 0 and 28000.
The 'Max point number' is used to limit the configuration size for a system. If the 'First scanner point number' is
set to 1 and the 'Max point number' is 64 then the system will only allow for the the first 64 scanner points to be
configured; scanner points above 64 cannot be configured and will be ignored.
Typically Max scanner will be set to the include all points up to the last enabled scanner, for example, if the
system has 16 scanners there are a total of 1024 inputs. Max scanner point' will then be set to 1024 plus one
less than the 'First scanner point number'. So if 'First scanner point number' is 1 then Max point number' should
be set to 1024; if the 'First scanner point number' is 0 then 'Max point number' should be set to 1023.
The 'Max point number' can be set to any number between 'First scanner point number' and 'First scanner point
number' + 4095. (The maximum number of scanner modules that can be used in a QNet4100 is 64, each with
64 points, providing for a total of 4096 inputs).
The factory default setting for the 'First scanner point number' is 1 and the default setting for the 'Max point
number' is 'First scanner point number' + 63. (By default only Scanner Module 1 is enabled, providing for 64
inputs. The 'First scanner point number' is set to 1 and 'Max point number' will be 64).
Note:
Changing the 'First scanner point number' or the 'Max point number' will change the acceptable point range
value (shown within parenthesis) for many other commands. See 'MI Modify Input Configuration'
command for additional information.
Changing the 'First scanner point number' or 'Max point number' WILL NOT cause the system to reboot on exit
from the Modify Configuration sub menu.
1.17.37 MC Modify Configuration sub menu

The MC Modify Configuration sub menu command allows for access to commands for configuration of
the QNet 4100.
If users security is not defined and the MC Modify Configuration sub menu is available from the main menu;
typing MC<cr> will display the header information (including the station name, station number and the current
date and time) and prompt for the system password.
60
If the correct password is entered the system will display the MC> prompt:
>MC<cr>
QNet4100
Station number: 1
28 Jan 2012 13:32:23
MC>
Note:
The default system level password in QNET
If an incorrect password is is entered the system will respond with Incorrect password and
immediately return to the main menu prompt (>):
>MC<cr>
QNet4100
Station number: 1
28 Jan 2012 13:32:23
Incorrect password
>
If user level security is defined and the 'MC Modify Configuration sub menu' command is available to
the logged on user, the system will not prompt for a password. (User level security requires that a user logon
and the user password is entered at the time that they logged logon rather than for individual commands.
>MC<cr>
QNet4100
Station number: 1
28 Jan 2012 13:32:23
MC>
Typing ?<cr> at the MC> prompt will cause the Modify Configuration sub menu to be displayed:
61
MC>?<cr>
MQ Modify QNet ID LQ List QNet Configuration
MS Modify Scanners
MB Modify Base Point & Range
MZ Modify Time Zone
MT Modify Time Configuration
MM Modify Misc Settings
MI Modify Input Configuration LI List Input Configuration
ML Modify Legends LL List Legends
MR Modify Relay Configuration LR List Relay Configuration
MP Modify Ports sub menu LP List Port Configuration
MN Modify Network sub menu LN List Network Configuration
MO Modify Output Assignments LO List Output Assignments
MX Modify Exceptions LX List Exceptions
MV Modify Vocabulary (Language)
SC Save Configuration Changes LA List Audit Log
UP Upload Configuration to QNet DN Download Configuration to QNet
XQ Reset QNet System
ET Edit Time
MC>
Entering a carriage return alone (<cr>) at the MC> prompt will prompt the user to exit the MC Modify
Configuration sub menu.
If configuration changes have been made but have not yet been saved the system will prompt for the user to
Save, Restore or Continue configuration (S, R or C). Additionally, if the changes are such
that the system needs to reboot after saving the changes a WARNING message will be displayed.
If the user chooses to save the configuration (S<cr>) the system will save the changes and reboot.
MC><cr>
Configuration has been modified
WARNING: System will reboot after changes are saved
Save, Restore, or Continue configuration (S, R, C)? S<cr>
Saving configuration...
Rebooting after save configuration...
System will reboot and show the system start up dialog
CAUTION: Using the 'SC Save Configuration Changes' command will cause the system to reboot
immediately without displaying the WARNING message if the changes made are such that a
reboot is required. The need for a reboot is dependent on the parameters changed. See
'Parameter modifications requiring a reboot'
If the user chooses to restore the configuration (R<cr>) system will restore the previous configuration to the
last configuration saved; either when the SC Save Configuration command was used or before the MC
Modify Configuration sub menu command was used if the SC Save Configuration
Changes command has not been used during this configuration session. After restoring the configuration
the system will return to the main menu prompt (>).
MC><cr>
62
Save, Restore, or Continue configuration (S, R, C)? R<cr>
Restoring configuration...
>
If the user chooses to continue configuration (C<cr>) system will return to the Modify configuration sub
menu prompt (MC>).
MC><cr>
Save, Restore, or Continue configuration (S, R, C)? C<cr>
MC>
If no changes have been made during this configuration session the system will prompt for the user to confirm
that they wish to Leave MC and return to the main menu (Y,N).
MC><cr>
Leave MC and return to main menu (Y,N)? Y<cr>
>
1.17.38 MG Modify Output Group Configuration

The MG Modify Output Group Configuration command allows the user to create Group points.
Group points allow the association of a group of input points to an output action. There are 2 predetermined
group points, G1 and G2, that associate system diagnostics to the system fault LED or the system fail LED.
To get to the MG command, enter MC from the main menu, then enter MG from the MC menu.
Every group point has these 4 attributes:
Inputs
Filter
Filter delay
Outputs
After entering the MG command, the system will prompt you for the number of Group points to configure. The
user may also press the Enter key at this Multipoint, Range, Single (M,R,S)? prompt to exit the
command and return to the MC> prompt.
After choosing the scope of points to change, the user will be prompted for the following information:
1. The Inputs
Enter the input expression for the group point at this Input expression? [] prompt. The user may
enter a dash at the prompt to disable the group point.
Inputs
Inputs are combined using input terms and Boolean or Mathematical operators to form an input expression.
63
Input terms can be:

Scanner input points (S1 thru S4096).
Diagnostic points (D1 thru D232).
External input points (X1 thru X4096).
Group points (G1 thru G1024).
Scanner failure groups (F1 thru F3) (See 'Special input functions' below)
Port groups (P1 thru P32) (See 'Special input functions' below)
Unacknowledged alarm in port group (O1 thru O32) (See 'Special input functions' below)
Unacknowledged return-to-normal in a port group (N1 thru N32) (See 'Special input functions' below)
Special Input Functions

Scanner failure groups (F1 thru F3):
There are three types of scanner module failures:
Self Test Failure where the scanner module fails to respond to a self test request from the controller
module.
Functional Tester Failure where a scanner module failed to perform a functional test because of a
malfunction of the test circuitry.
Functional Test Failure where a scanner module performed a functional test but found a point that
did not respond correctly.
An individual diagnostic alarm is provided for each of these types of failure for each of the 64 possible
scanner modules, resulting in a total of 192 diagnostic alarms. To allow these failures to be easily
grouped to the controller module fault or fail LED's or to relays, the diagnostic alarms for each failure
type are grouped by the F function as follows:
- F1 = Self Test Failure
- F2 = Functional Tester Failure
- F3 = Functional test Failure
Each Fx function represents an 'OR' group of the scanner diagnostic alarms and will become true
when any of the diagnostic alarms are TRUE (i.e. in an alarm or failed state).
Port groups (P1 to P32):

Alarm in port group function (P) binds all inputs in a port group in an '? Sx+? Dx+? Xx+? Gx > y'
expression where x are the range of points in the port group and y is the previous total for the group.
When any input to the point group is in the alarm condition the expression becomes TRUE.
Note: This function is intended to allow a number of input points to be easily assigned to a relay. A
port group can include scanner, diagnostic, external or group points. For help with assigning points
to port groups please refer to the documentation for the MO Modify Outputs Assignments
command found in this manual.
Unacknowledged alarm in port group (O1 thru O32):

When any input in the port group goes into the alarm condition, and this alarm event has not been
acknowledged, the expression becomes TRUE. O1 is associated with port group 1, O2 with port group
2, etc.
Note: This function is intended to be used in conjunction with a CRT (AdviSER) port or annunciator
port.
Unacknowledged return-to-normal in a port group (N1 thru N32):

When any input in the port group returns to normal from the alarm condition, and the alarm has not
been acknowledged, and the point has not been automatically reset, the expression becomes TRUE.
N1 is associated with port group 1, N2 with port group 2, etc.
Note: This function is intended to be used in conjunction with a CRT (AdviSER) port or annunciator
port. If this function is used as an input for a group point, the output of that group point can be used
to activate a ringback relay. When configured properly, AdviSER provides the ability to silence the
64
relay.
Expression Help:
The following information can be used when creating Input expressions, Filter expressions or Output
expressions. For these boolean expressions, inputs are considered TRUE when a point is in the alarm
condition and FALSE when a point is in the normal condition. For Mathematical expressions, inputs are
considered to have a weight of 1 when in the alarm condition and a weight of 0 when in the normal
condition.
The following Boolean and math operators may be used when creating any of the expressions:
Operato Function Example Expressions

r
OR or | Boolean OR S1|S2 or S1ORS2
The expression will be TRUE when either or both S1 or S2 are TRUE.
AND or & Boolean AND S1&S2 or S1ANDS2
The expression will be TRUE only when both S1 and S2 are TRUE.
XOR Boolean S1XORS2
XOR The expression will be TRUE only when either S1 or S2 are TRUE. The
(exclusive expression will be FALSE if both S1 and S2 are TRUE.
OR)
! Boolean NOT S1&!S2
The expression will be TRUE only when S1 is TRUE and S2 is NOT TRUE (or
FALSE).
+ Mathematical S1+S2+S3=3
addition The expression will be TRUE only when the S1 and S2 and S3 are TRUE (i.e.
the expression will be TRUE when the total weight is equal to 3).
= Conditional
equal
S1+S2+S3=2
The expression will be TRUE only when any two of S1 and S2 and S3 are
TRUE (i.e. the expression will be TRUE when the total weight is equal to 2).
# Conditional S1+S2+S3#3
Not equal The expression will be FALSE only when the S1 and S2 and S3 are TRUE (i.e.
the expression will be FALSE when the total weight is not equal to 3).
S1+S2+S3#2
The expression will be FALSE only when any two of S1 and S2 and S3 are
TRUE (i.e. the expression will be FALSE when the total weight is equal to 2).
< Conditional S1+S2+S3<3

less than The expression will be FALSE only when the S1 and S2 and S3 are TRUE (i.e.
the expression will be TRUE when the total weight is less than to 3).
> Conditional S1+S2+S3>2
greater than The expression will be TRUE only when S1 and S2 and S3 are TRUE (i.e. the
expression will be TRUE when the total weight is greater than to 2).
<= Conditional S1+S2+S3<=2
65
Operato Function Example Expressions

r
less than or The expression will be FALSE when any two of S1, S2 or S3 are TRUE (i.e. the
equal expression will be TRUE when the total weight is less than or equal to 2).
>= Conditional S1+S2+S3>=2
greater than The expression will be TRUE when any two of S1, S2 or S3 are ‘TRUE’ (i.e. the
or equal expression will be TRUE when the total weight is greater than or equal to 2).
? Conditional S1?S2:S3 (conditional part ? true part : false part)
IF
If S1 is TRUE the expression will be TRUE if S2 is TRUE and FALSE if S2 is
: Conditional
FALSE. Else, if S1 is FALSE the expression will be TRUE if S3 is TRUE and
ELSE
FALSE if S3 is FALSE. (i.e. If the condition part is true use the true part else
use the false part.)
The conditional part, true part and false part can also be expressions.
For example:
S1+S2+S3>1?S4&S5:S6+S7+S8>1
( Open and Used to control order of evaluation of an expression.
and close
) parentheses (S1|S2)&S3
The expression will be TRUE when S1 and S3 are TRUE, or when S2 and S3
are TRUE.
S1|(S2&S3)
The expression will be TRUE when S1 is TRUE or when S2 and S3 are TRUE.
An expression can contain up to 256 characters, however, a group point can be used as an input term to
another group point and hence can be cascaded to provide longer and more complex expressions.
CAUTION: Care should be taken to avoid creating a circular reference while assigning inputs to an output
group. A group point should not be used in an input expression for the same group point.
CAUTION: Care should be exercised when entering expressions to ensure that an input class identifier is
used for input terms. Expressions can contain constants. For example, S1+S2+S3+S4+5+S6>3 will be
treated as a valid expression. However, since ‘5’ is entered without an input class identifier it is treated as
a constant and the expression will always yield ‘TRUE’ since the input weight will always exceed 3!
2. The Filter
Enter the filter expression for the group point at this Filter expression? [] prompt. The user may
enter a dash at the prompt to disable the filter.
A filter expression will gate the input expression to the group output:
o If the filter expression is FALSE, the group output is TRUE when the input expression is TRUE and
FALSE when the input expression is FALSE.
o If the filter expression is TRUE, the group output will not change and will remain in its prior state
regardless of the state of the input expression.
3. The Filter delay type
66
Delays may be applied to the filter expression. If a Filter expression is specified in the previous prompt,
the user is then prompted for a filter delay type.
Enter a value for the filter delay type for the group point at this Filter delay type (0,1,2,3)?
[0] prompt. Help is available at this prompt by entering a ?.
a) If the user enters 0 for the filter delay type, no filter delay will be applied.
b) If the user enters 1 for the filter delay type, the user will be prompted for the ON delay value and the
OFF delay value. If required, enter a value for the filter ON delay at this Filter ON delay
(seconds) (0..255)?[0] prompt. The value entered will be the amount of time in seconds that
must pass, before the filter starts filtering for the group point, once the filter expression is TRUE.
After responding to the previous prompt, the Filter OFF delay (seconds) (0..255)?[0]
prompt is displayed. The value entered will be the amount of time in seconds that must pass, before
the filter stops filtering for the group point, once the filter expression is FALSE.
c) If the user enters 2 for the filter delay type, the user will be prompted for the OFF delay value. When
prompted, enter a value for this delay at the Filter OFF delay (seconds) (0..255)? prompt.
The value entered will be the amount of time in seconds that the filter is Active when the filter
expression is TRUE. After that amount of time has passed, the filter will not be applied to the group
point even if the filter expression is still TRUE. The filter will stay ACTIVE even if the filter expression
changes to FALSE before the designated time of the delay.
d) If the user enters 3 for the filter delay type, the user will be prompted for the OFF delay value. When
prompted, enter a value for this delay at the Filter OFF delay (seconds) (0..255)? prompt.
The value entered will be the amount of time in seconds that the filter is Active when the filter
expression is TRUE. After that amount of time has passed, the filter will not be applied to the group
point even if the filter expression is still TRUE. The filter will NOT stay ACTIVE if the filter expression
changes to FALSE before the designated time of the delay. As soon as the filter expression evaluates
to FALSE, the filter is removed from the group point, even if it is before the end of the designated time of
the delay.
A summary of the Filter delay type definitions

The definitions of the Filter delay types are as follows:
Filter delay type 0 - No delays are applied:
The filter becomes ACTIVE as soon as the resultant of the filter expression becomes TRUE
The filter becomes INACTIVE as soon as the filter expression becomes FALSE.
Filter delay type 1 - Two delays are applied; a delay ON and a delay OFF:
The delay ON time specifies the length of time that elapses between the filter expression becoming
TRUE and the filter becoming ACTIVE.
The delay ON time will start as soon as the filter expression becomes TRUE and will override the
delay OFF time; that is the delay OFF time will be canceled when the delay ON time starts.
The delay OFF time specifies the amount of time that elapses between the filter expression
becoming FALSE and the filter becoming INACTIVE.
The delay OFF time will start as soon as the filter expression becomes FALSE and will override the
delay ON time; that is the delay ON time will be canceled when the delay OFF time starts.
Filter delay type 2 - A single delay OFF is used:

The filter becomes ACTIVE as soon as the filter expression becomes TRUE.
The delay OFF time specifies the length of time that elapses between the filter expression
67
becoming TRUE and the filter becoming INACTIVE.

The filter will become INACTIVE after the delay OFF time even if the filter expression remains
TRUE.
The filter will remain ACTIVE for the delay OFF time even if the filter expression becomes FALSE.
Filter delay type 3 - A single delay OFF is used (This mode is similar to Filter delay type 2 except in
case iv below):
The filter becomes ACTIVE as soon as the filter expression becomes TRUE.
The delay OFF time specifies the length of time that elapses between the filter expression
becoming TRUE and the filter becoming INACTIVE.
The filter will become INACTIVE after the delay OFF time even if the filter expression remains
TRUE.
The filter will become INACTIVE as soon as filter expression becomes FALSE.
The delay ON and OFF times are adjustable between 0 to 255 seconds and have an accuracy of
within +1/-0 seconds; i.e. a delay time specified as 10 seconds will have a minimum delay time of 10
seconds and a maximum delay time of 11 seconds.
4. The Output List:

A group will always result in a group event even if no output device is specified in the output list. When a
group output transitions from ‘FALSE’ to ‘TRUE’ an alarm event will be generated and when the group
output transitions from ‘TRUE’ to ‘FALSE’ a return-to-normal event will be generated. Group events are
time stamped with the time that they were processed by the controller module, not the time associated
with the input that caused the group change of state (The time taken to process groups is dependent on
the number of groups and complexity of the expressions, but is typically only a few milliseconds). Group
events will be stored to the event history and will be sent to any ports that have the group output routed
via the MO Modify Outputs Assignments command.
The group output may also be used to affect one or more types of output.
Outputs can be either:
- controller module fault or fail LED’s (L1 or L2, respectively)
- controller module relays (R1 thru R8)
- Mute function used to silence a Horn or Ringback relay (M1 thru M8)
- Acknowledge function used to acknowledge alarms within a port group (K1 thru K32)
- Clear function used to reset alarms within a port group (C1 thru C32)
- Annunciator function used to send an alarm to the annunciator output modules (A1 thru A4096)
(assigned in the annunciator configuration to alarm an annunciator window)
Notes:
An LED will be ON when any group output associated with it is TRUE and will be OFF only when all
group outputs associated with it return to FALSE.
The action of the relay will depend on the mode for that relay (set using the MR Modify Relay
Configuration command)
When modifications are complete, press the Enter key at the Multipoint, Range, Single (M,R,S)?
prompt to exit the MG command and return to the MC sub menu.

1. Press the Enter key and 1 of 2 prompts will be displayed:
68
configuration.
and the system will be automatically restarted. Changes made to group points require a restart of the
system before they take effect.
1.17.39 MI Modify Input Configuration

The MI Modify Input Configuration command allows for the parameters associated with scanner
inputs points, diagnostic points, external input points and group points to be adjusted.
MC>MI<cr>
Point State Alarm Return Enable Critical Time Count AlarmSeq
1 NO 10 10 Y N 0 0 M
Input normal state (Open, Closed)? [Open]Closed<cr>
Critical Alarm (Y,N)? [N]<cr>
Alarm debounce (mS) (1..65535)? [10]<cr>
Normal debounce (mS) (1..65535)? [10]<cr>
Point enabled (Y,N)? [Y]<cr>
Auto delete from/restore to logging:
Time in multiples of 15 seconds (15..3825 or 0 to disable)? [0]<cr>
Count (1..255 or 0 to disable)? [0]<cr>
Alarm sequence reset (Auto,Manual)? [Manual]<cr>
Same data (Y,N)? Y<cr>
Modify Input Configuration complete
MC>
The system will prompt for the input point type of points to be adjusted and the scope of inputs to be adjusted.
If the input point type is scanner; the system will prompt for:
Input normal state (Open, Closed)?

This is the state that the input contact will be in for a non alarm condition, either open or closed.
The default setting for Input normal state is Open.
Critical Alarm (Y,N)?

This parameter is used only for printing of events:
When a point is set for critical the critical escape sequence is sent to the printer prior to printing the alarm
event.
The critical escape sequence can be used to change the print color or font to highlight the alarm on the
printed page.
All other printout is proceeded by the normal escape sequence.
69
The default setting for Critical alarm is No.
Alarm debounce (mS) (1..65535)? and Normal debounce (mS) (1..65535)?

The scanner modules scan each input every millisecond, if an input changes state the scanner module will
store the change of state and will wait for the period of time determined by the Alarm debounce or
Normal debounce, depending on the direction of the state change. After the wait period the scanner
module will compare the current state of the input with the initial state, and, if they are the same will report
the event to the controller module. If they are not the same, the event is canceled and no event is reported.
The Alarm debounce and Normal debounce times are adjustable individually for each input in one
millisecond steps from 1 millisecond to 65535 milliseconds.
The default setting for both Alarm debounce and Normal debounce is 10 milliseconds.
Point enabled (Y,N)?

The scanner will only report events to the controller module if the input point is enabled. Changes of state of
inputs connected to a disable input point will be ignored.
Input points that are disabled using the MI Modify Input Configuration command are considered
permanently disabled; that is, they cannot be re-enabled using the EX Edit Exceptions command and
are not included in the RX Report Exceptions command report. (They can only be re-enabled using
the MI Modify Input Configuration).
The default setting for Point enabled is es.
Auto delete from/restore to logging:

Time in multiples of 15 seconds (15..3825 or 0 to disable)?
Count (1..255 or 0 to disable)?
The automatic delete and restore from logging algorithm will stop scanner input events from being reported
to the controller module if the input changes state by more a given number of times (specified by the Count
parameter) within a given period of time (specified by the Time parameter). It should be noted however that
this does not stop the scanner from scanning the input point and if the point changes less than the give
number of times (specified by the Count parameter) within a period of time (specified by the Time
parameter) the
For diagnostic, group and external points the command will prompt only the Critical Alarm and Point Enable
parameters.
See also:
EX Edit Exceptions command.
1.17.40 ML Modify Legends

The ML Modify Legends command allows the user to modify the legend configuration of any point.
The Legend settings for each point are as follows:
Alarm text
Alarm background color
Return to Normal text
Return to Normal background color
To get to the ML command, enter MC from the main menu, then enter ML from the MC menu.
70
After entering the ML command, the system will prompt the user for the type of input points to modify. The user
may choose from Scanner, Diagnostic, External or Group points.
After choosing the type of input points to modify the user is prompted to choose the scope of points to modify,
Single, Multipoint or Range.
After choosing the type and scope of points to modify, the user will be prompted for the first point to modify if
the user selected Single or Multipoint scope. After the first point has been selected, the current legend
settings for the first point are displayed, along with the Alarm legend? prompt. The text entered at this
prompt will be displayed every time this point goes into the Alarm condition. The legend may be up to 60
characters long.
After responding to the previous prompt, the Alarm color? [black] prompt is displayed. Context help is
available at this prompt. The color entered at this prompt will be the background color of the legend text that is
displayed every time this point goes into the Alarm condition. The AdviSER display and the History display in
the web interface support legend background colors.
After responding to the previous prompt, the Normal legend? prompt is displayed. The text entered at this
prompt will be displayed everytime this point returns to the Normal condition. The legend may be up to 60
characters long.
After responding to the previous prompt, the Normal color? [black] prompt is displayed. Context help is
available at this prompt. The color entered at this prompt will be the background color of the legend text that is
displayed every time this point returns to the Normal condition. The AdviSER display and the History display in
the web interface support legend background colors.
After responding to the previous prompt, the Same data (Y,N)? prompt is displayed when modifying a range
of points. Entering Y will apply the same changes to the rest of the points in the range. Entering N will allow
the user to enter a different legend configuration for the next point.
MC>ML<cr>
Modify Legends
Alarm legend?<cr>
Alarm color? [black]?<cr>
Colors:
black red green yellow blue magenta cyan white
Alarm color? [black]red<cr>
Normal legend?<cr>
Normal color? [black]green<cr>
Same data (Y,N)? y<cr>
Modify Legends complete
MC>
In the example above, the user is modifying Scanner points 1 through 5. The Alarm color was changed to red,
71
and the Normal color was changed to green, for scanner point 1. These same changes were applied to scanner
points 2 through 5 after the user answered Y to the "Same data" prompt.
When the user is done modifying points they will be returned to the Multipoint, Range, Single (M,R,
S)? prompt The user can continue modifying the same type of point or press the Enter key to be returned to
the Scanner, Diagnostic, External, Group (S,D,X,G)? prompt. The user may then select a
different type of point to modify or exit the ML command by pressing the Enter key again to return to the MC
prompt.

configuration.
and the system will be automatically restarted. Changes made to the legends do not require a reboot.
1.17.41 MM Modify Miscellaneous Settings

The MM Modify Miscellaneous Settings command allows the user to modify system parameters not
set by other configuration commands.
The settings that can be modified with this command are as follows:
Event indent
Separate return legends
Hourly time print
Minute for hourly time print
Alarm summary at midnight
Alarm summary on reset
Clear historical buffer on reset
To get to the MM command, enter MC from the main menu, then enter MM from the MC menu.
After entering the MM command the Event indent (Alarm,Normal)? [Alarm] prompt will be
displayed. The user may choose Alarm or Normal. If Alarm is chosen, the Alarm events will be indented by 2
spaces. If Normal is chosen, the return to Normal events will be indented by 2 spaces. This only affects
console displays and printers.
Indented Alarm:
A 20:26:45.673 #S 1 Alarm Legend 1
A 20:26:46.363 #S 2 Alarm Legend 2
A 20:26:46.777 #S 3 Alarm Legend 3
N 20:26:48.238 #S 1 Return Legend 1
Indented Normal:
72
A 20:26:45.673 #S 1 Alarm Legend 1
A 20:26:46.363 #S 2 Alarm Legend 2
A 20:26:46.777 #S 3 Alarm Legend 3
After responding to the previous prompt, the Separate return legends (Y,N)? [Y] prompt is
displayed. If the user enters Y at this prompt, both legends will be used, the alarm legend and the normal
legend. If the user enters N at this prompt, only the alarm legend will be used for both the alarm and the normal
events.
Same legend:
A 20:26:45.673 #S 1 Alarm Legend 1
A 20:26:46.363 #S 2 Alarm Legend 2
A 20:26:46.777 #S 3 Alarm Legend 3
N 20:26:48.238 #S 1 Alarm Legend 1
N 20:26:48.592 #S 2 Alarm Legend 2
N 20:26:48.918 #S 3 Alarm Legend 3
Separate return legend:

A 20:18:55.454 #S 1 Alarm Legend 1
A 20:18:56.383 #S 2 Alarm Legend 2
A 20:18:57.177 #S 3 Alarm Legend 3
After responding to the previous prompt, the Hourly time print (Y,N)? [Y] prompt is displayed. The
system will print the time and date once per hour (this is useful to confirm that the system remains in operation
if no events occur.) If the user enters Y at the prompt the system will display an hourly date and time stamp
every hour. The default for the minute that this is printed is at 00 minutes i.e 12:00, 13:00 etc. To change
which minute the hourly timestamp is displayed, change the Minute for hourly time print setting. If the user
enters N at the prompt a timestamp will not be displayed every hour.
Hourly time print at 15 minutes past each hour.

12 Apr 2012 20:15:00
12 Apr 2012 21:15:00
12 Apr 2012 22:15:00
12 Apr 2012 23:15:00
13 Apr 2012 00:15:00
Note: Even if the 'hourly time print' is disabled an automatic scanner functional test will occur on the hour every
hour!
After responding to the previous prompt, the Minute for hourly time print (0..59)? [0] prompt
is displayed. Enter the minute that the Hourly time print will be displayed. In the example above, the minute is
set to 15.
73
After responding to the previous prompt, the Alarm summary at midnight (Y,N)? [N] prompt is
displayed. Enter Y for the system to display an Alarm summary at midnight. Entering N will disable the Alarm
summary at midnight.
After responding to the previous prompt, the Alarm summary on reset (Y,N)? [N] prompt is displayed.
Enter Y for the system to display an Alarm summary when the system is rebooted. Entering N will disable the
Alarm summary when the system is rebooted.
After responding to the previous prompt, the Clear historical buffer on reset (Y,N)? [N]
prompt is displayed. Enter Y for the system to Clear the history when the system is rebooted. Entering N will
disable Clearing the history when the system is rebooted. Events are stored in battery backed RAM and are
retained even if power is interrupted. On start-up the pointers for each communications port are reset to their
last reported event so that no events are lost. Setting 'Clear historical events on reset' to 'Yes' causes the
battery backed RAM storage to be cleared and the pointers for the communications port to be reset to the start
of the event history.
MC>MM<cr>
Modify Miscellaneous Settings
Event indent (Alarm,Normal)? [Alarm]<cr>
Separate return legends (Y,N)? [Y]<cr>
Hourly time print (Y,N)? [Y]<cr>
Minute for hourly time print (0..59)? [0]<cr>
Alarm summary at midnight (Y,N)? [N]Y<cr>
Alarm summary on reset (Y,N)? [N]Y<cr>
Clear historical buffer on reset (Y,N)? [N]<cr>
Modify Miscellaneous Settings complete
MC>
In the example above, the user is accepting all of the current settings by pressing the Enter key at each
prompt.
After responding to the last prompt, the user is returned to the MC prompt.

configuration.
74
1.17.42 MN Modify Network sub menu
The MN Modify Network sub menu command takes the user to the MN sub menu. The MN sub menu
contains several commands that will allow the user to change and view the current configuration of the Network
for the QNet4100.
To get to the MW Modify Network sub menu command, enter MC from the main menu, then enter MN from the
MC menu.
After the user types MN at the MC Modify Configuration sub menu prompt, the system displays the
message Modify Network sub menu indicating that there is another menu with additional commands
available.
MC>MN<cr>
Modify Network sub menu
MN>?<cr>
ED Enable/Disable DHCP LN List Network Configuration
EI Enable/Disable IP Forwarding
ES Edit Name-Servers (DNS)
EH Edit Host Table
ER Edit Routing Table
MN>
In the example above, note that all of the commands available to the user on the MN sub menu are displayed
when the user enters a ? at the MN> prompt. For assistance with any of the commands available on the MN
sub menu, please refer to the documentation for a particular command in this manual.

configuration.
and the system will be automatically restarted. Note that changes made to the network
settings will require a reboot of the system.
1.17.43 MO Modify Output Assignments

The MO Modify Output Assignments command allows the user to assign the output of Scanner,
Diagnostic, External and Group points to particular port groups. Output is defined as alarm or return to normal
events for the points. This command also allows the user to enable or disable Time sorting for port groups.
To get to the MO command, enter MC from the main menu, then enter MO from the MC menu.
After entering the MO command, the system prompts the user for a Port group.
75
Select a Port group, enter a number from 1 to 32.
Enable or disable Time sorting for the Port group, enter Y to enable, N to disable. It is not recommended to
enable time sorting on port groups that handle critical alarms. When time sorting is enabled, events will be
held for the longest debounce time of the points that are reporting alarms. This could delay the reporting of a
critical alarm. Time Sorting of output ports is used when it is desirable to have the displayed or printed events
in time-sorted order, regardless of the debounce times. If time sorting is selected for a given Port, the
Controller waits for the duration of the longest programmed debounce time, at which time all the reported
events by the Scanners are time sorted. The Ports without time sort selection are not affected and will
continue to report the events as received by the Controller.
Select the type of points to assign, Scanner, Diagnostic, External or Group, enter S, D, X or G.
Select the scope of points to assign, Multipoint, Range or Single, enter M, R or S. If Range is selected, the
changes made to the first point may be easily applied to the entire range of points.
Single - enter a point to modify
Multipoint - enter a point to modify, make the desired changes, enter another point to modify...etc.
Range - enter the starting point and the ending point of the range.
Choose the types of events for the current point, to be assigned to this port group, None, Alarm, Normal or
Both (Alarm and Normal). Enter a dash for None, A for Alarm, N for Normal or B for Both.
If working with a range of points, Enter Y at the Same data (Y,N)? prompt to apply the same data to
the remaining points, or N to move on to the next point in the range.
After changing the scope of points selected above, the user returns to the type of points prompt. Enter S, D,
X or G to assign more points to the current port group, or press the Enter key to go back to the port group
prompt.
At the port group selection prompt, either select another port group from 1 to 32 or press the Enter key to exit
the command and return to the MC prompt.
MC>MO<cr>
Modify Output Assignments
Port group (1..32)? 1<cr>
Time sorted (Y,N)? [N]<cr>
None, Alarm, Normal, Both (-,A,N,B)? [B]A<cr>
Same data (Y,N)? Y<cr>
Port group (1..32)?<cr>
Modify Output Assignments complete
MC>
In the example above, Time sorting is not enabled for the port group, and the Alarm events of Scanner points 1
through 5 are assigned to Port group 1.
76
configuration.
and the system will be automatically restarted. Changes made to the output
assignments do not require a reboot.
1.17.44 MP Modify Ports sub menu

The MP Modify Ports sub menu command takes the user to the MP sub menu. The MP sub menu
contains several commands that allow the user to change and view the current configuration of the Ports for the
QNet4100.
To get to the MP Modify Ports sub menu command, enter MC from the main menu, then enter MP from the MC
menu.
After the user types MP at the MC Modify Configuration sub menu prompt, the system displays the
message Modify Ports sub menu indicating that there is another menu with additional commands
available.
MP>?<cr>
DP Delete Port Configuration LP List Port Configuration
MP Modify Port Configuration
MP>
In the example above, note that all of the commands available to the user on the MP sub menu are displayed
when the user enters a ? at the MP> prompt. For assistance with any of the commands available on the MP

configuration.
and the system will be automatically restarted. Note that changes made to the Port
settings will require a reboot of the system.
77
1.17.45 MP Modify Ports

The MP Modify Port Configuration command will allow the user to create, delete, or modify Port
configurations.
To get to the MP command, enter MC from the main menu, then enter MP from the MC menu, and then enter
MP from the MP menu.
After entering the MP command, the system prompts the user for a Port name. The user can enter a ? at the
prompt to see a list of existing port names. Port names are case sensitive. If an existing port name is entered,
the user will be modifying that port configuration. If a new port name is entered, a new port configuration will be
created after verifiying that the user would like to create a new port. Pressing the Enter key at this prompt will
exit the MP command and return the user to the MP prompt.
After choosing a port name the user is prompted for a protocol for the port. There are several protocols the user
may choose from. Enter a ? to see the available protocol choices.
Note: Ports assigned to an Annunciator, Clocks, or a CRT are automatically configured with a Baud Rate of
9600, and Data Bits of 8.
console - Enter the first few characters of the word console to select the console protocol, i.e "con".
Serial - There are 5 serial ports to choose from, serial port 1 through serial port 5. Enter a number from 1 to
5 to pick one of the serial ports to use with the console protocol.
Note - If serial port 1 or serial port 5 are selected, the user will be able to choose the fiber interface if it
has not already been used for another purpose.
Define the serial port through the next several prompts. The user will be prompted for Data bits, Parity,
Baud rate, hardware flow control, data set ready and data carrier detect. These settings need to match
the serial port settings of the attached device.
Select a Backup port if desired from the available serial ports. This port is used if communication is lost
with the designated serial port.
Select Local or UTC time. This will affect how timestamps are displayed in this console interface.
Assign the port to a port group. Any points that have output assigned to this port group will be displayed
in this console interface. Please refer to the documentation for the MO command for assistance with
assigning point outputs to port groups.
After configuring the port the user is returned to the Port name prompt again so they have a chance to
continue making changes to port configurations or creating new ones. Pressing the Enter key at this
prompt will return the user to the MP prompt.
An example of creating a new serial console port configuration:
MP>MP<cr>
Modify Port Configuration
Port name? serialConsole<cr>
Create a new port (Y,N)? Y<cr>
Protocol? []con<cr>
Setting protocol to: console
Network or serial port number (Network or 1,2,3,4,5)? []1<cr>
Use fiber interface (Y,N)?[N]<cr>
Data bits (7, 8)? [8]<cr>
Parity (O, E, N)? [N]<cr>
Baud rate? [9600]38400<cr>
Use hardware flow control (Y,N)? [N]<cr>
Require data set ready (Y,N)? [N]<cr>
78
Require data carrier detect (Y,N)? [N]<cr>
Backup port (1..5)? [1]<cr>
Display Local or UTC time (L,U)? [U]<cr>
Assign to port group (1..32)? [1]<cr>
Port name?<cr>
Modify Port Configuration complete
MP>
Network - Enter the first few characters of the word Network to select a network console port configuration,
i.e. "net".
The user will be prompted for a Network port number. Any available network port may be used with a
console interface. It is recommended that only network ports above 1000 are used.
The remaining prompts are similar to the serial console port configuration. Choose Local or UTC time
and the port group this port will be assigned to.
An example of creating a network console port configuration:
MP>mp<cr>
Port name? networkConsole<cr>
Protocol? []con<cr>
Setting protocol to: console
Network or serial port number (Network or 1,2,3,4,5)? []net<cr>
Network port number (0..65535)? [0]25001<cr>
Display Local or UTC time (L,U)? [U]L<cr>
Port name?<cr>
printer - Enter the first few characters of the word printer to select the printer protocol, i.e "pri".
Serial - A serial port must be selected and configured to use the printer protocol. The serial port settings
must match the serial port settings of the device. The remaining prompts are the same as the serial
console port configuration.
An example of creating a new printer port configuration:
MP>MP<cr>
Port name? printer<cr>
Protocol? []?<cr>
Available protocols:
console printer colorprint CRT BPA data annunciator DNP
Protocol? []pri<cr>
Setting protocol to: printer
Serial port number (1..5)? []2<cr>
Baud rate? [9600]<cr>
79

Port name?<cr>
MP>
colorprint - Enter the first few characters of the word colorprint to select the colorprint protocol, i.e "color".
Serial - A serial port must be selected and configured to use the colorprint protocol. The settings are the
same as the printer protocol settings, except for 2 prompts.
The user must enter the "Return-to-normal escape sequence" and the "Critical alarm escape sequence"
at the respective prompts.
An example of creating a new colorprinter port configuration:
MP>MP<cr>
Port name? colorprinter
Protocol? []color<cr>
Setting protocol to: colorprint
Return-to-normal escape sequence (decimal)? [0:0:0]<cr>
Critical alarm escape sequence (decimal)? [0:0:0]<cr>
Port name?<cr>
MP>
CRT - Enter crt to select the CRT protocol. The protocol is used with the adviSER interface.
Serial - The serial port is automatically configured with a baud rate of 9600 and 8 data bits. No further
configuration of the serial port settings is required. There are 3 prompts unique to the CRT protocol.
Enter values for the Horn and Ringback relays. Enter a number from 1 through 8 or the word None at the
relay prompts. The chosen relays must be configured for the appropriate function. The relay chosen to
be the Horn relay must be configured for the HN function. The relay chosen to be the Ringback relay
must be configured for the RB function. Please refer to the MR command for further assistance with
configuration of relays.
The user may choose to have an audible Beep when there is a new event. Enter Y for a beep on event
and N for silent events.
The remaining prompts are the same. Choose Local or UTC display time, and the port group.
An example of creating a new serial CRT port configuration:
80
MP>MP<cr>
Port name? serialCRT<cr>
Protocol? []crt<cr>
Setting protocol to: CRT
Horn relay (None or 1..8)? [None]1<cr>
Ringback relay (None, or 1..8)? [None]2<cr>
Beep on event (Y,N)? [N]Y<cr>
Assign to port group (1..32)? [1]3<cr>
Port name?<cr>
MP>
Network - Enter "net".

The user will be prompted for a Network port number. Any available network port may be used with a
console interface. It is recommended that only network ports above 1000 are used.
The rest of the prompts are the same as the prompts for the serial CRT port configuration.
An example of creating a network CRT port configuration:
MP>MP<cr>
Port name? networkCRT<cr>
Protocol? []crt<cr>
Setting protocol to: CRT
Beep on event (Y,N)? [N]Y<cr>
Horn relay (None or 1..8)? [None]1<cr>
Ringback relay (None, or 1..8)? [None]2<cr>
Assign to port group (1..32)? [1]3<cr>
Port name?<cr>
MP>
bpa - Enter bpa to select the BPA protocol.

Serial - The serial port settings are similar to the serial port settings of the serial console port configuration.
The user is not prompted for data bits or parity, the rest of the prompts to set up the serial port are the
same.
The remaining prompts are the same as most other ports. Choose Local or UTC display time, and the
port group.
An example of creating a new serial BPA port configuration:
MP>MP<cr>
Port name? serialBPA<cr>
81

Protocol? []bpa<cr>
Setting protocol to: BPA
Baud rate? [9600]38400<cr>
Port name?<cr>

The prompts are the same as they are for a network console port configuration.
An example of creating a network bpa port configuration:
Port name? networkBPA<cr>

Protocol? []bpa<cr>
Setting protocol to: BPA<cr>
Port name?<cr>
data - Enter data to select the data protocol.

Serial - The serial port settings are the same as the serial port settings of the serial console port
configuration.
The remaining prompts are the same as the remaining serial port console prompts except for 1 prompt.
The user is not prompted for a backup port.
An example of creating a new serial data port configuration:
MP>MP<cr>
Port name? serialData<cr>
Protocol? []data<cr>
Setting protocol to: data<cr>
82
Port name?<cr>
MP>

The prompts are the same as they are for a network console port configuration.
An example of creating a network data port configuration:
MP>MP<cr>
Port name? networkData<cr>
Protocol? []data<cr>
Setting protocol to: data
Port name?
annunciator - Enter the first few characters of the word annunciator to select the annunciator protocol, i.e
"ann".
Serial - A serial port must be selected and configured to use the annunciator protocol. The only serial port
setting to be set is the baud rate.
The user is prompted to enter a serial port to be used as the Annunciator configuration port. An
annunciator configuration port may be configured from one of the remaining serial ports. An annunciator
configuration port is required before the user can use the SW, RW and CW commands. Please refer to
the documentation on the Modify Annunciator sub menu for further assistance with these commands.
Lastly the user is prompted for a port group for the port to be assigned to.
An example of creating a new annunciator port configuration:
MP>MP<cr>
Port name? annunciator<cr>
Protocol? []ann<cr>
Setting protocol to: annunciator
Annunciator Configuration port (1..5, or 0 to disable)? [0]3<cr>
Port name?<cr>
MP>
DNP - Enter dnp to select the DNP protocol.

Serial - The only serial port setting to be set is the baud rate.
There are 3 unique prompts for the DNP protocol. The first one is the Maximum number of events in
report. This can be a number from 1 to 100.
83
Enter a number for The Master station address from 1 to 65500.

Enter a number for the Station address from 1 to 65500.
Lastly the user is prompted for a port group for the port to be assigned to.
An example of creating a new serial DNP port configuration:
MP>MP<cr>
Port name? serialDNP<cr>
Protocol? []dnp<cr>
Setting protocol to: DNP
Maximum number of events in report (0..100)? [50]<cr>
Master station address (1..65500)? [65000]<cr>
Station address (1..65500)? [1]<cr>
Port name?<cr>
MP>

The prompts for the network DNP port configuration are similar to the prompts for the serial DNP port
configuration, but there are 4 more prompts for the network configuration. The 4 additional prompts are:
Enter UDP or TCP
DNP server port number. Enter a number from 0 to 65535.
Master station IP address. The DNP master station can be found at this address on the DNP server
port number.
Enter a value from 1 to 60000 for the TCP accept connection timeout. This represents the number of
milliseconds to wait when connecting to the server before the connection attempt times out. A value of
5000 here represents waiting 5 seconds for the connection attempt to time out.
The remaining prompts are the same as the prompts for the serial DNP port configuration.
An example of creating a network DNP port configuration:
MP>MP<cr>
Port name? networkDNP<cr>
Protocol? []dnp<cr>
Setting protocol to: DNP
UDP or TCP? [TCP]<cr>
DNP server port number (0-65535)? [20000]<cr>
Master station IP address (*.*.*.* allows any)? [*.*.*.*]12.34.56.78<cr>
TCP accept connection timeout mS (1..60000)? [5000]<cr>
Maximum number of events in report (0..100)? [50]<cr>
Master station address (1..65500)? [65000]<cr>
Station address (1..65500)? [1]<cr>
Port name?<cr>
84
MP>
Pressing the Enter key at the Port name? prompt will exit the MP command and return the user to the MP
prompt.

configuration.
and the system will be automatically restarted.. Changes made to the port
configurations will require a reboot of the system.
1.17.46 MQ Modify QNet ID

The 'MQ Modify QNet ID' command allows for the QNet4100 'Station name' and 'Station number' to be
changed.
MC>MQ<cr>
Modify QNet ID
QNet4100
Station number 1
28 Jan 2012 17:25:24
Station name [QNet4100]? Fairport-230KV-Substation<cr>
Station number (1..255)[1]? 6<cr>
MC>
The command may also be entered in terse fashion:
MC>MQ;Fairport-230KV-Substation;6<cr>
Modify QNet ID
Modify QNet ID complete
MC>
The 'Station name' provides unique identification of the system and is shown in the header for all system reports
and is also used to generate the systems network 'hostname' label.
To ensure correct identification of the systems to the network it is recommended that the 'Station name' is
changed before connecting the system to the network such that a unique 'hostname' is generated for each
individual system that may be connected.
While the 'Station name' field can accept up to 60 ASCII characters and can contain any printable character
other than the semicolon, a hostname can contain only the letters ('A' through 'Z' or 'a' through 'z') , digits ('0'
through '9'), and the hyphen (-). In some networks the 'hostname' may also be restricted to start only with a
letter ('A' through 'Z' or 'a' through 'z'), and / or to end only with a letter or digit ('A' through 'Z', a through 'z' or '0'
85
through '9'). In generating the 'hostname' label the controller will truncate the 'Station name' at the first illegal
character!
The following table shows examples of 'Station names' and the resulting 'hostname' label.
Station name Resulting 'hostname' label

St. Lawrence 380kV Substation St The period in St. Lawrence is first
illegal hostname character.
Watkins Glen 66kV Substation Watkins The 'Space' is the first illegal
character.
1st-Street-Substation 1st-Street-Substation All characters in the station name
are valid hostname characters,
however, since the name starts with a
digit this may result in an illegal
hostname in some networks.
-Miranda-11KV-Substation -Miranda-11KV-Substation All characters in the station name
however, since the label starts with a
hyphen this may result in an illegal
Valley-Brook-115KV-Line- Valley-Brook-115KV-Line- All characters in the station name
however, since the label end with a
hyphen this may result in an illegal
Watkins-Glen-380KV-Substation Watkins-Glen-380KV-Substation All characters in the station name
are valid hostname characters.
The 'Station number' provides a numeric identification for the system. This is an arbitrary setting and has no
useful function in the system and is provided for compatibility with earlier SER128plus, SER512, SER7000 and
SER4100 systems only.
[The SER128plus, SER512, SER7000 and SER4100 provided an Fiber Optic SDLC protocol for communication
with a Master Station via the Auxiliary Controller Module and Fiber Optic Network Controller. The 'Station
number' was used as the SDLC address for each system. Address '0' was reserved for the Master Station and
only addresses 1 through 255 were legal addresses for the SER. The Fiber Optic SDLC protocol is no longer
supported by the QNET4100 controller. Where specific equipment addresses are required by a protocol, such
as MODBUS or DNP, the address is set for that individual protocol in the port configuration and is specific to
the communication port rather than as a global address for the entire system.]
The 'Station number' may be set to any value from 1 to 255 (a value of 0 is not supported).
The default 'Station name' for the system is 'QNet4100' and the default 'Station number' is '1'.
Changing the 'Station name or 'Station number' WILL NOT cause the system to reboot on exit from the Modify
Configuration sub menu.
1.17.47 MR Modify Relay Configuration

Executing the MR Modify Relay Configuration command gives the user access to software that can program the
8 Auxiliary Relays.
86
Relays are designated numerically 1 - 8 ,and are assigned a function through a 2 character keyboard
commands.
There are 9 functional modes that can be programmed.
Command Function
CA Continuous Relay will be always operate on Alarm
Alarm
CN Continuous Relay will not operate until all assigned points are in the alarm state.
Normal
PA Pulse Alarm Relay will Pulse on Alarm
PN Pulse Relay will pulse on Return-To-Normal
Normal
PB Pulse Both Replay will pulse on both Alarm ad Return-To-Normal
The Relay is de-energized when the first alarm condition is detected. Subsequent alarms
RF Reflash cause the
Relay to pulse.
HN Horn Relay Relay will signal an audible alarm in the event of an Alarm condition, Return-to-Normal
condition, or a diagnostic error
RB Ringback
The Relay is normally energized; De-energized on Alarm-To-Normal; Reset by Silence
Input
-- The Relay is disabled.
After the user types MC>MR<cr> at the at the MC Modify Configuration sub menu prompt, the system prompts
the user to select a Relay number: to assign Relay number (1..8)? In the example below the user
selected Relay 2 (1..8)? 2<cr>
The system then prompts the user to select what function will be assigned Relay mode (CA,CN,PA,PN,
PB,RF,HN,RB or - to disable)? [--]. In the example, the user selected CN Continuous Normal
(CA,CN,PA,PN,PB,RF,HN,RB or - to disable)? [--]CN<cr>.
The next prompt requires that the user determine what Relay will be used when assigned a point in the Point for
Silence all Relays step of this command In the example, the user selected the default Relay number
(1..8)? .
The system then prompts the user to determine what point on the Relay will be used to silence all Relays
Point for silence all relays (1..64 or - to disable)? [-]. In the example, the user
selected point 64 Point for silence all relays (1..64 or - to disable)? [-] 64<cr>
MC>MR<cr>
Modify Relay Configuration
Relay number (1..8)? 2<cr>
Relay mode (CA,CN,PA,PN,PB,RF,HN,RB or - to disable)? [--]CN<cr>
Relay number (1..8)? <cr>
Point for silence all relays (1..64 or - to disable)? [-] 64<cr>
87
Modify Relay Configuration complete
- Pulse on Alarm (PA) mode:

Energize for approx 500mS, and then de-energize, when any group output that is mapped to it changes
from FALSE to TRUE.
- Pulse on Normal (PN) mode:

from TRUE to FALSE.
- Pulse on Both (PB) mode:

from FALSE to TRUE or from TRUE to FALSE.
- Reflash (RF) mode:

Energize when any group output that is mapped to it becomes TRUE.
De-energize for approx 500mS, and then re-energize, when any group output that is mapped to it is
TRUE and another group - output that is mapped to it changes from FALSE to TRUE.
De-energize, and remain de-energized, when all group outputs that are mapped to it become FALSE.
- Continuous on Alarm (CA) mode:

Energize when any group output that is mapped to it becomes TRUE.
De-energize when all group outputs that are mapped to it become FALSE.
- Continuous on Normal (CA) mode:

Energize when any group output that is mapped to it becomes FALSE.
De-energize when all group outputs that are mapped to it become TRUE.
- Horn (HN) mode:

Energize when any group output that is mapped to it changes from FALSE to TRUE and will remain
energized even if all inputs return to FALSE.
De-energize when the group output associated with Relay Silence changes from TRUE to FALSE.
- Ringback Horn (RB) mode:

Energized when any group output that is mapped to it changes state from TRUE to FALSE and will
remain energized even if all inputs return to TRUE.
De-energize when the group output associated with Relay Silence changes from TRUE to FALSE.
Mode Description
CA Continuous on Alarm:
The relay will energized when any group output associated with it becomes TRUE and will de-
energize only when all group outputs associated with it become FALSE.
CN Continuous on Normal:
The relay will energized when any group output associated with it becomes FALSE and will de-
energize only when all group outputs associated with it become TRUE.
PA Pulse on Alarm:
The relay will energized when any group output associated with it changes from FALSE to
TRUE and will de-energize after approximately 1/2 second. (See 'Special input functions' above )
.
PN Pulse on Normal:
88
Mode Description
The relay will energized when any group output associated with it changes from TRUE to
FALSE and will de-energize after approximately 1/2 second. (See 'Special input functions'
above)
PB Pulse on Both:
The relay will be energized when any group output associated with it changes from the FALSE
to TRUE or from TRUE to FALSE and will de-energize after approximately 1/2 second. (See
'Special input functions' above)
RF Re-Flash:
The relay will energized when the first group output associated with it becomes TRUE. When
any subsequent group output associated with it changes from the FALSE to TRUE the relay will
de-energize for approximately 1/2 second and then re-energize. The relay will de-energize and
remain de-energized only when all group outputs have returned to FALSE. (See 'Special input
functions' above)
HN Horn:
The horn relay is intended to be use to sound an audible device associated with one or more
AdviSER or alarm annunciators displays. The audible will sound when any new alarm occurs.
The displays are associated with the relay using the special 'Unacknowledged alarm in port
group' input function (See 'Special input functions' above).
The relay will energized (sound the audible) when any input associated with the port group
becomes goes into alarm condition and will de-energize (silence the audible) when:
- the Mute function function is used (See 'Special output functions' below)
- the AdviSER silence button is used (See CRT protocol and Adviser alarm display.)
- the silence all relays scanner input point is initiated (See MR Modify Relay
Configuration command).
- all inputs to the group have been acknowledged using the Acknowledge function (see 'Special
output functions' below).
- all inputs to the group have been acknowledged using the AdviSER Acknowledge button. (See
CRT protocol and Adviser alarm display.)
See also MI Modify Input Configuration command - Manual and Automatic Reset
Alarm Sequence).
RB Ringback:
The ringback relay is intended to be used to sound an audible device associated with one or
more AdviSER or alarm annunciators displays. The audible will sound when a point configured
for manual reset alarm sequence is ready for reset. (That is; the alarm has been acknowledged
and the input has returned to the normal condition). The displays are associated with the relay
using the special 'Unacknowledged return-to-normal in port group' function (See 'Special input
functions' above).
The relay will energized (sound the audible) when any input associated with the port group
returns-to -normal and the associated alarm event is acknowledged and will de-energize (silence
the audible) when when:
- the Mute function function is used (See 'Special output functions' below)
- the AdviSER silence button is used (See CRT protocol and Adviser alarm display.)
- the silence all relays scanner input point is initiated (See MR Modify Relay
Configuration command).
- all inputs to the group have been reset using the Clear function (see 'Special output functions'
below).
- all inputs to the group have been reset using the AdviSER Reset button. (See CRT protocol
and Adviser alarm display.)
89
Mode Description
See also MI Modify Input Configuration command - Manual and Automatic Reset
Alarm Sequence).
1.17.48 MS Modify Scanners

The 'MS Modify Scanners' command allows for the QNet4100 scanner modules to be enabled or disabled.
A QNet4100 system can contain up to 64 Scanner Modules. Each scanner module is assigned a unique
address, either by its physical location in the chassis, or by manually setting the Scanner Modules DIP
switches (see 'Chassis addressing' and 'Scanner Module addressing'). A Scanner Module must be enabled
before it can communicate with the Controller Module.
The 'MS Modify Scanners' command allows the QNet 4100 scanners modules to be enabled or disabled:
MC>MS<cr>
Modify Scanners
Scanner(s) to enable (1..64)? [1 8]2<cr>
Scanner(s) to enable (1..64)? [1 2 8]5<cr>
Scanner(s) to enable (1..64)? [1 2 5 8]<cr>
Scanner(s) to disable (1..64)? [3 4 6 7 9..64]8<cr>
Scanner(s) to disable (1..64)? [3 4 6..64]<cr>
MC>
The above will enable scanners 2 and 5 and disable scanner 8.
A carriage return (<cr>) alone is entered in response to the 'Scanner(s) to enable?' or 'Scanner(s) to
disable?'to complete the list.
The command may also be entered in terse fashion:
MC>MS;2;5;;8;;<cr>
Modify Scanners
MC>
Note: The double semicolon is used to signify the end of the 'Scanners to enable' and 'Scanner to disable'
list.
Terse entry may also be used within a command to allow enabling or disabling of scanner on a single line:
MC>MS<cr>
Modify Scanners
Scanner(s) to enable (1..64)? [1 8]2;5;;<cr>
Scanner(s) to disable (1..64)? [3 4 6 7 9..64]8;;<cr>
MC>
Note:
Scanners that are not explicitly enabled or disabled are unaffected; for example scanner 1 above was previously
90
enabled it will remain enabled, and scanner 3 above was previously disabled it will remain disabled!
The default setting enables Scanner Module 1 only; scanners 2 through 64 are disabled.
Enabling or disabling scanners WILL cause the system to reboot on exit from the Modify Configuration sub
menu.
1.17.49 MT Modify Time Sync Configuration

The MT Modify Time Sync Configuration command will allow the user to modify the configuration of
the system external time sources and internal oscillator.
To get to the MT command, enter MC from the main menu, then enter MT from the MC menu.
Note: The ? Context Help command can be used on most prompts to list available choices within the MT
Modify Time Sync Configuration command.
After entering the MT command, the system prompts the user for the desired time source. The available
choices for time sources are as follows:
None - Enter none to choose this option. The internal time source is used when this is selected.
NMEA - Enter nmea to select the NMEA time source. There are many PPS options available with this time
source. The system can synchronize to the rising edge of the PPS pulse, the falling edge, using copper
serial ports, fiber serial ports and modem signals.
The user is always prompted for a serial port when using the NMEA time source. Note that serial ports 2
through 5 are available for this function. When using a fiber interface serial port 5 must be used.
An example of configuring the system to use a NMEA MDM CDUP PPS signal for time synchronization.
The remaining prompts for MT are not shown.
MC>MT<cr>
Modify Time Sync Configuration
Precision time source? [NMEA]?<cr>
None - No time source selection IRIG - IRIG-B time source
NMEA - NMEA 0183 serial input stream PPS - Pulse per second correction
PPM - Pulse per minute correction PPH - Pulse per hour correction
Precision time source? [NMEA]<cr>
NMEA PPS connection? [MDM]?<cr>
NoPPS - No PPS signal MDM - PPS signal on modem signal
PPSR - TTL PPS on rising edge PPSF - TTL PPS on falling edge
FPPSR - Fiber PPS on rising edge FPPSF - Fiber PPS on falling edge
NMEA PPS connection? [MDM]<cr>
Type of PPS? [CDUP]?<cr>
CDUP - PPS when CD asserted CDDN - PPS when CD removed
DSRUP - PPS when DSR asserted DSRDN - PPS when DSR removed
CTSUP - PPS when CTS asserted CTSDN - PPS when CTS removed
Type of PPS? [CDUP]<cr>
NMEA serial port (2,3,4,5)? [2]<cr>
PPM - Enter ppm to choose Pulse per minute synchronization. The system synchronizes to an external
pulse received every minute on a designated scanner input point. The only information required to configure
91
this time source is that scanner point number.

Enter scanner point number for PPM pulse. Choose the scanner point from the available scanner points in
the range indicated in parentheses in the scanner point number prompt. The system will synchronize to
the PPM pulse if it is received between 5 seconds before changing to the next minute and 5 seconds after
changing to the next minute. This is a 10 second window that the pulse must be received in. If the pulse
is received outside of that timespan the pulse is ignored. If a synchronizing pulse is not received when
expected, the primary time failure diagnostic point will go into alarm.
An example of configuring the system to use a PPM pulse as an external time source. The remaining
prompts for MT are not shown.
MC>MT<cr>
Precision time source? [PPM]<cr>
Scanner point number (1..64)? [32]64<cr>
IRIG - Enter irig to select the IRIG-B time source. There are many PPS options available with this time
source. The PPS options can be broken down into 3 categories. TTL, Modulated and Fiber. Each of these 3
categories has the same 3 choices within it, No year, BCD year and IEEE. IEEE can include the year and is
always displayed in UTC time. The other 2 choices prompt for UTC or Local time.
Enter TTL, modulated or fiber. These entries must be spelled out in entirety.
Enter noyear, IEEE, or bcdyear. These entries also must be spelled out completely.
Enter Y at the "is Local time" prompt if the IRIG time source is set to local time. This prompt won't be
displayed if IEEE is chosen as IEEE is always set to UTC time.
An example of configuring the system to use an IRIG-B PPS pulse as an external time source. In this
example an IRIG Modulated BCDyear time source is configured. The remaining prompts for MT are not
shown.
MC>MT<cr>
Precision time source? [IRIG]?<cr>
Precision time source? [IRIG]<cr>
IRIG-B connection? [TTL]?<cr>
TTL - TTL signal source Fiber - Fiber signal source
Modulated - Modulated IRIG-B signal
IRIG-B connection? [TTL]modulated<cr>
IRIG-B code type? [NoYear]?<cr>
NoYear - IRIG-B signal without year BCDYear - IRIG-B signal with year
IEEE - IRIG-B with IEEE 1344 ext
IRIG-B code type? [NoYear]bcdyear<cr>
IRIG B is Local time (Y,N)? [N]<cr>
PPS - Enter pps to choose Pulse per second synchronization. The system synchronizes to an external
pulse received every second. There are four possible choices for this time source, two copper and two fiber
PPS inputs. The system can synchronize to the rising edge or the falling edge of either type of interface.
Enter the desired PPS choice from the four possiblities. The two copper choices are PPSR and PPSF,
and the two fiber choices are FPPSR and FPPSF. Take care to only choose a fiber interface option if the
92
fiber port is available for use.
An example of configuring the system to use a PPS pulse as an external time source. In this case the
system will synchronize to the rising edge of the PPS signal on the fiber interface. The remaining prompts
for MT are not shown.
MC>MT<cr>
Precision time source? [IRIG]PPS<cr>
Type of PPS? [FPPSR]?<cr>
PPSR - TTL PPS on rising edge FPPSR - Fiber PPS on rising edge
PPSF - TTL PPS on falling edge FPPSF - Fiber PPS on falling edge
Type of PPS? [FPPSR]<cr>
PPH - Enter pph to choose Pulse per hour synchronization. The system synchronizes to an external pulse
received every hour on a designated scanner input point. The only information required to configure this time
source is that scanner point number.
Enter scanner point number for PPH pulse. Choose the scanner point from the available scanner points in
the range indicated in parentheses in the scanner point number prompt. The system will synchronize to
the PPH pulse if it is received between 5 minutes before changing to the next hour and 5 minutes after
changing to the next hour. This is a 10 minute window that the pulse must be received in. If the pulse is
received outside of that timespan the pulse is ignored. If a synchronizing pulse is not received when
expected, the primary time failure diagnostic point will go into alarm.
An example of configuring the system to use a PPH pulse as an external time source. The remaining
prompts for MT are not shown.
MC>MT<cr>
Precision time source? [IRIG]PPH<cr>
Scanner point number (1..64)? []64<cr>
Trained Oscillator:
After entering the desired time source the user is prompted to set the high stability oscillator setting. Enter Y
at this prompt if there is a high stability oscillator in the system or enter N if there is not.
If the controller module is fitted with a high stability oscillator option either it or the standard oscillator may
be used as the trained oscillator source:
The system will prompt for a Trained oscillator base value. This value is used only at start up to
correct the oscillator frequency. After startup the system will automatically adjust the trained oscillator
value at 20 second intervals while it is receiving an IRIG B, NMEA with PPS or PPS precision time source
input signal
93
Use high stability oscillator (Y,N)? [N] n<cr>

Trained oscillator base value?[0] 300<cr>
Modify Time Sync Configuration complete
MC>
Next, the user is prompted to Transmit PPS on fiber. Enter Y to transmit PPS on the fiber interface.
NTP backup time source:
After configuration of the precision time source the system will prompt for an NTP server IP address
and, if an IP Address is entered, will prompt for an Alternative NTP server IP Address.
If an IP Address is not entered NTP backup synchronization will not be used:
NTP server IP address?[] 10.75.2.39<cr>

Alternate NTP server IP address?[] 10.75.2.21<cr>
After the last value is entered for the last prompt, the user will exit the MT command and return to the MC
prompt.

configuration.
and the system will be automatically restarted. Changes made to the time
synchronization settings require a reboot.
1.17.50 MV Modify Vocabulary (Language)

The 'MV Modify Vocabulary (Language)' command is used to set the system 'Language'.
MC>MV<cr>
Modify Vocabulary (Language)
Language? [english] ?<cr>
english spanish french german
Language? [english] spanish<cr>
Modify Vocabulary (Language) complete
MC>
Using the '? Context Help' command at the 'Language' prompt will list the language files available.
The new language will take effect only after saving the changes, exit exiting the Modify Configuration sub menu
and rebooting the system.
94
By default the QNet4100 Controller Module is supplied with all console commands, menus items and prompts
in the English language. Additional languages may be added to the controller based on an order specific basis.
The default setting for 'Language' is English.
1.17.51 MW Modify Annunciators sub menu

The MW Modify Annunciators sub menu command takes the user to the MW sub menu. The MW sub
menu contains several commands that allow the user to change and view the current configuration of the
Annunciators and the Annunciator Windows for the QNet4100.
An Annunciator is a device that is used to call attention to an abnormal process condition. The Annunciator
includes individual illuminated visual displays that will flash, or trigger an audible bell or horn to attract the user's
attention when the alarm condition is detected. The user can then silence the alarm manually, and the window
will remain lit as long as the condition is in the alarm state. When the alarm clears (process condition returns to
normal), the lamps and audible alarms clear.
To get to the MW Modify Annunciators sub menu command, enter MC from the main menu, then enter MW
from the MC menu.
After the user types MW<cr> at the MC Modify Configuration sub menu prompt, the system displays
the message Modify Annunciators sub menu indicating that there is another menu with additional
commands available.
MW>?<cr>
MA Modify Annunciator LW List Annunciator Windows
SW Send Configuration to Annunciators
RW Get Annunciator Report
CW Clear Window States
MW>
In the example above, note that all of the commands available to the user on the MW sub menu are displayed
when the user enters a ? at the MW> prompt. For assistance with any of the commands available on the MW

configuration.
and the system will be automatically restarted. Changes made to annunciators or
windows do not require a reboot of the system.
95
1.17.52 MW Modify Annunciator Windows

The MW Modify Annunciator Windows command allows the user to modify the configuration of the
annunciator windows for an annunciator pair. Use the MA Modify Annunciator command, found in the MW
Modify Annunciators sub menu to modify the configuration of an annunciator pair.
The Annunciator Window settings are as follows:
Sequence group
Audible
Point assignments
To get to the MW command, enter MC from the main menu, then enter MW from the MC menu, then enter MW
from the MW menu.
After entering the MW command, the system will prompt the user to enter the Annunciator pair number. The
user may exit the command by pressing the Enter key at this Annunciator to modify (0..63)?
prompt. To continue modifying an annunciator window, enter one of the annunciator numbers of the annunciator
pair the annunciator window belongs to. For example, if the user enters 0 they will be modifying the windows in
the configuration of annunciator pair 0, 1. Similarly, if the user enters 1, they will still be modifying the windows
in the configuration for annunciator pair 0, 1.
After entering a value for the previous prompt, the Window to modify (1..64)? prompt is displayed. The
value entered must be in the range indicated by the prompt. There are 64 annunciator windows in each
annunciator pair. Enter the number of the Window to modify.
After responding to the previous prompt, the Sequence group (A..E)? [B] prompt is displayed. The
user may enter any letter from A to E to represent the desired sequence group for this window. Only 1
sequence group may be chosen for a particular annunciator window.
After entering a value for the sequence group, the Audible (0,1)? [1] prompt is displayed. There are
only 2 possible valid values for this setting. 0 indicates there is no audible alarm associated with this
annunciator window alarm event. A value of 1 indicates there is an audible alarm associated with this
annunciator window alarm event.
After responding to the previous prompt, the Point assignment(s) (1..4096)? [1] prompt is
displayed. This setting will accept multiple values, separated by commas. The values entered for this prompt
represent the scanner points this annunciator window will respond to. In addition to entering either a single
value for a point, or multiple points separated by commas, the user may enter a range of points separated by a
dash [FIRST-LAST]. To clear out previously entered values, enter a dash at the prompt. This also disables the
window.
After responding to the previous prompt, the configuration for that particular annunciator window is complete.
Now, the user may configure another annunciator window by entering its value at the Annunciator to
modify (0..63)? prompt.
MW>MW<cr>
Modify Annunciator Windows
Annunciator to modify (0..63)? 0<cr>
Window to modify (1..64)? 1<cr>
Sequence group (A..E)? [A]<cr>
96
Audible (0,1)? [1]<cr>
Point assignment(s) (1..4096)? [1]1<cr>
Window to modify (1..64)?<cr>
Modify Annunciator Windows complete
MW>
In the example above, The configuration for Window 1 in Annunciator pair 0, 1 is being modified. The Sequence
group is left at A, the Audible setting is left at 1, and the point assignment is left at scanner point 1.
After the user is finished modifying Annunciator Windows, they may press the Enter key at the Annunciator
to modify (0..63)? prompt to exit the command and return to the MW sub menu.

configuration.
and the system will be automatically restarted.. Changes made to annunciators
or windows do not require a reboot of the system.
1.17.53 MZ Modify Time Zone

The 'MZ Modify Time Zone' command allows for the local time zone to be set:
Internally the QNet4100 stores time in Coordinated Universal Time (UTC), however, each display or printer
port can be configured to display the time in either UTC or local 'Time zone'.
MC>MZ<cr>
Modify Time Zone
Region? [America]?<cr>
Indian Pacific
Region? [America]Europe<cr>
Country? []?<cr>
AalandIslands Albania Andorra Austria
Belarus Belgium Bosnia_Herzegovina Britain_UK
Bulgaria Croatia CzechRepublic Denmark
Estonia Finland France Germany
Gibraltar Greece Guernsey Hungary
Ireland IsleofMan Italy Jersey
Latvia Liechtenstein Lithuania Luxembourg
Macedonia Malta Moldova Monaco
Montenegro Netherlands Norway Poland
97
Portugal Romania Russia SanMarino

Serbia Slovakia Slovenia Spain
Sweden Switzerland Turkey Ukraine
VaticanCity
Country? []Germany<cr>
Time zone? []?<cr>
Berlin
Time zone? []Berlin<cr>
Modify Time Zone complete
MC>
The Modify Time Zone command will prompt for a 'Region', then for a 'Country' within that 'Region', and then for a
'Time zone' within the 'Country'.
Entering the context help command ('?') at a 'Region', 'Country' or 'Time zone' prompt will display a list of
available entries.
Note:
Entries are not case sensitive but punctuation or special symbols must be entered.
Appendix A provides a full alphabetic listings of all available;

- 'Regions'
- 'Country' (by 'Region')
- 'Time zone' (by 'Countries' and 'Region')
The time zone files stored in the QNet4100 include information about the offset from UTC to the selected time
zone and, where applicable, the start and end of Daylight Savings Time (DST). This includes the current rules
and rules that have applied in previous years. Time zone rules are continuously changing; from time-to-time
Qualitrol will publish an update for the time zone files for the QNet4100. There is no need to update the time
zone files unless the DST rules that are applicable for your time zone have changed.
The default settings for the 'Region','Country' and 'Time zone' are 'Amierica', 'UnitedStates' and 'New_York'
respectively.
More information about time zones and both historic and recent changes can be found at the following web
site: http://cs.ucla.edu/~eggert/tz/tz-link.htm.
Changing the time zone WILL cause the system to reboot on exit from the Modify Configuration sub menu.
1.17.54 RA Report Alarm Summary

The RA Report Alarm Summary command provides a report of all scanner, diagnostic, external and group
points that are currently in the alarm state as well as any scanner points that been automatically deleted from
logging or that have failed a functional test.
>RA<cr>
QNet4100
Station number: 1
11 Feb 2012 18:58:03
Report Alarm summary
Scanner points in alarm:
scanner points that are currently in alarm state
98
Auto deleted scanner points:
scanner points that are currently automatically deleted from logging
Failed Scanner points:

scanner points that have failed last functional test
Diagnostic points in alarm:

diagnostic points that are currently in alarm state
External points in alarm:

external points that are currently in alarm state
Group points in alarm:

group points that are currently in alarm state
Report Alarm Summary complete

>
The Report Alarm Summary command may also be initiated automatically when the system is rebooted or at
midnight.
See also:
MM Modify Miscellaneous Settings
1.17.55 RH Report History

The RH Report History command provides a sequence of events (SOE) report that match the entered
parameters.
Events may be selectively reported as a function of three separate parameters:

- As a function of up to any 10 point addresses or all points. Point addresses are entered using the point
type (S, D, X or G) followed by the unique point ID, and are separated by a semi-colon (';').
- As a function of a designated start date and time and end date and time or with no time limitations.
- As a function of the number of the most recent events or all events. Up to 100,000 events can be reported.
Each parameter may be used individually or collectively. For example:
>RH<cr>
QNet4100
Station number: 1
8 Feb 2012 11:48:05
Report History
Point numbers (All, or up to ten points - S,D,X,G followed by number)? S1;
D1<cr>
Start date (All, or MM/DD/YY)? 01/15/12<cr>
Start time (HH:MM:SS)? 08:00:00<cr>
End date (MM/DD/YY)? 01/30/12<cr>
End time (HH:MM:SS)? 07:30:00<cr>
Number of historical events (1..100000 or All)? A<cr>
SOE report
>
99
Using the escape key (Esc) during a report will terminate the report.
If a new event occurs during a report listing, it will be reported when it occurs (in the middle of the list) and will
not be a part of the list.
The RH report History command will report points from the historical buffer irrespective of the port
assignment; i.e even if a point is not routed to a port using the MO Modify Output Assignments
command, the events for that point will still be reported when an RH Report History command is initiated.
See also
1.17.56 RI Report Input State

The RI Report Input State command provides a report of the current state of the selected input points.
The system will prompt for the type of input and the scope of the command and will report the point current
state as;
- ENABLED & ALARM
- ENABLED & NORMAL
- DISABLED (point was disabled using the EX Edit Exception command).
- DISABLED in config (point was disabled using the MI Modify Inputs command).
Disabled points are always considered as in the NORMAL state.
>RI<cr>
QNet4100
Station number: 1
8 Aug 2011 12:42:46 f
Report Input State
Scanner, Diagnostic, External, Group (S,D,X,G))? S<cr>
current point state report
Scanner, Diagnostic, External, Group (S,D,X,G))?<cr>
Report Input State complete
>
Entering a carriage return (<cr>) alone at the Scanner, Diagnostic, External, Group prompt will
terminate the command.
See also:
EX Edit Exceptions
MI Modify Inputs
1.17.57 RQ Report QNet ID

The RQ Report QNet ID command simply reports header text which includes the station name, station
number, the current system date and time and time quality character. The report also includes the current
controller state as either primary or backup.
100
>RQ<cr>
QNet4100
Station number: 1
8 Aug 2011 13:43:07 f
QNet4100 is Primary controller
Station number: 1
Report QNet ID complete
>
In a QNet4100R type system one of the controllers will always be reported as the primary controller and the
other as the backup controller. Both controllers will 'listen' for events from the scanner modules but only the
primary controller will send information to the scanner modules.
See also:
QNet4100R Redundant Controller System
1.17.58 RT Report Time

The RT Report Time command simply reports the header text which includes the station name, station
number, the current system date and time and time quality character.
>RT<cr>
QNet4100
Station number: 1
12 Feb 2012 16:53:10 f
Report Time complete
>
See also:
MQ Modify QNet ID
Time Quality
1.17.59 RU Report Update

The RU Report Update command provides a report of events that have occurred since the the last time the
command was initiated.
>RU<cr>
QNet4100
Station number: 1
8 Feb 2012 12:20:05
Report Update
SOE report of all events since last RU command
Report Update complete
>
Using the escape key (Esc) during a report will terminate the report and any events not yet reported will be
reported the next time that the RU Report Update command is initiated.
101
The RU Report Update command will report points from the historical buffer irrespective of the port
assignment; i.e even if a point is not routed to a port using the MO Modify Output Assignments
command, the events for that point will still be reported when an RU Report Update command is initiated.
See also
1.17.60 RW Get Annunciator Report

The RW Get Annunciator Report command allows the user to query the annunciators for the status of
the Annunciator Windows. Note that an Annunciator Configuration port is required for communcation to the
annunciator modules. Therefore, this command will not be able to get the annunciator report unless a
functioning annunciator configuration port is present in the system. Please refer to the documentation found in
this manual for the MP Modify Ports command, if further assistance is required to configure an Annunciator
Configuration port.
To get to the RW command, enter MC from the main menu, then enter MW from the MC menu, then enter RW
from the MW menu.
After entering the RW command, the system requests the report from the annunciator modules through the
Annunciator configuration port. If the request is successful, the annunciator report is displayed. The report
shows the current status of all of the annunciator windows in the system.
MW>RW<cr>
Get Annunciator Report
Annunciator configuration port is not configured
Get Annunciator Report complete
MW>
In the example above, the system cannot display the annunciator report because the Annunciator configuration
port is not configured.
After the Annunciator report is displayed, the user is returned to the MW sub menu prompt.

configuration.
102
1.17.61 RX Report Exceptions
The RX Report Exceptions will report any points that have been temporarily disabled using the EX Edit
Exceptions command.
>RX<cr>
QNet4100
Station number: 1
12 feb 2012 14:12:06
Report Exceptions
Disabled points:
temporarily disabled points
Report Exceptions complete
>
Only, points that are disabled using the EX Edit Exceptions command are reported; points that are
disabled in the system configuration using the MI Modify Inputs command will not be reported.
See also:
EX Edit Exceptions
MI Modify Inputs
1.17.62 SC Save Configuration Changes

The SC Save Configuration Changes command allows the user to save any changes made to the
current configuration of the QNet4100.
To get to the SC Save Configuration Changes command, enter MC from the main menu, then enter SC
from the MC menu.
After the user types MC>SC<cr> at the MC Modify Configuration sub menu prompt, the system displays:
MC>SC<cr>
Save Configuration Changes
Saving configuration...
Save Configuration Changes complete
In the example above, the configuration is saved using the SC command. The configuration file contains all the
set up information associated with the QNet 4100 including: Station name, number, associated input devices
and their settings, as well as configuration information for Ports and Networks. After the SC command
completes, the user is returned to the MC prompt.

configuration.
103

1.17.63 SS Simulate Scanners

The SS Simulate Scanner command allows the scanner input points to simulated via a serial or network
connection.
>SS<cr>
QNet4100
Station number: 1
19 Feb 2012 15:08:46
Enable scanner simulation (Y,N)? [N] Y<cr>
Simulation over network (Y,N)? [N] Y<cr>
Rebooting after simulate change...
xxxxxxxxxxxxxxxxxxxxx
This command is only accessible through the maintenance port (Port0) at the controller module.
If 'No' is entered at the Simulation over network prompt the system will enter serial scanner simulation
mode. The simulation computer is connected via a RS232 serial to fiber optic module to the system chassis
backplane. Serial communications use 38400 baud, 8 data bits, no parity and 1 stop bit (38400 8-N-1).
If 'Yes' is entered at the Simulation over network prompt the system will enter serial scanner simulation
mode. The simulation computer is connected via an Ethernet connection to either of the controller module
Ethernet ports. The simulator computer must be in the same sub-domain as the controller module and
communications use a TCP connection at port 28000.
After the SS Scanner Simulation command mode is changed the system will automatically reboot.
To change back from Scanner Simulation to normal scanner operation, used the SS Scanner Simulation
command again and enter 'No' at the 'Enable scanner simulation' prompt.
See also:
Scanner Simulation protocol
1.17.64 SW Send Configuration to Annunciator

The SW Send Configuration to Annunciators command allows the user to send an annunciator
configuration to the annunciator modules. Note that an Annunciator Configuration port is required for
communcation to the annunciator modules. Therefore, this command will not be able to send the configuration
unless a functioning annunciator configuration port is present in the system. Please refer to the documentation
found in this manual for the MP Modify Ports command, if further assistance is required to configure an
Annunciator Configuration port.
104
To get to the SW command, enter MC from the main menu, then enter MW from the MC menu, then enter SW
from the MW menu.
After entering the SW command, the system sends the configuration to the annunciator modules through the
Annunciator configuration port. If the transmission is successful, the annunciator modules are updated with the
new configuration.
MW>SW<cr>
Send Configuration to Annunciators
Annunciator configuration port is not configured
Send Configuration to Annunciators complete
MW>
In the example above, the system cannot send the annunciator configuration because the Annunciator
configuration port is not configured.
After the configuration is sent to the annunciators, the user is returned to the MW sub menu prompt.

configuration.
1.17.65 TA Test Annunciators

The TA Test Annunciators command allows for a lamp test message to be sent to an annunciator output
module (AOM) or Betalarm 1500 annunciator via an 'annunciator configuration' port.
The TA Test Annunciator command has a toggle action; initially, sending a test message to an
annunciator will cause all associated alarm windows to turn ON, sending the message the second time will
return the windows to their previous state.
>TA<cr>
QNet4100
Station number: 1
14 Feb 2012 09:40:23
Test Annunciators
Annunciator (0..63)? 0<cr>
Annunciator (0..63)? 0<cr>
Annunciator (0..63)? <cr>
Test Annunciators complete
>
105
If an 'annunciator configuration' port is not defined, the system will respond with 'Annunciator
configuration port is not configured' message and will immediately exit the command.
1.17.66 TW Test Watchdog

The TW Test Watchdog command allows for simulation of a controller module failure to test the watchdog timer
circuitry on the QNet4100 backplane.
>TW<cr>
QNet4100
Station number: 1
12 Feb 2012 21:32:18
Test Watchdog
WARNING: This command will terminate SER operation in 29 to 59 seconds.
The watchdog timer contacts should close within 77 seconds
and the SER will need to be reset to resume normal operation.
Test Watchdog complete
>
WARNING:
The TW Test Watchdog command is intended to allow for testing of the primary to backup change over
mechanism in redundant systems and deliberately sets the controller modules 'Activate Process' in to a non-
responsive loop condition. The 'Activate Process' is responsible for start up and health monitoring of all other
processes including the scanner module and peripheral device communications process and is also
responsible for sending a periodic reset signal to the backplane watchdog circuit. While the 'Console' interface
will still respond to command alarm and event monitoring will cease after between 29 and 90 seconds and
approximately 17 seconds later the watchdog timer will time out.
In a QNet4100R redundant controller type system, the system will automatically switch to the backup
controller and, assuming the backup controller is healthy, it will take over scanner module and peripheral
device communications.
In an non redundant system the controller module itself can no longer warn of failed the condition and if the
watchdog circuit contact is not being monitored by an external system there may be no indication of this
failure condition.
It is essential that the system is reset after using the TW Test Watchdog command either by using
the 'XQ Reset QNet System' command, by using the controller module reset button or by cycling
the power to the system.
1.17.67 TS Test Scanners

The TS Test Scanners command will broadcast a functional test request (FT RQ) message to all scanner
modules.
If the scanner module can perform the test it will first simulate a 'closed' contact condition at all inputs and store
the new input state and then simulate an 'open' contact condition at all inputs and store the new input state.
The scanner module will then respond with a functional test report (FTREP) message:
- If an input failed either the 'closed' or 'open' test the the functional test report will show a an unhealthy
state (logical 1) for the input.
106
- If an input responded correctly to both the 'closed' and 'open' test the functional test the report will show a
healthy state (logical 0) for the input.
If the scanner module cannot perform the functional test because of a fault with its functional test circuitry it will
respond with a Functional Tester Fail (FTFAL) message.
If the controller module receives a functional test report with all inputs in a healthy state from all enabled
scanner modules it will simply respond to the TS Test scanner command with Test scanners
complete:
>TS<cr>
QNet4100
Station number: 1
12 Feb 2012 18:01:21
Test Scanners
Test Scanners complete
>
If the controller module receives a functional test report that contains an input in an unhealthy state it will report
report the failed input either with an FA (Failed Alarm) or FN (failed Normal) event, depending on the last
reported state of the input, it will also set a 'Functional Test Failure' diagnostic alarm for the associated
scanner:
>TS<cr>
QNet4100
Station number: 1
12 Feb 2012 18:04:33
Test Scanners
FN 18:04:33.002 195 PUMP A MOTOR BEARING TEMP. NORMAL
FA 18:04:33.002 251 SEAL OIL PRESSURE LOW
A 18:04:33:024 #D 172 Scanner 4 Functional Test Failure
A 18:04:33:024 #G 2 System Fault Alarm
>
An event with an FN status indicates that the point has failed functional test and is currently reported in the
Normal state.
An event with an FA status indicates that the point has failed functional test and is currently reported in the
Alarm state.
A separate diagnostic alarm is associated with 'Functional Test Failure' for each scanner.
If the controller module receives a functional tester fail message from a scanner it will set the 'Functional Tester
Tester' diagnostic alarm for that scanner and report the new event:
>TS<cr>
QNet4100
Station number: 1
12 Feb 2012 18:08:26
Test Scanners
A 18:08:27.003 #D 71 Scanner 3 Functional Tester Failure
A 18:08:27.003 #G 2 System Fault Alarm
>
107
A separate diagnostic alarm is associated with 'Functional Tester Failure' for each scanner.
A 'Functional Test Request' (FT RQ) message is automatically broadcast to the scanner every hour, on the
hour; if the test is successful and no failures are reported the no messages will be generated and the test is
unapparent to the user, however, if a failure is reported the diagnostic alarms and input failure messages will be
reported as they would if the TS Test Scanners command had been used.
If a scanner module reports a failed input the input will be added to the controller modules failed scanner point
list and will be reported by the RA Report Alarm Summary command. The point will remain on the failed
points list until the controller module next receives a functional test report (FTREP) with that input show in a
healthy state (logical 0).
The default configuration for the system also groups diagnostic alarms into a 'System Fault Alarm' and 'System
Failure Alarm', and these alarms are associated with the controller module front panel 'Fault' and 'Fail' LED's.
(See Output Grouping and the MG Modify Output Group Configuration command).
See also:
RA Report Alarm Summary
DM Diagnostic mode
MG Modify Output Group Configuration
Scanner communications
Output grouping
Diagnostic alarms
Troubleshooting
1.17.68 UL User Login

The commands available on the 'Main Menu' are dependent on the role of the current user and the access rights
assigned for that role via the access control list (ACL); some commands may be available to all users while
other commands may be privileged commands only available after a user login.
The UL User Login command allows for access to commands assigned for the specific users role. After a
user login all commands that are available to that user are listed on the Main Menu.
>UL<cr>
QNet4100
Station number: 1
8 Aug 2011 14:56:04 f
User Login
Enter user name: UserName<cr>
Enter password: *******<cr>
User Login complete
>
User password is displayed as a series of asterisks.
It should be noted that access rights are port specific; login at one communications port does not change the
access rights at another communications port.
CAUTION: The system does not automatically 'logout' a user; user should ensure that they use the UO User
Logout command as soon as they have completed a privileged command task.
108
See also:
UO User Logout
1.17.69 UO User Logout

The UO User Logout command exits a specific users role and returns the system to the 'legacy' (all users)
role.
>UO<cr>
User Logout complete
>
It should be noted that access rights are port specific; logout at one communications port does not change the
access rights at another communications port.
CAUTION:
The system does not automatically 'logout' a user; user should ensure that they use the UO User Logout
command as soon as they have completed a privileged command task.
See also:
UL User Login
1.17.70 UP Upload Configuration to QNet

The UP Upload Configuration to QNet command allows the user to upload a configuration file from
their PC to the QNet4100.
To get to the UP Upload Configuration to QNet command, enter MC from the main menu, then enter
UP from the MC menu.
After the user types MC>UP<cr> at the MC Modify Configuration sub menu prompt, the system will display this
message:
MC>UP<cr>
Upload Configuration to QNet
Start XMODEM transmitter
CCCCC
When this message is displayed, the system is waiting for the user to send a file to it by using the XMODEM
protocol. Hyperterminal is one program that is able to send the file
using XMODEM. After the file is sent to the system, the configuration is applied. The changes will not take
affect until the system is rebooted.
UP<cr>
109
Upload Configuration to QNet

Start XMODEM transmitter
CCCCCCInstalling new configuration
System must reboot after changes are saved to complete intallation.
Upload Configuration to QNet complete
MC>
In the example above, the configuration file has been uploaded and applied to the system. The user needs to
reboot the system for the changes to take affect.
In this case the user is not able to return to the main menu. When the user presses the Enter key they will see
the "Reboot to refresh system state (Y,N)?" prompt. Enter N If more changes are required to the
configuration. The user is still able to navigate the modify menus. When all necessary changes to the
configuration have been made, enter Y at the same prompt, and the system will be automatically rebooted.
After the system starts up, the uploaded configuration will be the current configuration.
1.17.71 XQ Reset QNet System

The XQ Reset QNet System command allows the user to reset the QNet4100 system.
To get to the XQ Reset QNet System command, enter MC from the main menu, then enter XQ from the MC
menu.
After the user types MC>XQ<cr> at the MC Modify Configuration sub menu prompt, the system will display this
message:
MC>XQ<cr>
Reset QNet System
Rebooting after reset command...
When this message is displayed, the system is rebooting. After the system starts up, the user begins again at
the main menu.
1.18 Modifications requiring a reboot

Command Reboot required
MQ Modify QNet ID No
MB Modify Base Point & Range No
MS Modify Scanner Yes
110
1.19 Frequently Asked Questions
This section is intended to provide guidance for configuration and use of the QNet4100 system.
If you need additional assistance please contact Qualitrol Customer Service Center:
Qualitrol Customer Service Center (North America)

1385 Fairport Road, Fairport, New York, 14450, USA
Phone: (+1) 585-586-1515
Fax: +(1) 585-377-0220
Email: info@qualitrolcorp.com
Qualitrol Customer Service Center (Belfast, UK)

15 Wildflower Way, Belfast, BT12 6TA, Northern Ireland
Phone: +44 28 9022 5200
Fax: +44 28 9022 5225
Email: info@qualitrolcorp.com
1.19.1 How do i recover a lost password?

A lost password cannot be recovered, however:
If the system level password is lost:

The system level password can be reset to the factory default password using the DP Default Password
command.
The DP Default Password command can only be accessed via the maintenance port (Port0) and must be
available to for legacy role.
Typing DP<cr> at the main menu prompt (>) will display the station name, station number, the current date and
time and the main menu prompt (>)again.
To reset the password type TENQ<cr>; the system will display the entered text as asterisks (****). After the
carriage return (<cr>) is entered the system will respond simply with the 'complete' message. If the text is
entered correctly the system level password will be restored to the factory default (QNET).
If a user password is lost:

A user with the security role must login to the system and delete the users account, using the DU Delete
User command, and reestablish that user, using the AU Add New User command.
The AU Add New User command will prompt for a password to be entered for the user.
If the password for the only user with security role privileges is lost, please contact Qualitrol Customer Service
Center.
1.19.2 How do I change a users role?

If a user role needs to be changed (for example from a 'Operator' role to an 'Engineer'):
A user with the 'Security' role must login to the system to and delete the users account, using the DU Delete
111
User command, and reestablish that user, using the AU Add New User command.
The AU Add New User command will prompt for a role to be entered for the user.
2 Web Interface
The Web Interface allows the user to interact with the QNet4100 through a Graphical User Interface.
The status of the system can be seen on the Summary display page, Event History can be seen on the History
display page, and Scanner input point exceptions can be seen on the Exceptions display page. With the
proper permissions, the user can also modify the system configuration by clicking the Config button.
To access the Web Interface, open a web browser such as Windows Internet Explorer and go to the IP address
of the controller, i.e. "http://12.34.56.78". A more generic representation of this URL would be "http://" (ip
address of the controller). The first page that is displayed is a login page. The user must enter valid credentials
to access the interface. Credentials are configured by a user with the security role. To gain access to the web
interface, a security user must grant permission for web access to a user. The security user can also grant
modify access to the user by assigning the user a role with modify rights such as the Engineer role.
If the user has web access permissions they will be able to login to the web interface by using their QNet4100
credentials. If the user has modify access, the Config button will be enabled.
To change users, first close the web browser then reopen it. The user will be prompted again to enter
credentials.
If the web page does not open, verify the network configuration by using the LC and LN commands. If the
network needs to be set up or modified use the MC and MN commands, followed by the EN and ER
commands. These commands allow the user to set up the network interface and default gateway. Please refer
to the local network administrator to verify the proper network settings for the controller module.
The screenshot below shows an example of the Web Interface after logging in. Specific elements of the
interface will be explained in the following sub topics.
To exit the Web Interface, close the browser as normal.
112
2.1 History display
The History display allows the user to see the QNet4100 event history.
After the user logs in, the history display page is the first page that is displayed to the user. Up to 100
thousand events are stored in the event history.
Refer to the screenshot shown for the Web Interface topic to see an example of a complete picture of the
History display. The exact contents of the display vary from system to system and changes based on system
configuration and the actual event history.
There are several elements to the History display, and they will be explained one by one in the rest of this topic.
The Heading - The heading consists of the following elements

Station name - Refer to the MQ command to modify the station name.
Operator - the current user
System time - this is the browser local time, and includes the system time quality indicator (in this
example "c").
The screenshot below is an example of the History display heading. Note that the heading remains the same
on all of the displays.
113
The Events - The events section consists of the following elements

The event type, A for Alarm and N for return to Normal.
The timestamp of the event - this includes the time quality indicator.
Input - the input point number i.e. S 0015 is scanner point 15, G 0001 is group point 1.
Legend - the legend text and background color for the event input point. The legend is defined by the
legend configuration. Refer to the ML command to modify legends.
The screenshot below is an example of the History display events table.
The Page selector - Selects a specific page of events if more than 1 is available. The page selector
contains the following elements.
The page number entry box - enter a number from 1 to the maximum number of pages displayed in this
box. After tabbing away from the box the display will be updated to the selected page.
Up and Down buttons - navigate through the pages using these buttons. The top button advances to the
next page while the bottom button moves to the previous page.
The screenshot below is an example of the History display page selector.
114
The Display selector - Selects one of the three available displays of the Web Interface. Click on the
Exceptions radio button to navigate to the Exceptions display page, or click on the Summary radio button to
navigate to the Summary display page.
The screenshot below is an example of the Display selector.
The Event Time Interval filter - Filters the history events displayed by the specified time interval.
This filter is always active. By default the time interval begins 24 hours before the Web Interface is first
opened, and ends at the current date and time.
Events displayed will be limited to the time interval specifed by the Start date and time and the End date
and time.
When there is no End date and time specified, the current date and time is implied.
The date and time may be entered into the boxes for the Start and End times.
Each date may be selected by clicking on the icon to the right of each date and time input box. The
time may also be entered at the bottom of the date selector dialog box.
The screenshot below is an example of the Event Time Interval filter.
The Inputs filter - Filters the history events by point input type.
This filter is always active. By Default the Scanner, Diagnostic, Group and External checkboxes are all
checked.
Events of the specified input type will be displayed when their input type checkbox is checked. Events of
that input type will not be displayed if the checkbox is not checked.
When the "Filter by points" checkbox is checked, the filter in the box below it will be applied. An input
list may be entered into that box to filter the events to see only the events of those specified input points.
An example of a filter for that box would be "S1". This will limit the displayed events to only scanner
115
point 1. More than one point can be in the filter, i.e "S1,S2". This will filter the events allowing only
events for scanner points 1 and 2 to be displayed in the event history display.
The screenshot below is an example of the Inputs filter
The Legend Color filter - Filters the history events by Legend Colors.
This filter is always active. By Default all of the checkboxes are checked.
Events of the specified legend color will be displayed when their legend color checkbox is checked.
Events of that legend color will not be displayed if the checkbox is not checked. Legend colors are
defined by the legend background color of an input point. There can be a background color associated
with an alarm event and a separate color for the input point's return to normal event. Legends can be
modified using the ML command
The screenshot below is an example of the Legend Color filter
The Action buttons - These three buttons are on all three displays.
The Apply button - This button will change it's color to orange when a change has been made to any of
the filters. The event history display will be updated to reflect the changes made to the filters after
clicking the Apply button. The Apply button will then return to it's normal color until the next change is
made to one of the filters. Clicking on this button will always refresh the current display.
The Export button - For the History display page, this button will export only the filtered events to a .csv
file. If there are multiple pages of events, the export will export all of the events on every page in one csv
file.
The Config button - This button will only be enabled if the logged in user has modify access rights.
Clicking this button will open the Java user interface system configuration application.
116
The screenshot below is an example of the Action buttons.
To exit the History display, either click on the radio button of a different display, such as the Exceptions display
or the Summary display, or close the browser as normal.
2.2 Exceptions display

The Exceptions display allows the user to see the Scanner input points that are currently temporarily disabled
in the QNet4100. These points have been temporarily disabled through the use of the EX command.
This display is similar to the report obtained using the RX command.
The screenshot below is an example of the Exceptions display. The exact contents of the display vary
depending on the system configuration and the actual points disabled.
A few notes regarding this display follow the screenshot.
The Heading - The heading is the same as on the History display.
117
The Exceptions - This section consists of the following elements

The input point type and number. These will always be Scanner points, and their number will follow the
S, for example. S 0002 for scanner input point 2.
The Alarm legend text for the scanner input point. The alarm legend text will be on the alarm legend
background color.
The state of the input point. This will always be DISABLED.
The screenshot below is an example of the scanner input points that are disabled.
The Display selector - The same as on the History display page.
The Legend Color filter - The same as on the History display page.
The Apply button - The same as on the History display page. Note that this button refreshes the display.
The Export button - This button will export the disabled scanner input points to a .txt file.
The Config button - The same as on the History display page.
To exit the Exceptions display, either click on the radio button of a different display, such as the Summary
display or the History display, or close the browser as normal.
2.3 Summary display

The Summary display allows the user to see a summary of all the points that are in the Alarm state, reported
by the QNet4100.
This display is similar to the report obtained using the RA command.
The screenshot below is an example of the Summary display. The exact contents of the display vary
depending on the system configuration and the actual points in alarm.
A few notes regarding this display follow the screenshot.
118
The Heading - The heading is the same as on the History display.
The Summary report - The report is timestamped as to when it was run. Refresh the information displayed
by clicking the Apply button.
.The category headings describe the points that are in alarm directly below each heading.
The input point type and number are displayed for each point that is in alarm.
The Alarm legend text for each point is displayed to the right of the input point number. The alarm legend
text will be on the alarm legend background color.
The Display selector - The same as on the History display page.
The Apply button - The same as on the History display page. Note that this button refreshes the display.
The Export button - This button will export the Summary report to a .txt file.
The Config button - The same as on the History display page.
To exit the Summary display, either click on the radio button of a different display, such as the Exceptions
display or the History display, or close the browser as normal.
3 Java User Interface Configuration editor

The Java User Interface Configuration editor allows the user to modify the system configuration of the QNet4100
through a Graphical User Interface. Continuing forward the Java User Interface Configuration editor will be
referred to as the JUI.
This editor can only be used by a user with modify access rights.
To access the JUI, first open the Web Interface. For further assistance with this step, please refer to the Web
Interface topic.
119
Once the Web Interface is open, follow these steps to open the JUI:
1. Click on the Config button. If this button is not enabled, the current logged in user does not have modify
access rights. Login to the Web Interface with a user that has the correct permissions.
2. The first time the Config button is clicked a security warning may be displayed. Follow the instructions to be
able to download the java file the next time the config button is clicked. In the case of Internet Explorer 8 the
user must select the "Download file" option from the popup security bar.
3. Click the Config button again if necessary.
4. After a few seconds a Java authentication dialog box appears. Enter your QNet4100 user credentials to
download the JUI application file. If the credentials are accepted, the file downloads and a splash screen is
displayed informing you that it is downloading the application file to your pc. The screenshot below shows
one example of the Java credentials prompt.
5. After downloading the application file, the JUI automatically starts running. The first operation it tries to do is
to download the configuration from the controller at the IP address that the Web Interface is pointing to. To
allow the configuration to be downloaded, the next thing the JUI wants to do is to prompt you for your
QNet4100 user credentials again. The username may already be populated. If that is the case, enter the
password. Otherwise enter both the username and the password then click the OK button.
Note - The user can cancel reading the current configuration from the QNet4100 by clicking the close
button (the x in the upper right corner of the credentials dialog box). This will allow the user to open an
existing configuration from the user's pc instead.
Also Note - If the user has the current version of the application, the program will not be downloaded again.
The screenshot below shows the credential prompt for this step.
120
6. After validating the submitted credentials the JUI wants to know where to save the configuration file locally to
your pc. The next dialog box is asking you where you would like to save the new configuration file that it will
download in the next step. The screenshot below shows the Save configuration dialog box that the user sees
in this step. If the configuration file exists, the user will be prompted to verify that they would like to overwrite
the existing configuration file.
7. After telling the JUI where to save the configuration file, it reads the configuration from the QNet4100 and
saves the file to the designated filename and location.
8. After successfully completing the previous step, the JUI reads the configuration file it just saved, and displays
it to the user.
The screenshot below shows an example of the JUI with a simple configuration loaded. Specific elements of
the interface will be explained in the following sub topics.
To exit the JUI, close the X button in the upper right corner of the interface.
121
3.1 System Configuration tab

The System Configuration tab allows the user to view and modify system settings.
To get to the System tab, click on the System tab button in the top row of buttons in the JUI. The System tab
is displayed first by default whenever the JUI is opened.
The screenshot below shows the System Configuration tab. The exact contents of the display vary from
system to system and changes based on system configuration.
There are several elements on the System Configuration tab, and they will be discussed further in the remainder
of this topic.
There is basic help available in the right panel of the interface, pertaining to the current tab. These are meant
to be reminders and hints. For further assistance for a particular section, refer to this instruction manual,
either among these JUI topics or the corresponding Console modify command topics.
Settings that involve numbers, such as the station number seen below, usually have "spinners" that will allow
the user to increase or decrease the value of the number in the box by one per click.
If an entered value is incorrect the value in error will turn red. If the value of a setting has changed and the
122
new value is acceptable, the value will turn green to indicate that setting has changed. This applies to every
tab in the JUI.
The Heading - The only note concerning the heading of the JUI are the version numbers seen at the top
right of the interface.
The JUI version number - this is the top version number, currently the version number is 1.0.1.
The firmware version of the configuration that is loaded in the JUI. This version number will change
depending on the firmware version of the configuration that is being modified.
QNet ID - Modify the station name and station number. Refer to the MQ command for further assistance.
123
Base Point & Range - Modify the first scanner point and the max scanner point. Refer to the MB command
for further assistance.
Enabled Scanners - Enable or disable scanner modules. Check a checkbox to enable the scanner. In the
screenshot below, scanner 1 is enabled and the rest are disabled. Refer to the MS command for further
assistance.
Miscellaneous Settings - Modify miscellaneous system settings. Checking a checkbox enables the
setting, this is similar to a Yes response in the MM command. Refer to the MM command for further
assistance.
124
Relay Configuration - Modify the relay configurations and set the common relay silence setting.
Unchecking the "Disable common relay silence" checkbox will enable the common relay silence setting. I f
this setting is enabled a Scanner point input field will appear. Enter the scanner input point to use as the
control for the common relay silence functionality. Refer to the MR command for further assistance.
The Action buttons - These four buttons are available all the time.
Upload - This button uploads the current configuration in the JUI to the QNet4100. There are a few steps
to this procedure:
1. Click the Upload button.
2. If the current configuration has not been saved it will ask to save the file first. Click the "Save File and
Upload" button in this case. If the file has been saved already, this step will be skipped.
3. Enter the IP address of the QNet4100 controller you would like to upload this configuration file to.
The user is able to dropdown the IP address list to choose from previous IP addresses or enter a
different one. The screenshot below is an example of this dialog box.
1. Click the OK button when ready to upload the configuration file to the indicated IP address, or click
the Cancel button to stop the upload operation.
2. After clicking the Ok button the user is prompted for credentials to access the QNet4100 at the IP
address that was entered in step 4. The prompt looks like the screenshot below. Enter credentials
and click the OK button to proceed.
125
1. At this point Diagnostic point 5 goes into alarm. This is the "System reconfigured" diagnostic point.
After a short time, 10 to 15 seconds, that point will return to normal and the system will automatically
reboot. This activity can be seen on a console session attached to port 0. When the system
finishes starting, the uploaded configuration will be active on that QNet4100.
Download - Downloads the configuration of a QNet4100 to a file on the user's pc. After downloading the
file and saving it, the configuration is read into the JUI for viewing and modification. There a few steps
involved in this process.
1. The user is prompted for the IP address of a QNet4100. This is the same dialog seen in step 3 of the
Upload procedure above.
2. After providing the IP address of the QNet4100 to download the configuration from, the user is asked
for credentials to access that system. This dialog is similar to the credential dialog in step 5 of the
Upload procedure above.
3. After the credentials are validated, the user is prompted for a filename and location for the new
downloaded configuration file. The user will be asked to verify overwriting an existing file.
4. The configuration is downloaded from the specified QNet4100, saved to the user's pc and loaded into
the JUI for viewing and modification.
Open - Opens a saved configuration file from the user's pc for viewing and modification.
Save - Saves the current configuration to a file on the user's pc. The application will ask the user where
to save the file and verify overwriting the file if it already exists.
The screenshot below is an example of the Action buttons.
To exit the System tab either click on another tab in the JUI or close the application by clicking on the X button
in the upper right corner of the JUI.
3.2 Time Configuration tab

The Time Configuration tab allows the user to view and modify precision time source settings and the local time
zone setting.
126
To get to the Time Configuration tab, click on the Time tab button in the top row of buttons in the JUI.
The screenshot below shows the Time Configuration tab. The exact contents of the display vary from system to
system and changes based on system configuration.
There are several elements on the Time Configuration tab, and they will be discussed further in the remainder of
this topic.
Settings that involve numbers, such as the Trained oscillator base value seen below, usually have "spinners"
that will allow the user to increase or decrease the value of the number in the box by one per click.
tab in the JUI.
The Heading - Exactly the same on all tabs. Refer to the System Configuration tab for details.
127
Time Sync - Modify the various time related settings. Refer to the MT command for further assistance.
Precision time source - Choose from all of the possible time sources. These are the same choices that
are available in the MT command.
When an IRIG-B time source is selected from the Precision time source dropdown, a local time
checkbox will appear to the right of that dropdown, enabling the user to choose local time for the IRIG
time source. Leaving the checkbox unchecked indicates the IRIG time source is UTC.
When a NMEA time source is selected from the Precision time source dropdown, a serial port control
will appear to the right of that dropdown, enabling the user to choose the serial port for the NMEA signal.
When the PPM or PPH time source is selected from the Precision time source dropdown, a scanner
point number input box will appear to the right of that dropdown, enabling the user to choose the scanner
point number input to accept the PPM or PPH synchronization signal.
Time zone - Modify the local Time zone. Refer to the MZ command for further assistance.
Drop down each list to choose a value.
The user must manually select a value from each dropdown, even if there is only 1 item in the list and
that item is the desired item.
After selecting a value from one of the dropdowns, the values will remain red until the user selects a value
from each dropdown. When all the values are green a valid time zone has been selected.
The Action buttons - Exactly the same on all tabs. Refer to the System Configuration tab for details.
To exit the Time tab either click on another tab in the JUI or close the application by clicking on the X button in
the upper right corner of the JUI.
3.3 Network Configuration tab

The Network Configuration tab allows the user to view and modify network settings of the QNet4100.
128
To get to the Network Configuration tab, click on the Network tab button in the top row of buttons in the JUI.
The screenshot below shows the Network Configuration tab. The exact contents of the display vary from
There are several elements on the Network Configuration tab, and they will be discussed further in the remainder
of this topic.
Settings that involve numbers, usually have "spinners" that will allow the user to increase or decrease the
value of the number in the box by one per click.
tab in the JUI.
Refer to the MN submenu commands for assistance with modifying the settings on this tab.
129
Interface - Modify the settings for either ethernet port interface. Refer to the EN command on the MN
submenu for further assistance.
DNS table - Modify the DNS table settings. Refer to the ES command on the MN submenu for further
assistance.
Right click anywhere inside the DNS table to access the popup menu. From this menu the user is able
to Add or Remove rows in the table.
Host table - Modify the Host table settings. Refer to the EH command on the MN submenu for further
assistance.
Right click anywhere inside the Host table to access the popup menu. From this menu the user is able
130
Routing table - Modify the Routing table settings. Refer to the ER command on the MN submenu for further
assistance.
Right click anywhere inside the Routing table to access the popup menu. From this menu the user is
able to Add or Remove rows in the table.
To exit the Network tab either click on another tab in the JUI or close the application by clicking on the X button
3.4 Port Configuration tab

The Port Configuration tab allows the user to view and modify Port configuration settings of the QNet4100.
To get to the Port Configuration tab, click on the Port tab button in the top row of buttons in the JUI.
The screenshot below shows the Port Configuration tab. The exact contents of the display vary from system to
system and changes based on system configuration.
There are several elements on the Port Configuration tab, and they will be discussed further in the remainder of
this topic.
131
tab in the JUI.
Refer to the MP submenu commands for assistance with modifying the settings on this tab.
Port table - Add or Delete Ports, or Modify the settings for existing Port configurations. Refer to the MP
command on the MP submenu for further assistance.
Right click anywhere inside the Port table to access the popup menu. From this menu the user is able
The input controls in the area to the right of the port table will vary depending on the protocol of the
selected Port configuration.
The port group time sorting is controlled in the port configurations. If a port group is designated as time
sorted by checking the Port group time sorted checkbox while on a particular port, any port in that port
group will also show the port group time sorted checkbox as checked.
132
Port settings - Modify more port settings for the current port configuration that is selected in the port table.
Again, refer to the MP command on the MP submenu for further assistance with any of these settings.
The input controls displayed in the left and right areas of the Port settings section will vary depending on
the protocol of the selected Port configuration.
To exit the Port tab either click on another tab in the JUI or close the application by clicking on the X button in
3.5 Scanner Configuration tab

The Scanner Configuration tab allows the user to view and modify the input, output and legend configurations of
Scanner points for the QNet4100.
133
To get to the Scanner Configuration tab, click on the Scanner tab button in the top row of buttons in the JUI.
The screenshot below shows the Scanner Configuration tab. The exact contents of the display vary from
There are several elements on the Scanner Configuration tab, and they will be discussed further in the
remainder of this topic.
tab in the JUI.
Refer to the MI, ML and MO commands for assistance with modifying the settings on this tab.
134
Scanner - Select a scanner from the list of enabled scanners. All settings on this page relate to the scanner
points based on the scanner chosen from this dropdown list.
Scanner points - Modify scanner input point settings. Refer to the MI command on the MC submenu for
further assistance with any of these settings.
Settings can be modified to a single point or a range of points. If the user wants to apply the settings of
a scanner point to a range of scanner points, follow these steps.
1. Select a point row to start with. Verify that this point has the desired settings that are to be applied
to a range of scanner points.
2. Right click on that desired row.
3. Select the only option in the popup menu, "Apply Data to Multiple Rows"
1. Enter a range in the "Apply to:" input box that describes the range of scanner points the chosen
settings are to be applied to. The range is entered starting point - ending point, i.e 1-1000 to apply
the changes to scanner points from 1 to 1000.
2. Check any of the checkboxes in the Apply to multiple points dialog box that represent the settings to
be applied to the range of points indicated in step 4.
3. Click the Ok button and the settings are applied to all of the points in that range.
Note that the amount of time it takes to apply the changes to the range of points depends on how
many settings and how many points are being changed.
135
Point legend - Modify legend text and legend background colors for the selected scanner point. Refer to the
ML command on the MC submenu for further assistance with any of these settings.
Port groups - Modify the output assignments of the selected scanner point. Refer to the MO command on
the MC submenu for further assistance with any of these settings.
Assign the selected scanner point to any of the 32 port groups, and define the type of output desired,
Alarm, Normal, Both or None.
136
To exit the Scanner tab either click on another tab in the JUI or close the application by clicking on the X button
3.6 Diagnostic Configuration tab

The Diagnostic Configuration tab allows the user to view and modify the input, output and legend configurations
of Diagnostic points for the QNet4100.
To get to the Diagnostic Configuration tab, click on the Diagnostic tab button in the top row of buttons in the
JUI.
The screenshot below shows the Diagnostic Configuration tab. The exact contents of the display vary from
There are several elements on the Diagnostic Configuration tab, and they will be discussed further in the
tab in the JUI.
Refer to the MI, ML and MO commands for assistance with modifying the settings on this tab.
137
Select Diagnostic points - Select a page of Diagnostic points from the list of available pages. There are 4
pages available with 64 diagnostic points on each page. All settings on this tab relate to the Diagnostic
points based on the page selected from this dropdown list.
Diagnostic points - Modify Diagnostic input point settings. Refer to the MI command on the MC submenu
for further assistance with any of these settings.
a Diagnostic point to a range of Diagnostic points, follow these steps.
to a range of Diagnostic points.
138
1. Enter a range in the "Apply to:" input box that describes the range of Diagnostic points the chosen
settings are to be applied to. The range is entered starting point - ending point, i.e 5-15 to apply the
changes to Diagnostic points from 5 to 15.
139
Point legend - Modify legend text and legend background colors for the selected Diagnostic point. Refer to
the ML command on the MC submenu for further assistance with any of these settings.
Port groups - Modify the output assignments of the selected Diagnostic point. Refer to the MO command on
the MC submenu for further assistance with any of these settings.
Assign the selected Diagnostic point to any of the 32 port groups, and define the type of output desired,
To exit the Diagnostic tab either click on another tab in the JUI or close the application by clicking on the X
button in the upper right corner of the JUI.
3.7 Group Configuration tab

The Group Configuration tab allows the user to view and modify the input, output and legend configurations of
Group points for the QNet4100.
To get to the Group Configuration tab, click on the Group tab button in the top row of buttons in the JUI.
The screenshot below shows the Group Configuration tab. The exact contents of the display vary from system
to system and changes based on system configuration.
There are several elements on the Group Configuration tab, and they will be discussed further in the remainder
of this topic.
140
tab in the JUI.
Refer to the MI, MG, ML and MO commands for assistance with modifying the settings on this tab.
Select Group points - Select a page of Group points from the list of available pages. There are 16 pages
available with 64 Group points on each page. All settings on this tab relate to the Group points based on the
page selected from this dropdown list.
141
Group points - Modify Group input point settings. Refer to the MI command on the MC submenu for further
assistance with any of these settings.
a Group point to a range of Group points, follow these steps.
to a range of Group points.
1. Enter a range in the "Apply to:" input box that describes the range of Group points the chosen
settings are to be applied to. The range is entered starting point - ending point, i.e 5-15 to apply the
changes to Group points from 5 to 15.
142
Group Point definition - Modify the group point definition of the selected Group point. Refer to the MG
command on the MC submenu for further assistance with any of these settings.
Input controls will appear below the Filter delay type dropdown depending on what is selected from that
list.
143
Point legend - Modify legend text and legend background colors for the selected Group point. Refer to the
ML command on the MC submenu for further assistance with any of these settings.
Port groups - Modify the output assignments of the selected Group point. Refer to the MO command on the
MC submenu for further assistance with any of these settings.
Assign the selected Group point to any of the 32 port groups, and define the type of output desired,
To exit the Group tab either click on another tab in the JUI or close the application by clicking on the X button in
3.8 Annunciator Configuration tab

The Annunciator Configuration tab allows the user to view and modify Annunciator pair and Annunciator Window
configurations.
To get to the Annunciator Configuration tab, click on the Annunciator tab button in the top row of buttons in the
JUI.
The screenshot below shows the Annunciator Configuration tab. The exact contents of the display vary from
There are several elements on the Annunciator Configuration tab, and they will be discussed further in the
144
tab in the JUI.
Refer to the MA and MW commands for assistance with modifying the settings on this tab.
Annunciator - Select an Annunciator pair from the list of 32 annunciator pairs. There are 32 annunciator
pairs available with 64 Annunciator Windows for each annunciator pair. All settings on this tab relate to the
Annunciator pair selected from this dropdown list.
145
Annunciator settings - Modify the Annunciator pair only settings in this area. Refer to the MA command on
the MW submenu for further assistance with any of these settings.
Note - Settings of one annunciator pair may be applied to a range of annunciator pairs. Refer to the
Annunciator Windows section below for details.
Windows - Modify Annunciator Window settings. Refer to the MW command on the MC submenu for further
assistance with any of these settings.
Annunciator pair and / or annunciator window settings can be modified for a single pair or window or a
range of pairs and windows. If the user wants to apply the settings of a single Annunciator pair or a
single Annunciator Window to multiple pairs or windows, follow these steps.
1. Select an Annunciator window row to start with. (The source annunciator pair is implied) Verify that
this window (and pair) has the desired settings that are to be applied to a range of Annunciator pairs
and windows.
146
1. Enter a range in the "Apply to Annunciators:" input box and the "Apply to Windows" input box that
describes the range of pairs and windows the chosen settings are to be applied to. The range is
entered starting point - ending point, i.e 5-10 to apply the changes to Annunciator windows from 5 to
10. In the example above, the annunciator pair changes from the source annunciator 0-1, will be
applied to the destination annunciator 2-3. If a range of 1-32 is entered into the Apply to annunciators
input box, the changes will be applied to all of the annuciator pairs from 1 to 32 (16 pairs).
2. Check any of the checkboxes in the Apply to annunciators and windows dialog box that represent the
settings to be applied to the range of pairs and windows indicated in step 4.
3. Click the Ok button and the settings are applied to all of the pairs and windows in that defined
ranges.
Note that the amount of time it takes to apply the changes to the range of pairs and windows
depends on how many settings and how many pairs and windows are being changed.
To exit the Annunciator tab either click on another tab in the JUI or close the application by clicking on the X
button in the upper right corner of the JUI.
4 Appendix A - Timezones
4.1 Region
Time Zone Regions
147
Time Zone Regions

Indian Pacific
4.2 Country (by Region)

Time Zone Countries (by Region)
Africa
Algeria Angola Benin Botswana
BurkinaFaso Burundi Cameroon CentralAfricanRep
Chad Congo_Dem.Rep. Congo_Rep. Coted'Ivoire
Djibouti Egypt EquatorialGuinea Eritrea
Ethiopia Gabon Gambia Ghana
Guinea Guinea-Bissau Kenya Lesotho
Liberia Libya Malawi Mali
Mauritania Morocco Mozambique Namibia
Niger Nigeria Rwanda SaoTome_Principe
Senegal SierraLeone Somalia SouthAfrica
Spain Sudan Swaziland Tanzania
Togo Tunisia Uganda WesternSahara
Zambia Zimbabwe
America
Anguilla Antigua_Barbuda Argentina Aruba
Bahamas Barbados Belize Bolivia
Brazil Canada CaymanIslands Chile
Colombia CostaRica Cuba Dominica
DominicanRepublic Ecuador ElSalvador FrenchGuiana
Greenland Grenada Guadeloupe Guatemala
Guyana Haiti Honduras Jamaica
Martinique Mexico Montserrat NetherlandsAntilles
Nicaragua Panama Paraguay Peru
PuertoRico StBarthelemy StKitts&Nevis StLucia
StMartin(Frenchpart) StPierre_Miquelon StVincent Suriname
Trinidad&Tobago Turks&CaicosIs UnitedStates Uruguay
Venezuela VirginIslands_UK VirginIslands_US
Antarctica
Antarctica
Arctic
Svalbard_JanMayen
Asia
Afghanistan Armenia Azerbaijan Bahrain
Bangladesh Bhutan Brunei Cambodia
China Cyprus EastTimor Georgia
HongKong India Indonesia Iran
Iraq Israel Japan Jordan
148
Time Zone Countries (by Region)
Kazakhstan Korea_North Korea_South Kuwait
Kyrgyzstan Laos Lebanon Macau
Malaysia Mongolia Myanmar_Burma Nepal
Oman Pakistan Palestine Philippines
Qatar Russia SaudiArabia Singapore
SriLanka Syria Taiwan Tajikistan
Thailand Turkmenistan UnitedArabEmirates Uzbekistan
Vietnam Yemen
Atlantic
Bermuda CapeVerde FalklandIslands FaroeIslands
Iceland Portugal SouthGeorgia_theSout Spain
StHelena
Australia
Australia
Europe
AalandIslands Albania Andorra Austria
Belarus Belgium Bosnia_Herzegovina Britain_UK
Bulgaria Croatia CzechRepublic Denmark
Estonia Finland France Germany
Gibraltar Greece Guernsey Hungary
Ireland IsleofMan Italy Jersey
Latvia Liechtenstein Lithuania Luxembourg
Macedonia Malta Moldova Monaco
Montenegro Netherlands Norway Poland
Portugal Romania Russia SanMarino
Serbia Slovakia Slovenia Spain
Sweden Switzerland Turkey Ukraine
VaticanCity
Indian
BritishIndianOceanTe ChristmasIsland Cocos_KeelingIslands Comoros
FrenchSouthern_Antar Madagascar Maldives Mauritius
Mayotte Reunion Seychelles
Pacific
Chile CookIslands Ecuador Fiji
FrenchPolynesia Guam Kiribati MarshallIslands
Micronesia Nauru NewCaledonia NewZealand
Niue NorfolkIsland NorthernMarianaIslan Palau
PapuaNewGuinea Pitcairn Samoa_American Samoa_western
SolomonIslands Tokelau Tonga Tuvalu
UnitedStates Usminoroutlyingislan Vanuatu Wallis_Futuna
149
4.3 Time zone (by Country and Region)

Time Zones [alphabetical by Country]
AalandIslands (Europe)
Mariehamn
Afghanistan (Asia)
Kabul
Albania (Europe)
Tirane
Algeria (Africa)
Algiers
Andorra (Europe)
Andorra
Angola (Africa)
Luanda
Anguilla (America)
Anguilla
Antarctica (Antarctica)
Casey Davis DumontDUrville Macquarie
Mawson McMurdo Palmer Rothera
South_Pole Syowa Vostok
Antigua_Barbuda (America)
Antigua
Argentina (America)
Buenos_Aires Catamarca Cordoba Jujuy
La_Rioja Mendoza Rio_Gallegos Salta
San_Juan San_Luis Tucuman Ushuaia
Armenia (Asia)
Yerevan
Aruba (America)
Aruba
Australia (Australia)
Adelaide Brisbane Broken_Hill Currie
Darwin Eucla Hobart Lindeman
Lord_Howe Melbourne Perth Sydney
Austria (Europe)
Vienna
Azerbaijan (Asia)
Baku
Bahamas (America)
Nassau
Bahrain (Asia)
Bahrain
Bangladesh (Asia)
150
Dhaka
Barbados (America)
Barbados
Belarus (Europe)
Minsk
Belgium (Europe)
Brussels
Belize (America)
Belize
Benin (Africa)
Porto-Novo
Bermuda (Atlantic)
Bermuda
Bhutan (Asia)
Thimphu
Bolivia (America)
La_Paz
Bosnia_Herzegovina (Europe)
Sarajevo
Botswana (Africa)
Gaborone
Brazil (America)
Araguaina Bahia Belem Boa_Vista
Campo_Grande Cuiaba Eirunepe Fortaleza
Maceio Manaus Noronha Porto_Velho
Recife Rio_Branco Santarem Sao_Paulo
Britain_UK (Europe)
London
BritishIndianOceanTerritory (Indian)
Chagos
Brunei (Asia)
Brunei
Bulgaria (Europe)
Sofia
BurkinaFaso (Africa)
Ouagadougou
Burundi (Africa)
Bujumbura
Cambodia (Asia)
Phnom_Penh
Cameroon (Africa)
Douala
Canada (America)
151

Atikokan Blanc-Sablon Cambridge_Bay Dawson
Dawson_Creek Edmonton Glace_Bay Goose_Bay
Halifax Inuvik Iqaluit Moncton
Montreal Nipigon Pangnirtung Rainy_River
Rankin_Inlet Regina Resolute CanSt_Johns
Swift_Current Thunder_Bay Toronto Vancouver
Whitehorse Winnipeg Yellowknife
CapeVerde (Atlantic)
Cape_Verde
CaymanIslands (America)
Cayman
CentralAfricanRep. (Africa)
Bangui
Chad (Africa)
Ndjamena
Chile (America)
Santiago
Chile (Pacific)
Easter
China (Asia)
Chongqing Harbin Kashgar Shanghai
Urumqi
ChristmasIsland (Indian)
Christmas
Cocos_KeelingIslands (Indian)
Cocos
Colombia (America)
Bogota
Comoros (Indian)
Comoro
Congo_Dem.Rep. (Africa)
Kinshasa Lubumbashi
Congo_Rep. (Africa)
Brazzaville
CookIslands (Pacific)
Rarotonga
CostaRica (America)
Costa_Rica
Coted'Ivoire (Africa)
Abidjan
Croatia (Europe)
Zagreb
Cuba (America)
152
Havana
Cyprus (Asia)
Nicosia
CzechRepublic (Europe)
Prague
Denmark (Europe)
Copenhagen
Djibouti (Africa)
Djibouti
Dominica (America)
Dominica
DominicanRepublic (America)
Santo_Domingo
EastTimor (Asia)
Dili
Ecuador (America)
Guayaquil
Ecuador (Pacific)
Galapagos
Egypt (Africa)
Cairo
ElSalvador (America)
El_Salvador
EquatorialGuinea (Africa)
Malabo
Eritrea (Africa)
Asmara
Estonia (Europe)
Tallinn
Ethiopia (Africa)
Addis_Ababa
FalklandIslands (Atlantic)
Stanley
FaroeIslands (Atlantic)
Faroe
Fiji (Pacific)
Fiji
Finland (Europe)
Helsinki
France (Europe)
Paris
FrenchGuiana (America)
Cayenne
153

FrenchPolynesia (Pacific)
Gambier Marquesas Tahiti
FrenchSouthern_AntarcticLands (Indian)
Kerguelen
Gabon (Africa)
Libreville
Gambia (Africa)
Banjul
Georgia (Asia)
Tbilisi
Germany (Europe)
Berlin
Ghana (Africa)
Accra
Gibraltar (Europe)
Gibraltar
Greece (Europe)
Athens
Greenland (America)
Danmarkshavn Godthab Scoresbysund Thule
Grenada (America)
Grenada
Guadeloupe (America)
Guadeloupe
Guam (Pacific)
Guam
Guatemala (America)
Guatemala
Guernsey (Europe)
Guernsey
Guinea (Africa)
Conakry
Guinea-Bissau (Africa)
Bissau
Guyana (America)
Guyana
Haiti (America)
Port-au-Prince
Honduras (America)
Tegucigalpa
HongKong (Asia)
Hong_Kong
Hungary (Europe)
154
Budapest
Iceland (Atlantic)
Reykjavik
India (Asia)
Kolkata
Indonesia (Asia)
Jakarta Jayapura Makassar Pontianak
Iran (Asia)
Tehran
Iraq (Asia)
Baghdad
Ireland (Europe)
Dublin
IsleofMan (Europe)
Isle_of_Man
Israel (Asia)
Jerusalem
Italy (Europe)
Rome
Jamaica (America)
Jamaica
Japan (Asia)
Tokyo
Jersey (Europe)
Jersey
Jordan (Asia)
Amman
Kazakhstan (Asia)
Almaty Aqtau Aqtobe Oral
Qyzylorda
Kenya (Africa)
Nairobi
Kiribati (Pacific)
Enderbury Kiritimati Tarawa
Korea(North) (Asia)
Pyongyang
Korea(South) (Asia)
Seoul
Kuwait (Asia)
Kuwait
Kyrgyzstan (Asia)
Bishkek
Laos (Asia)
155

Vientiane
Latvia (Europe)
Riga
Lebanon (Asia)
Beirut
Lesotho (Africa)
Maseru
Liberia (Africa)
Monrovia
Libya (Africa)
Tripoli
Liechtenstein (Europe)
Vaduz
Lithuania (Europe)
Vilnius
Luxembourg (Europe)
Luxembourg
Macau (Asia)
Macau
Macedonia (Europe)
Skopje
Madagascar (Indian)
Antananarivo
Malawi (Africa)
Blantyre
Malaysia (Asia)
Kuala_Lumpur Kuching
Maldives (Indian)
Maldives
Mali (Africa)
Bamako
Malta (Europe)
Malta
MarshallIslands (Pacific)
Kwajalein Majuro
Martinique (America)
Martinique
Mauritania (Africa)
Nouakchott
Mauritius (Indian)
Mauritius
Mayotte (Indian)
Mayotte
156
Mexico (America)
Bahia_Banderas Cancun Chihuahua Hermosillo
Matamoros Mazatlan Merida Mexico_City
Monterrey Ojinaga Santa_Isabel Tijuana
Micronesia (Pacific)
Chuuk Kosrae Pohnpei
Moldova (Europe)
Chisinau
Monaco (Europe)
Monaco
Mongolia (Asia)
Choibalsan Hovd Ulaanbaatar
Montenegro (Europe)
Podgorica
Montserrat (America)
Montserrat
Morocco (Africa)
Casablanca
Mozambique (Africa)
Maputo
Myanmar(Burma) (Asia)
Rangoon
Namibia (Africa)
Windhoek
Nauru (Pacific)
Nauru
Nepal (Asia)
Kathmandu
Netherlands (Europe)
Amsterdam
NetherlandsAntilles (America)
Curacao
NewCaledonia (Pacific)
Noumea
NewZealand (Pacific)
Auckland Chatham
Nicaragua (America)
Managua
Niger (Africa)
Niamey
Nigeria (Africa)
Lagos
Niue (Pacific)
157

Niue
NorfolkIsland (Pacific)
Norfolk
NorthernMarianaIslands (Pacific)
Saipan
Norway (Europe)
Oslo
Oman (Asia)
Muscat
Pakistan (Asia)
Karachi
Palau (Pacific)
Palau
Palestine (Asia)
Gaza
Panama (America)
Panama
PapuaNewGuinea (Pacific)
Port_Moresby
Paraguay (America)
Asuncion
Peru (America)
Lima
Philippines (Asia)
Manila
Pitcairn (Pacific)
Pitcairn
Poland (Europe)
Warsaw
Portugal (Atlantic)
Azores Madeira
Portugal (Europe)
Lisbon
PuertoRico (America)
Puerto_Rico
Qatar (Asia)
Qatar
Reunion (Indian)
Reunion
Romania (Europe)
Bucharest
Russia (Asia)
Anadyr Irkutsk Kamchatka Krasnoyarsk
158
Magadan Novokuznetsk Novosibirsk Omsk
Sakhalin Vladivostok Yakutsk Yekaterinburg
Russia (Europe)
Kaliningrad Moscow Samara Volgograd
Rwanda (Africa)
Kigali
Samoa_American (Pacific)
Pago_Pago
Samoa_western (Pacific)
Apia
SanMarino (Europe)
San_Marino
SaoTome_Principe (Africa)
Sao_Tome
SaudiArabia (Asia)
Riyadh
Senegal (Africa)
Dakar
Serbia (Europe)
Belgrade
Seychelles (Indian)
Mahe
SierraLeone (Africa)
Freetown
Singapore (Asia)
Singapore
Slovakia (Europe)
Bratislava
Slovenia (Europe)
Ljubljana
SolomonIslands (Pacific)
Guadalcanal
Somalia (Africa)
Mogadishu
SouthAfrica (Africa)
Johannesburg
SouthGeorgia_theSouthSandwichIslands (Atlantic)
South_Georgia
Spain (Africa)
Ceuta
Spain (Atlantic)
Canary
Spain (Europe)
159

Madrid
SriLanka (Asia)
Colombo
StBarthelemy (America)
St_Barthelemy
StHelena (Atlantic)
St_Helena
StKitts_Nevis (America)
St_Kitts
StLucia (America)
St_Lucia
StMartin(Frenchpart) (America)
Marigot
StPierre_Miquelon (America)
Miquelon
StVincent (America)
St_Vincent
Sudan (Africa)
Khartoum
Suriname (America)
Paramaribo
Svalbard_JanMayen (Arctic)
Longyearbyen
Swaziland (Africa)
Mbabane
Sweden (Europe)
Stockholm
Switzerland (Europe)
Zurich
Syria (Asia)
Damascus
Taiwan (Asia)
Taipei
Tajikistan (Asia)
Dushanbe
Tanzania (Africa)
Dar_es_Salaam
Thailand (Asia)
Bangkok
Togo (Africa)
Lome
Tokelau (Pacific)
Fakaofo
160
Tonga (Pacific)
Tongatapu
Trinidad_Tobago (America)
Port_of_Spain
Tunisia (Africa)
Tunis
Turkey (Europe)
Istanbul
Turkmenistan (Asia)
Ashgabat
Turks_CaicosIs (America)
Grand_Turk
Tuvalu (Pacific)
Funafuti
Uganda (Africa)
Kampala
Ukraine (Europe)
Kiev Simferopol Uzhgorod Zaporozhye
UnitedArabEmirates (Asia)
Dubai
UnitedStates (America)
Adak Anchorage Beulah Boise
Center Chicago Denver Detroit
Indianapolis Juneau Knox Los_Angeles
Louisville Marengo UniMenominee Metlakatla
Monticello UnitedSNew_Salem New_York Nome
Petersburg Phoenix Shiprock Sitka
Tell_City Vevay Vincennes Winamac
Yakutat
UnitedStates (Pacific)
Honolulu
Uruguay (America)
Montevideo
USminoroutlyingislands (Pacific)
Johnston Midway Wake
Uzbekistan (Asia)
Samarkand Tashkent
Vanuatu (Pacific)
Efate
VaticanCity (Europe)
Vatican
Venezuela (America)
Caracas
161

Vietnam (Asia)
Ho_Chi_Minh
VirginIslands_UK (America)
Tortola
VirginIslands_US (America)
St_Thomas
Wallis&Futuna (Pacific)
Wallis
WesternSahara (Africa)
El_Aaiun
Yemen (Asia)
Aden
Zambia (Africa)
Lusaka
Zimbabwe (Africa)
Harare
5 Coordinated Universal Time

Coordinated Universal Time (UTC) is a time standard based on International Atomic Time (TAI) with
leap seconds added at irregular intervals to compensate for the Earth's slowing rotation. Leap
seconds are used to allow UTC to closely track UT1, which is mean solar time at the Royal
Observatory, Greenwich also known as Greenwich Mean Time (GMT).
Time zones around the world can be expressed as positive or negative offsets from UTC; UTC
replaced GMT as the basis for the main reference time scale or civil time in various regions on 1
January 1972.
6 Glossary
LAN - Local Area Network.
WAN - Wide Area Network.
PC - Personal Computer
7 Copyright
All rights reserved. This publication may not be reproduced, stored in a retrieval system, or
transmitted in whole or part, in any form or by any means, electronic, mechanical, audio,
photocopying, recording, or otherwise, without the prior written permission of Qualitrol Company
LLC.
While this information is presented in good faith and believed to be accurate, Qualitrol does not
162
guarantee satisfactory results from reliance upon such information. Qualitrol reserves the right,
without notice, to alter or improve the designs or specifications of the products described herein.
Nothing herein is to be construed as a warranty or guarantee, expressed or implied, regarding the
performance, merchantability, fitness, or any other matter with respect to the products, nor as a
recommendation to use any product or process in conflict with any patent.
163
NTP 19
Index -O-
-A- Output Group 46
Annunciators 95
-P-
-C- Port 0 4
Port Group 75
Configuration 35 PPH 19, 91
Console interface 4 PPM 19, 91
Continuous Alarm 86 PPS 19, 91
Continuous Normal 86 Pulse Alarm 86
Pulse Both 86
Pulse Normal 86
-D- Pulse per, hour 19
Pulse per, minute 19
DHCP 75
Pulse per, second 19
DNS 75
-H- -Q-
QNet 109
Home Relay 86
-I- -R-
Reflash 86
indention 53
Ringback 86
IRIG 19
RS232 4
IRIG-G 91
-L- -S-
Station, Name 19
legend 49
Station, Number 19
legend data 49
System Password 9
-M- -T-
Maintenance port 4
Time Sync Configuration 91
-N- -U-
Network Time Protocol 19
Universal Serial Bus (USB) 4
NMEA 19
USB 4
NMEA Modify Time Sync Configuration 91
40-08646-00Rev000

40-08646-00rev000 QNet4100 User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

40-08646-00rev000 QNet4100 User Manual

Uploaded by

Copyright:

Available Formats

User Manual

1 QNet4100 Console Interface

1.17.24 LG List Output Group Configuration 46

3 Java User Interface Configuration editor

5 Coordinated Universal Time

1 QNet4100 Console Interface

1.1 Maintenance Port

Maintenance Port (Port 0) RS232 Serial Connections

Port 1 through Port 5 RS232 Serial Connections

1.2 Port Groups

Macro Input/Output Function

1.3 Access Control List (ACL)

There are 5 predefined roles and 2 undefined roles:

Console Commands Security Legacy Password Engineer Operator Monitor

RA Report Alarm Summary Disabled Enabled Disabled Enabled Enabled Enabled

1.4 Main Menu

Default all users (legacy role):

? Context Help UL User Login

? Context Help UO User Logout

System level password protected:

1.5 Sub Menus

Modify Configuration sub menu:

MQ Modify QNet ID LQ List QNet Configuration

Modify Ports sub menu:

Modify Network sub menu:

Modify Annunciators sub menu:

List Configuration sub menu:

Command Prompt Menu

1.7 Terse Command Entry

The following terse command line produces the same result:

Terse entry can also be used within commands. For example:

Here the user enabled scanners 2 and 5 and disabled scanner 8.

The following would have the same result;

The same command could be entered as a single line terse command;

1.8 Event Printout

'Status' is either one or two characters:

The following is an example of a typical event printout:

A 16:14:52.625 S# 98 CONDENSER LEVEL HIGH

1.9 Input Point Type (S,D,X,G)

Alarm and event points can one of four types:

Point Type Description

1.10 Scope of Inputs (M, R, S)

Multipoint, Range or single (M, R, S)?

Same data (Y,N) [N]? Y<cr>

The header is format as follows:

1.12 Time Synchronization

IRIG-B Time code:

PPS (pulse per second):

PPM (pulse per minute) or PPH (pulse per hour)

NTP Network Time Protocol

1.13 Trained Oscillator

1.14 Time Quality

Character System Time Uncertainty

Command Configuration Other Commands affected

A suggested sequence of configuring the equipment is as follows:

Step Modify Configuration commands

Step Modify Configuration commands

1.16 XMODEM File Transfer

The QNet4100 configuration is split into 5 down-loadable files:

The System configuration (System)

1.17 Console Commands (English)

1.17.1 ? Context Help

Region? [America] ?<cr>