Multi-Channel Server Maintenance & Diagnostics...Backplane Programming Entered command to program Backplane Serial Number & Revision Level: • set_bp –cPTIXXXXX –bYYY -rZZZ Where

1 • Maintenance & Diagnostics Version 2.02 Avid Technology, Inc.

AirSPACE™ Multi-Channel Server

Maintenance & Diagnostics

This manual is intended as a guide for prospective AirSPACE maintenance engineers. The engineer should be familiar with AirSPACE Operations and Command Line Interface. In the event of problems and/or questions with this manual, please contact Technical Support at (303) 402-9000 Extension 145.


Table Of Contents • SECTION I: Hardware Design Interconnectivity and Mechanical Page 3 AirSPACE Motherboard (MOAB) Page 4 SCSI Piggyback (SCSI) Page 5 Reference Interface (RIF) Programming Page 5 Audio/Compressed Video (ACV) Page 6 Serial Digital I/O Module (DIO) Page 7 Interboard Connections & Performance Specifications Page 8 Backplane Programming Page 8 • SECTION II: AirSPACE RAID File System RAID Discussion & Disk Replacement Guidelines Page 9 RFS Tools Introduction Page 10 RFS (Meta-Data) Back-Up Files Page 10 Restoring Corrupt RFS & Initializing NVRAM Page 11 • SECTION III: AirSPACE Disk Diagnostics Tools Array Configuration Record (ACR) Page 13 Diagnostics Commands Page 14 Disk Drive Re-qualification Page 18 • SECTION IV: AirSPACE Software Update Procedures

Preliminary Procedures Page 22 Network Update Page 22 CD-ROM Update Page 23 AirSPACE NT Applications Downloads Page 23 “Gold Disk” Update Procedure Page 24

• SECTION V: Destructive Commands Page 26 • SECTION VI: AirSPACE Single Board Computer

AirSPACE 450M Single Board Computer Page 27 Loading 450M SBC BIOS Defaults Page 27 AirSPACE 700M Single Board Computer Page 28 Loading 700M SBC BIOS Defaults Page 28 Setting the System Time & Date Page 29 Localizing AirSPACE Page 30 SBC & Motherboard Functional Tests Page 30 SBC Replacement Procedure Page 36

• SECTION VII: ACV Assembly Functional Tests ACV Functional Tests Page 37 ACV Assembly I/O Connections Page 37 ACV Breakout Box Page 38 ACV Memory Tests Page 38 ACV Audio & Video Tests Page 40 ACV Time Code Tests Page 47 ACV Replacement Procedure Page 50

• SECTION VIII: Modem Card Modem Settings & Replacement Procedure Page 53

• SECTION IX: Gigabit Ethernet NIC Gigabit NIC Installation & Replacement Procedure Page 55 Gigabit NIC/100BaseT Enable/Disable Page 56

• SECTION X: AirSPACE Motherboard Motherboard Replacement Procedure Page 57

• SECTION XI AirSPACE System Level Tests System Level Tests Page 60 Network Debugging Tools Page 62

• SECTION XII AirSPACE Error Logging Hardware Logging Page 65 Software Logging Page 67

• SECTION XIII Common Errors Page 68

SECTION I: Hardware Design

Internal Connectivity and Mechanical • The Connector Board mounts to the rear panel with jack screws for D-Sub connectors. The

Reference/Interface board sits over top of ACV cards to provide a bridge for all ACV I/O as well as hold down for cards. The Reference/Interface Board also contains circuitry for reference genlock.

SCSI OPTION

ACVACVACVACV

SBCMODEM

NETWORK

ACV

PCIPCI

D
CONNECTOR BOAR
3 • Maintenance & Diagnostics Version 2.02

BackPlane

REF/INT BOARD

ACV CARD

REF/INTERFACE BOARD

CONNECTOR BOARD

XTRA OVER PCI FORM FACTOR

104078 60pos

104069 60pos104549 100pos

S O ND V C

104549 60pos

TO MOUNT ON I/O MODULETO MOUNT ON PCI CARD

104078 60pos

104069 60pos

I/O OUTPUTMODULEDIO BOARD (FRONT)ACV BOARD (BACK)

THIS RIF CONNECTOR MATES TO DIO BOARD. THIS RIF CONNECTOR MATES TO ACV BOARD.

DV CO

E

Avid Technology, Inc.

MOTHER BOARD

S O N YD V C A R D

P A ND V C A R D

Y A R D

MOTHERBOARD METAL SLED BASE

DECS


AirSPACE Motherboard (MOAB) • The Motherboard provides the framework of the system to transfer data to and from disk, I/O, or network while

calculating the parity data necessary for data reconstruction within the RAID system. The current AirSPACE Motherboard has been designed with an additional PCI bus allowing 6 PCI cards to be inserted into the chassis, providing room for a maximum of 5 ACV I/O cards. The remaining PCI slot is used for the Gigabit Ethernet NIC.

LBus #0

LBus #0

SCSI

PCI

SBC

(w/S

VGA)

ISA

Thermometers

Disk LEDs

PCI

CS

DI

(opt

iona

l)DEC#1

Watchdog &BIOS CTL

NVRam

DRAMController

&ParityEngine(FPGA)

1-BIOS

BackplaneConn. 3

BackplaneConnector 4

BackplaneConn. 2

BackplaneConn. 1

POST Display

SMPTEAlarm

ISA

Mod

em

PCI

HS

LAN

(opt

iona

l)Disk Sense

3.3v Regulator

Option &Backplane Keys

DIP Switches

Power & FanSense

DRAM SIMM(16-256 MB)

(BufferMemory)

ISA DecoderISA ISA

PCI 0Arbitor

RS-

422,

keyb

d, m

ouse

DEC#4

. . .

5/10 SCSIAdapters

PLX#4

AIC-7895 AIC-7895

TERM TERM

PCI Bus #4

SCSIDaughtercard

DEC#3 PLX

#3

AIC-7895(1/2)

AIC-7895(5/10)

TERM TERM

PCI Bus #3

Ext.SCSI

100BaseTLAN

10Ba

seT/

100B

aseT

PHY

PCI

ACV

PCI

PCI

ACV

ACV

PCI

ACV

PCI

ACV

PCI Bus #1

PLX#1

PCI Bus #2

DEC#2

PLX#2

PCI Bus #0

7 6 5 4 3 2

PCI

Spar

e

1 0

VGAAdapter

VGA

out

• Buses #1 and #2 are split for 4 peripheral cards on each. The Motherboard contains PCI bus #3 with 5 SCSI

adapters for first ten drives and an additional adapter for the external SCSI line to the CD-ROM. It also has a connector for a SCSI piggyback module. The SCSI piggyback module has 5 adapters, for the remaining 10 drives of the array.


SCSI Piggyback (SCSI) • The SCSI piggyback module is a shortened height PCI edge connector card with 5 SCSI adapters and a PLX

PCI to local bus adapter.

DECBridge

. . .5/10 SCSIAdapters

PLX

AIC-7895 AIC-7895

TERM TERM

PCI Bus #2

SCSIConnector

PCI EdgeConnector

Local BusConnector

Reference Interface Board (RIF) • The Reference Interface locks the AirSPACE to common house reference, and generates clocks for the entire

system. The board uses a three-dimensional connection between the Connector Board and ACV/DIO cards to eliminate internal cabling.

RaytheonGenlockTMC2072

Reference In

bref_vid A,B,C,D,E

sda,scl,rst*3 CVBS[7:0], ghsync, gvsync, int*, valid, burl12

pxck

Entered command to program Reference Interface Serial Number & Revision Level: • set_rif –sXXXXXXXX -rYYY

Where X=RIF Serial Number. Where Y=RIF Revision Level.

Current AirSPACE Production Part Numbers & Revision Levels: MOAB 0030-03086-01 Revision D05 Reference Interface 0030-03091-01 Revision A03 Connector Board 0030-03088-01 Revision B01 SCSI 0030-03096-01 Revision B00 ACV II Assembly 0030-03080-01 Revision D03 Power Supply, Jasper 441W 0840-03016-02 Revision E Single Board Computer 450 0030-03087-01 Single Board Computer 700 0030-03087-02 Backplane Board 0030-03085-02 Revision D01 Modem, V.90, 56k 0080-03025-01 Gigabit Ethernet NIC 0030-03081-01 Power Entry Module 0840-03018-01 Fan Assembly, External 0750-03006-01 AirSPACE Chassis Assembly 0020-03143-01 Breakout Box Assembly 0020-03144-01 Breakout Box Multi-Pin Cable 0070-03061-01 Breakout Box VGA Cable 0070-03054-01


Audio / Compressed Video (ACV) • The audio and compressed video interface ACV card is an enhanced version of the current VideoSPACE

AVIO PCI card. The ACV card interfaces one video and eight audio streams through a dual-ported DRAM buffer for direct memory access over the PCI interface. The DV and IMX (MPEG) Compression/De-Compression hardware is implemented with OEM codec modules and which are required for concurrent real-time record and playback and for accurate E-E monitoring.

ASRC

Local Bus

Host PCI Bus

PCIInterfacePLX 9080

DRAM8MB x 32 bit

GPI/O

SCC

8 In4 Out

DSP1-4MuteVolumeMix

ASRC

OutputTiming

DV

Cod

ecR

/PB

DV

Cod

ecPB

RS-422

DRAMController

BusArbiter

AESAudio I/O

SDI I/O DIO/AIOModule

DVR Bus

DVI

VideoRecord/PBInterface

Audio 1-4R/PB/EEInterface

ASRC

DSP5-8MuteVolumeMix

E-EFIFO

VideoOutputFormat

Vert.Filter

ReferenceTiming

InputTiming

Audio 5-8R/PB/EEInterface

XadBus

• The current configuration uses 4 rear fence BNC connectors for 1 SDI Input; 2 SDI Outputs; and 1 Analog

Composite Monitor output. The AirSPACE is capable of holding (5) DV ACV Assemblies; or (3) IMX MPEG ACV Assemblies.

• The Serial Digital I/O Module (DIO) also includes, via a Breakout Panel, AES digital audio inputs and outputs as well as analog audio monitoring outputs.


Serial Digital I/O Module (DIO) • Serial Digital I/O with cable equalization conforming to SMTPE 259M-1993. • Analog Composite and Component Video Monitor Outputs. • 8 channels of 16-bit or 24-bit, 48 kHz, AES digital audio, including AC-3 and Dolby E. • Preservation of important audio channel status bits. • Analog Audio Monitor Outputs.

Re-clockerCLC016

Serial toParallelDecoderGS9000

Vin[9:0]SerialVideo In

CableEQ

CLC014

iclk

Serial VideoOut 1

SerialEncoder,Driver 1GS9022

NTSC / PALComposite Analog OutLPF

Vout1[9:0]

LPF

LPF

LPF Comp/G/Y Out

Y/B/Pb Out

CH/R/Pr Out

auderr_rst

XMITCS8402

DACCS4327

AnalogAudioOut

AES Out +,-

LPF

ifsync,isclk,isdata

4x for 4 Stereo Pairs

car_det

oclk1

cbl,csts,verfAESRCV

CS8412

csout, vldout, dsprstclk6m1

clk12m3

ocbl

Analog monitor outputsto Con board

AES In +,-

E2,F2

common tothe 4 channels

VideoEncoderTMC2193io_sda,io_scl, io_rst

LTC/VITCReader/

GenICS2008A

ics_ctrl[13:0]frame, click

LTCin+,- LTCout+,-

LTC_intbuf_refvin

NECChar. Gen

uPD6465nec_clk, nec_cs*, csp,nec_data, nec_dotclk TC Burn-in

Char. OverlayTC MON 2

EEID

mbs360SerialEncoder,Driver 2GS9022

Serial VideoOut 2Vout2[9:0]

oclk2

DACLTC1448

dac_sda,dac_scl

DACLTC1448dac_e1_gb_cs*

comp/g/y gainy/b/Pb gainch/r/Pr gaincomp2 gain

dac_e1_rc_cs*TC MON 1

out_sclkl, out_fsyncl (ch 1-4), out_sdataout_sclkh, out_fsynch (ch 5-8)

looped from ref/int

io_sda,io_scl, io_rst


Inter-Board Connections

BackPanelConnectors

AIO/DIO

CONNREF/INT

ACV

Ref_vid

bref_vid,tc_mon_2

gpio, 422 control

audio i/o, ltc i/o,video out

video/audio data i/o& control,

ltc data i/o & control

Ref glk input data,clk & control

Performance Specifications Component Serial Digital Video I/O 10 bit, CCIR 601, SMPTE 259M compatible Serial Video Input Cable EQ 0 to 200 m. of Belden 8281 quality cable Serial Video I/O Return Loss > 15 dB at 270 MHz. Serial Video Output Timing Jitter < .2 UI (740ps) over 1 line Serial Video Output Signal Level 800 mV +/- 10% Reference Genlock Timing Jitter < 500ps over 1 line Analog Reference Black Input Return Loss > 40 dB @ 4.5 MHz. Video Output Timing Range > +/- 2 H in 74ns increments (12 bit control) Digital Audio I/O 4 channels AES-3 1992 Differential/AC-3/Dolby E Digital Audio Sample Rates 48kHz Digital Audio Resolution 16/24 Bits Disk Format Audio Output Timing Range + 5ms. , -11/15 ms. Serial Audio Output Timing Jitter < 500ps Linear Time Code SMPTE 12M, Balanced Impedance Vertical Interval Time Code SMPTE 266 compatible

Backplane Programming Entered command to program Backplane Serial Number & Revision Level: • set_bp –cPTIXXXXX –bYYY -rZZZ

Where X=AirSPACE Chassis Serial Number. Where Y=Backplane Serial Number. Where Z=Backplane Revision Level.


SECTION II: AirSPACE RAID File System RAID Level 3 Discussion & Disk Replacement Guidelines This section is intended to give the user background information on RAID Data Protection, and assist with AirSPACE failed drive replacement. The AirSPACE is designed with the prevention of data loss as a paramount system criterion. RAID Level 3 protection is provided on all system configurations. RAID parity protection simultaneously protects Audio, Video, and File System data, against any single drive failure in the array. The AirSPACE operating system is further protected with RAID Level 1, being mirrored on every drive. RAID Level 3 is defined as: "An array of (n + 1) disks recording 512 byte sectors on each of the (n) disks to create (n x 512) "super sectors", plus (1 x 512) "parity sector" on the additional disk which is used to check the data. The minimum unit of transfer is a whole superblock." RAID 3 is most suitable for systems in which large amounts of sequential data are transferred – such as for Audio and Video. Note the following operations regarding RAID Data Protection in the AirSPACE Server: • When an unrecoverable fault occurs (hard failure), the defective drive is identified via the red LED on the

SpacePod; the failure mechanism (diskfc) is recorded; and the drive is switched out of the array. • During the interval between a complete drive failure and the point at which the failed drive is rebuilt, system

performance will be impaired. Off-Speed Playback and Shuttle may not function at full resolution. • In the PLAY Mode, if a single drive fails to respond (Read) fast enough to provide the requested data, the

