FAQ# 9:
When I import a traffic log or music log, I get the message "No carts found."?

This is usually caused by the log file not matching the format that
ControlReady expects. Go into DOS Edit to determine the cart code offset (the
column number where the first character of the cart code is) the cart code
length, the Air time offset (the column where the first character of the air
time is) and whether the log uses 12-hour or 24-hour format. If 12-hour
format, also determine the AM/PM offset (the column where either A or P is).

Configure the import for these settings: from the cart deck production screen,
press F10, choose Configuration Changes, then choose Log Import Configuration.

FAQ# 12:
I am changing the satellite programs I am carrying. What is the easiest way to
implement this change in the playlists??

You will probably want to keep the names of the playlists the same. Revise the
playlists on another computer, then, on the day before the change:

Save the running playlists using the date. For example, if you are normally
running WNSI-MON and LNR-MON (on Monday) and the change is to occur on
Tuesday, May 10, on Monday, you would save WNSI-MON as May9, and LNR-MON and
LNR-MAY9. This way, bringing in the new playlists will not overwrite the
information you still need on Monday. These playlists will still be set up to
load and start WNSI-TUE and LNR-TUE.

Now, copy the new playlists from the other computer to the on-air computer.
Then, at midnight, when the playlists are loaded, they will be using the new
schedule.

FAQ# 13:
How to I get a record of carts that played??

ControlReady can keep a record of every cart that plays from automation,
including the time it played, and the play list that played it.

On a stand-alone system, you just have to create a subdirectory of the
installation directory, and call that subdirectory CONFIRM. So, if CartReady
is installed in the C:\WIRE directory, create the C:\WIRE\CONFIRM directory.

On a LAN system, you have to create the CONFIRM subdirectory of the user name.
So, if CartReady is installed on the F:\WIRE directory, and the computer goes
into CartReady with the user name ONAIR, create the directory
F:\WIRE\USERS\ONAIR\CONFIRM.

In both cases, there will be a log for every day. The file will be named in
the format MM-DD-YY.LOG, so that May 3, 1997's log is 05-03-97.LOG. The log is
a text file, which can be viewed in any text editor, such as DOS's Edit, or
the Notepad in CartReady.

FAQ# 16:
Can I have more than one USN1616 on my computer??

At this time, ControlReady can use only one USN1616.

FAQ# 29:
How do I enable jocks to stop automation, to go live for a short period, at
times that are not known ahead of time??

Here is a simple way to setup "optional" break away and rejoin points
throughout a music on hard-drive schedule which they can take with just two
momentary push buttons.

Requirements: Must already have a USN1616 Relay controller connected to a COM
port or they will have to buy one. Must also have a silence sensor.

1) A custom command called OPT LIVE BREAK is created as follows in the custom
command assignment screen.

The actual command setup for this in the custom command assignment screen is

PULSE AND WAIT

where the PULSE channel is any open relay for only 10ms on the USN1616 not
being used called "TRIGGER OUTPUT", and the WAIT is an input channel on the
USN1616 from here on now called the "trigger" to go HI. For now the
Trigger output relay won't be connected to anything, since in most cases we
don't need to use it.


2) Put the OPT LIVE BREAK wherever you want to give jocks the option of
going live. In generally we recommend putting this before any SCHEDULED
BREAK line, and before the first SCHEDULED MUSIC SWEEP line after break,
since 99% of the time this is where you want it. You can also put this
before any other MUSIC SWEEP line. Thus it's possible to take optional
breaks anytime a sweep or break is ending.

3) At this point some explaining is in order, I've only given you the
pieces, and not explained how they work together, or their purpose.

So far it's clear that whenever the OPT LIVE BREAK command is encountered,
it will only continue if the Trigger input you selected is HI, or it will
just sit there waiting.

Here's what we haven't told you.

Another automation deck will be activated running a supervisory program
called a subroutine which is actually going to be a gatekeeper.

This program will take up two additional inputs on the USN1616 called the
BREAK AWAY and REJOIN inputs.

And it will use a relay output on the USN1616 called TRIGGER CONTROL.

The program, (you could call it CUTAWAY) will look like this:

