hawkspringsfire
Member
Our local PD is now live on WyoLink. They have been testing tonight.
- Status
Torrington
I heard Torrington EMS on the Virgin Hill site last night. Is the Torrington tower operational yet?
I heard Torrington EMS on the Virgin Hill site last night. Is the Torrington tower operational yet?
hawkspringsfire
Member
They are in the testing process to see if there are any dead spots in the city. I am going to guess it will be live before the end of the month.
hawkspringsfire
Member
The new site is up and running in Torrington. Has anyone got the site info yet?
hawkspringsfire
Member
My bad I found it on the database. Thanks Don I must have looked right over it.
Pro96com for Cheyenne Watre Tanks
Would some kind soul run Pro96com against the Cheyenne Water Tanks site and post it?
I'm trying to reverse engineer how to build trunking tables and am unable to find a way for the posted multi-tables to hit on the the RR posted set of frequencies for CWT. Yes, I'm probably doing something wrong but it's also possible some of the posted data is incorrect. If I ever crack the formula for Pro96com to tables I plan to write it up.
CC is listed 169.625. (I can't hear it from my QTH)
Thanks!
Would some kind soul run Pro96com against the Cheyenne Water Tanks site and post it?
I'm trying to reverse engineer how to build trunking tables and am unable to find a way for the posted multi-tables to hit on the the RR posted set of frequencies for CWT. Yes, I'm probably doing something wrong but it's also possible some of the posted data is incorrect. If I ever crack the formula for Pro96com to tables I plan to write it up.
CC is listed 169.625. (I can't hear it from my QTH)
Thanks!
rickak
Member
What are you trying to crack? There is a section at the end of the pro96com manual that describes how to build pro96 tables from pro96com data.
I am pretty sure the system trunking tables are the same on all a systems' sites
Manual! Oh! I've had the program so long I didn't remember there was a manual.
I'll print those pages and study them.
I was trying to reverse-engineer how to build tables by studying what's on the Wyolink data because that's such a complex system.
I couldn't make the CWT freqs fit the trunking tables. So my calculation, or something, was wrong.
Ultimately trying to help another RR guy setup the new Ft. Carson system in Colo Spgs.
Last edited:
Thank you sir!
It looks like the trunking tables are the same as RR posted.
Which means that my backwards derivation of the tables is wrong.
Now that I have instructions on how to go from Pro96com to Pro-96 tables from the manual I guess I don't need to reverse-engineer it.
Thanks!
It looks like the trunking tables are the same as RR posted.
Which means that my backwards derivation of the tables is wrong.
Now that I have instructions on how to go from Pro96com to Pro-96 tables from the manual I guess I don't need to reverse-engineer it.
Thanks!
W7LES
Member
GRECOM PSR-800 scanner on WyoLink
GRECOM PSR-800 scanner on WyoLink
Howdy all:
Had a gent stop by with a PSR-800 the other day; got a chance to play with it on WyoLink for a bit. Programmed in the WyoLink trunking system wth all the VHF & 800 sites, and discovered something interesting. Seems that the 800 - unlike the 500 & 600 - does not have a STATionary trunking scanning mode: it is “stuck” in ROAM mode. If you don’t know what this means, check out the forum on GRE scanners and look through the postings on the PSR-800.
WyoLink has 3 areas that have overlapping coverage on both VHF & 800: Cheyenne, Casper & Gillette. Turns out that the Roam mode in the PSR-800 locks the scanner to the first strong site that meets the decode signal strength settings, and there the scanner stays until it moves away from that site and has to look for another site. During the tryout, the unit locked to the Cheyenne 800 site and would not scan to any of the VHF sites in the area. This is a problem because 90-95% of the time a talkgroup isn’t routinely going across to the other band. Sticking on 1 band will miss all the activity on the other band.
After a bit of head scratching, the workaround solution turned out to be very simple. What you want to do is to set up 2 trunking systems named WyoLink VHF and WyoLink 800. Then you program in all of the VHF sites (currently 50) to the WyoLink VHF system and all of the 800 sites (currently 4) to the WyoLink 800 system. Set up a wildcard for talkgroup and a wildcard for radio id in each system while you’re at it. The bad news is that you’re going to have to load all of the WyoLink talkgroup information into both system entries, probably by hand since there doesn’t seem to be any good way to cut-n-paste. (There may be a quick way to do the duplication, but I did not come across one in the short time I had to play with the unit.)
This will get the PSR-800 working fairly well on WyoLink, but as seen on the GRECOM forum discussions, the lack of a STAT mode is a serious drawback & handicap. In VHF only areas, the unit locks to 1 tower and will not look at other towers in the area that it can hear, thus missing out on traffic on those other towers that is not being carried on the tower that the radio happens to be locked on.
Bottom line: unless & until GRE updates the PSR-800 with user selectable STAT/ROAM, I’d recommend using another scanner than the PSR-800. Too bad, too - the 800 seems otherwise to be a nice slick little unit.
Regards,
Larry W7LES
GRECOM PSR-800 scanner on WyoLink
Howdy all:
Had a gent stop by with a PSR-800 the other day; got a chance to play with it on WyoLink for a bit. Programmed in the WyoLink trunking system wth all the VHF & 800 sites, and discovered something interesting. Seems that the 800 - unlike the 500 & 600 - does not have a STATionary trunking scanning mode: it is “stuck” in ROAM mode. If you don’t know what this means, check out the forum on GRE scanners and look through the postings on the PSR-800.
WyoLink has 3 areas that have overlapping coverage on both VHF & 800: Cheyenne, Casper & Gillette. Turns out that the Roam mode in the PSR-800 locks the scanner to the first strong site that meets the decode signal strength settings, and there the scanner stays until it moves away from that site and has to look for another site. During the tryout, the unit locked to the Cheyenne 800 site and would not scan to any of the VHF sites in the area. This is a problem because 90-95% of the time a talkgroup isn’t routinely going across to the other band. Sticking on 1 band will miss all the activity on the other band.
After a bit of head scratching, the workaround solution turned out to be very simple. What you want to do is to set up 2 trunking systems named WyoLink VHF and WyoLink 800. Then you program in all of the VHF sites (currently 50) to the WyoLink VHF system and all of the 800 sites (currently 4) to the WyoLink 800 system. Set up a wildcard for talkgroup and a wildcard for radio id in each system while you’re at it. The bad news is that you’re going to have to load all of the WyoLink talkgroup information into both system entries, probably by hand since there doesn’t seem to be any good way to cut-n-paste. (There may be a quick way to do the duplication, but I did not come across one in the short time I had to play with the unit.)
This will get the PSR-800 working fairly well on WyoLink, but as seen on the GRECOM forum discussions, the lack of a STAT mode is a serious drawback & handicap. In VHF only areas, the unit locks to 1 tower and will not look at other towers in the area that it can hear, thus missing out on traffic on those other towers that is not being carried on the tower that the radio happens to be locked on.
Bottom line: unless & until GRE updates the PSR-800 with user selectable STAT/ROAM, I’d recommend using another scanner than the PSR-800. Too bad, too - the 800 seems otherwise to be a nice slick little unit.
Regards,
Larry W7LES
PSR-800 not good for WYOLINK
That is not good news to here about Wyolink and the PSR-800. More so, since I just sold my PSR-500 in order to buy the 800.
That is not good news to here about Wyolink and the PSR-800. More so, since I just sold my PSR-500 in order to buy the 800.
Response from GRE - PSR-800 & WYOLINK
We are looking into adding the STAT mode to the PSR-800. We do not have a timetable for doing so. In the mean time, you could use the option in the latest version of the PC Application to duplicate the system, and then remove the 800Mhz systems from one of them.
Best Regards,GRE Support Team
GRE America, Inc. - Powered By Kayako SupportSuite
Ticket Information: GRE America, Inc. - Powered By Kayako SupportSuite Ticket Details===================Ticket ID: 26310Department: Scanner ReceiversPriority: MediumStatus: Open
We are looking into adding the STAT mode to the PSR-800. We do not have a timetable for doing so. In the mean time, you could use the option in the latest version of the PC Application to duplicate the system, and then remove the 800Mhz systems from one of them.
Best Regards,GRE Support Team
GRE America, Inc. - Powered By Kayako SupportSuite
Ticket Information: GRE America, Inc. - Powered By Kayako SupportSuite Ticket Details===================Ticket ID: 26310Department: Scanner ReceiversPriority: MediumStatus: Open
What version of PRO96COM are you using? why does it not show the WACN?
Casper 800 - fully integrated with WyoLink
Yup - as it says. The upgrade is done (actually, been done for a few months now). Casper (Natrona County's) 800Mhz SmartZone site has been upgraded to SmartNet and integrated with WyoLink.
Everything that was on the old Astro 800Mhz system is now managed by WyoLink.
Grand time was had by all, lemme tell ya. And now and then, the party continues.
Yup - as it says. The upgrade is done (actually, been done for a few months now). Casper (Natrona County's) 800Mhz SmartZone site has been upgraded to SmartNet and integrated with WyoLink.
Everything that was on the old Astro 800Mhz system is now managed by WyoLink.
Grand time was had by all, lemme tell ya. And now and then, the party continues.
wyomingmedic
Member
- Joined
- Aug 17, 2008
- Messages
- 541
- Reaction score
- 57
And it has really helped us scanner listeners. There were some dead areas on the 800Mhz frequencies. And since so many agencies are using the VF side more, the traffic is always "crossband" on the main TGs. The dead areas on 800 are not dead on VHF and visa verse. And areas out towards Alcova and Pathfinder were a tough copy on 800. They are now solid on VHF.
Same for routes south on I-25. North on I-25 still has better coverage on 800 unless the traffic is affiliated with the VHF mountain site as opposed to the port of entry site.
All in all, great for us.
WM
Same for routes south on I-25. North on I-25 still has better coverage on 800 unless the traffic is affiliated with the VHF mountain site as opposed to the port of entry site.
All in all, great for us.
WM
trunking
I don't think there is a NAC. NAC is for conventional digital kind of like PL or DPL on analog. Somebody correct me if I am wrong on this. I think the only way to filter out TGs is with a scanner in trunked mode. I listen on an old Astro radio but unfortunately I hear every talkgroup that is busy.
I don't think there is a NAC. NAC is for conventional digital kind of like PL or DPL on analog. Somebody correct me if I am wrong on this. I think the only way to filter out TGs is with a scanner in trunked mode. I listen on an old Astro radio but unfortunately I hear every talkgroup that is busy.
PJH
Member
- Joined
- Aug 23, 2002
- Messages
- 3,622
- Reaction score
- 87
Your logic is correct, however with APCO25 systems there actually is a NAC transmitted. Its derived from the system id and the connect tone. If you know the NAC, you can scan (conventionally) an APCO25 system using the NAC and talkgroup. What happens is when using the correct NAC code (vs using 293/F7E or digital CSQ) the radio will only unmute on the proper talkgroups being received. Hence my request 
NAC question
What if you set receive NAC to $F7F? Then would it let you filter by putting TG numbers in?
What if you set receive NAC to $F7F? Then would it let you filter by putting TG numbers in?
- Status
