Focusing on the future.     

  Texscan MSI - 801.956.0000 - fax:801.956.0750 - 2210 West Alexander Street, Suite A - Salt Lake City, UT 84119

Troubleshooting ComSerters (CSR) and Consert

CLICK HERE for Procomm Plus Configurations for use with the CSRs.

For the Local TV Avails Guide click Avail Guide.


Click on the following symptoms for possible solutions:

1)  The audio output levels from the ComSerter is bad .
2)  The ComSerter jumps to the wrong event list or does not change event lists.
3)  The ComSerter does not run any breaks.
4)  The ComSerter shows dayparts of event lists, but not the commercials.
5)  The ComSerter can't find reset (beginning of tape, BOT) mark of tape.
6)  The ComSerter finds reset mark but cannot read directory.
7)  The ComSerter can't read spot ID mark, but reads directory and otheut reads directory and other spot marks correctly.

8)  The ComSerter reads directory, but can't find spots.
9)  Scheduled breaks are skipped.
10) Tones on headend tapes can be heard over the air.
11)
Ads start into video as opposed to just prior to video at the beginning of the spot play on-air .
12) Ads roll to air either too early or too late.
13) The ad did not run and has been logged as "bad match."
14) Unable to access the ComSerter from the WYSE terminal at the headend.
15)
The ComSerter log indicates "bad match" even though spot appeared to have run correctly .
16) Unable to install or download event list to ComSerter.
17) Unable to retrieve any logs nable to retrieve any logs from ComSerter.
18) The ComSerter printer output changes from "Serial through terminal auxiliary" to "Parallel" seemingly automatically.

19) Unable to log onto ComSerter(s) from the F3 menu in Consert, but F1 will dial properly .
20) Consert finds ComSerter, but does not display status screen.
21) Consert will not accept market or network name in the F1 (Connect ComSerters menu.
22) Consert will not control modem.
23) Cannot transfer logs to Traffic and Billing system.
24) "Printed sorted log reports" does not print.
25) Consert will not print logs while logged on to ComSerter.
26) Erratic or "wrap around" printing occurs when logs are printed from Consert.
27) Unable to communicate with US Robotics Sportster FaxModems.
28)  Intermittent communication with the ComSerter.
29)  Unable to use COMPULINK with EditExpress.



Symptom: The audio output levels from the ComSerter is bad.
Probable Cause:
        1) The audio input levels into the ComSerter is high or low.
        2) The audio output levels out of the ComSerter is high or low.
Possible Solution:
        1) Verify that the satellite input levels are correct, if not readjust satellite audio levels.
        2) Verify that the ComSerter audio output levels are correct, if not readjust them. Use the turnable potentiometers to adjust levels.


Symptom:  The ComSerter jumps to the wrong event list or does not change event lists.
Probable Cause:
        1) The "goto" statement at the end of an event list is not correct. of an event list is not correct.
        2) The event list has a syntax error.
        3) There is no "goto" statement at the end of the event list.
Possible Solution:
        1) Verify that all even lists are ending at the same day part "goto" statement.
        2) Verify event list syntax as described in the CSR operations manual.
        3) Verify that all event lists have a "goto" statement at the end of the list.


Symptom:  The ComSerter does not run any breaks, assuming tapes are good, and the decks are parked at the 
designated cue points.
Probable Cause:
        1) DTMF sub carrier 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 in the DTMF table (F9) in the ComSerter c table (F9) in the ComSerter configurations setup menu.
        5) DTMF tones connected to the location where the ComSerter is being told to listen for the tones as specified in the (F9) configurations setup or with board jumper settings.
        6) ComSerter not set to the correct cue sequence for the desired network in the configurations setup menu.
        7) ComSerter is malfunctioning.
Possible Solution:
        1) Check wiring of base band video or source signal to the Wegener demodulator and sub carrier or contact closure from Wegener demodulator unit to ComSerter.
        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 wave form.
        4) Check ComSerter setup menu (F9 of setup configurations) for correct DTMF table entries for the specific network.
        5) Check to verify that tones are connected to the location specified in the configuration setup menu (F9) for CSR 194, 294, 194D, 292D and 294D models. This is controlled by the H jumper on CSR 191 and 192 models.
        6) Verify that ComSerter cue sequences are correct for the desired networks in the DTMF table of the configuration setup menu (F9).
        7) Repair Comserter.


