Hi Folks,
Historically, U of Akron has had a networked LTR system for years. In recent years they started replacing this system with a NEXEDGE48 trunked system. That NEXEDGE48 system has been online for some time, with the old LTR system remaining online and functional to facilitate a nice transition from the old technology to new.
I was recently contacted (by a person who gave me some useful information about this trunked system earlier on). This person indicated that at this time the old UAkron LTR system has been totally decommissioned, and that the new NEXEDGE48 trunked system is fully operational.
Only certain Whistler scanners, as well as DSDPlus and perhaps other software based solutions, can monitor this NXDN system at this time.
This is currently a three-site system, with the main site being at University of Akron (Summit Co) and other sites being at Wayne College (Wayne Co) and at Medina County University Center (Medina Co).
https://www.radioreference.com/apps/db/?sid=9004
NOTE: The database currently ONLY reflects that which has been confirmed. However, all sites should be online, and my guess would be that most of the frequencies assigned on the licenses are in use.
UAKRON: WPRU679
WAYNE COLLEGE: WQOV271 and WQRE213
MEDINA UNIVERSITY CENTER: WQJB561
Presumably, with a Whistler scanner that supports NXDN, you could set up a NXDN trunked system with three sites, each site containing all of the frequencies on the respective licenses for that location, and it would trunk and you would hear traffic (and thus could report back your findings).
However, we really need to get more concrete information regarding what frequencies are active, as well as what their official NXDN channel numbers are. If you weren't aware, every NXDN frequency active at a particular site has a "channel number" associated with it. Hardware (scanners) and software (DSDPlus) that properly do trunktracking will rely upon knowing the exact mapping of CH # <--> Frequency.
So, IF you live within range of one of the sites, and IF you know how to use DSDPlus and have a Dongle or Airspy and can monitor the active control channel for that site, you can watch DSDPlus display the CH #s in use on the system if you allow DSDPlus to sit on the control channel for that site for an extended period of time. Those channel numbers are very important, and we would appreciate it if somebody out there could obtain that information.
In addition, assuming you have both the ability to use DSDPlus and have a scanner (regardless of whether the scanner handles NXDN or not), you could program the site's frequencies in as a bank of conventional frequencies and then scan them (locking out the active control channel). Then, you could watch in DSDPlus as voice traffic is occurring, and you could correlate the CH#s that you see active in DSDPlus with activity you hear on a particular frequency on your scanner.
So, if you live in one of the areas above, please consider helping us map out this system in its entirety.
Please post any questions or findings related to this trunked system in this thread.
Thank you,
Mike
Historically, U of Akron has had a networked LTR system for years. In recent years they started replacing this system with a NEXEDGE48 trunked system. That NEXEDGE48 system has been online for some time, with the old LTR system remaining online and functional to facilitate a nice transition from the old technology to new.
I was recently contacted (by a person who gave me some useful information about this trunked system earlier on). This person indicated that at this time the old UAkron LTR system has been totally decommissioned, and that the new NEXEDGE48 trunked system is fully operational.
Only certain Whistler scanners, as well as DSDPlus and perhaps other software based solutions, can monitor this NXDN system at this time.
This is currently a three-site system, with the main site being at University of Akron (Summit Co) and other sites being at Wayne College (Wayne Co) and at Medina County University Center (Medina Co).
https://www.radioreference.com/apps/db/?sid=9004
NOTE: The database currently ONLY reflects that which has been confirmed. However, all sites should be online, and my guess would be that most of the frequencies assigned on the licenses are in use.
UAKRON: WPRU679
WAYNE COLLEGE: WQOV271 and WQRE213
MEDINA UNIVERSITY CENTER: WQJB561
Presumably, with a Whistler scanner that supports NXDN, you could set up a NXDN trunked system with three sites, each site containing all of the frequencies on the respective licenses for that location, and it would trunk and you would hear traffic (and thus could report back your findings).
However, we really need to get more concrete information regarding what frequencies are active, as well as what their official NXDN channel numbers are. If you weren't aware, every NXDN frequency active at a particular site has a "channel number" associated with it. Hardware (scanners) and software (DSDPlus) that properly do trunktracking will rely upon knowing the exact mapping of CH # <--> Frequency.
So, IF you live within range of one of the sites, and IF you know how to use DSDPlus and have a Dongle or Airspy and can monitor the active control channel for that site, you can watch DSDPlus display the CH #s in use on the system if you allow DSDPlus to sit on the control channel for that site for an extended period of time. Those channel numbers are very important, and we would appreciate it if somebody out there could obtain that information.
In addition, assuming you have both the ability to use DSDPlus and have a scanner (regardless of whether the scanner handles NXDN or not), you could program the site's frequencies in as a bank of conventional frequencies and then scan them (locking out the active control channel). Then, you could watch in DSDPlus as voice traffic is occurring, and you could correlate the CH#s that you see active in DSDPlus with activity you hear on a particular frequency on your scanner.
So, if you live in one of the areas above, please consider helping us map out this system in its entirety.
Please post any questions or findings related to this trunked system in this thread.
Thank you,
Mike