Lorgar wrote:Wapiti wrote:Is there a product available that can be used to drive UHF abusers who harass others (mainly farmers) so much on the channels they use for organisation and safety in the paddocks between each other - that can either torch these f+++wits radios or screech the living hell out of them so they just find another channel that farms aren't using?
There's bloody 80 of them after all, and half-channels as well too now for years.
Hey Wapiti,
Check out if your radios support CTCSS. I think it's pretty standard, I have a regularly off the shelf Uniden fixed unit in the truck that's 10 years old, and some newer basic GME handhelds, and they all have it.
To be honest, I set mine up years ago and have forgotten exactly how. I'm probably using some of the wrong terminology here, but you can Google how to do it.
CTCCS anyway, is basically sub-channels of the usual 80 available.
When you scroll / scan through the normal channels, you get 1,2,3.... 80, as you know.
Instead of just using channel 80, with CTCSS, you go to the channel, and into radio settings for CTCSS and can effectively pick 80.1, 80.2, 80.3 and so on. You can do this for any of the regular channels.
If you set your channel 80 to 80.1 CTCSS, you won't hear users on regular 80, and they won't hear you. So you need to set all the radios you want on the network to the same CTCSS.
All the other channels work exactly the same as usual, but once you get to "80" you'll be on your sort of private 80.1 CTCSS channel.
Technically these channels are still public, but honestly 99.9% of UHF users don't even know the feature exists, in my experience. Let alone use then.
I set all mine to have CTCSS for channel 15, and that's what I use in conveys on and off road when travelling with mates and not wanting the interruptions. Have done so over thousands of km, and multiple states.
In 10+ years I have never once heard an uninvited users on a CTCSS channel.
I dont think this is correct about how CTCSS works.
"Continuous Tone Coded Squelch System" works by the sender having a (mostly inaudible) sub-tone included in each transmission.
The receiver thats been set up for the same CTCSS code(and most makes/models of UHF radio will do it), will unlock the 'Squelch' on the receiver when it hears the correct sub-tone code being received, so you get to hear that transmission.
If a transmission is received that doesnt have the correct CTCSS code(ie from all the Bogans..), then the squelch wont un-lock, so the radio stays silent.
It effectively gives you a clear channel between parties, regardless of what other radio traffic is on the channels.
But note that all your transmissions between CTCSS-enabled radios, are still heard by all parties on that channel.
So, all it might do, is allow you to ignore any incoming transmissions that arent coded with your CTCSS code, so cut down on the chatter you hear.
It will also mean your receiver wont un-lock for anyone trying to call you, that doesnt have the same CTCSS code set up on their radio.
This means that IF you enable CTCSS, then you wont be hearing/receiving calls from people that dont know your CTCSS code.
I dont use the CTCSS system myself(not enough traffic to need it), so not sure if the CTCSS coding is set per channel, or for the radio as a whole.
I would've thought per channel would make more sense, but radio manufacturers do some weird stuff at times.
I dont think CTCSS is a perfect solution for the problem the OP described, but I cant think of an alternative that would work any better, either.
Given the village idiots are using a public-use channel(albeit for nothing useful), there isnt much that can be done.
Options:-
1). Convince the authorities to police the use of the frequency more proactively(Good luck with that).
2). Buy a licence for a separate 'private' channel, but I suspect this will incur licensing fees for each user, and has the problem of all radios using that channel needing to be able to be programmed for it. Many modern radios are capable of the programming to take extra channels (Icom IC-400 series can take another 40-odd channels), and I know a couple of the other brand names do same, but they would need programming by someone who knows what they are doing, and this isnt a solution beyond a smallish group.
Neither option is all that good.
50 years ago, any sort of 2-way radio (mostly VHF at the time) required license fees being paid for the use of the freqs.
Many of us in this area used the fire-band radios for day-to-day comms, which was pushing the boundaries of the law at the time.
At it's peak, it was even more crowded than you see on UHF these days, as the VHF sets transmitted a lot further, and there was only a handful of freqs in use.
Along came UHF(first got ours in 1981) with public-use licensing, and the option for 40 channels, and a much shorter transmission distance, which everyone took to like ducks to water.
Repeaters were installed for areas where distance needed extending, and we eventually moved to 80 channel, which allowed even more 'room'.
BUT, at the end of the day, the birth of UHF radios meant people stopped having to pay for the use of the radio freqs.
[Which was about when we lost being able to restrict whom can use our channel.]
The great, unwashed public can be a royal pain in the arse some times.
[I'd probably re-phrase the 'some' to 'most', myself..]