K4AAQ
Member
This may just be a sanity-check post.
I'd been doing some revisions to the Favorites Lists for my Uniden SDS 100 and BCD536 scanners, when 'suddenly' things got too quiet. OK, not 'volume' quiet... 'missing talk groups' quiet.
After a while, I noticed that it was just the agencies on the Wake Simulcast system - I was still hearing Cary Fire on the Cary Simulcast system, NCSHP on VIPER, Durham on their system, etc. But most of the stuff on Wake was never showing activity. Most, but not all: I was still hearing the Raleigh PD's Northwest Dispatch talk group. Just that one... none of the others.
To shorten the story... checking things with my old Radio Shack PRO106, I found other RPD talk groups active. I'd hold the SDS100 on one of them and hear nothing, while audio was spouting from the PRO106 on that talk group.
Then I noticed that the 'idle' System Frequencies (the control channel frequencies) were different. The PRO106 was 'listening' to a control channel on 853.15, while the SDS100 was 'listening' on 853.9625 (or so said the display). Except when tuned to the RPD Northwest Dispatch... then both scanners were on the 853.9625 control channel (and the SDS100 received the transmissions). Both of those frequencies are listed as alternate control channels for the Wake Simulcast system. 853.9625 is in the list ahead of 853.15.
I temporarily deleted the 853.9625 frequency from the Site Frequency List, and wa la (as the kids say), I started receiving lots of stuff. I'd say 'everything' but who knows if something else is missing that I haven't noticed. But the other RPD dispatch, TAC and OPS channels, Wake Sheriff, EMS, Fire, etc. all made noise again, including RPD's Northwest Dispatch channel (with the scanner now telling me it was looking at the 853.15 control channel). I put 853.9625 back in the list, but moved it down 'below' 853.15, and things continued to work.
RF-wise, both channels are active with continuous data, like a control channel would be.
Um... WTF, over?
I'd been doing some revisions to the Favorites Lists for my Uniden SDS 100 and BCD536 scanners, when 'suddenly' things got too quiet. OK, not 'volume' quiet... 'missing talk groups' quiet.
After a while, I noticed that it was just the agencies on the Wake Simulcast system - I was still hearing Cary Fire on the Cary Simulcast system, NCSHP on VIPER, Durham on their system, etc. But most of the stuff on Wake was never showing activity. Most, but not all: I was still hearing the Raleigh PD's Northwest Dispatch talk group. Just that one... none of the others.
To shorten the story... checking things with my old Radio Shack PRO106, I found other RPD talk groups active. I'd hold the SDS100 on one of them and hear nothing, while audio was spouting from the PRO106 on that talk group.
Then I noticed that the 'idle' System Frequencies (the control channel frequencies) were different. The PRO106 was 'listening' to a control channel on 853.15, while the SDS100 was 'listening' on 853.9625 (or so said the display). Except when tuned to the RPD Northwest Dispatch... then both scanners were on the 853.9625 control channel (and the SDS100 received the transmissions). Both of those frequencies are listed as alternate control channels for the Wake Simulcast system. 853.9625 is in the list ahead of 853.15.
I temporarily deleted the 853.9625 frequency from the Site Frequency List, and wa la (as the kids say), I started receiving lots of stuff. I'd say 'everything' but who knows if something else is missing that I haven't noticed. But the other RPD dispatch, TAC and OPS channels, Wake Sheriff, EMS, Fire, etc. all made noise again, including RPD's Northwest Dispatch channel (with the scanner now telling me it was looking at the 853.15 control channel). I put 853.9625 back in the list, but moved it down 'below' 853.15, and things continued to work.
RF-wise, both channels are active with continuous data, like a control channel would be.
Um... WTF, over?
