Trunking Check

[tsunami_australia]

Hey folks, a friend just received his new radio this week (well new to him) and I'm trying to fix up the programming to suite him. Conventional is a breeze as I already have an 03 5000 to dump most of the stuff off to his 03 5000. The trunking has me a little frazzled though since I've never played with it (always been meaning to).

The trunking setup is quite different to the usual non affil scanning suggestions I've seen in this case allowing trunked channels to be individually selected in zones etc (or at least it seems to me). My concern is what I'm seeing appears it will attempt to affiliate which we obviously do not want. The red light doesn't flash and ptt is meet with a low beep (could be an out of range thing too). But I want to be sure.

So I would appreciate it if one of the brilliant minds here could go over the disinfected codeplug (left a few things for example) and tell me if it will or won't affil and why.

View attachment trunk check.cpg

 

[tsunami_australia]

Have put a better edition without our personal frequencies etc (as it arrived to here) up just in-case the other doesn't show enough of the picture.

https://onedrive.live.com/redir?resid=7B8E0059E7B7BBF1!546039&authkey=!AO4ar97p2l4HTBg&ithint=file%2ccpg

 

[rescue161]

Man, that codeplug is a mess. There are 7/800 frequencies and UHF in the Astro 25 Channel ID? The zone assignments point directly to trunked talkgroups, so the radio will at least try to affiliate when those channel/zone assignments are selected.

Read up on hidden scan list method. Make sure you understand the workings of why the hidden scan list works. You also have transmit frequencies listed under the OBT Astro Control Channel segment. You only need the RX channels for RX only.

The codeplug needs a LOT of tweaking to make sure that it won't affiliate. Using it as is would not be a good idea at all and if the correct TX frequencies are in the CP, then it will more than likely become inhibited.

 

[rescue161]

Here is a VERY basic codeplug. Sys ID of 001. Two trunked talkgroups, ABC (TRUNK 1) & DEF (TRUNK 2). They are in Zone 2, which cannot be accessed because "Zone" was removed as a menu item. A scan list is created for each conventional channel in Zone 1 and they are set to scan automatically. When the radio is on the conventional channel "SCAN," the radio will scan both TGs. When on the conventional channel "TRUNK 1," the radio will scan TG "TRUNK 1." Same goes for TRUNK 2.

It becomes more difficult with the mobile series as the zone selection is usually a soft key and the channel selector does not have a stop like the portables, so it is possible that you can accidentally migrate to a trunked channel via soft keys if it is not programmed carefully. Omitting the Zone from the menu helps stop this from happening, but also limits the way you program your radio. You basically end up with one large zone, which is not ideal, but if you really want to listen to a TRS, then this is your best option.

As I said before, there is a lot more tweaking to do as this is just a BASIC codeplug. I only put in 2 control channels to show the example of leaving out the TX frequencies on OBT systems.

Good luck.

 

[tsunami_australia]

Thanks I'll look at that CPG in a moment and TYVM for confirming my suspicions. Yes I saw the 800 stuff in there and was like "WTF".

I'm aware of the NA scan method (might have to retouch on it again just to make sure) but it for what I remember worked on a scan that had a set talkback to 1 which is a conventional base (unused) frequency in it's own personality which when sat on forces the scan list that includes the trunked stuff and on tx attempt rocks back to scan member 1 which is the unused conventional member that you are sitting on meaning it cannot attempt tx on trunked. Am I correct?

If my above is correct it well explains why I was worried by what I saw. Next question, how would this radio NOT have been stung? Slack/lazy NOCops?

 

[tsunami_australia]

Further to my last, if the tx frequencies for the trunked network control channels are fudged would I be right then in assuming the radio cannot attempt affiliate?

 

[rescue161]

It will attempt to send a request to the controller(s) on the frequencies that are programmed. It will continually try to affiliate over and over and won't receive anything because it thinks that it has not affiliated due to it not receiving a grant from the controller.

The hidden TG method bypasses that handshake and allows TGs to be scanned even when the radio has not affiliated.

As far as not being inhibited goes, there are many reasons. The controller is not configured to only allow certain RIDs, an audit of valid RIDs was overlooked by the System Admin, etc.