LABEL --- SET TRIGGER CONTROL RELAY HI SO THAT AUTOMATION DOES NOT BREAK AWAY
LATCH CHANNEL XX HI
where XX is the Trigger Control relay you chose.
LABEL --- WAIT FOR JOCK TO HIT A PUSH BUTTON TO TAKE NEXT AVAILABLE OPT
BREAKAWAY
WAIT FOR CHANNEL YY HI
where YY is the Break away input channel you chose. (no time window)
LABEL --- SET TRIGGER CONTROL RELAY LO SO AUTOMATION TAKES NEXT OPT BREAK AWAY
LATCH CHANNEL XX LO
where XX is the Trigger Control relay you chose.
LABEL --- WAIT FOR JOCK TO HIT A 2nd PUSH BUTTON AGAIN TO GO BACK TO
AUTOMATION
WAIT FOR CHANNEL ZZ HI
where YY is the Rejoin input channel you chose. (no time window)
GOTO 1

4) The above program explained.

What is occuring here, is when the program is first started, it makes the
Trigger Control relay go HI. This will be wired into the TRIGGER input we
described in (1) above.

Thus when the program is started, the OPT LIVE BREAK custom command will
always be HI and thus not break away (go silent).

However, the WAIT FOR CHANNEL YY HI is the magic line that lets breakaways
occur.

If you wire any momentary push button your console to this input (Called the
Break Away input) this will cause the TRIGGER CONTROL relay to open.
Since the trigger control relay is wired into the TRIGGER input, anytime
someone pushes the button, the next time you hit a OPT LIVE BREAK command,
it will stop giving the jock time to go on the air with the MIC and say
things.

Thus the CUTAWAY program is doing the following:

Anytime they hit the "breakaway" push button (break away input will go HI),
it causes the the CUTAWAY program to open a relay called TRIGGER CONTROL.
TRIGGER CONTROL is wired into the TRIGGER INPUT. When the relay opens the
INPUT goes LO. Thus as soon as the automation program hits a point you put
the OPT LIVE BREAK command, the automation will stop cold.

Keep in mind the jocks can hit this button anytime they want, they don't
have to wait for the exact instance a song ends.

Once the automation system stops, they can resume automation anytime by
hitting the second push button called the REJOIN button.

If the REJOIN button is pushed, the REJOIN input goes HI, and the program
Latches (makes the TRIGGER CONTROL RELAY Close), which will make the
TRIGGER input go HI. Thus the OPT LIVE BREAK command will become true in
your main automation deck, and move to the next line, thus causing your
automation to start again.

5) The silence sensor.

A silence sensor is required because it is just too dangerous to give the
main automation program the chance to stop and get stock because (a) a jock
forgets to hit the button to resume. (b) a jock hits the button minutes
before the next optional breakaway point gets tired and goes home, goes to
sleep etc. (c) an electrical malfunction makes the wiring not work the
way it is supposed to.

A silence sensor is a box most radio stations are familiar with. If it
senses silence for a set number of seconds it closes a dry contact/relay.

This relay of course is tied to the TRIGGER INPUT on the USN1616.

Thus the TRIGGER INPUT is wired to two relays, one relay on the USN1616
called the TRIGGER CONTROL, and the silence sensor. These are in parallel.

Thus, if someone screws up, you can control how many seconds of silence
cause the automation system to resume. We recommend no less than 5 seconds,
and no more than 10.

A good silence sensor is one that opens the relay as soon as it hears
something, and closes the relay when the duration of silence is reached.
No resetting by the computer should be necessary.

If you don't use a silence sensor, it is guaranteed sooner or later you'll
go off the air.

We sell silence sensor models that cost between $150 and $250.

Aside from the sensor relay being wired, you also have to wire the sensor to
a place in your audio chain where it can hear what is going on.

We generally recommend you D/A the program output from your console or at a
point before your air signal goes into your exciter, STL, or transmitter.
This way the sensor will trip if it hears silence.

Some stations may use a second silence sensor for a similar reason, for
example setting a secondary sensor to 1 minute of silence can cause an
emergency source to kick in like a reel to reel, DAT player etc in case the
computer quits, another handy tip for radio station owners that enjoy
fishing in the country better than working in the station.

6) Variations on this idea.

You can hook up a light to let the jocks know whether they've armed the
system to breakaway at the next time.

Add a second LATCH command which closes a relay on your USN1616 called the
LIGHT RELAY.

For example below these two lines in the program above...

LABEL --- SET TRIGGER CONTROL RELAY LO SO AUTOMATION TAKES NEXT OPT BREAK AWAY
LATCH CHANNEL XX LO
where XX is the Trigger Control relay you chose.

