Troubleshooting PrizmTRONG> Troubleshooting Prizm
Analog
CLICK
HERE
for Procomm Plus Configurations for use with
the Prizms.
Click on the following symptoms for possible
solutions
.
1)
The
Prizm does not run any breaks.
2)
Prizm
cannot find reset (beginning of tape, BOT) mark of tape.
3)
Prizm
finds reset mark but cannot read directory.
4)
Prizm
cannot read spot identification mark but, reads directory and other spots
marks correctly.
5)
Prizm
reads directory but cannot find spots.
6)
When
loading or parsing event lists on the Prizm the message "Skip Breaks Not
Supported"
is
received.
7)
.
7)
Scheduled
breaks are skipped.
8)
Tones
on headend tapes can be heard over the air.
9)
Ads
start into video as opposed to just prior to video at the beginning of
the spot play on-air.
10)
Ads
roll to air either too early or too late.
11)
The
ad did not run and has been logged as "bad match."
12)
Unable
to access the Prizm from a locally connected computer at the headend.
13)
Prizm
log indicates "bad match" even though spot appeared to have run correctly.
14)
Unable
to install or download event list to Prizm(s).
15)
Unable
to remotely log onto Prizms but, the dial out seems to be happening normally
and
modems
connect properly.
16)
The
event list schedule does not change lists from one day to the next.
17)
When
I log onto the Prizm I have a hard time accessing logs and the status message
says
that
the system is waiting for the log flash to become idle.
18)
I
cannot log onto the Prizm locally and the log on screen says that it is
currently logged on remotely.
19)
Whenever
I attempt to fully load my chassis with 16 cards (including the CPU) the
system
does
not see the card(s) in the first slot(s).
Symptom: The Prizm does
not run any breaks, assuming tapes are good, and decks
are parked at the designated cue points.
Probable Cause:
1. DTMF input or contact closure is
not wired or is not wired correctly.
2. DTMF levels are too high or too
low.
3. There is a "bad" Wegener board.
4. DTMF tones are not entered or are
entered incorrectly in the network configurations setup menu.
5. DTMF tones are not connected to
the location where the Prizm is configured to listen for the tones as
specified in the
network configurations setup.
6. Prizm is malfunctioning. Bad DNET
or DNET I/O card.
Possible Solution:
1. Check wiring of baseband video or
source signal to the Wegener demodulator and DTMF tones or contact closure
from
Wegener demodulator to DNET I/O card.
2. Verify that the DTMF levels are
one volt peak-to-peak (1 v p-p) as measured across the audio wires (+ to
ground and - to
ground for balanced audio or + to
ground for unbalanced audio).
3. Check output of Wegener boards for
correct level.
4. Check Prizm network configurations
setup menu for correct DTMF entries for the specific network.
5. Check to verify that tones are
connected o verify that tones are
connected on the DNET I/O to the location specified in the network
configuration setup menu
such as DTMF input, G.P.
input, audio left, audio right, etc.
6. Isolate and repair malfunctioning
card.
Symptom: Prizm can't find reset (beginning of tape,
BOT) mark of tape.
Probable Cause:
1. Reset mark not on tape or marked
to far into tape.
2. Bad audio/video cable from deck to
inserter.
3. Bad tape deck (bad audio head,
audio output port, etc.).
4. Malfunctioning VCI or VCI I/O
card.
Possible Solution:
1 Reinitialize the tape using your
usual tape marking system to mark the tape with a valid reset mark.
2. Switch audio/video cable harness
to determine if cable is bad.
3. Replace tape deck.
4. Isolate malfunctioning card and
repair/replace the VCI or Voning card and
repair/replace the VCI or VCI I/O card.
Symptom: Prizm finds reset
mark but cannot read directory.
Probable Cause:
1. Bad tape directory.
2. Dirty tape deck audio head.
3. Bad tape deck, out of calibration.
4. Skew of tape deck not set
correctly.
5. Bad or damaged tape and/or master
tape.
Possible Solution:
1. Correct tape directory, then
reload tape directory into Prizm memory.
2. Clean tape deck audio heads.
3. Replace deck. Service bize="2"> 3. Replace deck. Service bad deck.
4. Verify skew settings on VCR.
5. Verify tape and master tapes are
OK and then correct or replace defective tape.
Symptom: Prizm cannot read spot
identification mark but reads directory and other spot marks correctly.
Probable Cause:
1. Bad spot identification mark.
2. Audio drop out on tape at spot
mark location.
3. Spot identification mark does not
match the directory for this spot.
4. Improper audio level marking on
this spot.
5. Tape damage at the spot mark
location.
Possible Solution:
1. Scan the tape for correct spot
marks and then re-mark spot(s) as necessary.
2. Replace tape.
3. Scan directory and spot then
remark spot or directory to correct which ever is in error.
4. Verify audio level and remark as
necessary. Maintain approximately -2 VU on FSK tape marks.
SK tape marks.
5. Replace tape.
Symptom: Prizm reads directory but can't find
spots.
Probable Cause:
1. Spot not marked or marked at wrong
location.
2. Inconsistent or "broken" control
track on tape.
3. Defective VCR.
4. Bad tape.
Possible Solution:
1. Verify that spots on tape are
marked correctly by scanning the tape.
2. Re-black tape, then insert edit
audio/video back onto tape.
3. Replace VCR.
4. Replace tape.
Symptom: When loading or parsing event lists on the
Prizm the message "r parsing event lists on the
Prizm the message "Skip Breaks Not Supported" is received.
Probable Cause:
Down level operating system software is running on the Prizm.
Possible Solution:
Contact Texscan MSI to obtain the latest version of analog
Prizm operating code and load it into the Prizm. Early versions of the
Prizm operating code did not support the "Skip Break" functionality.
Symptom: Scheduled breaks
are skipped.
Probable Cause:
1. There are "skip this break"
commands in the event list.
2. DTMF tones are not at the proper
voltage level at the input to the DNET I/O card, or at the baseband input
to the Wegener
demodulator card.
3. Dayparts are set too close to
avail times to allow decks to cue up.
4. Tape deck(s) are in bypass due to
one or more of many possible reasons.
5. VCR is defective
Possible Solution:
Possible Solution:
1. Check event list for syntax errors
(a space preceding the spot will cause the current spot to be skipped).
2. Verify that DTMF tone audio level
is one volt peak-to-peak (1 v p-p), +/- .2 v p-p, at the input to the
Prizm DNET I/O
card. Verify that
the Wegener card is receiving 1 v p-p baseband video at its input.
3. Check that time windows are not
too close to avail times (not less than five minutes).
4. Check logs for any VCR error
conditions.
5. Replace or repair defective VCR.
Symptom: Tones on headend tapes
can be heard over the air.
Probable Cause:
1. The tape is marked above
recommended levels.
2. The Prizm inserter has been wired
incorrectly at the headend.
3. Tape spot marks have been marked
on the wrong audio track.
Possible Solution:
1. Re-mark tape so that FSK marking
is done at approximately -2 VU.
is done at approximately -2 VU.
2. Correct audio wiring at headend,
satellite audio for appropriate configuration.
3. Re-mark tape on audio track one
(1) or left audio.
Symptom: Ads start into video
as opposed to just prior to video at the beginning of the spot play on-air.
Probable Cause:
1. Time averaging has been set to
"Disabled" in the VCR/Decks, Time to Play setup configurations.
2. Ads are not marked correctly.
3. Tape deck need to be re-calibrated
or rebuilt.
Possible Solution:
1. Verify that time averaging is set
to "Enabled" in the VCR/Decks, Time to Play setup configurations.
2. Verify that spots are marked at
least three frames prior to first frame of video.
3. Send deck to a Sony authorized
repair center for servicing.
Symptom: Ads roll to air either too
early or too late.
ProbablB>
Probable Cause:
1. The ad start delay or pre-roll time needs to be
adjusted or set for the specific network.
2. The deck is not coming up to speed
correctly.
3. The time averaging is disabled in the configurations
setup.
4. The ads are not marked correctly.
Possible Solution:
1. Adjust the ad start delay longer
or shorter as needed to meet the requirements of the specific network.
2. Rebuild or re-calibrate the tape
deck.
3. Set the time average mode to
"Enabled" in the configurations setup.
4. Verify that the ads are marked
according to specifications.
Symptom: The ad did not run and
has been logged as "bad match."
Probable Cause:
1. The spot on the tape is not in the
tape's directory.
2. The spot ID does not match the
information exactly that is in the directory.
3. Audio drop out occurring in the
directory or at the spot locring in the
directory or at the spot location.
Possible Solution:
1. Add spot to the tape directory.
2. Scan the tape and manually verify
the directory information with the spot ID mark. Remark the spot or update
the directory
to correct which ever is not accurate.
3. Replace tape.
Symptom: Unable
to access the Prizm from a locally connected computer at the headend.
Probable Cause:
1. The baud rate of the
communications software does not match the baud rate set on the Prizm.
2. One or more communications
software parameters are not set correctly.
3. The connector or cable from the
computer to the first Prizm in the daisy chain is not connected properly.
4. Incorrect key sequence pressed on
the computer while attempting to log onto the inserters.
5. One or more Prizms have the same
log on identification number.
6. One or more Prizms are "locked
up."
One or more Prizms are "locked
up."
7. One or more Prizms are turned off.
Possible Solution:
1. Verify the correct, and same baud
rate are set up both on the computer communications software and the
Prizm.
2. Verify that the communications
software's configuration parameters have been set up properly.
3. Verify that the cable for the
Prizm is connected to the appropriate port of the computer and then to the
direct connect input
on the Prizm. On the Prizm this
port is labeled Test or Local In.
4. Check that the key sequence being
entered when attempting to log onto the inserters is consistent with
manual instructions.
Normally, to log onto an inserter
type <Cntrl> + <\> together followed by the log on ID number
of the unit you are trying to
log onto.
5. Verify that all the Prizms are
configured for different log on ID numbers.
6. Reset each Prizm by pressing the
reset button located on the CPU board. This will cause a recueing of all
attached tape
decks and may result in missed breaks.
7. Verify that all Prizms are
properly powered.
Symptom: Prizm log indicates
"bad match" even though spot appeared to have run correctly.
Probable Cause:
1. Slight difference between spot ID
mark at ad location and tape directory exists.
2. Dirty audio heads on tape deck.
3. Drop out on tape.
4. Bad brakes on tape deck.
5. Skew on tape deck not set
correctly.
Possible Solution:
1. Scan the directory and the spot
mark to find differences. Re-mark if necessary.
2. Clean the tape deck.
3. Replace the tape.
4. Rebuild the tape deck.
5. Verify that the skew adjustment on
the deck is set correctly.
Symptom: Unable to install
or download event list to Prizm(s).
Probable Cause:
>
Probable Cause:
1. Event list for the particular
network does not exist or is incorrectly named.
2. Pool name is not correct.
3. Communications with Prizm is not
occurring.
Possible Solution:
1. Verify event list exists and is
named properly.
2. Verify correct pool name and
change if necessary.
3. Re-establish a functioning
communications link with the Prizm(s).
Symptom: Unable to remotely
log onto Prizms but the dial out seems to be happening normally and modems
connect properly.
Probable Cause:
1. Error in modem communications or
configurations.
2. Telephone line problems.
Possible Solution:
1. Verify that modems have been
initialized properly and that communication software and baud rates are
configured
appropriately.
<; appropriately.
2. Verify the correct operation of
the telephone lines.
Symptom: The event list schedule
does not change lists from one day to the next.
Probable Cause:
1. The event list from the first day
is not ending before the next day's event list is scheduled to begin.
2. CPU configuration set so that the
event list does not change.
Possible Solution:
1. Verify that the event list for one
day ends before the beginning of the next day's schedule. For instance,
say that the Prizm
was configured to have a start of
day at 12:01 A.M. I would always want to make sure that all schedules
terminate prior to
12:00 Midnight and do not start
until about 12:02 A.M. This type of approach will allow the Prizm's event
list schedules to
roll-over properly to the next day's
schedule.
2. Configure the CPU set up so that
the event lists will change in the desired manner.
Symptom: When I log onto
the Prizm inserter I have a hard time accessing logs and the status message
says
that the system is waiting for the log flash to become idle.
Probable Cause:
The system is stuck in a logging mode and will
not allow access until it is finished writing the current logs.
Possible Solution:
Reset the Prizm by either pressing
the CPU reset button on the CPU board or force the system to the boot code
by performing a jump to boot operation.
- Then go back to the main operating
code.
- Download all event logs for
verification purposes.
- Finally, it is recommended that an
erase log flash operation be performed. Following the erase log flash
operation do not access the system for approximately 5 minutes. This
will allow the last 400 logs which were stored redundantly on the CPU
card to be written back into log flash memory on the DNET(s).
- Once these steps have been followed
you can view the log flash status and see that only one flash chip will
currently be written to and that all future records are stored on the
flash chips in a sequential manner.
Symptom: I cannot
log onto the Prizm locally and the log on screen says that it is currently
logged on remotely.
Probable Cause:
1. The system is being accessed
remotely by modem from another location.
2. The remote communications port is
hung open.
Possible Solution:
1. Wait for the remote user to log
off or force the remote user off by pressing the CPU reset button. Be
aware that the CPU
will force all decks to rewind,
reset and recue before continuing spot insertion.
2. Reset the CPU by pressing the
reset button on the CPU card. Once again this will cause a recueing of all
decks and some
breaks may be missed because of the
recueing.
Symptom: Whenever I attempt to fully load my chassis
with 16 cards (inclload my chassis
with 16 cards (including the CPU) the system does not see
the card(s) in the first slot(s).
Probable Cause:
The chassis motherboard was never modified for an Engineering
Change Order (ECO) that was implemented in 1995 and the system is
experiencing excessive loading on the busses.
Possible Solution:
Have Texscan MSI implement the modifications to the Prizm
motherboard which will fix this condition.
|
