Misprint? WQCX408callsign WQCL408
Misprint? WQCX408callsign WQCL408
Thanks for catching my typo! It should be WQCX408.Misprint? WQCX408
The RR database shows SC21 using NAC141. Are you able to determine what NAC the 853.975 repeater you're hearing is using?Sitting here tuned to 853.975 and watching Pro96Com. There is a lot of enc P2 traffic on that frequency. That might explain some of the noise you are hearing
It is just a new voice channel for 2-29, so it uses the site nac 141.853.975 repeater
Thanks for the NAC confirmation!It is just a new voice channel for 2-29, so it uses the site nac 141.
I misunderstood your question. I will try and listen to 808.975 tonight or tomorrow.Are you able to determine what NAC the 853.975 repeater you're hearing is using?
853.975 is what I was wondering about, not the input freq.I misunderstood your question. I will try and listen to 808.975 tonight or tomorrow.
Appears it's not just me with issues. Heard county radio techs testing near Watterson a bit ago and saying anything on the new frequency is dropping a ton of packets and weak.Yep, NAC is 141. Doesn't come in very well to me but just good enough for DSD to...mostly...decode it. There's at least one other frequency my radios don't like for some reason from the Normal site and I've never been able to figure out why. Yet I can pull in Congerville and most of the other McLean County sites with absolutely no problems at all. Go figure.
No it is not just you. I think there are issues with the whole site.Appears it's not just me with issues. Heard county radio techs testing near Watterson a bit ago and saying anything on the new frequency is dropping a ton of packets and weak.
I'm seeing new radio ID's for the Troop 3-Chicago Telecommunicators today. 1904400 this morning and 1904401 started showing up this afternoon across all the talk groups. 190439x series are the current ones in use too. I previously saw these new radio ID's across the tollway talk groups testing over the summer.
It's been that way for about a week.Dispatcher on TG9008 today using 1904400
I have Cook North to monitor Troop 3 and NWCD on scan with the G5. I don't have any issues that I've seen. I will use my SDS100 if it does something.Is it just me, or is Site 1-049 (Cook North) acting up? For the past few days, it seems like my scanners briefly lose connection to the CC at random. One thing I found peculiar is that when running the CC (851.5375) through the Waterfall and Quick Search on my SDS200, it keeps switching between 'DATA' and 'LINK' which I've never seen happen before.
Things are back to normal as of now. This past Thanksgiving weekend, I switched my SDS' from Simple to Detail display and noticed that the CC would periodically switch between 851.5375 (the usual) and 851.8375. Not sure why it did that, but it was most likely the cause of the issue.I have Cook North to monitor Troop 3 and NWCD on scan with the G5. I don't have any issues that I've seen. I will use my SDS100 if it does something.
Yes. I've had it enabled for both my SDS100 and SDS200. And for 1-049, I can confirm that the Site NAC I have programmed is 141.Are you programming and setting up the scanner to use Site NAC?
I see 851.8375 as a Control Channel for both sites so just threw it out there. Are you in range of the Ottawa site or just one of those things that never happened before?Yes. I've had it enabled for both my SDS100 and SDS200. And for 1-049, I can confirm that the Site NAC I have programmed is 141.
Nowhere near within range, since it's over 90 miles away from me. Pretty sure it was the latter.Are you in range of the Ottawa site or just one of those things that never happened before?