Fairfax Public Safety Trunking

[ACU1000]

Every County Police Dispatch TGID showing up in RR is different than what I have hearing on my 396T.

Each ID showing up when I listen in ID SEARCH is about +3 higher than what is shown in the database.

For example TGID in the db 17232 (CH 3 MCLEAN), the audio comes through on my radio under TGID 17235. 16016 is 16019.

It appears the dispatch channels are coming up this way becasuse of the status bit indicating they are patched to another system.
http://www.radioreference.com/forums/showthread.php?t=59844

My question is, how are you supposed to download a system from RR and know if the TGID's are going to be patched or utilizing other features?
http://wiki.radioreference.com/index.php/Motorola_Type_II

What is the best way to know about this for all the systems out there and deal with it?

More specifically, is FCPD patching all dispatch channels all the time and should we change them in my system file?

M LEMISH

 

[KF4ZTO]

FCPD does patch the dispatch channels. However, you should program all the dispatch TGs because which TG will show up on your scanner will change from day to day...if that was what you were asking I'm not sure but I thought I would throw that out there.

to quote from the thread you linked to..

"22467 is the status bit. ID+3 is for patched talkgroups. The base talkgroup is 22464."

I would imagine that is why the TGID's are showing up differently than what is in the database. Again, I think thats what you were asking.

As far as I know, it should not make a difference if a system is patched into another system or not as far as monitoring a single system (the Fairfax County Public Safety system for example).

I think we need more of an expert on this to make sure, but I think thats whats up

 

[ACU1000]

freqhopping helped me figure it out. You have to set the system to ignore the status bit.

If you have it pay attention to the status bit, you would need to know the exact TGID that will be used if patching, etc.

When it ignores the status bit, the scanner is smart enough to know that xxxxx could be anything from xxxxx to xxxxx + 15 (depending on the function and status bit.)

Hope this makes sense to all - it took me a while to understand it.

ML

 

[eweiner]

I'll concur with KF4ZTO on that one. We do the same thing here in Henrico for some of the Fire talkgroups.