Avstar Systems, LLC™ Louth VDCP Device Manager Version 1.0.2 Device Operation Guide This addendum provides information on how to install and use the Avstar™ Newsroom Computer System (NRCS) Broadcast Control System™ (BCS) Device Manager (DM) for the Louth Video Disk Control Protocol (VDCP). Preface Who Should Use This Manual This manual is written for journalists, producers, directors, writers, and various technical personnel using Avstar BCS in a broadcast newsroom.
Look here in the margin for tips and environment-specific information. In the margin you will find tips that help you perform tasks more easily and efficiently. You will also find information specific to a particular operating environment. A note provides important related information, reminders, recommendations, and strong suggestions. A caution means that a specific action you take could harm your computer or cause you to lose data.
The console can display each computer’s prompt, based on the system ID and the computer’s name. Examples in this addendum may use a fictional station and system ID of WAVSTAR. For example, the following is the console prompt for computer A on the WAVSTAR system: WAVSTAR_A: Support If you are having trouble performing a system operation, you should: Repeat the procedure, carefully following the instructions provided for the task in this guide.
Avstar (formerly AvidNews) Broadcast Control System Release Notes provides installation, administration, and user-level information that may not have been available at the time the other documentation was printed. MCS Release Notes describe administration and user-level information on how to use the NetStation Machine Control System with the Avstar NRCS. Documentation Comments Avstar Systems, LLC continuously seeks to improve its customer documentation.
Handles several shows at the same time, enabling shows to be produced back-toback Windows-based GUI clients allow technical directors to control events on the Broadcast Control Server. Avstar NRCS The Avstar NRCS product set is constructed on a modular, open architecture, enabling its components to work efficiently not only with other Avstar products, but also with third-party hardware and software.
Figure 1-1 Dataflow through BCS System Architecture The BCS architecture consists of: BCServer Avstar Machine Control Protocol (AMCP) BCS Manager Device Managers BCWS BCServer The BCServer is an NT server connected to the broadcast production devices.
Tracks which clients have playlists and devices reserved AMCP AMCP is the interface between NRCS and BCServer. It translates the data coming in from Avstar Newsroom Computer System, or other newsroom computer systems, into data that the BCS can manage.
BCWS You may need to consult the AvidNews System Operations Manual for specific information on the Avstar server or various system operations related to the news server. Setup Tasks on the Avstar NRCS Server In /etc/hosts file, add the IP address/ethernet address for BCServer(s), devices, and BCWS(s). If you’re upgrading from MCS, you may have to remove device information for machines (CGs, and so on) from the /site/config file.
Louth VDCP DM Once BCS has been installed, you must set up the Avstar NRCS server before you can use the system. There are setup tasks that must be performed on the Avstar server at the console, and tasks that must be performed on the Avstar Newsroom Computer System (NRCS) Workstation (the client). For more information about any Avstar/AvidNews task, see the AvidNews Newsroom Computer System Operations Manual and the AvidNews Newsroom Computer System User’s Guide.
Device Profile Files For each device and device manager (except AirPlay devices), there must be a separate profile. A profile is a text file with the extension .dmp, which is opened and parsed at start-up. In addition to user-configurable formation, this file must contain the operational name of the device manager and the network name of the BCS computer. The profile can have any name, but it is recommended that you use the name of the device manager.
BCServer Hardware To install and run the BCServer/Louth VDCP Device Manager, you’ll need the base equipment detailed in the following table. Device Description CPU 200 MHz Pentium® Memory 64 MB RAM Keyboard 104 keyboard Monitor 15-inch monitor Video card SVGA 800x600 or better Hard drive configuration 2 GB drive Floppy drive 1.44 MB Operating system Microsoft NT 4.
On the BCS Server, we recommend the Equinox SST-64 board with the PM16RJ/422 Port Module, which has 16 RS-422 ports using RJ-45 sockets. Up to 4 such Port Modules can be attached to each other in series for a total of 64 ports without opening the computer or changing software or driver settings. NOTE: On the back of the Equinox board is a pin-out diagram. Several manufacturers' documentation conflict over the meaning of symbols like "TX A" and "TX B".
Digiboard BCS DB25 to RJ-45 adapter pin-outs: RJ45 cable to RJ45 to DB25 DIGIboard BCS Device Adapter DB25 on BCSrvr n/c 1 n/c n/c 2 Blue n/c GND 3 Orange to 1 1 GND RX - 4 Black to 16 16 RX TX + 5 Red to 2 2 TX + TX - 6 Green to 14 14 TX RX + 7 Yellow to 3 3 RX + GND 8 Brown to 7 7 GND n/c 9 White n/c n/c 10 n/c Louth VDCP DM Software Configuration BCServer and BCWS Requirements To install and operate the Broadcast Control System, you will need: Windows NT Server 4.
Identification Keywords DeviceName The DeviceName keyword specifies the name by which Avstar NRCS can refer to the device manager. Example: DeviceName=louth BCSHostName The BCSHostName keyword specifies the hostname of the computer running BCServer. Example: BCSHostName=localhost Device Control Keywords NumberOfChannels Specify the number of channels that the device manager will control with the NumberOfChannels keyword.
ChannelPollInterval Check at this interval (measured in seconds) to see if any channels that are offline can be brought back online. The default is 10 seconds. Example: ChannelPollInterval=10 CanPlayTransferringMedia CanPlayTransferringMedia indicates whether or not the DM should allow a transferring clip to be played. The default value is No, in which case a transferring clip cannot be played. Once the transfer is finished, the clip can be played.
NumberOfLogFiles To specify the maximum number of log files that will be created, use the NumberOfLogFiles keyword. If it is not specified, the LouthDM will create at most 10 log files. Example: NumberOfLogFiles=10 StartLoggingOnProgramStart The StartLoggingOnProgramStart keyword indicates whether the LouthDM should start logging immediately upon starting up, or should wait until the user explicitly starts logging using the Logging / Start Logging menu option. The default is to start logging immediately.
ReportEventStatusChange and ReportEventStatusChangeDetails EventStatusChange messages describe changes in the status of individual events. Examples: ReportEventStatusChange=No ReportEventStatusChangeDetails=No ReportDeviceStatusChange and ReportDeviceStatusChangeDetails DeviceStatusChange messages describe changes in the status of the VDCPcompatible device being controlled by the device manager.
VideoServers Section This section contains keys Server1, Server2, etc., one for each physical machine being controlled by the device manager. A video server is specified by a line of the form Server=:Chan:Chan:... where: • is an identifier for the physical machine (e.g., its host name), and • , , ... are the numbers from the [Channels] section that indicate the channels on that machine.
A serial port is specified by a line of the form: • Serial=:::: The Louth protocol specifies that the baud rate is 38400, the bit count is 8, the parity is odd, and there is one stop bit. Examples: Serial1=com3:38400:8:o:1 Serial2=com4:38400:8:o:1 Serial3=com5:38400:8:o:1 Serial4=com6:38400:8:o:1 The SerialOfflineInterval keyword specifies a timeout interval.
ReportDeviceStatusChange=No ReportDeviceStatusChangeDetails=No ReportErrors=Yes ReportErrorDetails=No ReportVDCPData=No ReportVDCPDataDetails=No DisplayVDCPDataOnScreen=No CueReplacesPlayingEvent=No ChannelPollInterval=10 CanPlayTransferringMedia=No SignalStartOfTransfer=Yes SignalEndOfTransfer=Yes ;--------------------------------------------------[VideoServers] Server1=PDR001:Chan1:Chan2 Server2=PDR002:Chan3:Chan4 ;--------------------------------------------------[Channels] Chan1=A:1:Serial1 Chan2=B:2:Se
Using the Louth VDCP DM This section tells you how to use the Louth Video Disk Control Protocol (VDCP) Device Manager (DM). (Refer to the Tektronix Profile User Guide for detailed information on the Profile VdrPanel setup.) Setting up the Louth VDCP DM to Run The following program must be running before you can set up the Louth VDCP Device Manager: Bcserver.exe Connecting to the Tektronix Profile The PDR must be running VdrPanel for the Louth VDCP DM to connect to it.
VdrPanel To set up the PDR for connecting to the Louth VDCP Device Manager (DM): VdrPanel Select the VdrPanel menu item Window Æ Open Panel.... Select the menu item Controller Æ Select.... Choose Louth Automation and press OK to set the panel’s controller. Select Controller Æ Comm Port... to set the COM port for the Louth Automation protocol. Select Video Æ Video Crosspoint... to set up the output channel associated with each panel.
Each message type has two levels of detail, indicated by the two columns. The “high level” is in the left column. If the “On-air control” check box is checked (enabled) as shown, then the Louth VDCP DM will report a message every time it receives a Cue, Play, or Stop command. If the “Details on on-air control” box is checked, it will further report which event is being controlled.
If a file is not specified, an open dialog will prompt you to choose a profile file. After the Louth VDCP Device Manager is started, it can be run unattended. To exit the Louth VDCP DM program, select the menu item File→ →Exit.
Louth VDCP DM Error Messages The following table describes Louth VDCP DM error messages. Error Message Description <<
Error getting duration from device The DM could not determine a clip’s duration. Error getting position The DM could not determine the amount of time remaining on a playing clip. Error reading Communications section of Profile file The DM could not read the [Communications] section of the Profile file. Error reading Configuration section of Profile file The DM could not read the [Configuration] section of the Profile file.
to play. EVT_STATUS: The clip '' on the video server '' may not be safe to play. The DM has detected that the clip is transferring to the video server and is not completely present. Playing it may yield unpredictable results. EVT_STATUS: The clip '' on the video server '' is now safe to play. The DM has detected that a clip that was transferring to the video server has finished transferring. Invalid channel assignment.
LogFileDirectory= in the Profile file, with an appropriate value for . Unable to cue event '' for playing User tried to play an uncued event, and the DM could not cue the event prior to playing it. Unable to open the Profile file '%s' DM cannot open the specified Profile file. Check the name and path.
Required Louth VDCP Commands The Louth VDCP Device Manager uses the following Louth VDCP commands. Any video server controlled by the device manager must support these commands. Required Louth VDCP Commands Command Description 1X.00 Stop 1X.01 Play 1X.04 Still 1X.06 Continue 2X.21 Close Port 2X.22 Select Port 2X.24 Play Cue 3X.01 Open Port 3X.02 Next 3X.05 Port Status Request 3X.06 Position Request 3X.11 ID List 3X.14 ID Size Request 3X.16 ID Request 3X.18 IDs Added List 3X.
Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avstar Systems, LLC. The software described in this document is furnished under a license agreement. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement.
including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages. The following disclaimer is required by Videomedia, Inc. “Videomedia, Inc.
George R.