Symptom:  ComSerter shows day parts of event lists, but not the commercials. 
Note: The probable cause and correction may only be troubles with one the tapes being utilized.
Probable Cause:
        1) One or more of the spots not listed in the tape directory.
        2) Event list syntax error.
      &nbs;      3) No directory in ComSerter memory.
        4) Wrong VCR listed in event list (such as tapes only in A and B decks, but the event list is calling for the spots to run from the C and D decks.
        5) Holes or missing spot(s) in any tape directory on the ComSerter.
Possible Solution:
        1) Verify event list printout of directories for the tapes loaded for the system.
        2) Verify event list syntax using the F8 (Create/Edit Event List) functions in the Consert software's main menu. Make sure there are no spaces preceding the spot (i.e. ; A3,B4 = > should be ;A3,B4;).
        3) Rewind and reset tapes to reload tape directories into the ComSerter memory.
        4) Verify that spots are preceded by an existing VCR that has a valid tape loaded.
        5) Verify all spot locations on a tape directory are filled and have not been left blank.


Symptom: ComSerter cannot find reset (beginning of tape, BOTeset (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) FSK or Digital marking modes are not set to match correct type of tape marking actually being utilized.
        5) Malfunctioning ComSerter.
Possible Solutions:
        1) Reinitialize the tape to mark tape with valid reset mark.
        2) Switch audio/video cable harness to determine if cable is bad.
        3) Replace tape deck.
        4) Verify marking mode corresponds to the actual mode being utilized.
        5) Repair ComSerter.


Symptom: ComSerter finds reset mark but cannot read directory.
Probable Cause:
        1) Bad tape directory.
   &nry.
        2) Dirty tape deck audio head.
        3) Bad tape deck, out of calibration.
        4) Skew of tape deck not set correctly.
        5) Bad tape and/or master tape.
Possible Solutions:
        1) Correct tape directory, then reload tape directory into ComSerter memory.
        2) Clean tape deck audio heads.
        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: ComSerter 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 same spot location.
   spot location.
        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 with another 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 0 VU for digitally marked tapes and approximately -2 VU for tapes marked using FSK.
        5) Replace tape.


Symptom: ComSerter reads directory but cannot find spots.
Probable Cause:
        1) Spot not marked or marked at wrong location.
        2) Inconsistent or "broken" control track on tape.
        3) Defective VCR.
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.


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 ComSerter, or at the base band input to the Wegener demodulator card.
        3) Dayparts are set too close to avail times to allow decks to cue up properly.
        4) Tape deck(s) are in bypass due to one or more of many possible reasons.
        5) VCR is defective.
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), +/- 0.2 v p-p base band vide/- 0.2 v p-p base band video at its input.
        3) Check that day parts are not too close to avail times (not less than 5 minutes).
        4) Check error trail for any VCR error conditions that are being logged.
        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) ComSerter has been wired incorrectly at 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 and Digital marking is done at approximately 0 VU.
        2) Correct audio wiring at headend, satellite audio right in/out for mono.
        3) Re-mark tape on audio track 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 "OFF" in 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 "ON" in 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.
Probable Cause:
        1) The ad start delay, pre-roll time, needs to be adjusted or set for the specific network being inserted upon.
        2) The deck is not coming up to speed correctly.
        3) The time averaging is set to "OFF" in the configurations setup. n 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 "ON" in the configuration setup.
        4) Verify that the ads are marked according to the ComSerter operations manual.


Symptom: Ad does not run and has been logged as "bad match."
Probable Cause:
        1) The spot on the tape is not in the tapes 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 location.
Possible Solution:
        1) Add spot to the tape directory.
        2) Scan the tape and manually  verify the directory information with the spotory information with the spot ID mark. Remark the spot or update the directory to correct which ever is not accurate.
        3) Replace the tape.


Symptom: Unable to access the ComSerter from the WYSE terminal at the headend.
Probable Cause:
        1) The baud rate of the WYSE terminal does not match the baud rate set on the ComSerter.
        2) One or more WYSE terminal parameters are not set in such a way as to allow communications between the terminal and the ComSerter.
        3) The ribbon cable from the WYSE to the first ComSerter in the daisy chain is not connected  to the correct port.
        4) Incorrect key sequence pressed on the WYSE terminal while attempting to log onto the inserters.
        5) One or more ComSerters have the same log on ID.
        6) One or more ComSerters are "locked up."
        7) One or more ComSerters are turned off.
