BCD396XT/BCD996XT: Uniden Fire Tone-Out frequencies and Proscan Logging (CalFire Riverside County, CA)

Cokeswigga

Member
Premium Subscriber
Joined
Jul 23, 2006
Messages
21
Location
California
Over the last week or two, I have been logging the fire tone-outs for CalFire in Southwestern Riverside County California, and I have found quite a bit of variation in what my scanner was decoding as the fire tone-out frequency.

Looking at just one of the tones decoded
What has been published (by the now offline scanriverside) as using a tone of 1092.4 has been decoded by my scanner and the ProScan software tone-out logger as ranging anywhere from 1086.9hz to 1101.7hz with 48 distinct tone-out frequencies decoded within that range for what should be one exact tone. Notice that the published tone of 1092.4 was not the most decoded tone in the range.

ToneOut.jpg

Given the Tone-Out Standby Mode limit of 10 (my my BC-996T) I'm guessing that this would lead to the scanner's Fire Tone-Out mode would fail to alert on most of the dispatches based on the variation of the tones decoded. There could be literally hundreds of combinations for each set of Tone-Out pairs needed to alert for just one fire station. Based on the data, if the scanner was in Tone-Out standby mode, it would have only alerted on only 2 of the 57 dispatched calls due to the variations which is exacerbated because two tones are needed to be properly decoded for a tone-out alert to occur.

Has anyone else seen or experienced this as well?
Are other scanners able to better handle Fire Tone-Out Alerts?


I think being able to set the center frequency of the tone, and a variance allowance (or even range for each fire tone) would significantly reduce the missed alerts, and would be a great feature to have on the scanner. I know they are not going to update the BC-996XT, but are other scanners able to handle this better?

ToneOut2.jpg



Interesting enough the range of the tones for any given "Base" tone increases with the frequency of the intended tone


Tone GroupSum of HitsMin of ToneMax of ToneStdDev of ToneWidth of Range
339
37​
337.5341.31.03.80
470
27​
469.6471.20.51.60
471
6​
469.9470.60.40.70
554
44​
551.3555.00.93.70
585
125​
583.3586.60.73.30
617
140​
614.2621.21.27.00
652
17​
649.7655.02.05.30
688
197​
686.4689.70.73.30
695
2​
694.1694.1
#DIV/0!​
-
727
128​
724.3729.91.15.60
767
37​
766.5767.90.51.40
810
25​
808.2813.71.45.50
855
23​
854.5858.31.13.80
903
111​
899.8905.51.25.70
1000
82​
996.41,007.02.010.60
1093
228​
1,086.91,101.71.914.80
1123
164​
1,118.41,129.21.910.80
1153
248​
1,141.31,160.02.118.70
1185
283​
1,181.31,193.31.812.00
1218
199​
1,211.91,224.52.012.60
1253
164​
1,248.11,267.22.719.10
1286
710​
1,276.11,297.42.121.30
1323
238​
1,310.01,331.13.021.10
1357
337​
1,348.51,365.02.116.50
1396
352​
1,388.71,405.32.616.60
1433
368​
1,425.11,440.92.115.80
 

JoeBearcat

Active Member
Uniden Representative
Joined
Jun 30, 2020
Messages
1,983
Over the last week or two, I have been logging the fire tone-outs for CalFire in Southwestern Riverside County California, and I have found quite a bit of variation in what my scanner was decoding as the fire tone-out frequency.

Looking at just one of the tones decoded
What has been published (by the now offline scanriverside) as using a tone of 1092.4 has been decoded by my scanner and the ProScan software tone-out logger as ranging anywhere from 1086.9hz to 1101.7hz with 48 distinct tone-out frequencies decoded within that range for what should be one exact tone. Notice that the published tone of 1092.4 was not the most decoded tone in the range.

View attachment 164490

Given the Tone-Out Standby Mode limit of 10 (my my BC-996T) I'm guessing that this would lead to the scanner's Fire Tone-Out mode would fail to alert on most of the dispatches based on the variation of the tones decoded. There could be literally hundreds of combinations for each set of Tone-Out pairs needed to alert for just one fire station. Based on the data, if the scanner was in Tone-Out standby mode, it would have only alerted on only 2 of the 57 dispatched calls due to the variations which is exacerbated because two tones are needed to be properly decoded for a tone-out alert to occur.

Has anyone else seen or experienced this as well?
Are other scanners able to better handle Fire Tone-Out Alerts?


I think being able to set the center frequency of the tone, and a variance allowance (or even range for each fire tone) would significantly reduce the missed alerts, and would be a great feature to have on the scanner. I know they are not going to update the BC-996XT, but are other scanners able to handle this better?

View attachment 164502



Interesting enough the range of the tones for any given "Base" tone increases with the frequency of the intended tone


Tone GroupSum of HitsMin of ToneMax of ToneStdDev of ToneWidth of Range
339
37​
337.5341.31.03.80
470
27​
469.6471.20.51.60
471
6​
469.9470.60.40.70
554
44​
551.3555.00.93.70
585
125​
583.3586.60.73.30
617
140​
614.2621.21.27.00
652
17​
649.7655.02.05.30
688
197​
686.4689.70.73.30
695
2​
694.1694.1
#DIV/0!​
-
727
128​
724.3729.91.15.60
767
37​
766.5767.90.51.40
810
25​
808.2813.71.45.50
855
23​
854.5858.31.13.80
903
111​
899.8905.51.25.70
1000
82​
996.41,007.02.010.60
1093
228​
1,086.91,101.71.914.80
1123
164​
1,118.41,129.21.910.80
1153
248​
1,141.31,160.02.118.70
1185
283​
1,181.31,193.31.812.00
1218
199​
1,211.91,224.52.012.60
1253
164​
1,248.11,267.22.719.10
1286
710​
1,276.11,297.42.121.30
1323
238​
1,310.01,331.13.021.10
1357
337​
1,348.51,365.02.116.50
1396
352​
1,388.71,405.32.616.60
1433
368​
1,425.11,440.92.115.80

Try FTO Search on your 996 and see what that shows. (set both A and B to 0 Hz)
 
Top