missing data is calculated from the parity information. A rebuild is not required. • In the RECORD Mode, if an individual drive fails to write its data in time and/or misses incoming data, a mini-

rebuild is required. The missing data is reconstructed, using the parity information, and written to that drive, immediately after the system becomes idle. The situation is noted in the runa log, and via the drives red Status LED. In the event of an unrecoverable error during recording, the system aborts the record and alerts the operator in both the error log and via an “Alert” dialog.

Note the following procedures regarding AirSPACE Rebuilds and Drive Replacements: • Do not swap drives around between slots in the array, while the system is powered on. The system will not

recover if this occurs, due to the fact that it sees a “multiple drive failure”. The ability to remove a failed drive, and replace it with a spare is defined as a Hot Swap. This action is permissible.

• The system begins to rebuild the missing data, automatically and immediately, if a qualified Hot Spare drive is installed. The system cannot rebuild to the boot drive. The rebuild is a background process, and does not interfere with Play/Record operations.

• While a drive is being rebuilt, both the BLUE and RED LED's on the SpacePod are ON. Upon completion of the rebuild, only the drives BLUE LED remains on, indicating that the rebuilt drive is now part of the array. A replacement for the failed drive may be installed at any time, before, during, or after the rebuild process. The replacement drive will automatically become the new Hot Spare. It is recommended that you replace a failed drive as soon as possible, and that you do not shut the system down during rebuilds. Operator intervention in the rebuild process is not required, except to replace a failed drive.

• A drive’s position in the physical disk array is not critical. The RAID system software determines what portion of the stripes is on each drive, and operates the array in the same manner regardless of drive position.


RFS Tools Introduction RFS, or Raid File System, is the partition on the AirSPACE server, which stores all of the Event and Playlist Meta-Data. This is known as partition g. Loss and/or corruption of the Meta-Data (partition g) will appear as a complete loss of media. As of software version 1.2.a23 (Referred to as the “V2 Feature Set) this Meta-Data along with all NVRAM parameters is backed up automatically. Upon boot, the system makes a working copy of RFS. This is what is used in the creation/deletion of events. RFS is updated when this working copy changes, and depending on the systems current work load, a RFS backup is created automatically. Prior to this version, saving the RFS information was a tedious, manual process. Although we have endeavored to provide an error free RAID protected system, random failures are beyond our control. For this reason we have added the auto-backup features described below, which should allow operations personnel to immediately restore backups of RFS and NVRAM settings.

Before using the following tools, you should be somewhat familiar with the AirSPACE product and its functionality. Basic knowledge and familiarity would include: Familiarity with the AirSPACE boot process, User Interface menus, logging into a shell from a command line and BSD-Unix command line entry. RFS Back-Up Files As mentioned above, each time the framework starts, it creates a fresh backup of RFS. These backup files are saved on the AirSPACE boot disk. Since AirSPACE can boot from disk A or C, it is possible to have backup files on either drive. The system defined, "best" backup is the one that was created most recently and that passes a simple sanity check. This backup is normally the best one to use because the MetaServer has checked and repaired the Meta-Data files as part of the start up process. (Thinking about the processes described below, one should see that “best backup” may not always be the file required. It is always best to check time/date stamps prior to restoring RFS.) The best_backup command, with no arguments, will search both drives, and print the pathname of the most recent backup. best_backup with -v (as in verbose) argument will list every backup directory it finds. Therefore, to create a backup that is perfectly in sync with the MetaServer, simply restart the framework. The framework may be restarted, by going to the Shutdown menu, selecting Restart User Interface and pressing OK. The newly created backup file will be located in:

/usr/home/pluto/RFSbackups/ There will be up to 4 backup files in this directory, named rfs.0 through rfs.3. Once in the RFSbackups directory, the ls -l command will list the files along with the associated creation dates, with rfs.0 being the most recent, and rfs.3 being the oldest.

Example:

air220:~{1} cd RFSbackups/air220:~/RFSbackups{2} ls -ltotal 4drwxrwxrwx 5 root wheel 512 Sep 17 10:23 rfs.0drwxrwxrwx 5 root wheel 512 Sep 17 10:22 rfs.1drwxrwxrwx 5 root wheel 512 Sep 16 16:38 rfs.2drwxrwxrwx 5 root wheel 512 Sep 16 16:34 rfs.3air220:~/RFSbackups{3}


rfs_restore This primary tool creates, deletes, and reads RFS restore records in NVRAM (the RRR record). To read the existing RFS restore record (if any), use rfs_restore with no arguments: rfs_restoreIf there is no restore record, the system responds: No RFS restore record

Should there be an existing RRR record it prints the date the record was created; which tool created the record (rfs_restore -b, or the framework), and the pathname of the backup directory which was restored:

RFS restore record created <date>Record created by this tool.Backup directory: <name of backup directory>

rfs_restore -d Prior to restoring a corrupt RFS partition, it may be necessary to delete any existing restore record (RRR record) in NVRAM. If there is already a RFS restore record loaded, it will not be automatically overwritten and you will see an error message. If you need to change a RFS restore record, you must first delete the existing record, as follows, before creating the new one: rfs_restore -d If there is a RFS restore record, it will be displayed and you will be asked to confirm the deletion, as follows:

RFS restore record created <date>Record created by this tool.

Backup directory: <name of backup directory>This RFS restore record is about do be deleted.

Is that OK? <y/n>yRFS restore record deletedNo RFS restore record

Restoring Corrupt RFS & NVRAM Let us assume that a catastrophic hardware failure caused the loss and/or corruption of the RFS partition (g) and/or the contents of NVRAM. To the operator, (if the system boots up) it will appear that the media is lost, as there are no clips visible in the Event Database. The AirSPACE may boot to the User Interface, or hang at the message: rfs not setup correctly. Call Tech Support. In addition, a message indicating a problem with NVRAM may look like: machine inoperable. Call Tech Support.

To correct this situation, and first initialize NVRAM: • From the Shutdown Menu, select Reboot Entire System. If the User Interface is down, login as

maint, with password mars. At the prompt, type reboot, followed by the Enter key. • At the AirSPACE splash screen, press the Num Lock key to drop this screen. • Watch for the message: Press ENTER to inhibit the framework. You will have approximately

3 seconds to respond, by pressing the Enter key. If successful, the system should reply: DO NOT STARTFRAMEWORK!

These commands are followed by the Enter key: • If not already logged in from above, login as: maint password: mars• At the command prompt, type: kbs • At the command prompt, type: init_nvram • Confirm the y/n dialog, and press the Enter key.


To restore corrupt RFS (partition g) and NVRAM: • At the command prompt, type: cd RFSbackups • At the command prompt, type: rfs_restore -b `best_backup` (Note: The single quotes around

`best_backup` are back quotes. It is likely one may have to substitute `best_backup` with rfs.0, rfs.1, etc.)

This restore command will do three things. (1) When NVRAM is restored the ACR (Array Configuration Record) is written; (2) the rfs (g) partition is zeroed; and (3) the rfs restore record (RRR Record) is written to NVRAM. NVRAM is written to insure that the meta-data files are consistent with the Array Configuration Record, and the Video Format. This process will result in a complete restoration of the machine-state stored in the specified backup, including the contents of NVRAM. • At the command prompt, type: reboot • As the framework is coming up, you will see the message:

About to restore RFS from back-up directory:usr/home/pluto/RFSbackups/<backup file name>Use kbs to stop the restore. (Not recommended.) Restore begins in 30 seconds: 30

Following the 30-second countdown, the User Interface should reappear. All events, playlists, and operational parameters should be restored.

Using readnvlog The AirSPACE keeps a log of critical events in NVRAM (the ETS Record). Basically, anything that affects the setup of RFS is logged. These are zeroPartition (g or d), write_acr, fix_acr, restore_nvram, rfs_restore, as well as restoring RFS from an RFS restore record. This log is used by the software to determine if RFS has been set up correctly, and as a record of critical events for debugging any RFS problems. The readnvlog command prints the contents of this log, sorted by time. Following, is an example readout:

02/23/2000 09:59:58.313913 restore_nvram02/23/2000 10:07:08.446296 fix_acr02/23/2000 15:35:19.568319 rfs restored02/23/2000 15:40:52.430163 rfs restored02/23/2000 15:54:42.670449 rfs restored02/23/2000 16:03:58.366468 rfs restored02/28/2000 15:03:00.894850 rfs_restore_rec02/28/2000 15:04:24.161899 rfs_restore_rec02/28/2000 16:41:05.687325 rfs_restore_rec03/02/2000 09:07:32.606107 rfs_restore_rec03/02/2000 09:08:28.793511 rfs restored03/02/2000 10:22:24.401822 fix_acr


SECTION III: AirSPACE Disk Diagnostic Tools

The following tools may be used in diagnosing problems with AirSPACE Disk Drives; RFS; and the RAID Array. All commands are executed from a console window, following login.

show_acrThis command will display the RAID Array Configuration Record which indicates drive mapping and status within the AirSPACE array. This is the ACR Record (Entry 2) from NVRAM. NOTE: Use keyboard “Scroll Lock” to view the entire ACR.

Entered Command: show_acr Example ACR:

DISK0(A) P0 0 B| DISK5(F) P0 5 | DISK10(K) P0 10 | DISK15(P) P0 15IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170NZD140767 | ZD13W524 | ZD13P693 | ZD140523

---------------------------------------------------------------------------DISK1(B) P0 1 | DISK6(G) P0 6 | DISK11(L) P0 11 | DISK16(Q) P0 16IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170NZD140999 | ZD141380 | ZD139674 | ZD140877

--------------------------------------------------------------------------DISK2(C) P0 2 | DISK7(H) P0 7 | DISK12(M) P0 12 | DISK17(R) P0 17IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170NZD140601 | ZD13X988 | ZD140766 | ZD13J385

--------------------------------------------------------------------------DISK3(D) P0 3 | DISK8(I) P0 8 | DISK13(N) P0 13 | DISK18(S) P0 18IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170NZD13K310 | ZD141258 | ZD140606 | ZD13T699

---------------------------------------------------------------------------DISK4(E) P0 4 | DISK9(J) P0 9 | DISK14(O) P0 14 | DISK19(T) UIBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170N | IBM DPSS-309170NZD141219 | ZD140933 | ZD140509 | ZD13J044

Interpreting The ACR 1. The first line in each drive table is the:

• Disk0(A) through Disk19(T) is the drive’s physical location. • P0 indicates the drive is included in the RAID configuration. • The drive’s Virtual Location (0-18) in the Array. • U signifies the drive is the unused Hot Spare. • X would indicate that a drive is not installed (or not communicating due to failure). • B identifies the drive as the current Boot Drive. Either of drives A or C could be the boot drive.

2. The second line of the block is the drive type, in this case an IBM 9GB.

3. The third line is the drive manufacturers serial number. An FC=XXXX on this line, indicates a failed drive.

Use show_diskfc as described in later in this section, for the meaning of the failure code. Related Commands: read_acr (Same as show_acr, only in list format.)


list_disksThis command will display a list of all disk drives, by Manufacturer and Model Number, currently qualified by Avid Technology for use within the SPACE Platform. If a drive is not listed here, it will not operate within the AirSPACE or VideoSPACE.

Entered Command: list_disks Example Result: PLUTO Supported Disks Drives

Size Vendor Product ID1 GB: SEAGATE ST31055N (VideoSPACE Only!)2 GB: SEAGATE ST32155N (VideoSPACE Only!)2 GB: QUANTUM FIREBALL ST2.1S (VideoSPACE Only!)2 GB: SEAGATE ST32272N (VideoSPACE Only!)4 GB: SEAGATE ST34371N (VideoSPACE Only!)4 GB: SEAGATE ST34572N (VideoSPACE Only!)4 GB: SEAGATE ST34573N (VideoSPACE Only!)4 GB: IBM DDRS-34560 (VideoSPACE Only!)4 GB: SEAGATE ST34501N (VideoSPACE Only!)9 GB: SEAGATE ST19171N (VideoSPACE Only!)9 GB: SEAGATE ST39173N (VideoSPACE Only!)9 GB: IBM DDRS-391309 GB: IBM DNES-309170?9 GB: IBM DPSS-309170?

18 GB: IBM DGHS18Z18 GB: IBM DNES-318350?36 GB: IBM DRHS36V36 GB: IBM DPSS-336950N73 GB: SEAGATE ST173404LW

181 GB: SEAGATE ST1181677LWV

show_diskfcThis command, with the proper arguments, will display a glossary of known four-digit Disk Failure Codes. A failed drive will have a four-digit code, i.e. FC=1505, associated with it, once RAID fails the drive. The meaning of this failure may be found with these commands:

Entered Command: show_diskfc ALL

Successful Result:

FC 1000: Disk not installed or removedFC 1001: Disk failure forcedFC 1010: Unsupported disk typeFC 1011: Invalid disk target id, must be 0FC 1012: Disk revision not supportedFC 1020: Weighted error count threshold exceededFC 1021: Glist threshold exceeded, to many media defectsFC 1022: Recovery List count exceededFC 1030: Unknown deferred error returnedFC 1040: Disk does not have a valid disklabelFC 1041: Disk has an invalid disklabelFC 1100: SCSI adapter hardware failureFC 1200: Disk hardware errorFC 1204: Disk reported hardware errorFC 1210: Disk hardware error, reties exaustedFC 1210: Disk reports not readyFC 1300: Firmware errorFC 1305: Firmware error, invalid CDBFC 1400: Disk permanent errorFC 1403: Disk media error


FC 1500: Received unexpected sense keyFC 1505: Received unexpected sense key 5, Illegal RequestFC 1507: Received unexpected sense key 7, Data ProtectFC 1508: Received unexpected sense key 8, VUFC 1509: Received unexpected sense key 9, Firmware ErrorFC 150a: Received unexpected sense key A, VUFC 150c: Received unexpected sense key C, Search EqualFC 150d: Received unexpected sense key D, Volume OverflowFC 150e: Received unexpected sense key E, MiscompareFC 150f: Received unexpected sense key F, VUFC 1600: Received unexpected response from adapter/driverFC 1700: Retries exhaused for sense keyFC 1702: Retries exhaused for sense key 2, Not ReadyFC 1704: Retries exhaused for sense key 4, Hardware errorFC 1706: Retries exhaused for sense key 6, Unit AttentionFC 170b: Retries exhaused for sense key B, Aborted CommandFC 1800: Retryable driver errorFC 1801: Retries exhaused for CDBFC 1810: Disk Queue fullFC 1811: Driver sent BDRFC 1900: Unknown error code

Related Commands: show_diskfc XXXX (Where XXXX is the Failure Code read from the AirSPACE ACR.)

read_dfr diskNumber XX (Where XX is the physical disk location, 0 through 19.)


updSpaceThis command will copy the OS partitions from the boot disk to all drives configured in the array. The hot spare is not affected by this command. This script is also run from the User Interface SOFTWARE UPDATE Menu, by selecting Copy to All Drives.

Entered Command: updSpace Example Result:

