Somerset County Control Channel Online!

[mikea7531]

The control channel for Somerset County is up! It is currently on 501.9125. We do not have a base configuration for this system yet, if anyone can figure it out, please share! This is all the frequencies licensed to the county for the TRS:

471.1625
471.1875
472.3875
472.4125
500.3375
500.6125
500.8875
501.9125 - 11:43 - Control Channel
502.5125
502.5375
502.5625
502.6125
502.6875
502.8375
470.0625
470.2375
470.2875
476.0625
476.1375
476.1875
476.2375
476.2875

 

[rbartolu]

Somerset County Control Channel

That control channel was online for 2-3 days on 501.9125, switched as of yesterday back to 502.6125. Tried to monitor the frequencies you mentioned when county was sending out a dispatch but there doesn't seem to be any simulcasting online as of yet. As of around 13:30 today it seems as though the control channel was switching between 501.9125 and 502.6125 every 5-10 mins or so.

 

[ka2mek]

Anyone running trunker or T4W on it yet?
73
Robert-KA2MEK

 

[mikea7531]

Jim Robbins is running trunker on the system. So far he said there's been little traffic on the system. I haven't heard anything else from him as of yet.

Mike

 

[ka2mek]

Jim Robbins is running trunker on the system. So far he said there's been little traffic on the system. I haven't heard anything else from him as of yet.

Mike

OK Mike
yeah thats a good usefull tool to run on a new system if he know how to use it correctly.
73
Robert-KA2MEK

 

[elk2370bruce]

Rob, Great QTH. Did you run the dipoles off the lighthouse tower or is there a giant full wave coil inside set for 160M? Is the 13 element 2M Spiral Ray Yagi in the back yard or on top of the light assembly?

 

[ka2mek]

2rj
73 & QRV! :wink:
Robert-KA2MEK

 

[rickey456]

Jim

Are you getting anything on Trunker? I've been running Trunker on 501.9125 tonight but can't get the signal above 45%. It won't decode the sysid or frequences at this time. Only have:

Type II NetCap 90Hz

v0x032 [this has been active]
v0x143

Rickey Stein

 

[robbinsj2]

Trunker on NJ Somerset Cty TRS

Rickey,

I typically get high-quality decode on the county system but when last I checked, Monday night I believe, all I saw was v=0x032 and it looked like an input to the 501.9125 CC. I logged another one or two Fx hex codes, but I suspected them as errors or inputs to 502.6125 CC. There was no traffic I could correlate from my conventional scanner watching the repeaters.

I will say I tuned in later, maybe Tuesday night, and only heard the CC periodically on 502.6125; nothing on 501.9125.

I'll sneak home at lunch and switch Trunker back to Somerset County. If I see any remarkable activity I'll send you a copy of my files (and post here) so we both can analyze them -- as you know I'm still new to Trunker and I may be missing something. I'm not at all familiar with T4Win and Treport; if they hold any edge over Trunker and would be more helpful I can try to get them running instead.

Thanks,

Jim

(whew, I'm getting dizzy trying to sort conversations in two forums, one group, and e-mail... )

 

[rickey456]

Jim

I was up to about 72.5% this am. I haven't tried T4W but it might have the advantage of giving all of the frequencies automatically. I have another Compaq laptop and tapped radio that I am going to try to set up with T4W and run Somerset on that tonight. Will you be around tonight?

Yes, I know what you mean- jumping between forums :lol:

Rickey

 

[robbinsj2]

Re: Trunker on NJ Somerset Cty TRS

I don't think T4Win, or any other hardware or software for that matter, will be able to grab frequencies from a Mot/APCO CC without already knowing the base and offset (which it would for standard 800MHz systems).

You weren't getting the sysid because they weren't transmitting it. I wasn't getting it at 98.2% noontime until they took the CC offline and back at about 1:15.

Rickey, I e-mailed you more stuff that doesn't need to be hashed out here.

 

[robbinsj2]

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)

 

[robbinsj2]

Original B/O/S adjusted, 2 more added immediately above.

 

[PhilaPoliceRadio]

I am working on information on the system now. Will get back to you guys later in the week with my findings. I hope I can recieve it here on the ground-plane.