Possible Solution:
        1) Verify;    1) Verify the correct, and same baud rate are set up both on the WYSE terminal and ComSerter.
        2) Verify that the WYSE terminal configuration parameters have been set up in such a way as to permit communications between the terminal and the inserter(s).
        3) Verify that the cable for the ComSerter is connected to the modem port of the WYSE terminal and then to the terminal (or CRT) port on the ComSerter.
        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 press <CTRL> + <\> together followed by the log on ID number of the ComSerter you are trying to log to.
        5) Verify that all the ComSerters are configured for different log on ID numbers.
        6) Reset each ComSerter by pressing the reset button located on the front of the control board.
        7) Verify that all ComSerters are properly powered and turned on.


Symptom: ComSerter log indicates : ComSerter 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 exist.
        2) Dirty audio heads on tape deck.
        3) Drop out on tape.
        4) Bad breaks on tape deck.
        5) Skew on tape deck no set correctly.
Possible Solution:
        1) Scan the directory and the spot mark to find difference. Re-mark if necessary to correct whichever is not correct. 
        2) Clean the tape deck.
        3) Replace the tape.
        4) Rebuild the tape.
        5) Verify that the skew adjustment on the deck is set correctly.


Symptom: Unable to install or download event list to ComSerter.
Probable Cause:
        1) Event list for the particular network does not exist.
   &nb.
        2) ComSerter event list buffer is full (i.e. all sixteen lists are being used).
Possible Solution:
        1) Use the F8 functions in Consert to verify that the event list does exist and that it is correct, then transfer the event list to the ComSerter.
        2) Delete one or more event lists on the ComSerter.


Symptom: Unable to retrieve any logs from ComSerter.
Probable Cause:
        1) Error in pointer file in Consert software pointer file.
        2) Data entry error in Consert F3 menu.
        3) One or more ComSerters are turned off.
        4) Date wrong in one or more ComSerters.
Possible Solution:
        1) From Consert main menu press <ALT> + <F3>, press <F6> and verify the pointer file data. Correct if necessary.
        2) Correct data entry error in Consert F3 menu data.
             3) Verify that all ComSerters are powered and are turned on.
        4) Correct date in the ComSerter(s).


Symptom: The ComSerter printer output changes from "Serial through terminal auxiliary" to "Parallel"  seemingly automatically.
Probable Cause:
        1) The Consert F7 menu is set to "Parallel."
Possible Solution:
        1) In the Consert F7 menu, set the printer output to "A" (Serial Aux).


Symptom: Unable to log onto ComSerters from the F3 menu in Consert, but F1 will dial properly.
Probable Cause:
        1) Contaminated market definitions table (F2).
        2) Error connecting modems.
Possible Solution:
        1) Delete market definitions table and re-enter data.
        2) Some error connecting modems will not allow certain functions. Replace modem orin functions. Replace modem or disable error correction. You also may try reloading Consert.


Symptom: Consert finds ComSerter, but does not display status screen.
Probable Cause:
        1) Wrong baud rate set in F7 menu screen.
        2) Two or more ComSerters are set with the same ID number.
        3) Error in market definitions table.

Possible Solution:
        1) Check modem baud rate setting in F7 (Set Up System) menus screen.
        2) Verify that all ComSerters have a different ID number.
        3) Check the market definition table and correct errors.


Symptom: Consert will not accept market or network name in the F1 (Connect to ComSerters) menu.
Probable Cause:
        1) Error in market definition table.
        2) Entering incorrect market or network.
&nbsrect market or network.
        3) Contaminated market definition table.
Possible Solution:
        1) Check market or network by pressing <ALT> + <F9> to Display Markets or <ALT> + <F10> to Display Channels and check for errors in market or channel definitions.
        2) Enter correct market or channel (network) information.
        3) Delete market definition table and re-enter information.


Symptom: Consert will not control modem.
Probable Cause:
        1) Modem not set or configured correctly.
        2) Computer to modem cable reversed.
        3) Bad phone line.
        4) Modem connected to wrong port on computer.
        5) Computer switch settings not configured correctly.
        6) Consert program corrupted.
        7) Wrong version of Consert if installing on n of Consert if installing on a 386/486 computer or on a 286 computer that has a different style UART configuration for the COM port than the previous versions of computers utilized.
