Good to hear from you again Dave.
On 164.415 RAN 7 I have TG 0 show up. But that's about it. Here's what I do have logged for this frequency however though as far as RID's go.
Unit - 57 RID 7257
Unit - 65 RID 7265
Unit - 95 RID 7295
Unit - 146 RID 7346
Unit - 158 RID 7358
Unit - 199 RID 7399
Unit - 255 RID 7455
Your 165.195 is input to 164.415 -
TAFL Search Results
and 169.995 is input to 166.005 -
TAFL Search Results
168.120 looks to be the input to 164.070 if I'm not mistaken -
TAFL Search Results
Now this one I'm not so sure about as to the input or output
TAFL Search Results
Judging by this observation of yours Dave, it seems that 164.415 that has been eluding me for quite some time, may also be Tackaberry as well then?
I also noted your observation on the IDs as well that here too, there was a pattern present with the RID's.
Also, if these frequencies are all associated with each other with the Radio IDs etc...Technically I could build it as a Conventional Networked system as apposed 2 separate conventional systems? All that requires is just adding another frequency to the system. Or not I guess considering the TGs used? Unless something like TG 0 isn't the same on 164.415 as it is on 166.005 right? Cause as you say, they're separate repeaters right?
Similar N96 activity using RIDs 72xx, 73xx and 74xx with RAN 7 shows up on several frequencies:
164.415
165.195
166.005
168.120
166.005 is registered to Tackaberry, others under Bell Mobility.
These are conventional repeaters, not trunked. The reason for no activity between calls is there is no CC.
It is all one big group call with no TG. That the RIDs show up as TGs is some sort of anomaly.
The tags UNIT-107 etc. are radio "aliases" associated with each RID. Some NXDN operations use
them, others don't. The unit number in this case is RID + 7200.
Dave