On Thursday 06 April 2006 20:24, Ken Walker wrote:
> > To notice the difference, the user must listen to the repeater's transmit
> > frequency at the same time as they transmit on the repeater's receive
> > frequency. This is normally not the case. That is unless you expect to be
> > able to press the PTT and just speak. At least I do an open-listen-speak
> > sequence when using a repeater. Maybe that's because most repeaters in
> > Sweden require a 1750Hz tone burst to open. Then the open-listen-speak
> > method feel normal.
> > Maybe it's easy to make this behavior configurable. I'll look into it.
> Thanks, If you could give a pointer as to where this would lie in the
> code, I can look at it as well.
If you are looking for a quick fix it's easy. Find the file
svxlink/svxlink/RepeaterLogic.cpp. Find the function "squelchOpen". Add a
call to "setUp(true);" when the squelch opens. Recompile.
> The problem in the states is that the FCC rules state there are to be
> no inidentified transmissions, not even to test access to a repeater. So
> what normally happens when you want to reach someone, you listen for quiet
> on the repeater, if it's quiet, then call the station, followed by your
> call which serves to identify the transmission.
> So with having to key the repeater first, your first transmission will
> go unheard (except for the FCC listening on the inbound freq (*: ) and you
> would have to key up and call again.
Well, I don't think the FCC will jail you if you transmit once to open the
repeater and then identify a couple of seconds later.
However, it could be a problem for automatic services opening the repeater as
I said in my previous mail so it should be fixed anyway.
73 de SM0SVX / Tobias
> Thanks for your time!
> 73, Ken - KC9GKA
> Unix IS user friendly...It's just choosy about who it calls friend!
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast and join the prime developer group breaking into this new coding
> Svxlink-devel mailing list