VistaLINK Manual 1v5
VistaLINK Manual 1v5
Table Of Contents
Table Of Contents.................................................................................................2
1 The VistaLINK™ System ...................................................................................3
1.1 Introduction to the VistaLINK ™ System.........................................................3
2.0 Getting Started With VistaLINK PRO ..............................................................5
3.0 Using The VistaLINK Pro ™ Software ..........................................................11
3.2 Working with the Navigation Tree .................................................................14
3.3 Auto Discovery and System Settings ............................................................16
3.4 Hardware Custom Descriptions ....................................................................21
3.5 Services ........................................................................................................23
3.6 Alarm Indication ............................................................................................27
3.7 Launches ..................................................................................................31
3.8 MVP DVL ......................................................................................................33
3.8.1 DVL Creation Dialog ..................................................................................33
3.9 Crosspoint Creation ......................................................................................37
4.0 Alarm Log Management................................................................................44
4.1 Alarm Operations ..........................................................................................46
4.2 Configuring Alarm Properties ........................................................................58
4.3 Email Notification System .............................................................................62
4.4 Audible Alert System.....................................................................................66
4.5 Alarm Log Management................................................................................68
4.6 Event Archiving (Database Administrator) ....................................................69
4.7 Alarm Forwarding..........................................................................................72
5.0 Configuration.................................................................................................73
5.2 Working With Configuration Windows...........................................................76
5.3 Saving and Loading Configurations ..............................................................79
6.0 Audit Logging ................................................................................................86
7.0 Remote Administration Features...................................................................89
8.0 User Administration.......................................................................................90
9.0 VistaLINK PRO Monitor (Grid) Client ............................................................93
9.3 Viewing Alarm Indications in the Monitoring (“Grid”) View .........................100
10 AutoConfig Overview ...................................................................................103
10.4 Schedule Calendar. ..................................................................................114
11 VistaLINK Graphics Client ...........................................................................115
11.1 View Node.................................................................................................115
11.2 Page Console ...........................................................................................116
11.3 Design Mode.............................................................................................120
11.4 View Links.................................................................................................129
11.5 Canvas Control .........................................................................................130
11.6 Dynamic Page Mode.................................................................................133
12.0 VistaLINK PRO Troubleshooting...............................................................135
Much has been written on the subject of maintaining video quality in a modern television
facility. But with often as many as a hundred or more television channels to monitor, we
must be concerned not only with signal quality, but also with the continuity of the video,
multiple audio channels, closed captioning, V-Chip parental guidance and other VBI data
associated with each channel. The task of monitoring so many channels often involves
employing a plethora of gadgets specifically designed to check each function. Even with
the best equipment, it is difficult to watch up to a hundred picture monitors and
impossible to monitor the levels and phases of hundreds of audio channels, closed
captions, XDS, and other data on every channel.
change messages inform the user of parameter setting changes. All changes are recorded
in VistaLINK™ PRO's audit trail tool in the full version. A configuration-only
VistaLINK™ PRO tool (VLPRO-C) is provided free with 7700FC VistaLINK™ Frame
Controllers for convenient card configuration.
2.4.1 If you are installing VistaLINK™ PRO Server and Client on the
same PC:
1. From the CD-ROM, select “Install VLPRO (Full/Demo Version)". This selection
will initiate the software installation procedure for VistaLINK™ PRO Server
• The Demo/Trial version of VistaLINK™ PRO will only allow 1 active general
client and 2 active PLUS client connections and only operate for 30 days from the
day of installation. To increase the amount of client connections allowed or to
remove the 30-day trial limitation a valid VistaLINKPro client license key must
be activated via the VistaLINKPRO server.
1. Copy the supplied client license key to the hard disk drive of the PC running the
VistaLINK PRO Server application.
2. From the VistaLINK Pro Server application select Help -> Activate License.
3. The Locate Activation File dialog will open. Browse to and select the license file
copied in step 1.
4. Click Open to activate the license file.
Note: To update or change existing client license information repeat the process outlined
above. New client license keys that activated will replace all existing license information.
The Logon window will appear shortly after you run the software. The purpose of this
window is to authenticate the user before access is given to the configuration and alarm
logs, as well as provide user audit tracking when an alarm is acknowledged.
Hardware
All hardware devices that are auto discovered or entered manually will appear under this
super-node. The Hardware super-node can contain any of the following hardware node
types:
• Frame nodes, denoted by the icons ( )
• Network Control Panel nodes, denoted by the icon -
• Module nodes, denoted by the icons -
• VIP modules, denoted by the icon -
Profiles
Profiles that have been created using the VistaLINK PRO AutoConfig Client will appear
under this Navigation Tree super-node.
• User created Alarm Profiles, denoted by the icon -
• User created Schedule Profiles, denoted by the icon -
Super-Node Groups
The Configurations, Services, and Launches super-nodes can all contain sub Groups to
aid in organizing the Navigation Tree nodes into logical groups. Super-node grouping can
be enabled or disabled on a per super-node basis by accessing the Tree Properties dialog.
Each of the Navigation Tree super-nodes can be displayed in the any of the following
state conditions (colors), representing the current alarm state of the hardware device.
The Navigation Tree Properties dialog box, allows the user to customize the super-nodes
that appear in the Navigation Tree. Select Tree -> Properties from the main menu to open
the Navigation Tree Properties dialog or right click the Navigation Tree super-node and
select -> Properties.
Desktop/Tree Link
When the Desktop/Tree Link option is active selections made in the Client working areas
will cause the tree selection focus to follow.
The Navigation Tree super-nodes can be expanded or collapsed at any time in order to
quickly view or hide sub nodes or hardware contained in the Navigation Tree.
1. In order to expand or collapse the entire Navigation Tree and all displayed super-
nodes select Tree -> Collapse All or Tree -> Expand All for the desired result.
The entire Navigation Tree panel can be displayed or hidden from view when it is not
required.
1. In order to toggle the Navigation Tree between display and hide modes, select Tree
-> Hide/Show Tree from the main menu. Hiding the Navigation Tree allows the
user to dedicate more display area for alarm views, configuration views, graphics
views or monitoring client grids.
(TOOLBAR ICON)
The toolbar button labeled "Hide/Show Tree" can also be used to toggle the
Navigation Tree on and off.
1. Select Tree -> Add/Update Frame. The Add/Update Frame dialog box will appear.
2. Enter the IP address of the frame that you want to manually add, and then select the
"OK" button. If the frame is already in the Hardware View you can select the IP
address from the drop-down list presented.
3. The Discovery Subsystem will now attempt to directly contact the specified frame.
• If the frame cannot be contacted it will not be added to the Navigation Tree's
Hardware super-node.
• If contact is established then the Discovery Subsystem will detect all products
in the frame and the frame will be added to the Navigation Tree's Hardware
super-node.
The Navigation Tree discovered hardware can be refreshed at any time by selecting Tree
-> Refresh from the main menu. Selecting this option will initiate an Auto Discovery
cycle disregarding the Discovery Interval setting.
All present frames will be updated with any newly added or removed modules. All newly
added or previously undiscovered hardware will be added to the Navigation Tree's
Hardware super-node.
(TOOLBAR ICON)
The toolbar button labeled "Refresh Network View" can also be used to
perform this action.
If products have been removed from a frame or a frame has been disconnected from your
network the Navigation Tree will show the frame and/or products, however, they will
appear disabled. If you know that the hardware does not exist on the network or has been
permanently removed you can force VistaLINK™ PRO to "clean up" the Navigation
Tree by removing the disabled hardware. To do this, select Tree -> Cleanup from the
main menu.
(TOOLBAR ICON)
The toolbar button labeled "Cleanup Network View" can also be used to perform
this action.
In order for VistaLINK™ PRO to monitor and control connected hardware it must first
perform a network auto discovery or have frame locations manually entered. The
software searches for VistaLINK™ (SNMP) enabled frames present on the network by
sending a broadcast message out on the network adapter and waiting for a response. If
multiple network cards are installed on the local machine then a broadcast message will
be sent for each adapter. When a valid frame response is received the frame will be
added to the Navigation Tree and the Discovery Subsystem will automatically begin
product detection for this frame, as indicated by the icon - .
When all products in the frame have been found, or the frame detection cycle has ended,
the frame node icon will change from the detection icon - to an idle frame icon - .
Detected products will be added as sub-nodes of the frame node. Any products that have
multiple video inputs, as in the 7761AVM-DC will be added with additional sub-nodes,
listed per-input.
Note: Once a device has been found and verified by the discovery system a reference for
that device will be added to the discovered devices file
(VistaLINKStandaloneSettings.xml.) After a device has been added to the discovered
devices file the VistaLINK™ PRO client will always try reconnecting to the device upon
startup even if the discovery system is disabled. (This is beneficial in that any hardware
that cannot be discovered by the Auto Discovery system only needs to be entered once
manually into the discovered devices file.)
Once the initial detection phase has completed VistaLINK™ PRO will enter into a
discovery interval cycle where it will awake at regular intervals, checking for new
VistaLINK™ enabled frames and verifying that all previous frames and products are still
responding across the network. If during this discovery cycle a new device is found, the
device will be added to the Navigation Tree. If a device can no longer be contacted the
icon for the device node will be changed to reflect the condition while leaving the device
in the Navigation Tree to alert the operator of the error condition.
The Auto Discovery subsystem can be configured for various detection cycle times and
discovery options.
To configure the automatic discovery settings select File -> Discovery Settings from the
main menu. The Discovery Settings dialog will open allowing the user to set options for
the discovery status panel and queue size, the discovery system itself and the unverified
hardware notification system.
When the automatic discovery system is enabled, it may be advantageous to the user to
view status information on what the discovery system has found and information on how
it is interacting with devices. When the discovery status panel is enabled a discovery
status bar will appear at the bottom of the client application window and will inform the
user when the auto discovery systems are active and provide details regarding the devices
that have been discovered. When the discovery status panel is visible, clicking the
Discovery Log button will open a log file containing all recent entries.
By default, VistaLINK™ PRO comes pre-configured with the Discovery System option
enabled. With this option enabled, the discovery subsystem will check the status of
frames and products and look for new frames and products on the network at preset
intervals. To change the Discovery System settings:
This setting will determine how often VistaLINK™ PRO will check the status of
equipment already present in the Navigation Tree as well as search for new VistaLINK
enabled equipment connected to the network. VistaLINK™ PRO keeps the network
connection open during the discovery cycle and closes the connection immediately before
the next discovery cycle. If you experience heavy load conditions, or delays in packet
responses on your network, you can increase this value to wait longer for equipment to
respond to the discovery process. To change the discovery cycle interval:
1. Locate the New Discovery period (secs) field directly below the Discovery
Enabled setting and enter the desired value (in seconds) into the field provided.
The Hardware Unverified notification option can be enabled to alert the user with an
alarm if the discovery system fails to contact a device that has already been added to the
Navigation Tree. If a discovered frame or module cannot be contacted its entry in the
Navigation Tree will turn light gray and a new pop-up dialog will be displayed to the user
with information regarding the frame or products that could not be contacted. The
system will continue to poll the lost product and if communication is re-established the
system will clear the entry from or remove the hardware unverified dialog. An audible
alert can also be played when the hardware unverified notification is present. The user
can select which sound to play by selecting the severity the sound is linked to (see
Audible Alerts)
General Settings can also be configured for each individual VistaLINK™ PRO client. To
set General Settings choose File -> General Settings from the main menu.
With this option enabled (checked) VistaLINK PRO Client applications will save any
configuration or alarm view windows that are open upon exiting and attempt to reopen
and position the saved windows when the client application is restarted. VistaLINK PRO
will not attempt to restore views that are specific to hardware that is no longer present in
the Navigation Tree.
When opening a configuration view for a product, VistaLINK PRO may not be able to
read an expected parameter from the module (this can be caused by outdated module
firmware, see the troubleshooting section for more detail). If VistaLINK PRO fails to
retrieve a configuration value, a "Configuration Advisory" message will pop-up to inform
the user. As these messages may interfere with the Configuration Auto-Refresh feature
the Advisory messages can be enabled or disabled on a per client basis by setting this
option.
When a user acknowledges an alarm an entry is inserted in the Audit Log recording the
client username and the alarms acknowledged. As acknowledging alarms is quite
common, this feature can be disabled if this level of tracking is not required. Disabling
this feature will considerable reduce the amount of entries and size of the Audit Log and
write operations to the database.
VistaLINK™ PRO allows the user to custom name each node in the Navigation Tree
(Super-nodes cannot be renamed). Once a custom name has been assigned, all future
references to the hardware device will use the custom description. Custom descriptions
will also be transferred as labels to any connected 9000NCP(2) Network Control Panels.
3. Enter the desired text and select the OK button to change the name or Cancel to
abort. The name change will take effect immediately. All remote VistaLINK™
PRO Clients running on the network will also update immediately displaying the
new hardware description.
Removing a custom name from a hardware device is very similar to naming a hardware
device. To remove a custom name:
Description dialog box will appear allowing you reset the device description.
3. Click the "Restore To Default" button. The name change will take effect
immediately. All remote VistaLINK™ PRO Clients running on the network will
also update immediately displaying the name change.
3.5 Services
The Service super-node is located within the Navigation Tree. It appears directly below
the Hardware super-node. Refer to "Adding or modifying a service” for additional
information on creating, editing and deleting services.
Services allow the user to logically group or isolate hardware from one or more frames to
create a logical relationship between the physical characteristics of your network and the
actual setup of your broadcast center. The hardware contained in a service view follows
the same "Rules of Broadcast" outlined in the Alarm Indication section. When an alarm
occurs on a hardware device contained in a service, the alarm condition is broadcasted up
to the Service, and subsequently the service super-node.
Note that there are exceptions to this rule when viewing alarms in the service view.
Consider where a frame has two products but only one of the products has been added to
the service view. If the product in the service view has a minor alarm condition, but the
product not contained in the service view has a critical condition, the frame in the service
will reflect a critical alarm condition. This is because the service view indicates the
actual state of the frame, not the perceived state of the frame in the service. In other
words, the frame contained in the service does not simply show the alarm status of only
the products contained in that service.
It is also possible to see an alarm condition on a frame in the service but not see any
alarm conditions on any of the products shown in the service. In this scenario the frame
has an alarm condition and you should check the Hardware super-node to determine
which product is causing the frame to show an alarm.
1. Ensure the Services super-node is visible by enabling though the Tree Properties
dialog.
2. Right click the Services super-node and select New -> Service.
3. The user will be prompted to enter a name for the new service. Once the service
has been named clicking the OK button will add the new service as a sub-node
under the Services super-node. The user is now ready to add hardware to the new
service.
VistaLINK PRO allows the user to add hardware to a Service using two different
methods.
1. In the Navigation Tree under the Hardware super-node, locate the hardware device
you wish to add to the newly created service.
2. While holding down the left mouse button, drag the selected hardware device over
the name of the service you wish to add it to and release the mouse button to add
it to the service.
1. In the Navigation Tree under the Hardware super-node, locate the hardware device
you wish to add to the newly created service.
2. Right click the hardware device and select the "Add to Existing Service..." option.
3. A dialog will appear listing all created Services allowing the user to select the
service the hardware device should be added to.
An alternate and faster way to create a service is to highlight all devices to be part of the
service in the Navigation Tree (hold the "Ctrl" key to select multiple items). After all
items are highlighted, right click the selected devices and choose the "Create service
from selection" option from the pop-up menu. The user will be prompted to enter a name
for the service, which will then be added to the Service Tree View list.
1. In the Navigation Tree, right click the service to be renamed and select the "rename
service" option.
2. The Rename Service dialog will open allowing the user to enter a new name for the
service, enter the new name and click "OK".
All local and remote clients will immediately update their Navigation Tree as well as any
Monitoring Client grid cells containing the service to display the new service name.
To remove a Service, right click the Service in the Navigation Tree and select the Delete
Service option.
To provide a second level of organization for Services in the Navigation Tree, VistaLINK
PRO provides the ability to further group user created services into Service Groups.
Grouping services into Service Groups provides a method for the user to logically
organizing created services according to their environment. Service Groups also provide
a better view of the Service Tree View fault indications for installations that utilize a
large list of services. The Service Group Mode feature can quickly be enabled or disabled
allowing the user to easily switch between a short Service Group list or a complete
Service list display in the Navigation Tree.
1. Ensure the Services super-node is visible by enabling though the Tree Properties
dialog. (The Groupings option must be enabled in order to create Service
Groups.)
2. Select one or more Services in the Navigation Tree (use the ctrl key to select
multiple services). Once the selection is complete, right click the selected services
and choose the Create Service Bundle from Selection... option.
3. Service Groups can also be created by, right clicking the Service super-node then
selecting New -> Service Group. Once the new Service group is created Services
can be added by dragging them to the new group while holding the left mouse
button down.
The Hardware and Service super-nodes in the Navigation Tree provide a means of
immediately alerting the operator when an alarm conditions exists on a hardware device
or in a service. Alarm events that have been setup to generate alerts (see Configuring
alarm properties) will color key the nodes presently in alarm and will use the “Rules of
Broadcast” to determine which alarm alerts the operator first.
Broadcast of alarms depends on the severity assignment of the alarm. If more than one
alarm condition is present for the same device the alarm with the higher severity
assignment will take priority over the lower severity assignment. When broadcasting
alerts back to the root (Hardware or Services) node, the highest product node severity
will take priority. When the higher severity alert has been acknowledged, the next
highest severity alert will be shown if one is present. See the below example for a
description of this process.
In the figure above, the products in slot 2 and 15 have alarm conditions. The product in slot 2 has a critical
alarm and the product in slot 15 has a minor alarm. Even though both products have alarms, the highest
severity alarm has been broadcasted to the frame node, and subsequently, the Hardware super-node. The
Rules of broadcast allow the operator to address the most critical alarms first.
Inhibiting Hardware:
When a device has been inhibited fault alarms generated by the device will not show any
indication in the Navigation Tree view and the fault will not be logged to the VistaLINK
PRO trap database. When a device is inhibited in VistaLINK™ PRO the device will still
be visible in the Network and Service views but will be displayed in a blue color where
the shade of blue will determine how the device has been inhibited (see “Inhibited/Sleep
Colors”).
Sleeping Hardware:
When a device has been put to sleep, fault alarms generated by the device will not show
any indication in the Navigation Tree view however the fault will be logged to the
VistaLINK PRO trap database. When a device is put to sleep in VistaLINK™ PRO the
device will still be visible in the Network and Service views but will be displayed in a
orange color where the shade of orange will determine how the device has been inhibited
(see “Inhibited/Sleep Colors”).
Inhibited/Sleep Colors
There are two types of colors displayed for both the Inhibit and Sleep features. Inhibited
hardware will be displayed in either dark or light blue. Sleeping hardware will be
displayed in dark or light orange.
• Direct Inhibit - Dark Blue - This status indicates that the device has been
directly inhibited by the Inhibit menu option.
• Direct Sleep - Dark Orange - This status indicates that the device has been
directly put to sleep by the sleep menu option.
• Inherited Inhibit - Light Blue - This status indicates that this “child” device is
being inhibited by the Direct Inhibit status of another higher (“parental”)
device. One of the many scenarios that this will occur is when a frame is
inhibited and all of the products within the frame inherit the inhibit status
from the frame.
• Inherited Sleep - Light Orange - This status indicates that this “child” device
is being put to sleep by the Direct sleep status of another higher
(“parental”) device. One of the many scenarios that this will occur is when
a frame is put to sleep and all of the products within the frame inherit the
The following are some examples of inhibit status on frames and/or products:
3.7 Launches
To create a new Launch, use one of the two methods described below depending on
whether it is an executable launch or an HTTP Launch.
Once new Launches have been created, they will appear in the Navigation Tree under the
Launches super-node. To use a Launch right click the Launch node and select -> Launch.
The right click menu will also allow you to Edit or Delete the selected Launch node.
To create a DVL, first right click on the DVL node( ) or group( ) to bring up the
popup menu. Select NEW -> then DVL. Once this is done a dialog will appear
as shown in Figure 1.
This dialog will show all required information for creation of a DVL.
This dialog uses drag and drop to facilitate ease of creation. Select a DVL server
from the tree, currently the only type is an MVP Server which appears in the tree
as the icon ( ). Drag this component into the dialog and drop it where the “Drag
Server Here” label appears. This server will then be contacted and all its
available Layouts and Displays will be populated in the dialog. The available
hardware will also be pulled from the server and shown in the Hardware Inputs
portion of the dialog based on the display that is selected. When the DVL Server
There are 3 main sections to the DVL Creation dialog, these include the Layout
Info; Hardware Inputs, and Preset Layout sections.
This section will determine which layout is to be displayed and which display it
will be placed on when activated. As described above the Layouts shown are
the available layouts to the MVP Server and as each one is selected from the list,
its layout will appear on the right in the Preset Layout area of the dialog. The
number and descriptions of the displays chooser comes from the number of
display cards that are available to the MVP. For example, if your MVP had a
PPV5 card in it, there would be 5 available displays.
Note : You might notice that when you change your Display that the hardware
changes in the Hardware Inputs section. This is due to the fact that each display
card can be hooked up to totally different hardware, as described in the
hwlinks.vssl file on the MVP Server itself, or setup in SCT.
This section is where the inputs for each of the windows are to be selected for
use.
The layout on the right shows each of the monitor components shown in the
layout selected. Each of the windows may be one of three colors. Red, which is
an unchangeable video source, Grey, which is a monitor that can be changed but
has no set video source, and Green, which is a changeable monitor that already
has a video source set on it. Samples of each are shown in Figures 3 and 4.
To assign a video source to a variable monitor, simply select an Input from one of
the pieces of hardware in the Hardware Inputs panel, and drag it into a Grey or
Green monitor context. If the video source can be placed there the monitor will
now turn green. If you wish to know what video sources are attributed to each
monitor, simply leave your mouse lingering over a video window and the tool tip
that pops up will display the video sources information.
Once all the video sources you wish to use have been assigned to the layout,
you can test run your layout on your MVP system by pressing the Run button at
the bottom. This will trigger the Sample DVL to be sent to the MVP Server and
that display will update to the corresponding settings. If you are satisfied with the
setup, give the DVL a name and then save the settings as a DVL using either the
Apply button (if you are planning on creating several layouts) or the OK button (if
you are planning on creating just one).
Once created the new DVL will appear under the specified name in the tree
under the DVL portion of the tree and can be executed simply by right clicking on
the DVL and selecting Launch.
This dialog uses drag and drop to facilitate ease of creation. Select a Router
from the tree, there exist several types of routers that can be used in this dialog.
For example each of the ptx ( )’s ports can be used as a router for control in a
Crosspoint.
The creation dialog consists mainly of four sections, the label field, and the
sections: Routers; Content, and Crosspoint Type. Each of these sections will
allow for a partial definition of a crosspoint.
On the left hand side of the dialog is a section that allows for the selection of the
router to be controlled. To select a router find it in the tree and simply click on it.
Components that cannot be used as routers will not affect the dialog. Once a
router has been selected the input and output areas in the Content section will be
filled in as in Figure 2.
The available inputs and outputs are populated through direct communication
with the router. If for any reason communication with the router is hindered, a
Content Section
A Crosspoint defined by input number and output number is only useful if all the
video inputs and outputs are on fixed numbers. However some routers allow for
inputs and outputs to be tracked dynamically by assigning inputs and outputs
labels. On occasion this labeling affects the ordering of the inputs and outputs
on a router. So if the label tracking option is selected, then the input/output
numbers are not used as the references for the Crosspoints, but the input/output
labels are used as in Figure 4. This feature is only available on some routers, if
the feature is enabled for a given router then the bottom section of the
dialog(Crosspoint Type) will be enabled, otherwise this feature will be disabled.
Once a router has been selected and the content specified, the new settings can
be saved into a Crosspoint. Specify a name for the Crosspoint in the Crosspoint
Field at the top of the dialog. Once this is done either press the apply button if
more then one Crosspoint is to be created, or press the OK button if only one is
to be created at this time.
Once the Crosspoint(s) have been created, they can be executed by right
clicking on the Crosspoint in the main tree and selecting launch in its popup
menu options.
Helpful Hints :
Some routers have thousands of inputs or outputs, which means that scrolling
through each of these lists may take a long time. To speed up this process the
Set fields for each of the input selection and output selection lists can be typed
into. When typing into these fields a search will be performed to select the
closest input or output to the description that has been typed. Once an input or
output has been found, press enter to ensure that the correct input or output will
be used.
To edit a Crosspoint simply take any Crosspoint from the main tree and drag it
into the description field at the top of the Crosspoint creation dialog. The existing
Crosspoint description will be displayed and modification of any field can be
performed. When finished with the changes simply press the Apply or OK
buttons. If you wish to discard your changes simply select the Cancel button.
• Log Alarms (Log Events) - This is the normal state of the logging system. This
setting will log and notify all clients of each alarm that is received.
• Buffer Alarms (Do Not Log) - This setting will put the logging system on hold and
buffer the alarms in memory. Alarms will not be logged to the database while in
this mode. If while in this mode alarms are received and the logging system is
switched to the normal mode, the alarms held in the buffer will be dumped to the
database and the logging and notification system will continue as usual.
• Hold (Ignore Events)- This setting will completely ignore all received alarms.
Alarms will not be buffered, or logged, thus any alarms generated will be ignored.
1. The Logging System settings can be accessed from either the VLPRO Server or
VLPRO client applications. To change the Logging System settings:
From the Server or Client application: Select Tools -> Logging.
2. In the Logging dialog box select the logging option of your choice and click the
OK button. The transaction will occur immediately and the Server logging
system will be adjusted to reflect the new setting.
The Alarm view window provides a means of viewing, acknowledging and correcting
alarms that have been logged to the alarm database. Alarms can be arranged by column
and filtered by acknowledged, corrected, severity settings etc.
Depending on the node selected in the Hardware or Service section of the Navigation
Tree, the Alarm view window will tailor the display to show only the information that is
pertinent for that device or service.
An alarm is defined as a SNMP trap event that has been generated by a hardware device.
Alarms can occur for various reasons and may be generated by conditions such as video
not present on the hardware device or the audio channel broadcasting over a pre-
determined level. The alarm or fault TRAP will be sent from the hardware device to the
VistaLINK PRO Server (trap destination) which will indicate fault states to the operator
by color keying nodes in the Navigation Tree.
VistaLINK™ PRO provides centralized alarm management. Incoming alarm events are
processed and logged by the VistaLINK™ PRO Server and then dispatched to all
VistaLINK™ PRO Clients connected to the server. When the VistaLINK™ PRO Client
receives a dispatched alarm event it first determines the alarm's severity setting and then
broadcasts the alarm to the Navigation Tree where the alarm is displayed to the operator.
• The status area at the top of the window displays the Navigation Tree node selected
for display, toolbar icons and the current filter settings.
• The alarm content area in the middle of the window displays the individual alarm
events for that node that are in the active alarm database.
• The “Notes” and “Details” panel at the bottom of the window shows extended
information about a selected alarm. See “Acknowledging and Correcting Alarms”
for more information.
Individual alarms are viewed using the Alarm View Window. An Alarm View Window can
be opened for any node on the tree in the Hardware or Service super-node sections. The
node that is selected by the user will determine what alarm information will be displayed
once the Alarm View Window is opened. Below is a description of the various types of
nodes that can be opened:
Note: There is no limit to the number of Alarm View Windows that can be open
simultaneously. Each time the user makes a new selection in the Navigation Tree
and launches the Alarm View a new Alarm View Window will open displaying
alarm information for the selected node. The "Window" menu found on the menu
bar provides options for configuring multiple open windows such as the ability to
cascade or tile the windows. This menu also provides the ability to minimize,
restore and close multiple windows simultaneously.
Hardware Super-node
Opening an alarm view from the Hardware super-node will display all alarm events in the
alarm database (alarm information for all hardware currently in the Navigation Tree)
including current alarm events as well as alarm events that have occurred under the
following conditions:
• Hardware that has generated alarms but are longer connected to the
network.
• Hardware that has generated alarms but have had their IP addresses
changed.
• This also includes notes from any of the below mentioned node types.
Frame Node
Opening this node will only display alarm events that have occurred for all products in
the selected frame.
• Includes alarm events for products that were previously in one slot but have
since been moved to a different slot. This also includes products that
were in the frame at one time but are no longer present in the frame.
Product Node
Opening an alarm view from this node will only display alarm events that have
occurred for the selected product.
Opening an alarm view from this node will only display alarm events that have
occurred for the selected video input.
To open an alarm view window use one of the following methods after selecting a node
in the Navigation Tree (node selected will determine alarms displayed as stated above)
Each alarm in the alarm view has two distinct operator states. The first state,
acknowledged, indicates that the operator has seen the alarm condition and has
dispatched a request to correct the problem. The second state, corrected, indicates that
the alarm condition has been corrected either by intervention of an engineer or the source
of the problem has restored itself. By utilizing these two alarm states it is possible to give
an accurate representation of the whole network system by keying alarm states in the
Hardware or Service views with various colors, and steady or flashing states.
The following table shows the acknowledged and corrected state and the visual indication
that will occur.
VistaLINK PRO will report all alarm information from enabled devices including alarm
conditions that have corrected themselves without user intervention (E.g. Momentary loss
of video). If the alarm generated to the system has corrected itself, VistaLINK PRO will
place a check in the corrected column check box for the particular alarm event and make
that column check box unavailable. The system makes this column unavailable in order
to indicate to the user that the alarm situation has returned to normal on its own as
opposed to an alarm entry that has been corrected by a user manually checking the
corrected column check box.
The Alarm view window provides a single click action to acknowledge all alarms
presently in the view. Alarms that are already acknowledged when this action is
performed will not be processed therefore the date and time stamps on those alarms will
not be updated.
To acknowledge all alarms in the view, click on the button located in the bottom-
right corner of the alarm view window
Each VistaLINK™ PRO Client installation can customize which headings are displayed
when the alarm view is opened for the various nodes of the Hardware and Service
sections of the Navigation Tree. To open the customization dialog, select Alarm ->
Configure Alarm Views.. The Configure Alarm Views dialog box will appear.
The Configure Alarm Views dialog is comprised of a View Category selector, Available
Fields area and the Show fields in this Order section. The view category selects the
corresponding node in the Hardware view that you want to customize the view for. The
available fields category contains fields (otherwise known as headers) that have not been
added to the view and the Show Fields in this Order category shows the fields that have
been added to the view. The top-to-bottom order in which the fields appear in the Show
Fields in this Order category determines the left-to-right order that the fields will appear
in the alarm view window, respectively.
The order of the fields can be changed by selecting one or more fields on the right and
selecting to move the fields up in the order or down in the order by clicking on the Up or
Down buttons.
Fields can be added or removed by selecting the field of choice then selecting the
available Add or Remove button.
Once complete, click on the "OK" button to save your changes. Any open alarm view
windows will not update to the new customizations until closed and re-opened.
Note: Some of the Available Fields options will be specific to certain hardware
modules. For example, the "Alarm GPI Label" which is populated by user defined
labels set on each individual 7700GPI module (if present). or the OV Trap Tag
field which is specific to a 3000OV MVP module.
Each alarm view window allows for the entry of additional custom note alarm entries.
These custom entries will appear in the Alarm View Window, however, will not be
associated with a particular system event. To enter a custom note click the Add
Custom Note button located in the toolbar of the currently displayed alarm view window.
The Add Custom Note dialog box will open allowing the operator to enter a description
for the custom note (displayed in the description column of the alarm view window), a
severity setting and any extended operator notes that should be included with this entry.
Click Save to add the Custom note to the alarm view window.
Normally when an alarm view is opened all alarm events for the selected node are shown.
This may not be the desired functionality. VistaLINK™ PRO provides an option to
display only alarms that match specified filter criteria. For example, the system can be set
to filter out any alarm events that have been previously acknowledged or corrected thus
only displaying the alarm events that have not been addressed.
In the event that new alarm are generated while a filter is enabled, the new events will be
displayed in the alarm view only if the event passes the filter criteria.
1. A Default Filter is established that will be applied to all alarm view windows
each time they are opened.
2. A Custom Filter is applied to an open alarm view window that will apply to
the alarms currently being displayed. However, when an alarm view window
with a Custom Filter is closed and then reopened the filter will be removed
and the display will return to the default view.
Default and Custom filters are both created using the Filter Options dialog. This dialog
allows the user the ability to establish a filter set that will limit which alarms are
displayed in an alarm view window.
The Filter Options dialog box presents individual filter options (per row) that can be
enabled or disabled in order to build the desired filter. Each filter option (row) has three
columns that make up the filter option parts. Each filter option can be enabled or
disabled as part of the final filter criteria by changing the Test Condition to any value
other than “Disable this filter”. When the Test Condition column has been changed for a
filter option, that option becomes active and is indicated active by displaying the rows
background color in yellow.
• Data Field: This is the field in the alarm view that will be checked when this filter
option is enabled.
• Test Condition: This drop down box is used to enable a filter option by selecting
the appropriate Test Condition for the Data Field (if set to “Disable this filter”, the
filter option specified on this row will not be part of the criteria for the filter being
created).
• Criteria: This sets what criteria the Test Condition should look for when checking
the Data Field.
Example: Changing the first Test Condition drop down box to “Is not” will establish a
filter that will only display alarms where the Acknowledged Status (Data Field) Is not
(Test Condition) Checked (Criteria) or simply, will only display alarms that are
unacknowledged.
The user can enable as many filter options (rows) as necessary, in order to build the
appropriate filter. When using more than one filter option the user has the ability to set
each additional option as an AND option, meaning the alarm must meet all filter
requirements (Option 1 AND Option 2), alternatively, additional options can be set as OR
options, meaning the alarm will be shown if it meets any of the filter options (Option 1
OR Option 2). After all filter option selections have been made, clicking the Apply Filter
button will activate the filter (Default or Custom depending on how the Filter Options
dialog was accessed).
The Clear and Clear All buttons can be used to reset filter options back to a disabled
state. Clear will reset only the selected row, while Clear All will reset all selected filter
options.
Once a filter has been created, it can be saved for future use or copied to other clients. To
save a created filter, click “Save Filter Set”. VistaLINK PRO will prompt for a name and
location to save the filter set to. Saved filters can be loaded back into the Filter Options
dialog by clicking “Load Filter Set” and then browsing to the saved filter and clicking
“Open”.
With this filter applied, the alarm view window will only display alarms if they have
neither been acknowledged nor corrected thus eliminating all alarms from the view that
have been fully addressed. To load the Unresolved Alarm filter click Load Filter Set in
the Filter Options dialog, browse to the VistaLINKProClient folder (C:\Program
Files\VistaLINKProClient by default) and select the “Filter_UnresolvedAlarms.xml” file.
This will load the default Unresolved Alarms filter into the Filter Options dialog enabling
the first two rows. (Ack Status Is not Checked OR Cor Status Is not Checked).
While an alarm view window is open it may be desirable to temporarily hold new alarms
from interrupting the display of existing alarms. In this case it is possible to suspend the
processing of alarm updates by clicking on the Suspend toolbar button in the top-right
corner of the alarm view window. The button will stay depressed and the alarm view will
display the button with a red background to indicate that the alarm view window is
currently suspended.
While in this mode, the alarm view window will not receive any new alarm events. The
alarm view will continue to update the status of any events in the view if the status
changes.
To resume receiving new alarms, click on the Suspend button once again. The button
will restore to its normal state and the alarm view will immediately catch up on any
alarms that have occurred during the suspended period.
This feature allows you to save (or export) the alarms in the alarm view window to an
external file. Any filter settings that are currently applied to the view will also be applied
to the save operation. Note that any customizations to the headings will not be inherited
by the save. All headings are saved when the current view is saved.
2. Select the desired location for the file and enter a filename in the file name
area. If no extension to the filename is specified a .txt extension will be
appended.
Follow the steps outlined in the “Saving to a new file” procedure above except specify
the filename of an alarm log file that already exists on your system. You will then be
prompted whether or not you wish to append to the end of this file. If you choose to
append, the alarm information will be appended to the end of the specified file, separating
existing information from new information with a single line header describing the date
and time the new append occurred.
The Alarm Severity Configuration dialog provides a means of custom tailoring each
alarm event to meet the requirements of your installation. The hardware devices
connected to your network generate alarm events, also known as “TRAPS”. These traps
are received by the VistaLINK™ PRO Server and stored in VistaLINK™ PRO's alarm
database. The alarm properties determine if, when and how VistaLINK™ PRO clients
are informed of these alarm events.
Upon installation, VistaLINK™ PRO comes configured with all alarms set to their
highest severity setting (critical). You should review these settings as soon as possible to
ensure that they are setup correctly for your broadcast center.
VistaLINK™ PRO provides five severity level options. The following is a list of
severities and their description:
• Critical - The highest level of severity that can be set for an alarm. This
severity setting should be used for alarm events that are critical in nature
and require immediate attention. All critical alarms will be shown in red.
• Major - This setting is of a lesser importance than the Critical alarm setting
above. This setting should be used for alarm events that are still
important in nature but can be looked at after all critical alarm events have
been acknowledged. All major alarms will be shown in orange.
• Minor - This setting is of a lesser importance than both the Critical and
Major alarm settings above. All minor alarms will be displayed in yellow.
• Warning - This setting is the lowest severity that can be assigned to an
alarm event and still generate an operator alert in the Device View. Use
this setting for alarms that are of lowest importance. All warning alarms
will be displayed in dark gray.
• None - This setting will cause the alarm event to be ignored. Alarms with
this setting can still be acknowledged but do not generate an operator
alert in the Device View. All alarms of this type will not have a color
associated to them.
1. Select Alarm -> Configure Alarms or right click a hardware device in the
Navigation Tree and select the Configure Alarms... option. The Alarm Severity
Configuration dialog box will appear displaying the User Label, Severity, Auto-
acknowledge, Email and Alarm Note settings for all "TRAPS" of the product type
selected. Severities other than "None" will be color-keyed to the severity setting.
2. When you have completed making changes select either the OK or Apply button.
Below is a list of the columns that can be modified and their meanings:
Severity
This setting determines the severity of the alarm event. When the event occurs
and is reported to the Clients the Navigation Tree indication and the Alarm View
Description column background color will match the severity color level set in
this dialog. For more information, see Alarm Indication.
Ack
If this option is checked, the alarm event will automatically be marked as
acknowledged at the time it is stored in the alarm database. Having an event
marked as acknowledged means that an operator has seen the alarm and knows
that there is a problem. See Acknowledging and correcting alarms for more
information about this setting.
Email
This setting will cause an email to be dispatched to a list of recipients describing
the alarm condition. (see Configuring the Email Alert System)
Alarm Notes
Alarm notes are additional pieces of information that can help the operator
diagnose a problem. These notes will be displayed in the Alarm Notes section of
the Alarm View for each alarm of this type that is logged by the system.
You can clear all changes you have made to a product by first ensuring the correct
product is selected in the product type drop-down and selecting the Set to Factory
Defaults button. A confirmation box will appear asking you to verify the operation. A
Set to Factory Defaults operation will reset all severity settings back to critical and clear
the auto acknowledge and email flags. The User Readable Label and Alarm Notes will
not be reset by this operation.
Programming each alarm event for every product can be a tedious task. To ease this
process you can perform bulk apply and clear operations. First, select the alarm events
that you want to modify. This can be done either by holding down the control (Ctrl) key
and highlighting each alarm event individually, or by selecting one alarm event, holding
down the shift key and selecting a second alarm event. All events that lie in between the
first and second selections will be highlighted.
Once you have selected the events, click the right mouse button while the mouse pointer
is over top of any one of the selected items. This will display a pop-up menu with the
following items:
• Enable Autoack
• Enable Email
• Set Severity - The Set Severity menu item has a sub-menu that will pop-up
when the mouse is hovered over the menu item text. The sub-menu
contains all severity option settings
• Clear Autoack
• Clear Email
• Clear Alarm notes
Selecting any one of these items will apply the operation to all selected alarm events the
same as if you had performed the action on one item.
VistaLINK™ PRO can be configured to dispatch email when an alarm event occurs if the
alarm "TRAP" event has the email option checked in the Configure Alarms dialog. The
Email system must be enabled and properly configured with valid SMTP mail server and
recipient addresses for email notification to function.
Select Alarm -> Configure Email. The Configure Email dialog box will appear
displaying options for the email system.
To enable or disable the email alert system, check or un-check the Enable Notification
option in this dialog.
Enter a valid mail server address in the Outgoing Mail Server text area. VistaLINK™
PRO will use this mail server for sending email notifications.
VistaLINK PRO will issue email notification packages to a valid SMTP mail server on
port 25. The mail server (e.g. Microsoft Exchange Server) must be set up to accept
unsolicited mail on port 25 for relay.
Note: As opening port 25 for any incoming unsolicited mail for relay would
be a security concern it is suggested that the SMTP mail server be setup to
only relay unsolicited mail when received from the IP address of the
VistaLINK PRO Server PC only.
New Alarms Only: Email notification will be sent only when a new alarm event is
received. Recipients will only be notified once for a particular new event according to
the Check and Send time interval.
New and Previous Uncorrected: Email notification will be sent for new alarm events as
well as existing events that have not been corrected. Existing alarm events that have not
been corrected will persist in the email alerts up to the Remove alarm if not corrected
after ____ email count
Note: Enter a number in Remove alarm if not corrected after _____ email option to
change the count for how many email alerts an existing uncorrected alarm will persist for,
before being removed.
Set the Check and send alarm email every _____ seconds to set the duration in seconds
for the VistaLINK™ PRO system to check for alarms and send email notifications
according to the Delivery Options
Select Alarm -> Configure Email. Change to the Recipients tab of the Configure Email
dialog.
To add a recipient address to the list, click Add, enter the email address and click OK.
To remove a recipient from the list highlight the address and click Remove.
Note: All addresses displayed in the Recipients list will receive email notifications from
VistaLINK™ PRO. Email notifications will only be sent for those alarms that have the
email notification option enabled in the Alarm Configuration setup.
Note: Audible alert settings are local to each VLPRO Client they are established on. Each
separate Client application can have its own audible alert settings programmed.
Select "Alarm" from the Client menu bar then select "Configure Sounds". This will
open the Audio Configuration dialog box allowing sounds (.wav files) to be linked to
each of the 9 severity states for an alarm (4 severities unacknowledged [flashing], 4
severities acknowledged [non flashing] and the OK state).
Click the browse button (...) next to the Audio File text box to enter a sound file to play
when an alarm with the selected severity is displayed in the Hardware/Service View. Set
the repeat count and playback volume for each sound
Note: To program the sound to repeat forever (intelligent mode only) until the alarm
condition is acknowledged, set the repeat count to the maximum setting until the count
value shows
When an alarm is displayed in the Navigation Tree, a corresponding sound that matches
the severity condition can be played (if programmed) up to the repeat count, or until
acknowledged, depending on how the sound is configured. To play sounds when alarms
are received:
1. Select Alarm -> Configure Sounds. This will open the Audio Configuration dialog
box allowing sounds (.wav files) to be linked to each of the 9 severity states for an
alarm (4 severities unacknowledged [flashing], 4 severities acknowledged [non
flashing] and the OK state).
2. Click the browse button (...) next to the Audio File text box to enter a sound file to
play when an alarm with the selected severity is displayed in the Navigation Tree.
Set the repeat count and playback volume for each sound
Note: To program the sound to repeat forever (intelligent mode only) until the alarm
condition is acknowledged, set the repeat count to the maximum setting until the count
value shows
The Enable intelligent alarm sound playback option can be enabled or disabled to switch
between the two available operating modes for audible alerts.
Upon installation, VistaLINK™ PRO comes pre-configured to log all alarms that are
received. If you are designing and setting up the infrastructure of your broadcast center
you may not want to be notified, or may not want to log any alarms that are being
generated during this process. In this scenario you can choose to hold the logging of
alarms or ignore alarms completely. Below are the possible logging states with
description:
• Log Alarms (Log Events) - This is the normal state of the logging system. This
setting will log and notify all clients of each alarm that is received.
• Buffer Alarms (Do Not Log) - This setting will put the logging system on hold and
buffer the alarms in memory. Alarms will not be logged to the database while in
this mode. If while in this mode alarms are received and the logging system is
switched to the normal mode, the alarms held in the buffer will be dumped to the
database and the logging and notification system will continue as usual.
• Hold (Ignore Events)- This setting will completely ignore all received alarms.
Alarms will not be buffered, or logged, thus any alarms generated will be ignored.
1. The Logging System settings can be accessed from either the VLPRO Server or
VLPRO client applications. To change the Logging System settings: From the
Server application: Select Tools -> Logging. From the Client application:
Select Tools -> Server Properties from the main menu.
2. In the Logging dialog box select the logging option of your choice and click the
OK button. The transaction will occur immediately and the Server logging
system will be adjusted to reflect the new setting.
1. Select Tools -> Logging in the VLPRO Server application or select Tools ->
Server Properties in the VLPRO Client application. Either of these two methods
will open the Logging dialog box .
2. Select the Database Administrator tab and check or un-check the Enable Database
Administrator option to enable or disable this feature.
1. Select Tools -> Logging in the VLPRO Server application or select Tools -> Server
Properties in the VLPRO Client application. Either of these two methods will
open the Logging dialog box .
2. Select the Database Administrator tab and change the Archive events that are older
than ___ day(s) duration.
3. Select the OK button. Your new duration will take effect the next time the
VistaLINK™ PRO Server queries the alarm database.
The Logging dialog also allows the user to select a different location to save the archived
alarm and audit logs to. Use the browse button to select a different path location.
Clicking the Run Database Administrator button found in the Logging / Database
Administrator dialog will immediately run the Database Administrator feature, bypassing
its regular schedule thus immediately archiving events according to the Archive events
that are older than duration.
1. Select Alarm -> Configure Alarm Forwarding which will open the Alarm
Forwarding Manager dialog.
2. Enter the following information; Host IP or where the SNMP TRAPs should be
forwarded to, Alias name for this forward rule and the Port the TRAPs will be
forwarded to (default 162.)
3. Click OK to begin forwarding TRAPs to this location.
5.0 Configuration
Using VistaLINK PRO a user can change individual module setups by accessing and
changing values in its associated Configuration View. Configuration Views provide
access to all controllable parameters available on a module similar to its card edge
controls or OSD menu system. Configurations can be saved and loaded into hardware
using the VistaLINK PRO system.
By taking advantage of VistaLINK PRO's Advanced System Configurations feature many
powerful and scalable system presets can be defined and used to quickly and accurately
change hardware setups.
Each Configuration View window provides a means of remotely viewing and setting the
various parameters within a product. The configuration view window is composed of a
series of tabs along the top of the window and a content area for each tab that contains the
various configuration options. The configuration options, also known as components, can
be broken down into six basic categories.
Described below are the six basic component categories and how each component
operates.
• Monitored Text Component - The text component is a descriptive label. This type
of component cannot be selected and does not represent a modifiable option.
• Group Box Component - The group box component, as it's name implies, is used to
• Radio Button Component - Radio button components are used to represent a choice
in configuration options. A single radio button represents each option. Only one
radio button item can be selected within the group of radio buttons present. To
change the value of a radio button component click on the radio button with the
left mouse button. Since at least one option must be selected within a group of
radio buttons, to remove the selection from one radio button you must select a
different radio button within that group.
Product Node
Opening this node will display the complete configuration view for the
product selected.
At any time you may refresh the configuration view that you have open. Performing this
option will synchronize your view with the information contained in the product. Any
configuration changes that have not been applied to the product will be overwritten after
executing a refresh.
To refresh the view, select Configuration -> Refresh or click the Refresh button
found on the top of each configuration view window.
VistaLINK™ PRO can automatically refresh an open configuration view. This is useful
if you want to monitor a parameter that changes frequently. To enable Automatic refresh
select Configuration -> Auto Refresh from the main menu. A check mark should appear
to the left of the menu item. To disable, select Auto Refresh again. The check mark
should disappear.
An alternate method would be to select the button on the toolbar. When Auto refresh
is enabled the toolbar button should appear green with a plus (+) sign in the bottom
right corner of the button. When disabled, the toolbar button should appear red with a
minus (-) sign in the bottom right corner of the button.
The refresh interval will depend on your network conditions. The refresh operation is a
continuous cycle meaning that the refresh will start with the first parameter, continue
until the last parameter has been refreshed and start from the beginning again.
Note: Automatic Refresh and Dynamic Apply cannot be enabled at the same time.
When changes are made to a product's configuration settings the changes need to be
applied. There are two methods of applying changes: Dynamically and Deferred.
Deferred apply refers to the process of making one or more changes and then manually
requesting for those changes to be sent to the product. Deferred apply also has the
advantage of being able to chose how the changes are to be applied. Applying changes
using this method can be performed using the toolbar buttons found at the top of each
Configuration View window. Please see below for a list of deferred options and their
descriptions:
• Apply Changes - applies only the configuration settings that have been
changed in the configuration view since the last apply operation. To apply
just the changed settings, select Configuration -> Apply Changes from the
main menu or click the Apply Changes toolbar button located at the
top of each Configuration View window .
• (Global) Apply To Same Product Types - applies only the configuration
settings that have been changed since the last apply operation to all
similar products. This is the same operation as the Apply item except that
the configuration settings will be applied to all like products. For example,
if the configuration is being applied for an AVM card, this operation would
apply the same settings to all AVM's currently in the Navigation View. To
apply changes to all similar products, select the button on the toolbar.
Note: Deferred apply is a verified process. This means that once the configuration has
been applied the same configuration will be read back from the product to verify that all
settings have indeed been set to the proper value.
Dynamic apply refers to the process of updating the product in real time as the
configuration settings are being made. Dynamic apply cannot be applied to all product
types as can Deferred apply. To enable dynamic apply, select Configuration -> Dynamic
Apply. A check mark should appear to the left of the menu option. To disable, select the
Dynamic Apply option again. The check mark should disappear if disabled.
An alternate method would be to select the button on the toolbar. When Dynamic
apply is enabled the toolbar button should appear green with a plus (+) sign in the
bottom right corner of the button. When disabled, the toolbar button should appear red
with a minus (-) sign in the bottom right corner of the button.
Note: When Dynamic apply is enabled, the Apply and Apply to Same Product types
buttons will be disabled. Dynamic Apply cannot be enabled if Auto Refresh is active.
VistaLINK™ PRO provides the ability to save the configuration for a product to an
external file or system file so that the saved configuration can be loaded at a later date
using the Load feature. This is useful if you want to create a backup of your product's
configuration settings or if you want to use the saved configuration file as a template and
rubber stamp the configuration settings to all like product types by loading the
configuration file into those products. It also provides a method to create custom scalable
presets for any single or group of hardware with resolution down to the individual
parameter level . Configurations can be stored in several different formats depending on
its intended use.
VistaLINK PRO's new System Configurations feature allows for scalable and
powerful system level changes as well as adding extended functionality to the
9000NCP(2) Network Control Panels. Advanced System and System Configurations
are the most common and powerful methods of saving configuration files. If you are
unsure what method to use choose one of these options.
When saving a Configuration file for a product(s) there are several different methods to
choose from depending on the intended use for the Configuration file. To save a
configuration file select the products in the Navigation Tree (hold the Ctrl key to select
multiple products) right click the selected product(s) and choose Save -> <save options
below>. System configuration files can also be saved/created by right clicking the
Configurations super-node and selecting New -> Configuration. Configurations files can
be saved using the following formats.
If Local is selected as the format for the configuration save, all parameters for the
product(s) selected will be stored to an external .xml file. This file can be copied to a disk
for transfer to a different location. The user will be prompted to enter a name and location
to store the configuration file to.
Advanced Local configurations files are also stored to an external .xml file however, the
user is presented with an extra dialog during the save operation to choose what individual
parameters from each product(s) will be saved as part of the configuration file. Advanced
configurations are advantageous as they allow the user to load settings on to a module(s)
for a specific parameter without effecting other non related parameters on the same
module(s). To build an Advanced Local configuration select the product(s) to be part of
the save option, right click and choose Save -> Advanced Local. The Advanced
Configuration Dialog will appear allowing you to create the configuration file.
1. Expand modules in the left-most tree to expose the individual parameters for each
module.
2. Select a parameter and while holding the left mouse button, drag it to the center
tree to add it to the configuration file..
3. Once a parameter has been added to the center tree view, double click the
parameter to set its value. Repeat steps 1-3 for all desired modules / parameters.
4. Provide a name and location to save the configuration file to and click Save.
System configurations are similar to Local in that all parameters for the product(s) are
saved, however, System configurations differ in that they are not stored to an external
file.
System configurations are stored in the VistaLINK PRO Server database and will appear
under the Configurations super-node in the Navigation Tree. System configurations
are advantageous in that they can be run directly from the Navigation Tree, they are
immediately available to all remote connected clients and they can be used with other
systems such as the 9000NCP Control Panels or placed on a View in the VistaLINK PRO
Graphics Client.
Advanced System configurations are stored under the Configurations super-node similar
to System configurations, however, they do not have to store all parameters for all
selected products. When building an Advanced System configuration the user is presented
with a dialog allowing them to choose the individual parameters that will be saved in the
configuration. The Advanced Configuration Save dialog works in the same manor as for
Advanced Local however the configuration file will be stored to the Navigation Tree's
Configurations super-node rather than an external .xml file.
1. Expand modules in the left-most tree to expose the individual parameters for each
module.
2. Select a parameter and while holding the left mouse button, drag it to the center
tree to add it to the configuration file.
3. Once a parameter has been added to the center tree view, double click the
parameter to set its value. Repeat steps 1-3 for all desired modules / parameters.
4. Provide a name and location to save the configuration file to and click Save.
VistaLINK™ PRO provides the ability to configure a product by loading settings from an
external file created by the Save feature. A configuration file may contain the
configuration settings for one product, multiple products, one parameter or multiple
parameters. Saved Local configurations can only be applied to the same product or
product multiples that they where saved from.
For example:
A save operation was executed on a frame with an AVM in Slot 4 and an AVM-DC in Slot
8. This configuration file can only be loaded into a frame that contains an AVM in slot 4
and an AVM-DC in slot 8.
If the saved Local configuration is limited to a specific module or sub parameter, that
saved configuration can be loaded into any similar product anywhere in the system.
2. Right click the selected nodes and choose Load -> Local. The Config Local Load
dialog box will appear. Select the saved configuration file and then select Open.
System configuration files can be loaded into modules in a similar manner to local files,
however, System configurations can also be launched directly from the Navigation Tree.
When initiated in this manner the System configuration will apply its settings strictly to
the exact hardware that the configuration was built from.
System configurations can also be added to VistaLINK PRO Graphics Views as well as
attached to a 9000NCP(2) preset button.
The Audit View window provides a means of viewing activity that has occurred in the
VistaLINK™ PRO system. Each audit entry is stamped with the user logon name, date
and time of the action, a description of the activity and a detailed breakdown of data that
was changed. The audit system also allows operators to add custom audit entries so that
operator issues can also be tracked through the audit system. For more information on
custom audit entries, see “Manually adding an Audit Entry”.
To view the Audit Log select Audit -> View Audit Log
The Audit system in VistaLINK™ PRO allows an operator to add a custom audit entry.
In addition to adding the audit entry into the audit database, the audit entry can be
addressed to a specific operator of the system, notifying that operator immediately if
logged on, or prompting the operator the next time he/she logs in to the VistaLINK™
PRO system. To add a custom audit entry:
1. Select Audit -> Add Audit Entry (the Audit Log must be visible). The audit entry
dialog will appear allowing you to enter an audit heading and detailed description.
If you selected to notify a user in the above operation the user will be immediately
notified of the audit entry if they are presently logged on to the VistaLINK™ PRO. If the
user is not logged on, he/she will be notified of the entry the next time he/she logs on to
the VistaLINK™ PRO.
This feature allows an administrator to purge (delete) all alarm events that are stored in
the alarm database. Once purged, the alarm events cannot be recovered. To remotely
clear the alarm database:
Select Tools -> Purge Alarm Database from the main menu.
You will be prompted to confirm your request to delete all alarm events. Select Delete to
proceed with the operation. A Remote Server Message will automatically be sent to all
running clients to inform them that the alarm database has been purged.
This feature allows an administrator to send a message to all running clients. This is
useful if you want to notify all users of an event that has occurred or is about to occur.
To send a remote server message:
You will be prompted to enter a message to send. Enter your desired message. Once
complete, select the Send button.
VistaLINK™ PRO provides audit tracking and restricts access to features by requiring
operators to Logon with an appropriate user account before gaining access to the
software. Each user that requires access to VistaLINK™ PRO should have a unique
logon. Doing so ensures that a user will only have access to areas defined by the account
privileges and allow for an audit trail indicating which users handled certain events.
1. In order to add or modify user accounts you must be logged on to VistaLINK PRO
with an account that has access to the Configure Users option. The Administrator
account has this ability by default.
2. User accounts can be added, edited or removed through the User Manager dialog.
Select Tools -> Configure Users from the main menu. The User Manager dialog
box will open displaying all current users accounts for the system.
3. If adding a new user, select the Add button. If modifying an existing user,
highlight the user in the list and select the Edit button. The Add New/Edit User
dialog box will open allowing configuration of the user account username,
password and privileges.
4. The user account details dialog contains the following fields that can be changed
when adding a new user or editing an existing user account: User name: The
name of the account being created/edited. This is the name the user will use to
logon to the VistaLINK PRO system. All audit log entries will reference this
accounts actions by the name entered in this field. Password: The password this
account will use to logon to the system with the appropriate account privileges.
Privilege Class: This dropdown menu will change the privilege authorization
screen to allow privileges to be assigned for any feature type in VistaLINK PRO.
The available options are: Common Privileges, Monitoring Privileges, Scheduling
Privileges and Server Privileges. Change this selection and then use the
Authorization area to select specific access rights. Note: the Privilege Class is
not a user account type, it simply changes what options are displayed in the
Authorization area. Authorization: This area presents all features for a Privilege
Class with an Authorization check box for each. Access per feature can be
enabled or disabled for the current account by checking or un-checking the
Authorization check box for the feature in selected.
5. After setting up a user account clicking OK will add the user (or update if editing)
to the User Manager list. Continue steps 2 - 3 for additional users or click the
OK button to close the User Manager and save changes. Click the Cancel button
to abort all changes.
Deleting a user will remove the ability for that user to Logon to the VistaLINK™ PRO
software. Deleting a user will not delete any actions the user has performed prior to the
delete. All audit entries, acknowledged or corrected alarms, etc. remain as-is with the
user's name attached to the operation. To delete a user:
1. Selecting Tools -> Configure Users from the main menu. The User Manager
dialog box will open displaying all current users of the system.
2. Highlight the user you wish to delete from the list of users and select the Remove
button. You will be prompted to confirm the action. Select Yes to delete the user
or No to abort the operation.
The Monitor “Grid” view provides the operator with a simplified monitoring tool that
emulates existing real or virtual monitor walls. Simply stated, given an actual or virtual
monitoring wall consisting of 16 displays in a 4x4 matrix, VistaLINK™ PRO will allow
the user to set-up the SNMP monitoring GUI in a similar pattern, which is also
configurable should the number of displays change. This view also allows the user to set
the same UMD names as currently displayed by the monitors. Font size, color and type
allow the display to be customized for the application.
VistaLINK™ PRO provides an easy to use interface for adding a grid to the Monitor
Client for Service Monitoring
1. Select Grid -> Add -> Grid on the main menu or click the Add Grid button on
the toolbar. The Add Grid properties window will open allowing the user to
establish the parameters for the new grid.
2. Enter a name for the new grid in the Grid Name text box. This name will be
displayed along the bottom of the grid display window indicating the currently
active grid view.
3. Enter the number of cells the grid should contain by supplying the appropriate row
and column values.
4. Check the “Make new grid active view” to set the new grid to be the default grid
shown in the grid display area.
5. Uncheck the “Use Default Font and Colors” check box in order to manually
configure the font type, font size, and font colour and background colors the grid
will use for the Info and Service cells.
6. Click OK to accept the settings and create the new grid view.
To edit an existing grid view, ensure the grid is currently active by clicking its
corresponding select button and choose Grid -> Properties from the main menu or click
the Properties button on the toolbar.
Right clicking a cell in an existing grid will open a pop-up menu with options to modify
the existing grid or the properties of the clicked cell.
• The grid right click menu provides the user with quick access to add or remove
services, labels, rows and/or columns from an existing grid or grid cell.
• The Cell Properties option on the right click menu allows the user to change the
color and font attributes for individual grid cells (will affect the cell clicked on)
When creating a new grid the Monitoring Client will use the default grid properties to
establish the initial grid size, font type, font size, font color and background color of the
new grid. To change the default grid properties select "Grid" from the main menu then
select "Default Properties". Change the settings to establish a new default grid profile
and click OK to activate. Clicking the "Restore Defaults" button in this window will
return the Grid Defaults to the values displayed when the dialog was opened.
To delete an existing Grid select Grid -> Remove -> Grid from the main menu or click
the Remove Grid button on the toolbar. Select the grid to be deleted in the drop
down menu and click OK to remove the selected grid.
To add a service to a grid view, ensure the target grid is displayed in the active grid
display area. Click Grid -> Add -> Service from the main menu or click the Add
Service button on the toolbar. Choose the service to add from the Select Service drop
down menu, set the Row and Col values to the coordinates of the target cell and click
OK. The service will appear in the grid at the cell coordinates specified as a filled cell
location using the colors set in the grid properties.
As of VistaLINK PRO version 7.x.x, services can now be placed into grid cells by
holding the left mouse button and dragging the service from the Navigation Tree
to the desired grid location. Release the left mouse button to drop the service into
place on the grid.
Custom labels can be added to a grid in order to provide organization and a more detailed
grid view for operator use. A custom label can be added to a grid cell by selecting Grid -
> Add -> Label from the main menu or by clicking the Add Label button on the
client toolbar. Enter the text to use for the label in the Enter label text box as well as the
Row and Col coordinates to select which grid cell the label will appear in.
• An alternative and faster method for adding labels is to right click a cell
displayed in the active grid area and select Add Label. This option will
automatically set the Row and Col values in the Add Label window to the
cell that was clicked on.
To delete an existing grid label select Grid -> Remove -> Label from the main menu or
click the Remove Label button on the toolbar. Select the label to remove from the
drop down menu and click OK to remove the selected label.
• An alternative method for removing grid labels is to right click a grid cell in
the active grid display area containing a label and select Remove Label.
This will automatically set the Remove Label Window to the grid cell
clicked on. Click OK to remove the selected label.
After creating a new grid view, its name will be displayed in a button along the bottom of
the grid display area. If the “Make new grid active view” box was checked during grid
setup, the new grid view will be the currently active grid displayed in the grid display
area. If multiple grid views have been established a user can switch between the grid
views by clicking its corresponding named button along the bottom of the grid display
area.
In order to easily recognize grid locations, Grid Headers can be toggled on and off for the
grid display area. To activate the Grid Headers select "Grid" from the main menu and
check the "Grid Headers" option. With Grid Headers activated an additional row and
column will appear along the top and left edge of the grid, containing numbers
corresponding to the cell coordinates.
The Dynamic Grid option can be enabled to maximize the use of the active grid display
area. With Dynamic Grid enabled, the currently active grid view will be dynamically
maximized to use the entire display area. To enable Dynamic Grid select "Grid" from the
menu bar then check the "Dynamic Grid" option or click the Toggle Grid View
toolbar button.
In order to further maximize the size of the active grid display the Navigation Tree can be
toggled on and off to allow the active grid to use the entire Client window area. To hide
the Navigation Tree, select Tree from the main menu bar then select the Hide/Show
Tree... option or click the Hide/Show Tree... toolbar button.
When a service in a grid view contains an alarm condition the operator will be visually
notified with either flashing text or a flashing background in the alarm severity color.
Left clicking the cell with a service will open the detailed Alarm View Window for that
service. The Alarm view window provides a means of viewing, acknowledging and
correcting alarms that have been logged to the alarm database. Alarms can be arranged
by column and filtered by acknowledged, corrected or severity settings. Monitoring
Client alarm view window operations are consistent with the standard client as outlined
in the “About the Alarm View” section.
• Clicking the Alarm View button on the toolbar will open the split pane and
display the alarm view for the item that is currently highlighted in the service tree
view.
When an alarm view window is opened for a service a sliding panel will expand to show
the alarm view window to the operator. This sliding panel can be configured to split
horizontally or vertically. To set how the sliding panel operates select "Grid" from the
menu bar then "Grid/Alarm Split" and check either "Split Horizontal" or "Split Vertical".
• Left clicking more than one service cell will open multiple alarm view
windows in the split pane, allowing operators to view multiple service
alarm views at one time. If all alarm view windows are closed the sliding
pane will collapse allowing the grid display to use the maximum viewable
area once again.
After a grid has been setup and services to monitor have been added to grid locations the
Monitoring Client is ready to monitor alarms on the particular services included in the
grids. When an alarm condition occurs for a product included in a service, its
corresponding grid location will flash either the text or background of the cell with the
alarm condition color, according to the “Rules of Broadcast” outlined in “Alarm
Indication”.
When an alarm occurs for a particular grid location the cell in that location will alert the
operator by either flashing the cell’s text color or background color according to the
Alarm Indicator Selection. To change which method the grid display will use to indicate
alarm conditions select "Grid" from the menu bar then select "Indicator Select" and check
either the "Flashing Text" or "Flashing Background" option.
10 AutoConfig Overview
The Autoconfig Client presents a new node in the Navigation Tree. This node
holds all automation configurations and may be shown on other VistaLINK PRO
clients. This node is called ‘Profiles’ and is noted by the following icon. If
this node is not available on other VistaLINK clients or the AutoConfig client,
check the Navigation Tree properties to see if it’s enabled (Tree > Properties).
Currently the Profiles node does not support groupings like other nodes found in
the Navigation Tree.
Profiles Type
There are two types of profiles that can be created. Each has distinct capabilities
and configuration views. Also they are represented in the profiles node with
different node icons.
The alarm profiles are represented by . These profiles are created and
executed based on alarms sent to the VistaLINK server and in return what
configuration(s) to run. An example of a alarm profile would be to run a stored
configuration that might heal an error that is sent from a device.
The scheduled profiles are represented by . These profiles are created and
executed on a specified time or re-occurring time to launch configuration(s). An
example of a scheduled based profile would be to change a multi-viewer layout
or disabling of alarms when a different circuit is being used in the facility.
Before creating any automation setups ensure that there are configurations
available underneath the ‘Configurations’ node in the tree. The key to the
Autoconfig is to schedule when these configuration scripts must run. Use the
appropriate functions from either the AutoConfig client or other VistaLINK clients
that support configurations to populate the ‘Configurations’ node.
To create an alarm profiles
(1) Select the profile node from the Navigation tree using the right-click
mouse button. A menu option will appear called ‘New’.
(2) From the ‘New’ menu, the menu can be further expanded to ‘Alarm Profile’
and ‘Sched Profile’. Select the ‘Alarm Profile’ to open its config view.
The following steps will demonstrate how to create a successful alarm profile with
descriptions in each of the steps.
Step 1.
Step 2.
The next step is to select which cards this configuration needs to apply too.
There is no limit to the amount of hardware this configuration can run against.
The hardware tree on the left gets populated with what hardware is compatible
for the desired configuration. The hardware tree will also only show from what’s
available in the Navigation Tree. Cards can be dragged from the left pane to the
right pane to denote which cards the configuration should run against. The arrow
buttons at the bottom may be used to move cards back and forth between the
panes.
Step 4.
The bottom left two panes are used to select which of the devices traps will be
used to execute the configuration. The hardware tree on the left will be
populated with the same contents in the Navigation Tree. You can use drag and
drop to move devices from the left pan to the right pan. There is no limit on the
amount of devices that can be listed in the right pane. The arrow buttons below
can also facilitate moving the devices from the two panes.
Step 5.
Once the selected hardware that will trigger this profile has been selected than
selecting the specific alarm can be made. Selecting the hardware from the
middle bottom pane will present a list of alarms in the right pane. Use the check
boxes to make the selection for which traps would have to be sent in order for the
profile to execute. The ‘select’ column denotes the error traps. The ‘Cor’ column
is to denote the correcting trap for that error trap. To utilize the ‘cor’ column, the
companion error trap must be selected from the ‘select’ column. Multiple alarms
or alarms from different cards can be combined to an ‘OR’ logic to have the
profile executed. Currently, a ‘AND’ logic is not supported.
Step 6
The alarm profile can also execute not only just configurations but it can execute
the MVP DVLs created in VistaLINK. Select the DVL tab by the
Configurations tab to select DVLs from the list. A Configuration and a DVL
can be ready for execution in a single alarm profile.
(1) Select the profile node from the Navigation tree using the right-click
mouse button. A menu option will appear called ‘New’.
(2) From the ‘New’ menu, the menu can be further expanded to ‘Alarm Profile’
and ‘Sched Profile’. Select the ‘Sched Profile’ to open its config view.
The following steps will demonstrate how to create a successful scheduled profile
with descriptions in each of the steps.
Step 1.
Step 2.
The first step is to select the configuration that needs to be configured for. This
step is exactly the same as when choosing a configuration for a alarm profile .
Once the configuration is selected, details about the configuration can be viewed
in the panel below the tree.
Step 3.
Hardware will than be populated in the middle tree for what the configuration that
was selected supports. Select hardware elements and either drag’n drop into the
tree on the right, or use the < > arrow buttons to move them back and forth.
Step 4.
Once the configurations or DVL adjustments have been made than the proper schedule
can than be created. The ‘Calendar’ control section specifies the frequency of this
schedule profile. Selections can be made on a daily, weekly or monthly basis. Also a
profile can be made to run just once on a specific time. Options to enable notifications
before starting and on completion are available to alert other VistaLINK clients about the
upcoming schedule change. The ‘Schedule’ control selection is used to control the
duration the scheduled alarm should be active and working for. The ‘Schedule’ control
section is also needed for one time scheduled alarm profiles.
Step 5.
The scheduler system can be paused and played on demand. By default the
scheduler system is turned on and will run schedule profiles created when the
time criteria is met. The icon that denotes that the system is running looks like
the following . If the icon is set to this than the scheduler has been
forcefully stopped and will not run scheduled profiles. To toggle this mode, select
the icon from the tool bar at the top of the program.
The alarm system can also be stopped or started by clicking its icon on the top
tool bar of the program. The icon denotes that the alarm system is running
and able to execute profiles based on alarms that are propagated to the
AutoConfig client. The icon denotes that the system has been forcefully
stopped and no alarm profiles will run.
Active Profiles
Profiles Log
The following icon will be shown in the navigation tree when Views are
enabled in the Tree properties.
To access the creation and deletion of views a user can use 2 menu systems.
The ‘view’ menu at the top of the program can facilitate the view management.
A right click menu system is also available to work at the navigation tree. The
menu’s provide the ability to create and delete views. Group creation and
deletion are also available through the same menu system
To create views select Views from the navigation tree using the right click mouse
button or from the Views menu at the top. Using the mouse to expand a new
menu from New in the right click menu and select View. The below dialog shows
were to customize the view. Enter a name in the View Name field and select the
browse button to choose a graphical background for the view. Click OK when
fished.
Click the Open Page Console button to expand the page console tools.
If for some reason at this point you do not see the Page Console change the
graphics display mode using either of the following icons in the Graphics
system.
When the Page Console is open 4 tools will be provided for managing
This icon allows the addition of pages. A dialog will pop to allow the user
to provide a mandatory name for the page.
Page names can have the same name as views but two pages cannot
have the same name.
This icon facilitates the removal of pages. Pages can be select and
removed using this button. If no pages are selected a dialog with a list of
available pages for removal will appear.
The Page Console has the functionality of not displaying all the available
pages on the system. This icon can be used to hide certain pages from
certain VLPRO Graphics installations.
Pages that have been set to hide can be available using this icon. A list
will be provided of the hidden pages once this button is clicked.
Pages created in the Page Console will appear like the above. This example
only shows two pages that have been created, Page 1 and Page 2. A listing of
created pages is only available when the Page Console is set to open. Also
make sure the graphics display mode is set correctly by clicking the following
icons to see the list of pages.
Pages can be opened further for adding views. To open pages double click the
page from the Page Console. When a page is opened the page console will
close and the ‘Active Page:’ field will show the current opened page. Only one
page can be opened at a time during this time. Below shows the Page Console
status when a page is opened.
When a page is first created the page will contain no views. Views created
earlier can now be put onto the newly created pages for viewing. An opened
page can display two body fields. The top body labeled ‘View Holder’ shows a
thumbnail image for all the views on the page. The bottom body ‘View Picture’
shows a select view as a whole.
By default an opened page will look like this when the split mode is set.
View
Holder
View
Picture
To open up another page click the ‘Open Page Console’ from the Page Console
to get a listing of available pages to be opened.
To add any created views from the Navigation Tree ‘Views’ super node, select a
view and drag and drop it with the mouse into the ‘View Holder’ body of an
opened page.
The above image shows two views, ‘View 1’ and ‘view 2’ on Page 1. Currently
View1 is selected for viewing. If ‘view 2’ was selected, the bottom body will show
the background of ‘view 2’.
The VistaLINK PRO Graphics can be adjusted to different display modes the list
of views on pages and to view the View’s canvas. Below describes the 3 types
of panel modes. These buttons are always located in the middle location on the
tool bar
Split mode sets the application to display the page console at the top and
display a selected view canvas at the bottom. This mode also allows the
user to adjust how much of the page console is shown and show much of
the view’s canvas is shown.
This mode sets the application to use the whole panel for the page
console. Lists of pages are only shown or a list of views (thumbnail
images of views) is shown when opening a page.
This mode shows the canvas in full and hides the page console
completely. The full view mode is mostly desirable when exposing your
Design Mode is used to bring the application into a mode to edit the views.
Editing the views involve many tasks that are describe throughout the manual.
Views can include all elements from the navigation tree. Only in design mode a
user can change the way the view looks or what is on the view. When the
application is out of design mode the elements on the view operate the same as
they would from the navigation tree. The view becomes this static picture of
whatever vector arts or custom icons that was created on the view. The Design
Mode control is seldom delegated to all operators and is heavily used by the
graphics developer and administrator.
To toggle the application to in and out of Design Mode the follow icon is always
available in the toolbar of the application. . A user can see the application
distinctively move into design mode because the view’s canvas opens up in full
and vector arts controls appear immediately underneath the tool bar. Below is a
screenshot to show a view in design mode.
The vector art tools give the user the ability to create vector art designs through
the VistaLINK PRO Graphics applications. These tools are available so the
application can assist in labeling, line drawings, colored boxes and circles. To
create vector arts in your graphics view select one of the vector arts and double
click in the graphics view to draw the vector. 7 Vectors are available for use with
distinct characteristics they are listed below.
To manipulate the vector arts in the graphics view select one of the vectors
points to resize it. Each vector art as it’s own properties control for color and line
change. Certain vector arts have distinct properties like the Text art. To access
the properties control of a vector art, select one of its points using the right click
mouse button and click ‘Properties’.
The VistaLINK PRO Graphics integrates everything from the navigation tree into
the graphics system. Elements from the Navigation Tree can be placed into
graphics views using drag’n’drop. All hardware elements, services, saved
configurations and etc can be carried over and be placed strategically into the
graphics view to best fit the operational needs. Elements dropped into the
graphics view will function the same as they do in the
Navigation Tree. Alarm severities will be available in the graphics view for hardware and
service elements to give the graphics view dynamics in alarm monitoring setups. Below is
a sample picture of the majority of the Navigation Tree elements placed into the graphics
view.
The above picture demonstrates that VistaLINK PRO Thumbnail images can be
embedded into the graphics view for a fully converged environment of
VistaLINK’s tasks. To modify the graphics view of any sort, the program will
need to be in Design Mode. As each element gets added to the graphics view
through Drag’n’Drop, the view node in the Views super node in the navigation
tree gets updated with to show what elements are added to it. Existing elements
may be added multiple times for increase flexibility designs.
To start working with the Control Selection, select the hardware from the
Navigation Tree and drag’n’drop it into the Control Selection. Once done a list
of parameters will be available. Drag’n’drop the parameters from the Control
Selection to the graphics views to expose the parameters control. All the types
of controls found in a configuration view can be
deployed into a graphics view. Controls like sliders; combo boxes, text boxes
and status boxes can be strategically laid into the graphics view for a optimal
layout design.
Apply and Refresh controls found in the configuration views are available on the
applications toolbar. These controls will work with all configuration parameters in
the graphics view and they function the same as a product’s configuration view.
The powerful flexibility on the graphics program is the ability to change the
elements icons in the graphics view. The graphics user has the ability to import
icons from the supplied library or from a custom library. By default the
tiny(Standard) library is used. To change an elements icon face select the
element using the right click mouse button and select the ‘Change Icon
Face…’ option. A dialog will appear were the user can select imported icons
from a combo box. The below image displays the 2 step process to change a
element icon face.
The ‘Change Icon Face..’ option is available for all elements in the Navigation
Tree except for Thumbnails and items from the Control Selection. Two Icon
Face controls are available in Design Mode for managing the icons. They are
described below
This control gives the application the ability to change its default icon face.
This is desirable for rack views when working with different types of
elements
This control opens up a dialog box to import icons into the system. This
dialog will allow the user to select the icon from the hard disk and create a
custom name for it.
Drop as Rack
The visibility controls are purpose built controls to aid in the development of the
graphics views. They can hide control types temporary while in design mode.
Settings of these controls do not take effect when the graphics program is not in
design mode.
The VistaLINK PRO graphics program gives the developer the ability to link
multiple views together much like a web page. Views can be linked together
though the Navigation Tree elements and Custom components allowing an
operator to double click one of the items to access another view. This
functionality can create a ‘drill down’ system from a top view to a bottom view.
Much like a national map linked to a facility view, than the facility view linked to a
specific item view in the facility.
To successfully switch from one view to another view, the destination view must
be located on at least on one Page. The destination view can be on the same
page as the source view or on another page. An operator can recognize a view
element being a link path to another view by observing the mouse icon change
when hovering over the view element.
The below images demonstrates conceptually how a drill down might look like.
Notice how the frame view might have view link to the map view. Of course, the
frame view would have two icons to link to the Racks view and the Global view.
This design would be up to the graphics developer discretion.
The below image demonstrates how to create the view link using the right click
mouse button . All created views will be populated in the combo box were the
destination view is selected from.
History controls are available on the menu bar to revert back to a previous view.
These history controls record every action made. They can be identified on the
menu bar by the following icons. Using the eraser icon can erase the action
history.
Canvas controls are available to manipulate the canvas while in design mode.
One option is to change the canvas into a grey scale and the other options are to
lay a grid over top of the canvas. The grid option can further be set so that
elements are snapped to the grid points for alignment accuracy. These settings
removed when the Graphics program is brought out of design mode. To access
these options, right click anywhere in the canvas while in design mode and
select ‘Canvas Properties’. Below illustrates how to access the menu items.
The canvas background can also be changed while in design mode. Select the
following grayscale image at the top left corner. A dialog will appear to select a
new background.
Import and Export feature is used to re-use design layouts. Elements from the
navigation and vector arts may be included in the export. The export function
creates a text editable XML based file. This file can be hand edit and is used by
the Import function. Typical uses of the Import and Export are for repetitive and
favorable designs. This feature is more powerful than using the clipboard (copy
and paste) because the export makes the copy into a file that can be saved on
the local hard disk.
The above figure shows the steps to do an Import and Export. Below explains in
detail.
Export
Import
1. Open the global option menu in design mode using the right click button
anywhere in the canvas.
2. Select import from the menu.
3. Choose the import method whether it’s absolute or relative
a. Absolute does the import from where the elements were exactly
located from before. This is ideal to duplicate a view layout exactly
on another view.
Dynamic Page Mode is a mode that can create Pages automatically. The View
groups drive this mode from the navigation tree. When in dynamic page mode,
each group created creates a page automatically in the Page Console. When
views are added to the view groups, the views will automatically be placed on the
Page named after the view group. Dynamic Page Mode disables the Page
Console controls appropriately in regards to add and removing pages. The
system therefore cannot run either mode simultaneously and one mode should
be used throughout the VistaLINK PRO Graphics install base. This mode will
hinder a view from belonging to multiple pages because the nature how the
views are organized in the Navigation Tree. Meaning a view cannot belong to
Below is the step-by-step process in enabling Dynamic Page Mode and using it.
1) Enable dynamic page mode from the page console using the following icon.
While doing the above three steps, you might notice that a Page was created as
soon as your created the view group. Also when dragging view’s into the groups,
the views would have been automatically placed onto the Pages.
• Ensure there is a valid Ethernet path connecting the Remote Client to the Server PC.
• Ensure that the Client configuration specifies the correct Server hostname / IP
address.
• Ensure the Server application is running.
• Ensure there is an available client license on the Server for the type of Client being
used.
• Ensure the 7700FC Frame Controllers have been correctly configured for the
Ethernet network.
• Ensure there is a valid Ethernet connection between computers running VistaLINK
PRO and the 7700FR-C frames to be monitored.
• Ensure the “Auto Discovery” options have been configured properly.
• If the frames you are attempting to discover are beyond a router or gateway the
broadcast discovery packets will not reach the frames. In this case manually add
the hardware to VistaLINK PRO (once added hardware references will be stored
for future discoveries.)
• Ensure you have logged into VistaLINK™ PRO with a user account that has
configuration abilities.
• If the module has a Local/Remote mode (jumper/DIP switch) ensure it is set to the
"Remote" mode.