On May 31, 2007, at 8:21 PM, W0uaw@...
> Am up and running! thanks to all who helped. I do have a
> question. I ran the pulsecheck script and it told me to set the
> second number to 5370ms. The docs I was reading says if the second
> number is over 500ms there may be something wrong between the radio
> and the node. I am using a Motorola M120 with the correct cable
> (making the mods on the DB-9 as documented). should I be
> concered?? Will this cause issues??
> 73 & Thanks
> de Emit, W0UAW
Yes. Pulsecheck is keying the radio and then measuring the amount of
time COS is active after it unkeys.
I'm going to guess because you haven't described your setup. Are you
linking to a repeater on the user input/output frequency and not on a
link channel? If so, and you're on the user input/output you must
find a way to get rid of the repeater's transmitter tail at the link
There are three ways to do it - program the repeater with a mode that
can be used that has no transmitter tail (least desirable because
most users won't understand why they can't "kerchunk" the repeater)
or set up the repeater to only transmit CTCSS tone when a valid user
input signal is being received by the repeater -- and then wire the
IRLP up and/or program the link radio to only send a signal to the
IRLP board when someone is actually keying/talking through the
repeater. The third way is to put a multi-port controller at the
repeater site and use a dedicated link frequency... however you'll
still need to ID that radio and find a way to turn the CTCSS tone off
during transmit of CW ID's when no user signal is present on the main
You should configuring your system to send no repeater transmitter
tail that the IRLP node on the far end can "hear" and no CW ID's
without users talking.
Remember IRLP is a link, and since it's not a "user" on the repeater,
the ID's and tail are undesirable to pass through the link to the
The remote system you're linking to doesn't want to listen to 5
seconds of silence after each of your transmissions where they can't
reply (because you still have their radio keyed - your IRLP node is
still "hearing" something), and your ID should only ID your system.
It shouldn't be sent to the other side unless it just happens to go
off during a user's transmission.
If you can fix only the former (the COS time) but not the latter
(ID's are still sent regularly to your node, even after everyone's
done talking), you'd be able to allow node-to-node connections, but
you won't be allowed to access Reflectors. Most node owners won't
complain (too much) if your ID leaks out to their side of the link,
but Reflectors can't allow tails or ID's since you might be sending
those out multiple people's repeater systems with a Reflector and
tying up the channel when someone tries to respond to someone else.
A CW ID from your station would interrupt two other stations talking
at whatever interval you have your ID's set to.
Nate Duehr - WY0X