Possible Solution:
        1) Check modem switch settings as per installation manual for the particular ComSerter and make of modem.
        2) Check to make sure that the computer to modem cable is properly installed.
        3) Verify proper phone line operation.
        4) Verify that the modem cable is connected to COM 1 from the computer for modem operation or from COM 2 from the computer for direct connection to the ComSerters.
        5) Verify computer switch settings as per computer installation manual.
        6) Reload Consert software onto computer.
        7) Check with Texscan MSI as to your particular computer to see if there are known problems relating to using the particular type of computer in this application.


Symptom: Cannot transfer logs to Traffic and Billing System.
Probable Cause:<
Probable Cause:
        1) No log.clk file in the CSC190 directory.
        2) Log.clk file contains no data.
        3) Traffic and Billing system misconfiguration or error.
        4) Consert did not retrieve any logs from inserters.
        5) Bad link between computers.
        6) Wrong date in ComSerters.
Possible Solution:
        1) Verify that the F7 (Set Up System) menu is set for Compulink.
        2) Verify that the log.clk file is in the CSC190 directory and that it contains more than zero bytes of data.
        3) Call your Traffic and Billing vendor for assistance in troubleshooting any misconfigurations or errors.
        4) Verify that automatic log retrieval is set up correctly and that the pointer file is correct, then run the "Retrieve Logs" (F3) one time function (<ALT> + <F3>) to again attempt to pull logs from the ComSerters.
        5) Check hard link between the computer running the Consert software and tthe Consert software and the Traffic and Billing system computer for integrity.
        6) Correct date on ComSerter(s).


Symptom: "Print sorted log reports" does not print.
Probable Cause:
        1) Some or all of the information requested does not exist on the hard drive.
        2) Improper printer defined in the F7 (Set Up System) menu in the Consert software.
Possible Solution:
        1) Verify that the information requested is valid.
        2) Correct printer definition in F7 menu in Consert.


Symptom: Consert will not print logs while logged on to ComSerter.
Probable Cause:
        1) Printer is off-line.
        2) ComSerter is set to wrong printer type.
        3) ComSerter not set to proper interface in set-up menu (usually "serial through terminal aux").
 &ugh terminal aux").
        4) Consert printer type incorrect.
        5) Printer cable bad or not connected.
        6) No logs to print.
Possible Solution:
        1) Return printer to on-line status.
        2) Correct printer type on ComSerter setup screen.
        3) Change ComSerter setup screen F8 (Set Printer Output) to proper setting for your location; usually set to "serial through terminal aux."
        4) Verify Consert printer type F7 (Set Up System) main menu then <ALT> + <F3>.
        5) Verify proper connection of printer cable.
        6) Verify that there are no logs in the ComSerter available to print.


Symptom: Erratic or "wrap around" printing occurs when logs are printed from Consert.
Probable Cause:
        1) Consert printer setup is incorrect.
        2) Printer setup features sp; 2) Printer setup features are incorrect.
Possible Solution:
        1) Check hex codes in printer setup table (F7 from Consert main menu, then <ALT> + <F3>.
        2) Check owner's manual of printer to determine proper settings.


Symptom: Unable to communicate with US Robotics Sportster FaxModems.
Probable Cause:
        1) Modem settings are wrong.
        2) Baud rate settings on ComSerter is not set properly.
Possible Solution:
        1) Check modem settings. Click here for Modem Settings.
        2) Verify that the baud rate settings on the ComSerter matches modem's baud rate.


Symptom: Intermittent communication with the ComSerter.
Probable Cause:
        1) If the ComSerter is a CSR194D, 292D, or 294D. It may need firmware reprogra4D. It may need firmware reprogramming.
        2) Voltage readings from the power supply is low.
Possible Solution:
        1) Reload firmware program into ComSerter with MEMCART.
        2) Measure the voltages from the power supply in the chassis. (Yellow cable +12 +/- .5 volts, Purple
cable -12 +/- .5 volts, Black cable is Ground, and Red cable is +5 volts; not less than 4.8 volts). If it is less than +4.8 volts, the power supply will need to be replaced.


Symptom: Unable to use COMPULINK with the EditExpress.
Probable Cause:
        1) Converting from CCMS to COMPULINK to use with EditExpress.
Possible Solution:
        1) Verify that the filenames are saved in an 8.3 format. EditExpress uses MS-DOS version of filename extensions.  For example: texscan1.drl is a filename with 8 characters with a 3 character extension.

>