26
8900NET Instruction Manual
Using the 8900NET GUI
During initial polling, modules that do not respond immediately may tran-
sition to a
WARNING, MODULE NOT RESPONDING
status. In this case, this is a tem-
porary status until a maximum number of sequential attempts fail and a
Fault is reported.
Note
The first release of 8960DEC module code causes a Fault condition because
it never responds on the Frame Bus. There is no way for the 8900NET module
to tell the difference between a fully functional early release of 8900DEC and
a module whose Frame Bus Interface has failed.
Note
Early releases of the 8960ENC, 8950DAC, 8950ADC, 8920DAC, 8920ADC,
and the 8916 signal a warning condition due to limited capability over the
Frame Bus. All of these, except the 8916, can be upgraded by the user with
fully capable Frame Bus software.
Frame Properties
The Properties section on the Frame Status page reports:
•
Vendor name,
•
Number of media module slots,
•
Software version (installed on the 8900NET module),
•
Network Config (whether the network configuration is stored on the
8900NET module or on the frame backplane, depending on frame
model). Refer to
Network Configuration Storage on page 22
.
Older and Legacy Module Support
8900 and legacy Grass Valley modules that can reside in the 8900TFN frame
are supported to different degrees by the 8900NET module. A compati-
bility matrix describing the hardware versions, software update methods
requiredm, and remote control features of the various modules supported
by the 8900 frames and 8900NET module is located in the
Note
When the 8900NET is first installed or when many modules are installed
simultaneously, it may take some time for the 8900NET to poll, update status
and build the HTML pages, especially if there are modules that do not
respond as expected, such as legacy modules. During these periods the
Frame Status Page may fall behind temporarily until the 8900NET board can
catch up and present a true current status.
