The buttons – Grass Valley NV9000-SE v.5.0 User Manual
Page 92

74
System Management
Main System Page
The 3 indicators are ellipses that resemble (North American) traffic lights. There are 3 indicators
for each controller.
This is what the colors mean:
•
A solid red indicator means that the controller is stopped (or not present).
•
A solid yellow indicator means that the controller is active.
•
A solid green indicator means that the controller is healthy.
When the indicators are grey (with a colored outline) they do not apply. Figure 5-3 shows that
controller 1 is active and healthy and that controller 2 is non-existent.
The buttons for the controllers are highlighted when they can be applied. For example, a
running controller can be restarted or stopped; it cannot be started. Therefore the ‘Start’ button
would not be highlighted, as shown in Figure 5-3.
The Buttons
These are the functions of the buttons:
•
Dynamic Update
The ‘Dynamic Update’ button is intended to transfer certain kinds of changes to the active
system controller’s configuration (from your PC) without requiring a restart.
The button specifies to which control system it applies. You are to infer from the state of the
controller buttons to which controller it applies.
The ‘Dynamic Update’ button is unreliable and it is not possible to give information
about when it is designed to work and when it is not. Therefore, avoid it.
•
Read Configuration
The ‘Read Configuration’ button transfers configuration data from the active system control-
ler to a configuration in your PC. When you click the ‘Read’ button, NV9000-SE Utilities pre-
sents a dialog in which you can choose a configuration:
The first entry in the list is ‘New’. Choose this entry to create a new configuration. NV9000-SE
Utilities will present an additional dialog in which to enter the configuration name.
If you choose an existing configuration, NV9000-SE Utilities will present a confirmation mes-
sage asking you whether it may overwrite the existing configuration.
The button legend specifies from which control system the software will read. You will have
to infer from the state of the controller buttons from which controller it will read (if you have
a redundant pair).