
Options, Licensing and Upgrades
7-16
1/1553-FGC 101 1790 Uen Y
Notes:
If the software or firmware version on the newly inserted card is different
from the software or firmware version on the replaced card, the Upgrade
Wizard must be run again to resolve the version conflicts.
The conflict is reported on the
Dashboard
in the
Model
accordion of the
Device Information
widget and on the
Versions
tab of the
Support
page.
The process to replace an option card is as follows:
1. Disconnect any cables from the option card to be replaced.
2. Loosen the two captive screws that retain the option card in the base chassis.
3. Holding the captive screws, pull the option card from the unit, (observe the
handling precautions and advice for module pairs where applicable).
4. Carefully remove the replacement option card from its anti-static package, and
insert it in to the base chassis, slotting the card edges in to the card guides.
5. Push the card home; so that the rear panel is flush with the rear of the base
chassis (observe the handling precautions and advice for module pairs where
applicable).
6. Tighten the two captive retaining screws.
7. Connect any external cables to the replacement option card.
Note:
If the replacement card is of the same type as the failed card, has the same
capabilities (licenses), is at the same software version and is fitted in the
same slot, then it will be automatically configured to the same settings as
the failed card. If the replacement card is of a different type then an alarm
will be generated.
7.10.6
Option Card Plug and Play
The unit is designed around a Plug and Play concept to make it as easy as possible
to add new option cards and functionality. This means that the chassis and Host
controller card provide a base level of functionality, while any specific functionality
associated with an option card is contained on the option card itself.
A good example of this is MPEG SI generation. The Host controller provides the
functionality to generate and play out the SI required by a Transport Stream.
However a VCM is required to provide any descriptors required for any elementary
stream types that it generates.
Summary of Contents for AVP 4000
Page 1: ...AVP Family AVP 4000 Software Version 9 31 x REFERENCE GUIDE 1 1553 FGC 101 1790 Uen Y ...
Page 10: ...Preliminary Pages x 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 26: ...Introduction 1 16 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 42: ...Getting Started 3 6 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 140: ...Getting Started 3 104 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 184: ...Front Panel Control 4 44 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 278: ...Advanced Video Processing and Networking 6 4 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 304: ...Advanced Video Processing and Networking 6 30 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 324: ...Preventive Maintenance and Fault finding 8 4 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 346: ...Preventive Maintenance and Fault finding 8 26 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 386: ...Technical Specification B 20 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 388: ...Dolby E PCM Bypass and Switchout C 2 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 390: ...Dolby E PCM Bypass and Switchout C 4 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 392: ...Alarm Lists D 2 1 1553 FGC 101 1790 Uen X BLANK ...
Page 416: ...Logo Creator E 2 1 1553 FGC 101 1790 Uen Y BLANK ...
Page 422: ...Logo Creator E 8 1 1553 FGC 101 1790 Uen Y BLANK ...