Insert these lines

LABEL --- MAKE BREAK AWAY LIGHT TURN ON
LATCH CHANNEL QQ LO
where QQ is the light relay channel you chose.

And below these two lines in the program above.

LABEL --- SET TRIGGER CONTROL RELAY HI SO THAT AUTOMATION DOES NOT BREAK AWAY
LATCH CHANNEL XX HI

Insert these liens

LABEL --- MAKE BREAKAWAY LIGHT TURN OFF
LATCH CHANNEL QQ HI
where QQ is the same relay you used above to control the light.

Your engineer can create the light circuit that is controlled via this
relay. Your engineer can use this relay to control another relay/light
circuit, or use a low voltage DC type light with this relay. NEVER RUN AC
LINE POWER THROUGH any relay on the USN1616, you'll fry the USN1616, kill
yourself, and likely burn down the facility. Again any wiring that involves
light bulbs, current etc should be done by a qualified radio engineer.

They may decide to just use a LED, a resistor and a AAA battery. But this
is all up to them.

A light circuit is nice since a jock will always know if the system is armed
to go into live mode at the next preset opportunity.

7) Manual break always.

If you allow your jocks supervisor access to your running programs, keep in
mind they can hit F6 EDIT, and insert the custom command for an OPT LIVE
BREAK anywhere they please.

Especially since they are editing a running program, any changes they make
get blown out the next time that day schedule runs the following week.

8) TRIGGER OUTPUT RELAY.


As you may recall we told you this relay in the very beginning was not wired
to anything and thus we set the delay to 10ms 1/100 of a second so it doesn't
introduce silence when not taking optional breaks.

If you have an old or inexpensive silence sense that must be reset before it
will trigger silence, then you need to increase the duration of the pulse to
at least 100ms (possibly longer) and wire this relay to the reset input of
your silence sense.

Many silence sensors may need a reset anytime they trigger silence, or their
output relay stays high which would prevent any break Awa's.

By using the PULSE AND WAIT (i.e the OPT LIVE BREAK custom command), this
pulse can reset the silence sensor just in case it has tripped) so when we
check to see if the trigger input is HI to continue playing, the sensor will
force the input HI in a specified number of seconds if someone hit the break
away button earlier and forgot to take their cue.

FAQ# 48:
Is there an easy way to convert scheduled breaks to scheduled music sweeps??

This should only be necessary if you use the scheduled break command, but
actually have music imported under those commands.

[The scheduled music sweep is a newer command. Prior to the introduction of
the command, it was necessary to change the log import configuration based on
which was being imported: a music log or a traffic log.]

You will want to maintain the break times and lengths. Instead of manually
typing them into each scheduled music sweep command, you can have ControlReady
"remember" what the times and lengths are, using the same settings as were in
the scheduled break command.

Highlight the scheduled break command, and press F6 (Edit). Then press F4.
This changes nothing. Now, press Enter, then press 1. This brings up a
scheduled music sweep command, with the time and length from the scheduled
break command. Press F4 to save the scheduled music sweep command.

Do this for each scheduled break you wish to convert to a scheduled music
sweep.

Once you start doing this, you will find that you can do it more quickly:
highlight scheduled break, F6, F4, Enter, 1, F4.

NOTE: This is not quick, but it is easier than typing in all the information
for each scheduled music sweep, and it cuts down on errors.

FAQ# 64:
Using Natural Music software?

The following is only basic information. See the Natural Music software manual
for further details.

Throughout the software, you can press Esc to return one menu higher. Your
changes are automatically saved.

After first installing the software, go to Setup from the main menu. To have
the Natural Music software create a log in the format used by ControlReady,
arrow to the Automation ? field and type 16. This field will now display
16-CartReady(tm). When the text file is created by Natural Music, it will be
in the format: Air time Offset 1; AM/PM offset 0; cart code offset 10; cart
code length 8. (These are the settings to configure in CartReady's log
import.) This will also have a new entry in the song library default to media
type HD.

In this same screen, you can set a password, which will keep out anyone who is
not authorized. If you do not set up a password, anyone with access to the
computer will have access to the Natural Music software, which means they can
change rules, clocks, music information, etc.

You will need to create at least one music category. From the main menu, press
C (Controls) then M (Music Categories). To add a category, press N. To change
an existing category, highlight the code in the left-most column, and press E,
or the Enter key. These are the categories you will use when entering songs
into the library.

