[TrunkCom] GRE folks

[Todd Hartzel]

On 19 Jun 2003 at 9:23, Wayne M H wrote:

> On Thu, 19 Jun 2003 07:15:22 -0500, "Todd Hartzel" <toddh@brick.net>
> wrote:
> 
> >On 18 Jun 2003 at 22:17, Brian J Cathcart wrote:
> 
> "Cross-patching" or not, both patching and MSELs operate in the same
> manner over the CC. Just the TG incrementation changes. So your point
> is irrelevant. He was trying to make a point in relation to his
> example. Not every system operates like St Louis does.
> 
> -Wayne

They do?  If so, then Multi-Selecting should not be a problem for
my Trunktrackers (bc-235, bc-245, bc-780, pro-92 & pro-94).  Because two 
years ago when those talkgroups were patched together, my trunktrackers 
received the patched groups with no problems at all (Flawlessly).  I have to 
disagree with you.  There is something differant over the Control Channel
between cross-patching & Multi-Select.  Otherwise this problem would 
not exist.     The fact that a seemingly random (ID+7) ID pops up on our 
trunktrackers, which is other than the original dispatcher hitting the 'APB' 
button on the Centracom Gold Elite console.  

Receiving Cross-patching (ID+3) in St Louis was never a problem here, in the
years it was used.  The only problem I did have with it, is that a lot of local
scanner enthusiasts thought the patched IDs was a separate talkgroup,
all to itself.  I had to explain to quite a few it was a side effect of the
patching.  Here is the example of St Louis:

SODD  = 57552
BOI      = 57584
INFO A = 57712
INFO B = 57744

Patched IDs that were constantly transmitted::  SODD =  57555 / BOI = 57587
Also:  INFO A = 57715 / INFO B = 57747

You'd be surprised how many here thoughtt these patch IDs were unique,
and separate from the original ones. But again, my fleet of radios had no
problems with patching.  Its the Multi-select that is the problem. 



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