Page 1
Admin Console
User’ s Guide
Model No.
WJ-MPU955
please read these instructions carefully and save this manual for future use.
Before attempting to connect or operate this product,
Page 2
WJ-MPU955
Admin Console
Installation and Configuration
For System Administrators and Operators
Page 3
The contents of this document are subject to change without notice and do not constitute
a commitment on the part of Matsushita Electric Industrial Co., Ltd. Every effort has
been made to ensure the accuracy of this document. However, due to ongoing product
improvements and revisions, Matsushita Electric Industrial Co., Ltd. cannot guarantee the
accuracy of printed material after the date of publication, nor can it accept responsibility
for errors or omissions. Matsushita Electric Industrial Co., Ltd. will update and revise
this document as needed.
The software and hardware described in this document may be copied or used only in
accordance with the terms of the license pertaining to said software or hardware.
Reproduction, publication, or duplication of this manual, or any part thereof (with an
exception - listed below), in any manner, mechanically, electronically, or
photographically, is prohibited without permission of the Matsushita Electric Industrial
Co., Ltd.
Permission is given to reproduce or duplicate the entire “Worksheets” section at the end
of this manual as needed, and the “Definition” topics within the “Configuration” section.
©2001 - 2003 by Matsushita Electric Industrial Co., Ltd.
All rights reserved.
Trademarks
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United
States and other countries.
Intel and Pentium is a registered trademark of Intel Corporation in the United States and
other countries.
Other products and company names mentioned herein may be the trademarks of their
respective owners.
Page 4
Table of Contents
Welcome...............................................................................................................1
Introduction...........................................................................................................3
Control of the System........................................................................................3
How It Works.....................................................................................................4
Configuration Management ...........................................................................4
User Control...................................................................................................4
What Happens Next..........................................................................................4
Installation.............................................................................................................5
System Requirements....................................................................................... 5
Minimum Hardware Requirements ................................................................5
Minimum Video Display Setting Requirements..............................................5
Operating System Requirements................................................................... 5
Installing MPU955 Admin Console....................................................................6
What Happens Next..........................................................................................6
Configuration ........................................................................................................7
Worksheet Tasks...............................................................................................7
Instructions........................................................................................................8
Checklist............................................................................................................8
Starting the Program.........................................................................................9
Logging In .........................................................................................................9
First Time Operation........................................................................................10
CPU Setup...................................................................................................10
Scheduled Modes........................................................................................13
Main Window...................................................................................................15
Database Management...................................................................................16
At Installation...............................................................................................16
Database Archive ........................................................................................16
Creating a Database....................................................................................17
Selecting a Database...................................................................................18
Renaming a Database.................................................................................20
Deleting a Database....................................................................................21
Backing up or Restoring a Database...........................................................22
System Configuration ..................................................................................28
Input to Screen................................................................................................36
Switch Nodes...............................................................................................37
Components ................................................................................................40
Alarms .........................................................................................................41
Cameras......................................................................................................53
System Controllers ......................................................................................62
Alarm Input/Output.......................................................................................66
Monitors.......................................................................................................69
Operators.....................................................................................................73
Automate.........................................................................................................79
Tour Sequences ..........................................................................................80
Group Presets (not currently supported)......................................................86
Group Sequences (not currently supported)................................................92
i
Page 5
Table of Contents
Event Scheduler ..........................................................................................98
Tools ............................................................................................................. 101
Log Manager..............................................................................................102
AC Log.......................................................................................................107
Areas.........................................................................................................109
Account Manager.......................................................................................110
Help ...........................................................................................................113
Uninstalling .......................................................................................................113
Appendix A .......................................................................................................114
Appendix B .......................................................................................................124
Glossary............................................................................................................125
Acronyms ......................................................................................................125
Terms............................................................................................................126
Index ...............................................................................................................131
Worksheets.......................................................................................................135
Instructions....................................................................................................135
Teamwork .....................................................................................................136
Checklist........................................................................................................136
ii
Page 6
Welcome
Welcome
Welcome to the MPU955
guide is organized in a logical step-by-step sequence that will allow for both an easy and
accurate configuration.
First, an explanation of what MPU955 Admin Console is and how it works in a Network
Security System (NSS) is presented in general terms. Next, you will be guided through
installing the software, creating a configuration database, and loading the database into
the Network Security System’s CPU.
While creating the configuration database, you will find that many components interact
with each other, and are dependent on specific values. It will be important to utilize the
worksheets provided at the end of this manual to gather the data necessary to create the
configuration database, and to develop an understanding of your Network Security
System. These worksheets, once completed, should also be utilized when making
updates or changes to the system’s configuration, to ensure accurate results.
This part of the process will be explained in the Configuration section of this manual,
which is divided into three phases: physical planning, worksheet tasks, and keying in the
data.
*
Admin Console Installation and Configuration manual. This
*
Throughout this document, MPU955 refers to WJ-MPU955.
1
Page 7
This page intentionally left blank.
2
Page 8
Introduction
Introduction
MPU955 Admin Console enables an administrator and other users to closely control the
operation of a Network Security System (NSS). Such a system can include as many as
1,024 cameras and 256 monitors. You will be guided through the process of installing
MPU955 Admin Console to manage an NSS, creating the databases that dictate the
operation of the NSS, and allowing an administrator to easily change the system’s
configuration when necessary.
Control of the System
MPU955 Admin Console enables an administrator to utilize an NSS’s performance
capabilities to meet the surveillance needs of a facility during initial installation, as well
as when conditions change.
The NSS can be configured to help security personnel respond in different ways using
MPU955 Admin Console. For example, based on:
• Time of day - such as when open to the public, closed, and after-hours cleaning
and maintenance.
• Night quiet time.
• Quiet day of the week - which would be a 24-hour period of quiet time without
any activity except security personnel doing rounds.
• Special business activity - such as taking physical inventory, restocking, and
doing routine maintenance of special equipment.
• Visits by celebrities, dignitaries, or officials.
In addition, the NSS can be configured using MPU955 Admin Console to allow for quick
responses to unexpected disruptions of normal activity that could be caused by power,
fire, police, health, or other emergencies.
3
Page 9
Introduction
How It Works
MPU955 Admin Console is a management tool that maintains tracking, reporting, and
functional relationships between the various components in a network security system.
Configuration Management
It is possible for MPU955 Admin Console to maintain several separate configurations for
a given system.
One configuration, for example, could differ greatly from the typical configuration used,
because its purpose may be to watch over a particular activity, such as the taking of an
equipment and supplies inventory when the facility is closed to the public.
User Control
In addition to controlling individual cameras, MPU955 Admin Console provides the user
with selections from lists of presets and sequences.
• If the user chooses a group preset (not currently supported), a group of monitors
will display a set of video outputs from a group of cameras at preset positions.
• A sequence, on the other hand, is a system-controlled series of views - one of
several cameras on one monitor (a Tour Sequence) or of group presets (a Group
Sequence on several monitors – not currently supported).
What Happens Next
Installing the MPU955 Admin Console software only takes a few minutes and is very
simple to complete. A series of Windows dialog boxes guide the installation onto the PC.
The subsequent task of configuring the software, once installed, can range from modest,
for a small system, to complex, for a very large system, such as in an airport.
When it comes to security surveillance, all potential contingencies should be considered
when planning a system’s functionality. MPU955 Admin Console is the tool that
simplifies this process.
4
Page 10
Installation
Installation
Part of installing MPU955 Admin Console means copying program files from a CDROM onto the hard drive of a dedicated PC. MPU955 Admin Console is a tool that
allows an administrator to configure the NSS (Network Security System) with
information compiled about components and users, and to use well-planned presets and
sequences.
System Requirements
As with any PC application that must be reliable, MPU955 Admin Console should be the
primary program running on the computer it is installed on. There should be little other
than MPU955 Admin Console running on the same computer.
Minimum Hardware Requirements
• PC with an Intel® Pentium
• 64 MB memory
• 80 MB free hard drive space
• 10/100 Mbps Ethernet network interface card
Minimum Video Display Setting Requirements
• 256 colors
• 800 x 600 resolution
Operating System Requirements
• Microsoft
98SE, 2000 Professional SP4, XP Professional SP1a
®
Windows® (English Version)
®
III processor
5
Page 11
Installation
Installing MPU955 Admin Console
1. Insert the MPU955 CD-ROM into the CD-ROM drive on your computer – an
installation menu will appear
2. Select Admin Console and click the Next button – MPU955 Admin Console will
begin installing automatically
3. Respond to the dialog boxes by following the directions given
What Happens Next
The next section will guide you through the phases involved with the setup and
configuration of MPU955 Admin Console.
6
Page 12
Configuration
Configuration
MPU955 Admin Console configuration is a three-step process:
1. Mark copies of drawings of the facility under surveillance.
2. Fill in the appropriate worksheets provided at the end of this manual. (This will
result in a survey of all the components in your system, and how they interact
with one another.)
3. Enter the values collected on the worksheets into MPU955 Admin Console. (The
values entered determine the operation of the Network Security System (NSS) in
complete detail by creating relationships among all of the components, including
the users.)
Once existing copies of the facility’s drawings are marked, there is a basis for assigning
logical or area/local numbers, titles, and practical names for the various components of
the surveillance system. With this information, you can then continue with the MPU955
Admin Console worksheet tasks indicated below.
Worksheet Tasks
The MPU955 Admin Console worksheets aid in the collection and organization of
information needed to configure the NSS. One person can complete all of the worksheets
in a smaller system, but to speed up any installation, consider assigning a team of several
individuals to complete different worksheets concurrently.
Perhaps the surveillance system you are working with is small enough for you to collect
the required information, and input those values directly on to the MPU955 Admin
Console screens.
However, if the system is more complex, it is best to gather and write down the
information needed for the initial configuration of MPU955 Admin Console.
If settings need to be modified or updated in the future because of a change in
surveillance needs, or changes made in the components of the system, the worksheets can
be used to track past, current, and future configurations. The worksheets make it very
easy to do this, regardless of the size of your system.
7
Page 13
Configuration
As with any system configuration, it is wise to keep initial and updated worksheets on file,
just in case there is ever a need to re-enter the data, or troubleshoot the system.
Instructions
The title of each worksheet is the same as the title of the MPU955 Admin Console
window it supports. For example, the “Operators” worksheet supports the “Operators”
window. The fields that need to be filled in on the various MPU955 Admin Console
windows correspond to the sequence presented on the worksheets.
Reproduce the worksheets supplied with the system.
Copy pages from the actual worksheets located in the back of this manual.
You may only need a single copy of a certain worksheet, but dozens of copies of others,
depending on the components that make up your surveillance system.
Checklist
Worksheets are arranged alphabetically to make them easy to find. However, you can
follow the checklist below vertically for a workable sequence.
For a team approach to information collection, use best judgment to decide how to
distribute the worksheet among several individuals.
CPU Setup
GX Device Definition
(GX encoder or decoder)
Camera Definition
Monitor Definition
Alarm Input/Output
Operator Definition
Tour Sequences
Camera Presets
Group Presets
(not currently supported)
Group Sequences
(not currently supported)
Alarm Target Definition(s)
Alarm Definition(s)
Alarm Target Assignment(s)
Camera-to-Monitor Permission(s)
Controller-to-Camera View Permission(s)
Controller-to-Camera Control Permission(s)
Controller-to-Monitor Permission(s)
Controller-to-Group Sequence Permission(s)
(not currently supported)
Controller-to-Alarm IO Permission(s)
Controller-to-Alarm Permission(s)
Operator-to-Controller Permissions
Event Scheduler
8
Page 14
Configuration
Starting the Program
To start MPU955 Admin Console:
1. On the taskbar, click the Start button, click on Programs, click on Panasonic,
and then click MPU955 Admin Console
Logging In
Each time MPU955 Admin Console is run, this login screen will appear.
1. Enter the user login name (default = admin) and click the green check mark
(or press ENTER on your computer’s keyboard)
By default, there is no password defined.
Both the user login name and password fields are case sensitive.
It is recommended that after entering MPU955 Admin Console the first time,
that the user login name is changed, and a login password is defined, in order
to control administrative access.
During the configuration, add user names and passwords at various access levels as
needed. See the Account Manager section on page 110.
9
Page 15
Configuration
First Time Operation
CPU Setup
When MPU955 Admin Console is run the first time, the following window will appear
after you enter the default login name.
On this window you must match the CPU configuration in the software with the actual
CPU running the NSS.
Unit ID is always “1” when using MPU955 Admin Console, as only a single system unit
is supported.
1. Enter the IP address for the Main A CPU
10
Page 16
Configuration
Ask your installer or network administrator for the IP address for the Main A CPU. This
will let the MPU955 Admin Console software know where to send the configuration
database later.
2. If your system is equipped with a redundant CPU, then select the Redundant
check box and enter the IP address for the Main B CPU
Ask your installer or network administrator for the IP address for the Main B CPU. If the
system has just a single CPU, leave the redundant check box blank. The Main B CPU IP
address will not be required.
3. Enter a Unit Name for the system unit
It is best if the name is practical, and easy to understand by anyone using the system.
4. Decide on the operational mode for the NSS CPU by choosing the size of your
system from the Size drop-down menu
The Size Configuration section of this window is where you will see the details on the
size the CPU you select. As you choose Standard, Enhanced, or High-Speed, from the
Size drop-down menu, the maximum capacities of each size will display. The maximum
capacity is the largest supported number of each of the components listed. You must
match the main CPU (MCPU) capacity with the capacity in this window.
11
Page 17
Configuration
Standard
If any of the components in your system exceed the maximum capacity listed, you must
choose the next highest system type. For example, if the number of each of your
system’s components are less than the maximums listed for “Standard”, but you have 65
monitors, you would need to select “Enhanced” as your system type.
Enhanced
This is the next NSS CPU type available. Using the Enhanced CPU type will increase
the capacity of the system. This can be chosen as long as your system MCPU is the
correct version for this type.
12
Page 18
Configuration
High-Speed
This is the largest CPU type available, providing the capacity for handling the largest
number of components.
5. After making your selection, click the green check mark to save.
6. You can then click on the EXIT button to leave this window
Scheduled Modes
If the Scheduled Modes check box is selected on the CPU System Configuration
window’s Unit tab, an administrator can configure up to four different modes of
operation that can then be scheduled to become active as desired. The configuration of
these modes are programmed or set by an administrator during the configuration of the
system’s components through MPU955 Admin Console.
13
Page 19
Configuration
Viewing and Programming
In each of the components’ permissions tabs that contain a section like the
one shown to the left, modes can be viewed and programmed.
Clicking the View option button allows you to view permissions for the
mode chosen, and defaults to programming for the same mode. In the
case of the graphic to the left, mode 1 is set for viewing, and thereby
programming.
The permissions grid reflects the contents of the mode whose view is
selected with the View option button. In the image below, the permission
grid is displaying the contents of mode 1.
More than one mode can be programmed at the same time by clicking on
the Prog check boxes of the other mode numbers that you wish to
program simultaneously. This will append, or add any permissions that
are then changed on the permissions grid, but will not
modes or overwrite existing permissions in the other modes.
The image to the left indicates that the permissions grid would now be
displaying the contents of mode 3 (which is also by default being
programmed), and would simultaneously be programming any subsequent
changes into modes 1 and 4 as well.
It is not necessary to perform a Save for each mode viewed or programmed. Saving
permissions, when completed, automatically saves all four modes, regardless of the
current View or Prog selection. Permissions are described on page 56.
14
duplicate entire
Page 20
Configuration
Main Window
After entering the CPU IP address, selecting your system’s size, and exiting, the
following window will appear, which is the MPU955 Admin Console main window.
This window will be the first one you see from now on whenever you enter MPU955
Admin Console.
The main window is the heart of the MPU955 Admin Console configuration software.
Each component, sequence, setup, and management task will be accessed from the menus
on this window.
Each section will be utilized in order to configure and maintain the NSS.
15
Page 21
Configuration
py
p
Database Management
The active database for this system is the one residing within the Network Security
System (NSS). MPU955 Admin Console is used to create that database initially, and
from that point forward works with copies of it in order to establish and maintain useful
variations.
At Installation
When MPU955 Admin Console is first installed, an administrator must create and name a
new database. The database is stored on the MPU955 Admin Console computer’s hard
drive.
The administrator then enters all the information available about devices, components,
users, and sequences, and saves these details into the database using the Database
Manager.
See Creating a Database on page 17 for initial and subsequent database creations.
Database Archive
The Database Archive section of the Database Manager window is where each
configuration file (database) is manipulated. Several functions that can be performed
with the configuration files are selecting, creating, copying, renaming, or deleting.
This section also includes options to backup or restore a configuration file to or from
removable media or an alternate location, such as a floppy diskette or network drive.
Select
New
Co
Rename
Delete
Backu
Restore
16
Page 22
Configuration
Creating a Database
When entering Database Manager for the first time, there will not
as none have yet been created. An administrator must create and name a new database
for configuration.
1. Select Database Mgr… from the File menu
be any .adm files listed,
2. Click on the “New” button – the 2nd button in the Database Archive section
3. Type in a new name for the new database in this field
4. Click the green check mark
Enter any name that fits in the space provided. It is best if the name is practical, and easy
to understand by anyone using the system. You will be returned to the main menu after
naming the database.
This database will reside in MPU955 Admin Console. Adding and saving information
about the components and desired operation of the system will configure it.
17
Page 23
Configuration
Selecting a Database
Viewing and Reconfiguring
Whenever you wish to view or edit settings from the components, sequences, or setup
choices on the main menu, you must have the database whose contents you wish to work
with open. If you have just entered MPU955 Admin Console, and click on one of those
options, you will automatically be prompted to select a database. The database you
choose will open, and will immediately be followed by the option window you have
chosen. The database you select becomes the default database for all settings until you
go back to Database Manager to choose or create a different one.
1. Select the name of a database by clicking on it
2. Click the Select button - the 1st button in the Database Archive section - or
double-click on the desired database
You will notice that the system unit ID number and the name of the database currently in
use are displayed on the title bar of this window. In the example above, the system unit
number is 01, and the database currently being used is “standard”.
When changing the database you are working with, MPU955 Admin Console will open
the selected database, making it the default, and will close the Database Manager window.
You will be returned to the main menu, ready for the configuration or review of the
database you just selected.
18
Page 24
Configuration
Copying a Database
Making Similar or Alternative Databases
An administrator can make copies of a database, as desired, and name them to reflect
their purpose. This would normally be done to enable the system to respond to changing
conditions and surveillance needs without having to completely recreate a database to
accommodate these changes.
1. Highlight the name of the database you wish to copy in the Database
Manager window
2. Click the Copy button - the 3rd button in the Database Archive section
3. Name the copy in the space provided
4. Click the green check mark
Enter any name that fits the space provided. It is best if the name is practical and easy to
understand by anyone using the system.
19
Page 25
Configuration
Renaming a Database
Renaming a database is useful when creating several configurations to fit the needs of
specific occasions, and changing the name to ensure each file has been updated. For
example, if date codes or initials are used in the name or description of a database, an
administrator may want to revise the date code or user initials as necessary.
1. To rename a database, highlight a database name
2. Click the Rename button - the 4th button in the Database Archive section
3. In the “Rename to:” box, type the new name desired
4. Click the green check mark
20
Page 26
Configuration
Deleting a Database
In order to reduce the number of configuration files listed in Database Manager, and
thereby decrease the potential for confusion as to which file is loaded on the NSS CPU,
outdated or unused configuration files can be deleted. If the files may be needed again in
the future, it is recommended that you backup the files to an alternate location (see page
22) so they can be deleted from MPU955 Admin Console, and restored later if necessary.
1. To delete a database, highlight the database name
2. Click the Delete button - the 5th button in the Database Archive section
The following confirmation message will appear:
3. Click Yes to delete, or No to cancel.
21
Page 27
Configuration
Backing up or Restoring a Database
It may be necessary at times to save a copy of a particular database for backup,
troubleshooting, or other purposes. MPU955 Admin Console allows an administrator to
perform both backup and restore functions in order to maintain copies of the
configuration files outside of the MPU955 Admin Console system.
Backing up a Database
1. Within Database Manager, highlight a database name and click the Backup
button - the 6
th
button in the Database Archive section
The following window will appear.
22
Page 28
Configuration
2. Choose the drive and folder you wish to backup to, just as you would in
Windows Explorer
3. Click OK
This procedure will only copy the highlighted configuration file to the specified location.
It will not remove it from the Database Manager.
Restoring a Database
In addition to backing up a configuration file, it may also be necessary at times to restore
a copy of a particular database from a backup, an e-mail, or from troubleshooting
personnel. MPU955 Admin Console allows an administrator to perform a database
restore from a source outside of MPU955 Admin Console.
1. Within Database Manager, click the Restore button - the last button under
the Database Archive section
The following window will appear.
23
Page 29
Configuration
2. Choose the drive and folder that contains the desired .adm file, just as you
would in Windows Explorer
3. Click OK
Because you may have multiple files saved in the same location, the restore feature
allows you to choose which file to restore.
4. Select the desired file to restore, and click the green check mark
The left side of the Database Manager window represents the configuration files already
stored within MPU955 Admin Console. The right side of the window represents the files
stored in the folder that you have just specified.
24
Page 30
Configuration
This procedure will copy the selected configuration file into MPU955 Admin Console
from removable media or an alternate location, but will not remove it from its current
location.
Getting the Current Database
In order to retrieve a copy of the configuration currently running on the system, and to
bring it into MPU955 Admin Console, an administrator must retrieve it using the
Database Transfer section’s “GET from CPU” option. This option allows the
administrator to view, modify, copy, or create new versions of the current configuration
once it is imported into MPU955 Admin Console.
1. From the drop-down menu in the Database Transfer section select either 01A
or 01B CPU
2. Click the “GET from CPU” button - the left button under the Database
Transfer section
3. Enter the new name for this particular database in the “Save to:” box
4. Click the green check mark
A copy of the database that is currently running on the selected NSS CPU is now saved
on the MPU955 Admin Console computer’s hard drive. It will not
Main CPU. At this time, you may view or modify the configuration.
be removed from the
25
Page 31
Configuration
Loading a Database
In order to copy a configured database from MPU955 Admin Console onto the NSS Main
CPU, an administrator would need to use the Database Transfer section’s “PUT to CPU”
option.
Although not mandatory, first saving the current database residing on the CPU would
allow for a manual comparison of any differences prior to loading the new database.
MPU955 Admin Console itself cannot detect differences. (Unless this is a first time
operation.)
Putting a configuration database onto the NSS CPU will overwrite its
entire existing database. It is recommended that you save the database
currently running on the Main CPU under a distinctive name before
loading a new database.
The following instruction will guide you through loading a database from MPU955
Admin Console to the CPU. See the Getting the Current Database section on page 25 to
save the database that is currently loaded in the CPUs.
1. Select the name of the database to load by clicking on the .adm file name
2. From the drop-down menu, select the proper CPU
For a redundant CPU system, you must load the database onto both CPUs to ensure they
are each using the same configuration.
For single CPU systems, choose 01A.
3. Click the “PUT to CPU” button - the right button under the Database
Transfer section
26
Page 32
Configuration
A “Confirm PUT Transfer” window will appear.
If you choose to continue, the new database will be loaded, overwriting the existing
database, and it will remain on the CPU to run the NSS according to the configuration.
4. Click Yes to continue the transfer, or No to cancel
27
Page 33
Configuration
System Configuration
The system file (##A=sys.ini – where ## is the system unit ID number) resides on the
main system CPU, and contains information that is critical for proper operation. On
systems with a redundant CPU, it may be necessary to modify the system file on both of
the NSS CPUs individually, in order to maintain proper operation. DO NOT
file unless instructed to do so by qualified technical support personnel.
MPU955 Admin Console uses the System Configuration utility to allow an administrator
to work with this file. When instructed, follow the steps below for viewing, modifying,
backing up, and restoring the ##A=sys.ini file.
For the purposes of this document, the system unit ID will be 01, so the system file name
will be 01A=sys.ini.
System Transfer
When performing a file transfer in the System Configuration utility, the system file is
written to the MPU955 Admin Console computer’s hard drive as “01A=sys.ini” and
“01B=sys.ini” - depending on which CPU this function was performed. In most cases,
the system file residing on the MPU955 Admin Console computer’s hard drive will be an
exact duplicate of the file being used on the system’s CPU(s).
It is possible for the file on the local drive to differ from the one being used by the system,
when using the restore function. An administrator must be very careful when using the
backup and restore functions, as well as when retrieving and replacing the system file on
the CPU(s). It is very important that the administrator be aware of which CPU is being
updated.
modify this
28
Page 34
Configuration
Retrieving the System File from the Main CPU
1. Select the CPU Units command from the Domain menu
2. Click on the SYS tab on the right side of the window
The following window will appear.
Choose “01A” from the SYS Transfer drop-down
menu (01 is the system unit ID in this example)
29
Page 35
Configuration
3.Click the “GET from CPU” button – the left button under SYS
Transfer
MPU955 Admin Console will retrieve the system file from the selected CPU and display
it in the window provided.
At the same time, the system file is saved in the “\Program
Files\Panasonic\GXLAC\SysIni” folder as “01A=sys.ini” (or “01B=sys.ini” if from the
redundant CPU).
4. Modify the system file as needed
Modifications will not be saved on the MPU955 Admin Console computer’s hard drive
until a “PUT to CPU” is performed, which replaces the system file in the CPU selected.
See “Replacing the System File in the Main CPU” below, in order to send the updated
file information to the system CPU.
Replacing the System File in the Main CPU
1. From the CPU System Configuration window (accessed by selecting the CPU
Units command from the Domain menu), click on the SYS tab on the right
side of the window
2. Choose “01A” from the SYS Transfer drop-down menu (01 is the system unit
ID in this example)
3. Click the “PUT to CPU” button – the right button under
SYS Transfer
This will replace the existing system file in the specified CPU with the modified one.
3. A “Confirm PUT Transfer” window will appear. Click Yes to continue with
the transfer, or No to cancel the transfer
Repeat the steps for Main B CPU, as needed, selecting “01B” from the drop-down menu
in step 2 of the Retrieving the System File from the Main CPU and Replacing the System
File from the Main CPU procedures. (01 is the system unit ID in this example)
It will be necessary to reboot each CPU when finished so that the updated
information is read and executed correctly. See Resetting the Main CPU on
page 35.
30
Page 36
Configuration
01A and 01B system files differ slightly. It is not recommended that
identical system files be loaded into both Main A and Main B CPUs.
System Archive
After the Main A and Main B CPU system files have been
retrieved for the first time, it will be possible to view these files
at a later date without actually performing a transfer. These files
(“01A=sys.ini” and “01B=sys.ini”) will be stored in the
“\Program Files\Panasonic\GXLAC\SysIni” folder on the
MPU955 Admin Console computer’s hard drive.
Selecting
In order to view the system file stored on the MPU955 Admin Console computer’s hard
drive:
1. From the CPU System Configuration window (accessed by selecting the CPU
Units command from the Domain menu), click on the SYS tab on the right
side of the window
2. Choose “01A” from the SYS Archive drop-down menu
3. Click the “Select” button
31
Page 37
Configuration
Backing Up
After the “01A” and “01B” CPU system files have been retrieved for the first time, it will
be possible to save these files to a different location, such as to floppy diskette. These
files (01A=sys.ini and 01B=sys.ini) are stored in the “\Program
Files\Panasonic\GXLAC\SysIni” folder on the MPU955 Admin Console computer’s hard
drive. Performing a backup from the SYS Archive section will save a copy of the
specified system file to an alternate location of your choice.
1. Choose “01A” from the SYS Archive drop-down menu
2. Click the Backup button under the SYS Archive section
3. When the “Browse for Folder” window appears, browse to the desired
location
4. Click the OK button
5. Repeat for the “01B” system file if needed
Restoring
At some time, it may be necessary to restore or replace the current system files with a
saved (backed up) version, for example, during system troubleshooting. The restore
function will copy the “01A=sys.ini” and “01B=sys.ini” files from the location you
specify, and put them into the “\Program Files\Panasonic\GXLAC\SysIni” directory on
the MPU955 Admin Console computer’s hard drive.
1. Choose “01A” from the SYS Archive drop-down menu
2. Click the Restore button under the SYS Archive section
3. When the “Browse for Folder” window appears, browse to the location that
the saved system file resides
This should be the location you backed the file up to.
4. Click the OK button
The system file (01A=sys.ini) that is stored in the “\Program
Files\Panasonic\GXLAC\SysIni” folder will be replaced with the file from the location
that you specified.
32
Page 38
Configuration
5. Load the restored file into the Main A CPU if desired
See “Replacing the System File in the Main CPU” section on page 30
6. Repeat for the “01B” system file, if needed
Wizard
When you want to make changes to the system file’s [System] section - which defines the
values for Cameras, Monitors, and Keyboards - you can use the wizard function in the
SYS Archive section of the CPU Configuration Window to do this automatically.
If the values for these components already exist in your system file, they will be edited, if
necessary, to reflect the recommended settings. If the values for these components do not
already exist in your system file, the wizard will add them to the system file.
1. Choose “01A” from the SYS Transfer drop-down menu
2. Click the Wizard button under the SYS Archive section.
3. When the Confirm window opens for you to confirm the changes to be made,
click Yes to continue and edit the file, or click No to cancel the wizard
function
33
Page 39
Configuration
The Wizard button’s appearance will change to indicate if any changes to the system file
are recommended. The gauge area on the left side of this icon indicates if the [System]
components’ settings are: A) too low for the CPU size selected (yellow), B) matching the
CPU size selected (yellow and green), or C) too high for the CPU size selected (yellow,
green, and red).
Too low
for CPU
setting
Matches
CPU
setting
Too high
for CPU
setting
When the icon displays yellow and green, indicating that the settings match the CPU size
selected, there is no action required. If the icon indicates settings are too low or too high,
click the Wizard button to have the settings changed to match your system. You will
then be prompted to confirm that you want the suggested modifications of the system file
to take place.
34
Page 40
Configuration
Resetting the Main CPU
After replacing the system file in the main CPU, each CPU needs to be rebooted so that
the updated information is read and executed correctly (See Replacing the System File in
the Main CPU on page 30).
1. Select the CPU command from the Domain menu, and select the Reset tab
2. Select the CPU you wish to reset from the drop-down box
3. Click the red Reset button to reset the selected CPU
4. Verify that you wish to reset the selected CPU by clicking Yes on the
Confirm Reset window that appears
If a backup CPU is in place, you will be asked to reset that CPU as well. Reset
that CPU as well, so that both CPUs are using the update system file.
35
Page 41
Configuration
Input to Screen
You will begin configuring the database using the Domain and Components menus on
the main window:
The title bar of each option window you enter will show the name of the main
menu option being displayed, followed by the name of the current default
database (.adm) file being viewed or edited. In the case below, the option being
displayed is controllers, and the database file being used is standard.adm.
Main menu
option you are
working with.
System unit number, and
database (.adm) file you
are working with.
36
Page 42
Configuration
Switch Nodes
Digital (GX) – GX Devices
GX devices include both encoders and decoders. Encoders convert analog video signals
to digital data (MPEG2). Decoders convert digital data (MPEG2) to analog video signals.
Definition
1. Select the Switch Nodes command from the Domain menu, and then select
Digital (GX)
2. Click the Add Record button
37
Page 43
Configuration
3. Enter all information required about each GX Device
GX DEVICES - Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a device is added, in order to
ID
identify one device to the system. 1 to 1,024.
MPU955 Admin Console automatically generates this number in consecutive order. Upon
adding devices, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify
one component or sequence from another in row and column style. Since logical and local
numbers are not necessarily unique or consecutive; and the permission grids are displayed as
consecutive, unique numbers; MPU955 Admin Console generates these ID numbers.
Numeric Ethernet interface number identifying a port on a CPU where the device will connect.
I/F
0 to 15, though generally 0, 1, or 2.
Unique Internet Protocol address assigned by the system administrator. Dotted decimal, 15
IPA
characters (including dots). Example: 128.010.050.125
Numeric address for an Ethernet controller. Dotted hexadecimal Example: 23.56.82.13.60.82
EA
(Also known as MAC address.)
A name for the device. Alphanumeric, 16 characters.
Name
Location
Encoder / Decoder
(device type)
A name for the device location. Alphanumeric, 16 characters.
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
If the device is an encoder, select the Encoder button, and choose the range of input ports from
the Input Ports drop-down menu. The range must be unique for each encoder.
For GXDIN, select its Input Ports; for GXDOUT, select its Output Ports; and for GXRS485,
enter its Port number.
Enter the hexadecimal Address [SW1] in the A, B, and C fields.
If the device is a decoder, select the Decoder button, and choose the range of output ports from
the Output Ports drop-down menu. The range must be unique for each decoder.
For GXDOSD Output Ports, select the output ports from the drop-down menu.
Enter the hexadecimal Address [SW1] in the A, B, and C fields.
4. Click the green check mark to save
You will remain in the “Add” mode, allowing you to enter information about another
device.
5. To exit the “Add” mode, click the red X
You will exit the “Add” mode.
6. To edit a configured device, highlight a device ID and click the Edit
button
You may also double-click on a device ID in the list to enter the edit mode.
7. Edit the desired fields
38
Page 44
Configuration
8. Click the green check mark to save and exit the edit mode, or click the red X
to cancel
9. To delete a device, highlight a device ID and click the Delete Record
button
A confirmation message will appear.
10. Click No to cancel, or click Yes to delete the selected device
11. To view details about a device, highlight the device ID and click the
Advanced Config button (see warning below)
A message window appears asking you to confirm that you want to access these settings.
If you answer “Yes”, a GX Details window appears, showing details about the selected
device.
Do not change any of the values in the GX Details table that
appears.
These default settings ensure proper operation in almost all cases.
Refer to the Appendix section of this manual for additional details.
Consult with your surveillance system’s design and
implementation professional before changing any values.
Analog (MX) switch nodes are only configurable in ASC960
Admin Console 4.0. Contact your Panasonic representative for
details.
39
Page 45
Configuration
Components
Selecting any of the components listed on the Components menu opens a window that
requires information from one or more of the Setup Worksheets that you have completed.
Input the required information for each of these components separately: alarms, cameras,
system controllers, alarm I/O ports, monitors, and operators.
40
Page 46
Configuration
Alarms
Alarms play an important role within an NSS. Alarms can automatically trigger up to ten
actions, such as camera spots, tour sequences, or group sequences (not currently
supported), in any combination. These actions allow the system to open or close a
contact connected to an I/O port that will start a siren or possibly turn on a spotlight.
They also can alert the operator by displaying cameras on a monitor during a triggered
alarm.
In order to configure alarms successfully, an administrator must first create the alarm
targets, and then create records that will initiate the actions. Targets are defined as a
group of monitors. The alarm actions are then linked to available alarm targets.
The following are rules to follow when configuring alarms:
• An alarm can invoke up to ten actions
• A monitor can be a member of only one target
• A target can contain several monitors exclusively
• Many targets can be linked to each alarm
• The same target can be assigned to more than one alarm
Defining an alarm can be a challenging task. ID numbers identify each alarm, source,
action type, and target. The following procedure will explain each step so that an alarm
target can be defined, an alarm can be identified by the source, actions can be taken when
the alarm is triggered, and a target can be defined and assigned to display the specified
action.
41
Page 47
Configuration
Alarm Target
An alarm target is an ID number that defines a group of one or more monitors.
Alarm targets are assigned to alarms in order to link alarm actions to specific monitors.
At least one alarm target must be created before you can create an alarm.
When an alarm is triggered, an action will occur. For example, causing a camera spot
(configured in the alarm definition) to display on an array of monitors assigned to a
specific target.
Be careful when assigning monitors across areas to the same target.
This will be important when assigning a target that contains monitors
in a different area than the Alarm Action Tour Sequence.
1. Select the Alarms command from the Component menu, and then select
Target Setup
2. Click the Add Record button to add a target record
42
Page 48
Configuration
3. Double-click on each monitor ID that you wish to add to this target record
As you double-click on a monitor ID number’s corresponding box, the representative box
will turn green, indicating that it is now part of this record.
First row = monitor IDs 0-9, second row = monitor IDs 10-19, etc.
Besides choosing which monitors will be part of a specific target ID, you must also
choose either Hold or Sequence from the Display Mode section of this window to define
the display mode for the entire target record.
When more than one monitor is selected, alarm actions are distributed across those
monitors.
When “Hold” is chosen, the alarm action with the highest priority for each monitor is
displayed, and remains until it is acknowledged. Once acknowledged, the next queued
action with next-highest priority is then displayed – again until acknowledged. When
“Sequence” is chosen, the alarm actions for each monitor are displayed in sequence
without requiring acknowledgement.
You will also select the first and last Output Port for the entire target record. The First
port indicates which port will be triggered when there is an alarm action to the target
monitor. The Last port indicates which port will be triggered when the alarm actions are
removed from the target monitor.
43
Page 49
Configuration
4. Click the green check mark to add the series of monitors, or click the red X
to cancel
The permission grid is shown by monitor ID only.
A monitor can only be a member of one target. Therefore, when adding
additional targets, monitors that are already assigned to a different target
appear as yellow blocks. Green blocks indicate monitors assigned to the
highlighted target ID. White blocks are either unassigned or undefined
monitor IDs.
To re-assign a monitor to a different target, remove the monitor from its
current target, thus making it available for re-assignment. You can determine
what target ID it is currently assigned to by clicking on it and seeing the ID
number that appears in the Target box under the grid.
Targets cannot be deleted if they are assigned. The assignment must be
removed from the Alarms window prior to deleting it.
The Other tab shows the alarm(s) that the selected target is assigned to. Targets are
assigned to alarms from the Target tab of the Alarms (Records) window as described
below.
Use the Edit Record or Delete Record icons at the bottom of this window to edit or delete
alarm target records as needed.
44
Page 50
Configuration
Alarm Definition To define an alarm record, select Alarms from the Components menu, and then select
Records. An Alarm Target must be created before an alarm can be defined.
Add, edit, or delete alarm records as needed using the three icons at the bottom of this
window.
45
Page 51
Alarms – Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as an alarm is added, in order to identify
ID
the alarm to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon
adding alarms, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one
component or sequence from another in row and column style. Since logical and local numbers
are not necessarily unique or consecutive, and the permission grids must be displayed as
consecutive, unique numbers, MPU955 Admin Console generates these ID numbers. 1 to 1,024.
Logical
Priority
Enable
Auto Arm
Allow Disarm
One State
Output Port:
Active
Source:
Unique number assigned by an NSS administrator. An operator will view alarms by this logical
number. 0 to 65535.
Level that determines an order of precedence between alarms. Alarm priorities work in
conjunction with the operator priority and determine the order of precedence between alarms and
operators. (Smaller number has higher priority.) 0 to 65535.
Defines whether or not an alarm is enabled. Check the box to enable the specific alarm.
If checked, the specified alarm will automatically re-arm itself after being acknowledged
If checked, operator will be allowed to disarm the specified alarm.
If checked, the specified alarm, once triggered, will not be monitored for its return from the
triggered state.
This is useful when you are only concerned that the alarm was triggered, but do not need to know
the duration of the triggered state.
An alarm set for One State can be reset even if the alarm condition still exists. Without this
option checked, if an alarm is triggered and you attempt to reset it, it will continuously trigger
again until the triggered state has ended.
If checked, the indicated output port will be turned ON when this alarm is active.
If not checked, the indicated output port will be turned OFF when the alarm is active.
Enter an output port number to specify which port will be turned ON or OFF when the alarm is
active.
If no output port action is required when the alarm is active, uncheck and leave the output port
number blank.
If checked, the indicated output port will be turned ON when this alarm is acknowledged.
Ack
If not checked, the indicated output port will be turned OFF when the alarm is acknowledged.
Enter an output port number to specify which port will be enabled when the alarm is
acknowledged.
If no output port action is required when the alarm is acknowledged, uncheck and leave the
output port number blank.
If checked, the indicated output port will be turned ON when this alarm is reset.
Reset
If not checked, the indicated output port will be turned OFF when the alarm is reset.
Enter an output port number to specify which port will be enabled when the alarm is reset.
If no output port action is required when the alarm is reset, uncheck and leave the output port
number blank.
Type
Identifies the source of the specified alarm, camera (motion detection), or I/O (external source
connected to an alarm input card), RS232 (external source connected to an RS232 port), Vid Loss
(any) (detects video loss from any port in the system), or Vid Loss (cam) (detects video loss only
from the single specified camera).
Configuration
46
Page 52
Alarms – Definition
Field Data
Uniquely identifies the chosen source that will trigger the specified alarm by its ID number.
ID
Camera = port number of camera connected to the controller card. I/O Port = port number of the
Input port that the external source is connected. RS232 = port number of the external source that
will be connected through the RS232 port. Vid Loss (port) = port number of the input port that
will be detecting video loss. Note: When the source type is Vid Loss (any), this selection is
unavailable since multiple ports on the system can serve as the source.
Acknowledge:
On-Screen
Display
Location
Reset – Mode
Determines whether a user must manually respond to an alarm when triggered or if an automatic
Mode
response is generated requiring no user intervention. Choose Manual, Auto, or Both.
Defines the delay in seconds when an alarm is in Auto Acknowledge mode before the alarm is
Delay
automatically acknowledged. (min:sec) Up to 59:59
In the Text box enter the text that you want to appear on the screen when an alarm is triggered.
This text will be displayed on all of the monitors that are part of the actions you select on the
Actions tab.
Practical name to help an administrator select an alarm by location. Alphanumeric. Examples:
Main concourse, loading dock, boiler room.
Chooses the method by which the alarm will be reset. Manual, Auto, and Both are options.
Specify the amount of delay time prior to resetting the alarm using the mode selected. In Auto
Delay
mode, the reset delay is started after the alarm is acknowledged.
Configuration
47
Page 53
Configuration
Alarm Actions The Actions tab allows an administrator to specify up to ten alarm actions for each alarm.
To add an action to the list, click anywhere on the next available empty row (or row 0 if
this is the first entry), make your action selections, and then click:
The green check mark to confirm the action, or
the red “x” to cancel its entry.
To remove an existing action from an alarm, click on the line that contains
the action you wish to remove, select the delete check box and then click
the green check mark to confirm the removal of the selected action.
48
Page 54
Alarms – Actions
Field Data
Choose the type of action to perform when the alarm is triggered. Click on the first
Type
blank box under this column, and select Cam Spot (camera spot), Tour Seq (tour
sequence), Grp Seq (group sequence – not currently supported), or Text Only.
Identifies the ID number of the camera, tour sequence, or group sequence (not currently
ID
supported) depending on what was selected as the action type. Choose the ID number
off of the list that appears at the right of the Alarms window when on this tab.
CPreset. Number identifying a preset position of the camera specified. 0 to 64 (0 = no
CPre
preset). This setting is only available and necessary when Cam Spot is the selected
action type.
Choose if an auxiliary function will take place. An auxiliary function requires
Aux
additional hardware at the chosen camera – such as a camera receiver switch. If
unavailable or not desired, choose None. If available and desired, choose Aux1, Aux2,
or Both as the function to perform during that action. This setting is only available and
necessary when Cam Spot is the selected action type.
Amount of time that a monitor maintains a view. Up to 59:59 (hr:min)
Dwell
Practical name given to an action, or in the case of the action type of Text Only,
Text
specifies the text that will be displayed.
Configuration
Assign an Available Target
The Target tab from the Alarms window allows an administrator to assign an existing
target ID to a specific alarm. The existing target IDs appear under the Available section
of this window.
The Monitors section of this window shows the administrator which monitors are part of
the highlighted target ID; and the display mode section shows the mode for the target.
Monitors can also be viewed by area\local number.
49
Page 55
Configuration
1. Highlight the available target ID you wish to assign to the selected action for
the selected alarm
2. Click the Assign Target icon to assign the selected target to the
selected action for the selected alarm
The Display Mode and Output Port sections are informational only.
3. Click EXIT when finished assigning targets to actions associated with alarms
More than one alarm target can be assigned to each action. A target can be
assigned to more than one action. More than one alarm ID can contain the
same alarm targets in its actions.
Removing an Assigned Target From the Target tab of the Alarms window:
1. Highlight the alarm you wish to remove a target from
2. Highlight the assigned target you wish to remove
3. Click the Remove Assigned Target button
4. Click EXIT to exit
50
Page 56
Configuration
Alarm Permissions Modify or copy alarm permissions in the same manner described in the Camera
Permissions section, beginning on page 56.
The Controller permission tab allows an administrator to permit or deny a controller the
ability to seize a specific alarm. The Modes section of this tab is described on page 13.
The permission grid’s dimensions are based on the maximum capacity for
the chosen CPU size, not on physically installed components already in the
database.
51
Page 57
Configuration
The Modes tab on the Alarms window allows an administrator to determine what modes
are active for an alarm. By default, all four modes are active, even if all four have not yet
been defined. This tab will be grayed out and inaccessible unless Scheduled Modes
have been selected. See page 13 for full details on modes.
52
Page 58
Configuration
Cameras
Every camera in the system can be identified in several ways. Not only is there a
physical identification to a particular installation (such as the cabling run and port
connection), but there is also information that may change when a camera is removed or
replaced at any given location. For each camera there is a record that contains its details.
An operator calls a camera by its logical camera number. However, configurations can
be viewed in MPU955 Admin Console not only by logical number, but also by ID
number, control port, or video port.
Definition
1. Select the Cameras command from the Component menu
Add, delete, edit, or replicate camera records as necessary using the four icons at the
bottom of this window.
53
Page 59
Configuration
When deleting or modifying a camera, be sure to check the Other tab to find
references to other sections that refer to the camera.
Deleting a camera will automatically delete the referenced permissions,
but will not change any other references, such as sequences or alarms.
CAMERAS – Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a camera is added, in order to identify one
ID
camera to the system. 1 to 8,192.
MPU955 Admin Console automatically generates this number in consecutive order. Upon adding
cameras, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one
component or sequence from another in row and column style. Since logical and local numbers are not
necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique
numbers, MPU955 Admin Console generates these ID numbers.
Logical
Model
Switch:
Digital / Analog
Ports:
Control
Video Signal
Compensation
Loss Threshold
Alarm Trigger
Digital Bitrate
On-Screen Display
Location
Unique number assigned by an NSS administrator, usually designated by combining two references, such
as having the first 2 digits represent a logical group (such as a group of cameras surveying a loading
dock), and up to three serial digits assigned for other logical reasons. 1 to 99,999. Examples: 84 001,
84002, 84003, 84004; 3 6 001, 36002, 36003, 36004. An operator will select cameras to view by this
logical number. 0 to 65535.
Choose from the drop-down list the correct camera model connected to the specified ports. MPU955
Admin Console will automatically enable the features available with the specific camera model, such as
pan/tilt, iris control, motion detection, configuration menu, control data, zoom/focus, presets, VD2
synchronization, RS485, or function codes.
If the desired camera model is not listed, choose <Other>. Enable the appropriate features manually,
according to the manufacturer’s camera description, by checking the associated check boxes.
Check the “control data” box when a control data signal should be sent to the camera.
When RS485 is chosen, the Cfg (configure) button will become enabled. Click the Cfg button to
configure the RS485 port for the following settings: baud rate, parity, data length, stop bits, daisy on/off,
and choosing a 2 or 4 wire connection.
Note: Analog is only selectable in ASC960 Admin Console 4.0. Contact your Panasonic representative
for details.
Number of the input port on the GX device to which the camera cable is connected. 1 to 8,192.
The video port will be assigned the same value as the control port. It cannot be changed.
Video
Cable length from camera to the video import board: short, medium, or long. The system compensates
for these three values by modifying the signal strength.
Note: Only selectable in ASC960 Admin Console 4.0. Contact your Panasonic representative for details.
Select this checkbox if you wish to use the video loss alarm as an alarm trigger.
Choose the bitrate (Mbps) from the drop-down list. Select “Shutdown” from this list to close this video
channel.
Enter an alphanumeric Title to be displayed.
Only a decoder generates the time and date (T&D), the camera ID (ID), and the Title specified.
Name to help an administrator identify a camera by location. Alphanumeric, 16 characters. Examples:
main concourse, loading dock, boiler room.
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
54
Page 60
Configuration
Replicating a Camera Definition
1. Highlight a configured camera ID and click the “Replicate Record”
button
A confirmation message will appear asking “Are you sure you want to REPLICATE this
camera?” and explaining the replication rules:
[1] Records will be generated according to ID.
[2] ID will be incremented to the next available value.
[3] Logical #, Control & Video Ports will be incremented from a specified base value you
assign.
[4] If a record already exists with a matching value for any of these unique fields, that
Target assignment will be skipped.
[5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel
3. Enter the number of camera records to create in the Target Size box
4. Enter the beginning Base Values of the logical camera number and control
port from where you wish to begin incrementing
5. Click the green check mark to add the series of cameras, or click the red X to
cancel
After clicking the green check mark, a Replication Summary window will
appear, which will let you know how many records were actually generated,
and indicate if any records could not be created due to a conflict with an
exiting record. If any of the required unique values involved are already in
use, the entire record will be skipped; existing records will not be overwritten.
If a conflict exists, you will be asked if you wish to see a list of the records
that were skipped. Click Yes to see the Replication Activity Log list, or click
No if you do not wish to see the list. It is recommended that you view the list,
so that you can modify the conflicting values as necessary, and add the
records you desire.
55
Page 61
Configuration
Permissions
The permission tabs allow an administrator to easily permit or deny components access to
other components.
By default, all components are allowed to access all other components. An administrator
must deny permissions.
1. Highlight a camera and click on the Cam Ctrl permission tab
The Cam Ctrl permission tab allows an administrator to permit or deny a system
controller to control specific cameras. The Modes section of this tab is described on page
13.
Allowing a system controller to control a certain camera will automatically
allow the same controller to view the specified camera.
56
Page 62
Configuration
Cameras are displayed in the list on the left by ID number, but can also be viewed by
logical number, control port, or video port. The grid on the right represents the
following:
First row = controller IDs 0-9, second row = controller IDs 10-19, etc.
Green blocks indicate an allowed permission, and white blocks indicate that permission is
denied.
2. Double-click on a specific controller to invert or alternate between permit or
deny
Be sure to click the save button (the picture of the floppy disk) before exiting
each particular permission tab to ensure the changes will be saved correctly.
The permission grid’s dimensions are based on the maximum capacity for the
chosen CPU size, not on physically installed components already in the
database.
3. Highlight a row, a column, or click and hold the mouse button to highlight a
group of controllers
4. Click the Invert Grid Selection button to change the state of
the permission for the highlighted group, or
5. Click on the Permit All button to turn the entire grid green –
allowing all controllers permission to control the specified
camera, or
6. Click on the Deny All button to turn the entire grid white –
denying all controllers permission to control the specified
camera, or
7. Click on the Copy Grid button to copy the permission grid
from a specific camera to other cameras
Copying Cam Ctrl permissions to other cameras will also copy Cam
View permissions to the specified cameras.
A confirmation message will appear asking “Are you sure you want to COPY the Cam
Ctrl & Cam View permission for this Camera?” and explaining the copying rules:
[1] Permissions will be copied by Camera ID.
57
Page 63
Configuration
[2] If permission already exists for a Camera that falls within the Target range, that
original permission will be overwritten.
8. Click Yes to continue or No to cancel
The copy source is the highlighted camera ID from where the Cam Ctrl permissions will
be copied.
9. Enter the Target ID range of camera ID numbers, with the beginning
number in the START box, and the ending number in the END box
Permissions existing for cameras within the specified range will be
overwritten.
10. Repeat steps 1-9 for all other permission tabs
The Cam View permission tab allows an administrator to permit or deny a system
controller to view specific cameras. The Modes section of this tab is described on page
13.
Denying a system controller to view a certain camera will
automatically deny the same controller permission to control the
specified camera.
The Monitor permission tab allows an administrator to permit or deny a camera the
ability to be displayed on a monitor.
A monitor ID can be determined by its area and local number by entering
each value into the appropriate box, and then clicking the “Search for
Monitor by Area & Local” button.
11. Highlight a component within the permission grid, and click the
definition button.
A window will appear; giving a quick view of that component’s configured definition.
58
Page 64
Configuration
This button is available: 1) on each of the permission tabs for each component; 2) on the
Other tab in the Cameras window; and 3) on the Areas window.
12. Click on the “x” in the upper right corner to close.
Other
The Other tab shows which other NSS components or sequences are configured to
include the highlighted camera.
This section is informational only. Changes cannot be made to other components or
sequences from this window. Changes must be made from each specific component or
sequence’s menu option.
On the next image, for example, tour sequence number 1 is configured to include camera
ID 1. The Tour Sequence section of this tab for camera ID 1 was automatically updated
when tour sequence 1 was created to include this camera. To remove camera 1 from tour
sequence 1, you would need to exit the Cameras window, enter the Tour Sequences
window from the main menu, and edit sequence number 1.
59
Page 65
Configuration
Camera Positions (not currently supported)
An operator, from a system controller, can control each camera in the system that
supports Presets by pressing the Camera Position button on the controller. The operator
cannot define positions, but rather, can only recall positions (which are a combination of
Camera ID and CPreset numbers) that have already been defined.
The Camera Positions setting in MPU955 Admin Console allows administrators to define
and consolidate the Camera ID and CPreset numbers into a Position ID number that the
operator can then conveniently call from the system controller.
1. Select the Cameras command from the Component menu, and then select
Positions
60
Page 66
Configuration
The Position ID is automatically inserted and incremented by the application.
1. Enter a Logical number for the position record you are creating
2. Click in the Camera field, and a list of available cameras that support Presets
will appear on the right of this window
3. Choose the desired camera by double-clicking on its ID number
4. Click in the CPreset field and type in the desired preset number
5. Click in the Scene field and enter a description of the camera view in that
position, if desired
You can add, edit, delete, or replicate Position IDs as needed using the four icons at the
bottom of this window.
61
Page 67
Configuration
System Controllers
A system controller is a device used by an operator to control specific components within
the NSS, such as: cameras, monitors, alarms, alarm outputs, etc. Controllers are
generally identified to an operator using their ID number, but can be viewed in MPU955
Admin Console by ID, IPA, EA, or Area.
Definition
1. Select the Controllers command from the Component menu
Add, edit, or delete controller records as necessary using the three icons at the bottom of
this window.
62
Page 68
Configuration
SYSTEM CONTROLLERS – Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a system controller is added, in order to
ID
identify one controller to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon adding
controllers, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one
component or sequence from another in row and column style. Since logical and local numbers are
not necessarily unique or consecutive, and the permission grids must be displayed as consecutive,
unique numbers, MPU955 Admin Console generates these ID numbers. 1 to 128.
Unique number identifying a Monitor Surveillance Area (MSA) comprised of an array of monitors
Area
and one or more keyboard controllers. 1 to 64.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor. The
use of areas is restricted to values of 1 to 64. Only use area “0” when no areas are needed within
the entire system.
Click the Area button on the main window to view all components defined in a specific area.
Priority
Boot File
Timeout
Model
This number assigns this controller an order of precedence. Applies only when operator priorities
are the same. The controller with the lower number priority takes over the part of the system it is
addressing.
If more than one controller with the same priority is operating at the same time, access is given and
held for the latest call to a function, in other words, on a last-come first-served basis. Alarm
priorities have precedence over operator priorities. 0 to 65,534.
The name of the file used by the Ethernet keyboard’s boot process. Use the default filename unless
instructed otherwise by qualified personnel. Alphanumeric, 12 characters. The file name IS case
sensitive.
Be sure to select WV-CU850 Controller type FIRST so that the default boot name will be filled in
automatically. This is the only system controller type that will require a boot name.
If the boot name field is filled in before WV-CU850 type is selected, the default boot name will not
be inserted.
Amount of time that must elapse after the user stops entering keystrokes, before the system logs off
the operator from this controller. (hr:min:sec) 00:00:00 to 11:59:59
The controller timeout works in conjunction with the operator timeout. The system will choose the
lowest timeout value of the two.
Entering a “0” into this field will cause the timer to never expire regardless of the operator timeout
value.
Drop-down and select the correct type of system controller. This will enable or disable fields that
are specific to each particular controller. CU350 or CU360 (RS485), CU850 (Ethernet), PFW100
[CU350] (RS485), PFW100 [CU850] (Ethernet), PFW850 (Ethernet), RS232 (serial), or ActiveX.
63
Page 69
Configuration
SYSTEM CONTROLLERS – Definition
Field Data
Unique Internet Protocol Address assigned by the system administrator. Dotted decimal, 15
IPA
characters. Example: 128.010.050.125. Each of the four groups of numbers with values between 0
and 255.
Depending on the model number chosen, the following will apply:
WV-CU350: If this controller is not connected to an RS485 Expander Unit, use the default IPA. If
this controller is connected to an RS485 Expander Unit, enter the IPA for the expander unit.
WV-CU360: If this controller is not connected to an RS485 Expander Unit, use the default IPA. If
this controller is connected to an RS485 Expander Unit, enter the IPA for the expander unit.
WV-CU850: A unique IPA is necessary within the scheme of the MCPU interface IPA.
PFW100 [CU350]: Same as the WV-CU350.
PFW100 [CU850]: Same as the WV-CU850.
PFW850: Enter the IPA of the desktop computer where the PFW850 is installed, making sure it is
within the scheme of the MCPU interface IPA.
RS-232: If this controller is not connected to an RS485 Expander Unit, use the default IPA. If this
controller is connected to an RS485 Expander Unit, enter the IPA for the expander unit.
ActiveX: Enter the IPA of the desktop computer that ActiveX is running from, making sure it is
within the scheme of the MCPU interface IPA.
Numeric address for an Ethernet controller. This field is only required if Model WV-CU850 is
EA
chosen. Dotted hexadecimal Example: 23.56.82.13.60.82 (Also known as MAC address.) Use all
zeroes if not using DHCP.
Numeric identifier of the port used by an RS-485 controller (CU350, CU360, and PFW100A) (port
Port
1-12) or RS232 controller (Port 1,2, or 3). Match the data port that this keyboard is connected and
use the proper IPA for the MCPU default or RS485 Expander Unit.
This port address will be unique within the IPA specified for the MCPU or RS485 Expander.
Location
A practical name that will identify where this controller can be found. Alphanumeric, 16
characters.
A name for the controller, easy to remember, and practical. Alphanumeric, 16 characters.
Name
Manufacturer’s serial number. Alphanumeric, 16 characters.
Ser.
Permissions
Modify or copy system controller permissions in the same manner described in the
Camera Permissions section, beginning on page 56.
The Cam Ctrl permission tab allows an administrator to permit or deny a system
controller the ability to control specific cameras. The Modes section of each of the
permissions tabs is described on page 13
Copying Cam Ctrl permissions to other system controllers will also copy Cam
View permissions to the specified controller.
Allowing a system controller to control a certain camera will automatically
allow the same controller to view the specified camera.
64
Page 70
Configuration
The permission grid’s dimensions are based on the maximum capacity for the
chosen CPU size, not on physically installed components already in the
database.
The Cam View permission tab allows an administrator to permit or deny a controller to
view specific cameras.
Copying Cam View permissions to other system controllers will also copy
Cam Ctrl permissions to the specified controllers.
Denying a system controller to view a certain camera will automatically deny
the same controller to control the specified camera.
The Monitor permission tab allows an administrator to permit or deny a controller’s
ability to seize a specific monitor.
A monitor ID, if unknown, can be determined by its area and local number,
by entering each value into the appropriate boxes, and then clicking the
“Search for Monitor by Area & Local” button.
The Group Seq (not currently supported) permission tab allows an administrator to
permit or deny a controller’s ability to control a group sequence.
If the group sequence ID is unknown, you can enter the area and local
numbers of the sequence in the appropriate boxes, and click the “Search
for Group Seq by Area & Local” button.
The Alarm permission tab allows an administrator to permit or deny a controller’s ability
to seize a specific alarm.
The Alarm I/O permission tabs allows an administrator to permit or deny a controller’s
ability to seize a specific IO port.
65
Page 71
Configuration
Alarm Input/Output
Alarm input and alarm output ports are used for alarm action purposes, and although each
has a specific function, both are configured within this section.
Each encoder supplies 8 ports – 4 are input ports, 4 are output ports. Because of this, 4
consecutive IDs must be configured with the same directional type - either input or output.
For example, if ID 1 is configured as an input port, then IDs 2-4 must be input ports as
well.
Then, port 5 through port 8 must be configured as output ports.
Although the system controller operator must control the I/O ports by logical number,
these ports are viewable within MPU955 Admin Console by both ID and logical port
numbers.
Definition
1. Select the I/O Ports command from the Controller menu
66
Page 72
Configuration
Add, Edit, Delete, or Replicate alarm I/O port records as needed using the four icons at
the bottom of this window. Deleting a port will delete the entire bank that port is part of.
A l a r m I/O PORTS – Definition
Field Data
ID
Logical
Type
Switch:
Digital / Analog
Bank and I/O
Dwell Time
Unique record ID assigned by MPU955 Admin Console as an I/O port is added, in order to identify the
port to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon adding I/O
ports, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one
component or sequence from another in row and column style. Since logical and local numbers are not
necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique
numbers, MPU955 Admin Console generates these ID numbers. 1 to 1,024.
Assigned by an NSS administrator, enabling operators to address this port. An operator will select alarm
I/O ports by logical number. 1 to 65,534.
Click on either Input or Output. Input Example: Fire exit door opening. Output Examples: Unlock/lock
a door. Alarm to firefighters. Call for police. Call for medical rescue.
Each type must be configured in groups of 8.
Note: Analog is only selectable in ASC960 Admin Console 4.0. Contact your Panasonic representative
for details.
Choose a Bank (which consist of 4 digital ports). The port numbers (I/O) are automatically assigned.
For each bank, 4 records are added.
Once a record is created, only Logical number and Dwell Time can be edited.
Deleting a port will delete the entire bank that port is part of.
Time available for a momentary output. Up to 59:59 (min:sec)
Dwell time will only be enabled for output type I/O circuits.
67
Page 73
Configuration
Permissions
Modify or copy I/O port permissions in the same manner described in the Camera
Permissions section, beginning on page 56.
The Controller permission tab allows an administrator to permit or deny a system
controller the ability to seize a specific I/O port. The Modes section of this tab is
described on page 13
The Other tab shows which Alarm ID numbers are using a particular Alarm I/O port.
The permission grid’s dimensions are based on the maximum capacity for
the chosen CPU size, not on physically installed components already in the
database.
68
Page 74
Configuration
Monitors
Monitors are generally viewed within MPU955 Admin Console by ID number, but can be
viewed by area\local number, since the user will operate the NSS by selecting a monitor
by local number within a specific area.
Area\local numbers are displayed in MPU955 Admin Console as one whole number. The
four right-most digits represent the local number and the left-most one or two digits will
represent the area. For example, 10034 represents area 1 and local number 34, or 251100
represents area 25 and local number 1100.
Definition
1. Select the Monitors command from the Components menu
Add, edit, delete, or replicate monitor records as needed using the four icons at the
bottom of this window.
69
Page 75
Configuration
When deleting or modifying a monitor, be sure to check the Other tab to find
references to other sections that the monitor will influence.
When changing the Monitor Surveillance Area (MSA) of a monitor, make
sure that any affected presets or alarm action target assignments are within the
same area.
Deleting a monitor will automatically delete the referenced
permissions, but will not change any other references, such as
sequences, presets, etc.
MONITORS – Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a monitor is added, in order to identify one
ID
programmed monitor to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon adding
monitors, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify one
component or sequence from another in row and column style. Since logical and local numbers are not
necessarily unique or consecutive, and the permission grids must be displayed as consecutive, unique
numbers, MPU955 Admin Console generates these ID numbers. 1 to 1,024.
Unique number identifying a Monitor Surveillance Area (MSA) comprised of an array of monitors and
Area
one or more keyboard controllers. 1 to 64.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
The use of areas is restricted to values of 1 to 64. Only use area “0” when no areas are needed within the
entire system.
Click the Area button on the main window to view all components defined in a specific area.
Unique number assigned by an NSS administrator, enabling operators to address this particular monitor
Local
within an area. 1 to 9,999.
Operators will address specific monitors by selecting the local number with an area.
Switch:
Digital / Analog
Location
Model
Note: Analog is only selectable in ASC960 Admin Console 4.0. Contact your Panasonic representative
for details.
Enter the video port number, which can be different from the ID number, if desired.
Ports
Practical name indicating where this monitor is located. Alphanumeric.
Monitor model number assigned by its manufacturer. Alphanumeric.
Monitor serial number assigned by its manufacturer. Alphanumeric.
Ser.
70
Page 76
Configuration
Replicating a Monitor Definition
1. Highlight a configured monitor and click the Replicate button
A confirmation message will appear asking “Are you sure you want to REPLICATE this
monitor within this Area?” and explaining the replication rules:
[1] Records will be generated according to ID.
[2] ID will be incremented to the next available value.
[3] Local #, Video Port will be incremented from a specified base value you assign.
[4] If a record already exists with a matching value for any of these unique fields, that
Target assignment will be skipped.
[5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel
Monitors can only be replicated within an area. If you wish to replicate
monitors in several areas, at least one monitor must be configured in each area.
3. Enter the number of monitors to create in the Target Size box
4. Enter the beginning base value of the local monitor number that you wish to
begin incrementing from
5. Click the green check mark to add the series of monitors, or click the red X
to cancel
After clicking the green check mark, a message will appear letting you know how many
records were actually generated, indicating if any records were skipped. See Note section
of page 55.
Monitors existing within the specified range will not be overwritten.
71
Page 77
Configuration
Permissions
Modify or Copy Monitor permissions in the same manner described in the Camera
Permissions section, beginning on page 56.
The Camera permission tab allows an administrator to permit or deny a monitor the
ability to display a specific camera.
The Controller permission tab allows an administrator to permit or deny a system
controller the ability to seize a specific monitor. The Modes section of this tab is
described on page 13
Other
The Other tab displays additional sections that a highlighted monitor will affect.
This section is informational only, and changes cannot be made to the Group Sequences
(not currently supported), Group Presets (not currently supported), or Targets the
specified monitor will affect. Changes must be made within the specific Group
Sequence/Preset windows, accessed from their respective main menu options.
72
Page 78
Configuration
Operators
Class Setup
An operator is one who accesses the system via a system controller, selects resources, and
controls selected system resources, such as cameras, monitors, sequences, etc.
Before an operator can be defined, an operator class needs to be created.
An operator class defines which functions an operator or groups of operators have
privileges to perform.
1. Select the Operators command from the Component menu, and then select
Class Setup
2. Enter an ID number and descriptive name for the class record you are
creating
73
Page 79
Configuration
3. Choose the privileges to grant the class by checking the boxes to the left of
the desired privileges
Be careful when assigning the CAM Lock privilege. When an
operator uses CAM Lock, every camera in the system is locked.
Other users can select cameras normally, but cannot control them.
Operators with the CAM Lock Override privilege can override locked
cameras on a camera-by-camera basis, as determined by priorities.
4. Click the green check mark to add the class of operators, or click the red X
to cancel
You can add, edit, delete, or replicate class IDs as needed using the four icons at the
bottom of this window.
The Other tab of the Operator Classes window can be used to view a list of the
operators that are assigned to the class selected.
Operator Class Privileges
Privilege Function
Permission
Override
Area Change
ALM Select
ALM Reset [ALL]
ALM Ack/Reset
ALM Arm/Dis
[ALL]
ALM Arm/Dis
Output Ports
CAM Select
CAM Pos
CAM Preset Prg
CAM Menu
On/Off
CAM Function
Cds
CAM Receiver
CAM Setup Data
CAM Lock
CAM Lock
Override
Tour Sequence
When selected, users can override partition permissions. Users in this operator class become super users.
This privilege is tied to the Area Change privilege – selecting one automatically selects the other.
When selected, users can access areas beyond their defined, current area. This privilege is tied to the
Area Change privilege – selecting one automatically selects the other.
When selected, users can select alarms.
When selected, users can reset all system alarms within the domain. This function should be reserved for
system administrators.
When selected, users can acknowledge and reset alarms.
When selected, users can arm or disarm all system alarms with one command operation. This function
should be reserved for system administrators.
When selected, users can arm and disarm alarms.
When selected, users can turn alarm digital ports on or off.
When selected, users can select cameras.
When selected, users can control camera preset positions.
When selected, users can program camera presets and store them in the cameras.
When selected, users can enable or disable the camera menu from user controllers.
When selected, users can control cameras through their function codes.
When selected, users can use camera receiver controls, such as aux on or off, or camera wiper on or off.
When selected, users can access camera setup data.
When selected, users can lock a camera.
When selected, users can override cameras locked by other users.
When selected, users can control and select tour sequences.
74
Page 80
Configuration
Operator Class Privileges
Privilege Function
SEQ Stop [ALL]
SEQ Controller
MON Select
MON Lock
OSD On/Off
Time & Date
On/Off
When selected, users can stop all tour and group sequences within the domain.
When selected, users can program tour and group sequence.
Prg
When selected, users can select monitors.
When selected, users can select more than one monitor at the same time
When selected, users can turn on screen display items on or off.
When selected, users can enable or disable time and date OSD display operations.
Operator Records Definition
Once a class has been created, you can then access the Operators menu to specify your
system’s operators, their priorities, and their permission to access system controllers.
1. Select the Operators command from the Component menu, and then select
Records
Add, edit, delete, or replicate operators, as needed, using the four icons at the bottom of
this window.
75
Page 81
The maximum number of operators that can be defined for the system is 512.
OPERATORS
Field Data
Operator ID
Password
Priority
Timeout
Operator logon identification. This ID is different from all other component IDs. An
administrator assigns it. It is not assigned automatically as is the case with other components.
This number does not need to be sequential. This will be used as the log-on ID assigned to
each operator. 1 to 65,534.
Operator password. After the operator has entered the logon ID to a system controller, this
numeric password must be entered to complete the logon process. 1 to 99,999.
Operator’s name, in any format. Alphanumeric, 20 characters.
Name
Choose the class this operator is to be added to from the classes available on the drop-down
Class
menu.
Sets precedence among operators. Alarm priority has precedence over the operator priority.
Operator priority has precedence over the system controller priority. The operator with the
lower number priority takes over the part of the system being addressed. If more than one user
with the same priority is operating at the same time, access is given according to the lowest
controller priority number. If both priorities are the same, access is given and held for the
latest call to a function, in other words, on a last-come first-served basis. 0 to 65,534.
Number of seconds that must elapse after the user stops entering keystrokes before the system
logs the operator off of this controller. Up to 11:59:59 (hr:min:sec).
The operator timeout works in conjunction with the controller timeout. The system will use
the lowest timeout value of the two.
Entering a “0” into this field will cause the timer to never expire regardless of the controller
timeout value.
Configuration
Class privileges granted for the selected class also appear on Definition tab of this
window, but cannot be changed. This section is for the administrator’s reference.
Changes to class privileges must be done through the Operator Classes window. See
page 73 for details.
76
Page 82
Configuration
Replicating an Operator Definition
1. Highlight a configured operator ID and click the Replicate Record
button.
A confirmation message will appear asking “Are you sure you want to REPLICATE this
Operator?” and explaining the replication rules:
[1] Records will be generated according to ID.
[2] ID numbers will incremented to the next available value.
[3] If a record already exists with a matching value for any of these unique fields, that
Target assignment will be skipped.
[4] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel
The copy source is the highlighted operator ID from which the subsequent operators will
be copied.
3. Enter the Target range of operator ID numbers, with the beginning number
in the START box, and the ending number in the END box
4. Click the green check mark to add the series of operators, or click the red X
to cancel
After clicking the green check mark, a message will appear letting you know how many
records were actually generated, indicating if any records were skipped. See Note section
of page 55.
► Operator IDs existing within the specified range will not
► The maximum number of operators that can be defined for the system is
512.
► The default password for replicated each operator is the same as the
replicated operator’s ID number. The default name for each replicated
operator is “Operator #”, where “#” is the operator’s ID number.
be overwritten.
77
Page 83
Configuration
Permissions
Modify or copy operator permissions in the same manner described in the Camera
Permissions section, beginning on page 56.
The Controller permission tab allows an administrator to permit or deny an operator the
ability to login to a specific controller.
As with the Alarms window tabs, the Modes tab of the Operators window will be
accessible only if Scheduled Modes have been selected. The Modes tab on the
Operators window allows an administrator to determine what modes are active for an
operator. By default, all four modes are active, even if all four have not yet been defined.
This tab will be grayed out and inaccessible (as seen above) unless Scheduled Modes
have been selected. See page 13 for full details on modes.
78
Page 84
Configuration
Automate
MPU955 Admin Console allows operators to automate certain tasks, via the Automate
menu on the main window.
A sequence is a pre-determined series of views on one or several monitors, with preconfigured dwell times between views.
Three different kinds of automated sequences are available so that frequently used
combinations of monitors and cameras can be displayed automatically; tour sequences,
group presets (not currently supported), and group sequences (not currently supported).
An event is a scheduled action that will be automatically initiated at the time defined by
an administrator.
79
Page 85
Configuration
Tour Sequences
A tour sequence is an automated sequence of steps that can be run on any monitor by first
activating the monitor, and then initiating the sequence. Each step in a tour consists of a
specific camera aimed at a preset position, and a dwell time of a certain duration.
The values entered in this window determine the sequence in which cameras are viewed
by a single monitor when a tour is invoked.
Although an operator will call sequences or presets by local number within a specific area,
an administrator can view these tours by ID or area\local numbers within MPU955
Admin Console.
Definition
1. Select the Tour Sequence command from the Automate menu
80
Page 86
Configuration
TOUR SEQUENCES- Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a tour sequence is added, in order
ID
to identify the programmed tour sequence to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon
adding tours, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to identify
one component or sequence from another in row and column style. Since logical and local
numbers are not necessarily unique or consecutive, and the permission grids must be displayed
as consecutive, unique numbers, MPU955 Admin Console generates these ID numbers. 1 to
256.
Unique number identifying a Monitor Surveillance Area (MSA) comprised of an array of
Area
monitors and one or more keyboard controllers.1 to 128.
Click the Area button on the main window to view all components defined in a specific area.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
The use of areas is restricted to values of 1 to 64. Only use area “0” when no areas are needed
within the entire system.
Unique number within a monitor surveillance area, assigned by the system administrator. 1 to
Local
9,999.
Practical name that is easy for an administrator to remember, in order to reference a certain
Name
tour sequence. Alphanumeric, 16 characters.
Camera
CPreset
AUX1 & AUX2
ID number for a camera, previously configured, to be displayed in a step when a tour sequence
is invoked. 1 to 8,192.
Number identifying a preset position of the camera specified.
0 to 64 (0 = no preset).
Amount of time that a monitor maintains a view. Up to 86,399 seconds (23 hours, 59 minutes,
Dwell
59 seconds).
Used to determine if an auxiliary function will take place during a sequence. An auxiliary
function would require additional hardware at the chosen camera – such as a switch. If
unavailable, leave both fields blank (for none or no function desired). If available, choose On,
Off, or On/Off (switches to the opposite state) as the function to perform during that step.
81
Page 87
Configuration
1. To add a tour sequence, click the green Add Tour button
The following panel will appear.
MPU955 Admin Console will automatically assign the next available ID.
2. Fill in an area and local number
Be aware that changing the area may affect other configured
components such as alarm target assignments.
3. Give the tour a descriptive name
4. Add a camera in the Sequence of Steps
Double-click on a camera ID in the list on the right. It will automatically insert that
camera number in step one. Double-clicking on another camera ID will automatically
insert that camera number into step 2, and so on.
5. Type a preset number associated with each specific camera in the CPreset
column
Enter a “0” to indicate no preset associated with that camera.
82
Page 88
Configuration
To enter the same value in several steps, highlight desired cells using the click
and drag method. Type in a value and press the enter key. All highlighted cells
will be filled with the typed value.
6. Type a dwell time in seconds for each step
7. Double-click on AUX1 or AUX2 to change its setting from none (blank), to
On, Off, or On/Off as desired, and if available
8. To add a step in the middle of a sequence, highlight a step and
click the Insert Step button
A blank row will appear before the highlighted step.
9. To delete a step, highlight a step and click the Delete Step button
The entire row will be deleted.
10. After adding all desired steps, click the green check mark to continue, or the
red X to cancel
Add, edit, delete, or replicate monitor tour sequences as needed.
83
Page 89
Configuration
Replicating a Tour Sequence Definition
1. Highlight a configured Tour Sequence ID and click the
Replicate Tour button
A confirmation message will appear asking “Are you sure you want to REPLICATE this
Tour within this Area?” and explaining the replication rules:
[1] Records will be generated according to ID.
[2] ID will be incremented to the next available value.
[3] Local # will be incremented from a specified base value you assign.
[4] If a record already exists with a matching value for any of these unique fields, that
Target assignment will be skipped.
[5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel
The copy source is the highlighted tour sequence ID from where the subsequent tours will
be copied.
3. Enter the number of tours to create in the Target Size box.
4. Enter the starting local ID number to begin incrementing from in the Base
Values box
5. Click the green check mark to add the series of tours, or click the red X to
cancel
After clicking the green check mark, a message will appear letting you know how many
records were actually generated, indicating if any records were skipped. See Note section
of page 55.
Tour Sequences existing within the specified range will not
84
be overwritten.
Page 90
Configuration
To modify the replicated Tour Sequences, use the Edit Tour button.
The Other tab on the Tour Sequences window shows the Alarms that the selected Tour
Sequence ID is associated with.
85
Page 91
Configuration
Group Presets (not currently supported)
A Group Preset carries its own ID, and is created from MPU955 Admin Console to
include a list of camera-monitor connections. An operator selecting a Group Preset is
able to display a preset series of camera views over several monitors at one time. Each
camera-monitor connection must also include a camera-preset position.
Group Presets must be carefully planned, keeping in mind that they may be used as
elements of Group Sequences. Keeping camera-monitor permissions in mind, configure
several Group Presets using the same sets of monitors to enable the Group Sequences to
run smoothly.
Definition
86
Page 92
Configuration
Add, edit, delete, and replicate Group Presets, as necessary, using the four buttons at the
bottom of this window.
GROUP PRESETS – Definition
Field Data
Unique record number identifying a single Group Preset assembling several camera-
ID
monitor pairs that an operator can view at one time. MPU955 Admin Console assigns this
ID as a Group Preset is added.
MPU955 Admin Console automatically generates this number in consecutive order. Upon
adding Group Presets, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to
identify one component or sequence from another in row and column style. Since logical
and local numbers are not necessarily unique or consecutive, and the permission grids must
be displayed as consecutive, unique numbers, MPU955 Admin Console generates these ID
numbers. 1 to 256.
Unique number identifying a Monitor Surveillance Area (MSA) comprised of an array of
Area
monitors and one or more keyboard controllers. 1 to 64.
Click the Area button on the main window to view all components defined in a specific area.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
The use of areas is restricted to values of 1 to 64. Only use area “0” when no areas are
needed within the entire system.
Unique number assigned by an NSS administrator, enabling operators to address this
Local
particular monitor within an area. 1 to 9,999.
Practical name to help an operator identify a Group Preset.
Name
Examples: FireX by flr. CashReg by flr. Alphanumeric, 16 characters.
Set of Views
Camera
CPreset
Monitor
Specify a set of camera (with preset position) and monitor pairs that will take place in a
single shot.
ID number for a camera, previously configured, to be displayed in a step when a monitor
tour is invoked. 1 to 8,192.
Number identifying a preset position of the camera specified.
0 to 64 (0 = no presets).
ID number for the monitor that will display the specified camera preset position. 1 to 1,024.
87
Page 93
Configuration
1. To add a group preset, click the green Add Preset button
The following panel will appear.
MPU955 Admin Console will automatically assign the next available ID.
2. Fill in the area and local number
3. Give the group preset a descriptive name
4. Add camera to monitor pairs to the Set of View section by clicking on the ID
numbers for each as needed
Double-click on a camera and a monitor from the lists on the right. It will automatically
insert that camera and monitor ID in step one. Double-clicking on another camera and
monitor will automatically insert that camera and monitor ID into step 2, and so on.
5. Type a preset number associated with a specific camera in the CPreset
column
Enter a “0” to indicate no preset associated with that camera.
To enter the same value in several steps, highlight desired cells using the click
and drag method. Type in a value and press the enter key. All highlighted cells
will be filled with the typed value.
88
Page 94
Configuration
6. To add a step in the middle of a sequence, highlight a step and
click the Insert View button
A blank row will appear before the highlighted step.
7. To delete a step, highlight a step and click the Delete View
button
The entire row will be deleted.
After adding all desired steps, click the green check mark to continue, or the red X to
cancel
Add, edit, delete, or replicate group presets as needed.
When changing the area of an existing Group Preset, notice that all of the preconfigured monitors are deleted. This prevents an administrator from
inadvertently having monitors of different areas in a single group preset.
89
Page 95
Configuration
Replicating a Group Preset Definition
1. Highlight a configured Group Preset ID and click the Replicate
Preset button
A confirmation message will appear asking “Are you sure you want to REPLICATE this
Preset within this Area?” and explaining the replication rules:
[1] Records will be generated according to ID.
[2] ID will be incremented to the next available value.
[3] Local # will be incremented from a specified base value you assign.
[4] If a record already exists with a matching value for any of these unique fields, that
Target assignment will be skipped.
[5] All other record values will be identical to the Source record.
2. Click Yes to continue or No to cancel.
The copy source is the highlighted Group Preset ID from where the subsequent Group
Presets will be copied.
3. Enter the number of Group Presets to create in the Target Size box
4. Enter the starting base value for the logical ID number to begin incrementing
from in the Base Values box
5. Click the green check mark to add the series of group presets, or click the
red X to cancel
After clicking the green check mark, a message will appear letting you know how many
records were actually generated, indicating if any records were skipped. See Note section
of page 55.
90
Page 96
Configuration
Group Presets existing within the specified range will not be overwritten.
6. To modify the replicated Group Presets, use the Edit Preset button
The Other tab on the Group Presets window displays the Group Sequences associated
with the selected Group Preset ID.
91
Page 97
Configuration
Group Sequences (not currently supported)
Programmed in MPU955 Admin Console, a Group Sequence combines several group
presets, separated by specific periods called dwells.
Although an operator will call tour sequences or presets by local number within a specific
area, an administrator can view these sequences by ID or area\local numbers within
MPU955 Admin Console.
Definition
92
Page 98
Configuration
Add, edit, delete, or replicate group sequences, as necessary, using the four buttons at the
bottom of this window.
GROUP SEQUENCES – Definition
Field Data
Unique record ID assigned by MPU955 Admin Console as a group sequence is added, in
ID
order to identify one programmed group of several group presets to the system.
MPU955 Admin Console automatically generates this number in consecutive order. Upon
adding group sequences, the system will automatically assign the next available number.
Component ID and sequence ID numbers are used primarily in the permission tabs to
identify one component or sequence from another in row and column style. Since logical
and local numbers are not necessarily unique or consecutive, and the permission grids must
be displayed as consecutive, unique numbers, MPU955 Admin Console generates these ID
numbers. 1 to 256.
Unique number identifying a Monitor Surveillance Area (MSA) comprised of an array of
Area
monitors and one or more system controllers. 1 to 64
Click the Area button on the main window to view all components defined in a specific area.
Inserting a “0” indicates area 0. This will disable the Area field in the OSD on the monitor.
The use of areas is restricted to values of 1 to 64. Only use area “0” when no areas are
needed within the entire system.
Unique numeric identifier for a single group sequence within one area. 1 to 9,999.
Local
Practical name to help an operator identify a group sequence.
Name
Examples: FireX all flrs, CashRs, all flrs. Alphanumeric, 16 characters.
Sequence of Steps
GrpPre
Monitors
Specify a single group sequence by entering a list of Group Presets (GrpPre) with Dwell
values. 1 to 128 steps
Table of group preset numbers (which are made up of a series of camera-monitor ID
connections and camera preset positions). 1 to 1,024.
Table of dwell time intervals in seconds, to be applied each of the group presets. Up to
Dwell
86,399 seconds (23 hours, 59 minutes, 59 seconds).
Displays a list of the monitor IDs associated with the selected group preset.
93
Page 99
Configuration
1. To add a Group Sequence, click the green Add Tour button
The following panel will appear.
2. Fill in the area and local number
3. Give the sequence a descriptive name
4. Add group preset numbers and dwell times in the Sequence of Steps section
Double-click on a group preset from the list on the right. It will automatically insert that
group preset ID in step one. Double-clicking on another group preset will automatically
insert that group preset ID into step 2, and so on.
Make sure that the same sets of monitors are used for each Group Preset in
order to ensure that the Group Sequence will run smoothly.
5. Type a dwell time in seconds for a specific group preset
94
Page 100
Configuration
To enter the same value in several steps, highlight desired cells using the click
and drag method. Type in a value and press the enter key. All highlighted cells
will be filled with the typed value.
6. To add a step in the middle of a sequence, highlight a step and
click the Insert Step button
A blank row will appear before the highlighted step.
7. To delete a step, highlight a step and click the Delete Step
button
The entire row will be deleted.
8. After adding all desired steps, click the green check mark to continue, or the
red X to cancel
Add, edit, or delete group sequences as needed.
95
Loading...