Grass Valley Jupiter v.1.0 - Manual (Page 39)

Jupiter L-S Series Control Panels Installation and Operating Manual 39
Section
3
Software Installation & IP
Addresses
Introduction
The L-S series panels operate with the Jupiter AccuSwitch control system
using Ethernet LAN connections. This functionality requires compatible
software versions and IP addresses must be used by all Jupiter system
devices on the network.
L-S series hardware panels are shipped with the current software installed.
There is no need to install panel software on newly shipping systems. How-
ever, the IP address must be set on each panel so it can operate on the net-
work. The NetConfig application is used to discover and set IP addresses
of the L-S series panels. NetConfig is also used to update L-S series panel
software, by transferring panel code from the computer running NetConfig
directly to the panels. The L-S panels communicate with the CM4000 con-
troller boards via the ESLAN protocol. Once communications is estab-
lished, the L-S panels will receive their operational configurations from the
Jupiter CM4000 controller.
The panel software update mechanism above is different from that used by
the Jupiter control system itself. Jupiter (VM, SI, CM-4000) controller
boards update their software via Bootstrap Protocol (bootp) and Trivial File
Transport Protocol (tftp) when activating a configuration. The controller
boards send out a “bootp” request and the file server responds by indi-
cating what files need to be downloaded from where. The controller boards
then use tftp to download the files from the Jupiter file server. The files
consist of the.sys files (accuswch.sys, jupiter.sys) and a.cfg file. The .sys file
is the operating system and the .cfg file is for configuration. The .sys file is
installed during the Jupiter install process and the .cfg file is created after
compiling the configuration and activating it.
Note The Jupiter Control Center and NetConfig use the same tftp port. NetConfig
cannot be used to send software to the control panels if the Jupiter Control
Center is running. Configuration changes from the Jupiter Control Center
could also be interrupted if NetConfig is running at the same time, depending
which application has the port bound.