NJ Somerset TRS update
Hypotheses after several hours/days/weeks of investigation and observation:
Licenses indicate the TRS is or will be the following: 471.1625, 471.1875, 472.3875, 472.4125, 500.3375*, 500.6125*, 500.8875*, 501.9125*, 502.5125*, 502.5375*, 502.5625*, 502.6125*, 502.6875*, 502.8375*. (*=base/offset believed to be worked out for these)
The control channel has been observed on four frequencies: 501.9125, 502.6125, 502.6875, and 502.8375.
We have tentatively calculated three configurations that together should work for all the 50#.#### frequencies.
B=500.3375 MHz, O=380, S=25.0 kHz, ChLow=380, ChHigh=429.
B=501.9125 MHz, O=430, S=25.0 kHz, ChLow=430, ChHigh=449.
B=502.5125 MHz, O=450, S=25.0 kHz, ChLow=450, ChHigh=469.
B=470.0000 MHz, O=470, S=25.0 kHz, ChLow=470, ChHigh=759. (This last config is a placeholder only, until the 471 & 472 channels are brought up and their real B/O/S is available. There may end up being 2 more configs for them.)
I want to again emphasize that this is tentative, and is based only on minimal "behind-the-scenes" activity (like the 35360 TGID mentioned above, which has turned out to not be a real talkgroup) on the trunked system. No actual talkgroup usage has been observed so far, at least not by me. The above configurations will probably work but we won't know for sure until all channels are in routine use by voice activity on talkgroups.
The previously-announced B/O/S will work for the 502.#### frequencies, which may (or may not) be Phase 1 of the TRS implementation, but they will interfere with proper tracking of the other frequencies once they are placed into use.
Thanks to Rickey Stein for assistance on most aspects of what I wrote above.
(edit 8/13@18:50; * added to 502.5375)
(edit 8/22@20:05; rewrote most everything)
(edit 8/23@1505; minor data & grammar)