usage: kill [-s signal_name] pid ...kill -l [exit_status]

kill -signal_name pid ...kill -signal_number pid ...

Scanning...Found 19 of 19 disks listed in ACRScanning...Found 19 of 19 disks listed in ACRCopying 'a' partition from disk 0 to 18 target disksScanning...Found 19 of 19 disks listed in ACRCopying 'e' partition from disk 0 to 18 target disksScanning...Found 19 of 19 disks listed in ACRCopying 'f' partition from disk 0 to 18 target disks** /dev/rsd18a** Last Mounted on /** Phase 1 - Check Blocks and Sizes** Phase 2 - Check Pathnames** Phase 3 - Check Connectivity** Phase 4 - Check Reference Counts** Phase 5 - Check Cyl groups2029 files, 17644 used, 14099 free (35 frags, 1758blocks, 0.1% fragmentation)

***** FILE SYSTEM MARKED CLEAN ******* /dev/rsd18e** Last Mounted on /usr** Phase 1 - Check Blocks and Sizes** Phase 2 - Check Pathnames** Phase 3 - Check Connectivity** Phase 4 - Check Reference Counts** Phase 5 - Check Cyl groups3210 files, 113792 used, 74751 free (303 frags, 9306blocks, 0.2% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****updSpace completed, elapsed time: 1 mins, 17 secs


copyGoldDiskThis command will initiate a script which will copy the AirSPACE OS partitions (a, e, and f) from any “Source” drive to any “Target” drive. Audio and Video partitions are not copied. See Section IV, Software Upgrades.

Entered Command: copyGoldDisk 0 19 (This example copies OS from Drive 0 to Drive 19.)

Example Result: Copy Gold Disk 0 (BLUE led on) to Disk 19 (BOTH ledson) [y/n]?

Confirmation: y Example Result: Disk 19 is valid type (9 gig), writing disklabel

prod_disk.9gigCopying 'a' partition from disk 0 to disk 19Copying 'e' partition from disk 0 to disk 19Copying 'f' partition from disk 0 to disk 19/dev/rsd19a: 2071 files, 19454 used, 12289 free (33frags, 1532 blocks, 0.1% fragmentation)/dev/rsd19e: 3656 files, 128730 used, 59813 free (333frags, 7435 blocks, 0.2% fragmentation)/dev/rsd19f: 25 files, 2506 used, 13341 free (13frags, 1666 blocks, 0.1% fragmentation)copyGoldDisk completed, elapsed time: 0 mins, 47 secs

fsckIf the AirSPACE is not properly halted via the SHUTDOWN Menu, or command line, portions of the OS may become corrupt, preventing a successful boot. The system will indicate this condition by issuing message: Enter pathname or Return for sh. The system will be hung, awaiting user intervention.

Enter Command: Hit the RETURN Key.

(Note the shell command prompt change, and run the following:)

Enter Command: fsck –y /var (Runs fsck against the /var directory.) Enter Command: fsck –y /usr (Runs fsck against the /usr directory.) Enter Command: fsck –y / (Runs fsck against the root directory.)

NOTE: One or more of the above directories may have become corrupt, such that when fsck finds stray pointers, it will respond that the file system has been modified. Following completion of fsck, type exit, and reboot.


Disk Drive Re-qualification

THESE TESTS ARE DESTRUCTIVE! ALL DATA ON THE TEST DRIVE WILL BE LOST!

The following routines allow the AirSPACE user to re-qualify possible faulty disk drives currently installed in the system. A show_acr command should point to the physical locations of the system drives, allowing the user to identify the suspect drive location. It is not possible to run a burn test on the AirSPACE boot drive, unless you first swap the boot drive with another drive in the array. Typical Burn Test times are as follows: • AirSPACE AS-12 9GB Drives: 7.5 - 8 Hours • AirSPACE AS-24 18GB Drives: 11 – 12 Hours • AirSPACE AS-48 36GB Drives: 18 – 24 Hours • AirSPACE AS-96 73GB Drives: 24 Hours

To prevent the loss of data, it is possible to burn test one drive with the framework down; power cycle the AirSPACE, such that the system sees the re-qualified drive as “failed”; then allow the system to rebuild the lost data to the hot spare. Once the first rebuild is complete, RAID will drop the hot spare into the array; and the re-qualified drive would then become the new hot spare. This process could then be repeated to re-qualify a second drive.

Running the Drive Re-qualification Routines All commands are run from a console window, and are executed with the ENTER key. The BLUE LED on the drive under test will be flashing, indicating the burn test routine is running. These tests cannot be run with the system “ON-AIR”.

• Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type cd and press ENTER. Burn Tests should be run from ~ (root). • At the command prompt, type kbs and press ENTER. • At the command prompt, type the desired test shown below, followed by the ENTER key.

burnTest BEWARE! This command will initiate a Burn Test any individual drive. Slightly modified, it will test a group of drives.

Entered Command: burnTest XX (Where XX is the physical location of the drive, 01-19.) Entered Command: burnTest XX& (Followed by ENTER.)

burnTest YY& (Followed by ENTER.)burnTest ZZ& (Followed by ENTER.)

(Where XX, YY, and ZZ, are the physical location of a group of drives.)


burnAll BEWARE! This command will initiate a Burn Test on ALL drives in the system: Entered Command: burnAll

Example Result: Starting burnTest on disk1 Starting burnTest on disk2

Starting burnTest on disk3Starting burnTest on disk4

Starting burnTest on disk5Starting burnTest on disk6Starting burnTest on disk7

Starting burnTest on disk8Starting burnTest on disk9Starting burnTest on disk10Starting burnTest on disk11Starting burnTest on disk12

Starting burnTest on disk13Starting burnTest on disk14Starting burnTest on disk15

Starting burnTest on disk16Starting burnTest on disk17Starting burnTest on disk18Starting burnTest on disk19

Interpreting the Burn Test Results Once a drive has completed a burn test, the record is written as a text file to the AirSPACE directory from which the test was run. The file name is the drive serial number, with an extension of .XX, where XX is the physical drive location (01-19) within the array. To view the Burn Test Records: (1) Login to the system with maint and mars. Type cd. Press ENTER. (2) Type ls to list the contents of the root directory (assuming the tests were run from root). Press ENTER and note the Burn Test Records. (3) Type cat XXXXXXXX.XX, followed by the Enter key. (Where XXXXXXXX.XX is the desired Burn Test

record.) See examples below:


Example FAILED Burn Test Record: Note the Glist entries at the end of the file.

Entered Command: cat BZ12M820.01

Disk Vendor: IBM Disk Type: DPSS-336950NDisk Serial Number BZ12M820The Disk slot to be tested is 1Start time: Wed Apr 25 07:55:04 2001Starting iteration 1 of 4Writing Data Pattern for Sequential Forward sequenceReading Data Pattern for Sequential Forward sequence: Pass 1 of 2Reading Data Pattern for Sequential Forward sequence: Pass 2 of 2Spin Up/Down Test PassedWriting Data Pattern for Sequential Reverse sequenceTimeout on LBA 18479488 io 419464Reading Data Pattern for Sequential Reverse sequence: Pass 1 of 1Starting iteration 3 of 4Writing Data Pattern for Random sequenceTimeout on LBA 5908480 io 11998Timeout on LBA 23227264 io 28469Timeout on LBA 14659968 io 195947Timeout on LBA 60374016 io 227414Timeout on LBA 31480448 io 266012Timeout on LBA 64827008 io 287589Timeout on LBA 59697408 io 340302Timeout on LBA 46832000 io 349277Timeout on LBA 8937600 io 434257Timeout on LBA 69405184 io 443486Timeout on LBA 46208256 io 534851Reading Data Pattern for Random sequence: Pass 1 of 1Starting iteration 4 of 4Writing Data Pattern for Butterfly sequenceRetryable error 0x153 on LBA 59814528 io 193068Drive reported unit attention or not readyDisk retryable error. Sense:(pass1:ahc1:0:0:0): WRITE(10). CDB: 2a 0 0 bc 8b 0 0 0 80 0(pass1:ahc1:0:0:0): UNIT ATTENTION asc:29,3(pass1:ahc1:0:0:0): Bus device reset function occurredTimeout on LBA 57339264 io 231744Timeout on LBA 53158784 io 297064Timeout on LBA 52050816 io 314376Timeout on LBA 51183232 io 327932Timeout on LBA 50601088 io 337028Reading Data Pattern for Butterfly sequence: Pass 1 of 1Completion time: Wed Apr 25 23:56:30 2001Total test time: 16:1:26The burnTest has failed

The disk has 0 reassigned LBAsThe disk had 17 command timeoutsThe disk had 0 recovered data errorsThe disk had 1 retryable errorsThe disk had 0 SCSI bus resets


Example PASSED Burn Test Record: Note the Glist entries at the end of the file.

Entered Command: cat E155128.01 Disk Vendor: IBM Disk Type: DDRS-39130Disk Serial Number E155128The Disk slot to be tested is 1Start time: Fri Oct 6 11:32:20 2000Starting iteration 1 of 4Starting iteration 1 of 4The drive has 9 Glist entriesWriting Data Pattern for Sequential Forward sequenceReading Data Pattern for Sequential Forward sequence: Pass 1 of 4Reading Data Pattern for Sequential Forward sequence: Pass 2 of 4Reading Data Pattern for Sequential Forward sequence: Pass 3 of 4Reading Data Pattern for Sequential Forward sequence: Pass 4 of 4Spin Up/Down Test PassedSCSI bus reset Test PassedStarting iteration 2 of 4The drive has 9 Glist entriesWriting Data Pattern for Sequential Reverse sequenceReading Data Pattern for Sequential Reverse sequence: Pass 1 of 3Reading Data Pattern for Sequential Reverse sequence: Pass 2 of 3Reading Data Pattern for Sequential Reverse sequence: Pass 3 of 3Spin Up/Down Test PassedSCSI bus reset Test PassedStarting iteration 3 of 4The drive has 9 Glist entriesWriting Data Pattern for Random sequenceReading Data Pattern for Random sequence: Pass 1 of 2Reading Data Pattern for Random sequence: Pass 2 of 2Spin Up/Down Test PassedSCSI bus reset Test PassedStarting iteration 4 of 4The drive has 9 Glist entriesWriting Data Pattern for Butterfly sequenceReading Data Pattern for Butterfly sequence: Pass 1 of 1Spin Up/Down Test PassedSCSI bus reset Test PassedCompletion time: Fri Oct 6 19:21:36 2000Total test time: 7:49:16

The burnTest has passedThe disk has 9 reassigned LBAsThe disk had 0 command timeoutsThe disk had 0 recovered data errorsThe disk had 0 retryable errorsThe disk had 0 SCSI bus resets


SECTION IV: AirSPACE Software Update Procedures Preliminary Procedures All commands are followed by the Enter key. These procedures cannot be run with the system “on-air”. Irrespective of the method of updating perform the following steps: • Verify that the AirSPACE is booted from Drive A, if not halt the AirSPACE and cycle power. • From the user interface, enter the Set-up Menu and Software Update Sub-menu. • Click “Copy To All Drives”, to copy the current OS and RFS Back-ups to all drives in the array. • Once the copy is complete, go to a console window with Ctrl+Alt+F1. • Login maint, password mars • Confirm the Spare Drive location. Look for the drive with no blue led on, or type show_acr and look for the

drive marked “U”. • Type copyGoldDisk 0 n, where n is the physical location of the Spare Drive. • Check the led indication and confirm the y/n dialog. There is now a copy of the existing OS on all the drives in the AirSPACE. User Interface Based Updates There are essentially two methods of updating from the User Interface: Network Update and CD-ROM Update. Network Update There are two variants of network updates; direct network and modem. Essentially the methods are the same. A modem update is simply a means of establishing a network connection when no direct connection is available. Even if the unit is connected to a house network that has internet access it may not be possible to carry out the update. This is almost certainly due to firewall restrictions at the user site. How Do I Know When A Network Connection Will Work? If the unit is known to be on an internet accessible network click the “Retrieve Versions” button in the Software Update menu. After a short interval a list of software versions available for download is displayed. Should it not be possible to retrieve the versions, even after two or three attempts, it is very likely that network access is blocked. In this case it will be necessary to establish a modem connection. Making The Modem Connection: Just click the “Modem Update” button and scroll down the list of displayed numbers to find a local number for your location. Edit the dial string if needed, for example to add an outside line access digit. Click “Dial”. If all is well the message “Connection Established” will be displayed in the status window. • Note that the only external modem found, which gives reliable results is a US Robotics 56k. Identifying The Version For Update: Once a network connection is established clicking “Retrieve Versions” will display a list of software releases available. Note that these are officially released versions. If a non-release (Alpha/Beta) version is required, press Ctrl+a before clicking “Retrieve Versions”. • Note that it is not a good idea to download one of the non-release versions without having first established

which are suitable for customer use.


Updating The Boot Drive: Once the list of releases has been obtained simply locate and hi-light the version required. Click “Update Boot Drive”; confirm the action in the dialog that follows; and allow the update to proceed to its conclusion. This process will take anything from a few tens of seconds to possibly an hour, depending on how much of the operating system has been changed, and how fast the network connection is. When the update is complete a dialog will be displayed, with a message prompting the user to “Wait 2 minutes, and power cycle the AirSPACE”. Once power cycled, the AirSPACE should boot to the User Interface.

CD-ROM Update Updating AirSPACE with a CD-ROM is a straight forward process providing that the various steps are followed in the correct order. Make sure that you have the CD-ROM drive connected to the rear SCSI connector; that it is set to a SCSI ID 1; is powered up; and that the CD is inserted. If the CD-ROM drive was not connected before the AirSPACE was booted it may be necessary to reboot the system in order that the CD-ROM is recognized. Once the drive is connected and “ready”, click “CD-ROM Update”, and follow the prompts that are displayed. The update process will take approximately 3 to 4 minutes, after which the user should halt the AirSPACE. Drives A and C must then be physically exchanged, after which the unit can be rebooted. If the update was successful the AirSPACE will be running on the new software, which can be checked in the Version/License Info Menu.

Following the CD-ROM Update: Once the unit is running satisfactorily on the new software go to the Software Update Menu, and click “Copy To All Drives”. • NOTE: The distributed AirSPACE NP software CD also contains installers for:

AvidNetAvidNet NTNewsCutter 1.5SpaceNet (LaunchPad & Mission Control)

CountDown AirSPACE NT & Windows 2000 Downloads: Downloads of the AirSPACE NT/Windows 2000 Applications and CountDown can also be obtained from the field at the following link: ftp://pluto:[email protected]/outgoing/

NOTE: CountDown requires a license for both the AirSPACE Server and PC. Contact Technical Support for

additional information.

A C

ftp://ftp.plutotech.com/pub/outgoing/put/

24 •

“Gold Disk” Update A “Gold Disk” update is a convenient means of updating the software when neither of the previous methods is available. This may be because it is not possible to obtain a CD in time to perform the update, and there is no network connection available. It also represents a speedy means of updating a number of units. There are essentially two Gold Disk update scenarios: Updating A Unit From A “Gold Disk”: This method is used whenever a unit is to be updated from a Gold Disk that has been prepared in advance. This may be by copying software to a drive specifically for the purpose, or taking along a drive temporarily removed from another unit which already has the desired software installed. Before starting the update make sure that the existing OS has been copied to all the drives on the target unit, including the spare drive. (See “Preliminary Procedures”, at the beginning of this section for instructions.) While there are a number of variations on the way in which the Gold Disk is used they all follow the same procedures: • Boot the target AirSPACE from the Gold Disk, with the original boot drive in the Spare location. • Copy the OS to the original boot drive. • Shutdown the system and restore the drives to their original locations. • Reboot the AirSPACE and “Copy To All Drives”. Refer to the diagram, below: • Halt the AirSPACE. • Locate and remove the Spare drive. These notes assume that it is Drive 19(T). • Remove boot Drive 0(A) and place it in the Spare location. • Place the Gold Disk in the Drive 0(A). • R• W• Lo• Ty• C• O

Ai

Replace

Move b

Put Gold Diskin Drive 0(A).

eboot the AirSPACE. When the splash screen appears press the NumLock key. atch for the message “Press Enter to inhibit Framework” and press Enter at that time. gin using maint and mars. pe copyGoldDisk 0 n, where n is the physical location of the Spare drive.

heck the led indication and confirm the y/n dialog. nce complete, halt the AirSPACE, and restore all drives to their original locations. Power cycle the rSPACE..

Remove Spare.

oot drive to Spare.

Remove GoldDisk.

Maintenance & Diagnostics Version 2.02 Avid Technology, Inc.

Replace Spare.

original boot drive.


Updating A Boot Drive From Another Unit: This method is used when one unit has been updated and a number of other units at the same location are to be updated to the same software version. The unit(s) to be updated will be referred to as the Target unit(s); the unit having the required software revision as the Source. The steps to follow are: • If the Source AirSPACE is up and running you should login from a console, and halt the framework. To halt

the framework, type kbs, followed by the Enter key. • Halt the Target AirSPACE from its User Interface. • Remove the Spare drive from the Source AirSPACE, and replace it with the Target AirSPACE boot drive.

• On the Source unit type spinUp 20 and wait for the p• Type copyGoldDisk 0 19, check the led indication• Once the copy completes, return the updated disk to

Target AirSPACE(s). • Repeat this process for other Target AirSPACE units. • Replace the Spare drive in the Source AirSPACE. • If the Source unit is required to be operational type “reb Following the “Gold Disk” Update: Once the unit is running satisfactorily on the new software All Drives”. What If There’s A Problem With The New Software? In the unlikely event of a serious problem the previous versi • Halt the AirSPACE. • Exchange the boot drive (Drive 0(A)) and the Spare driv• Power cycle the AirSPACE. • From the Software Update Menu, select “Copy To All • Exchange the boot drive (Drive 0(A)) and the Spare driv• Power cycle the AirSPACE. NOTE: Downgrading software is not recommended, an

Remove Source Spare.

Source AirSPACE Target AirSPACE

.
Move Target Boot Drive to Spare

rompt and confirm the y/n dialog. the Target AirSPACE boot drive location. Reboot the

oot” to restart the system.

go to the Software Update Menu, and click “Copy To

on of software can be restored with the following steps:

e.

Drives”. Once complete, halt the AirSPACE. e.

d could possibly result in loss of media.


SECTION V: Destructive Commands The AirSPACE toolset contains a number of commands and scripts, many of which are intended for use only during the manufacturing stage. In the field, it may be necessary to initiate these routines following replacement of a Motherboard (MOAB), or to solve a problem with the RAID array. These commands are embedded in the AirSPACE OS (in addition to the previously described tests), and are not “hidden” from the average user. The AirSPACE OS is BSD-Unix. UNIX is not forgiving of mistakes. There is no “UNDO”.

THE FOLLOWING COMMANDS ARE INTENDED FOR QUALIFIED SUPPORT PERSONNEL!

These commands are deadly, and could destroy the meta-data pointers to the media on the array. No further explanation will be given in this document. In other words:

EXECUTING THESE COMMANDS MAY DESTROY ALL MEDIA ON THE SERVER.

All CAUTIONS having been said, and as a courtesy to the curious, do NOT execute these commands unless specifically instructed to do so, by a qualified engineer! init_nvramdelete_nvramwrite_acrfix_acrzeroPartitioncopyPartitionmsc_keybldSpaceprog_dspremoveclipsrfs_restorewriteFirmwarewriteAllFirmware

All previously described burnTest commands are also destructive. And there may be more. Never initiate a command unless you know what it will do. Unless you are an above average UNIX user, with knowledge of the consequences (like the system hanging at boot, because it cannot find a file); and have a good idea of what you are doing, it is not a very good idea to: Rename files or directories.Remove files or directories.Move files or directories.Copy files or directories.Create new files or directories.


SECTION VI: Single Board Computer (SBC) Diversified Technologies 450M Single Board Computer The first generation of AirSPACE contains a 450Mhz Pentium II, Single Board Computer, with 128MB of RAM. BIOS VERSION: To view the SBC BIOS settings, power on the AirSPACE Chassis. As the system is booting, the BIOS version should appear:

PhoenixBIOS 4.0 Release 6.0LBC8523 rls 2.0127M Extended RAM Passed

SYSTEM SUMMARY: While the initial boot screen is displayed, press F2 to enter the Set-Up Menu. The summary table should show the following settings:

Diversified Technology, Inc. – LBC8523Pentium II: 450MHz Diskette A: DisabledSys Ram: 640 KB Diskette B: DisabledExt Ram: 130048 KB Hard Disk0: NoneShadow Ram: 384 KB Hard Disk1: NoneCache Ram: 512 KB Comm Ports: 3F8 2F8Display: EGA / VGA LPT Ports: 378BIOS Date: 05/18/99 PS/2 Mouse: InstalledSystem ROM: EBCC-FFFF Volts (-5): -0.00vVolts (+5): +5.00v (-12): -11.98v(+12): +11.85v (+2.5) +2.49v(+3.3): +3.29v CPU1 Temp: +86C(CPU1): +1.97v Sys. Temp: +68C

NOTE: Any supply voltages and/or temperature settings which show a significant variation from the above values, may indicate a problem with the SBC Board; CPU Fan; or AirSPACE Power Supplies. LOADING SBC SETUP DEFAULTS: The following procedure will load the Single Board Computer BIOS Defaults. NOTE: Under normal operation, BIOS settings other than the “set-up defaults” should never be required. • Press ESC, and select F10 to bring up the EXIT Menu. • Arrow key down to Load Setup Defaults, and press ENTER. • Arrow key to [Yes], and press ENTER. • Arrow key to Exit Saving Changes, and press ENTER. • Arrow key to [Yes], and press ENTER. The system will resume the normal boot sequence with the SBC BIOS set for proper operation.


Diversified Technologies 700M Single Board Computer: The second generation of AirSPACE contains a 700Mhz Pentium III or AMD K6, Single Board Computer, with 128MB of RAM.

BIOS VERSION: Power on the AirSPACE Chassis. As the system is booting, the BIOS version should appear:

PhoenixBIOS 4.0 Release 6.0LBC8716 rls 1.1127M Extended RAM Passed

SYSTEM SUMMARY: While the initial boot screen is displayed, press F2 to enter the Set-Up Menu. The summary table should show the following settings:

Diversified Technology, Inc. – LBC8716Pentium III: 700MHz Diskette A: DisabledSys Ram: 640 KB Diskette B: DisabledExt Ram: 130048 KB Hard Disk0: NoneShadow Ram: 384 KB Hard Disk1: NoneCache Ram: 256 KB Comm Ports: 3F8 2F8Display: EGA / VGA LPT Ports: 378BIOS Date: 01/12/00 PS/2 Mouse: InstalledSystem ROM: ECC3-FFFF Volts (-5): -0.00vVolts (+5): +5.00v (-12): -11.98v(+12): +11.85v (+2.5) +2.49v(+3.3): +3.29v CPU1 Temp: +86C(CPU1): +1.97v Sys. Temp: +68C

NOTE: Any supply voltages and/or temperature settings which show a significant variation from the above values, may indicate a problem with the SBC Board; CPU Fan; or AirSPACE Power Supplies. LOADING SBC SETUP DEFAULTS: The following procedure will load the Single Board Computer BIOS Defaults. NOTE: Under normal operation, BIOS settings other than the “set-up defaults” should never be required. • Press ESC, and select F10 to bring up the EXIT Menu. • Arrow key down to Load Setup Defaults, and press ENTER. • Arrow key to [Yes], and press ENTER. • Arrow key to Exit Saving Changes, and press ENTER. • Arrow key to [Yes], and press ENTER.

The system will resume the normal boot sequence with the SBC BIOS set for proper operation.


Setting the System Time/Date: Setting the System Time: The SBC System Time should always be set to GMT (Greenwich Mean Time). The AirSPACE should then be localized, as described in the following section. The AirSPACE System Time/Date is normally set to GMT prior to shipment. NOTE: These settings cannot be run with the system “ON-AIR”. • Via the Shutdown Menu, select “Reboot Entire System”. While the initial boot screen is displayed, press F2

to enter the BIOS Menu. • Once the System Summary screen appears, select F2 for System Setup. The following should be displayed:

System Time: 15:03:56 System Date: 05/19/2000

PS/2 Mouse: Auto Detect

Diskette A: DisabledDiskette B: Disabled

• Press Enter, to move the cursor to the System Time field. • With the keypad, enter the correct GMT hour, and press Enter. • With the keypad, enter the correct GMT minute, and press Enter. • With the keypad, enter the correct GMT seconds, and press Enter.

Setting the System Date: As with the System Time, the SBC System Date should always be set to GMT.

• From the System Time field, down arrow to the System Date field. • With the keypad, enter the correct GMT month, and press Enter. • With the keypad, enter the correct GMT day, and press Enter. • With the keypad, enter the correct GMT year, and press Enter. • Press the Esc key, and select F10, for the Exit Menu. • Arrow key to Exit Saving Changes, and press ENTER. • Arrow key to [Yes], and press ENTER.

Allow the system to boot to the User Interface, and proceed to the “Localizing AirSPACE” procedure.


Localizing AirSPACE: “Localizing” the AirSPACE ensures that all system generated logging and back-up files will reflect the correct time/date stamps. NOTE: This procedure cannot be run with the system “ON-AIR”. • Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type cd /usr/share/zoneinfo, and press Enter. • Type ls, and press Enter. The following list should be displayed: Africa Asia CST6 CDT Etc HST MST7 MDT WETAmerica Atlantic EET Europe Indian PST8 PDT posixrulesAntarctica Australia EST Factory MET Pacific zone.tabArctic CET EST5 EDT GMT MST SystemV

• Find the correct “continent”, or “zone” for your specific locale from the above list. • At the command prompt, type cd <Continent or Zone>, and press Enter. (For example, if your

continent is “America”, you would type cd America, followed by Enter.) • At the /usr/share/zoneinfo/America prompt, type ls and press Enter. • Choose the closest city file to your location. If you are in New York, you would select the New_York file. • At the next command prompt, type:

cp /usr/share/zoneinfo/America/New_York /etc/localtime. • Press Enter. Following a return to the command prompt, this will have copied the New_York file to the

localtime file in the /etc directory. • At the command prompt, type reboot, and press the ENTER key. Allow the system to boot to the User

Interface. The correct time of day should be displayed on the dashboard.

Single Board Computer / Motherboard Functional Tests All user interaction with the AirSPACE system may also be done as a telnet session, via modem.

GENERIC COMMANDS & HOT KEYS Ctrl+Alt+F1 Drops User Interface and opens a console window. Ctrl+Alt+F2 Opens a second console window. maint AirSPACE system login. mars AirSPACE system password. kbs Followed by ENTER. Drops framework and creates a lock file in

/var/tmp. Required prior to running any functional tests. rm /var/tmp/lock.runbs Followed by ENTER. Removes /var/tmp/lock.runbs file

and restarts the framework and User Interface. cd Returns to (~) root directory. Ctrl+c Terminates a test routine or “hung” condition and returns the user

to the command prompt. Ctrl+Alt+F3 Returns to User Interface from command mode. xilinx_eram Followed by ENTER. If the normal boot sequence was

interrupted by inhibiting the framework, execute this command prior to running the first test.


RUNNING THE SBC/MOTHERBOARD TEST ROUTINES All commands in this procedure are executed with the ENTER key. These tests cannot be run with the system “ON-AIR”.

• Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type kbs and press ENTER. • At the command prompt, type the desired test, followed by the ENTER key.

moabDmaThis command verifies the ability to perform DMA burst transfers to and from all combinations of data paths.

Entered Command: moabDma

Successful Result: Moab DMA Test PPN 001-915 Rev E

eram0 - ch0 to eram1 - ch0 (with verify) ........... Passederam0 - ch0 to eram2 - ch0 (with verify) ........... Passederam0 - ch0 to eram3 - ch0 (with verify) ........... Passederam1 - ch0 to eram0 - ch0 (with verify) ........... Passederam1 - ch0 to eram2 - ch0 (with verify) ........... Passederam1 - ch0 to eram3 - ch0 (with verify) ........... Passederam2 - ch0 to eram0 - ch0 (with verify) ........... Passederam2 - ch0 to eram1 - ch0 (with verify) ........... Passederam2 - ch0 to eram3 - ch0 (with verify) ........... Passederam3 - ch0 to eram0 - ch0 (with verify) ........... Passederam3 - ch0 to eram1 - ch0 (with verify) ........... Passederam3 - ch0 to eram2 - ch0 (with verify) ........... Passederam0 - ch1 to eram1 - ch1 (with verify) ........... Passederam0 - ch1 to eram2 - ch1 (with verify) ........... Passederam0 - ch1 to eram3 - ch1 (with verify) ........... Passederam1 - ch1 to eram0 - ch1 (with verify) ........... Passederam1 - ch1 to eram2 - ch1 (with verify) ........... Passederam1 - ch1 to eram3 - ch1 (with verify) ........... Passederam2 - ch1 to eram0 - ch1 (with verify) ........... Passederam2 - ch1 to eram1 - ch1 (with verify) ........... Passederam2 - ch1 to eram3 - ch1 (with verify) ........... Passederam3 - ch1 to eram0 - ch1 (with verify) ........... Passederam3 - ch1 to eram1 - ch1 (with verify) ........... Passederam3 - ch1 to eram2 - ch1 (with verify) ........... Passed

Test Completed Successfully


moabSerconThis command will initiate “loopback” test between the REMOTE 1 and REMOTE 2 ports at the rear of the AirSPACE Chassis, and verify proper operation. NOTE: An RS-422 cable is required for this test.

Entered Command: moabSercon

Successful Result: Moab Serial Port Test PPN 001-920 Rev B

Connect a RS-422 cable between the REMOTE 1 and REMOTE2 connectors located at the lower left rear corner ofthe chassis.

Hit ENTER to Continue.

Using /dev/mci0 and /dev/mci1 for serial port test.Test Completed Sucessfully.

NOTE: These ports are not currently implemented and should not be connected to any controlling device.

moabMemTestThis test script will run moabMem on the NVRAM, ERAM0, ERAM1, ERAM2, and ERAM3 paths. Successful completion verifies the system memory, and all paths to and from the memory SIMM’s. This test will run approximately 40 minutes. Successful completion is a return to the command prompt.

Entered Command: moabMemTest

Example Result: Moab DMA Memory Test PPN 001-918 Rev. D ERAM size 7fffe00

testing with pattern fffffffftesting with pattern 55555555testing with pattern aaaaaaaatesting with increasing valuetesting with decreasing patterntesting with walking 1’stesting with walking 0’s

The above result would be the first iteration for ERAM0. The same results should be expected for ERAM1; ERAM2; and ERAM3. A faulty ACV card may cause this test to fail. This test may be terminated at any time withCtrl+c. NOTE: A failure during the ERAM1 iteration would indicate a faulty SCSI Board. A failure of this test may look like this: MB010: Failure 0x001809d4 SIMM U18: 0xfff9fe0a should be 0x000601F5MB010: Failure 0x003805f8 SIMM U19: 0xfff1ff01 should be 0x000e00fe


moabBusTestThis script will execute read/write operations to the buffer present on each disk drive. There are (3) iterations of this test: • 2500 Write Operations (Successful result is a Total Bandwidth of >70MB/s.) • 2500 Read Operations (Successful result is a Total Bandwidth of >70MB/s.) • 200 Read/Write Operations (Successful result is a Total Bandwidth of >1.5MB/s.) NOTE: This test must be initiated from the /toolsbin. This test will run approximately 10 Minutes.

Entered Command: cd toolsbinEntered Command: moabBusTest Successful Result:

2500 requested iterationsTransfering into eram

Moab All Buses Test Pluto PN. 001-910 Rev. A

bandwidth is 7.06 MB/sbandwidth is 7.06 MB/sbandwidth is 7.05 MB/sbandwidth is 7.06 MB/sbandwidth is 7.06 MB/sbandwidth is 7.05 MB/sbandwidth is 7.05 MB/sbandwidth is 7.04 MB/sbandwidth is 6.97 MB/sbandwidth is 6.93 MB/sbandwidth is 6.92 MB/sbandwidth is 6.90 MB/sbandwidth is 6.90 MB/sbandwidth is 6.90 MB/sbandwidth is 6.89 MB/sbandwidth is 6.91 MB/sbandwidth is 6.90 MB/sbandwidth is 6.89 MB/sbandwidth is 6.88 MB/sbandwidth for disk 0 is 6.91 MB/sbandwidth for disk 1 is 6.91 MB/sbandwidth for disk 2 is 6.92 MB/sbandwidth for disk 3 is 6.92 MB/sbandwidth for disk 4 is 6.92 MB/sbandwidth for disk 5 is 6.92 MB/sbandwidth for disk 6 is 6.93 MB/sbandwidth for disk 7 is 6.93 MB/sbandwidth for disk 8 is 6.93 MB/sbandwidth for disk 9 is 6.93 MB/sbandwidth for disk 10 is 6.84 MB/sbandwidth for disk 11 is 6.84 MB/sbandwidth for disk 12 is 6.84 MB/sbandwidth for disk 13 is 6.84 MB/sbandwidth for disk 14 is 6.84 MB/sbandwidth for disk 15 is 6.85 MB/sbandwidth for disk 16 is 6.83 MB/sbandwidth for disk 17 is 6.83 MB/sbandwidth for disk 18 is 6.83 MB/sbandwidth for disk 19 is 6.83 MB/sThe total bandwidth is 137.60 MB/s (Successful Result = >70MB/s)


2500 requested iterationsTransfering from eramMoab All Buses Test Pluto PN. 001-910 Rev. A

bandwidth is 6.50 MB/sbandwidth is 6.50 MB/sbandwidth is 6.49 MB/sbandwidth is 6.45 MB/sbandwidth is 6.45 MB/sbandwidth is 6.44 MB/sbandwidth is 6.43 MB/sbandwidth is 6.42 MB/sbandwidth is 6.42 MB/sbandwidth is 6.43 MB/sbandwidth is 6.43 MB/sbandwidth is 6.40 MB/sbandwidth is 6.40 MB/sbandwidth is 6.38 MB/sbandwidth is 6.38 MB/sbandwidth is 6.37 MB/sbandwidth is 6.37 MB/sbandwidth is 6.37 MB/sbandwidth is 6.37 MB/sbandwidth is 6.32 MB/sbandwidth for disk 0 is 6.27 MB/sbandwidth for disk 1 is 6.27 MB/sbandwidth for disk 2 is 6.27 MB/sbandwidth for disk 3 is 6.27 MB/sbandwidth for disk 4 is 6.28 MB/sbandwidth for disk 5 is 6.28 MB/sbandwidth for disk 6 is 6.28 MB/sbandwidth for disk 7 is 6.28 MB/sbandwidth for disk 8 is 6.28 MB/sbandwidth for disk 9 is 6.28 MB/sbandwidth for disk 10 is 6.28 MB/sbandwidth for disk 11 is 6.29 MB/sbandwidth for disk 12 is 6.29 MB/sbandwidth for disk 13 is 6.29 MB/sbandwidth for disk 14 is 6.29 MB/sbandwidth for disk 15 is 6.29 MB/sbandwidth for disk 16 is 6.30 MB/sbandwidth for disk 17 is 6.30 MB/sbandwidth for disk 18 is 6.30 MB/sbandwidth for disk 19 is 6.30 MB/sThe total bandwidth is 125.70 MB/s (Successful Result = >70MB/s)


200 requested iterationsTransfering in both directions With VerifyMoab All Buses Test Pluto PN. 001-910 Rev. A

Verify test being run on system disk.bandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth is 0.10 MB/sbandwidth for disk 0 is 0.10 MB/sbandwidth for disk 1 is 0.10 MB/sbandwidth for disk 2 is 0.10 MB/sbandwidth for disk 3 is 0.10 MB/sbandwidth for disk 4 is 0.10 MB/sbandwidth for disk 5 is 0.10 MB/sbandwidth for disk 6 is 0.10 MB/sbandwidth for disk 7 is 0.10 MB/sbandwidth for disk 8 is 0.10 MB/sbandwidth for disk 9 is 0.10 MB/sbandwidth for disk 10 is 0.10 MB/sbandwidth for disk 11 is 0.09 MB/sbandwidth for disk 12 is 0.09 MB/sbandwidth for disk 13 is 0.09 MB/sbandwidth for disk 14 is 0.09 MB/sbandwidth for disk 15 is 0.09 MB/sbandwidth for disk 16 is 0.09 MB/sbandwidth for disk 17 is 0.09 MB/sbandwidth for disk 18 is 0.09 MB/sbandwidth for disk 19 is 0.09 MB/sThe total bandwidth is 1.90 MB/s (Successful Result = >1.5MB/s)


Single Board Computer Replacement Procedure NOTE: Always observe proper static precautions when handling AirSPACE Assemblies. AirSPACE Sled Removal and Disassembly: • Via the User Interface Shutdown Menu, HALT the system. Once the system indicates it has halted, turn off

both power supplies and remove the power cords and all cables connected to the AirSPACE chassis. • Remove the nine (9) PHS screws around the perimeter of the Sled Assembly. Slide the Sled Assembly directly

out the back of the AirSPACE chassis. • With the Sled Assembly positioned on a static safe work area, remove the five (5) PHS screws attaching the

fan bracket to the long standoffs. Remove the fan bracket and disconnect the power connector from J8 on the Motherboard, allowing access to the boards underneath. Set the Fan Bracket Assembly aside.

NOTE: The U-shaped Reference Interface Board attaches to the sled assembly as follows: a) It is attached to a connector board on the rear of the Sled Assembly via two large multi-pin connectors. b) It is also attached to the ACV (Video I/O Boards) via pairs of connectors (J8-J11 ACV5); (J12-J13 ACV4); (J2-

J3 ACV3); (J4-J5 ACV2); (J6-J7 ACV1).

• To remove the Reference Interface Board, carefully lift the rear of the board and break the connections to the installed ACV Boards, underneath. Carefully slide the board towards the front of the Sled Assembly to break loose the multi-pin connections, which attach to the rear connector board. Set the Reference Interface Board aside.

AirSPACE Single Board Computer Replacement: • Locate the Single Board Computer. Disconnect the two (2) ribbon cables, and the Yellow/Black RESET wire

from the SBC. Remove the hold-down screw, and remove the SBC from the Motherboard. • Install the replacement SBC and reconnect the ribbon cables (Remote 1 to Remote 1; and Remote 2 to

Remote 2). Reconnect the RESET line, to the SBC header, with the BLACK wire facing the rear of the SBC. • Replace the Reference Interface Board as follows: NOTE: It is extremely important that the connectors are properly "keyed", to eliminate the possibility of bent pins. a) Carefully seat the two large multi-pin connectors to the connector board on the rear of the Sled Assembly. b) Line up the remaining connectors with the connectors on the top of the ACV Boards. c) Gently press down on the Reference Interface Board to seat the remaining connectors to the ACV Boards.

• Re-install the fan bracket and replace the five (5) PHS screws on the long standoffs. Reconnect the fan

power connector to J8 on the Motherboard. • Re-install the Sled Assembly in the system chassis; replace the nine (9) PHS screws, and reconnect all

cables. • Restore system power, while holding the F2 key on the keypad. When the System Summary screen appears,

verify the System Time is set to GMT, and load the SBC Set-Up Defaults, as previously described in this section. Exit Saving Changes, and allow the system to boot to the User Interface.


SECTION VII: ACV Board Functional Tests The following series of routines allow the user to perform functional testing on any ACV (Audio/Compressed Video) board in the AirSPACE system. GENERIC COMMANDS & HOT KEYS Ctrl+Alt+F1 Drops User Interface and opens a console window. Ctrl+Alt+F2 Opens a second console window. maint AirSPACE system login. mars AirSPACE system password. kbs Followed by ENTER. Drops framework and creates a lock file in



to the command prompt. Ctrl+Alt+F3 Returns to User Interface from command mode.

RUNNING THE ACV BOARD TEST ROUTINES All commands in this procedure are executed with the ENTER key. These tests cannot be run with the system “ON-AIR”.

• Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type kbs and press ENTER. • At the command prompt, type the desired test command, followed by the ENTER key. NOTE: AirSPACE is capable of holding (5) ACV Boards, in PCI Slots 1-5, as shown. When running the ACV tests, the first ACV Board the system recognizes (from LEFT to RIGHT), regardless of the PCI location, will be ACV0. As an example, ACV Boards in PCI Slots 2 & 4, would be read as ACV0 & ACV1, respectively. ACV Boards in PCI Slots 2,3, and 4, would be read as ACV0, ACV1, and ACV2 respectively. ACV Assembly Video I/O Connections

REFERENCE VIDEO INPUT

COMPOSITE ANALOG OUT

SDI DIGITAL OUT

SDI DIGITAL LOOP (E/E)

SDI DIGITAL INPUT


38 • Maintenance & Diagno

ACV Breakout Box ACV Memory TestsacvMemThis test script will verify proACVs may be tested, as sho

Entered Command:Successful Result:

ACV Memory/

ProgrammingProgramming

Configurati

Acv0 MemoryTesting ATesting ATesting ATesting ATesting ATesting ATesting ATesting ATesting ATesting A

All Acv0 Te

Test Comple

COMPOSITE VIDEO OUTPUT (NO TIMECODE BURN-IN).
RS-422 REMOTE CONNECTORS.
stics Version 2.02 Avid Technology, Inc.

per operation of all paths to and from the memory resident on the ACV Board. Single wn, or the addition of the –i argument will test multiple ACV’s.

acvMem 0 (Example ACV Test: ACV0.) Testing acv0

Xilinx Test Pluto PN. 001-940 Rev. D

the acv0 with /usr/home/pluto/config/acv_II.hexthe acv0 with /usr/home/pluto/config/acv_II_dv.hex

on Test on acv0 - Passed

Test:cv0 with pattern ffffffff .... Passedcv0 with pattern 55555555 .... Passedcv0 with pattern cccccccc .... Passedcv0 with pattern aaaaaaaa .... Passedcv0 with pattern 33333333 .... Passedcv0 with pattern 0 .... Passedcv0 with increasing value .... Passedcv0 with decreasing pattern .. Passedcv0 with walking one's ....... Passedcv0 with walking zero's ...... Passed

sts Successful

ted Successfully


acvDmaThis test will verify burst transfers to and from the ACV memory. The addition of the –i argument will test multiple ACV’s, or a single ACV may be tested as shown above.

Entered Command: acvDma –i2 (Example Multiple ACV Test: ACV0 and ACV1.) Successful Result: Testing acv0 and acv1

ACV DMA Test PPN - 001-939 Rev. F

eram0 - ch0 to acv - ch0 (with verify) ........... Passedacv - ch0 to eram0 - ch0 (with verify) ........... Passederam0 - ch1 to acv - ch1 (with verify) ........... Passedacv - ch1 to eram0 - ch1 (with verify) ........... Passed

ACV0 Test Completed Successfully

eram0 - ch0 to acv - ch0 (with verify) ........... Passedacv - ch0 to eram0 - ch0 (with verify) ........... Passederam0 - ch1 to acv - ch1 (with verify) ........... Passedacv - ch1 to eram0 - ch1 (with verify) ........... Passed

ACV1 Test Completed Successfully

acvRegThis test will verify proper operation of the acessable read/write registers on the ACV Board. The addition of the –i argument will test multiple ACV’s.

Entered Command: acvReg –i2 (Example Multiple ACV Test: ACV0 and ACV1.) Successful Result: Testing acv0 and acv1

ACV Register Test Pluto PN. 001-947 Rev. B

Programming ACV0 Xilinx with /usr/home/pluto/config/acv_II.hexProgramming ACV0 Xilinx2 with /usr/home/pluto/config/acv_II_dv.hex


Register Test Passed


ACV Audio & Video TestsacvCompThis command will initiate a loopback test to verify proper operation of the Audio/Video compression circuitry on any single ACV Board. The test will verify audio and video compression at the following standards: DV25 525, DV25 625, DV50 525, DV50 625. NOTE: A short BNC-BNC cable is required for this test.

Entered Command: acvComp 0 (Enter argument of 0 – 4 to assign the ACV card under test.) Successful Result: ACV Video Compression Pluto PN. 001-931 Rev. C

Verify SetupMake sure that the card under test's output(ACV0) is connected to it's input

When the setup is correct press the enter key


DV video Test 25M 525 Loopback Codec 1 Port 1A ... PassedDV video Test 25M 525 Loopback Codec 1 Port 1A ... PassedDV video Test 25M 625 Loopback Codec 1 Port 1A ... PassedDV video Test 25M 525 Loopback Codec 2 Port 2A ... PassedDV video Test 25M 625 Loopback Codec 2 Port 2A ... PassedDV video Test 50M 525 Loopback Codec 1 Port 1A ... PassedDV video Test 50M 625 Loopback Codec 1 Port 1A ... PassedDV video Test 50M 525 Loopback Codec 2 Port 2A ... PassedDV video Test 50M 625 Loopback Codec 2 Port 2A ... Passed



acvDACThis command will initiate a loopback test to verify analog-digital and digital-analog circuitry using a pair of ACV Boards. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: (2) Two short BNC-BNC cables are required for this test.

Entered Command: acvDAC 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)

(Argument 2 = ACV0 SOURCE & ACV2 DESTINATION) (Argument 3 = ACV0 SOURCE & ACV3 DESTINATION) (Argument 4 = ACV0 SOURCE & ACV4 DESTINATION)

Successful Result: ACV DAC Test Pluto PN. 001-935 Rev D

For this test the order of the cards from left to right is: (ACV0, ACV1, ...)

Verify SetupMake sure that the reference interface card is connected between thesource card (ACV0) and the destination card(ACV1).Connect house reference and terminator to the Analog Ref inputs.Make sure that the source card's output is connected to the destinationcard's inputMake sure that the destination card's output is connected to the sourcecard's input




Please wait - Checking the selected cards DAC Free Run Mode ... PassedPlease wait - Checking the selected cards DAC Reference Mode ... Passed



acvEEThis command will initiate a loopback test to verify the pass-through EE circuitry using a pair of ACV Boards. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: (2) Two short BNC-BNC cables are required for this test.

Entered Command: acvEE 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)


Successful Result: ACV EE Test Pluto PN. 001-943 Rev C


Verify Setup

Check that the source card's output(ACV0) is connected to the destinationcard's input(ACV1)Check that the source card's input is connected to the destination card'soutputCheck that the 525 house reference is connected to the reference input




Checking the source card's E to E mode with PLL data .................. PassedChecking the source card's E to E mode with Equilizer data ............ PassedChecking the destination Card's E to E mode with PLL data ............. PassedChecking the destination Card's E to E mode with Equilizer data ....... Passed



acvCCThis command will initiate a loopback test to verify the Closed Caption circuitry using a pair of ACV Boards. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: (2) Two short BNC-BNC cables are required for this test.

Entered Command: acvCC 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)


Successful Result: ACV CC Test Pluto PN. 001-942 Rev. CFor this test the order of the cards from left to right is: (ACV0, ACV1, ...)

Verify SetupMake sure that the source card's first output (ACV0)is connected to thedestination card's input(ACV1)Make sure that the source card's input(ACV0) is connected to the destinationcard's first output(ACV1)


Programming ACV1 Xilinx with /usr/home/pluto/config/acv_II.hexProgramming ACV1 Xilinx2 with /usr/home/pluto/config/acv_II_dv.hexProgramming ACV0 Xilinx with /usr/home/pluto/config/acv_II.hexProgramming ACV0 Xilinx2 with /usr/home/pluto/config/acv_II_dv.hex

CC Test - Destination Card to Source Card 525 8 Bit ... PassedCC Test - Source Card to Destination Card 525 8 Bit ... PassedCC Test - Destination Card to Source Card 525 10 Bit ... PassedCC Test - Source Card to Destination Card 525 10 Bit ... PassedCC Test - Destination Card to Source Card 625 8 Bit ... PassedCC Test - Source Card to Destination Card 625 8 Bit ... PassedCC Test - Destination Card to Source Card 625 10 Bit ... PassedCC Test - Source Card to Destination Card 625 10 Bit ... Passed

Now set the source card's second output to connect to the new card's input.Also set the new card's second output to connect to the source card's input.

NOTE: Move cables from each ACV’s SDI Output to each ACV’s Serial Loop-Through at this point.


CC Test - Destination Card to Source Card 525 8 Bit ... PassedCC Test - Source Card to Destination Card 525 8 Bit ... PassedCC Test - Destination Card to Source Card 525 10 Bit ... PassedCC Test - Source Card to Destination Card 525 10 Bit ... PassedCC Test - Destination Card to Source Card 625 8 Bit ... PassedCC Test - Source Card to Destination Card 625 8 Bit ... PassedCC Test - Destination Card to Source Card 625 10 Bit ... PassedCC Test - Source Card to Destination Card 625 10 Bit ... Passed



acvFilterThis command will initiate a loopback test to verify the filter circuitry on a pair of ACV Boards. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: (2) Two short BNC-BNC cables are required for this test.

Entered Command: acvFilter 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)


Successful Result: ACV Filter Test Pluto PN. 001-949 Rev. B


Verify SetupMake sure that the source card's output(ACV0) is connected to the

destination card's input(ACV1)Make sure that the source card's input is connected to the destination

card's output




Golden Card to Card Under Test Filter Test - Black Line on Grey ... PassedCard Under Test to Golden Card Filter Test - Black Line on Grey ... PassedGolden Card to Card Under Test Filter Test - White Line on Grey ... PassedCard Under Test to Golden Card Filter Test - White Line on Grey ... Passed



acvLoopThis command will initiate a test to verify the video loopback path and associated circuitry on any single ACV Board. NOTE: A short BNC-BNC cable is required for this test.

Entered Command: acvLoop 0 (Enter argument of 0 – 4 to assign the ACV card under test.) Successful Result: ACV Loop Test Pluto PN. 001-936 Rev. C

Verify Setup:Make sure that the second (from top) output on the card(s) under test

is connected to the input (bottom) on the card(s) under test



External Loopback of 8 Bit PLL worst case data ......... PassedExternal Loopback of 8 Bit Equalizer worst case data ... PassedExternal Loopback of 10 Bit PLL worst case data ......... PassedExternal Loopback of 10 Bit Equalizer worst case data ... Passed

Now run the cable from the next (one down) output to the inputPress enter when ready

External Loopback of 8 Bit PLL worst case data ......... PassedExternal Loopback of 8 Bit Equalizer worst case data ... PassedExternal Loopback of 10 Bit PLL worst case data ......... PassedExternal Loopback of 10 Bit Equalizer worst case data ... Passed


acvSerialThis command will initiate a loopback test to verify proper operation of the RS-422 ports on any single ACV Board. NOTE: A short RS-422 cable (to connect between REMOTE 1 and REMOTE 2 on the BOB) and AirSPACE Breakout Box is required for this test.

Entered Command: acvSerial 0 (Enter argument of 0 – 4 to assign the ACV card under test.) Successful Result: ACV Serial Test PPN 001-933 Rev E

Verify SetupMake sure that the ACV loopback cable is connected to the card under test,or a BOB is connected to the desired ACV I/O port, and an RS-422 loop cableis connected between the BOB's serial port connectors.



Using /dev/mci2 and /dev/mci3 for acv0



acvVOTThis command will initiate a loopback test using a pair ACV Boards to verify the Video Output Timing circuitry. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: A short BNC-BNC cable and SDI source are required for this test.

Entered Command: acvVOT 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)


Successful Result: ACV VOT Test Pluto PN. 001-946 Rev. B


Verify SetupMake sure that the destination card's output(ACV1) is connected to thesource card's input(ACV0)Make sure that the destination card's input(ACV1) is connected to thehouse outputMake sure that 525 house reference is connected to the reference input




+2 Output Timing Test - 525 8 bit Source to Destination ... Passed+2 Output Timing Test - 525 8 bit Destination to Source ... Passed+4 Output Timing Test - 525 8 bit Source to Destination ... Passed+4 Output Timing Test - 525 8 bit Destination to Source ... Passed-2 Output Timing Test - 525 8 bit Source to Destination ... Passed-2 Output Timing Test - 525 8 bit Destination to Source ... Passed-4 Output Timing Test - 525 8 bit Source to Destination ... Passed-4 Output Timing Test - 525 8 bit Destination to Source ... Passed+2 Output Timing Test - 525 10 bit Source to Destination ... Passed+2 Output Timing Test - 525 10 bit Destination to Source ... Passed+4 Output Timing Test - 525 10 bit Source to Destination ... Passed+4 Output Timing Test - 525 10 bit Destination to Source ... Passed-2 Output Timing Test - 525 10 bit Source to Destination ... Passed-2 Output Timing Test - 525 10 bit Destination to Source ... Passed-4 Output Timing Test - 525 10 bit Source to Destination ... Passed-4 Output Timing Test - 525 10 bit Destination to Source ... Passed


ACV Time Code Tests acvLTCThis command will initiate a loopback test to verify proper operation of all Time Code circuitry on any single ACV Board. NOTE: A AirSPACE Breakout Box and a short M-F XLR cable (Between LTC IN and LTC OUT) are required for this test. Run acvReg test prior to acvLTC.

Entered Command: acvLTC 0 (Enter argument of 0 – 4 to assign the ACV card under test.)


Successful Result: ACV LTC Test Pluto PN. 001-950 Rev. C

Verify SetupMake sure that the card is connected to the RIF card on the chassis.Make sure that the acv loopback cable is installed.Or, the BOB is connected and LTC loop cable installed.

Make sure that 525 reference is connected to the reference input.Make sure that a serial digital source in conneced to the acv (bottom BNC).



LTC Test ......... Passed


acvVITCThis command will initiate a loopback test to verify proper operation of all VITC control circuitry using a pair of ACV Boards. One ACV is used as the SOURCE; and the other ACV as the DESTINATION. Once the test is completed on the first pair of ACV Boards, run the test on the next ACV using the required argument, shown below. NOTE: (2) Two short BNC-BNC cables are required for this test. Run acvReg test prior to acvVITC.

Entered Command: acvVITC 1 (Argument 0 = ACV1 SOURCE & ACV0 DESTINATION) (Argument 1 = ACV0 SOURCE & ACV1 DESTINATION)


Successful Result: ACV VITC Test Pluto PN. 001-941 Rev. B


Verify SetupMake sure that the source card's output (ACV0) is connected to thedestination card's input(ACV1)Make sure that the source card's input (ACV0) is connected to thedestination card's output(ACV1)




VITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 0 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 0 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 1 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 1 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 2 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 2 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 3 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 3 ... Passed


VITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 4 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 4 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 5 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 5 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 6 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 6 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 7 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 7 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 0 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 0 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 1 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 1 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 2 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 2 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 3 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 3 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 4 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 4 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 5 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 5 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 6 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 6 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 7 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 7 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit ... PassedVITC Test - Card Under Test to Golden Card 525 10 Bit ... PassedVITC Test - Golden Card to Card Under Test 525 10 Bit ... PassedVITC Test - Card Under Test to Golden Card 625 8 Bit ... PassedVITC Test - Golden Card to Card Under Test 625 8 Bit ... PassedVITC Test - Card Under Test to Golden Card 625 10 Bit ... PassedVITC Test - Golden Card to Card Under Test 625 10 Bit ... Passed

Now set the source card's second output to connect to the new card's input.Also set the new card's second output to connect to the source card's input.

NOTE: Move cables from each ACV’s SDI Output to each ACV’s Serial Loop-Through at this point.




VITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 0 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 0 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 1 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 1 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 2 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 2 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 2 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 3 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 3 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 4 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 4 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 5 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 5 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 6 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 6 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Pri. Line 7 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit Sec. Line 7 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 0 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 0 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 1 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 1 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 2 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 2 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 3 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 3 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 4 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 4 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 5 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 5 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 6 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 6 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Pri. Line 7 ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit Sec. Line 7 ... PassedVITC Test - Card Under Test to Golden Card 525 8 Bit ... PassedVITC Test - Golden Card to Card Under Test 525 8 Bit ... PassedVITC Test - Card Under Test to Golden Card 525 10 Bit ... PassedVITC Test - Golden Card to Card Under Test 525 10 Bit ... PassedVITC Test - Card Under Test to Golden Card 625 8 Bit ... PassedVITC Test - Golden Card to Card Under Test 625 8 Bit ... PassedVITC Test - Card Under Test to Golden Card 625 10 Bit ... PassedVITC Test - Golden Card to Card Under Test 625 10 Bit ... Passed



ACV Assembly Replacement Procedure NOTE: Always observe proper static precautions when handling AirSPACE Assemblies. AirSPACE Sled Removal and Disassembly: • Via the User Interface Shutdown Menu, HALT the system. Once the system indicates it has halted, turn off





J3 ACV3); (J4-J5 ACV2); (J6-J7 ACV1).


AirSPACE ACV Assembly Replacement: • Refer to the figure below. Locate the faulty ACV Assembly. Remove the 9/16” BNC nuts and faceplate from

the ACV. Remove the PCI hold-down screw, and remove the ACV Assembly from the Motherboard.

ACV Assemblies in Slots 2-4.


• Install the replacement ACV Assembly, and replace the PCI hold-down screw and faceplate. • Replace the Reference Interface Board as follows: NOTE: It is extremely important that the connectors are properly "keyed", to eliminate the possibility of bent pins. a) Carefully seat the two large multi-pin connectors to the connector board on the rear of the Sled Assembly. b) Line up the remaining connectors with the connectors on the top of the ACV Boards. c) Gently press down on the Reference Interface Board to seat the remaining connectors to the ACV Boards. • Re-install the fan bracket and replace the five (5) PHS screws on the long standoffs. Reconnect the fan

power connector to J8 on the Motherboard. • Re-install the Sled Assembly in the system chassis; replace the nine (9) PHS screws, and reconnect all

cables. • Restore system power, and allow the system to boot to the User Interface. Verify proper programming of the ACV Assembly as follows: • Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • Run the following commands: acvinfoThis command, with the proper arguments, will display ACV Board Revision; Serial Number; PLX ID, and verify the programming of the PLX devices. The first ACV Board the system recognizes, regardless of the PCI location, will be ACV0. Example: AVC Boards in PCI Slots 2 & 4, would be read as ACV0 & ACV1, respectively.

Entered Command: acvinfo /dev/acvX ver (Where X = acv0 through acv4.) Example Result for ACV I (XL) Assembly: ACV detected, PLX Device ID = 0008Serial Number: 00521311Revision Number: C03Verification Successful

Entered Command: acvinfo /dev/acvX ver (Where X = acv0 through acv4.) Example Result for ACV II Assembly (XLA): ACV II detected, PLX Device ID = 000BSerial Number: 00770059Revision Number: D02Verification Successful

ACV Sub-Assembly Part Number & Revision Level Breakdown: • ACV Board AirSPACE, XLA 0030-03080-01 Revision D02 • ACV Board AirSPACE, XL 0030-03080-02 Revision C03 • DIO Board AirSPACE, XLA 0030-03090-01 Revision C02 • DIO Board AirSPACE, XL 0030-03090-02 Revision B06 • Codec Panasonic DV 0030-00088-02 Revision C01 • Codec Panasonic DV 0030-00088-02 Revision D00

NOTE: The installed ACV Assembly (XL/XLA) is normally transparent to the user. Embedded Audio and Dolby E, used in delay applications, require XLA ACV Assemblies.


dmesgThis command, with redirection and filters can be used to verify proper programming and recognition of the ACV Assemblies during the boot sequence.

Entered Command to Check ACV Boards: dmesg | grep acv

Successful Result for ACV II XLA (This system has two ACV Assemblies installed): acv0: <Pluto ACV/XLA> rev 0x00 int a irq 10 on pci5.3.0acv0: PLX register base at 0xcffff800acv1: <Pluto ACV/XLA> rev 0x00 int a irq 10 on pci5.11.0acv1: PLX register base at 0xcffff000nsu2 at acv0 serial I/O port 0nsu3 at acv0 serial I/O port 1nsu4 at acv1 serial I/O port 0nsu5 at acv1 serial I/O port 1acv0: Simulating Record Interruptsacv1: Simulating Record Interrupts

Entered command to reprogram ACV II XLA Serial Numbers & Revision Levels: • plx_acvII /dev/acvX ser=AAAAAAAA rev=BBBWhere X=0-4, for ACV 0-4. Where A=ACV Board Serial Number. Where B=ACV Board Revision Level Entered command to reprogram ACV I XL Serial Numbers & Revision Levels: • plx_acv /dev/acvX ser=AAAAAAAA rev=BBBWhere X=0-4, for ACV 0-4. Where A=ACV Board Serial Number. Where B=ACV Board Revision Level Entered command to reprogram DIO Serial Numbers & Revision Levels: • set_dio A –dBBBBBBBB –rCCC –cDDDDDDDD –rEEE –cFFFFFFFF –rGGGWhere A=0-4, for DIO 0-4. Where B=DIO Serial Number. Where C=DIO Revision Level. Where D=Codec 1 Serial Number. Where E=Codec 1 Revision Level. Where F= Codec 2 Serial Number. Where G=Codec 2 Revision Level. Entered command to load ACV Assembly DSP Code:: • acvLoadDSP –iXWhere X=The number of ACV Assemblies installed in the system.


SECTION VIII: AirSPACE Modem The AirSPACE currently has installed a K56 Zoom V.90 modem. AirSPACE does not support PNP (Plug & Play) devices, so the internal modem is physically jumpered for COM3 & IRQ5.

Modem Replacement Procedure NOTE: Always observe proper static precautions when handling AirSPACE Assemblies. AirSPACE Sled Removal: • Via the User Interface Shutdown Menu, HALT the system. Once the system indicates it has halted, turn off


out the back of the AirSPACE chassis. • To replace the modem, it is normally not necessary to disassemble the sled. AirSPACE Modem Replacement: • Refer to the figure below, and locate the faulty modem card. Remove the PCI hold-down screw, and remove

the modem from the Motherboard.

• Refer to the figure below, and verify the proper jumper settings for COM3 and IRQ5 on the replacement

modem:

• Re-install the Sled Assembly in the system chassis; replace the nine (9) PHS screws, and reconnect all

cables. • Restore system power, and allow the system to boot to the User Interface.

Modem Card


Manual Initialization of the Modem: • Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type kbs and press ENTER. • At the command prompt, run the following command: modem-initThe modem is a valuable asset to enable remote diagnostics, feature upgrades, and software upgrades. The following test, run from root, will reset the modem and verify its connectivity.

Entered Command: /etc/sliphome/modem-init Successful Result: spawn tip cuaa2

connectedATOKATS0=1&W0OKATI3ZOOM V.90 kfav173 ISA I111098V -G Z207 (*)

OK~[EOT]:

(*) Results may vary slightly, depending on the modem type installed.

NOTE: modem_init is run automatically during the boot sequence.


SECTION IX: AirSPACE Gigabit Ethernet NIC The AirSPACE may require a Gigabit Ethernet NIC, depending on the NewsCutter/Unity environment. The NIC drivers are embedded in the AirSPACE OS. No configuration of the NIC is required.

Gigabit Ethernet NIC Installation & Replacement Procedure NOTE: Always observe proper static precautions when handling AirSPACE Assemblies. AirSPACE Sled Removal: • Via the User Interface Shutdown Menu, HALT the system. Once the system indicates it has halted, turn off


out the back of the AirSPACE chassis. • To replace/install a Gigabit Ethernet NIC, it is normally not necessary to disassemble the sled. Gigabit Ethernet NIC Installation & Replacement: • Refer to the figure below, and locate the Gigabit NIC, installed in the PCI slot next to the Modem. Install or

remove/replace the faulty NIC, as required.

• Re-install the Sled Assembly in the system chassis; replace the nine (9) PHS screws, and reconnect all

cables. • Restore system power, and allow the system to boot to the User Interface.

Gigabit NIC goes here.


Gigabit Ethernet NIC Enable/Disable:

touch no_gigeThis command, run from /etc, will disable the Gigabit Ethernet Fiber NIC, and enable the internal 100BaseT port on the SBC. This command creates a “place holder” in the /etc directory. Reboot the system for these changes to take effect.

Entered Command: cd /etcEntered Command: touch no_gige

NOTE: Unless a no_gige lock file is present in /etc, the AirSPACE will always boot with Gigabit Ethernet ENABLED and 100BaseT DISABLED.

rm no_gigeThis command, run from /etc, will remove the lock file created in the above step; disable the 100BaseT port on the SBC, and enable the Gigabit Ethernet NIC. Reboot the system for these changes to take effect.

Entered Command: cd /etc Entered Command: rm no_gige


SECTION X: AirSPACE Motherboard (MOAB) This section describes the AirSPACE Motherboard replacement and the required RFS restore procedures. For convenience and static safety, the replacement Motherboard Assembly is shipped on the metal sled.. It may be necessary to transfer the existing SBC; ACV Assemblies; Modem/Serial Card; Reference Interface; SCSI Card; and/or Gigibit Ethernet NIC to the replacement Motherboard Assembly. The reasons behind the Motherboard failure, and/or the extent of the failure, may cause all media to be lost. The extent of the Motherboard failure may also prevent the User Interface from starting. Motherboard Replacement Procedure If the AirSPACE User Interface is UP: • From the Shutdown Menu, select Restart User Interface, to create a fresh RFS Backup file. • Once the User Interface reappears, enter a console window with Ctrl+Alt+F1. • Login: maint Password: mars • Type cd RFSbackups, followed by the Enter key. • Type ls –l, followed by the Enter key. Verify the rfs.0 file is in the RFSbackups directory, and make

note of the Time/Date stamp on this backup file. The Time/Date stamp will be used to identify the correct backup file, for the restore process, described later in this procedure.

If the AirSPACE User Interface is DOWN: • Press the Enter key until a login prompt appears. Login: maint Password: mars • Type cd RFSbackups, followed by the Enter key. • Type ls –l, followed by the Enter key. Inspect the Time/Date stamps on the rfs.0 through rfs.9

backup files. Verify an RFS Backup file exists, which you feel would be usable for the restore process, and make note of the Time/Date stamp on this backup file.

AirSPACE Sled Removal and Disassembly: • Via the User Interface Shutdown Menu, HALT the system. Once the system indicates it has halted, turn off





J3 ACV3); (J4-J5 ACV2); (J6-J7 ACV1).



AirSPACE Motherboard Replacement: • Transfer all of the necessary peripheral boards to the replacement Motherboard Assembly. • Reconnect all internal cables, including the RESET line, to the SBC header, with the BLACK wire facing the

rear of the SBC. • Replace the Reference Interface Board as follows: NOTE: It is extremely important that the connectors are properly "keyed", to eliminate the possibility of bent pins. a) Carefully seat the two large multi-pin connectors to the connector board on the rear of the Sled Assembly. b) Line up the remaining connectors with the connectors on the top of the ACV Boards. c) Gently press down on the Reference Interface Board to seat the remaining connectors to the ACV Boards.

• Re-install the fan bracket and replace the five (5) PHS screws on the long standoffs. Reconnect the fan

power connector to J8 on the Motherboard. • Note the replacement Motherboard Serial Number and Revision level, prior to installation in the chassis. The

Motherboard Serial Number is a six-digit number, on a white bar code label, located on the Component Side of the board. Write this number down, for reprogramming later in this procedure.

• The Motherboard Revision Level is a three-character combination, written on the silkscreen, located on the Component Side of the board. Such as D02, D03, Etc. Write this number down, for reprogramming later in this procedure.

• Re-install the Sled Assembly in the system chassis; replace the nine (9) PHS screws, and reconnect all cables.

Restore RFS and NVRAM: • Restore system power. When the splash screen appears press the NumLock key. • Watch for the message “Press Enter to inhibit Framework” and press Enter at that time. • Login using maint and mars. • At the command prompt, type kbs followed by the Enter key. • At the command prompt, type cd RFSbackups followed by the Enter key. • At the command prompt, type rfs_restore –b <backup file name> followed by the Enter key.

The backup file name would be rfs.0, rfs.1, or any backup file chosen earlier in this procedure. Following the rfs_restore command, wait for the prompt before proceeding.

Reprogram Motherboard S/N and Revision Level: • At the command prompt, type set_sn –m00xxxxxx –ryyy followed by the Enter key. Where xxxxxx

is the Motherboard Serial Number and yyy is the Motherboard Revision Level, which you recorded above. Following the Enter key, the system should echo back the correct Serial Number and Revision Level.

• At the command prompt, type halt followed by the Enter key. Once the AirSPACE indicates a halted state, power cycle the system.

• When the splash screen appears press the NumLock key. Observing the boot sequence, allow the system to restore the RFS Backup File, and boot to the User Interface. Do not intervene in this boot sequence.

• Once the User Interface is displayed, the system should be fully operational. Current Motherboard Production Part Numbers & Revision Levels: • MOAB, AirSPACE, XLA 0030-03086-01 Revision D01 • MOAB, AirSPACE, XL 0030-03086-01 Revision B07


Verify Replacement Motherboard ERAM Programming: dmesgThis command, with redirection and filters can be used to verify proper programming and recognition of the AirSPACE ERAM during the boot sequence.

Entered Command to Verify ERAM Programming: dmesg | grep eram

Successful Result for Revision D (XLA) Motherboard. Use set_sn to check revision. eram0: <MOAB External RAM (XLA)> rev 0x00 int a irq 11 on pci2.13.0eram0: PLX register base at 0xfcfff800eram0: phys_size = 128 MB Offset f0000200eram1: <MOAB External RAM (XLA)> rev 0x00 int a irq 11 on pci3.15.0eram1: PLX register base at 0xeffff800eram1: phys_size = 128 MB Offset e0000200eram2: <MOAB External RAM & Parity Engine (XLA)> rev 0x00 int a irq 11 onpci4.15.0eram2: PLX register base at 0xdffff800eram3: <MOAB External RAM & Parity Engine (XLA)> rev 0x00 int a irq 11 onpci5.12.0eram3: PLX register base at 0xcffff400

Successful Result for Revision C (XL) Motherboard. Use set_sn to check revision. eram0: <MOAB External RAM> rev 0x00 int a irq 11 on pci2.13.0eram0: phys_size = 128 MBeram1: <MOAB External RAM> rev 0x00 int a irq 11 on pci3.15.0eram1: PLX register base at 0xeffff800eram1: phys_size = 128 MB Offset e0000200eram2: <MOAB External RAM & Parity Engine> rev 0x00 int a irq 11 on pci4.15.0eram2: PLX register base at 0xdffff400eram3: <MOAB External RAM & Parity Engine> rev 0x00 int a irq 11 on pci5.12.0eram3: PLX register base at 0xcffff400

Entered commands to reprogram AirSPACE XLA Motherboard ERAM, if required: • plx_moaberamII /dev/eram0• plx_moaberamII /dev/eram1• plx_moabpeII /dev/eram2• plx_moabpeII /dev/eram3

Entered commands to reprogram AirSPACE XL Motherboard ERAM, if required: • plx_moaberam128 /dev/eram0• plx_moaberam128 /dev/eram1• plx_moabpe128 /dev/eram2• plx_moabpe128 /dev/eram3


SECTION XI: AirSPACE System Level Tests The following series of routines allow the operator to monitor system status; check serial numbers; check hardware revisions; and monitor fan tachs and temperature sensors. Some basic network de-bugging tools are included. GENERIC COMMANDS & HOT KEYS Ctrl+Alt+F1 Drops User Interface and opens a console window. Ctrl+Alt+F2 Opens a second console window. maint AirSPACE system login. mars AirSPACE system password. kbs Followed by ENTER. Drops framework and creates a lock file in



to the command prompt. Ctrl+Alt+F3 Returns to User Interface from command mode. xilinx_eram Followed by ENTER. If the normal boot sequence was

interrupted by inhibiting the framework, execute this command prior to running the first test.

RUNNING THE SYSTEM LEVEL TEST ROUTINES All commands in this procedure are executed with the ENTER key. These tests cannot be run with the system “ON-AIR”.

• Open a console window with Ctrl+Alt+F1, and login to the system with maint and mars. • At the command prompt, type kbs and press ENTER. • At the command prompt, type the desired test, followed by the ENTER key.

set_snThis command will display the AirSPACE Serial Number; Motherboard Serial Number; and Motherboard Revision.

Entered Command: set_sn Example Result: Chassis S/N PTI20090, Motherboard S/N 00567345,

Motherboard Rev: D01

check_nvramThis command will verify the CRC returned from NVRAM:

Entered Command: check_nvram Successful Result: CRC is OK


sync_nvramThis command will re-sync NVRAM with the operating system software.

Entered Command: sync_nvram Successful Result: sync_nvram: successfully synced NVRAM

read_nvram TOCThis command will display a list of the current binary files stored in NVRAM.

Entered Command: read_nvram TOC Example Result: Entry 0, name S/N, offset 384, length 22

Entry 1, name MSC, offset 406, length 772Entry 2, name ACR, offset 1178, length 1052Entry 3, name RST, offset 2230, length 12Entry 4, name syc, offset 2242, length 512Entry 5, name RFQ, offset 2754, length 4Entry 6, name EvL, offset 2758, length 808Entry 7, name ETS, offset 3566, length 480Entry 8, name MCP, offset 4046, length 443

led_test2This command will initiate a script to test all drive sleds; indicate the settings of the (6) six pole DIP switch on the Motherboard; and exercise all drive sled LED’s:

Entered Command: led_test2 Successful Result: All sleds detected. Initiating DIP TEST.

boot_adapter_t: 0disable_plx_eeprom: 0disable_watchdog: 0test: 0spare_1: 0spare_2: 0

DIP settings are correct.COMM cables attached.Now exercising LED’s.

NOTE: An incorrect DIP Switch position will be indicated. This test is terminated with Ctrl+c.


ESStempThis will initiate a script to show current fan tach and speed; and the output of the (7) seven temperature sensors located on the AirSPACE Backplane. Sensor temperatures are in C (Centigrade) and F (Fahrenheit):

Entered Command: ESStemp Successful Result: Pluto Technologies ESS Tool

Fan 0:Status: OK Fan Speed: 42Fan 1:Status: OK Fan Speed: 43

The Box is Not Hot.

Sensor 1: 27C 80FSensor 2: 28C 82FSensor 3: 27C 80FSensor 4: 27C 80FSensor 5: 28C 82FSensor 6: 28C 82FSensor 7: 28C 82F

NOTE: The above readings are nominal values. Excessive temperature readings will cause a thermal shutdown. This will spin down all drives. Related Commands: weather

moabFanTemp

NETWORK DEBUGGING TOOLS arp -aThis command will list the IP Addresses of all devices talking to AirSPACE.

Entered Command: arp -a Example Result: gatelab.plutotech.com (10.168.67.129) at 0:a0:c9:5c:ba:13

netstat -iThis command will list the status of IN/OUT data transmissions.

Entered Command: netstat -i Example Result: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Collfxp0 1500 <Link> 00.20.13.51.62.6b 3145 0 259 0 1


netstat -sThis command will provide a detailed breakdown of all data transmissions.

Entered Command: netstat -s Example Result: ip:

12532 total packets received0 bad header checksums0 with size smaller than minimum0 with data size < data length0 with header length < data size0 with data length < header length0 with bad options0 with incorrect version number0 fragments received0 fragments dropped (dup or out of space)0 fragments dropped after timeout0 packets reassembled ok10321 packets sent from this host0 packets sent with fabricated ip header0 output packets dropped due to no bufs, etc.0 output packets discarded due to no route0 output datagrams fragmented0 fragments created0 datagrams that can't be fragmented

igmp:0 messages received0 messages received with too few bytes0 messages received with bad checksum0 membership queries received0 membership queries received with invalid field(s)0 membership reports received0 membership reports received with invalid field(s)0 membership reports received for groups to which we belong0 membership reports sent

tcp:10313 packets sent

7293 data packets (78755 bytes)0 data packets (0 bytes) retransmitted0 resends initiated by MTU discovery2986 ack-only packets (2934 delayed)0 URG only packets2 window probe packets0 window update packets32 control packets

10431 packets received3254 acks (for 77334 bytes)14 duplicate acks0 acks for unsent data7258 packets (68320 bytes) received in-sequence0 completely duplicate packets (0 bytes)0 old duplicate packets


pingIndicates stability of the network connection, from the AirSPACE to the workstation, by transferring packets between systems.

Entered Command: ping 10.168.67.244 Example Result: PING 10.168.67.244 (10.168.67.244): 56 data bytes64 bytes from 10.168.67.244: icmp_seq=0 ttl=255 time=0.045 ms64 bytes from 10.168.67.244: icmp_seq=1 ttl=255 time=0.046 ms64 bytes from 10.168.67.244: icmp_seq=2 ttl=255 time=0.042 ms64 bytes from 10.168.67.244: icmp_seq=3 ttl=255 time=0.043 msò^C--- 10.168.67.244 ping statistics ---4 packets transmitted, 4 packets received, 0% packet lossround-trip min/avg/max/stddev = 0.042/0.044/0.046/0.002 ms


SECTION XII: Error Logging

HARDWARE LOGGING To display the boot sequence log, created following a power cycle or soft boot, enter: dmesg

This log contains detailed information from each boot sequence, since the last power cycle. Hardware such as: ERAM, SCSI Disks and Controllers, Power Supplies, CPU, ACV’s, Etc. will be identified during each boot process. At the end of the log will be any kernel messages (indicated by bright white lettering) since the boot process completed. This information may be helpful in diagnosing specific system problems. A portion of a typical dmesglog is shown below: Copyright (c) 1992-1999 FreeBSD Inc.Copyright (c) 1982, 1986, 1989, 1991, 1993

The Regents of the University of California. All rights reserved.FreeBSD 3.1-STABLE #0: Fri Oct 6 11:09:39 MDT 2000

[email protected]:/build/lisafw/Alpha/1.2.a22/src/sys/compile/PRODUCTIONTimecounter "i8254" frequency 1193182 HzTimecounter "TSC" frequency 448877111 HzCPU: Pentium II/Xeon/Celeron (448.88-MHz 686-class CPU)

Origin = "GenuineIntel" Id = 0x652 Stepping=2

Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,<b24>>real memory = 134217728 (131072K bytes)avail memory = 127266816 (124284K bytes)Preloaded elf kernel "kernel" at 0xf02f0000.Preloaded splash_image_data "/splash_bmp.ko" at 0xf02f009c.Preloaded elf module "splash_bmp.ko" at 0xf02f00e8.Pentium Pro MTRR support enabledEnabled SERR# and IOCHK# NMIsProbing for devices on the ISA bus:sc0 on isasc0: VGA color <16 virtual consoles, flags=0x0>atkbdc0 at 0x60-0x6f on motherboardatkbd0 irq 1 on isapsm0 irq 12 flags 0x200 on isapsm0: model Generic PS/2 mouse, device ID 0Disabling Watchdog Timeriic0 at maddr 0xdfff0 msize 16 on isaweather0 at maddr 0xdfff0 msize 16 on isanvram0 at maddr 0xd0000 msize 1008 on isanvram0: size is 32768 bytesbpeeprom0 at maddr 0xdfff0 msize 16 on isavga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isanpx0 on motherboardnpx0: INT 16 interfacensu0 at 0x3f8-0x3ff irq 4 on isansu0: type 16550Ansu1 at 0x2f8-0x2ff irq 3 on isansu1: type 16550Afxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 11 on pci0.13.0fxp0: Ethernet address 00:20:13:51:62:6bbridge0: <DEC 21150 PCI-PCI bridge> rev 0x04 on pci0.17.0bridge1: <DEC 21150 PCI-PCI bridge> rev 0x04 on pci0.19.0bridge2: <DEC 21150 PCI-PCI bridge> rev 0x04 on pci0.20.0Probing for devices on PCI bus 1:bridge3: <DEC 21150 PCI-PCI bridge> rev 0x04 on pci1.12.0bridge4: <DEC 21150 PCI-PCI bridge> rev 0x04 on pci1.14.0Probing for devices on PCI bus 2:


eram0: <MOAB External RAM (XLA, 55MHz)> rev 0x00 int a irq 11 on pci2.13.0eram0: PLX register base at 0xfcfff800

eram0: phys_size = 128 MB Offset f0000200set 9080 threshold register to 0x7c3Delayed reads enabled

Registered engine at base address 0xf0000200base mask 0x7ffffff: base test 0xf0000000ahc19: Host Adapter Bios disabled. Using default SCSI device parameterseram1: <MOAB External RAM (XLA, 55MHz)> rev 0x00 int a irq 11 on pci3.15.0eram1: PLX register base at 0xeffff800

eram1: phys_size = 128 MB Offset e0000200set 9080 threshold register to 0x7c3Delayed reads enabled

Registered engine at base address 0xe0000200base mask 0x7ffffff: base test 0xe0000000Probing for devices on PCI bus 4:avioII0: <Pluto A/V I/O W (270/360 Mbps)> rev 0x00 int a irq 10 on pci4.14.0avioII0: memory size is 0x1000000, limiting to 0x800000

set 9080 threshold register to 0x7c3Registered engine at base address 0xde000000base mask 0x1000000: base test 0xde000000eram2: <MOAB External RAM & Parity Engine (XLA, 55MHz)> rev 0x00 int a irq 11 onpci4.15.0eram2: PLX register base at 0xdffff400

pe2: phys_size = 128 MB Offset d0000200set 9080 threshold register to 0x7c3

Registered engine at base address 0xd0000200base mask 0x7ffffff: base test 0xd0000000Probing for devices on PCI bus 5:raidioctl: RAIDIOCONFIGraidioctl: RaidFS size = 204768raidioctl: DIOCGDINFO, fs_status 0raidioctl: RAIDIOSTATraidioctl: DIOCGDINFO, fs_status 0raidioctl: DIOCGPART, fs_status 0

Note: Drives listed in dmesg are not necessarily mapped one-to-one between disk address and hardware controller.

MOAB Controllers:

da0 at ahc0 bus 0 target 0 lun 0 da1 at ahc1 bus 0 target 0 lun 0 da2 at ahc2 bus 0 target 0 lun 0 da3 at ahc3 bus 0 target 0 lun 0 da4 at ahc4 bus 0 target 0 lun 0 da5 at ahc5 bus 0 target 0 lun 0 da6 at ahc6 bus 0 target 0 lun 0 da7 at ahc7 bus 0 target 0 lun 0 da8 at ahc8 bus 0 target 0 lun 0 da9 at ahc9 bus 0 target 0 lun 0

SCSI Daughter Card:

da10 at ahc18 bus 0 target 0 lun 0 da11 at ahc19 bus 0 target 0 lun 0 da12 at ahc16 bus 0 target 0 lun 0 da13 at ahc17 bus 0 target 0 lun 0 da14 at ahc14 bus 0 target 0 lun 0 da15 at ahc15 bus 0 target 0 lun 0 da16 at ahc12 bus 0 target 0 lun 0 da17 at ahc13 bus 0 target 0 lun 0 da18 at ahc10 bus 0 target 0 lun 0 da19 at ahc11 bus 0 target 0 lun 0


SOFTWARE LOGGING Software logs are named runa, and are stored in the /var/tmp directory. The last (4) four logs are automatically saved, and may be listed by issuing: ls –l /var/tmp, from the root directory. See the following example:

fst104:~{1} ls -l /var/tmptotal 88drwxrwxrwt 2 root wheel 512 Oct 12 07:38 .X11-unix-rw-r--r-- 1 root wheel 43 Oct 12 07:38 lock.runbs-rw-r--r-- 1 root wheel 16117 Oct 12 07:38 runa-rw-r--r-- 1 root wheel 19177 Oct 12 07:35 runa.0-rw-r--r-- 1 root wheel 11829 Oct 12 03:27 runa.1-rw-r--r-- 1 root wheel 19521 Oct 12 02:50 runa.2-rw-r--r-- 1 root wheel 19431 Oct 10 09:14 runa.3

Each log has a date stamp associated with the last time the file was updated, which will not correspond to when the file was originally created. These files are created when the GUI job starts, and end when the GUI job ends. The logging is held in a recursive buffer, which is written to disk when an orderly shutdown/reboot occurs (i.e. power cycles with the GUI up will cause the loss of the current logging.) Only the (4) most recent logs are saved. These are runa.0 through runa.3, with runa being the recursive log. The following example is a portion of a runa log:

fst104:/var/tmp{3} cat runa.003:27:09.5024 F161:1 bswP.c 1365: BSM PRODUCTION03:27:09.5250 F161:1 bswP.c 222: FRAMEWORK version: 1.2.a22 2000-10-0603:27:09.5251 F174:2 bswP.c 1389: bswP is now at Realtime Priority 503:27:11.5371 F161:1 bsCommon.c 2216: unable to access display :003:27:11.5373 F 0:2 bsCommon.c 2219: nvsys.remote=003:27:11.5378 F181:2 smpte.c 60: Set SMPTE Alarm RESET03:27:11.5395 F161:1 bswP.c 960: AVIO argument specified, but no AVIOargument in the config file03:27:11.5395 F161:1 bswP.c 960: AVIO argument specified, but no AVIOargument in the config file03:27:11.5395 F161:1 bswP.c 960: AVIO argument specified, but no AVIOargument in the config file03:27:11.5397 F161:1 hdwr.c 229: Found real eram hardware! Goody!!Goody!!!03:27:13.5677 F161:1 hdwr.c 242: programmed /dev/eram0 with hex file"/usr/home/pluto/config/mpe3.hex"03:27:13.5679 F 99:1 sconfig.c 214: Attempting to upgrade back version(8) of MSC key.03:27:13.5679 F 99:1 sconfig.c 224: Upgraded to version 9.03:27:13.5681 F161:1 hdwr.c 155: open of /dev/avioII0.videopsuccessful03:27:13.5681 F161:1 hdwr.c 157: Found real AVIO hardware!! Oh Boy!!03:27:16.7129 F161:1 hdwr.c 192: programmed /dev/avioII0.videop withhex file "/usr/home/pluto/config/avio270.hex"

The current runa log consists of two parts. The first portion is written to disk as the UI is started, which is useful in determining if all hardware and software processes initialized normally. The second portion is written into a circular buffer and contains all events after the UI has started. The information in this buffer is not normally written to disk until the UI is restarted, which in many instances means the buffer is overwritten by the time the user has a chance to flush the logs with a UI or system reset. That means the important (anomalous) event logging may be missed or overwritten. To dump the current contents of this log, without impacting the current operation of the system, you would issue the dump_log command. This writes the circular buffer logging into the runa log, which may then be viewed the same way as the archived versions. Software logging is always enabled, but the degree and level of logging may be varied by changing logging parameters. Contact Technical Support if you feel the need to enable advanced logging.


Common Errors Error or Symptom Diagnosis and Correction TMC2072 during boot-up Reported at bootup or in dmesg logging. Error may occur once or twice during

bootup, as part of a normal initialization of this chip. If repeating is excessive (>4x per bootup), problem may indicate a poorly seated RIF connection to one or more ACV Cards, or failed RIF components. Reseat RIF – verify no bent pins on all ACV-RIF connections. Replace RIF if problem persists.

TMC2193 during boot-up Reported in dmesg logging. Indicates possible DIO malfunction, which

would also be indicated by bad Analog Video outputs and good Digital Video out. Reseat ACV DIO connection and replace if problems persist.

Recorded Video is bad Verify record channel indicates a good/solid input (green indicator to far

right of channel in UI). If red, or flashing, you need a valid SDI input to the card. Next, swap input with a known good channels input. Re-record. Ensure playback on known good channel. Reseat card. Replace ACV as necessary.

Audio output is bad or silent Reload (acvLoadDSP) DSP for bad ACV. If problem continues, verify no

bent pins on ACV-RIF connection. Reseat ACV card. Replace ACV if problem persists.

Serial Digital output bad Verify event plays back on another channel – if not, your record is bad. If

playout is good on another channel, verify not a switching issue by connecting directly to ACV output – either composite or SDI. If either are good, your SDI should be good (composite is derived from the SDI). If not, try rebooting to see if problem clears. If problem is persistent, try reseating the ACV. Replace card as necessary.

Analog/Composite Video output bad Verify composite output (top BNC connection on ACV) is good. If so,

verify BOB cables are correct (if new installation) – specifically, the VGA cable is connected between BOB and appropriate chassis connection. Reseat RIF if problem persists, checking for bent pins at the ACV-RIF connection. Replace ACV as last resort.

422 communication errors If new installation, verify MultiI/O cable is connected between BOB and

correct ACV location. If using VDCP (Record/Playlist configuration), ensure channel is set to REMOTE on CONTROLS menu. Verify proper configuration in CONTROLLER menu (verify proper configuration and protocol). Reset all 422 ports by toggling one protocol setting on this menu, then pressing OK to save – warning should be given that all streams will be stopped. If problem persists, run the “acvSerial” diagnostic test to verify 422 loop-back. If failing, replace BOB and cable then rerun test to determine if BOB, MultiI/O cable, or ACV may be at fault. Next, reseat RIF – look for bent pins on the ACV-RIF connection. Last, replace ACV if above steps do not resolve.

Documents

Multi-Channel Server Maintenance & Diagnostics...Backplane Programming Entered command to program Backplane Serial Number & Revision Level: • set_bp –cPTIXXXXX –bYYY -rZZZ Where