You will need to create at least one clock. From the main menu, press C
(Controls). Then press C (Clocks). Then press S (Setup). Type the name you
want to use for this clock. Press Enter to create/edit the clock settings. You
can scroll through, creating/editing up to 676 clocks. A clock is a schedule
for an hour. So, if some hours have 3 songs, a break, 4 songs, a break, then 5
songs, that would be one clock. Hours with 6 songs, a break, 3 songs, a break,
then 3 songs, that would be another clock. Etc.

In each clock, you will define which category of song should play. You can
enter information in the Log Text column of any line that does not have a Pri
or Sec category entered. This information will be placed in the log text file,
but will not be used to determine what audio plays. (With the exception of &;
see below.)

Usually, you will only set up Pri (primary categories, although you might set
up sec (secondary categories). A secondary category will be used only of no
songs from the primary category can be used at that time, based on the rules.
The times listed are not exact; they are only estimates. Use them as a
guideline of where you are in the hour. These will be the times listed in the
log text file. So, if the clock has songs at :03 and :06, and the software
schedules a 5 minute song at :03, the log will list the songs playing at :03
and :06. (Even though, if the first song plays at :03, the second song will
play at :08.) Don't worry, the ControlReady playlists can work properly with
this. You should just be aware of it.

You can put notes in the Log Text column. If you start the Log Text column
with &[code], then the log text file created will put that code in at that
point. This is useful for jingles, liners, ids, etc. You can enter the name of
a rotation as the code. You can put more text after the &[code]. For example,
entering "&legal Play a legal ID" (without the quotation marks) would place
LEGAL as the cart code; where the log normally puts the name of the song, it
would put PLAY A LEGAL ID. If, under Pri, you put a category, followed by an
asterisk (*), then that song is considered optional. If the rest of the hour
meets or exceed the maximum time, the song will be dropped. To define the
maximum time, press F10. NOTE: The maximum time you defined can still be
exceeded if the non-optional songs add up to more time. That is, no
non-optional song will ever be dropped.

To assign which clock plays in which hour, from the main menu, press C, then
C, then A (Assign Hours). Go to each hour of each day, and type the two letter
code for the clock that is to play. For quick entering, you can highlight any
hour that has the clock you use the most, and press F10. This will assign ALL
hours to use that clock. You can then go to hours that do not use this clock,
and change them.

FAQ# 68:
My confirmation log is not being created?

The ControlReady system logs to a directory called CONFIRM. This directory is
under WIRE for a stand-alone system; for example, c:\wire\confirm. It is under
the user name for a LAN system. For example, the directory would be
f:\wire\users\onair\confirm for the user ONAIR. If you haven't created the
directory and are running in DOS, you must exit the system, create the
directory, and restart. If you are running in Windows95/98, you can leave
CartReady running, and open My Computer or Windows Explorer to create the
directory.

Then use the built-in Notepad to pull up, read, print or save logs. The files
are name in the format MM-DD-YY.LOG; for example, 06-12-98.LOG is the log for
June 12, 1998.

If you have done this, but still see no log created, consider the following:

Sometimes, it can appear as if the confirmation log is not functioning. The
confirmation log can buffer up to 20 plays before they are written to disk.
During back to back plays, the confirmation log will not
be flushed. Once there is at least 3 seconds of no playing or recording, the
confirmation log is flushed. The confirmation log should be flushed when the
program exits normally.

Thus if you immediately go back in, and still don't see a log file created,
wait at least for 20 things to play, or for at least 3 seconds of idle time
between scheduled plays.

Remember that the confirmation log only logs information for carts played from
a play list, in automation. It does not log information for carts played from
Live Assist, the quick player, or any other section of the software.

FAQ# 92:
How do I change the channels on a Virtex receiver??

GO DIRECTLY FROM A COM PORT INTO THE VIRTEX RECEIVER
WITHOUT AN SCC8 AT ALL.

THE STRING IS SENT AT 9600, N, 8, 1 AND IS COMPOSED AS SUCH:

SP C,S,X

WHERE SP MEANS "SET PORT", C MEANS "PORT C", S MEANS "SERVICE", AND X IS A
NUMBER FROM 1 TO WHATEVER, WHICH IS THE NUMBER OF THE DESIRED PROGRAM FEED AS
LISTED IN THE RECEIVER IN ORDER

FOR EXAMPLE, 1=NONE, 2=00/01 PAIR, 3=090/091 DATS PAIR, ETC). YOU CAN ONLY
CALL UP THE PAIRS THAT ARE ALREADY IN THE RECEIVER, AND THEY MUST BE
AUTHORIZED FOR YOUR USE TO FUNCTION.

