rbritton1201
Captain1201
- Joined
- Jul 27, 2020
- Messages
- 407
Within the Radio Reference data base, the tone squelch number that is programmed into the data base for Franklin County Sheriff's Department, Channel 2, 154.6725 Mhz., is actually blocking FCSD traffic, if programming your scanner from the RR data base (Uniden Sentinel Programming), because the FCSD isn't apparently using tone squelch on their Channel 2, as well as some other frequencies in the data base.
As for the other "conventional" frequencies in the RR data base for FCSD, I'm not sure whether any of the other frequencies listed in RR, which include the remote links listed for outlying areas, actually have tone squelch programmed into those frequencies by FCSD, and/or whether programming those tone squelch numbers from the RR data base into your scanner will serve to also block the other "conventional" frequencies as well.
My suggestion would be to remove the tone squelch entries for FCSD when programming your scanner via the RR data base, so the tone squelch entries in the data base don't inadvertently block reception of radio traffic on some FCSD channels. If it's determined that interference exists on some frequencies, and FCSD has tone squelch installed on certain other "conventional" frequencies, then the tone squelch programming can always be added back into scanner programming for channels where they might be needed due to skip interference, or whatever.
Furthermore, for several weeks, FCSD has been pretty consistently dispatching on Channel 1, 151.340 Mhz., no tone squelch, but today they're on their Channel 2, 154.6725 Mhz., no tone squelch. They continue to switch between these two channels when dispatching calls , apparently when radio techs are working on their system. I'm not sure which of these two channels will eventually be the main dispatch frequency for FCSD.
I suspect that any of the commercially available services, like Broadcastify, have these same RR tone squelch codes entered into their programming as well, which is probably also blocking traffic from FCSD with respect to their feeds.
As for the other "conventional" frequencies in the RR data base for FCSD, I'm not sure whether any of the other frequencies listed in RR, which include the remote links listed for outlying areas, actually have tone squelch programmed into those frequencies by FCSD, and/or whether programming those tone squelch numbers from the RR data base into your scanner will serve to also block the other "conventional" frequencies as well.
My suggestion would be to remove the tone squelch entries for FCSD when programming your scanner via the RR data base, so the tone squelch entries in the data base don't inadvertently block reception of radio traffic on some FCSD channels. If it's determined that interference exists on some frequencies, and FCSD has tone squelch installed on certain other "conventional" frequencies, then the tone squelch programming can always be added back into scanner programming for channels where they might be needed due to skip interference, or whatever.
Furthermore, for several weeks, FCSD has been pretty consistently dispatching on Channel 1, 151.340 Mhz., no tone squelch, but today they're on their Channel 2, 154.6725 Mhz., no tone squelch. They continue to switch between these two channels when dispatching calls , apparently when radio techs are working on their system. I'm not sure which of these two channels will eventually be the main dispatch frequency for FCSD.
I suspect that any of the commercially available services, like Broadcastify, have these same RR tone squelch codes entered into their programming as well, which is probably also blocking traffic from FCSD with respect to their feeds.
Last edited: