Version 1.400 Interoperability Requirements • Encore version 1.7 or newer, or • Jupiter version 4.2 or newer, or • Jupiter version 7.4.1c or newer (for LAN connection). Upgrade Requirements • The software installation procedure must be followed as described. This includes uninstalling the previous version of software before installing v1.4 software (as described on page 19).
Caveats 6. It is now possible to use Telnet and the VxWorks command “ixGetBatteryStatus” to check the status of the NVRAM backup battery on the Maestro rear panel. For more information, refer to Field Modification Note 075079500, Maestro Processor Backup Battery, CP Server, and CP FPGA Telnet Upgrade.
Version 1.400 The DVE option allows one background bus (audio and video) and its selected upstream keys to be in a squeeze window with another back- ground bus and its selected upstream keys serving as the background. The AUX bus is fully utilized with this release. A DVE effect is entered by selecting the desired effect and pressing Take While the DVE effect is active, a variety of audio/video transitions may be...
Page 9
• If the Maestro will use embedded audio, no additional hardware is required for DVE operation. • If the system includes a Grass Valley Apex audio router, no additional hardware is required for DVE operation since Apex includes AES- MADI conversion as a standard feature.
Version 1.400 General Purpose “Transition” Input/Output With this release, the GPIO connector on the Maestro rear panel can be used to receive an “Action: Transition” signal from a controlling external device (Figure 3), or to transmit an “Action: Transition in Progress” signal to a con- trolled external device (Figure Maestro Controlled by External Device...
Page 11
General Purpose “Transition” Input/Output Maestro Controlling External Device When used to control an external device, all present Maestro systems require installation of a leakage-current swamping resistor in the GPO cir- cuit. This resistor is used to prevent leakage current from reaching the external device when the Maestro GPO relay is open.
Page 12
Version 1.400 It is also possible for one Maestro to control another. See Figure Figure 6. Maestro-to-Maestro GPIO Connections Controlling Maestro "Transition in Progress" signal - 5 V External power GPO Port/Relay See Notes Note 1 Connections between Maestro GPIO Connector and controlled external device are bipolar.
Page 14
Version 1.400 Maestro Configuration The GPIO Definition table is used to configure the GPIO ports on the rear panel of the Maestro. The table is located in the Input/Output Sets group of the Maestro Configurator (“4th Step”). When the GPIO Definition table is first opened, the editor will open a set panel.
Page 15
General Purpose “Transition” Input/Output Trigger Duration This column is not used in this application. Trigger Sense Select “High” if the external device is normally low and will send between 3 and 10 V to assert “Transition.” Select “Low” if the external device is nor- mally high and will present zero V to assert “Transition.”...
Page 16
Version 1.400 Purpose “Transition in Progress” is the only choice when “MaestroGPO” is the device type. Trigger Type “Level” is the only choice when “MaestroGPO” is the device type. When a transition begins, the GPIO contact will go to the state selected in the Trigger Sense column (described below).
Software Upgrade Procedure Software Upgrade Procedure CAUTION Portions of this procedure will interrupt video and audio signals passing through the system. Users of this equipment should consult with Grass Valley Technical Support personnel before proceeding. Maestro Deployment PC Note In some installations, the “deployment PC” will be the same as the GUI PC. Requirements •...
Page 18
Step 4 below. • If you see an older date, or no date at all, the Boot ROM should be updated. Contact Grass Valley Technical Support for update instructions. 4. If there is another Processor (channel) in the system, repeat Step 1 above and following.
Page 19
Software Upgrade Procedure Installing the Maestro Software Package Perform this procedure only after checking the Boot ROM versions. Note It is recommended that all default values be used during the installation. 1. Make a copy of the current configuration set: a.
Page 20
Version 1.400 Figure 10. Run Dialog Box b. Enter “D:\setup.exe” where D: is the CD Drive. c. Click the OK button. A popup will appear that asks if the install should continue; select Next Go to Step 4. A popup will indicate the default destination folder. Select Next . 5.
Page 21
Software Upgrade Procedure Figure 11. Installing Maestro Software Package When this step is complete, the window shown in Figure 12 will appear. Figure 12. Maestro Software Package Installation Complete 7. Select Finish . Installation of the Maestro Software Package on the PC is now com- plete.
Page 22
Version 1.400 Manually Removing the Maestro Jupiter Router Service Software Perform this procedure only if you see the error message “Error 1001 -- the specified service already exists” referred to in the Note on page 1. Go to “Control Panel > Adminstrative Tools > Services.” 2.
Page 23
Software Upgrade Procedure Re-compiling the Configuration File This step is required because changes have be been made to the structure of the Monitor Follow configuration table 1. Launch the Maestro Configuration Editor by going to “Start > All Programs > Thomson > Maestro Configuration Editor.” 2.
Page 24
Version 1.400 Updating the System Configuration and Software 1. Launch the Maestro Deployment control center by selecting “Start > All Programs > Thomson > Maestro Deployment Center.” A Maestro Deployment Control Center window similar to that shown Figure 13 should appear. Figure 13.
Page 25
Software Upgrade Procedure c. Click the Update Only button. This will update the contents of the “Pending>>” rows in the Board Configuration and Active Configuration columns. The Configuration box contains two buttons: Update Only Update and Apply - Activates the configuration and downloads it to the Update Only boards, but does not apply it as the running configuration.
Page 26
Version 1.400 b. Click the Update and Apply Button. The pending software files will load and execute. This will also update the contents of the “Running>>” rows in the Version columns. 7. Verify that the new Configuration and Application versions are “Running”...
Software Upgrade Procedure Checking the GUI Control Panel for Proper LAN Settings The “Panel Server IP” address and the "Local IP” address for the Maestro GUI must now use control LAN addresses only. In previous releases, the GUI application would connect and run over the facility LAN; this is no longer possible with version 1.400.
Page 28
Version 1.400 Updating FPGAs/CPLDs (FPGA = Field Programmable Gate Array. CPLD = Complex Program- mable Logic Device.) 1. Updating FPGAs/CPLDs on the Processor board(s): Note Some of the FPGAs on the Processor are updated using the Software Version Update and Apply procedure described above. The remaining FPGAs on the Processor are updated using the procedure below.
Page 29
Software Upgrade Procedure Figure 16. FPGA/CPLD Update Menu (Example for Processor) This menu shows the names of all FPGAs/CPLDs on the Processor and the version number of the gateware now running (“Loaded”) in each device. Certain of the FPGA-type components and all of the CPLD-type components can be updated using this menu, and if a newer (“current”) version of gateware is available for those compo- nents the menu will indicate the new version number and display a...
Page 30
Version 1.400 • An error message may indicate that the “physical JTAG chain is broken.” If this message appears, the FPGAs/CPLDs on the Pro- cessor cannot be updated. Discontinue the v1.400 installation and contact Technical Support. 2. Updating FPGAs/CPLDs on the hardware control panel(s): a.
Page 31
Software Upgrade Procedure • A popup will show that the control panel update was suc- cessful. Repeat Step 2 above if another control panel is present. When all FPGAs/CPLDs have been updated, the v1.400 upgrade is complete. • An error message may indicate that the “physical JTAG chain is broken.”...