FAQ# 96:
When I type Alt-13 in a comtalk command, it comes up with a heart shape
instead of a music note.?

We are not sure why this occurs. We have seen it in one instance, a
Hewlett-Packard computer running Windows98, so we are not sure if it is a
widespread issue. We found that the problem does not exist when running on a
computer a booted into DOS mode, but does when running in a DOS box.


So the solution is to set up all of your custom commands when booting into DOS
mode. Then run CartReady from a DOS box.

NOTE: CartReady cannot run properly when booting into DOS mode on a Windows98
computer. So only boot into DOS mode to set up the custom commands.

FAQ# 212:
How to commands items into a running playlist.?
--------------------------------------------------------------------------------------------------------------------------------
You can edit a playlist EVEN when it's running. Normally when
it's running, the highlight bar is locked preventing any editing
from occuring. If it's running, you can still edit, by hitting
EDIT (F6), it asks you if you are sure, say Y, then you can
scroll around editing as nesessary with the INSERT and/or DELETE
keys.
Note: in this mode, the highlight bar stays put, the curser is a
group of arrows which takes the place of the line number on the
line you're currently working on.
To return the playlist to normal operation, hit the F3 start key,
and you will be returned to the normal play mode.
====================================================

FAQ# 217:
How do I send serial strings of data out COM ports to talk to serial devices?
-----------------------------------------------------------------
The command in your ControlReady automation deck to send commands out the serial port is called COMTALK. When you hit enter on the command, it lets you specify a com port, (com2 is 2F8) and there is a slot to type in the string. It lets you specify the baud rate, bits, etc. And there's an intercharacter delay which can be used if required, the default is 0 and is fine for just about everything.
If you have to include extended characters (paragraph markers ect.) you can hold the alt key while typing the hex equilivent on the numeric keypad. There is also an equivant command called HexTalk that allows you to enter the command string in hex format (ex 01 05 12).
=================================================================

FAQ# 225:
How do I set up an auto-recording, using a stop channel, if they tone at the end of the recording is the same as the one at the beginning?? 
-----------------------------------------------------------------
The reason this is an issue is becuse when the auto-recording starts, the tone is usually still present, causing the auto-recording to stop (because it sees the stop channel). Setting up SHUNT and LOGIC GATE circuits so one playlist can aid another: 

Example: Preventing a successive AUTO-RECORD from prematurely detecting a stop channel during back to back segment auto-records when the stop channel relay stays closed too long.

Autorecord supports a stop channel from the second it starts recording.

In cases where the next segment autorecord has to start immediately, the second it does, if the same relay is still energized, it considers that a valid stop command. This can create problems.

Here is a solution that I think will work with minimum changing/wiring.

The "Stop channel" input is currently wired directly to the satellite programming closure.

Instead, run one wire of this input pair through the NC and COM contacts of an available relay on the 1616, and then into the opto input point it was originally wired too. We will call this relay the SHUNT RELAY.

In the off state, the relay passes the input closures through as if nothing happened. If we energize this relay for any period, the input on the 1616 will no longer see any closure that is still present.

Now, we need to setup a "logic gate"

Take an available relay and an available input on the 1616. Wire the NO and COM points on the relay to the input. 
We now have the wiring we need.

Programming changes:

Between each back to back autorecording command, insert a custom command called SHUNT (which pulses the logic gate relay for 500ms (assuming you can live with a 1/2 second break between segments). You can try going down to as little as 250ms, but the more the better.

Now use an empty unused automation deck to do the following. 

1 WAIT FOR CHANNEL "LOGIC GATE INPUT" TO GO HI
2 PULSE SHUNT RELAY FOR DESIRED TIME (I.e in your case 10000ms
3 GOTO 1


Now we have what we want.

Whenever you end an autorecord command, the SHUNT custom command will PULSE the logic gate relay on the 1616. Because the logic gate relay is directly looped into an INPUT, which this extra playlist is monitoring, this initial shunt pulse, makes this monitoring playlist, energizing the SHUNT
relay for the desired time, blocking the successive autorecord command from prematurely ending because the satellite closure is still closed.