Unknown Comms on Fire Tac 3 and Avcom

[Jeff302]

I am getting a lot of unknown comms on NCC Fire TAC 3 (3216) and AVCOM (1712) here in Newark. I'm using a BC 796D which I've programmed with ARC 20 Pro. I have the same frequency / TG setup on my BC250D in North Wilmington and I have no problems.

Is this a control channel hung up? Or is it something else? It is driving me nuts.

I don't want to listen to DART or DELDOT on TAC 3!!!

Jeff

 

[Mark]

Yes the Northern Delaware Lums Pond Tower i believe has been hanging on 866.5625 for quite a few months now.
It does it on my PRO-96 and 785D.
Got to keep your finger on the scan buttons from time to time unfortunately when you see that freq pop up and start getting busses and Deldot.

Mark

 

[hai_akeeba]

Claymont and Smyrna towers are ok. Everything in between are h-h-h-h-a-a-a-a-n-n-n-n-g-g-g-g-i-i-i-n-n-n-n-g-g-g-g-g-g. DivCom is pre-occupied with testing. ???????

 

[doctordave]

Yep, the hanging is a bit annoying. Had the same thing over the 4'th weekend while I was in Sussex Co, as well.

 

[Jeff302]

Can I lock out the culprit, 866.5625? Or is this a control channel?

Jeff

 

[h8tdigitalradio]

Hello,

The frequency can be attenuated. You can try it. Sometimes it works. 866.5625 is a Voice Frequency.

73

Dave AKA The Tripzter :shock:

 

[hai_akeeba]

Locking out that frequency will cause you to miss transmissions assigned to it by the system controller.