[TrunkCom] GRE folks

Todd Hartzel [email protected]
Wed, 18 Jun 2003 16:32:04 -0500


Greetings All,
      To the folks at GRE working on the PRO-96.  To advise
you.   Here in St Louis, Mo the 'STATUS BIT' features don't
exactly work in the normal manner here.   Example:

I 'HOLD' monitor District 1 & 2 (Only).(STATUS BIT mode 'ON')
Say the 'District 1 & 2' Dispatcher goes 'All Points'.  1 & 2
talkgroup is  57360.  So, when the 1 & 2 Dispatcher goes
out with an APB, you'd expect that 57367 would come out
over the data channel, right?  Well, NOT here in St Louis.

It could be any of the Dispatch talkgroups+7 (the status
bit).  One thing I can tell you.  Even though our trunktrackers
do not receive it correctly.  The actual system radios:

- stx-800s (most) & XTS-3000s (few)

They receive them correctly (everytime). The officer's radios
receive all APBs correctly.  Its only our trunktrackers that
do not.  So the 'STATUS BIT' mode on the Uniden models
is completely useless for us in St Louis, Mo
 
Also, using the same example above, monitoring 1 & 2.  Dist
1 & 2  is quiet, not much going on (talkgroup not active).  Then
the District 4 & 5 dispatcher goes out with an APB.  With our
Trunktrackers, we never hear the APB from 4 & 5.  The APB
goes out with the talkgroup ID of 57719 (which is the INFO A
talkgroup+7)  But, at the same time.  All officers with XTS-3000 
& STX-800 radios receive the broadcast just fine.  (Not a 
selective APB ; we very rarely, if ever do selective APBs)

This is a very prominent problem.  Occuring 3 out of every 4 
times, day or night, round the clock 24/7.  

Conclusion, the officers radios receive the APBs just fine.  Its
only our Trunktrackers that do not.  Before the PRO-96 ships
later this year, could someone from GRE investigate this matter.
I hope the problem is not unique.  I do not consider the St Louis
City Police Type II Motorola TRS to be that special, or differant
from all other systems.  Obviously, the problem lies in our 
trunktrackers, not the police radios.  Our scanners are ignoring 
something in the Data Channel's data stream. 

73 from todd hartzel / n0vkg
http://www.n0vkg.web1000.com