sfd119
Member
- Joined
- Jul 18, 2009
- Messages
- 1,762
- Reaction score
- 105
Does anyone know if there is any truth to the rumor that Sawyer Co went back to their conventional channels?
They're still on WISCOM as of tonight. I heard them on their normal TGs.
Does anyone know if there is any truth to the rumor that Sawyer Co went back to their conventional channels?
No WISCOM towers or enhancements just expansion of the legacy system.
The crossover from legacy to WISCOM will still remain in place also.
The comments in that article by the sheriff are a bit stark, but perhaps that's the rhetoric needed to get things done sometimes.
This would imply that they are going to be moving off of WISCOM but I don't have any firsthand knowledge of that.
http://www.apg-wi.com/sawyer_county...cle_b140d170-8d7f-11e5-8bea-f764626be641.html
Article is unclear what the funds are exactly for, but the sentiment expressed by the sheriff is very clear.
Drove through the entire length of the state recently, traveling for the holidays.
I upgraded my mobile setup, this time using 5/8 wave commercial antennas with just a very short run of low-loss coax, terminating directly (no adapters) into my portables I was using on this trip. These antennas are advertised with 3db gain, and they perform very well indeed. The downside is that they are about 5 feet tall, so they strike trees in driveways, low overhangs and there’s no way they’ll go into a garage or parking structure/sallyport. I also put them in the correct place which is the center of the roof of my SUV, I suspect many users would be sorely tempted to place them on the trunk; they will still function there but the radiation pattern will be altered.
In any case, the payoff is with far greater listening distance. It wasn’t horrible on my last trip, but this time it was simply excellent. As an example, I could hear the Baraboo site in Warrens (north of the 90/94 split).
When looking at the coverage maps created before the trip, I was skeptical that the maps were correct, they looked horribly optimistic. Turns out they are generally accurate, and in a few cases, even a bit pessimistic. This was good, as I added quite a few towers to capture more traffic on the drives up and back. All in all, I had over 35 sites programmed. Also note - this is site to mobile coverage. Site to handheld and mobile to site, as well as handheld to site are different maps, with smaller coverage areas. Also, these sites have coverage which vastly exceeds their operational serving area, check the best server maps for comparisons. Typically (based on configuration and programming; exceptions do exist) a P25 unit in the field will automatically be selecting the site with the strongest CC signal, which will generally be the closest site.
The native P25 traffic - what little there is - sounds, well, like native P25 traffic, which is pretty good, but will never sound as good as a good quality full-quieting FM signal. But it’s generally more consistent and once you’re used to it, the consistency is a major plus; going back to analog, you’ll quickly notice all of the analog artifacts. The scan TGs are still pretty bad, not that I expected any improvements of course.
There was no WSP activity that I heard; last trip there were some patches up, those were gone, I only heard them on conventional VHF.
Iowa county sounded fine; as did Gold Cross in Eau Claire and Sawyer county traffic. Something was amiss with Douglas County; not all traffic was being carried on all sites, and for quite a long time Maple’s CC would not decode but I could hear it quite well. The last morning I was in the area it started decoding, but heard no traffic on it. I suspect there was some maintenance going on as when I drove past the Parkland site there were people on the tower.
Unlike the last trip, Gold Cross Duluth traffic wasn’t always heard on the Douglas WISCOM sites either. Perhaps a console patch needs to happen, or there was a timeout of some sort on either side, but GC dispatches weren’t heard until there was a call into Superior, then some towers (not all) started carrying the traffic.
I did have the opportunity to monitor the Red Cliff site for extended periods of time, while decode was 100%, I heard not one transmission the entire time (approx 10 hours of listening over several days). It’s quiet up in the northwoods this time of year. As a site note, coverage for Red Cliff extends well up the Minnesota north shore, perhaps as far as Lutsen.
Since no licenses have been granted for the Port Wing site yet, I didn’t attempt to monitor that site.
In the southern part of the state, the Dane Scan TG wasn’t being carried by the Van Hise site, but it is carried by both the Milton and Deerfield sites - that’s the only Scan TG that I’ve found carried on more than one tower so far.
I didn’t even try to figure out what’s going on Juneau county, didn’t even program it in based on getting nothing on the last trip and basically having that confirmed in this thread before I left. My editorial comment is that C4FM simulcasting is likely to be a cluster for technical reasons, LSM has definite reasons for being used. “Just because you can doesn’t mean you should” definitely applies to C4FM simulcasting.
Much like last time, there’s very little traffic on the system other than the scan groups. Of course, some of that has to do with the time of year and the fact that much of the state is quite rural and there just isn’t much going on.
Perhaps this has been noticed; I found the following blurb in the state budget summary, which was out in July of 2015, so I believe the June 30th date refers to 6/30/2016:
“Interoperability Report: The budget requires the Interoperability Council to submit a report to the Joint Committee on Finance by June 30 regarding the following issues: the amount the state has expended to develop, construct, and operate the Wisconsin Interoperability System for Communications (WISCOM), from its inception through 2015-16; the annual operating budget for WISCOM during 2015-16, specifically identifying costs relating to staff, infrastructure expansion, infrastructure maintenance, supplies and services, and other related costs; the local, state, and federal agencies that use WISCOM, as well as the frequency with which the agencies use the system and a description of how each agency uses WISCOM to support the agency’s operation; identification of the local, state, and federal agencies that use an alternative communications system for its emergency responders, as well as an explanation why the alternative system is used; identification of each federal, state, and local agency that uses WISCOM daily, and an explanation why they do so; identification of each federal, state, and local agency that does not currently use WISCOM daily, but intends to do so, as well as when the agencies intend to use WISCOM daily; an explanation of the current status of WISCOM’s infrastructure and an indication of whether, and how, it may be expanded in the future; a comparison to other, similar systems in other states; a statement of WISCOM’s successes; a statement of the challenges facing WISCOM; an explanation of WISCOM’s compatibility with other emergency response communication networks; and a statement on the number of sites, channels, and users WISCOM currently supports and its anticipated future capacity.”