Talkgroups are noted as FDMA (mode "D") so the 796D should be able to track them, although perhaps they may have incorporated TDMA (mode "T") and no one updated the RRDB?
It handles a 7.5khz step size so in theory it shouldn't have any issues tuning to these frequencies...
My apologies. I wasn't looking well enough at the options when I posted earlier to see that it will indeed tune in 7.5 kHz steps. Sorry about that.
On my 796, I see it defaults to Auto for the step size and for VHF, mine appears to be using a 5 kHz step when you enter a VHF frequency that needs a 7.5 kHz step. One must change the step size to the correct size when entering a frequency that needs a 7.5 kHz step otherwise it will use Auto which is incorrect for this case.
I no longer have the VHF P25 site near me that uses anything but standard 5 kHz frequencies so I cannot test what mine does when the CC tells the 796 to tune a splinter freq.
This is now sounding like it may be that the bandplan info (trunking table) is missing or incorrect in the OPs 796?
The 796 needs manually entered bandplan info for VHF and UHF (450 MHz) P25 sites as it can't read that info from the control channel like newer models do.
I had to add entries for the VHF sites I can receive here even though they are all using only 5 kHz step frequencies. My 796 would not track VHF sites if I didn't enter valid bandplan info.
I ran into an issue with one VHF site here because the 796 can only hold three bandplan entries for a P25 trunked site. One of the sites needed four table entries to track all frequencies correctly for that site. I recall leaving the info for the least used frequency out of the bandplan table as it appeared to only be needed if the site needed to use the ID or Alternate CC frequencies for a voice channel when the site was at capacity. I don't recall which it was in my case.
Both of those frequencies were rarely used for voice unless the site was using all normal voice channels when a new voice channel request came in. The site would then grant the request by using the ID or Alternate CC frequency. I was never able to see what happened if it used the active CC for a voice channel but I know that site did that before.
Using the three most active trunking table values out of the four needed actually worked well.
I did know that I'd miss voice calls that used the frequency used by the trunk table that was missing but it was better than hearing nothing!
I didn't look at the OPs system to see if anyone added the trunking table needed by the early trunking capable P25 scanners.
