https://wiki.radioreference.com/api.php?action=feedcontributions&user=Loumaag&feedformat=atomThe RadioReference Wiki - User contributions [en]2024-03-29T09:10:10ZUser contributionsMediaWiki 1.33.0https://wiki.radioreference.com/index.php?title=Houston_Police_and_Fire_P25&diff=117587Houston Police and Fire P252013-07-16T15:06:56Z<p>Loumaag: Adding further clarification about the P25 CCh and why it needs to be done just like suggested</p>
<hr />
<div>The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using [[APCO_Project_25|P25 Phase 2]] technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the [[PSR-800|GRE PSR800]]) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with the specific site 3-05 and, depending on your scanner's make up, as a separate system or bank. <br/><br />
<br />
<site>4563|19576</site><br />
<br />
== Programing Details ==<br />
=== Considerations ===<br />
==== Layer Layout ====<br />
In general, as stated above, the specific site needs to set up as a separate system in your scanner. It should not be combined with other sites as the traffic on that site is separate and distinct from other sites in the system. This system should really be considered as four layers or Radio Frequency Subsystems (RFSS) , even though there are only three layers enumerated. For programing purposes the following should be considered:<br />
* Layer 1 - contains only P25 Phase 1 traffic for the regional area in and around metropolitan Houston and close in environs. This includes, but is not limited to Austin, Brazoria, Chambers, Ft Bend, Galveston, Harris, Liberty, Montgomery, Walker, Waller, and Washington counties.<br />
* Layer 2 - contains only P25 Phase 1 traffic for the regions outside the areas covered by layer 1. <br />
* Layer 3 - contains a mix of P25 Phase 1 and Phase 2 as follows:<br />
** All layer 3 sites except 3-05 - carry only Phase 2 traffic for the City of Houston and some other smaller entities in and around the city; for example, the Memorial Villages which are in the clear but Phase 2 only. These entities also make extensive use of encryption on other than the dispatch channels and in some case (Bellaire for example) encrypt the dispatch channels also. <br />
** Layer 3, site 5 - the Houston General Government Services Simulcast site. This site is used for the all City of Houston public works in addition to the simulcast of the HPD/HFD channels mentioned above.<br />
<br />
==== Breakdown ====<br />
Naturally, a lot of interest is in how to program this system for more than one agency. As such, in general you should consider it as three separate systems from a scanner programming standpoint. <br />
* Layers 1 & 2 as one FDMA (Phase 1) system<br />
* Layer 3 sites (except for 3-05) as one TDMA (Phase 2) only system<br />
* Layer 3, site 05 as a mixed FDMA / TDMA system<br />
<br />
===== Non HPD/HFD Phase 1 Only =====<br />
Treating layers 1 and 2 as you would any other P25 system, considering overlap and who uses what sites, you would program your scanner as you would for any other P25 trunking system. <br />
<br />
===== All Phase 2 =====<br />
If you are in possession of a GRE PSR800, you can program all the TDMA available channels in, using layer 3 sites remembering that different traffic is carried on site 3-05 than is carried on the rest of the layer 3 sites. In other words, if you happen to have a PSR800 and wanted to listen to HPD or HFD in TDMA, that traffic is <b>not</b> carried on site 3-05, but rather on the other sites under standard affiliation concepts with a preference given to sites 3-01 through 3-04, meaning sites 3-11 through 3-16 will only carry HPD/HFD traffic if an affiliated radio is completely out of range of the primary sites. That programing is not the subject of this article but this explanation is given to help understand what is carried where.<br />
<br />
===== HPD/HFD Phase 1 Simulcast =====<br />
As stated above, this is found using the listed talk groups and on the specified site (3-05). Interestingly enough, that site uses only 800 MHz frequencies. This means that even older scanners, capable of following a P25 9600 bps control channel, but not able to tune 700 MHz frequencies can be used to monitor these simulcast talk groups. Such scanners include Uniden BC796D and Radio Shack Pro-96 type scanners. Please note, this site is simulcast from seven different towers (at this time), so your scanner does have to deal with multi-path distortion. <br />
<br />
Naturally, each scanner model or brand is programed differently so the following detailed steps for setting this up are in general and you will have to use this as a guide to setting your individual radio up:<br />
* Program site 3-05 as a separate single site system<br />
* Program only the talk groups you want to hear from the list above<br />
* Since the P25 control channel is the same no matter what type of voice channel is being used (Phase 1 or 2) and you do not want your scanner chasing talk groups it cannot hear, the following two points are vital:<br />
** Set the system up as Closed or ID Scan, depending on the brand of scanner<br />
** Do not set a "wildcard" talk group up on the system<br />
<br />
=== Synopsis ===<br />
Almost any P25 trunking scanner can be used for this. Some handle multi-path distortion better than others, and how you adapt your scanner programing to fit this situation is up to you. However, so far it has been shown that the above works on radios as varied as a Uniden BC796D to the HP-1 and a Pro-96 to the PSR800. The key is to remember that monitoring the HPD/HFD Phase 1 simulcast transmissions needs to be considered as a separate operation from any other operation your scanner might be tasked with.<br />
<br />
<br />
Return to [[Texas Wide Area Radio Network (TxWARN) Project 25]] collaboration page.<br />
<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Houston_Police_and_Fire_P25&diff=115631Houston Police and Fire P252013-05-17T21:41:49Z<p>Loumaag: /* All Phase 2 */ Expanding on site preferences</p>
<hr />
<div>The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using [[APCO_Project_25|P25 Phase 2]] technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the [[PSR-800|GRE PSR800]]) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with the specific site 3-05 and, depending on your scanner's make up, as a separate system or bank. <br/><br />
<br />
<site>4563|19576</site><br />
<br />
== Programing Details ==<br />
=== Considerations ===<br />
==== Layer Layout ====<br />
In general, as stated above, the specific site needs to set up as a separate system in your scanner. It should not be combined with other sites as the traffic on that site is separate and distinct from other sites in the system. This system should really be considered as four layers or Radio Frequency Subsystems (RFSS) , even though there are only three layers enumerated. For programing purposes the following should be considered:<br />
* Layer 1 - contains only P25 Phase 1 traffic for the regional area in and around metropolitan Houston and close in environs. This includes, but is not limited to Austin, Brazoria, Chambers, Ft Bend, Galveston, Harris, Liberty, Montgomery, Walker, Waller, and Washington counties.<br />
* Layer 2 - contains only P25 Phase 1 traffic for the regions outside the areas covered by layer 1. <br />
* Layer 3 - contains a mix of P25 Phase 1 and Phase 2 as follows:<br />
** All layer 3 sites except 3-05 - carry only Phase 2 traffic for the City of Houston and some other smaller entities in and around the city; for example, the Memorial Villages which are in the clear but Phase 2 only. These entities also make extensive use of encryption on other than the dispatch channels and in some case (Bellaire for example) encrypt the dispatch channels also. <br />
** Layer 3, site 5 - the Houston General Government Services Simulcast site. This site is used for the all City of Houston public works in addition to the simulcast of the HPD/HFD channels mentioned above.<br />
<br />
==== Breakdown ====<br />
Naturally, a lot of interest is in how to program this system for more than one agency. As such, in general you should consider it as three separate systems from a scanner programming standpoint. <br />
* Layers 1 & 2 as one FDMA (Phase 1) system<br />
* Layer 3 sites (except for 3-05) as one TDMA (Phase 2) only system<br />
* Layer 3, site 05 as a mixed FDMA / TDMA system<br />
<br />
===== Non HPD/HFD Phase 1 Only =====<br />
Treating layers 1 and 2 as you would any other P25 system, considering overlap and who uses what sites, you would program your scanner as you would for any other P25 trunking system. <br />
<br />
===== All Phase 2 =====<br />
If you are in possession of a GRE PSR800, you can program all the TDMA available channels in, using layer 3 sites remembering that different traffic is carried on site 3-05 than is carried on the rest of the layer 3 sites. In other words, if you happen to have a PSR800 and wanted to listen to HPD or HFD in TDMA, that traffic is <b>not</b> carried on site 3-05, but rather on the other sites under standard affiliation concepts with a preference given to sites 3-01 through 3-04, meaning sites 3-11 through 3-16 will only carry HPD/HFD traffic if an affiliated radio is completely out of range of the primary sites. That programing is not the subject of this article but this explanation is given to help understand what is carried where.<br />
<br />
===== HPD/HFD Phase 1 Simulcast =====<br />
As stated above, this is found using the listed talk groups and on the specified site (3-05). Interestingly enough, that site uses only 800 MHz frequencies. This means that even older scanners, capable of following a P25 9600 bps control channel, but not able to tune 700 MHz frequencies can be used to monitor these simulcast talk groups. Such scanners include Uniden BC796D and Radio Shack Pro-96 type scanners. Please note, this site is simulcast from seven different towers (at this time), so your scanner does have to deal with multi-path distortion. <br />
<br />
Naturally, each scanner model or brand is programed differently so the following detailed steps for setting this up are in general and you will have to use this as a guide to setting your individual radio up:<br />
* Program site 3-05 as a separate single site system<br />
* Program the talk groups you want to hear from the list above<br />
* Set the system up as Closed or ID Scan, depending on the brand of scanner<br />
* Do not set a "wildcard" talk group up on the system<br />
<br />
=== Synopsis ===<br />
Almost any P25 trunking scanner can be used for this. Some handle multi-path distortion better than others, and how you adapt your scanner programing to fit this situation is up to you. However, so far it has been shown that the above works on radios as varied as a Uniden BC796D to the HP-1 and a Pro-96 to the PSR800. The key is to remember that monitoring the HPD/HFD Phase 1 simulcast transmissions needs to be considered as a separate operation from any other operation your scanner might be tasked with.<br />
<br />
<br />
Return to [[Texas Wide Area Radio Network (TxWARN) Project 25]] collaboration page.<br />
<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=User:Loumaag&diff=115614User:Loumaag2013-05-17T18:56:48Z<p>Loumaag: Replaced content with "Scratch page for me"</p>
<hr />
<div>Scratch page for me</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Houston_Police_and_Fire_P25&diff=115612Houston Police and Fire P252013-05-17T18:52:29Z<p>Loumaag: /* Synopsis */ adding "collaboration" to avoid confusion</p>
<hr />
<div>The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using [[APCO_Project_25|P25 Phase 2]] technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the [[PSR-800|GRE PSR800]]) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with the specific site 3-05 and, depending on your scanner's make up, as a separate system or bank. <br/><br />
<br />
<site>4563|19576</site><br />
<br />
== Programing Details ==<br />
=== Considerations ===<br />
==== Layer Layout ====<br />
In general, as stated above, the specific site needs to set up as a separate system in your scanner. It should not be combined with other sites as the traffic on that site is separate and distinct from other sites in the system. This system should really be considered as four layers or Radio Frequency Subsystems (RFSS) , even though there are only three layers enumerated. For programing purposes the following should be considered:<br />
* Layer 1 - contains only P25 Phase 1 traffic for the regional area in and around metropolitan Houston and close in environs. This includes, but is not limited to Austin, Brazoria, Chambers, Ft Bend, Galveston, Harris, Liberty, Montgomery, Walker, Waller, and Washington counties.<br />
* Layer 2 - contains only P25 Phase 1 traffic for the regions outside the areas covered by layer 1. <br />
* Layer 3 - contains a mix of P25 Phase 1 and Phase 2 as follows:<br />
** All layer 3 sites except 3-05 - carry only Phase 2 traffic for the City of Houston and some other smaller entities in and around the city; for example, the Memorial Villages which are in the clear but Phase 2 only. These entities also make extensive use of encryption on other than the dispatch channels and in some case (Bellaire for example) encrypt the dispatch channels also. <br />
** Layer 3, site 5 - the Houston General Government Services Simulcast site. This site is used for the all City of Houston public works in addition to the simulcast of the HPD/HFD channels mentioned above.<br />
<br />
==== Breakdown ====<br />
Naturally, a lot of interest is in how to program this system for more than one agency. As such, in general you should consider it as three separate systems from a scanner programming standpoint. <br />
* Layers 1 & 2 as one FDMA (Phase 1) system<br />
* Layer 3 sites (except for 3-05) as one TDMA (Phase 2) only system<br />
* Layer 3, site 05 as a mixed FDMA / TDMA system<br />
<br />
===== Non HPD/HFD Phase 1 Only =====<br />
Treating layers 1 and 2 as you would any other P25 system, considering overlap and who uses what sites, you would program your scanner as you would for any other P25 trunking system. <br />
<br />
===== All Phase 2 =====<br />
If you are in possession of a GRE PSR800, you can program all the TDMA available channels in, using layer 3 sites remembering that different traffic is carried on site 3-05 than is carried on the rest of the layer 3 sites. In other words, if you happen to have a PSR800 and wanted to listen to HPD or HFD in TDMA, that traffic is <b>not</b> carried on site 3-05, but rather on the other sites under standard affiliation concepts. That programing is not the subject of this article but this explanation is given to help understand what is carried where.<br />
<br />
===== HPD/HFD Phase 1 Simulcast =====<br />
As stated above, this is found using the listed talk groups and on the specified site (3-05). Interestingly enough, that site uses only 800 MHz frequencies. This means that even older scanners, capable of following a P25 9600 bps control channel, but not able to tune 700 MHz frequencies can be used to monitor these simulcast talk groups. Such scanners include Uniden BC796D and Radio Shack Pro-96 type scanners. Please note, this site is simulcast from seven different towers (at this time), so your scanner does have to deal with multi-path distortion. <br />
<br />
Naturally, each scanner model or brand is programed differently so the following detailed steps for setting this up are in general and you will have to use this as a guide to setting your individual radio up:<br />
* Program site 3-05 as a separate single site system<br />
* Program the talk groups you want to hear from the list above<br />
* Set the system up as Closed or ID Scan, depending on the brand of scanner<br />
* Do not set a "wildcard" talk group up on the system<br />
<br />
=== Synopsis ===<br />
Almost any P25 trunking scanner can be used for this. Some handle multi-path distortion better than others, and how you adapt your scanner programing to fit this situation is up to you. However, so far it has been shown that the above works on radios as varied as a Uniden BC796D to the HP-1 and a Pro-96 to the PSR800. The key is to remember that monitoring the HPD/HFD Phase 1 simulcast transmissions needs to be considered as a separate operation from any other operation your scanner might be tasked with.<br />
<br />
<br />
Return to [[Texas Wide Area Radio Network (TxWARN) Project 25]] collaboration page.<br />
<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Houston_Police_and_Fire_P25&diff=115610Houston Police and Fire P252013-05-17T18:51:11Z<p>Loumaag: /* Specific Site */ Fixing site code</p>
<hr />
<div>The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using [[APCO_Project_25|P25 Phase 2]] technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the [[PSR-800|GRE PSR800]]) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with the specific site 3-05 and, depending on your scanner's make up, as a separate system or bank. <br/><br />
<br />
<site>4563|19576</site><br />
<br />
== Programing Details ==<br />
=== Considerations ===<br />
==== Layer Layout ====<br />
In general, as stated above, the specific site needs to set up as a separate system in your scanner. It should not be combined with other sites as the traffic on that site is separate and distinct from other sites in the system. This system should really be considered as four layers or Radio Frequency Subsystems (RFSS) , even though there are only three layers enumerated. For programing purposes the following should be considered:<br />
* Layer 1 - contains only P25 Phase 1 traffic for the regional area in and around metropolitan Houston and close in environs. This includes, but is not limited to Austin, Brazoria, Chambers, Ft Bend, Galveston, Harris, Liberty, Montgomery, Walker, Waller, and Washington counties.<br />
* Layer 2 - contains only P25 Phase 1 traffic for the regions outside the areas covered by layer 1. <br />
* Layer 3 - contains a mix of P25 Phase 1 and Phase 2 as follows:<br />
** All layer 3 sites except 3-05 - carry only Phase 2 traffic for the City of Houston and some other smaller entities in and around the city; for example, the Memorial Villages which are in the clear but Phase 2 only. These entities also make extensive use of encryption on other than the dispatch channels and in some case (Bellaire for example) encrypt the dispatch channels also. <br />
** Layer 3, site 5 - the Houston General Government Services Simulcast site. This site is used for the all City of Houston public works in addition to the simulcast of the HPD/HFD channels mentioned above.<br />
<br />
==== Breakdown ====<br />
Naturally, a lot of interest is in how to program this system for more than one agency. As such, in general you should consider it as three separate systems from a scanner programming standpoint. <br />
* Layers 1 & 2 as one FDMA (Phase 1) system<br />
* Layer 3 sites (except for 3-05) as one TDMA (Phase 2) only system<br />
* Layer 3, site 05 as a mixed FDMA / TDMA system<br />
<br />
===== Non HPD/HFD Phase 1 Only =====<br />
Treating layers 1 and 2 as you would any other P25 system, considering overlap and who uses what sites, you would program your scanner as you would for any other P25 trunking system. <br />
<br />
===== All Phase 2 =====<br />
If you are in possession of a GRE PSR800, you can program all the TDMA available channels in, using layer 3 sites remembering that different traffic is carried on site 3-05 than is carried on the rest of the layer 3 sites. In other words, if you happen to have a PSR800 and wanted to listen to HPD or HFD in TDMA, that traffic is <b>not</b> carried on site 3-05, but rather on the other sites under standard affiliation concepts. That programing is not the subject of this article but this explanation is given to help understand what is carried where.<br />
<br />
===== HPD/HFD Phase 1 Simulcast =====<br />
As stated above, this is found using the listed talk groups and on the specified site (3-05). Interestingly enough, that site uses only 800 MHz frequencies. This means that even older scanners, capable of following a P25 9600 bps control channel, but not able to tune 700 MHz frequencies can be used to monitor these simulcast talk groups. Such scanners include Uniden BC796D and Radio Shack Pro-96 type scanners. Please note, this site is simulcast from seven different towers (at this time), so your scanner does have to deal with multi-path distortion. <br />
<br />
Naturally, each scanner model or brand is programed differently so the following detailed steps for setting this up are in general and you will have to use this as a guide to setting your individual radio up:<br />
* Program site 3-05 as a separate single site system<br />
* Program the talk groups you want to hear from the list above<br />
* Set the system up as Closed or ID Scan, depending on the brand of scanner<br />
* Do not set a "wildcard" talk group up on the system<br />
<br />
=== Synopsis ===<br />
Almost any P25 trunking scanner can be used for this. Some handle multi-path distortion better than others, and how you adapt your scanner programing to fit this situation is up to you. However, so far it has been shown that the above works on radios as varied as a Uniden BC796D to the HP-1 and a Pro-96 to the PSR800. The key is to remember that monitoring the HPD/HFD Phase 1 simulcast transmissions needs to be considered as a separate operation from any other operation your scanner might be tasked with.<br />
<br />
<br />
Return to [[Texas Wide Area Radio Network (TxWARN) Project 25]] page.<br />
<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Houston_Police_and_Fire_P25&diff=115609Houston Police and Fire P252013-05-17T18:48:48Z<p>Loumaag: New article on monitoring Houston PD and FD</p>
<hr />
<div>The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using [[APCO_Project_25|P25 Phase 2]] technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the [[PSR-800|GRE PSR800]]) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with the specific site 3-05 and, depending on your scanner's make up, as a separate system or bank. <br/><br />
<br />
<site>18743|19576</site><br />
<br />
== Programing Details ==<br />
=== Considerations ===<br />
==== Layer Layout ====<br />
In general, as stated above, the specific site needs to set up as a separate system in your scanner. It should not be combined with other sites as the traffic on that site is separate and distinct from other sites in the system. This system should really be considered as four layers or Radio Frequency Subsystems (RFSS) , even though there are only three layers enumerated. For programing purposes the following should be considered:<br />
* Layer 1 - contains only P25 Phase 1 traffic for the regional area in and around metropolitan Houston and close in environs. This includes, but is not limited to Austin, Brazoria, Chambers, Ft Bend, Galveston, Harris, Liberty, Montgomery, Walker, Waller, and Washington counties.<br />
* Layer 2 - contains only P25 Phase 1 traffic for the regions outside the areas covered by layer 1. <br />
* Layer 3 - contains a mix of P25 Phase 1 and Phase 2 as follows:<br />
** All layer 3 sites except 3-05 - carry only Phase 2 traffic for the City of Houston and some other smaller entities in and around the city; for example, the Memorial Villages which are in the clear but Phase 2 only. These entities also make extensive use of encryption on other than the dispatch channels and in some case (Bellaire for example) encrypt the dispatch channels also. <br />
** Layer 3, site 5 - the Houston General Government Services Simulcast site. This site is used for the all City of Houston public works in addition to the simulcast of the HPD/HFD channels mentioned above.<br />
<br />
==== Breakdown ====<br />
Naturally, a lot of interest is in how to program this system for more than one agency. As such, in general you should consider it as three separate systems from a scanner programming standpoint. <br />
* Layers 1 & 2 as one FDMA (Phase 1) system<br />
* Layer 3 sites (except for 3-05) as one TDMA (Phase 2) only system<br />
* Layer 3, site 05 as a mixed FDMA / TDMA system<br />
<br />
===== Non HPD/HFD Phase 1 Only =====<br />
Treating layers 1 and 2 as you would any other P25 system, considering overlap and who uses what sites, you would program your scanner as you would for any other P25 trunking system. <br />
<br />
===== All Phase 2 =====<br />
If you are in possession of a GRE PSR800, you can program all the TDMA available channels in, using layer 3 sites remembering that different traffic is carried on site 3-05 than is carried on the rest of the layer 3 sites. In other words, if you happen to have a PSR800 and wanted to listen to HPD or HFD in TDMA, that traffic is <b>not</b> carried on site 3-05, but rather on the other sites under standard affiliation concepts. That programing is not the subject of this article but this explanation is given to help understand what is carried where.<br />
<br />
===== HPD/HFD Phase 1 Simulcast =====<br />
As stated above, this is found using the listed talk groups and on the specified site (3-05). Interestingly enough, that site uses only 800 MHz frequencies. This means that even older scanners, capable of following a P25 9600 bps control channel, but not able to tune 700 MHz frequencies can be used to monitor these simulcast talk groups. Such scanners include Uniden BC796D and Radio Shack Pro-96 type scanners. Please note, this site is simulcast from seven different towers (at this time), so your scanner does have to deal with multi-path distortion. <br />
<br />
Naturally, each scanner model or brand is programed differently so the following detailed steps for setting this up are in general and you will have to use this as a guide to setting your individual radio up:<br />
* Program site 3-05 as a separate single site system<br />
* Program the talk groups you want to hear from the list above<br />
* Set the system up as Closed or ID Scan, depending on the brand of scanner<br />
* Do not set a "wildcard" talk group up on the system<br />
<br />
=== Synopsis ===<br />
Almost any P25 trunking scanner can be used for this. Some handle multi-path distortion better than others, and how you adapt your scanner programing to fit this situation is up to you. However, so far it has been shown that the above works on radios as varied as a Uniden BC796D to the HP-1 and a Pro-96 to the PSR800. The key is to remember that monitoring the HPD/HFD Phase 1 simulcast transmissions needs to be considered as a separate operation from any other operation your scanner might be tasked with.<br />
<br />
<br />
Return to [[Texas Wide Area Radio Network (TxWARN) Project 25]] page.<br />
<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Texas_Wide_Area_Radio_Network_(TxWARN)_(P25)&diff=115608Texas Wide Area Radio Network (TxWARN) (P25)2013-05-17T18:48:07Z<p>Loumaag: Added a link to a new article on Houston PD/FD communications and monitoring thereof</p>
<hr />
<div>This is the wiki collaboration page for the [http://www.radioreference.com/apps/db/?sid=4563 Texas Wide Area Radio Network (TxWARN) Project 25] trunked radio system. The [[Texas Wide Area Radio Network (TxWARN) Motorola]] trunked radio system is the older analog version of this system. Talkgroups on the system are linked to facilitate migration from analog to digital radios.<br />
<br />
==Former Names==<br />
This system has been known by other names in the past:<br />
* Harris County Regional Radio System (HCRRS)<br />
* Southeast Texas Area Radio Network (STAR-Net)<br />
<br />
==Radio IDs==<br />
MCSO (Montgomery County Sheriff's Office)<br />
* 56294 MCSO Dispatch<br />
* 56295 MCSO Dispatch<br />
* 56296 MCSO Dispatch<br />
* 56297 MCSO Dispatch<br />
* 56298 MCSO Dispatch<br />
<br />
Matagorda County<br />
<br />
* 44170 Sheriff Dispatch<br />
* 40820 Bay City EMS Dispatch<br />
<br />
Walker County <br />
* 51107 EMS Dispatch<br />
* 51108 EMS Dispatch<br />
* 51070 Fire Dispatch<br />
* 31976 Sheriff Dispatch<br />
<br />
City of Huntsville<br />
* 51079 Dispatch<br />
* 51080 Dispatch<br />
* 51081 Dispatch<br />
<br />
Sam Houston State University<br />
* 1012 Police Dispatch<br />
<br />
Wharton County<br />
* 44175 Sheriff Dispatch<br />
<br />
City of Wharton<br />
* 46070 Police Dispatch<br />
<br />
Austin County<br />
* 41145 County Dispatch<br />
* 8369 County Dispatch<br />
* 8320 Medic 1<br />
* 8199 Medic 1<br />
* 8219 Medic 2<br />
* 19610 Medic 2<br />
* 8357 EMS 1<br />
* 8192 EMS 1<br />
<br />
College Station<br />
* 71371 Dispatch<br />
* 71372 Dispatch<br />
<br />
City of Tomball<br />
* 39415 Dispatch<br />
<br />
==Houston Public Safety==<br />
Recently the City of Houston moved their Police and Fire communications to this system using P25 Phase 2 and as a result there has been much confusion and many questions on how one could continue to monitor these agencies. The the article [[Houston Police and Fire P25]] is an attempt to aid those seeking this information.<br />
<br />
==Related Links==<br />
* [http://www.hctx.net/itc/trsradio/ Harris County Information Technology Center] - This is the agency that controls and coordinates this system.<br />
* [http://freqzone.home.comcast.net/~freqzone/freqs/Regional.xls Regional Radio System] (Excel) - KG5AI's talkgroup list<br />
<br />
[[Category:Texas]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=User:Loumaag&diff=115606User:Loumaag2013-05-17T16:58:26Z<p>Loumaag: </p>
<hr />
<div>Scratch page for me<br />
<br />
Houston Police and Fire P25<br />
<br />
The Houston Police (HPD) and Houston Fire (HFD) departments have made the switch to digital TDMA technology. <br />
<br />
== Overview ==<br />
In April and May of 2013 the Houston Fire department and then the Houston Police department abandoned the use of their respective legacy UHF analog conventional systems and moved to the [http://www.radioreference.com/apps/db/?sid=4563 TxWARN P25] system. This move, in addition to moving from an analog conventional system to a digital trunking system caused problems since HPD and HFD are using P25 Phase 2 technology. <br />
<br />
The City of Houston recognized that this move would cause problems for various interest that monitor those agencies and as a partial aid to those interests, including the scanner hobbyist, the dispatch channels for HPD and the main dispatch channel as well as 4 regional channels for HFD are being simulcast on P25 Phase 1 talk groups, allowing for normal P25 trunking capable scanners to monitor those channels. <br />
<br />
== Details ==<br />
In addition to the move to P25 Phase 2 technology, both HPD and HFD are making extensive use of encryption on all tactical (Tac) and talk around (TAC) channels. The reasoning for this is not within the scope of this discussion; however, it should be noted that their decision to leave non Tac and TAC channel in the clear is to everyone's advantage. As this article is being prepared, there is only one scanner available (the GRE PSR800) that is capable of monitoring P25 Phase 2 channels, and that unit is no longer in production. <br />
<br />
This brings this discussion to the simulcast of the dispatch channels and regional channels (for HFD) in P25 Phase 1 technology and how that can be implemented in a normal P25 trunking scanner. <br />
<br />
=== Specific Talk Groups ===<br />
The HPD has identified 12 channels and HFD has 5 to rebroadcast in P25 Phase 1, they refer to these as Mutual Aid channels as any authorized user can access these to communicate with them:<br />
<br />
* HPD -- These cover the basic 12 dispatch / common use channels they had on the legacy analog conventional system minus the old car to car channel (Channel 8) which is not available any longer<br />
** TG 30180 - HPD North MA -- North Dispatch; also known as North Shepard<br />
** TG 30181 - HPD NEast MA -- North East Dispatch; also know as Kingwood<br />
** TG 30182 - HPD SEast MA -- South East Dispatch<br />
** TG 30183 - HPD SWest MA -- South West Dispatch; also known as Beechnut<br />
** TG 30184 - HPD Cntrl MA -- Central Dispatch<br />
** TG 30185 - HPD SCtrl MA -- South Central Dispatch<br />
** TG 30186 - HPD NWest MA -- North West Dispatch<br />
** TG 30187 - HPD West MA -- West Dispatch; also known as Westside<br />
** TG 30188 - HPD Sp Op MA -- Special Operations Dispatch; traffic dispatch; used to be Channel 7 on the legacy lineup<br />
** TG 30189 - HPD Detct MA -- Detective Dispatch; hasn't been used for detectives for a long time; used to be Channel 10 on the legacy lineup <br />
** TG 30190 - HPD CtyWd MA -- Citywide Dispatch; a common use dispatch monitored channel used for wide events<br />
** TG 30191 - HPD AIrprtMA -- Airports Dispatch; common use for airports around the city<br />
<br />
* HFD -- These cover the dispatch channel and four quadrant regional channels. The Tac channels that were previously used are no longer available, even as direct equivalents to the legacy analog conventional channels and all Tac channels are encrypted in any case. <br />
** TG 40002 - HFD Disp MA -- Robot dispatcher, backed up by live dispatcher who can be contacted and occasionally calls individual units on this talk group<br />
** TG 40018 - HFD NE RO MA -- North East Regional Operator - This and the following three channels are used for communication back to dispatch office on a regional basis. They have not, so far been used in working a fire; although, responding units occasionally will ask questions or receive direction on these. <br />
** TG 40038 - HFD SE RO MA -- South East Regional Operator<br />
** TG 40058 - HFD NW RO MA -- North West Regional Operator<br />
** TG 40078 - HFD SW RO MA -- South West Regional Operator<br />
<br />
* Other -- There is at least one more P25 Phase 1 channel available at this time, although of limited interest<br />
** TG 45191 - Hou Parking1 -- Houston Parking Enforcement channel<br />
<br />
=== Specific Site ===<br />
To receive the above talk groups, a scanner must be programmed with a specific site and, depending on your scanner's make up, as a separate system. <br />
<site>18743|19576</site></div>Loumaaghttps://wiki.radioreference.com/index.php?title=PSR-800&diff=112245PSR-8002013-02-14T04:24:09Z<p>Loumaag: /* RR System Compatibility */</p>
<hr />
<div>'''GRE COM PSR-800 scanning receiver'''<br />
<br />
[[Image:PSR-800LG.jpg|right|thumb]]<br />
<br />
The PSR-800 is manufactured by GRE in China.<br />
<br />
==General Specifications==<br />
* A brochure for the PSR-800 can be downloaded here: [http://www.greamerica.com/download/specs/PSR-800.pdf PSR-800 Brochure].<br />
* [[Rebanding]] supported? {{Color|Green|YES}} EZ-Scan will import tables for identified rebanded systems from the RadioReference database.<br />
* USB 2.0 Compliant Interface built in. <br />
*Dimensions approximately 5 5/16 x 2 1/8” x 1 1/16” (135 x 67 x 28 mm) (HWD).<br />
*Weight approximately 7.4 oz. (210g) without accessories and batteries.<br />
*BNC connector.<br />
*Operating voltage<br />
**DC 4.8 Volts (“AA” cell x 4pcs. Ni-MH Batteries).<br />
**DC 6 Volts (“AA” cell x 4pcs. ALKALINE Batteries).<br />
**Ext. power and charge voltage USB Power (DC 5V 500mA).<br />
** If batteries and the power cable are removed for more than ~1 minute, the clock and time will need to be reset by hand or through the software.<br />
<br />
<br><br />
{|border=1<br />
|+'''Frequency Coverage'''<br />
|-<br />
!Freq.<br />
!Step<br />
!Mode (Default)<br />
|-<br />
|25.0000 − 26.9600 MHz<br />
|10 kHz <br />
|AM<br />
|-<br />
|26.9650 − 27.4050 MHz<br />
|10 kHz<br />
|AM<br />
|-<br />
|27.4100 − 29.5050 MHz<br />
|5 kHz<br />
|AM<br />
|-<br />
|29.5100 − 29.7000 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|29.7100 − 49.8300 MHz<br />
|10 kHz<br />
|FM<br />
|-<br />
|49.8350 − 54.0000 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|108.000 − 136.9916 MHz<br />
|8.33 kHz<br />
|AM<br />
|-<br />
|137.000 − 137.995 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|138.000 − 143.9875 MHz<br />
|12.5 kHz<br />
|AM<br />
|-<br />
|144.000 − 147.9950 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|148.000 − 150.7875 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|150.800 − 150.8450 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|150.8525 − 154.4975 MHz<br />
|7.5 kHz<br />
|FM<br />
|-<br />
|154.5150 − 154.6400 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|154.6500 − 156.2550 MHz<br />
|7.5 kHz<br />
|FM<br />
|-<br />
|156.2750 − 157.4500 MHz<br />
|25 kHz<br />
|FM<br />
|-<br />
|157.4700 − 161.5725 MHz<br />
|7.5 kHz<br />
|FM<br />
|-<br />
|161.6000 − 161.9750 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|162.0000 − 174.0000 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|216.0025 − 219.9975 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|220.0000 − 224.9950 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|225.0000 − 379.999375 MHz<br />
|6.25 kHz<br />
|AM<br />
|-<br />
|380.0000 − 419.987500 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|420.0000 − 450.000000 MHz<br />
|5 kHz<br />
|FM<br />
|-<br />
|450.00625 − 469.99375 MHz<br />
|6.25 kHz<br />
|FM<br />
|-<br />
|470.00000 − 512.00000 MHz<br />
|6.25 kHz<br />
|FM<br />
|-<br />
|764.00000 − 781.996875 MHz<br />
|3.125 kHz<br />
|FM<br />
|-<br />
|791.00000 − 796.996875 MHz<br />
|3.125 kHz<br />
|FM<br />
|-<br />
|806.00000 − 823.987500 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|849.00000 − 868.987500 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|894.00000 − 939.987500 MHz<br />
|12.5 kHz<br />
|FM<br />
|-<br />
|940.00000 − 960.000000 MHz<br />
|6.25 kHz<br />
|FM<br />
|-<br />
|1240.0000 − 1300.00000 MHz<br />
|6.25 kHz<br />
|FM<br />
|-<br />
|137.0000 − 174.0000 MHz<br />
|5 kHz<br />
|FM (Canada)<br />
|-<br />
|380.00000 − 512.00000 MHz<br />
|12.5 kHz<br />
|FM (Canada)<br />
|}<br />
<br />
<br />
* [http://en.wikipedia.org/wiki/Object_oriented Object oriented memory management]. See the [[Object Oriented Scanning Described]] article for more information.<br />
* Object capacity (Nominal, with 2 GB MicroSD Card): > 10 million, varies depending on user configuration.<br />
* Location-based Scanning - allows you to enter your zip code, city, or county to select channels to scan in the US (only).<br />
* 201 Scan Lists; 200 regular lists and a SkyWarn list.<br />
* 20 Scan Sets; create a set of scan lists tailored to your favorite scan list settings.<br />
* 200 V-Folders with second generation Virtual Scanner Memory Management system. One copy of working memory can hold a virtual numbers of objects, meaning any combination of talkgroups, conventional channels, and trunking systems. Each V-Scanner II folder holds one copy of working memory. Actual memory size is determined by the size of the microSD card memory size used. <br />
* Preprogrammed with all systems currently in the Radioreference database with ability to update as needed or once a week.<br />
* 4 way navigation keys to access special modes and programming options emulating today's standard media player operation.<br />
* Easy-to-read back lit control and display with back lit keypad with user selectable settings.<br />
* [[Spectrum Sweeper]] Near field frequency capture.<br />
* Tri-color alert LED - Object programmable; eight factory default colors to any color / brilliance you want by having direct access to the R-G-B drive values (including flash) to assign to talkgroups, frequencies, agencies, etc. Example settings are shown in the owners manual.<br />
** LATCH option; the color of the last received object stays on until reset.<br />
* Programmable Backlight Flash Patterns - The backlight can be programmed to flash with custom flash patterns when certain objects are active, providing another way alerting the operator when important radio traffic is present.<br />
* Audible Alarms - programmable audible alerts can be configured when certain objects are active.<br />
* Autoboost (software only) - available for conventional frequencies, IDs, and entire trunked systems, boosts the audio levels slightly louder.<br />
* Recording / playback of objects or all received audio at a set volume unchanged by the volume control.<br />
** Audio codec is AU format and is time/date stamped at the header file of the audio sample.<br />
** AU audio files can be played via Windows Media Player, WinAmp, and other players.<br />
** Additional information such as frequency, TGID, etc. can be see using the included software.<br />
* Priority Scan - the scanner will sample conventional objects for activity periodically while scanning and monitoring other objects. The scanner will also give IDs priority over other IDs while checking a particular trunking system for activity.<br />
* Clock display while "off" (and connected to external power).<br />
* Auto power-on ("alarm clock").<br />
* Power-on password.<br />
* Scan rate 70 CPS (without trunk scan).<br />
* Search speed 80 CPS.<br />
* Adaptive digital tracking (ADT).<br />
* Digital signal processing (DSP).<br />
* Triple conversion.<br />
* [[Continuous Tone-Coded Squelch System|CTCSS]]/[[DCS]] abilities.<br />
* [[NAC|Network Access Code]] can be programmed to only break squelch when receiving the correct NAC in a conventional P25 system.<br />
* 16-character alpha-tagging with text entry can show ID code or service name set per the users preference.<br />
* Signal strength meter.<br />
* 700MHz and 380MHz trunk scanning.<br />
* Multi-site trunking.<br />
* Trunking option to look for the site with the best received CC decode rate (not the same as RSSI on the Motorola rigs, but similar in operation}.<br />
* Motorola [[Control Channel Only]] trunking.<br />
* Private Calls and RadioID display in decimal or hex.<br />
** Note: If RadioID is greater than 9,999,999 (decimal), then HEX is displayed to fit in the 16 character display.<br />
* EDACS and Motorola TGID Patch (when used on system), currently in the HEX display format only.<br />
* Regular LTR trunking with auto-arrange for LCN.<br />
* Selectable digital [[AGC]].<br />
* FlexStep - allows you to enter a frequency in any 1.250 MHz step.<br />
* 20 dB [[attenuator]] global and per object settings.<br />
* 7 service search ranges/ 1 user definable search range tunes virtually all important bands; marine, fire/police, Ham, CB, VHF-air, UHF-Air, and racing.<br />
* Zeromatic search tuning.<br />
* Weather band with enhanced [[SAME]] Weather Alert functions and weather priority—access weather channels and alerts with the push of a button.<br />
* Skywarn List can be programmed with any number of "objects".<br />
* Built in IF discriminator data output can be enabled to the headphone jack and can be used with [http://wiki.radioreference.com/index.php/Unitrunker UniTrunker], [http://groups.yahoo.com/group/TRUNK88 Trunk88], and [http://www.thebriarpatch.org/treport/ Treport] decoders with a standard stereo audio patch cord. <br />
* Built in discriminator data output in simple ASCII output using the PC/IF port can be sent to a com port or internal microSD card.<br />
* The PSR-800 uses a true USB interface. The 800 uses a logical device and installs drivers for both the radio and the microSD card.<br />
** Please see the [[Connecting scanners via USB]] article for USB cables to connect your PC to the scanner.<br />
* Advanced encryption handling:<br />
**EncMode selects how the radio treats encrypted voice calls. Simple Display must be unchecked.<br />
**“Noise” setting plays the random undecoded encryption noise. Simple Display must be unchecked.<br />
**“Silent” setting plays no audio during the call. Simple Display must be unchecked.<br />
**“Tone” setting plays a soft tone for the duration of the call. Simple Display must be unchecked.<br />
**EncLevel selects the tone level for tones played during encrypted calls<br />
*Advanced conventional P25 systems:<br />
**CONV TGID When enabled, shows the Talkgroup ID for P25 Conventional Talkgroup calls. Simple Display must be unchecked.<br />
**CONV Radio ID when enabled, shows the Radio ID for P25 conventional calls. Simple Display must be unchecked.<br />
* 2 second default delay can be set from 0 to 60 sec.<br />
*Skip or Lockout - lets you skip ''or'' permanently lockout any programmed object. All skipped objects can be restored (unskipped).<br />
* 250 Search lockouts.<br />
* Low Battery Alert - with customizable battery icon threshold values for NiMH and alkaline batteries.<br />
* Default Options Key; return to default settings for any menu.<br />
<br />
<br />
==Features found on the PSR-800 '''Not''' included on the RadioShack Pro-18==<br />
These are the features that the PSR-800 has above the PRO-18:<br />
* X2 TDMA and P25 Phase II 2 slot TDMA ('''Note: ''' Firmware/DSP Upgrades are required)<br />
* Recording / playback<br />
* 201 scan lists (PRO-18 has 100 play lists)<br />
* Tri-color alert LED<br />
* Discriminator output<br />
* V-Scanner II<br />
* Scan Sets<br />
* Clock display while "off" (and connected to external power)<br />
* Auto power-on ("alarm clock")<br />
* "Extra" audio alert tones (PRO-18 has the 7 from PSR-500; PSR-800 has 8 more)<br />
* Power-on password<br />
<br />
==Operating Tips==<br />
===Scan Sets Feature===<br />
*There are 20 Scan Sets. Scan Sets you let you quickly select large groups of Scanlists to enable or disable just by enabling or disabling the Scan Sets that contain the Scan Lists instead of individually selecting each group of Scanlists.<br />
<br />
*The Scan Sets feature is geared toward people who have lots of different things (where "different" is based on geography, agency, usage, etc.) they want to monitor, and want a somewhat easier method of choosing what to monitor than the default toggling of individual Scan Lists.<br />
<br />
*Firmware version 1.6 added "ScanSets Opt" setting. If enabled (checked), Scan Sets alone govern whether a scan list is scanned and the master Scan List enable array is ignored.<br />
<br />
*In order to be "scanned", an object (talkgroup or conventional channel) must:<br />
** a) be a member of at least one enabled Scan List, where that Scan List<br />
** b) is a member of at least one enabled Scan Set<br />
** By default:<br />
***Scan List 001 is enabled, all others are disabled<br />
***Scan Set 01 contains all 200 Scan Lists, all other Scan Sets are empty<br />
***Scan Set 01 is enabled, all other Scan Sets are disabled<br />
** These defaults effectively make the Scan Sets feature transparent. Since Scan Set 01 is enabled and contains all 200 Scan Lists, condition (b) above is always satisfied: you can completely ignore the Scan Sets feature, and just use Scan Lists like you might on a PSR-500, PSR-310, PSR-700.<br />
** The default settings are geared toward the [presumed] majority of users, who will only have a few Scan Lists they want to monitor or toggle. Those users can control what they hear by just toggling a few Scan Lists on or off.<br />
** For more "advanced" users, who might have many areas or agencies they want to split among many Scan Lists but who might have a few "common listening setups" (certain unique groups of Scan Lists they commonly monitor), toggling 200 Scan Lists might be cumbersome. The Scan Sets are intended to help with that.<br />
** Example:<br />
** City PD and FD, county Sheriff, and CHP. A generic example, though, might be something like this:<br />
*** 10 cities, each with their own PD and FD<br />
*** specific channels/talkgroups for PD and FD dispatch<br />
*** 40 Scan Lists: <10 cities> x <PD vs. FD> x <dispatch vs. "everything else"><br />
*** All 40 Scan Lists enabled<br />
*** Scan Sets for things like:<br />
*** All cities' PD dispatch<br />
*** City #1 Fire (both dispatch and "everything else")<br />
*** City #2 PD (both dispatch and "everything else")<br />
*** City #1 and City #2 PD, dispatch only<br />
*** City #1, City #3, and City #4, all PD and all Fire<br />
***Toggling Scan Sets on/off can enable/disable such "groupings" much more easily than going through 40 Scan Lists<br />
<br />
<br />
===Setting Up a System for Rebanding===<br />
#Select the system<br />
#Select the site<br />
#Bring up the trunking tables for the system<br />
#Set it from '''Auto-fill''' to '''Custom'''<br />
#Hit the '''Set Reband''' button<br />
#Load the new configuration to the scanner<br />
<small>Thanks to Troymail for the procedure</small><br />
<br />
==RR System Compatibility==<br />
This scanner is compatible with the following Trunking System Types and System Voices used in the RadioReference Database, of course you must verify that the scanner will cover the appropriate frequency range:<br />
* System Types:<br />
** Motorola Type I<br />
** Motorola Type II<br />
** Motorola Type IIi Hybrid<br />
** Motorola Type II Smartnet<br />
** Motorola Type II Smartzone<br />
** Motorola Type II Smartzone Omnilink<br />
** EDACS Standard (Wide)<br />
** EDACS Standard Networked<br />
** EDACS Narrowband (Narrow)<br />
** EDACS Narrowband Networked<br />
** EDACS SCAT<br />
** EDACS ESK (not ProVoice)<br />
** LTR Standard<br />
** Project 25 Standard<br />
** X2 TDMA <br />
** Project 25, 2 slot Phase II (2 slot TDMA only; 4 slot is not supported)<br />
<br />
*System Voices:<br />
** Analog<br />
** Analog and APCO-25 Common Air Interface<br />
** APCO-25 Common Air Interface Exclusive<br />
** APCO-25 Phase II TDMA<br />
<br />
==Included Accessories==<br />
* 5" 09080 Rubber Antenna<br />
* A standard USB A to USB Mini-B cable (No PC/IF converter cable needed)<br />
* 2GB MicroSD Card (Inside The Scanner)<br />
* Rotatable Belt Clip<br />
* CD-Rom (EZ Scan Digital Software Utility Program)<br />
<br />
==Recommended accessories (Not included with the radio)==<br />
* [http://www.radioshack.com/product/index.jsp?productId=2102525 RS #20-283 Radio Shack 800MHz handheld antenna]<br />
* [http://www.radioshack.com/product/index.jsp?productId=4385738&kw=4385738&sr=1&origkw=4385738 4385738 USB power adapter]<br />
* [http://www.radioshack.com/product/index.jsp?productId=2963871 Car USB power adapter]<br />
* [http://www.radioshack.com/product/index.jsp?productId=3118203 Digital Concepts™ SD Memory Card Converter Drive]<br />
* [http://www.radioshack.com/product/index.jsp?productId=10951240 MicroSD to SD card adapter]<br />
<br />
==FCC Type Acceptance==<br />
* [http://tinyurl.com/48yekeb FCC Type Acceptance: ADV0602902]<br />
<br />
==Related Pages==<br />
* [[Programming Your GRE Scanner]]<br />
*[http://forums.radioreference.com/gre-scanners/203998-psr-800-multi-site-trunked-system-poll.html PSR-800 Multi-Site Trunked System Poll]<br />
*[http://n9ewo.angelfire.com/psr800.html Dave N9EWO's Review on the PSR-800]<br />
<br />
==Yahoo Groups and Mailing Lists (receiver support)==<br />
* [http://groups.yahoo.com/group/PSR-800 PSR-800 Yahoo Group]<br />
* [http://www.radioreference.com/forums/forumdisplay.php?f=117 RadioReference GRE forum]<br />
<br />
==eBay Listings== <br />
<br />
<ebay>GRE ("PSR-800","PSR800")</ebay><br />
<br />
Return to the [[GRE Radios]] page<br />
<br />
[[Category:Trunking Scanners]]<br />
[[Category:Handheld Scanners]]<br />
[[Category:Digital Scanners]]<br />
[[Category:Object Oriented Scanners]]<br />
[[Category:Rebanding Supported Scanners]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Trunking_Basics&diff=101987Trunking Basics2012-11-17T15:31:39Z<p>Loumaag: Moving the "Short Version" to the bottom as it completely disrupted the flow of the page</p>
<hr />
<div>== Early attempts at spectrum management ==<br />
<br />
=== Repeaters ===<br />
To understand trunking, one must first understand the concept of [[repeater]] operation. Straight repeater operation isn't especially complicated: place a remotely controlled receiver and transmitter on a high point somewhere in the area. The repeater receives all the signals transmitted on one frequency known as the input frequency (call this channel "A") and takes what it hears and retransmits it on another frequency known as the output frequency (call this channel "B") at the same time. All mobile and base stations listen on channel "B" and transmit on channel "A." <br />
<br />
This system allows units across a wide area to communicate with each other via the repeater (called a mobile relay by the [[FCC]]). <br />
<br />
=== Tone-controlled access ===<br />
The first way interference was solved was by the use of [[CTCSS]] or [[DCS]] (more commonly called PL or DPL tones). These are subaudible (and in the case of DCS, digitally encoded) signals sent out along with the radio signal carrying the voice transmission. Radio receivers are set to only open squelch when a specific CTCSS or DCS is detected. This meant, for example, that two counties near each other could use the same frequency (for example, 155.25 [[MHz]]) with different tones and would not normally interfere with each other. One organization could be using 155.25 MHz with a CTCSS tone of 114.8 [[Hz]] and in the next county over, another organization could be using 155.25 MHz with a CTCSS tone of 110.9 Hz and for the most part they would not hear each other. <br />
<br />
CTCSS, of course, does not actually keep stations in different nets from interfering with one another ''if they transmit at the same time'', but at least one net's users won't open the other net's repeater.<br />
<br />
== Trunking ==<br />
While the use of CTCSS and DCS proved to be a good solution for a while, [[spectrum]] crowding, especially in urban areas, overwhelmed such solutions, and eventually led to the development of [[trunked radio systems]]. Trunking is the use of several repeaters, on different frequencies in the same band, operating together under computer control to allow the pooling of resources for several agencies. A presentation on the basics of trunked radios systems was done at Defcon 15 and a video of that presentation is available [http://video.google.com/videoplay?docid=2933067560876937617&hl=en here].<br />
<br />
The trunking radio, in a patrol car for example, is much more sophisticated than the simple [[transceiver]] previously used in a [[simplex]] or [[repeater]] configuration. A [[trunking]] transceiver is a microprocessor-controlled radio capable of receiving instructions from the system controller and changing frequencies on the fly. All trunked radios operate in a similar manner although the type of trunking technology used by each type of trunked radio system differs greatly.<br />
<br />
In the trunked radio environment, each agency is assigned one or more [[talkgroups]] that the agency's communications will use. All agencies on the system will have different talkgroups but all will share the same pool of frequencies. For simplicity I will use an example of a [[control channel]]-based type of trunked radio system as an example. (Some trunking systems don't use a dedicated control channel.) In this type of system, all the radios on the system (except the computer controlled set of repeaters, of course) listen to a common control channel (CCh) output frequency and transmit (initially) on a common control channel input frequency, unless they are listening to a conversation on a talkgroup. <br />
<br />
Let's say that Patrolman Bob (from Smalltown Police Department) wants to tell the dispatch office that he is now in service. The following actions take place in a very short time--much less time than it takes you to read this. <br />
<br />
*He picks up his microphone and keys the mike, his radio sends a signal on the CCh input frequency, which the controlling computer understands as a request for a channel grant for the talkgroup assigned to Smalltown Police.<br />
*His radio then instantly goes back into receive mode, ''while he's still holding down the PTT switch''. The computer looks at the system for an empty channel pair and issues that channel grant on a specific channel pair and sends that channel grant information out on the CCh output channel. This channel grant information tells all radios on the system: "if you are listening (monitoring) for communications on the Smalltown Police talkgroup: change to channel pair XX on the system for a communication". <br />
*All radios tuned to Smalltown Police's talkgroup, including Patrolman Bob's, then switch frequencies to that channel pair granted by the computer. <br />
*Patrolman Bob's radio, after changing frequencies, goes into transmit mode and he can start to talk. Generally, the radio will generate a "talk-permit tone" to tell him that it has tuned to a channel, and is now in transmit mode.* As he talks, all the radios monitoring the Smalltown Police's talkgroup are now listening on the assigned repeater output channel and are ready to talk on the assigned repeater input channel. This continues until Patrolman Bob has finished his transmission. On some types of systems, further communication may be on the initially assigned channel pair or it may move to another, but the process stays the same.<br />
<br />
[ *If you think this sounds similar to the Nextel chirp, it is: Nextel (iDEN) is essentially a digital trunking radio system licensed as Specialized Mobile Radio -- they bought up lots of licenses in that non-cellular band Way Back When. ]<br />
<br />
A trunk-tracking scanner is designed to follow those same instructions (except, of course, it ignores the instructions relative to the input side of the repeater pair) so that it will also follow the conversations by changing frequency to the appropriate repeater output frequency. Each type of trunked radio system operates a little differently, and some cannot be monitored by current trunk-tracking scanners at all. <br />
<br />
Please take a look at detail information in regard to the type of system that you are attempting to monitor and the instructions that come with your scanner in regard to that type of system.<br />
<br />
==Networked Systems==<br />
A trunking system that uses more than one site is either a multi-cast (sometimes referred to as [[simulcast]]) system covering a larger but restricted area, like a mid-sized city; or a networked system. A multi-cast system could also be part of a larger networked system. <br />
<br />
Networked systems typically are made up of a trunked system that uses control channels as opposed to a [[LTR]] type system. The reason this is important to you the scanner user is that you must accommodate the use of multiple control channels in your scanner programming. For the purposes of this discussion on networking, we will only consider those systems that use control channels to manage usage (as described in the above section.) Also, in networked systems that also have multi-cast systems, consider the multi-cast system as a single site within the network.<br />
<br />
===Affiliation===<br />
An important concept to understand with networked systems is '''affiliation'''. Affiliation is what happens when a specific subscriber's radio is using a specific site to communicate with the trunked system; it "checks in", and this causes talkgroup traffic for the talkgroup to which that radio is "tuned" to appear on that particular site/tower.<br />
<br />
To explain this further let us consider a very large system, say a statewide system. Using our example above, let's consider that Smalltown has a local site on the statewide system. Normally all the traffic for Smalltown PD would probably be carried on the Smalltown tower. If patrolman Bob had to take a prisoner to a detention facility in Big City then as he traveled from Smalltown toward Big City he probably would leave the range of the Smalltown site and pass into other towers' range as he travelled. <br />
<br />
Assuming he kept his radio tuned to the Smalltown Dispatch channel as he travelled, into the range of each site, his radio would automatically affiliate with the closest (or strongest) site and unaffiliate from the site he previously was on. This means that as patrolman Bob travels, he is causing the Smalltown Dispatch channel to be able to be heard (by anyone who's selected it) on each site as he affiliates with it. <br />
<br />
This is important to you, the scanner user, because you are using a passive device to listen to this trunking network. You cannot force traffic from a desired talkgroup to appear on the site that you can hear, because you don't actively communicate on the system. You must rely on actual subscribers to cause desired traffic to appear on the site you are listening to.<br />
<br />
This concept affects you in two ways and both are best presented by examples. <br />
* Say you grew up in Smalltown and would like to hear it to keep up with what is going on, but you moved to Big City for a job. Unless patrolman Bob (or someone else) comes to Big City and keeps his radio tuned to Smalltown Dispatch, you will never hear it because no one in Big City has a radio affiliated with the Smalltown Dispatch talkgroup on the Big City site, and therefore, the system controller doesn't '''send''' the Smalltown Dispatch audio to your tower.<br />
* Say you are listening to a couple of state policeman who are doing some surveillance many miles away and they are communicating on the regular dispatch channel for the local state police station. They can be heard, even though they are not affiliated on the local site, because the local state police station's radio is affiliated with the dispatch channel. If the two state policemen (who are affiliated with some other site you can't normally hear) decide to switch channels to a TAC (talk around channel) that no one in your area has tuned, then you will lose the conversation because it will not be carried on the local site.<br />
<br />
These two circumstances are why you, the scanner user, should try and set up as many sites as you can hear in your scanner. And if you are traveling, program all the sites that you will come within range of on your trip. The actual programming of many sites within specific trunking systems becomes too complicated to discuss in this basic article. It depends on your scanner and the type of system you are attempting to monitor, so once again take a look at detailed information in regard to the type of system that you are attempting to monitor and the instructions that come with your scanner in regard to that type of system.<br />
<br />
==The Technical Jargon==<br />
'''[[Trunked Radio Systems]]''' share a small pool of frequencies among a large number of users. They can do this because communications are typically less than 5 seconds long, and a particular channel might be busy less than 5% of the time. System users are assigned to "talk groups" which function as virtual channels. When a user makes a call, the radio transmits a unique radio ID number and current talk group ID and a request for a radio channel (frequency pair) to the computer which controls the trunking system.<br />
<br />
The controller then sends out a “channel grant” specifying which frequency pair to use, and telling every other radio in that user group to also switch to that frequency pair for the duration of the transmission. When the user stops transmitting, the assigned frequency pair is released so that it is available for the next group to use, which can be any other users of the system. On a trunking radio, a “channel” is not a specific frequency pair, but instead determines the affiliation of that radio with a talk group assigned to a particular group of users on the system.<br />
<br />
The benefit of this technology to the agencies is that many more virtual channels are available for specialized traffic than there are frequencies. For example, the Fort Worth trunked system has only 20 frequencies, but services over 400 talkgroups. All radio channels in a trunking system are repeaters, so system traffic can be widely heard.<br />
<br />
The down side for scanner users is that, because a new frequency is assigned every time a user keys his radio, an exchange of communications can occur across several different system frequencies. If you just program the RF frequencies for your local trunking system directly into your scanner channels, you’ll get a mix of all the users on the system and have a very difficult time hearing any one particular communications exchange.<br />
<br />
Trunk Tracking lets a scanner monitor the system's digital [[control channel]], so it can watch for the channel assignments and follow individual communications (or scan for communications of interest) on such systems.<br />
<br />
==The Short Version==<br />
<br />
=== DickH's easy-to-read Motorola trunking explanation ===<br />
All credit for this goes to DickH (Note. You should still read the information above this, because this is a condensed explanation)<br />
<br />
Motorola Trunking:<br />
The object of trunking is to allow many users to share a relatively few frequencies.<br />
A trunking system is controlled by a computer. Information (data) is exchanged between the system radios and the computer on a control channel, sometimes called a data channel. It sounds like a strong buzz.<br />
A large system can have up to 28 freqs., 4 of which may be used as control channels. The control channel may be changed once a day or as often as the programmer decides. Some scanners need only the control channels to track an entire system. Just put in the 4 Control Channels.<br />
<br />
Each group of users (Fire, Police, etc.) is assigned TALK GROUPS. In a Motorola Type II system, the most common type, TGs are usually in 32 number steps starting with 16 and going up to 65536; 16, 48, 80 --- 4656, 4688, 4720 --- 28944, 28976, etc. System radios can have more than 100 TGs programmed into them.<br />
<br />
How it works<br />
When a user pushes the talk button on his radio, data is sent to the computer. The computer chooses an unused freq. and sends that data to all the radios that are set to the TG of the originating unit. This all happens in a fraction of a second and it happens EVERY TIME a radio is used.<br />
<br />
EXAMPLE:<br />
<br />
Fire Dispatch calling Engine 4 (TG 4528 on 856.7125)<br />
<br />
Engine 4 answering Dispatch (TG 4528 on 852.2625) <br />
<br />
Respond to 73 Elm Street (TG 4528 on 855.9625)<br />
<br />
Engine 4 responding (TG 4528 on 851.6375)<br />
<br />
<br />
If you have entered TG 4528 into your scanner, it will read the control channel data and change your scanner freqs. to follow the conversation on TG 4528. .<br />
<br />
<br />
[[Category: RR Glossary]]<br />
[[Category: FAQ]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Wabash_County_(IL)&diff=94070Wabash County (IL)2012-06-11T15:05:51Z<p>Loumaag: /* Wiki Articles */</p>
<hr />
<div>==Wiki Articles==<br />
* [[Businesses Wabash County (IL)]]<br />
<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Wabash_County_(IL)&diff=94069Wabash County (IL)2012-06-11T15:05:30Z<p>Loumaag: Linking an orphan page</p>
<hr />
<div>==Wiki Articles==<br />
* [[Businesses Wabash County (IL)\\<br />
<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=La_Salle_County_(IL)&diff=94068La Salle County (IL)2012-06-11T14:59:38Z<p>Loumaag: Adding link to orphaned page</p>
<hr />
<div>==La Salle County==<br />
*[http://lasallecounty.org/ County Website]<br />
===La Salle County Sheriff's Department===<br />
Possible future trunked system:<br />
857.2375, 859.4375, 859.9625, 860.4875<br />
<pre> <br />
458.27500 KSA521 M LaS Shrf MX Sheriff: Mobile Extenders<br />
866.07500 821.07500 WPWC445 RM LaS Jail Ops Sheriff: Jail Operations <br />
868.58750 WPWC445 M LaS Jail MX Sheriff: Mobile Extenders to 866.075 (low power 2.5/3wt)<br />
461.05000 M LkHol Secrty Lake Holiday Security (link to Sheriff 155.7 <br />
823.58750 WPWC445 M LaS Jail M Sheriff: Jail (low power 2.5wt)<br />
</pre><br />
===La Salle County ESDA/Highway===<br />
<pre><br />
453.72500 KAT354 M EMA <br />
453.97500 458.97500 WQL487 RM Highway Department <br />
453.82500 458.82500 WQL485 RB Highway Department <br />
</pre><br />
<br />
==EMS Agencies and Hospitals==<br />
===Community Hospital of Ottawa===<br />
<pre><br />
452.7 457.70 WQBZ866 RM CHO Sec/Ops Security, Maintenance, Medical Staff & Administrative<br />
151.89500 KRV728 BM CHO Ops VHF Hospital Ops [IG - portables]<br />
462.75000 WQIP525 BP CHO Paging Paging [Digital]<br />
</pre><br />
<br />
===Illinois Valley Community Hospital (Peru)=== <br />
<pre><br />
152.31500 157.54500 WQFQ989 RM IVCH Ops 1 Hospital Ops <br />
463.26250 468.26250 KD31913 M IVCH Ops 2 Hospital Ops(LP R? w/ phone patch)<br />
463.82500 468.82500 WPXP448 RM IVCH Ops 3 Hospital Ops <br />
464.97500 KWS479 BM IVCH Ops 4 Hospital Ops / Paging <br />
464.52500 469.52500 WNKI502 RM IVCH Ops 5 Mat Mgmt [Expired 3/03]<br />
155.20500 WNLU472 BM IVCH EMS ? EMS Ops?<br />
</pre><br />
<br />
==Mendota Community Hospital==<br />
<pre><br />
154.60000 M MCH Security Hospital Security<br />
</pre><br />
<br />
==St. Mary's Hospital (Streator)==<br />
3rd Order St Francis<br />
<pre><br />
155.20500 WQCY417 BM EMS (2 Bases) <br />
155.32500 KD4785 M EMS: ? [Exp 8/04] <br />
155.40000 WQCY417 BM MERCI400 Hospital-to-Ambulance Communications <br />
155.28000 WQCY417 BM IDPH -- Statewide Hospital Disaster Channel<br />
462.95000 467.95000 WQCY417 RM Med Repeater<br />
462.97500 467.97500 WQCY417 RM Med Repeater <br />
463.00000 468.00000 WQCY417 BM All Med Channels<br />
152.00750 WQCN834 BP Paging<br />
</pre><br />
<br />
==Municipalities and Districts==<br />
===Dana Fire Protection District===<br />
<pre><br />
453.21250 458.31250 WQFH642 RMP Dana Fire U1 Fire: Operations <br />
154.44500 WQFH642 BM Dana Fire 2 Fire <br />
</pre><br />
<br />
===Cedar Point===<br />
''Fire Unit Numbers''<br />
*1900 Cedar Point Base<br />
*1915 First Response unit<br />
*1916 Tanker<br />
*1912 Mini Pumper<br />
*1911 Engine<br />
*1916 Tanker<br />
<pre><br />
154.44500 WPPZ888 M Fire: Local <br />
154.14500 M Mutual Aid w/ Tonica Ambulance<br />
</pre><br />
<br />
'''Cedar Point Fire Department'''<br />
*154.190 Fire Primary; 154.145 Comms w/ Tonica Ambulance<br />
*150.995 voice paging via a dial access encoder at Standard Fire in Putnam Co. Both Standard and Cedar Point Run Auto Aid to each other on 95% of calls. LaSalle Co pages via this dial access endcoder<br />
<br />
===Dana===<br />
'''Dana Fire Protection District'''<br />
<br />
===Earlville===<br />
'''Earlville Police Department'''<br />
*WQMN325 Future Repeater 155.49 with 158.9475 input<br />
*Units E1-E16 (Dispatched out of Mendota)<br />
'''Earlville Fire Protection District'''<br />
<br />
===Grand Ridge===<br />
'''Grand Ridge Volunteer Fire Department'''<br />
<br />
===La Salle===<br />
<pre><br />
153.86000 KD41948 M LaS PubWorks Public Works <br />
453.08750 WQAM433 M LaS PW WDD 1 Water Distribution Data<br />
451.52500 WPBK247 F LaS PW WDD 2 Water Distribution Data<br />
</pre><br />
<br />
===Leland===<br />
'''Leland Police Department'''<br />
*WQOG681 - mobiles on 154.65 and FX2 on 158.9475 (Earlville repeater input)<br />
*WQEL266 - 155.4975 Repeater with 154.65 mobiles for Public Works/Police (11K)<br />
*Police Units are Lincoln units... L1 - L30 <br />
<br />
'''Leland Community Fire Protection District'''<br />
*Dispatched by MABAS 06, DeKalb County Ambulance: 1M38 (ALS provided by Somonauk Community Emergency Ambulance)<br />
*Fire Units: 200s (201 Chief, 202 Asst, 211 engine, 214 engine, 244, 295 equipment) <br />
<br />
===Lostant===<br />
<pre><br />
154.19000 KFN555 BM CSQ LaSalle Fire Fire: Countywide Fire Dispatch <br />
155.20500 WPKF679 BM Ambulance [Expired 2/02] <br />
</pre><br />
<br />
===Marseilles===<br />
*Police Unit IDs 71,72,73<br />
**Indiviual's IDs M1, M2, M3,ect<br />
*Fire IDs: 500s (Base 509, Chief 501)<br />
<br />
<pre><br />
154.89000 M Mars PD C2C5 Police: Car-to-Car "Code 5" <br />
158.83500 KTO358 BM Mars Streets Street Department <br />
</pre><br />
*New 12/10 - WQNE265 for 154.47125 F for Water Data<br />
'''Marseilles Area Ambulance Service'''<br />
<br />
===Mendota===<br />
155.085 KAT354 M ESDA <br />
154.085 KWH772 BM Mend DPW Street Dept, Water & Sewer, Parks / Police Back-up <br />
154.085 KSD972 BM Mend DPW Street Dept, Water & Sewer, Parks / Police Back-up <br />
<br />
===Millington===<br />
*LaSalle County portion patrolled by LaSalle County Sheriff. Kendall County portion patrolled by Kendall County Sheriff. <br />
*Fire Protection by Millbrook FPD (DB: KENCOM)<br />
<br />
===Naplate===<br />
'''Naplate Volunteer Fire Department'''<br />
<br />
===North Utica===<br />
<pre><br />
155.64000 WQFD730 BM NUtic Police Police FM Law Tac <br />
151.47500 WQFD730 BM NUtic PD New Police: New FM Law Tac <br />
</pre><br />
<br />
===Oglesby===<br />
<pre><br />
155.76000 KWH773 BM Public Works / Police Secondary FM Public Works <br />
155.74500 M Public Works FM Public Works <br />
</pre><br />
<br />
===Ottawa River Rescue===<br />
<pre><br />
155.40000 WQEY377 BM Rescue Ops FM Fire-Tac <br />
</pre><br />
<br />
===Ottawa===<br />
<pre><br />
458.08750 WQDR677 M Otta Alarms Burglar/Fire Alarm: Installation/Monitoring <br />
153.12500 158.41500 RM Otta FD Old Fire: (Old) FM Fire-Tac <br />
154.13000 KSC852 BM Otta FD Loc Fire: Local/Special Operations FM Fire-Tac <br />
155.08500 M Civil Defense / Fire Rescue FM Emergency Ops <br />
155.40000 M Otta River Ottawa River Rescue FM Fire-Tac <br />
155.74500 KSS873 M Otta Str/Swr Street / Sewer Department FM Public Works <br />
453.88750 WPUK535 F Otta Water Water Department: SCADA Short Range Telemetry <br />
</pre><br />
<br />
===Peru===<br />
*[http://perupolice.org/ Police Website]<br />
'''Peru Rescue Station, Inc.'''<br />
'''Peru Fire'''<br />
*was previously listed as:<br />
<pre><br />
F1 153.950 (DPL 114) Dispatch/Fireground (simplex)<br />
F2 154.400 (DPL 114) Fireground (repeats 153.950)<br />
<pre><br />
'''Peru Volunteer Ambulance'''<br />
*KD48741 add 154.7625 Repeater with 153.9875 input<br />
<br />
===Sandwich===<br />
'''Northville Township Road Maintenance (Sandwich)'''<br />
*WQOL367 - 155.595 Base/Mobile (11K)<br />
<br />
===Seneca===<br />
<pre><br />
154.14500 KNEJ802 M Senaca Fire2 Fire: Local <br />
155.10000 KNEN333 BM CSQ Seneca PW Public Works<br />
453.06250 458.06250 WPEA884 M Seneca Water Water Data? (Digital-low power repeater?) <br />
457.72500 WQIA717 F Seneca WDD Water Distribution Data (2wt@2 Locations)<br />
</pre><br />
<br />
===Streator===<br />
<pre><br />
153.81500 KSA736 M Police: Future (input or car-to-car) <br />
155.85000 KSA736 M Police: Car-to-Car (in use, but not 107.2 PL) <br />
155.83500 WNNT228 BM 114.8 PL Public Works - Old (Abandoned)<br />
</pre><br />
<br />
===Utica===<br />
'''Utica Fire Protection District'''<br />
*Dispatched by Oglesby PD/FD<br />
*WQAH471 - add 155.6625 Repeater with 159.03 input 11K<br />
<br />
==Schools==<br />
===LaSalle-Peru Schools===<br />
*[http://lasalleschools.net/ Lasalle Schools Website]<br />
*WQOW433 replace expired WPTE595 153.425 Repeater with 158.205 input (11K)<br />
<br />
===Ottawa Schools===<br />
'''Elementary School District 141'''<br />
'''Township High School District 140'''<br />
<br />
===Tonica School District===<br />
*[http://www.tonicagradeschool.org/ Website]<br />
<br />
<br />
==Codes & Lists==<br />
===LaSalle Co Public Safety Unit Numbers===<br />
Possible Police Unit numbers:<br />
*980 Sheridan?<br />
*981-985 Leland<br />
<br />
'''Dispatched by LaSalle County only on 155.145<br />
*Sheridan 915 (Chief) 916/917/918<br />
*Utica 991 (Chief) 992-K9/993<br />
*Grand Ridge 989<br />
*Naplate 981<br />
*Tonica 982<br />
*Cedar Point 988<br />
*Dalzell 923<br />
*Lostant 984<br />
*Lake Holiday 980 (Security only, non law enforcement)<br />
*Wildwood 910 (Security only, non law enforcement)<br />
<br />
<br />
The following units are not dispatched by LaSalle County, but if necessary they can contact LASCO only on 155.145 using these call signs:<br />
<br />
'''Dispatched by Marshall County'''<br />
*Wenona ML24 (Chief) ML23<br />
<br />
'''Dispatched by Kendall County'''<br />
*Millington 996<br />
<br />
'''Dispatched by Mendota PD'''<br />
*Earlville 995 996* I know this duplicates Millington, but this is what I was given.<br />
*Leland 983 (Chief) 985/986/987<br />
<br />
'''Dispatched by Dekalb County'''<br />
*Somonauk 921<br />
<br />
LASCO has direct communications with Mendota, Peru, Seneca and Spring Valley on 155.370 (point to point)<br />
<br />
LASCO does not have direct radio comms with Ottawa, Streator or LaSalle PD's, but can talk to all County city cars on 155.145<br />
<br />
Earlville and Leland PD are dispatched out of Mendota PD. The following ID's are used. Each unit ID serves to identify a particular officer.<br/><br />
*Earlville E-1 through E-16<br />
*Leland L-1 through L-12<br />
<br/><br />
The LASCO Sheriff squads are P1 - P28 (Paul Units) and refer to the vehicle number.<br />
Also heard are <br />
*P1 (Post 1) these are locations<br />
*P1 = Ottawa<br />
*P2 = County Hq<br />
*P17 = Grand Ridge<br />
*P11 = Mendota.<br />
Some "Posts" refer to resturants; etc.<br />
<br />
LASCI is divided up into 4 quadrants with the axis bein Route 23 and the Illinois River<br />
'''Peru ESDA'''<br />
*PR-1, PR-2, PR-3 or Peru ESDA 1, Peru ESDA 2 etc<br />
<br />
*2314 Morris Ambulance<br />
*2315 Morris Ambualnce<br />
<br />
*3100 Coal City Fire Base<br />
*3101 Coal City Fire Chief<br />
*3115 Coal CIty Ambulance<br />
<br />
*3200 Morris Fire Base<br />
*3201 Morris Chief<br />
*3202 Morris Asst Chief<br />
*3203 Morris Asst Chief<br />
<br />
*3212 South Wilmington Ambulance<br />
*3214 Braceville Ambulance<br />
<br />
*3400 Mazon Fire Base<br />
*3401 Mazon Fire Chief<br />
*3402 Mason Asst Fire Chief<br />
*3410 Mazon Fireman<br />
<br />
*6614 Gardner Ambualnce<br />
<br />
*1M21 Seneca<br />
*1M33 Ransom<br />
*1M41 Utica<br />
*1M51 Utica<br />
*2G26 Wilmington<br />
*2G44 Wilmington<br />
*2G42 Braidwood<br />
*2G90 Channahon<br />
*2G100 Braidwood<br />
*2H11 Braceville<br />
*2H15 Equistar<br />
*2H16 Minooka<br />
*2H17 Coal City<br />
*2H18 South Wilmington<br />
*2H20 Coal City<br />
*2H21 MVK<br />
*2H26 Minooka<br />
*2H52 Gardner<br />
*2I15 Essex<br />
*2I25 Reddick<br />
*3M16 Dwight<br />
*3M21 Selcas<br />
*3M22 Selcas<br />
*3M28 Selcas<br />
*3M29 Dwight<br />
<br />
==Separate Wiki Articles==<br />
* [[Businesses, Railroads, Media, Attractions and Recreation La Salle County (IL)]]<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Lee_County_(IL)&diff=94067Lee County (IL)2012-06-11T14:57:35Z<p>Loumaag: Adding link to orphaned page</p>
<hr />
<div>==Lee County===<br />
*[http://www.countyoflee.com Lee County Website]<br />
*Steward and Flag Center Fire both cover parts of Ogle & Lee Counties.<br />
*1/09 - Housing Authority appears to be using Wireless Phones now instead of UHF Radios.<br />
*Sheriff: Old Car-to-Car; 1- 154.83 167.9 PL; 2- 154.83 156.7 PL<br />
<br />
==EMS Agencies and Hospitals==<br />
===Katherine Shaw Bethea Hospital (Dixon)===<br />
*[http://ksbhospital.com/ Website]<br />
*WQOG403 - All MED Channels<br />
<br />
==Municipalities & Districts==<br />
<br />
===TwinComm - Twin Cities Communications===<br />
*"Twincomm" is an acronym for twin city communications. Formerly known as CGH EMS which covers the cities of Sterling and Rock Falls Il and are directly across the river from each other.<br />
<br />
===Ashton===<br />
'''Ashton Fire Protection District'''<br />
<br />
===Dixon===<br />
*[http://www.discoverdixon.org/ City Website]<br />
*[http://www.dixonpd.com/ Police Website]<br />
'''Dixon Rural Fire Protection District'''<br />
'''Dixon Community Fire Protection District of Lee And Ogle Counties'''<br />
*[http://dixonruralfire.com/ Website]<br />
*Serves rural Lee County in and around Dixon; also uses Fire MABAS Red<br />
<br />
<br />
==Schools==<br />
===Ashton-Franklin Center CUSD 275===<br />
*WQMF504 - 153.3425 Base/Mobile (was to be RM w/ 158.2275 input) 11K<br />
<br />
==Airports==<br />
===Charles R. Walgreens Field (Dixon) [C73]===<br />
*126.0 for Rockford Approach/Departure<br />
*WQMC731 Dixon Municipal AIrport AWOS 118.0-136.0<br />
<br />
<br />
==Businesses==<br />
===Agricultural===<br />
<pre><br />
463.9 BM WQKC984 Book, Debra: Farming (Compton)<br />
</pre><br />
<br />
==Separate Wiki Articles==<br />
* [[Businesses, Attractions and Recreation Lee County (IL)]]<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Iroquois_County_(IL)&diff=94066Iroquois County (IL)2012-06-11T14:54:47Z<p>Loumaag: Adding link to orphaned page</p>
<hr />
<div>==Iroquois County==<br />
===Sheriff/Highway===<br />
<pre><br />
453.47500 WQCD920 M Iroq SD RF Sheriff: Remote Receive Link to 155.755R <br />
153.96500 WQCR953 M IroqFirgrnd1 Fireground <br />
153.81500 WQCR953 M IroqFirgrnd2 Fireground <br />
158.76000 153.84500 KBU251 RM Iroq Highway Highway Department <br />
458.37500 KBU251 M Iroq HW RF1 Highway: Remote Receive Link to 158.76R <br />
458.37500 WQCR953 M Iroq HW RF2 Highway: Remote Receive Link to Highway Department 158.76R ( Watseka) <br />
</pre><br />
<br />
'''Township Roads Maintenance'''<br />
*Multiple licenses/applications for 150.995<br />
*Beaver, Sheldon and Concord Township Roads have licenses for 150.995 Base/Mobile (11K)<br />
*5/12 FCC Application 0005240394 for Middleport Roads (Watseka) 150.995 BM (11K)<br />
*WQPF211 - Martinton Township Roads - 151.13 Base/Mobile (11K)<br />
*WQPF208 - Milks Grove Township Roads - 151.13 Base/Mobile (11K at Herscher)<br />
<br />
===Fire Unit Numbering===<br />
<pre><br />
1431 & 1451 heard on 154.4 192.8 (6/11)<br />
</pre><br />
<br />
===Eastern Illinois Mutual Aid Fire Association===<br />
<pre><br />
154.40000 WNAG495 M 192.8 PL IroquoisFire Fire: County Dispatch (Watseka, Ashkum, Buckley, Donovan, Milford) [Expired 7/04] <br />
458.37500 WNAG495 F Remote Receive Link (Watseka) [Expired 7/04] <br />
153.81500 WNAG495 M IroqFirgrnd2 Fireground [Expired 7/04] <br />
153.96500 WNAG495 M IroqFirgrnd1 Fireground [Expired 7/04] <br />
</pre><br />
<br />
==Iroquois Memorial Hospital (Watseka)==<br />
*[http://www.iroquoismemorial.com/ Website]<br />
<br />
==Municipalities & Districts==<br />
<br />
==Schools==<br />
===Crescent-Iroquois High School=== <br />
<pre><br />
466.33750 WPUN651 M CIHS Ops Operations FM Schools <br />
</pre><br />
<br />
===Iroquois West Community High School===<br />
<pre><br />
452.22500 457.22500 KNJG465 RM IQCHS Buses1 Buses (Gilman) FM Schools <br />
461.82500 466.80000 KNJG465 RM IQCHS Buses2 Buses (Gilman) FM Schools <br />
</pre><br />
<br />
<br />
==Businesses==<br />
*Forrest Ready Mix: WQJS624 - 152.99 Base/Mobile (Gilman)<br />
===Agricultural===<br />
*Redeker Farms: KNCA997 - 452.0 Base/Mobile (Crescent City)<br />
*William J Young: Farming WPTH587 463.725 Repeater (11K at Watseka)<br />
*WIlliam J Young: Farming WPQA278 451.4 Repeater (11K at Watseka)<br />
*William J Young: Farming WPPY483 451.475 Repeater (Watseka-Canceled 12/11)<br />
*Zabel Farms: WPXL944 - 461.5 Repeater (Donaven)<br />
<br />
<pre><br />
HERBERT & HELEN MYERS FARMS KNBA391 451.97500 2001-06-11 A 1 0 FB4 IG WATSEKA <br />
HERBERT & HELEN MYERS FARMS KNBA391 456.97500 2001-06-11 A 8 0 MO IG WATSEKA <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 25 0 MO IG GILMAN <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 1 0 FB IG LEONARD <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 25 0 MO IG LEONARD <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 1 0 FB IG WELLINGTON <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 25 0 MO IG WELLINGTON <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 1 0 FB IG CISSNA PARK <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 25 0 MO IG CISSNA PARK <br />
HERITAGE FS INC WPEY269 151.95500 2004-04-17 A 1 0 FB IG GILMAN <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 1 0 FB IG LEONARD <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 25 0 MO IG LEONARD <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 1 0 FB IG WELLINGTON <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 25 0 MO IG WELLINGTON <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 1 0 FB IG CISSNA PARK <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 25 0 MO IG CISSNA PARK <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 1 0 FB IG GILMAN <br />
HERITAGE FS INC WPJS206 152.87000 2001-09-22 A 25 0 MO IG GILMAN <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 1 0 FB IG LEONARD <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 25 0 MO IG LEONARD <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 1 0 FB IG WELLINGTON <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 25 0 MO IG WELLINGTON <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 1 0 FB IG BEAVERVILLE <br />
HERITAGE FS INC KZY943 152.96000 2001-07-26 A 25 0 MO IG BEAVERVILLE <br />
<br />
RAVENS FARMS INC. WQDS322 151.52000 2005-10-19 A 1 0 FB6 IG <br />
RAVENS FARMS INC. WQDS322 151.52000 2005-10-19 A 29 0 MO IG <br />
RAVENS FARMS INC. WQDS322 151.52000 2005-10-19 A 1 0 FB6 IG MILFORD <br />
RAVENS FARMS INC. WQDS322 151.52000 2005-10-19 A 29 0 MO IG MILFORD <br />
RAVENS FARMS INC. WQDS322 158.34000 2005-10-19 A 29 0 MO IG MILFORD <br />
RAVENS FARMS INC. WQDS322 158.34000 2005-10-19 A 1 0 FX1 IG MILFORD <br />
RAVENS FARMS INC. WQDS322 158.34000 2005-10-19 A 29 0 MO IG <br />
RAVENS FARMS INC. WQDS322 158.34000 2005-10-19 A 1 0 FX1 IG <br />
<br />
AGRI TECH SERVICE INC KJQ267 154.54000 2003-12-25 A 1 0 FB IG GOODWINE <br />
AGRI TECH SERVICE INC KJQ267 154.54000 2003-12-25 A 11 0 MO IG GOODWINE <br />
ASHKUM GRAIN COMPANY WNGN554 463.47500 2001-08-21 A 1 0 FB4 IG ASHKUM BAUER FARM SERVICE INC KBL638 151.55000 1997-06-26 T 1 0 FB IG CISSNA PARK <br />
BAUER FARM SERVICE INC KBL638 151.55000 1997-06-26 T 10 0 MO IG CISSNA PARK <br />
BORK NURSERIES INC WNCD490 151.83500 2005-03-24 A 1 0 FB IG ONARGA <br />
Cargill, Incorporated/Cargil WQDK560 152.27750 2005-09-19 A 1 0 FB2 IG GILLMAN <br />
Cargill, Incorporated/Cargil WQDK560 152.27750 2005-09-19 A 15 0 MO IG GILLMAN <br />
Cargill, Incorporated/Cargil WQDK560 157.53750 2005-09-19 A 15 0 MO IG GILLMAN <br />
CHEBANSE AG SERVICE INC KST435 154.54000 2004-06-30 A 1 30 FB IG CHEBANSE <br />
CHEBANSE AG SERVICE INC KST435 154.54000 2004-06-30 A 15 0 MO IG CHEBANSE <br />
CROP PRODUCTION SERVICES INC KNCX953 463.50000 2002-02-23 A 1 0 FB2 IG ONARGA <br />
CROP PRODUCTION SERVICES INC KNCX953 463.50000 2002-02-23 A 13 0 MO IG ONARGA <br />
CROP PRODUCTION SERVICES INC KNCX953 468.50000 2002-02-23 A 1 0 FX1 IG ONARGA <br />
DANFORTH GILMAN GRAIN COMPAN WNFP380 464.97500 2002-10-11 A 1 0 FB IG DANFORTH <br />
DANFORTH GILMAN GRAIN COMPAN WNFP380 464.97500 2002-10-11 A 10 0 MO IG DANFORTH <br />
DANFORTH GILMAN GRAIN COMPAN WNFP380 464.97500 2002-10-11 A 1 0 FB IG GILMAN <br />
DANFORTH GILMAN GRAIN COMPAN WNFP380 464.97500 2002-10-11 A 10 0 MO IG GILMAN <br />
DE PATIS, DARIN WPNV723 160.06500 2004-07-08 A 5 0 MO IG <br />
DIETRICH, DENNIS WNMC976 152.87000 2003-07-16 A 1 0 FB IG SAINT ANNE <br />
DIETRICH, DENNIS WNMC976 152.87000 2003-07-16 A 30 0 MO IG SAINT ANNE <br />
DONOVAN FARMERS COOP INC KNGE522 462.17500 1998-02-24 T 1 0 FB2 IG ONARGA <br />
DONOVAN FARMERS COOP INC KNGE522 462.17500 1998-02-24 T 10 0 MO IG ONARGA <br />
DONOVAN FARMERS COOP INC KNGE522 467.17500 1998-02-24 T 2 0 FX1 IG ONARGA <br />
DONOVAN FARMERS COOP INC KNGE522 467.17500 1998-02-24 T 10 0 MO IG ONARGA <br />
FORD IROQUOIS F S INC KTA402 152.96000 2000-01-12 T 1 0 FB IG GILMAN <br />
FORD IROQUOIS F S INC KTA402 152.96000 2000-01-12 T 45 0 MO IG GILMAN <br />
FRAKE JR, HERBERT W WPVY493 461.05000 2002-09-05 A 1 0 FB2 IG CLIFTON <br />
FRAKE JR, HERBERT W WPVY493 461.05000 2002-09-05 A 15 0 MO IG CLIFTON <br />
FRAKE JR, HERBERT W WPVY493 466.05000 2002-09-05 A 15 0 MO IG CLIFTON <br />
FRAKE JR, HERBERT W WPVY493 466.05000 2002-09-05 A 1 0 FX1 IG CLIFTON <br />
FREY HYBRID CORN CO INC WNKB345 462.17500 1997-08-28 T 1 0 FB4 IG ONARGA <br />
FREY HYBRID CORN CO INC WNKB345 462.17500 1997-08-28 T 10 0 MO IG ONARGA <br />
FREY HYBRID CORN CO INC WNKB345 467.17500 1997-08-28 T 1 0 FX1 IG ONARGA <br />
FREY HYBRID CORN CO INC WNKB345 467.17500 1997-08-28 T 10 0 MO IG ONARGA <br />
GENZEL, LEE KDN295 152.93000 2002-03-23 A 8 0 MO IG BUCKLEY <br />
GENZEL, LEE KDN295 152.93000 2002-03-23 A 1 0 FB IG BUCKLEY <br />
GOODWINE COOPERATIVE GRAIN C KNCC465 451.82500 2005-05-17 A 1 0 FB IG GOODWINE <br />
GOODWINE COOPERATIVE GRAIN C KNCC465 451.82500 2005-05-17 A 6 0 MO IG GOODWINE<br />
</pre><br />
<br />
===Miscellaneous===<br />
<br />
===Utilities===<br />
<pre><br />
PRAIRIE POWER COOP WGZ934 154.47125 2001-10-18 A 1 0 FXO IG CLIFTON <br />
PRAIRIE POWER INC. WGZ979 154.47125 2001-10-18 A 1 0 FXO IG WELLINGTON <br />
PRAIRIE POWER INC. WHA216 154.47125 2001-10-18 A 1 0 FXO IG BUCKLEY <br />
PRAIRIE POWER INC. WHA217 154.47125 2001-10-18 A 1 0 FXO IG GILMAN <br />
PRAIRIE POWER INC. WHA219 154.47125 2001-10-18 A 1 0 FXO IG WOODLAND <br />
PRAIRIE POWER INC. WHA220 154.47125 2001-10-18 A 1 0 FXO IG CISSNA <br />
PRAIRIE POWER INC. WGZ894 154.47125 2001-10-18 A 1 0 FXO IG PAPINEAU <br />
PRAIRIE POWER INC. WGZ896 154.47125 2001-10-18 A 1 0 FXO IG WATSEKA <br />
PRAIRIE POWER INC. WGZ897 154.47125 2001-10-18 A 1 0 FXO IG DONOVAN <br />
PRIEST, RONALD WNUX232 151.92500 2000-12-16 A 1 0 FB IG WATSEKA <br />
<br />
NORTHERN ILLINOIS GAS COMPAN WNHU780 173.35000 2001-10-26 A 1 0 FXO IG GILMAN 101 <br />
NORTHERN ILLINOIS GAS COMPAN WNHU780 173.39000 2001-10-26 A 1 0 FXO IG GILMAN 101 <br />
NORTHERN ILLINOIS GAS COMPAN WNRL401 456.10000 2004-12-04 A 1 0 FX1 IG KANKAKEE <br />
<br />
NICOR GAS KSF320 451.07500 2003-08-14 A 1 0 FXO IG SAINT ANNE <br />
NICOR GAS KSF320 451.07500 2003-08-14 A 1 0 FB2 IG SAINT ANNE <br />
NICOR GAS KSF320 451.07500 2003-08-14 A 20 0 FXOT IG SAINT ANNE <br />
NICOR GAS WNNN541 451.10000 2003-08-14 A 1 0 FXO IG SAINT ANNE <br />
NICOR GAS WNNN541 451.10000 2003-08-14 A 1 0 FB2 IG SAINT ANNE <br />
NICOR GAS WNNN541 451.10000 2003-08-14 A 40 0 FXOT IG SAINT ANNE <br />
NICOR GAS KSF320 451.25000 2003-08-14 A 1 0 FXO IG SAINT ANNE <br />
NICOR GAS KSF320 451.25000 2003-08-14 A 1 0 FB2 IG SAINT ANNE <br />
NICOR GAS KSF320 451.25000 2003-08-14 A 20 0 FXOT IG SAINT ANNE <br />
NICOR GAS WNNN541 456.10000 2003-08-14 A 40 0 FXOT IG SAINT ANNE <br />
NICOR GAS WNNN541 461.75000 2003-08-14 A 1 0 FXO IG SAINT ANNE <br />
NICOR GAS WNNN541 461.75000 2003-08-14 A 1 0 FB2 IG SAINT ANNE <br />
NICOR GAS WNNN541 466.75000 2003-08-14 A 40 0 FXOT IG SAINT ANNE <br />
NICOR GAS COMPANY KDA581 451.07500 2004-04-03 A 1 0 FB2 IG CRESCENT CITY <br />
Comcast of Illinois/Texas, L WNBJ783 461.25000 2002-09-24 A 1 0 FB4 IG ONARGA <br />
Comcast of Illinois/Texas, L WNBJ783 461.25000 2002-09-24 A 10 0 MO IG ONARGA <br />
Comcast of Illinois/Texas, L WNBJ783 466.25000 2002-09-24 A 2 0 FX1 IG ONARGA<br />
</pre><br />
<br />
===Communications Companies===<br />
<pre><br />
CAILTEUX, KENNETH WPVB525 451.72500 2002-06-12 A 1 0 FB6 IG CRESCENT CITY <br />
CAILTEUX, KENNETH WPVB525 451.72500 2002-06-12 A 200 0 MO IG CRESCENT CITY <br />
CAILTEUX, KENNETH WPVB525 456.72500 2002-06-12 A 200 0 MO IG CRESCENT CITY <br />
CAILTEUX, KENNETH WPVB525 456.72500 2002-06-12 A 20 0 FX1 IG CRESCENT CITY <br />
CAILTEUX, KENNETH WPEC498 461.87500 2003-12-16 A 1 0 FB6 IG CLIFTON <br />
CAILTEUX, KENNETH WPEC498 461.87500 2003-12-16 A 75 0 MO IG CLIFTON <br />
CAILTEUX, KENNETH WPAW276 464.57500 2002-09-26 A 1 0 FB2 IG CLIFTON <br />
CAILTEUX, KENNETH WPAW276 464.57500 2002-09-26 A 7 0 MO IG CLIFTON <br />
CAILTEUX, KENNETH WPEC498 466.87500 2003-12-16 A 75 0 MO IG CLIFTON <br />
CAILTEUX, KENNETH WPAW276 469.57500 2002-09-26 A 7 0 MO IG CLIFTON<br />
YOUNG Mr, LAURENCE E KZJ581 158.38500 2001-08-25 A 1 0 FB IG BUCKLEY <br />
YOUNG Mr, LAURENCE E KZJ581 158.38500 2001-08-25 A 8 0 MO IG BUCKLEY <br />
YOUNG Mr, WILLIAM J WPPY483 451.47500 2004-12-29 A 105 0 MO IG WATSEKA <br />
YOUNG Mr, WILLIAM J WPPY483 451.47500 2004-12-29 A 1 0 FB6 IG WATSEKA <br />
YOUNG Mr, WILLIAM J WPPY483 456.47500 2004-12-29 A 105 0 MO IG WATSEKA <br />
YOUNG Mr, WILLIAM J WPPY483 456.47500 2004-12-29 A 1 0 FX1 IG WATSEKA <br />
YOUNG Mr, WILLIAM J WPPW717 461.02500 2004-12-29 A 1 0 FB6 IG ONARGA <br />
YOUNG Mr, WILLIAM J WPPW717 461.02500 2004-12-29 A 105 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPVB923 461.45000 2002-06-14 A 1 0 FB6 IG ONARGA <br />
YOUNG MR, WILLIAM J WPVB923 461.45000 2002-06-14 A 35 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPVB923 461.45000 2002-06-14 A 45 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPTY587 463.72500 2002-01-14 A 110 0 MO IG WATSEKA <br />
YOUNG MR, WILLIAM J WPTY587 463.72500 2002-01-14 A 1 0 FB6 IG WATSEKA <br />
YOUNG MR, WILLIAM J WPXZ754 464.80000 2003-07-08 A 1 0 FB6 IG ONARGA <br />
YOUNG MR, WILLIAM J WPXZ754 464.80000 2003-07-08 A 33 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPXZ754 464.80000 2003-07-08 A 40 0 MO IG ONARGA <br />
YOUNG Mr, WILLIAM J WPPW717 466.02500 2004-12-29 A 1 0 FX1 IG ONARGA <br />
YOUNG Mr, WILLIAM J WPPW717 466.02500 2004-12-29 A 105 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPVB923 466.45000 2002-06-14 A 45 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPVB923 466.45000 2002-06-14 A 35 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPTY587 468.72500 2002-01-14 A 110 0 MO IG WATSEKA <br />
YOUNG MR, WILLIAM J WPTY587 468.72500 2002-01-14 A 1 0 FX1 IG WATSEKA <br />
YOUNG MR, WILLIAM J WPXZ754 469.80000 2003-07-08 A 40 0 MO IG ONARGA <br />
YOUNG MR, WILLIAM J WPXZ754 469.80000 2003-07-08 A 33 0 MO IG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 461.86250 2003-07-07 A 35 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 461.86250 2003-07-07 A 45 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 461.86250 2003-07-07 A 1 0 FB8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 463.98750 2003-07-07 A 45 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 463.98750 2003-07-07 A 35 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 463.98750 2003-07-07 A 1 0 FB8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 466.86250 2003-07-07 A 45 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 466.86250 2003-07-07 A 35 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 468.98750 2003-07-07 A 45 0 MO8 YG ONARGA <br />
YOUNG MR., WILLIAM J WPXZ589 468.98750 2003-07-07 A 35 0 MO8 YG ONARGA <br />
YOUNG, WILLIAM J WPQA278 451.40000 2005-04-05 A 1 0 FB6 IG WATSEKA <br />
YOUNG, WILLIAM J WPQA278 451.40000 2005-04-05 A 105 0 MO IG WATSEKA <br />
YOUNG, WILLIAM J WPQA278 456.40000 2005-04-05 A 1 0 FX1 IG WATSEKA <br />
YOUNG, WILLIAM J WPQA278 456.40000 2005-04-05 A 105 0 MO IG WATSEKA<br />
</pre><br />
<br />
==Separate Wiki Articles==<br />
* [[Businesses, Attractions and Recreation Iroquois County (IL)]]<br />
<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Midland_County_(MI)&diff=94065Midland County (MI)2012-06-11T14:50:53Z<p>Loumaag: Linking an orphan page</p>
<hr />
<div>== Police ==<br />
10-3 Affirmative <br><br />
10-9 Repeat <br><br />
10-22 Cancel <br><br />
<br />
<br />
==Business==<br />
* [[Dow Chemical (Midland)]]<br />
<br />
<br />
==Wiki Articles==<br />
* [[Businesses, Railroads, Media, Attractions and Recreation Midland County (MI)]]<br />
<br />
<br />
==Fire==<br />
Fire Tone Outs <br />
(edited 4-16-09 - Corrected City Tones)<br />
(edited 10-5-10 - Added Sanford DNR to unknown)<br />
<pre>County Station System Code 1 Tone 1 Duration Code 2 Tone 2 Duration Disp Freq<br />
Midland Midland City Station 1 QCII 190 1122.5 1 110 330.5 3 154.445 <br />
Midland Midland City Station 1 QCII 190 1122.5 1 198 1395.0 3 154.445 <br />
Midland Midland City Station 2 QCII 115 433.7 1 117 483.5 3 154.445<br />
Midland Midland City Station 3 QCII 158 855.5 1 128 879.0 3 154.445<br />
Midland All City Stations QCII 198 1395.0 8 154.445<br />
Midland Coleman, City of QCI MZ 881.0 1 NZ 977.2 3 154.370<br />
Midland Edenville Township QCI MZ 881.0 1 DZ 384.6 3 154.370<br />
Midland Homer Township QCI HZ 582.1 1 DZ 384.6 3 154.370<br />
Midland Hope Township QCI MZ 881.0 1 LZ 794.3 3 154.370<br />
Midland Jerome Township QCI MZ 881.0 1 HZ 582.1 3 154.370<br />
Midland Larkin Township QCI HZ 582.1 1 LZ 794.3 3 154.370<br />
Midland Lee Township QCI DZ 384.6 1 MZ 881.0 3 154.370<br />
Midland Lincoln Township QCI HZ 582.1 1 MZ 881.0 3 154.370<br />
Midland Midland Township QCI HZ 582.1 1 NZ 977.2 3 154.370<br />
Midland Mills Township QCI DZ 384.6 1 LZ 794.3 3 154.370<br />
Midland Sanford DNR QCI NZ 977.2 1 HZ 582.1 3 154.370<br />
</pre><br />
<br />
Search:MichiganFTO<br />
[[Category:FTOs]]<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Missouri_(US)&diff=94064Missouri (US)2012-06-11T14:45:02Z<p>Loumaag: /* Wiki Articles */ Oops, fixed order of last edit</p>
<hr />
<div>{{Collaboration<br />
|Statename=Missouri <br />
|StateDB=[http://www.radioreference.com/apps/db/?stid=29 {{color|white|Missouri DB]}}<br />
|Stateforum=[http://www.radioreference.com/forums/missouri-radio-discussion-forum/ {{color|white|Missouri Forum}}] }}<br />
<br />
{{LAudio<br />
|Sname=Missouri<br />
|LDBentry=[http://www.radioreference.com/apps/audio/?stid=29 Live Audio Links]<br />
}}<br />
<br />
==Apparatus/Equipment==<br />
* [[Laclede County, MO Fire Departments, Apparatus]]<br />
* [[Medical Helicopters, MO]]<br />
* [[Police Laclede, County Sheriffs Department, Apparatus]]<br />
* [[Police Springfield, MO Appartus]]<br />
* [[Police Waynesville, MO Apparatus]]<br />
* [[Waynesville, Mo Police Apparatus]]<br />
<br />
==List of Counties==<br />
* [[Information by County]] <br />
<br />
==Trunked Radio Systems==<br />
*[[Trunked Radio Systems (MO)|Trunked Radio Systems]]<br />
**[[Trunked Radio Systems (MO)#Education Trunked Systems|Education Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Federal Trunked Systems|Federal Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Private Trunked Systems|Private Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Public Trunked Systems|Public Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Unidentified Trunked Systems|Unidentified Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Utility Trunked Systems|Utility Trunked Systems]]<br />
<br />
==Mailing Lists==<br />
* [http://groups.yahoo.com/group/kc-scanning/ kc scanning]<br />
* [http://groups.yahoo.com/group/ScanMissouri/ Scan Missouri]<br />
* [http://groups.yahoo.com/group/MissouriScanners/ MissouriScanners]<br />
* [http://groups.yahoo.com/group/ScanMetroStLouis/ Scan Metro St.Louis]<br />
* [http://groups.yahoo.com/group/StLASE/ St.Louis Area Scanner Enthusiasts]<br />
<br />
==Online Scanners==<br />
* [http://myweb.accessus.net/~090/scan/scanneraudio.html AWH Live Scanner Audio]<br />
* [http://nevadamofeed.homeip.net:8000/live.m3u Nevada, Mo Live Scanner Feed]<br />
<br />
==Public Safety==<br />
* [[* STARRS - St Louis Area Regional Response System]]<br />
<br />
==Web/Wiki Sites==<br />
===Web Sites===<br />
* [http://www.mokanscanner.com/ MoKanScanner.com] Active frequencies and severe weather information for the Joplin and surrounding area<br />
* [[Media:ADC ServiceMap-1.gif|AmerenIP/Cilco service map (GIF)]]<br />
* [http://www.indepmo.com/frequencies/ Indepmo.com - Frequencies page]<br />
* [http://myweb.accessus.net/~090/scan/airfreq.html#milair St.Louis Military Air Freqs]<br />
* [http://sm0kenet.net/metroscan.net/ MetroScan]<br />
* [http://www.ksmoscanner.com/ KsMoScanner]<br />
** '''NOTE:''' The Milcom area is password protected<br />
<br />
===Wiki Articles===<br />
* [[Department of Corrections (MO)]]<br />
* [[Department of Public Safety (DPS) (MO)]]<br />
* [[Kansas City Metro Area]]<br />
* [[Medical Helicopters / EMS Agencies (Area Wide) (MO)]]<br />
* [[Missouri Communications Companies]]<br />
* [[Missouri Sports]]<br />
* [[Missouri Statewide Interoperable Network (MOSWIN)]]<br />
* [[Travel Reference (MO)|Missouri Travel Reference]]<br />
<br />
====Regional Categories====<br />
*[[:Category:St Louis Metro Area|St.Louis Metro Area]] <br />
<br />
{{Geographic Location<br />
| Northwest = [[Nebraska (US)|Nebraska]]<br />
| North = [[Iowa (US)|Iowa]]<br />
| Northeast = <br />
| West = [[Kansas (US)|Kansas]]<br />
| Center = Missouri<br />
| East = [[Illinois (US)|Illinois]]<br />
| Southwest = [[Oklahoma (US)|Oklahoma]]<br />
| South = [[Arkansas (US)|Arkansas]]<br />
| Southeast = [[Kentucky (US)|Kentucky]] & [[Tennessee (US)|Tennessee]]<br />
}}<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Missouri_(US)&diff=94063Missouri (US)2012-06-11T14:43:58Z<p>Loumaag: /* Wiki Articles */ Linking an orphan agency page</p>
<hr />
<div>{{Collaboration<br />
|Statename=Missouri <br />
|StateDB=[http://www.radioreference.com/apps/db/?stid=29 {{color|white|Missouri DB]}}<br />
|Stateforum=[http://www.radioreference.com/forums/missouri-radio-discussion-forum/ {{color|white|Missouri Forum}}] }}<br />
<br />
{{LAudio<br />
|Sname=Missouri<br />
|LDBentry=[http://www.radioreference.com/apps/audio/?stid=29 Live Audio Links]<br />
}}<br />
<br />
==Apparatus/Equipment==<br />
* [[Laclede County, MO Fire Departments, Apparatus]]<br />
* [[Medical Helicopters, MO]]<br />
* [[Police Laclede, County Sheriffs Department, Apparatus]]<br />
* [[Police Springfield, MO Appartus]]<br />
* [[Police Waynesville, MO Apparatus]]<br />
* [[Waynesville, Mo Police Apparatus]]<br />
<br />
==List of Counties==<br />
* [[Information by County]] <br />
<br />
==Trunked Radio Systems==<br />
*[[Trunked Radio Systems (MO)|Trunked Radio Systems]]<br />
**[[Trunked Radio Systems (MO)#Education Trunked Systems|Education Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Federal Trunked Systems|Federal Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Private Trunked Systems|Private Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Public Trunked Systems|Public Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Unidentified Trunked Systems|Unidentified Trunked Systems]]<br />
**[[Trunked Radio Systems (MO)#Utility Trunked Systems|Utility Trunked Systems]]<br />
<br />
==Mailing Lists==<br />
* [http://groups.yahoo.com/group/kc-scanning/ kc scanning]<br />
* [http://groups.yahoo.com/group/ScanMissouri/ Scan Missouri]<br />
* [http://groups.yahoo.com/group/MissouriScanners/ MissouriScanners]<br />
* [http://groups.yahoo.com/group/ScanMetroStLouis/ Scan Metro St.Louis]<br />
* [http://groups.yahoo.com/group/StLASE/ St.Louis Area Scanner Enthusiasts]<br />
<br />
==Online Scanners==<br />
* [http://myweb.accessus.net/~090/scan/scanneraudio.html AWH Live Scanner Audio]<br />
* [http://nevadamofeed.homeip.net:8000/live.m3u Nevada, Mo Live Scanner Feed]<br />
<br />
==Public Safety==<br />
* [[* STARRS - St Louis Area Regional Response System]]<br />
<br />
==Web/Wiki Sites==<br />
===Web Sites===<br />
* [http://www.mokanscanner.com/ MoKanScanner.com] Active frequencies and severe weather information for the Joplin and surrounding area<br />
* [[Media:ADC ServiceMap-1.gif|AmerenIP/Cilco service map (GIF)]]<br />
* [http://www.indepmo.com/frequencies/ Indepmo.com - Frequencies page]<br />
* [http://myweb.accessus.net/~090/scan/airfreq.html#milair St.Louis Military Air Freqs]<br />
* [http://sm0kenet.net/metroscan.net/ MetroScan]<br />
* [http://www.ksmoscanner.com/ KsMoScanner]<br />
** '''NOTE:''' The Milcom area is password protected<br />
<br />
===Wiki Articles===<br />
* [[Department of Public Safety (DPS) (MO)]]<br />
* [[Department of Corrections (MO)]]<br />
* [[Kansas City Metro Area]]<br />
* [[Medical Helicopters / EMS Agencies (Area Wide) (MO)]]<br />
* [[Missouri Communications Companies]]<br />
* [[Missouri Sports]]<br />
* [[Missouri Statewide Interoperable Network (MOSWIN)]]<br />
* [[Travel Reference (MO)|Missouri Travel Reference]]<br />
<br />
====Regional Categories====<br />
*[[:Category:St Louis Metro Area|St.Louis Metro Area]] <br />
<br />
{{Geographic Location<br />
| Northwest = [[Nebraska (US)|Nebraska]]<br />
| North = [[Iowa (US)|Iowa]]<br />
| Northeast = <br />
| West = [[Kansas (US)|Kansas]]<br />
| Center = Missouri<br />
| East = [[Illinois (US)|Illinois]]<br />
| Southwest = [[Oklahoma (US)|Oklahoma]]<br />
| South = [[Arkansas (US)|Arkansas]]<br />
| Southeast = [[Kentucky (US)|Kentucky]] & [[Tennessee (US)|Tennessee]]<br />
}}<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Newton_County_(MO)&diff=94062Newton County (MO)2012-06-11T14:40:50Z<p>Loumaag: Linking an orphan page</p>
<hr />
<div>* [[Communications Associates - UHF (Springfield)]] <br />
* [[Rayfield Communications, Inc. - UHF SWMO]]<br />
* [[Businesses, Attractions and Recreation Newton County (MO)]]<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Jackson_County_(MO)&diff=94061Jackson County (MO)2012-06-11T14:37:10Z<p>Loumaag: Linking an Orphan Page</p>
<hr />
<div>==Central Jackson County Fire Protection District==<br />
*[http://cjcfpd.org/ Website]<br />
*[http://cjcfpd.org/images2/cjc_map.jpg Coverage Map]<br />
<br />
8/06 - Central Jackson County Fire Protection District launched our new 911 Communication Center during the month of July 2006. This Communication Center, which focuses solely on Fire and EMS, will bring a higher standard of care to the citizens of Blue Springs, Grain Valley, Lake Tapawingo, and surrounding parts of Jackson County that are included in CJCFPD's jurisdiction.<br />
<br />
CJC's Communication Center is comprised of eight communication officers and one communication supervisor. The nine person staff runs a total of four shifts per week; utilizing a team structure and twelve hour shifts, maintaining an active center 24/7/365.<br />
<br />
The focus and function of the communication center includes answering and processing emergency phone calls, dispatching Fire and EMS units to call location, using EMD (Emergency Medical Dispatch) Protocol System for pre-arrival instructions, notifying additional personnel and utilities when needed, maintaining and updating mapping of the district, and monitoring availability of hospitals.<br />
<br />
===County Government===<br />
*[http://www.radioreference.com/apps/db/www.jacksongov.org/ Website]<br />
<br />
==Independence==<br />
*[http://www.indepmo.org City Website]<br />
Independence has migrated all Public Safety and Municipal Services users to [[Independence Public Safety (P25)|Independence Public Safety]], an 800 MHz 9600 baud [[Project 25]] Phase I system.<br />
<br />
'''Independence Fire Department'''<br />
*[http://ci.independence.mo.us/MapsPDF/FireDistricts.pdf Link to Fire Districts and Quads Map]<br />
<br />
==Kansas City==<br />
'''Public Safety'''<br />
*[[Kansas City (MO) Public Safety]]<br />
<br />
'''Parks & Recreation'''<br />
*[http://www.kansascityzoo.org/ Kansas City Zoo]<br />
<br />
==Lees Summit==<br />
*[http://www.leessummit.mo.us/ Website]<br />
<br />
===Fire Department===<br />
'''Fire Tone-Outs'''<br />
<pre><br />
Station 1 = Tone A#616.1 -- Tone B#650.5<br />
Station 2 = Tone A#616.1 -- Tone B#706<br />
Station 4 = Tone A#616.1 -- Tone B# 787.1<br />
</pre><br />
<br />
<br />
==Hospitals==<br />
<br />
==Research Medical Center==<br />
*[http://www.ResearchMedicalCenter.com Website]<br />
*"Midwest Division RMC LLC Hospital"<br />
<br />
<pre><br />
CenterpntASC 467.7125 MP WQKU837 Centerpoint Ambulatory Surgery Cntr (Independence)<br />
</pre><br />
<br />
==Schools==<br />
*[[Jackson County (MO) Schools|Schools]]<br />
<br />
==Separate Agency Page(s)==<br />
[[Attractions and Recreation Jackson County (MO)]]<br />
<br />
==Trunked Radio Systems==<br />
*[[Adventis Pharmaceuticals (Kansas City)|Adventis Pharmaceuticals]]<br />
*[[AirTime Services (KC)|AirTime Services]]<br />
*[[Clarkson Construction Company, Inc. - 800 MHz (KC)|Clarkson Construction Company]]<br />
*[[Commenco - UHF (Kansas City area)|Commenco]]<br />
*[[Grandview Public Safety/Works (Jackson MO)|Grandview Public Safety/Works]]<br />
*[[Great Plains Energy - 900 MHz (Kansas City Metro Area)|Great Plains Energy]]<br />
*[[Independence Public Safety (P25)|Independence Public Safety]]<br />
*[[Kansas City Chiefs Football Club]]<br />
*[[Kansas City Mo P25 - Metropolitan Area Regional Radio System (MARRS)|Kansas City MO Metropolitan Area Regional Radio System (MARRS)]]<br />
*[[Kansas City MO Public Safety|Kansas City MO Public Safety EDACS)]]<br />
*[[KC Wireless, Inc. - UHF (KC)|KC Wireless]]<br />
*[[Missouri Statewide Wireless Interoperable Network (MOSWIN)]]<br />
*[[Raytown Public Safety (Jackson MO)|Raytown Public Safety]]<br />
*[[Sprint Center - UHF (Kansas City MO)|Sprint Center]]<br />
*[[University of Missouri - 800 MHz (Kansas City)|University of Missouri]]<br />
*[[Westar Energy - 900 MHz (KS/MO)|Westar Energy]]<br />
<br />
{{Geographic Location<br />
|Center = Jackson County, MO<br />
|North = [[Clay County (MO)|Clay County, MO]]<br />
|Northeast = [[Ray County (MO)|Ray County, MO]]<br />
|East = [[Lafayette County (MO)|Lafayette County, MO]]<br />
|Southeast = [[Johnson County (MO)|Johnson County, MO]]<br />
|South = [[Cass County (MO)|Cass County, MO]]<br />
|Southwest = [[Johnson County (KS)|Johnson County, KS]]<br />
|West = <br />
|Northwest = [[Wyandotte County (KS)|Wyandotte County, KS]]<br />
}}<br />
<br />
Return to [[Missouri (US)|Missouri]]<br />
<br />
[[Category:FTOs]]<br />
[[Category:Kansas City Metro Area]]<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Johnson_County_(MO)&diff=94060Johnson County (MO)2012-06-11T14:33:57Z<p>Loumaag: Linking an agency orphan page</p>
<hr />
<div>Also See: [[Business, Media, Railroads, Recreation and Attractions Johnson County (MO)]]<br />
<br />
===University of Central Missouri (Warrensburg)===<br />
*KRZ868 -155.13 Repeater with 158.91 input<br />
*KRZ858 add 156.18 Repeater with 159.0 input (11K) [Returned 5/12 - High ERP]<br />
*KNJB570 - 151.895 Base/Mobile<br />
*WPGS862 - 463.825, 464.325 Repeaters for Building Maintenance<br />
*WNAF267 - 151.775 Base/Mobile [Expired]<br />
<br />
[[Category:Midwest Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=P25_CAI&diff=88686P25 CAI2012-01-13T15:53:34Z<p>Loumaag: /* P25 CAI means a digital trunking system */ Fixed Project 25 link</p>
<hr />
<div>The '''APCO Project 25 Common Air Interface''' is used to describe the [http://www.apcointl.org/ APCO] (Association of Public Safety Communications Officials International) specified standard for digital voice modulation. This standard specifies the type of digital signals transmitted by compliant radios. <br />
<br />
One radio using P25 CAI should be able to communicate with any other P25 CAI radio, regardless of what manufacturer produced the radio. P25 CAI uses a specific method of digitized voice called Improved Multi-Band Excitation ([[IMBE]]). The IMBE voice encoder-decoder ([[vocoder]]) samples the audio input at the microphone and produces a digital stream that represents the sound, this digital stream is then transmitted. The receiver sends this digital stream to the vocoder in its radio and it is used to produce a synthetic equivalent of the input sound. The IMBE vocoder is optimized for human speech and does not reproduce other types of sounds well, so analog ([[DTMF]] or multi-tone) alerts, such as fire tone outs, cannot be used with P25 CAI.<br />
<br />
<br />
==Common Misunderstandings==<br />
<br />
===P25 CAI means a digital trunking system===<br />
P25 CAI is a digital voice ([[modulation]]) type and therefore can be used on conventional simplex or repeater radio systems or in a trunking radio system. System type is not dependent on the use of P25 CAI except in the case of a [[Project 25]] Trunking Radio System; in that specific case only P25 CAI modulation is used (no analog allowed.)<br />
<br />
===P25 CAI means a 9600 bps control channel===<br />
P25 CAI is not related to the bps rate of any trunking system at all. P25 CAI is used on several [[Motorola ASTRO]] systems (3600 bps) both shared with analog talk groups or as an exclusive modulation type. Examples of the latter are the South Dakota State TRS and the Ohio State MARCS systems. Neither of these systems are Project 25 systems, but both are P25 CAI exclusive.<br />
<br />
===Motorola ASTRO and P25 CAI are not the same===<br />
There is much confusion regarding about Project 25 and Motorola's ASTRO product line. Some of this confusion comes from the scanner manufacturers themselves and some from oft repeated, but incorrect, information. <br />
<br />
Motorola ASTRO actually comes in two versions:<br />
*Motorola ASTRO -- Motorola, early in the digital modulation age came up with a proprietary digital form of modulation called Vector-Sum-Excited Linear Prediction or [[VSELP]]. This digital modulation type is fast becoming obsolete in Motorola's product line; however, there are still some radio systems using it and it is not compatible with P25 CAI. There are no scanners capable of monitoring VSELP.<br />
*Motorola ASTRO-25 -- Motorola contributes to the confusion by offering P25 CAI in its product line but referring to it generically as ASTRO-25. These radios can be used conventionally or on a Motorola TRS (3600 bps) system. These radios do use P25 CAI digital modulation and any scanner capable of P25 CAI decoding can be used with systems using these radios. Motorola also uses this same equipment when installing a Project 25 trunking system (9600 bps).<br />
<br />
The key to remember is that Motorola ASTRO and Project 25 are not synonymous.<br />
[[Category:RR Glossary]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Trunked_Radio_Systems&diff=88401Trunked Radio Systems2012-01-07T16:59:10Z<p>Loumaag: Removed dead link to "statistical multiplexing" that has been there for over a year.</p>
<hr />
<div>A '''trunked radio system''' is a specialized repeater system with one or more towers, and multiple frequencies, which allows channelized, semi-private conversations between many more groups of users than it actually has allocated RF channels; this is an example of statistical multiplexing. There are many different implementations of trunked business and public-safety radio, using different trunking protocols (like P25 CAI, LTR and Smartzone) and different audio modulations (like FM, NFM, and P25), but they all function in similar ways, and current generation scanners can receive most of them.<br />
<br />
<br />
== Overview ==<br />
<br />
Please read the [[Trunking Basics]] overview first. [[Media:Trunking description.pdf|Here]] is UPMan's excellent description on trunking. If you still have questions, feel free to post on the [http://www.radioreference.com/forums/forumdisplay.php?f=71 Trunking] forum at Radioreference.<br />
<br />
== Trunking FAQs ==<br />
* [http://www.bensware.com/scandfw/tttipsfaqs.htm Ben Saladino's Trunktracking Tips]<br />
** This site is a bit dated, but still contains some useful basic information<br />
* [[Uniden Multi-Site Trunking]]<br />
* Articles written by Dan Veeneman, MT Scanning Report columnist<br />
** [http://www.signalharbor.com/ttt/00jan/index.html Trunking Theory 101]<br />
** [http://www.signalharbor.com/sr/05apr/index.html Understanding Trunking]<br />
* [http://wiki.radioreference.com/index.php/Rebanding Rebanding Wiki Article]<br />
* [http://gtrac.ztn.net/ GTRAC EDACS info]<br />
* [http://www.thebriarpatch.org/trunking/ Motorola Trunking theory/concepts]<br />
* [http://www.police-scanner.info/scanning/trunked-radio-systems.htm Police Scanner info Trunked Radio Systems page]<br />
* The [http://mailman.qth.net/mailman/listinfo/trunkcom Trunkcom] mailing list at QTH.net is another great resource for questions and answers<br />
* [http://www.winradio.com/home/trunking_theory.htm WinRadio's Trunking Theory page]<br />
<br><br />
* For more technical topics regarding trunktracking, please see our [[:Category:Trunktracking Topics|Trunktracking Topics]] article<br />
<br />
== Trunked Radio System Types ==<br />
All forum links go to RadioReference<br />
* M/A-COM, Inc.<br />
** [http://www.radioreference.com/forums/forumdisplay.php?f=23 M/A-Com forum]<br />
** [[EDACS Provoice]]<br />
** [[EDACS]]<br />
** [[OpenSky]]<br />
* EF Johnson<br />
** [http://www.radioreference.com/forums/forumdisplay.php?f=24 LTR forum]<br />
** [[LTR]]<br />
* [[Motorola]]<br />
** [http://www.radioreference.com/forums/forumdisplay.php?f=22 Motorola forum]<br />
** [[iDEN]]<br />
** Motorola Harmony (see [[iDEN]])<br />
** [[Motorola Type I|Type I]]<br />
** [[Motorola Type II|Type II]]<br />
*** [[Motorola Type IIi Hybrid|Type IIi Hybrid]]<br />
*** [[Motorola Type II SmartNet|Type II Smartnet]]<br />
*** [[Motorola Type II SmartZone|Type II SmartZone]]<br />
*** [[Motorola Type II SmartZone OmniLink|Type II SmartZone OmniLink]]<br />
*** [[Motorola Type II VOC|Type II VOC]]<br />
* [[MPT-1327]]<br />
** [http://www.radioreference.com/forums/forumdisplay.php?f=27 MPT-1327 forum]<br />
* [[Project 25]]<br />
** [http://www.radioreference.com/forums/forumdisplay.php?f=25 P-25 forum]<br />
* [[SmarTrunk]]<br />
* [[TETRA]]<br />
* [[TETRAPOL]]<br />
<br />
[http://www.monitoringtimes.com/html/trunkedscanners.html Here] is a link from Monitoring Times magazine that outlines the various trunktracking scanners, and what system(s) they will cover. <br><br />
<br />
Sadly some systems are encrypted - and no scanner will ever copy them. A brief listing of these agencies can be found in the [[Encrypted Agencies]] article.<br />
<br />
The current 800MHz Public Safety band plan change is discussed under [[Rebanding]]. You may also find references to what scanners may be supported by following links from the [[Main Page]].<br />
<br />
== Trunked Radio Terms ==<br />
<br />
* [[Failsoft]]<br />
* [[Control Channel Only]]<br />
* [[Site trunking]]<br />
* [[Simulcast]]<br />
<br />
== Additional Trunking Topics==<br />
* [[Common Trunking Programming Questions]]<br />
* [[Determining Base/Step/Offset for VHF/UHF Motorola Systems]]<br />
* [[Determining Motorola Type I Fleetmaps]]<br />
* [[Locating additional LTR frequencies]]<br />
* [[Mapping an LTR System]]<br />
<br />
[[Category: RR Glossary]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Common_Public_Safety&diff=86471Common Public Safety2011-11-06T17:40:31Z<p>Loumaag: Undo revision 85535 by Nd5y (talk) Database Corrected</p>
<hr />
<div>== Nationwide Public Safety Interoperability Channels ==<br />
'''See: [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels] and [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide]'''<br />
<br />
'''Some states, regional and local areas have their own interoperability or mutual aid channels or trunked system talkgroups which are used instead of, or in addition to, those listed below.'''<br />
<br />
'''In some areas the channels listed below may have different channel names, tones, etc. or be used for different purposes.'''<br />
<br />
* State and regional frequencies are usually found on the ''Common/Shared'' or ''Statewide'' drop-down list on the main [http://www.radioreference.com/apps/db/ RadioReference Database] page for each state.<br />
* Interoperability channel plans are often published on various state government web sites. See links at the bottom of this page.<br />
* In analog mode all end user radios should transmit PL 156.7 (136.5 for high band temporary repeaters, 167.9 for NITA channels) and receive CSQ (carrier squelch) unless PL decode is necessary due to interference.<br />
* In APCO P25 dgital mode all radios should use NAC $293 (NAC $68F for NTIA channels).<br />
<br />
=== VHF ===<br />
==== VHF Low Band ====<br />
<freqsubcat> 64465</freqsubcat><br />
<br />
==== VHF High Band ====<br />
<freqsubcat> 64466</freqsubcat><br />
<br />
==== VHF NTIA Law Enforcement ====<br />
<freqsubcat>64500</freqsubcat><br />
<br />
==== VHF NTIA Incident Response ====<br />
<freqsubcat>64502</freqsubcat><br />
Notes<br />
* (1) VTAC17 and VTAC17D are VHF marine band channels and their use is limited to inland [http://www.fcc.gov/oet/info/maps/areas/maps/vpc.pdf VHF Public Coast Station Areas (VPCSA)] 10 through 42.<br />
* (2) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== UHF ===<br />
==== UHF Public Safety ====<br />
<freqsubcat> 64468</freqsubcat><br />
<br />
==== UHF NTIA Law Enforcement ====<br />
<freqsubcat>64501</freqsubcat><br />
<br />
==== UHF NTIA Incident Response ====<br />
<freqsubcat>64503</freqsubcat><br />
Notes<br />
* (1) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== 700 MHz ===<br />
<freqsubcat>64470</freqsubcat><br />
<br />
=== 800 MHz ===<br />
<freqsubcat>64471</freqsubcat><br />
<br />
<br />
== 700 MHz Low Power/Itinerant ==<br />
* The following narrowband channels (12.5 kHz) are designated for low power use for on-scene incident response purposes using mobiles and portables.<br />
* Transmitter power must not exceed 2 watts (ERP)<br />
* Three of the pairs can be licensed for nationwide itinerant use, the rest are subject to regional planning.<br />
<freqsubcat> 64498</freqsubcat><br />
<br />
<br />
== [[Disaster Relief]] ==<br />
<br />
===American Red Cross===<br />
====VHF Low====<br />
<freqsubcat>52358</freqsubcat><br />
====VHF High====<br />
<freqsubcat>52360</freqsubcat><br />
<br />
== [[Emergency Medical Services Radio]] ==<br />
<freqsubcat>64545</freqsubcat><br />
<br />
== Law Enforcement ==<br />
<freqsubcat>64547</freqsubcat><br />
* 155.370 is used as a law enforcement intersystem frequency used in many states and is often called "Point-to-Point". The FCC rule designation was removed in recent years.<br />
* 155.475 and 155.4825 are available nationwide for use in police emergency communications networks operated under statewide law enforcement emergency communications plans. 155.475 is often called "National Law Enforcement Mutual Aid"<br />
<br />
== [[National Incident Radio Support Cache]] ==<br />
== Search and Rescue ==<br />
<freqsubcat>64544</freqsubcat><br />
<br />
==Related Links ==<br />
=== References ===<br />
* [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels]<br />
* [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide (NIFOG) v 1.4] - Page also has programming guide and programming template (Excel spreadsheet).<br />
* [http://www.npstc.org/channelNaming.jsp NPSTC interoperability channel name standardization]<br />
* [http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1621A1.pdf FCC DA-01-1621 Federal Government Spectrum Available for Public Safety Interoperability Communications]<br />
* [http://www.fcc.gov/pshs/ FCC Public Safety & Homeland Security Bureau]<br />
** [http://transition.fcc.gov/pshs/techtopics/techtopics12.html Topic 12: National Interoperability Channels]<br />
* [http://www.apcointl.org/frequency/interoperability.php APCO Interoperability Resources]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr;sid=17215d8c8052bfef50e5299b335bd82c;rgn=div8;view=text;node=47%3A5.0.1.1.3.2.110.4;idno=47;cc=ecfr 47CFR90.20 Public Safety Pool Frequency Table]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=17215d8c8052bfef50e5299b335bd82c&rgn=div8&view=text&node=47:5.0.1.1.3.17.114.7&idno=47 47CFR90.531 Public Safety 700 MHz band Plan]<br />
* [http://www.apco911.org/frequency/documents/700_NB_channel_centers.pdf 700 MHz Narrowband Public Safety band plan (.PDF file) from APCO web site]<br />
* [http://www.apco911.org/frequency/documents/700_channel_centers_WB.pdf 700 MHz Widewband Public Safety band plan (.PDF file) from APCO web site]<br />
* [[Federal/Non-Federal Interoperability]]<br />
<br />
=== State Interoperability Web Sites ===<br />
* [http://www.dhs.alabama.gov/interopcomm.aspx?sm=b_d Alabama]<br />
* [http://ready.alaska.gov/SERC/committee_interop.htm Alaska]<br />
* [http://www.azgita.gov/psic Arizona]<br />
* [http://www.awin.arkansas.gov Arkansas]<br />
* [http://www.calema.ca.gov/TechnologyOperations/Pages/Communications-Interoperability-%28CICO%29.aspx California]<br />
* Colorado: [http://www.ccncinc.org CCNC], [http://www.colorado.gov/cs/Satellite/OIT-ServicesApps/CBON/1251575060697 OIT]<br />
* [http://www.ct.gov/demhs/cwp/view.asp?a=1923&q=287892&demhsNav=| Connecticut]<br />
* [http://divcomm.delaware.gov Delaware]<br />
* [http://www.capwin.org DC]<br />
* [http://www.dms.myflorida.com/suncom/public_safety_bureau/radio_communications Florida]<br />
* [http://www.gainterop.com Georgia]<br />
* Hawaii: need link<br />
* [http://www.bhs.idaho.gov/Pages/Communications/IdahoSIEC.aspx Idaho]<br />
* [http://www.state.il.us/IEMA/SCIP.asp Illinois]<br />
* [http://www.in.gov/ipsc Indiana]<br />
* [http://isicsb.iowa.gov Iowa]<br />
* [http://www.kansastag.gov/siec.asp Kansas]<br />
* [http://www.kwiec.ky.gov Kentucky]<br />
* [http://gohsep.la.gov/commo.aspx Louisiana]<br />
* [http://www.state.me.us/mema/programs/mema_prog_icomm.shtml Maine]<br />
* [http://doit.maryland.gov/interoperability/Pages/default.aspx Maryland]<br />
* [http://www.mass.gov/?pageID=eopssubtopic&L=3&L0=Home&L1=Homeland+Security+%26+Emergency+Response&L2=Other+Statewide+Homeland+Security+Information&sid=Eeops Massachusetts]<br />
* [http://www.michigan.gov/mpscs Michigan]<br />
* [http://dps.mn.gov/divisions/ecn Minnesota]<br />
* [http://www.wcc.ms.gov Mississippi]<br />
* [http://www.dps.mo.gov/HomelandSecurity/Communications.htm Missouri]<br />
* [http://pssb.mt.gov/pscommunications.mcpx Montana]<br />
* [http://its.ne.gov/network_serv/wireless/wireless.html Nebraska]<br />
* [http://homelandsecurity.nv.gov/NCSC.htm Nevada]<br />
* [http://www.nh.gov/safety/divisions/homeland/psic/index.html New Hampshire]<br />
* [http://interoperability.nj.gov New Jersey]<br />
* [http://www.nmdhsem.org/Statewide_Communications_Inoperability_Plan.aspx New Mexico]<br />
* [http://www.dhses.ny.gov/oiec New York]<br />
* [https://secure.nccrimecontrol.org/hsb/Pages/InteroperableCommunications.aspx North Carolina]<br />
* [http://www.nd.gov/des/state-radio North Dakota]<br />
* Ohio: [http://ema.ohio.gov/PlanForOhioMainPage.aspx EMA], [http://das.ohio.gov/Divisions/InformationTechnology/MARCSServices/tabid/124/Default.aspx MARCS]<br />
* Oklahoma: [http://www.ok.gov/homeland/Interoperable_Communications/Statewide_Communications_Interoperability_Plan_/index.html SCIP], [http://www.ok.gov/okwin OKWIN]<br />
* Oregon: [http://www.oregon.gov/SIEC/SCIP_Page.shtml SEIC], [http://www.oregon.gov/ODOT/HWY/StateRadioProject/index.shtml State Radio Project]<br />
* [http://www.portal.state.pa.us/portal/server.pt/community/public_safety_radio Pennsylvania]<br />
* Rhode Island: need link<br />
* South Carolina: [http://www.sled.sc.gov/HSOfficeHome.aspx?MenuID=HSOffice SLED HSO], [http://www.cio.sc.gov/councilscommittees/palmetto800 Palmetto]<br />
* [http://www.sdpscc.sd.gov South Dakota]<br />
* [http://www.region39.org Tennessee]<br />
* Texas: [http://tsiec.region49.org TSIEC], [http://txrc.region49.org TRC]<br />
* [http://siec.utah.gov Utah]<br />
* [http://vcomm.vermont.gov Vermont]<br />
* Virginia: [http://www.commonwealthpreparedness.virginia.gov/Initiatives/Interoperability CICO], [http://www.vsp.state.va.us/stars.shtm STARS]<br />
* [http://siec.wa.gov Washington]<br />
* [http://www.wvirp.com West Virginia]<br />
* [http://interop.wi.gov Wisconsin]<br />
* [http://wyolink.state.wy.us Wyoming]<br />
<br />
{{Refreshpage<br />
|Pageurl=http://wiki.radioreference.com/index.php/Common_Public_Safety}}<br />
<br />
Search:Interoperability<br />
[[Category:US and Canadian Common Frequencies]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Common_Public_Safety&diff=86470Common Public Safety2011-11-06T17:39:44Z<p>Loumaag: Undo revision 85536 by Nd5y (talk) Database corrected</p>
<hr />
<div>== Nationwide Public Safety Interoperability Channels ==<br />
'''See: [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels] and [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide]'''<br />
<br />
'''Some states, regional and local areas have their own interoperability or mutual aid channels or trunked system talkgroups which are used instead of, or in addition to, those listed below.'''<br />
<br />
'''In some areas the channels listed below may have different channel names, tones, etc. or be used for different purposes.'''<br />
<br />
* State and regional frequencies are usually found on the ''Common/Shared'' or ''Statewide'' drop-down list on the main [http://www.radioreference.com/apps/db/ RadioReference Database] page for each state.<br />
* Interoperability channel plans are often published on various state government web sites. See links at the bottom of this page.<br />
* In analog mode all end user radios should transmit PL 156.7 (136.5 for high band temporary repeaters, 167.9 for NITA channels) and receive CSQ (carrier squelch) unless PL decode is necessary due to interference.<br />
* In APCO P25 dgital mode all radios should use NAC $293 (NAC $68F for NTIA channels).<br />
<br />
=== VHF ===<br />
==== VHF Low Band ====<br />
<freqsubcat> 64465</freqsubcat><br />
<br />
==== VHF High Band ====<br />
<freqsubcat> 64466</freqsubcat><br />
<br />
====NTIA VHF Law Enforcement====<br />
* The [http://www.radioreference.com/apps/db/?aid=7742 database entry] for this subsection is wrong. This is the correct information taken from the documents linked at the top and bottom of this page.<br />
{|class=rrtable<br />
|+<br />
!Frequency!!Input!!Type!!Tone!!Alpha Tag!!Description!!Mode!!Tag<br />
|-<br />
|167.0875||||BM||167.9 PL||LEA||National Calling (Direct for LE1)||FMN ||Interop<br />
|-<br />
|167.0875||162.0875||R||167.9 PL||LE1||Operations||FMN||Interop<br />
|-<br />
|167.2500||162.2625||R||68F NAC||LE2||Operations||P25||Interop<br />
|-<br />
|167.7500||162.8375||R||68F NAC||LE3||Operations||P25||Interop<br />
|-<br />
|168.1125||163.2875||R||68F NAC||LE4||Operations||P25||Interop<br />
|-<br />
|168.4625||163.4250||R||68F NAC||LE5||Operations||P25||Interop<br />
|-<br />
|167.2500||||BM||68F NAC||LE6||Direct for LE2||P25||Interop<br />
|-<br />
|167.7500||||BM||68F NAC||LE7||Direct for LE3||P25||Interop<br />
|-<br />
|168.1125||||BM||68F NAC||LE8||Direct for LE4||P25||Interop<br />
|-<br />
|168.4625||||BM||68F NAC||LE9||Direct for LE5||P25||Interop<br />
|}<br />
<br />
<br />
====NTIA VHF Incident Response====<br />
* The [http://www.radioreference.com/apps/db/?aid=7742 database entry] for this subsection is wrong. This is the correct information taken from the documents linked at the top and bottom of this page.<br />
{|class=rrtable<br />
|+<br />
!Frequency!!Input!!Type!!Tone!!Alpha Tag!!Description!!Mode!!Tag<br />
|-<br />
|169.5375||164.7125||R||167.9 PL||NC 1 CALLLING ||National Calling||FMN||Interop<br />
|-<br />
|170.0125||165.2500||R||167.9 PL||IR1||Operations||FMN||Interop<br />
|-<br />
|170.4125||165.9625||R||167.9 PL||IR2||Operations||FMN||Interop<br />
|-<br />
|170.6875||166.5750||R||167.9 PL||IR3||Operations||FMN||Interop<br />
|-<br />
|173.0375||167.3250||R||167.9 PL||IR4||Operations||FMN||Interop<br />
|-<br />
|169.5375||||BM||167.9 PL||IR5||Direct for NC1||FMN||Interop<br />
|-<br />
|170.0125||||BM||167.9 PL||IR6||Direct for IR1||FMN||Interop<br />
|-<br />
|170.4125||||BM||167.9 PL||IR7||Direct for IR2||FMN||Interop<br />
|-<br />
|170.6875||||BM||167.9 PL||IR8||Direct for IR3||FMN||Interop<br />
|-<br />
|173.0375||||BM||167.9 PL||IR9||Direct for IR4||FMN||Interop<br />
|}<br />
<br />
<br />
=== UHF ===<br />
==== UHF Public Safety ====<br />
<freqsubcat> 64468</freqsubcat><br />
<br />
====NTIA UHF Law Enforcement====<br />
* The [http://www.radioreference.com/apps/db/?aid=7742 database entry] for this subsection is wrong. This is the correct information taken from the documents linked at the top and bottom of this page.<br />
{|class=rrtable<br />
|+<br />
!Frequency!!Input!!Type!!Tone!!Alpha Tag!!Description!!Mode!!Tag <br />
|-<br />
|414.0375||||BM||167.9 PL||LEB||National Calling||FMN||Interop<br />
|-<br />
|409.9875||418.9875||R||167.9 PL||LE10||Operations||FMN||Interop<br />
|-<br />
|410.1875||419.1875||R||68F NAC||LE11||Operations||P25||Interop<br />
|-<br />
|410.6125||419.6125||R||68F NAC||LE12||Operations||P25||Interop<br />
|-<br />
|414.0625||||BM||68F NAC||LE13||Operations||P25||Interop<br />
|-<br />
|414.3125||||BM||68F NAC||LE14||Operations||P25||Interop<br />
|-<br />
|414.3375||||BM||68F NAC||LE15||Operations||P25||Interop<br />
|-<br />
|409.9875||||BM||167.9 PL||LE16||Direct for LE 10||FMN||Interop<br />
|-<br />
|410.1875||||BM||68F NAC||LE17||Direct for LE 11||P25||Interop<br />
|-<br />
|410.6125||||BM||68F NAC||LE18||Direct for LE 12||P25||Interop<br />
|}<br />
<br />
<br />
====NTIA UHF Incident Response====<br />
* The [http://www.radioreference.com/apps/db/?aid=7742 database entry] for this subsection is wrong. This is the correct information taken from the documents linked at the top and bottom of this page.<br />
{|class=rrtable<br />
|+<br />
!Frequency!!Input!!Type!!Tone!!Alpha Tag!!Description!!Mode!!Tag<br />
|-<br />
|410.2375||419.2375||R||CSQ ||NC 2 CALLING||National Calling||FMN||Interop<br />
|-<br />
|410.4375||419.4375||R||167.9 PL||IR10||Operations||FMN||Interop<br />
|-<br />
|410.6375||419.6375||R||167.9 PL||IR11||Operations||FMN||Interop<br />
|-<br />
|410.8375||419.8375||R||167.9 PL||IR12||Operations||FMN||Interop<br />
|-<br />
|413.1875||||BM||167.9 PL||IR13||Operations||FMN||Interop<br />
|-<br />
|413.2125||||BM||167.9 PL||IR14||Operations||FMN||Interop<br />
|-<br />
|410.2375||||BM||167.9 PL||IR15||Direct for NC 2||FMN||Interop<br />
|-<br />
|410.4375||||BM||167.9 PL||IR16||Direct for IR 10||FMN||Interop<br />
|-<br />
|410.6375||||BM||167.9 PL||IR17||Direct for IR 11||FMN||Interop<br />
|-<br />
|410.8375||||BM||167.9 PL||IR18||Direct for IR 12||FMN||Interop<br />
|}<br />
<br />
<br />
=== 700 MHz ===<br />
<freqsubcat>64470</freqsubcat><br />
<br />
=== 800 MHz ===<br />
<freqsubcat>64471</freqsubcat><br />
<br />
== 700 MHz Low Power/Itinerant ==<br />
* The following narrowband channels (12.5 kHz) are designated for low power use for on-scene incident response purposes using mobiles and portables.<br />
* Transmitter power must not exceed 2 watts (ERP)<br />
* Three of the pairs can be licensed for nationwide itinerant use, the rest are subject to regional planning.<br />
<freqsubcat> 64498</freqsubcat><br />
<br />
== [[Disaster Relief]] ==<br />
<br />
===American Red Cross===<br />
====VHF Low====<br />
<freqsubcat>52358</freqsubcat><br />
<br />
====VHF High====<br />
<freqsubcat>52360</freqsubcat><br />
<br />
== [[Emergency Medical Services Radio]] ==<br />
<freqsubcat>64545</freqsubcat><br />
<br />
== Law Enforcement ==<br />
<freqsubcat>64547</freqsubcat><br />
* 155.370 is used as a law enforcement intersystem frequency used in many states and is often called "Point-to-Point". The FCC rule designation was removed in recent years.<br />
* 155.475 and 155.4825 are available nationwide for use in police emergency communications networks operated under statewide law enforcement emergency communications plans. 155.475 is often called "National Law Enforcement Mutual Aid"<br />
<br />
== [[National Incident Radio Support Cache]] ==<br />
== Search and Rescue ==<br />
<freqsubcat>64544</freqsubcat><br />
<br />
==Related Links ==<br />
=== References ===<br />
* [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels]<br />
* [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide (NIFOG) v 1.4] - Page also has programming guide and programming template (Excel spreadsheet).<br />
* [http://www.npstc.org/channelNaming.jsp NPSTC interoperability channel name standardization]<br />
* [http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1621A1.pdf FCC DA-01-1621 Federal Government Spectrum Available for Public Safety Interoperability Communications]<br />
* [http://www.fcc.gov/pshs/ FCC Public Safety & Homeland Security Bureau]<br />
** [http://transition.fcc.gov/pshs/techtopics/techtopics12.html Topic 12: National Interoperability Channels]<br />
* [http://www.apcointl.org/frequency/interoperability.php APCO Interoperability Resources]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr;sid=17215d8c8052bfef50e5299b335bd82c;rgn=div8;view=text;node=47%3A5.0.1.1.3.2.110.4;idno=47;cc=ecfr 47CFR90.20 Public Safety Pool Frequency Table]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=17215d8c8052bfef50e5299b335bd82c&rgn=div8&view=text&node=47:5.0.1.1.3.17.114.7&idno=47 47CFR90.531 Public Safety 700 MHz band Plan]<br />
* [http://www.apco911.org/frequency/documents/700_NB_channel_centers.pdf 700 MHz Narrowband Public Safety band plan (.PDF file) from APCO web site]<br />
* [http://www.apco911.org/frequency/documents/700_channel_centers_WB.pdf 700 MHz Widewband Public Safety band plan (.PDF file) from APCO web site]<br />
* [[Federal/Non-Federal Interoperability]]<br />
<br />
=== State Interoperability Web Sites ===<br />
* [http://www.dhs.alabama.gov/interopcomm.aspx?sm=b_d Alabama]<br />
* [http://ready.alaska.gov/SERC/committee_interop.htm Alaska]<br />
* [http://www.azgita.gov/psic Arizona]<br />
* [http://www.awin.arkansas.gov Arkansas]<br />
* [http://www.calema.ca.gov/TechnologyOperations/Pages/Communications-Interoperability-%28CICO%29.aspx California]<br />
* Colorado: [http://www.ccncinc.org CCNC], [http://www.colorado.gov/cs/Satellite/OIT-ServicesApps/CBON/1251575060697 OIT]<br />
* [http://www.ct.gov/demhs/cwp/view.asp?a=1923&q=287892&demhsNav=| Connecticut]<br />
* [http://divcomm.delaware.gov Delaware]<br />
* [http://www.capwin.org DC]<br />
* [http://www.dms.myflorida.com/suncom/public_safety_bureau/radio_communications Florida]<br />
* [http://www.gainterop.com Georgia]<br />
* Hawaii: need link<br />
* [http://www.bhs.idaho.gov/Pages/Communications/IdahoSIEC.aspx Idaho]<br />
* [http://www.state.il.us/IEMA/SCIP.asp Illinois]<br />
* [http://www.in.gov/ipsc Indiana]<br />
* [http://isicsb.iowa.gov Iowa]<br />
* [http://www.kansastag.gov/siec.asp Kansas]<br />
* [http://www.kwiec.ky.gov Kentucky]<br />
* [http://gohsep.la.gov/commo.aspx Louisiana]<br />
* [http://www.state.me.us/mema/programs/mema_prog_icomm.shtml Maine]<br />
* [http://doit.maryland.gov/interoperability/Pages/default.aspx Maryland]<br />
* [http://www.mass.gov/?pageID=eopssubtopic&L=3&L0=Home&L1=Homeland+Security+%26+Emergency+Response&L2=Other+Statewide+Homeland+Security+Information&sid=Eeops Massachusetts]<br />
* [http://www.michigan.gov/mpscs Michigan]<br />
* [http://dps.mn.gov/divisions/ecn Minnesota]<br />
* [http://www.wcc.ms.gov Mississippi]<br />
* [http://www.dps.mo.gov/HomelandSecurity/Communications.htm Missouri]<br />
* [http://pssb.mt.gov/pscommunications.mcpx Montana]<br />
* [http://its.ne.gov/network_serv/wireless/wireless.html Nebraska]<br />
* [http://homelandsecurity.nv.gov/NCSC.htm Nevada]<br />
* [http://www.nh.gov/safety/divisions/homeland/psic/index.html New Hampshire]<br />
* [http://interoperability.nj.gov New Jersey]<br />
* [http://www.nmdhsem.org/Statewide_Communications_Inoperability_Plan.aspx New Mexico]<br />
* [http://www.dhses.ny.gov/oiec New York]<br />
* [https://secure.nccrimecontrol.org/hsb/Pages/InteroperableCommunications.aspx North Carolina]<br />
* [http://www.nd.gov/des/state-radio North Dakota]<br />
* Ohio: [http://ema.ohio.gov/PlanForOhioMainPage.aspx EMA], [http://das.ohio.gov/Divisions/InformationTechnology/MARCSServices/tabid/124/Default.aspx MARCS]<br />
* Oklahoma: [http://www.ok.gov/homeland/Interoperable_Communications/Statewide_Communications_Interoperability_Plan_/index.html SCIP], [http://www.ok.gov/okwin OKWIN]<br />
* Oregon: [http://www.oregon.gov/SIEC/SCIP_Page.shtml SEIC], [http://www.oregon.gov/ODOT/HWY/StateRadioProject/index.shtml State Radio Project]<br />
* [http://www.portal.state.pa.us/portal/server.pt/community/public_safety_radio Pennsylvania]<br />
* Rhode Island: need link<br />
* South Carolina: [http://www.sled.sc.gov/HSOfficeHome.aspx?MenuID=HSOffice SLED HSO], [http://www.cio.sc.gov/councilscommittees/palmetto800 Palmetto]<br />
* [http://www.sdpscc.sd.gov South Dakota]<br />
* [http://www.region39.org Tennessee]<br />
* Texas: [http://tsiec.region49.org TSIEC], [http://txrc.region49.org TRC]<br />
* [http://siec.utah.gov Utah]<br />
* [http://vcomm.vermont.gov Vermont]<br />
* Virginia: [http://www.commonwealthpreparedness.virginia.gov/Initiatives/Interoperability CICO], [http://www.vsp.state.va.us/stars.shtm STARS]<br />
* [http://siec.wa.gov Washington]<br />
* [http://www.wvirp.com West Virginia]<br />
* [http://interop.wi.gov Wisconsin]<br />
* [http://wyolink.state.wy.us Wyoming]<br />
<br />
{{Refreshpage<br />
|Pageurl=http://wiki.radioreference.com/index.php/Common_Public_Safety}}<br />
<br />
Search:Interoperability<br />
[[Category:US and Canadian Common Frequencies]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Location_Based_Scanning&diff=86277Location Based Scanning2011-10-27T12:46:21Z<p>Loumaag: /* Understanding GPS data in the RadioReference database */ Removed the note about diff to reflect change enacted yesterday</p>
<hr />
<div>== Overview ==<br />
<br />
'''Location-based scanning''' is a patented function of certain Uniden DMA scanners. (US Patents 6,192,233 and 9,941,120.)<br />
*RR Wiki: [[Uniden_DMA_FAQ]]<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features]]<br />
<br />
According to Uniden, location-based scanning allows you to control which systems/sites and channel groups are scanned based on your exact location. This frees you from having to manually enable and disable systems or channel groups as you change location. Specifically, location-based scanning uses the scanners lockout function to control what is scanned based on your location. It unlocks systems, sites, or channel groups when you are inside an element's radius. When you exit the radius, the element is temporarily locked out.<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/LocationBasedScanning Location Based Scanning]<br />
<br />
Uniden scanners [[BCD996T]], [[BCT15]], [[BCT15X]] and all XT models ([[BC346XT]], [[BCD396XT]], [[BCD996XT]]) support location-based scanning. The Uniden [[HomePatrol-1]] (HP-1) also supports location-based scanning, with the added feature of Zip-Code control. The HomePatrol-1 has the ability to let you set your location using a Zip-Code, but the Zip-Code itself is not used (it is converted to GPS coordinates, which are used for determining what will be scanned.) <br />
<br />
The HP-1 comes preloaded with the entire RadioReference database and users can enter a Zip-Code, a range in miles, and the types of services they want to hear. Within seconds users can be listening to all Police Dispatch calls within a 5 miles range of downtown Indianapolis, etc.<br />
<br />
*HomePatrol Blog: [http://www.homepatrol.com/index.php?option=com_content&view=article&id=17 Location, Location, Location]<br />
<br />
The scanners do not have a GPS receiver built-in, you must purchase an aftermarket GPS device compatible with your scanner. Details for connecting a GPS receiver vary by scanner. Compatible GPS devices all use the common DB9 serial type connection. For the mobile models (BCT15, BCD996T, BCT15X, BCD996XT) you can connect directly to the rear port of the scanner. For the portable scanners (BC346XT and BCD396XT) you can use the data cable that was supplied with the scanner. Some installations may require a gender changer to mate DB-9 connections. In the case of either portable scanner, if you use the cable that came with the scanner a null modem/gender changer is a requirement. A null modem adapter is not required if you purchase the optional GPS adapter cable designed for use with the HP-1 and other DMA scanners. <br />
<br />
*RR Wiki [[Uniden_Scanner_GPS_Features#Compatible_GPS_receivers|Compatible GPS Receivers]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ConnectingAGpsReceiver Connecting A GPS Receiver]<br />
<br />
The GPS function of your scanner can be used for more than just controlling what you listen to. For example, you can enter, store and have the scanner alert you to dangerous intersections or when you are going too fast, etc. These are commonly referred to as location alert functions.<br />
<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features#Non-Radio_Location-Based_GPS_Features|Non-Radio Location Based GPS Features]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/GPSMode GPS Mode]<br />
<br />
In addition to the basic GPS functions, for every entry you want to monitor with your scanner, you can program a set of criteria using GPS coordinates and a range. (In the case of the HP-1, this comes already pre-programmed or you can program any entity yourself.) To better understand how this works, you should become familiar with how to program your scanner with third party software. You can program manually, but it can be more difficult and time consuming. This article does not cover how to program entities (frequencies or systems) into your scanner, rather the concept and understanding of programming locations with an entity or alert function.<br />
<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ProgrammingLocations Programming Locations]<br />
<br />
===Understanding GPS data in the RadioReference database===<br />
<br />
In addition to being familiar with your scanner and an understanding of programming locations (described above) you should have a general understanding of where RadioReference stores location data with its radio data that can be downloaded by third party software.<br />
<br />
While it is not necessary to know the specific names of all data fields, currently the RadioReference database stores location data in several database fields that are not used for Location-based scanning, such as: Zip-Code info and FCC location, etc. For example, when you review any agency info in the database if you click on the FCC license call sign the GPS coordinates registered with the FCC will sometimes be shown. This data is not what is used for location based scanning.<br />
<br />
It is very helpful to be aware of the RadioReference database fields that match up to what can be used in the scanners. Each description below is followed by a sample link where RadioReference users can view specific types of data online in report format. The following fields correspond directly to the data used in the scanners.<br />
<br />
<blockquote>'''''Trunked System site''''' – a trunking site can have specific location data assigned to it. If none is specified, then it inherits the location data based on the county that it is located in. If no county is defined for the site, the site inherits the trunked system default location data. The name of the field used by the third party software is called '''TrsSite''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=7&sid=2856 http://www.radioreference.com/apps/db/?rpt=7&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Trunked System Talkgroup category''''' – a talkgroup category can have specific location data assigned to it. If none is specified, it inherits the trunked system default location data. The name of the field used by the third party software is called '''TalkgroupCat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=8&sid=2856 http://www.radioreference.com/apps/db/?rpt=8&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Frequency Subcategory''''' - a conventional frequency subcategory can have specific location data assigned to it. If no location data is specified for the frequency subcategory, then it inherits location data from the parent agency or county. The name of the field used by the third party software is called '''subcat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=6&ctid=255 http://www.radioreference.com/apps/db/?rpt=6&ctid=XXXX]<br><br><br />
[http://www.radioreference.com/apps/db/?action=locPop&scid=4872 http://www.radioreference.com/apps/db/?action=locPop&scid=XXXX]<br />
</blockquote></blockquote><br />
<br />
RadioReference members can submit data for any of these fields where there is none or where there are errors. (Remember, if you are submitting data, that the coordinates and range should be entered for the intended useable area, not the coverage area. For example, if Agency XYZ has a 300 watt repeater that you can hear for miles away from the city, the intended usable area is more likely to be the agency boundary of the city or county. When submitting data to the database you would enter the radius necessary to cover the city or county, not a larger radius to cover the capable listening area of the transmitter.) Users who desire to add [[Location_Based_Info]] should become very familiar with [[RR_Database_Submission_Guidelines]] before submitting changes to the RadioReference database.<br />
<br />
The descriptions of the fields described above make reference to ‘inheriting’ data from higher levels of the database. There are multiple fields that the RadioReference User cannot see by looking at the database online. The key fields relevant to location-based scanning that you cannot see are as follows:<br />
# '''''State''''' – a state can have location data assigned to it that serves as a default set of location data for the state or for state agencies.<br />
# '''''County''''' – a county can have location data assigned to it that serves as a default set of location data for the county. <br />
# '''''Agency''''' – an agency can have location data assigned to it that serves as a default set of location data for the agency. <br />
# '''''Trunk System''''' – a trunked system can have location data assigned to it that serves as a default set of location data for the entire system.<br />
<br />
The RadioReference database does not currently show the RR user GPS data for State, County, Agency, or System in any of the online user reports. For example, if you were to review the online report for any conventional frequency subcategory data, if there is no data entered for that subcategory you will see absolutely no data (inherited data is not shown online.) All data values are processed and provided to third party applications using the RadioReference Web Service [[API]] with an indication if it is an inherited or native value. The inherit feature/function will appear to the end user as if it can only be seen by third party applications.<br />
<br />
The RadioReference database is by no means complete, but it has the capability to store all of the info necessary for Location-based Scanning. You can cut and paste the info from the database for free, but to download this information directly into your scanner you will need a third party software that is capable of connecting to RadioReference and you will need a [http://www.radioreference.com/apps/subscription/ paid subscription] to RadioReference.com website for access.<br />
<br />
===Using third party software with the GPS features===<br />
<br />
Most importantly you will simply want to understand the capabilities of the scanners ability to store GPS data compared to the fields that are used by the [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service RadioReference Web Service] to interface with third party software that connects to the database and extracts useable data. <br />
<br />
For HP-1 users, it is not required to interface or access RadioReference directly. While you can download data and GPS coordinates, Uniden provides HP-1 owners with weekly updates for no charge via the Sentinel software. Uniden extracts data from RadioReference and tweaks it for the HP-1 radio. For all other scanners, some of the DMA supported applications are Location-Based scanning capable.<br />
<br />
* RR Wiki: [[Uniden_DMA_Software_Support]]<br />
<br />
It is important to make sure the software you have selected uses the ‘inherit’ feature capability if you expect to download accurate GPS data. Each time RadioReference changes the structure of its database they release a set of code or instructions, [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service3.1 Simple Object Access Protocol (SOAP)], to third party vendors so they can utilize any new features. <br />
The “inherit” capabilities were released in version 8 of the SOAP RadioReference Web Service. The current release is version 9 and many third party software vendors are using release 9 or in the process of upgrading their programs to be compatible. If you are not sure, or you are downloading unexpected GPS data that doesn’t match what you expect or what is in the RadioReference database, ask the vendor of the software product you have selected.<br />
<br />
Third party software using older versions of the Radio Reference Web Service can cause missing and/or erroneous location-based data to be downloaded. In addition, programs that are designed to program a variety of scanners may be misleading you as to where the data is being stored or used; it is possible that the program is downloading data in one location that would be used with XT models and data in another location that would be used with other models, etc. Without a good knowledge of the scanners and data explained above, even the experienced user can easily be confused.<br />
<br />
The XT model scanners are capable of storing coordinates with each Trunked Radio Site within a system (this can be single site systems or multi-site systems) and within each set or “GROUP” of Talk Group ID’s (TGID) within a system. The XT models also can store coordinates for a set or “GROUP” of frequencies within a conventional system. The non-XT models handle coordinates differently and do not store GPS coordinates at the TGID level, you can only segment by trunk site. For the conventional entries on the non-XT models the GPS data is stored at the conventional system level, not the group level – which may or may not be the same depending on what you have programmed. In either cases data is retrieved from RadioReference the same for both scanner types. (For the Home Patrol, this is transparent to the user since it is translated to the Home Patrol database by Uniden on a weekly basis.)<br />
<br />
Someday, ‘seamless’ GPS scanning may be a reality. For now, the data in the RadioReference database is only as good as what scanner enthusiasts populate into the database and the capabilities of the software/hardware using the data. The completeness of the database is evolving only as fast as users are adding data. To this accord, there may be cases where you want to enter your own data directly into the third party software before uploading to your scanner. However, where possible you should update the database if you can.<br />
<br />
Most of the third party programs that handle location-based scanning have some sort of tools for viewing maps and searching locations necessary for programming locations. While the focus of this article has been how to understand the data that is downloaded from RadioReference automatically, there are some advantages to programming locations on your own.<br />
<br />
===Tips / Tricks for more effective location-based scanning===<br />
<br />
Not every city is the shape of a circle or is of moderate size. You may need to consider custom shapes and large listening areas when programming your scanner. As briefly suggested in the overview Wiki linked at the beginning of this page, you can create a duplicate site with a different radius to make an oblong entity. Essentially, the scanner narrows and expands the coverage area by scanning the same site twice (but it doesn’t slow the scan rotation enough to be noticeable to the end user since it only scans twice in overlap areas.) Your scanner also needs to be able to handle large geographical areas for statewide and nationwide channels in a scan rotation.<br />
<br />
#A custom shaped listening area can be as simple as an oblong shape or it can accommodate the rare instance you may monitor a system that operates in two simulcast locations separated by a long distance. As a complex example, imagine a large military simulcast system with more than one base or campus. Your main listening area is base A & B & C (or however many campus locations.) Instead of drawing a large radius around the 3 campus locations you could create multiple sites for each location and have a radius for each that only covers the specific campus. If the military police travel one or two miles down certain roads to get from point A to point B, you can create more sites with smaller radius that follow the roads, essentially giving you location-based scanning coverage of just the areas in which the military police operate, the 3 main campuses and the roads in between.<br />
#Statewide systems, depending on your state, may need to have custom shapes defined. GPS data for states in the radio reference database are all based on a perfect circle surrounding an entire state. In rare cases for statewide agencies listed in the database the agency may inherit the statewide coordinates if there are no agency, county, or subcategory coordinates entered in the database. However, you must be aware that the XT model scanners are only capable of storing a radius of up to 125 miles and the other models are only capable of up to 50 miles radius. If you live in an average or larger size state, you will likely encounter these limits. (Similarly, note that the third party software programs may round up or down and any radius under 1.0 may get rounded to 0 depending on the program you are using.) Hence, the data stored in the RadioReference database may not be useable in your scanner and may not be processed correctly by your third party software. In this case you can duplicate entries with different radius information to cover a large area – similar to the tip / trick above for odd shape sites.<br />
#Nationwide frequencies listed in the RR are now able to be downloaded into many third party software programs. All of the Nationwide frequencies have a center point in the middle of the US and a range of 1800 miles. While the scanners have limitations on the range of a frequency, site or system, it would be memory prohibitive to draw many circles and enter duplicate entries for any Nationwide channels. You can always tell the software not to scan a particular entry using GPS. You will want to set all Nationwide frequencies to scan all the time, and you can manually lock them out if you need to. They will be active wherever you go (which is how scanning used to work anyhow, remember?)<br />
<br />
In the future, both the RadioReference database and some scanners will also have the option of using multiple rectangles to define areas for a single entry, but for now using duplicate entries with different radiuses is the only way to create your own custom shaped listening area. (The HP-1 already can use rectangles, but no support is available in RadioReference yet.) As location-based scanning popularity grows, the number of users submitting changes and updates to the database will increase and the data will become more robust and accurate.<br />
<br />
<br><br />
----<br />
<br><br />
Location-based scanning can be as simple or complex as you want it to be. If you live in a major metropolitan area you can detail most Uniden scanners for your listening enjoyment to precisely where you are at any given moment. If you travel cross country you can attach GPS to your Uniden Home Patrol and drive from coast to coast without reprogramming and without missing the local action along the way.<br />
<br><br><br />
[[Category:RR Glossary]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Location_Based_Scanning&diff=86234Location Based Scanning2011-10-25T13:42:29Z<p>Loumaag: /* Understanding GPS data in the RadioReference database */ Clarifying difference between WebSite and SOAP</p>
<hr />
<div>== Overview ==<br />
<br />
'''Location-based scanning''' is a patented function of certain Uniden DMA scanners. (US Patents 6,192,233 and 9,941,120.)<br />
*RR Wiki: [[Uniden_DMA_FAQ]]<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features]]<br />
<br />
According to Uniden, location-based scanning allows you to control which systems/sites and channel groups are scanned based on your exact location. This frees you from having to manually enable and disable systems or channel groups as you change location. Specifically, location-based scanning uses the scanners lockout function to control what is scanned based on your location. It unlocks systems, sites, or channel groups when you are inside an element's radius. When you exit the radius, the element is temporarily locked out.<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/LocationBasedScanning Location Based Scanning]<br />
<br />
Uniden scanners [[BCD996T]], [[BCT15]], [[BCT15X]] and all XT models ([[BC346XT]], [[BCD396XT]], [[BCD996XT]]) support location-based scanning. The Uniden [[HomePatrol-1]] (HP-1) also supports location-based scanning, with the added feature of Zip-Code control. The HomePatrol-1 has the ability to let you set your location using a Zip-Code, but the Zip-Code itself is not used (it is converted to GPS coordinates, which are used for determining what will be scanned.) <br />
<br />
The HP-1 comes preloaded with the entire RadioReference database and users can enter a Zip-Code, a range in miles, and the types of services they want to hear. Within seconds users can be listening to all Police Dispatch calls within a 5 miles range of downtown Indianapolis, etc.<br />
<br />
*HomePatrol Blog: [http://www.homepatrol.com/index.php?option=com_content&view=article&id=17 Location, Location, Location]<br />
<br />
The scanners do not have a GPS receiver built-in, you must purchase an aftermarket GPS device compatible with your scanner. Details for connecting a GPS receiver vary by scanner. Compatible GPS devices all use the common DB9 serial type connection. For the mobile models (BCT15, BCD996T, BCT15X, BCD996XT) you can connect directly to the rear port of the scanner. For the portable scanners (BC346XT and BCD396XT) you can use the data cable that was supplied with the scanner. Some installations may require a gender changer to mate DB-9 connections. In the case of either portable scanner, if you use the cable that came with the scanner a null modem/gender changer is a requirement. A null modem adapter is not required if you purchase the optional GPS adapter cable designed for use with the HP-1 and other DMA scanners. <br />
<br />
*RR Wiki [[Uniden_Scanner_GPS_Features#Compatible_GPS_receivers|Compatible GPS Receivers]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ConnectingAGpsReceiver Connecting A GPS Receiver]<br />
<br />
The GPS function of your scanner can be used for more than just controlling what you listen to. For example, you can enter, store and have the scanner alert you to dangerous intersections or when you are going too fast, etc. These are commonly referred to as location alert functions.<br />
<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features#Non-Radio_Location-Based_GPS_Features|Non-Radio Location Based GPS Features]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/GPSMode GPS Mode]<br />
<br />
In addition to the basic GPS functions, for every entry you want to monitor with your scanner, you can program a set of criteria using GPS coordinates and a range. (In the case of the HP-1, this comes already pre-programmed or you can program any entity yourself.) To better understand how this works, you should become familiar with how to program your scanner with third party software. You can program manually, but it can be more difficult and time consuming. This article does not cover how to program entities (frequencies or systems) into your scanner, rather the concept and understanding of programming locations with an entity or alert function.<br />
<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ProgrammingLocations Programming Locations]<br />
<br />
===Understanding GPS data in the RadioReference database===<br />
<br />
In addition to being familiar with your scanner and an understanding of programming locations (described above) you should have a general understanding of where RadioReference stores location data with its radio data that can be downloaded by third party software.<br />
<br />
While it is not necessary to know the specific names of all data fields, currently the RadioReference database stores location data in several database fields that are not used for Location-based scanning, such as: Zip-Code info and FCC location, etc. For example, when you review any agency info in the database if you click on the FCC license call sign the GPS coordinates registered with the FCC will sometimes be shown. This data is not what is used for location based scanning.<br />
<br />
It is very helpful to be aware of the RadioReference database fields that match up to what can be used in the scanners. Each description below is followed by a sample link where RadioReference users can view specific types of data online in report format. The following fields correspond directly to the data used in the scanners.<br />
<br />
<blockquote>'''''Trunked System site''''' – a trunking site can have specific location data assigned to it. If none is specified, then it inherits the location data based on the county that it is located in. (Note: This is different from what is presented on the Web Site DB interface.) If no county is defined for the site, the site inherits the trunked system default location data. The name of the field used by the third party software is called '''TrsSite''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=7&sid=2856 http://www.radioreference.com/apps/db/?rpt=7&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Trunked System Talkgroup category''''' – a talkgroup category can have specific location data assigned to it. If none is specified, it inherits the trunked system default location data. The name of the field used by the third party software is called '''TalkgroupCat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=8&sid=2856 http://www.radioreference.com/apps/db/?rpt=8&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Frequency Subcategory''''' - a conventional frequency subcategory can have specific location data assigned to it. If no location data is specified for the frequency subcategory, then it inherits location data from the parent agency or county. The name of the field used by the third party software is called '''subcat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=6&ctid=255 http://www.radioreference.com/apps/db/?rpt=6&ctid=XXXX]<br><br><br />
[http://www.radioreference.com/apps/db/?action=locPop&scid=4872 http://www.radioreference.com/apps/db/?action=locPop&scid=XXXX]<br />
</blockquote></blockquote><br />
<br />
RadioReference members can submit data for any of these fields where there is none or where there are errors. (Remember, if you are submitting data, that the coordinates and range should be entered for the intended useable area, not the coverage area. For example, if Agency XYZ has a 300 watt repeater that you can hear for miles away from the city, the intended usable area is more likely to be the agency boundary of the city or county. When submitting data to the database you would enter the radius necessary to cover the city or county, not a larger radius to cover the capable listening area of the transmitter.) Users who desire to add [[Location_Based_Info]] should become very familiar with [[RR_Database_Submission_Guidelines]] before submitting changes to the RadioReference database.<br />
<br />
The descriptions of the fields described above make reference to ‘inheriting’ data from higher levels of the database. There are multiple fields that the RadioReference User cannot see by looking at the database online. The key fields relevant to location-based scanning that you cannot see are as follows:<br />
# '''''State''''' – a state can have location data assigned to it that serves as a default set of location data for the state or for state agencies.<br />
# '''''County''''' – a county can have location data assigned to it that serves as a default set of location data for the county. <br />
# '''''Agency''''' – an agency can have location data assigned to it that serves as a default set of location data for the agency. <br />
# '''''Trunk System''''' – a trunked system can have location data assigned to it that serves as a default set of location data for the entire system.<br />
<br />
The RadioReference database does not currently show the RR user GPS data for State, County, Agency, or System in any of the online user reports. For example, if you were to review the online report for any conventional frequency subcategory data, if there is no data entered for that subcategory you will see absolutely no data (inherited data is not shown online.) All data values are processed and provided to third party applications using the RadioReference Web Service [[API]] with an indication if it is an inherited or native value. The inherit feature/function will appear to the end user as if it can only be seen by third party applications.<br />
<br />
The RadioReference database is by no means complete, but it has the capability to store all of the info necessary for Location-based Scanning. You can cut and paste the info from the database for free, but to download this information directly into your scanner you will need a third party software that is capable of connecting to RadioReference and you will need a [http://www.radioreference.com/apps/subscription/ paid subscription] to RadioReference.com website for access.<br />
<br />
===Using third party software with the GPS features===<br />
<br />
Most importantly you will simply want to understand the capabilities of the scanners ability to store GPS data compared to the fields that are used by the [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service RadioReference Web Service] to interface with third party software that connects to the database and extracts useable data. <br />
<br />
For HP-1 users, it is not required to interface or access RadioReference directly. While you can download data and GPS coordinates, Uniden provides HP-1 owners with weekly updates for no charge via the Sentinel software. Uniden extracts data from RadioReference and tweaks it for the HP-1 radio. For all other scanners, some of the DMA supported applications are Location-Based scanning capable.<br />
<br />
* RR Wiki: [[Uniden_DMA_Software_Support]]<br />
<br />
It is important to make sure the software you have selected uses the ‘inherit’ feature capability if you expect to download accurate GPS data. Each time RadioReference changes the structure of its database they release a set of code or instructions, [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service3.1 Simple Object Access Protocol (SOAP)], to third party vendors so they can utilize any new features. <br />
The “inherit” capabilities were released in version 8 of the SOAP RadioReference Web Service. The current release is version 9 and many third party software vendors are using release 9 or in the process of upgrading their programs to be compatible. If you are not sure, or you are downloading unexpected GPS data that doesn’t match what you expect or what is in the RadioReference database, ask the vendor of the software product you have selected.<br />
<br />
Third party software using older versions of the Radio Reference Web Service can cause missing and/or erroneous location-based data to be downloaded. In addition, programs that are designed to program a variety of scanners may be misleading you as to where the data is being stored or used; it is possible that the program is downloading data in one location that would be used with XT models and data in another location that would be used with other models, etc. Without a good knowledge of the scanners and data explained above, even the experienced user can easily be confused.<br />
<br />
The XT model scanners are capable of storing coordinates with each Trunked Radio Site within a system (this can be single site systems or multi-site systems) and within each set or “GROUP” of Talk Group ID’s (TGID) within a system. The XT models also can store coordinates for a set or “GROUP” of frequencies within a conventional system. The non-XT models handle coordinates differently and do not store GPS coordinates at the TGID level, you can only segment by trunk site. For the conventional entries on the non-XT models the GPS data is stored at the conventional system level, not the group level – which may or may not be the same depending on what you have programmed. In either cases data is retrieved from RadioReference the same for both scanner types. (For the Home Patrol, this is transparent to the user since it is translated to the Home Patrol database by Uniden on a weekly basis.)<br />
<br />
Someday, ‘seamless’ GPS scanning may be a reality. For now, the data in the RadioReference database is only as good as what scanner enthusiasts populate into the database and the capabilities of the software/hardware using the data. The completeness of the database is evolving only as fast as users are adding data. To this accord, there may be cases where you want to enter your own data directly into the third party software before uploading to your scanner. However, where possible you should update the database if you can.<br />
<br />
Most of the third party programs that handle location-based scanning have some sort of tools for viewing maps and searching locations necessary for programming locations. While the focus of this article has been how to understand the data that is downloaded from RadioReference automatically, there are some advantages to programming locations on your own.<br />
<br />
===Tips / Tricks for more effective location-based scanning===<br />
<br />
Not every city is the shape of a circle or is of moderate size. You may need to consider custom shapes and large listening areas when programming your scanner. As briefly suggested in the overview Wiki linked at the beginning of this page, you can create a duplicate site with a different radius to make an oblong entity. Essentially, the scanner narrows and expands the coverage area by scanning the same site twice (but it doesn’t slow the scan rotation enough to be noticeable to the end user since it only scans twice in overlap areas.) Your scanner also needs to be able to handle large geographical areas for statewide and nationwide channels in a scan rotation.<br />
<br />
#A custom shaped listening area can be as simple as an oblong shape or it can accommodate the rare instance you may monitor a system that operates in two simulcast locations separated by a long distance. As a complex example, imagine a large military simulcast system with more than one base or campus. Your main listening area is base A & B & C (or however many campus locations.) Instead of drawing a large radius around the 3 campus locations you could create multiple sites for each location and have a radius for each that only covers the specific campus. If the military police travel one or two miles down certain roads to get from point A to point B, you can create more sites with smaller radius that follow the roads, essentially giving you location-based scanning coverage of just the areas in which the military police operate, the 3 main campuses and the roads in between.<br />
#Statewide systems, depending on your state, may need to have custom shapes defined. GPS data for states in the radio reference database are all based on a perfect circle surrounding an entire state. In rare cases for statewide agencies listed in the database the agency may inherit the statewide coordinates if there are no agency, county, or subcategory coordinates entered in the database. However, you must be aware that the XT model scanners are only capable of storing a radius of up to 125 miles and the other models are only capable of up to 50 miles radius. If you live in an average or larger size state, you will likely encounter these limits. (Similarly, note that the third party software programs may round up or down and any radius under 1.0 may get rounded to 0 depending on the program you are using.) Hence, the data stored in the RadioReference database may not be useable in your scanner and may not be processed correctly by your third party software. In this case you can duplicate entries with different radius information to cover a large area – similar to the tip / trick above for odd shape sites.<br />
#Nationwide frequencies listed in the RR are now able to be downloaded into many third party software programs. All of the Nationwide frequencies have a center point in the middle of the US and a range of 1800 miles. While the scanners have limitations on the range of a frequency, site or system, it would be memory prohibitive to draw many circles and enter duplicate entries for any Nationwide channels. You can always tell the software not to scan a particular entry using GPS. You will want to set all Nationwide frequencies to scan all the time, and you can manually lock them out if you need to. They will be active wherever you go (which is how scanning used to work anyhow, remember?)<br />
<br />
In the future, both the RadioReference database and some scanners will also have the option of using multiple rectangles to define areas for a single entry, but for now using duplicate entries with different radiuses is the only way to create your own custom shaped listening area. (The HP-1 already can use rectangles, but no support is available in RadioReference yet.) As location-based scanning popularity grows, the number of users submitting changes and updates to the database will increase and the data will become more robust and accurate.<br />
<br />
<br><br />
----<br />
<br><br />
Location-based scanning can be as simple or complex as you want it to be. If you live in a major metropolitan area you can detail most Uniden scanners for your listening enjoyment to precisely where you are at any given moment. If you travel cross country you can attach GPS to your Uniden Home Patrol and drive from coast to coast without reprogramming and without missing the local action along the way.<br />
<br><br><br />
[[Category:RR Glossary]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Location_Based_Scanning&diff=86157Location Based Scanning2011-10-21T14:47:16Z<p>Loumaag: /* Understanding GPS data in the RadioReference database */ Corrected Site location inheritance.</p>
<hr />
<div>== Overview ==<br />
<br />
'''Location-based scanning''' is a patented function of certain Uniden DMA scanners. (US Patents 6,192,233 and 9,941,120.)<br />
*RR Wiki: [[Uniden_DMA_FAQ]]<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features]]<br />
<br />
According to Uniden, location-based scanning allows you to control which systems/sites and channel groups are scanned based on your exact location. This frees you from having to manually enable and disable systems or channel groups as you change location. Specifically, location-based scanning uses the scanners lockout function to control what is scanned based on your location. It unlocks systems, sites, or channel groups when you are inside an element's radius. When you exit the radius, the element is temporarily locked out.<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/LocationBasedScanning Location Based Scanning]<br />
<br />
Uniden scanners [[BCD996T]], [[BCT15]], [[BCT15X]] and all XT models ([[BC346XT]], [[BCD396XT]], [[BCD996XT]]) support location-based scanning. The Uniden [[HomePatrol-1]] (HP-1) also supports location-based scanning, with the added feature of Zip-Code control. The HomePatrol-1 has the ability to let you set your location using a Zip-Code, but the Zip-Code itself is not used (it is converted to GPS coordinates, which are used for determining what will be scanned.) <br />
<br />
The HP-1 comes preloaded with the entire RadioReference database and users can enter a Zip-Code, a range in miles, and the types of services they want to hear. Within seconds users can be listening to all Police Dispatch calls within a 5 miles range of downtown Indianapolis, etc.<br />
<br />
*HomePatrol Blog: [http://www.homepatrol.com/index.php?option=com_content&view=article&id=17 Location, Location, Location]<br />
<br />
The scanners do not have a GPS receiver built-in, you must purchase an aftermarket GPS device compatible with your scanner. Details for connecting a GPS receiver vary by scanner. Compatible GPS devices all use the common DB9 serial type connection. For the mobile models (BCT15, BCD996T, BCT15X, BCD996XT) you can connect directly to the rear port of the scanner. For the portable scanners (BC346XT and BCD396XT) you can use the data cable that was supplied with the scanner. Some installations may require a gender changer to mate DB-9 connections. In the case of either portable scanner, if you use the cable that came with the scanner a null modem/gender changer is a requirement. A null modem adapter is not required if you purchase the optional GPS adapter cable designed for use with the HP-1 and other DMA scanners. <br />
<br />
*RR Wiki [[Uniden_Scanner_GPS_Features#Compatible_GPS_receivers|Compatible GPS Receivers]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ConnectingAGpsReceiver Connecting A GPS Receiver]<br />
<br />
The GPS function of your scanner can be used for more than just controlling what you listen to. For example, you can enter, store and have the scanner alert you to dangerous intersections or when you are going too fast, etc. These are commonly referred to as location alert functions.<br />
<br />
*RR Wiki: [[Uniden_Scanner_GPS_Features#Non-Radio_Location-Based_GPS_Features|Non-Radio Location Based GPS Features]]<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/GPSMode GPS Mode]<br />
<br />
In addition to the basic GPS functions, for every entry you want to monitor with your scanner, you can program a set of criteria using GPS coordinates and a range. (In the case of the HP-1, this comes already pre-programmed or you can program any entity yourself.) To better understand how this works, you should become familiar with how to program your scanner with third party software. You can program manually, but it can be more difficult and time consuming. This article does not cover how to program entities (frequencies or systems) into your scanner, rather the concept and understanding of programming locations with an entity or alert function.<br />
<br />
*Uniden TWiki: [http://info.uniden.com/twiki/bin/view/UnidenMan4/ProgrammingLocations Programming Locations]<br />
<br />
===Understanding GPS data in the RadioReference database===<br />
<br />
In addition to being familiar with your scanner and an understanding of programming locations (described above) you should have a general understanding of where RadioReference stores location data with its radio data that can be downloaded by third party software.<br />
<br />
While it is not necessary to know the specific names of all data fields, currently the RadioReference database stores location data in several database fields that are not used for Location-based scanning, such as: Zip-Code info and FCC location, etc. For example, when you review any agency info in the database if you click on the FCC license call sign the GPS coordinates registered with the FCC will sometimes be shown. This data is not what is used for location based scanning.<br />
<br />
It is very helpful to be aware of the RadioReference database fields that match up to what can be used in the scanners. Each description below is followed by a sample link where RadioReference users can view specific types of data online in report format. The following fields correspond directly to the data used in the scanners.<br />
<br />
<blockquote>'''''Trunked System site''''' – a trunking site can have specific location data assigned to it. If none is specified, the site inherits the trunked system default location data. The name of the field used by the third party software is called '''TrsSite''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=7&sid=2856 http://www.radioreference.com/apps/db/?rpt=7&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Trunked System Talkgroup category''''' – a talkgroup category can have specific location data assigned to it. If none is specified, it inherits the trunked system default location data. The name of the field used by the third party software is called '''TalkgroupCat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=8&sid=2856 http://www.radioreference.com/apps/db/?rpt=8&sid=XXXX]<br />
</blockquote></blockquote><br />
<br />
<blockquote>'''''Frequency Subcategory''''' - a conventional frequency subcategory can have specific location data assigned to it. If no location data is specified for the frequency subcategory, then it inherits location data from the parent agency or county. The name of the field used by the third party software is called '''subcat''' <blockquote>[http://www.radioreference.com/apps/db/?rpt=6&ctid=255 http://www.radioreference.com/apps/db/?rpt=6&ctid=XXXX]<br><br><br />
[http://www.radioreference.com/apps/db/?action=locPop&scid=4872 http://www.radioreference.com/apps/db/?action=locPop&scid=XXXX]<br />
</blockquote></blockquote><br />
<br />
RadioReference members can submit data for any of these fields where there is none or where there are errors. (Remember, if you are submitting data, that the coordinates and range should be entered for the intended useable area, not the coverage area. For example, if Agency XYZ has a 300 watt repeater that you can hear for miles away from the city, the intended usable area is more likely to be the agency boundary of the city or county. When submitting data to the database you would enter the radius necessary to cover the city or county, not a larger radius to cover the capable listening area of the transmitter.) Users who desire to add [[Location_Based_Info]] should become very familiar with [[RR_Database_Submission_Guidelines]] before submitting changes to the RadioReference database.<br />
<br />
The descriptions of the fields described above make reference to ‘inheriting’ data from higher levels of the database. There are multiple fields that the RadioReference User cannot see by looking at the database online. The key fields relevant to location-based scanning that you cannot see are as follows:<br />
# '''''State''''' – a state can have location data assigned to it that serves as a default set of location data for the state or for state agencies.<br />
# '''''County''''' – a county can have location data assigned to it that serves as a default set of location data for the county. <br />
# '''''Agency''''' – an agency can have location data assigned to it that serves as a default set of location data for the agency. <br />
# '''''Trunk System''''' – a trunked system can have location data assigned to it that serves as a default set of location data for the entire system.<br />
<br />
The RadioReference database does not currently show the RR user GPS data for State, County, Agency, or System in any of the online user reports. For example, if you were to review the online report for any conventional frequency subcategory data, if there is no data entered for that subcategory you will see absolutely no data (inherited data is not shown online.) All data values are processed and provided to third party applications using the RadioReference Web Service [[API]] with an indication if it is an inherited or native value. The inherit feature/function will appear to the end user as if it can only be seen by third party applications.<br />
<br />
The RadioReference database is by no means complete, but it has the capability to store all of the info necessary for Location-based Scanning. You can cut and paste the info from the database for free, but to download this information directly into your scanner you will need a third party software that is capable of connecting to RadioReference and you will need a [http://www.radioreference.com/apps/subscription/ paid subscription] to RadioReference.com website for access.<br />
<br />
===Using third party software with the GPS features===<br />
<br />
Most importantly you will simply want to understand the capabilities of the scanners ability to store GPS data compared to the fields that are used by the [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service RadioReference Web Service] to interface with third party software that connects to the database and extracts useable data. <br />
<br />
For HP-1 users, it is not required to interface or access RadioReference directly. While you can download data and GPS coordinates, Uniden provides HP-1 owners with weekly updates for no charge via the Sentinel software. Uniden extracts data from RadioReference and tweaks it for the HP-1 radio. For all other scanners, some of the DMA supported applications are Location-Based scanning capable.<br />
<br />
* RR Wiki: [[Uniden_DMA_Software_Support]]<br />
<br />
It is important to make sure the software you have selected uses the ‘inherit’ feature capability if you expect to download accurate GPS data. Each time RadioReference changes the structure of its database they release a set of code or instructions, [http://wiki.radioreference.com/index.php/RadioReference.com_Web_Service3.1 Simple Object Access Protocol (SOAP)], to third party vendors so they can utilize any new features. <br />
The “inherit” capabilities were released in version 8 of the SOAP RadioReference Web Service. The current release is version 9 and many third party software vendors are using release 9 or in the process of upgrading their programs to be compatible. If you are not sure, or you are downloading unexpected GPS data that doesn’t match what you expect or what is in the RadioReference database, ask the vendor of the software product you have selected.<br />
<br />
Third party software using older versions of the Radio Reference Web Service can cause missing and/or erroneous location-based data to be downloaded. In addition, programs that are designed to program a variety of scanners may be misleading you as to where the data is being stored or used; it is possible that the program is downloading data in one location that would be used with XT models and data in another location that would be used with other models, etc. Without a good knowledge of the scanners and data explained above, even the experienced user can easily be confused.<br />
<br />
The XT model scanners are capable of storing coordinates with each Trunked Radio Site within a system (this can be single site systems or multi-site systems) and within each set or “GROUP” of Talk Group ID’s (TGID) within a system. The XT models also can store coordinates for a set or “GROUP” of frequencies within a conventional system. The non-XT models handle coordinates differently and do not store GPS coordinates at the TGID level, you can only segment by trunk site. For the conventional entries on the non-XT models the GPS data is stored at the conventional system level, not the group level – which may or may not be the same depending on what you have programmed. In either cases data is retrieved from RadioReference the same for both scanner types. (For the Home Patrol, this is transparent to the user since it is translated to the Home Patrol database by Uniden on a weekly basis.)<br />
<br />
Someday, ‘seamless’ GPS scanning may be a reality. For now, the data in the RadioReference database is only as good as what scanner enthusiasts populate into the database and the capabilities of the software/hardware using the data. The completeness of the database is evolving only as fast as users are adding data. To this accord, there may be cases where you want to enter your own data directly into the third party software before uploading to your scanner. However, where possible you should update the database if you can.<br />
<br />
Most of the third party programs that handle location-based scanning have some sort of tools for viewing maps and searching locations necessary for programming locations. While the focus of this article has been how to understand the data that is downloaded from RadioReference automatically, there are some advantages to programming locations on your own.<br />
<br />
===Tips / Tricks for more effective location-based scanning===<br />
<br />
Not every city is the shape of a circle or is of moderate size. You may need to consider custom shapes and large listening areas when programming your scanner. As briefly suggested in the overview Wiki linked at the beginning of this page, you can create a duplicate site with a different radius to make an oblong entity. Essentially, the scanner narrows and expands the coverage area by scanning the same site twice (but it doesn’t slow the scan rotation enough to be noticeable to the end user since it only scans twice in overlap areas.) Your scanner also needs to be able to handle large geographical areas for statewide and nationwide channels in a scan rotation.<br />
<br />
#A custom shaped listening area can be as simple as an oblong shape or it can accommodate the rare instance you may monitor a system that operates in two simulcast locations separated by a long distance. As a complex example, imagine a large military simulcast system with more than one base or campus. Your main listening area is base A & B & C (or however many campus locations.) Instead of drawing a large radius around the 3 campus locations you could create multiple sites for each location and have a radius for each that only covers the specific campus. If the military police travel one or two miles down certain roads to get from point A to point B, you can create more sites with smaller radius that follow the roads, essentially giving you location-based scanning coverage of just the areas in which the military police operate, the 3 main campuses and the roads in between.<br />
#Statewide systems, depending on your state, may need to have custom shapes defined. GPS data for states in the radio reference database are all based on a perfect circle surrounding an entire state. In rare cases for statewide agencies listed in the database the agency may inherit the statewide coordinates if there are no agency, county, or subcategory coordinates entered in the database. However, you must be aware that the XT model scanners are only capable of storing a radius of up to 125 miles and the other models are only capable of up to 50 miles radius. If you live in an average or larger size state, you will likely encounter these limits. (Similarly, note that the third party software programs may round up or down and any radius under 1.0 may get rounded to 0 depending on the program you are using.) Hence, the data stored in the RadioReference database may not be useable in your scanner and may not be processed correctly by your third party software. In this case you can duplicate entries with different radius information to cover a large area – similar to the tip / trick above for odd shape sites.<br />
#Nationwide frequencies listed in the RR are now able to be downloaded into many third party software programs. All of the Nationwide frequencies have a center point in the middle of the US and a range of 1800 miles. While the scanners have limitations on the range of a frequency, site or system, it would be memory prohibitive to draw many circles and enter duplicate entries for any Nationwide channels. You can always tell the software not to scan a particular entry using GPS. You will want to set all Nationwide frequencies to scan all the time, and you can manually lock them out if you need to. They will be active wherever you go (which is how scanning used to work anyhow, remember?)<br />
<br />
In the future, both the RadioReference database and some scanners will also have the option of using multiple rectangles to define areas for a single entry, but for now using duplicate entries with different radiuses is the only way to create your own custom shaped listening area. (The HP-1 already can use rectangles, but no support is available in RadioReference yet.) As location-based scanning popularity grows, the number of users submitting changes and updates to the database will increase and the data will become more robust and accurate.<br />
<br />
<br><br />
----<br />
<br><br />
Location-based scanning can be as simple or complex as you want it to be. If you live in a major metropolitan area you can detail most Uniden scanners for your listening enjoyment to precisely where you are at any given moment. If you travel cross country you can attach GPS to your Uniden Home Patrol and drive from coast to coast without reprogramming and without missing the local action along the way.<br />
<br><br><br />
[[Category:RR Glossary]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Common_Public_Safety&diff=85267Common Public Safety2011-09-21T12:48:19Z<p>Loumaag: added a couple more DB sub cat references</p>
<hr />
<div>== Nationwide Public Safety Interoperability Channels ==<br />
'''See: [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels] and [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide]'''<br />
<br />
'''Some states, regional and local areas have their own interoperability or mutual aid channels or trunked system talkgroups which are used instead of, or in addition to, those listed below.'''<br />
<br />
'''In some areas the channels listed below may have different channel names, tones, etc. or be used for different purposes.'''<br />
<br />
* State and regional frequencies are usually found on the ''Common/Shared'' or ''Statewide'' drop-down list on the main [http://www.radioreference.com/apps/db/ RadioReference Database] page for each state.<br />
* Interoperability channel plans are often published on various state government web sites. See links at the bottom of this page.<br />
* In analog mode all end user radios should transmit PL 156.7 (136.5 for high band temporary repeaters, 167.9 for NITA channels) and receive CSQ (carrier squelch) unless PL decode is necessary due to interference.<br />
* In APCO P25 dgital mode all radios should use NAC $293 (NAC $68F for NTIA channels).<br />
<br />
=== VHF ===<br />
==== VHF Low Band ====<br />
<freqsubcat> 64465</freqsubcat><br />
<br />
==== VHF High Band ====<br />
<freqsubcat> 64466</freqsubcat><br />
<br />
==== VHF NTIA Law Enforcement ====<br />
<freqsubcat>64500</freqsubcat><br />
<br />
==== VHF NTIA Incident Response ====<br />
<freqsubcat>64502</freqsubcat><br />
Notes<br />
* (1) VTAC17 and VTAC17D are VHF marine band channels and their use is limited to inland [http://www.fcc.gov/oet/info/maps/areas/maps/vpc.pdf VHF Public Coast Station Areas (VPCSA)] 10 through 42.<br />
* (2) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== UHF ===<br />
==== UHF Public Safety ====<br />
<freqsubcat> 64468</freqsubcat><br />
<br />
==== UHF NTIA Law Enforcement ====<br />
<freqsubcat>64501</freqsubcat><br />
<br />
==== UHF NTIA Incident Response ====<br />
<freqsubcat>64503</freqsubcat><br />
Notes<br />
* (1) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== 700 MHz ===<br />
<freqsubcat>64470</freqsubcat><br />
<br />
=== 800 MHz ===<br />
<freqsubcat>64471</freqsubcat><br />
<br />
<br />
== 700 MHz Low Power/Itinerant ==<br />
* The following narrowband channels (12.5 kHz) are designated for low power use for on-scene incident response purposes using mobiles and portables.<br />
* Transmitter power must not exceed 2 watts (ERP)<br />
* Three of the pairs can be licensed for nationwide itinerant use, the rest are subject to regional planning.<br />
<freqsubcat> 64498</freqsubcat><br />
<br />
<br />
== [[Disaster Relief]] ==<br />
<br />
===American Red Cross===<br />
====VHF Low====<br />
<freqsubcat>52358</freqsubcat><br />
====VHF High====<br />
<freqsubcat>52360</freqsubcat><br />
<br />
== [[Emergency Medical Services Radio]] ==<br />
<freqsubcat>64545</freqsubcat><br />
<br />
== Law Enforcement ==<br />
<freqsubcat>64547</freqsubcat><br />
* 155.370 is used as a law enforcement intersystem frequency used in many states and is often called "Point-to-Point". The FCC rule designation was removed in recent years.<br />
* 155.475 and 155.4825 are available nationwide for use in police emergency communications networks operated under statewide law enforcement emergency communications plans. 155.475 is often called "National Law Enforcement Mutual Aid"<br />
<br />
== [[National Incident Radio Support Cache]] ==<br />
== Search and Rescue ==<br />
<freqsubcat>64544</freqsubcat><br />
<br />
==Related Links ==<br />
=== References ===<br />
* [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels]<br />
* [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide (NIFOG) v 1.4] - Page also has programming guide and programming template (Excel spreadsheet).<br />
* [http://www.npstc.org/channelNaming.jsp NPSTC interoperability channel name standardization]<br />
* [http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1621A1.pdf FCC DA-01-1621 Federal Government Spectrum Available for Public Safety Interoperability Communications]<br />
* [http://www.fcc.gov/pshs/ FCC Public Safety & Homeland Security Bureau]<br />
** [http://transition.fcc.gov/pshs/techtopics/techtopics12.html Topic 12: National Interoperability Channels]<br />
* [http://www.apcointl.org/frequency/interoperability.php APCO Interoperability Resources]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr;sid=17215d8c8052bfef50e5299b335bd82c;rgn=div8;view=text;node=47%3A5.0.1.1.3.2.110.4;idno=47;cc=ecfr 47CFR90.20 Public Safety Pool Frequency Table]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=17215d8c8052bfef50e5299b335bd82c&rgn=div8&view=text&node=47:5.0.1.1.3.17.114.7&idno=47 47CFR90.531 Public Safety 700 MHz band Plan]<br />
* [http://www.apco911.org/frequency/documents/700_NB_channel_centers.pdf 700 MHz Narrowband Public Safety band plan (.PDF file) from APCO web site]<br />
* [http://www.apco911.org/frequency/documents/700_channel_centers_WB.pdf 700 MHz Widewband Public Safety band plan (.PDF file) from APCO web site]<br />
* [[Federal/Non-Federal Interoperability]]<br />
<br />
=== State Interoperability Web Sites ===<br />
* [http://www.dhs.alabama.gov/interopcomm.aspx?sm=b_d Alabama]<br />
* [http://ready.alaska.gov/SERC/committee_interop.htm Alaska]<br />
* [http://www.azgita.gov/psic Arizona]<br />
* [http://www.awin.arkansas.gov Arkansas]<br />
* [http://www.calema.ca.gov/TechnologyOperations/Pages/Communications-Interoperability-%28CICO%29.aspx California]<br />
* Colorado: [http://www.ccncinc.org CCNC], [http://www.colorado.gov/cs/Satellite/OIT-ServicesApps/CBON/1251575060697 OIT]<br />
* [http://www.ct.gov/demhs/cwp/view.asp?a=1923&q=287892&demhsNav=| Connecticut]<br />
* [http://divcomm.delaware.gov Delaware]<br />
* [http://www.capwin.org DC]<br />
* [http://www.dms.myflorida.com/suncom/public_safety_bureau/radio_communications Florida]<br />
* [http://www.gainterop.com Georgia]<br />
* Hawaii: need link<br />
* [http://www.bhs.idaho.gov/Pages/Communications/IdahoSIEC.aspx Idaho]<br />
* [http://www.state.il.us/IEMA/SCIP.asp Illinois]<br />
* [http://www.in.gov/ipsc Indiana]<br />
* [http://isicsb.iowa.gov Iowa]<br />
* [http://www.kansastag.gov/siec.asp Kansas]<br />
* [http://www.kwiec.ky.gov Kentucky]<br />
* [http://gohsep.la.gov/commo.aspx Louisiana]<br />
* [http://www.state.me.us/mema/programs/mema_prog_icomm.shtml Maine]<br />
* [http://doit.maryland.gov/interoperability/Pages/default.aspx Maryland]<br />
* [http://www.mass.gov/?pageID=eopssubtopic&L=3&L0=Home&L1=Homeland+Security+%26+Emergency+Response&L2=Other+Statewide+Homeland+Security+Information&sid=Eeops Massachusetts]<br />
* [http://www.michigan.gov/mpscs Michigan]<br />
* [http://dps.mn.gov/divisions/ecn Minnesota]<br />
* [http://www.wcc.ms.gov Mississippi]<br />
* [http://www.dps.mo.gov/HomelandSecurity/Communications.htm Missouri]<br />
* [http://pssb.mt.gov/pscommunications.mcpx Montana]<br />
* [http://its.ne.gov/network_serv/wireless/wireless.html Nebraska]<br />
* [http://homelandsecurity.nv.gov/NCSC.htm Nevada]<br />
* [http://www.nh.gov/safety/divisions/homeland/psic/index.html New Hampshire]<br />
* [http://interoperability.nj.gov New Jersey]<br />
* [http://www.nmdhsem.org/Statewide_Communications_Inoperability_Plan.aspx New Mexico]<br />
* [http://www.dhses.ny.gov/oiec New York]<br />
* [https://secure.nccrimecontrol.org/hsb/Pages/InteroperableCommunications.aspx North Carolina]<br />
* [http://www.nd.gov/des/state-radio North Dakota]<br />
* Ohio: [http://ema.ohio.gov/PlanForOhioMainPage.aspx EMA], [http://das.ohio.gov/Divisions/InformationTechnology/MARCSServices/tabid/124/Default.aspx MARCS]<br />
* Oklahoma: [http://www.ok.gov/homeland/Interoperable_Communications/Statewide_Communications_Interoperability_Plan_/index.html SCIP], [http://www.ok.gov/okwin OKWIN]<br />
* Oregon: [http://www.oregon.gov/SIEC/SCIP_Page.shtml SEIC], [http://www.oregon.gov/ODOT/HWY/StateRadioProject/index.shtml State Radio Project]<br />
* [http://www.portal.state.pa.us/portal/server.pt/community/public_safety_radio Pennsylvania]<br />
* Rhode Island: need link<br />
* South Carolina: [http://www.sled.sc.gov/HSOfficeHome.aspx?MenuID=HSOffice SLED HSO], [http://www.cio.sc.gov/councilscommittees/palmetto800 Palmetto]<br />
* [http://www.sdpscc.sd.gov South Dakota]<br />
* [http://www.region39.org Tennessee]<br />
* Texas: [http://tsiec.region49.org TSIEC], [http://txrc.region49.org TRC]<br />
* [http://siec.utah.gov Utah]<br />
* [http://vcomm.vermont.gov Vermont]<br />
* Virginia: [http://www.commonwealthpreparedness.virginia.gov/Initiatives/Interoperability CICO], [http://www.vsp.state.va.us/stars.shtm STARS]<br />
* [http://siec.wa.gov Washington]<br />
* [http://www.wvirp.com West Virginia]<br />
* [http://interop.wi.gov Wisconsin]<br />
* [http://wyolink.state.wy.us Wyoming]<br />
<br />
{{Refreshpage<br />
|Pageurl=http://wiki.radioreference.com/index.php/Common_Public_Safety}}<br />
<br />
Search:Interoperability<br />
[[Category:US and Canadian Common Frequencies]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Common_Public_Safety&diff=85266Common Public Safety2011-09-21T12:34:50Z<p>Loumaag: Fixing the refresh link</p>
<hr />
<div>== Nationwide Public Safety Interoperability Channels ==<br />
'''See: [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels] and [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide]'''<br />
<br />
'''Some states, regional and local areas have their own interoperability or mutual aid channels or trunked system talkgroups which are used instead of, or in addition to, those listed below.'''<br />
<br />
'''In some areas the channels listed below may have different channel names, tones, etc. or be used for different purposes.'''<br />
<br />
* State and regional frequencies are usually found on the ''Common/Shared'' or ''Statewide'' drop-down list on the main [http://www.radioreference.com/apps/db/ RadioReference Database] page for each state.<br />
* Interoperability channel plans are often published on various state government web sites. See links at the bottom of this page.<br />
* In analog mode all end user radios should transmit PL 156.7 (136.5 for high band temporary repeaters, 167.9 for NITA channels) and receive CSQ (carrier squelch) unless PL decode is necessary due to interference.<br />
* In APCO P25 dgital mode all radios should use NAC $293 (NAC $68F for NTIA channels).<br />
<br />
=== VHF ===<br />
==== VHF Low Band ====<br />
<freqsubcat> 64465</freqsubcat><br />
<br />
==== VHF High Band ====<br />
<freqsubcat> 64466</freqsubcat><br />
<br />
==== VHF NTIA Law Enforcement ====<br />
<freqsubcat>64500</freqsubcat><br />
<br />
==== VHF NTIA Incident Response ====<br />
<freqsubcat>64502</freqsubcat><br />
Notes<br />
* (1) VTAC17 and VTAC17D are VHF marine band channels and their use is limited to inland [http://www.fcc.gov/oet/info/maps/areas/maps/vpc.pdf VHF Public Coast Station Areas (VPCSA)] 10 through 42.<br />
* (2) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== UHF ===<br />
==== UHF Public Safety ====<br />
<freqsubcat> 64468</freqsubcat><br />
<br />
==== UHF NTIA Law Enforcement ====<br />
<freqsubcat>64501</freqsubcat><br />
<br />
==== UHF NTIA Incident Response ====<br />
<freqsubcat>64503</freqsubcat><br />
Notes<br />
* (1) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== 700 MHz ===<br />
<freqsubcat>64470</freqsubcat><br />
<br />
=== 800 MHz ===<br />
<freqsubcat>64471</freqsubcat><br />
<br />
<br />
== 700 MHz Low Power/Itinerant ==<br />
* The following narrowband channels (12.5 kHz) are designated for low power use for on-scene incident response purposes using mobiles and portables.<br />
* Transmitter power must not exceed 2 watts (ERP)<br />
* Three of the pairs can be licensed for nationwide itinerant use, the rest are subject to regional planning.<br />
<freqsubcat> 64498</freqsubcat><br />
<br />
<br />
== [[Disaster Relief]] ==<br />
<br />
===American Red Cross===<br />
====VHF Low====<br />
<freqsubcat>52358</freqsubcat><br />
====VHF High====<br />
<freqsubcat>52360</freqsubcat><br />
<br />
== [[Emergency Medical Services Radio]] ==<br />
<freqsubcat>64545</freqsubcat><br />
<br />
== Law Enforcement ==<br />
* 155.370 is used as a law enforcement intersystem frequency used in many states and is often called "Point-to-Point". The FCC rule designation was removed in recent years.<br />
* 155.475 and 155.4825 are available nationwide for use in police emergency communications networks operated under statewide law enforcement emergency communications plans. 155.475 is often called "National Law Enforcement Mutual Aid"<br />
<br />
== [[National Incident Radio Support Cache]] ==<br />
== Search and Rescue ==<br />
* 155.160 is used in many areas for search and rescue.<br />
<br />
<br />
==Related Links ==<br />
=== References ===<br />
* [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels]<br />
* [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide (NIFOG) v 1.4] - Page also has programming guide and programming template (Excel spreadsheet).<br />
* [http://www.npstc.org/channelNaming.jsp NPSTC interoperability channel name standardization]<br />
* [http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1621A1.pdf FCC DA-01-1621 Federal Government Spectrum Available for Public Safety Interoperability Communications]<br />
* [http://www.fcc.gov/pshs/ FCC Public Safety & Homeland Security Bureau]<br />
** [http://transition.fcc.gov/pshs/techtopics/techtopics12.html Topic 12: National Interoperability Channels]<br />
* [http://www.apcointl.org/frequency/interoperability.php APCO Interoperability Resources]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr;sid=17215d8c8052bfef50e5299b335bd82c;rgn=div8;view=text;node=47%3A5.0.1.1.3.2.110.4;idno=47;cc=ecfr 47CFR90.20 Public Safety Pool Frequency Table]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=17215d8c8052bfef50e5299b335bd82c&rgn=div8&view=text&node=47:5.0.1.1.3.17.114.7&idno=47 47CFR90.531 Public Safety 700 MHz band Plan]<br />
* [http://www.apco911.org/frequency/documents/700_NB_channel_centers.pdf 700 MHz Narrowband Public Safety band plan (.PDF file) from APCO web site]<br />
* [http://www.apco911.org/frequency/documents/700_channel_centers_WB.pdf 700 MHz Widewband Public Safety band plan (.PDF file) from APCO web site]<br />
* [[Federal/Non-Federal Interoperability]]<br />
<br />
=== State Interoperability Web Sites ===<br />
* [http://www.dhs.alabama.gov/interopcomm.aspx?sm=b_d Alabama]<br />
* [http://ready.alaska.gov/SERC/committee_interop.htm Alaska]<br />
* [http://www.azgita.gov/psic Arizona]<br />
* [http://www.awin.arkansas.gov Arkansas]<br />
* [http://www.calema.ca.gov/TechnologyOperations/Pages/Communications-Interoperability-%28CICO%29.aspx California]<br />
* Colorado: [http://www.ccncinc.org CCNC], [http://www.colorado.gov/cs/Satellite/OIT-ServicesApps/CBON/1251575060697 OIT]<br />
* [http://www.ct.gov/demhs/cwp/view.asp?a=1923&q=287892&demhsNav=| Connecticut]<br />
* [http://divcomm.delaware.gov Delaware]<br />
* [http://www.capwin.org DC]<br />
* [http://www.dms.myflorida.com/suncom/public_safety_bureau/radio_communications Florida]<br />
* [http://www.gainterop.com Georgia]<br />
* Hawaii: need link<br />
* [http://www.bhs.idaho.gov/Pages/Communications/IdahoSIEC.aspx Idaho]<br />
* [http://www.state.il.us/IEMA/SCIP.asp Illinois]<br />
* [http://www.in.gov/ipsc Indiana]<br />
* [http://isicsb.iowa.gov Iowa]<br />
* [http://www.kansastag.gov/siec.asp Kansas]<br />
* [http://www.kwiec.ky.gov Kentucky]<br />
* [http://gohsep.la.gov/commo.aspx Louisiana]<br />
* [http://www.state.me.us/mema/programs/mema_prog_icomm.shtml Maine]<br />
* [http://doit.maryland.gov/interoperability/Pages/default.aspx Maryland]<br />
* [http://www.mass.gov/?pageID=eopssubtopic&L=3&L0=Home&L1=Homeland+Security+%26+Emergency+Response&L2=Other+Statewide+Homeland+Security+Information&sid=Eeops Massachusetts]<br />
* [http://www.michigan.gov/mpscs Michigan]<br />
* [http://dps.mn.gov/divisions/ecn Minnesota]<br />
* [http://www.wcc.ms.gov Mississippi]<br />
* [http://www.dps.mo.gov/HomelandSecurity/Communications.htm Missouri]<br />
* [http://pssb.mt.gov/pscommunications.mcpx Montana]<br />
* [http://its.ne.gov/network_serv/wireless/wireless.html Nebraska]<br />
* [http://homelandsecurity.nv.gov/NCSC.htm Nevada]<br />
* [http://www.nh.gov/safety/divisions/homeland/psic/index.html New Hampshire]<br />
* [http://interoperability.nj.gov New Jersey]<br />
* [http://www.nmdhsem.org/Statewide_Communications_Inoperability_Plan.aspx New Mexico]<br />
* [http://www.dhses.ny.gov/oiec New York]<br />
* [https://secure.nccrimecontrol.org/hsb/Pages/InteroperableCommunications.aspx North Carolina]<br />
* [http://www.nd.gov/des/state-radio North Dakota]<br />
* Ohio: [http://ema.ohio.gov/PlanForOhioMainPage.aspx EMA], [http://das.ohio.gov/Divisions/InformationTechnology/MARCSServices/tabid/124/Default.aspx MARCS]<br />
* Oklahoma: [http://www.ok.gov/homeland/Interoperable_Communications/Statewide_Communications_Interoperability_Plan_/index.html SCIP], [http://www.ok.gov/okwin OKWIN]<br />
* Oregon: [http://www.oregon.gov/SIEC/SCIP_Page.shtml SEIC], [http://www.oregon.gov/ODOT/HWY/StateRadioProject/index.shtml State Radio Project]<br />
* [http://www.portal.state.pa.us/portal/server.pt/community/public_safety_radio Pennsylvania]<br />
* Rhode Island: need link<br />
* South Carolina: [http://www.sled.sc.gov/HSOfficeHome.aspx?MenuID=HSOffice SLED HSO], [http://www.cio.sc.gov/councilscommittees/palmetto800 Palmetto]<br />
* [http://www.sdpscc.sd.gov South Dakota]<br />
* [http://www.region39.org Tennessee]<br />
* Texas: [http://tsiec.region49.org TSIEC], [http://txrc.region49.org TRC]<br />
* [http://siec.utah.gov Utah]<br />
* [http://vcomm.vermont.gov Vermont]<br />
* Virginia: [http://www.commonwealthpreparedness.virginia.gov/Initiatives/Interoperability CICO], [http://www.vsp.state.va.us/stars.shtm STARS]<br />
* [http://siec.wa.gov Washington]<br />
* [http://www.wvirp.com West Virginia]<br />
* [http://interop.wi.gov Wisconsin]<br />
* [http://wyolink.state.wy.us Wyoming]<br />
<br />
{{Refreshpage<br />
|Pageurl=http://wiki.radioreference.com/index.php/Common_Public_Safety}}<br />
<br />
Search:Interoperability<br />
[[Category:US and Canadian Common Frequencies]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Common_Public_Safety&diff=85262Common Public Safety2011-09-21T01:04:19Z<p>Loumaag: Converted tables to grabbing the frequency data from the new Nationwide DB area.</p>
<hr />
<div>== Nationwide Public Safety Interoperability Channels ==<br />
'''See: [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels] and [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide]'''<br />
<br />
'''Some states, regional and local areas have their own interoperability or mutual aid channels or trunked system talkgroups which are used instead of, or in addition to, those listed below.'''<br />
<br />
'''In some areas the channels listed below may have different channel names, tones, etc. or be used for different purposes.'''<br />
<br />
* State and regional frequencies are usually found on the ''Common/Shared'' or ''Statewide'' drop-down list on the main [http://www.radioreference.com/apps/db/ RadioReference Database] page for each state.<br />
* Interoperability channel plans are often published on various state government web sites. See links at the bottom of this page.<br />
* In analog mode all end user radios should transmit PL 156.7 (136.5 for high band temporary repeaters, 167.9 for NITA channels) and receive CSQ (carrier squelch) unless PL decode is necessary due to interference.<br />
* In APCO P25 dgital mode all radios should use NAC $293 (NAC $68F for NTIA channels).<br />
<br />
=== VHF ===<br />
==== VHF Low Band ====<br />
<freqsubcat> 64465</freqsubcat><br />
<br />
==== VHF High Band ====<br />
<freqsubcat> 64466</freqsubcat><br />
<br />
==== VHF NTIA Law Enforcement ====<br />
<freqsubcat>64500</freqsubcat><br />
<br />
==== VHF NTIA Incident Response ====<br />
<freqsubcat>64502</freqsubcat><br />
Notes<br />
* (1) VTAC17 and VTAC17D are VHF marine band channels and their use is limited to inland [http://www.fcc.gov/oet/info/maps/areas/maps/vpc.pdf VHF Public Coast Station Areas (VPCSA)] 10 through 42.<br />
* (2) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== UHF ===<br />
==== UHF Public Safety ====<br />
<freqsubcat> 64468</freqsubcat><br />
<br />
==== UHF NTIA Law Enforcement ====<br />
<freqsubcat>64501</freqsubcat><br />
<br />
==== UHF NTIA Incident Response ====<br />
<freqsubcat>64503</freqsubcat><br />
Notes<br />
* (1) The NTIA channels are provided for informational purposes only and are not part of the American National Standard (ANS).<br />
<br />
=== 700 MHz ===<br />
<freqsubcat>64470</freqsubcat><br />
<br />
=== 800 MHz ===<br />
<freqsubcat>64471</freqsubcat><br />
<br />
<br />
== 700 MHz Low Power/Itinerant ==<br />
* The following narrowband channels (12.5 kHz) are designated for low power use for on-scene incident response purposes using mobiles and portables.<br />
* Transmitter power must not exceed 2 watts (ERP)<br />
* Three of the pairs can be licensed for nationwide itinerant use, the rest are subject to regional planning.<br />
<freqsubcat> 64498</freqsubcat><br />
<br />
<br />
== [[Disaster Relief]] ==<br />
<br />
== [[Emergency Medical Services Radio]] ==<br />
<freqsubcat>64545</freqsubcat><br />
<br />
== Law Enforcement ==<br />
* 155.370 is used as a law enforcement intersystem frequency used in many states and is often called "Point-to-Point". The FCC rule designation was removed in recent years.<br />
* 155.475 and 155.4825 are available nationwide for use in police emergency communications networks operated under statewide law enforcement emergency communications plans. 155.475 is often called "National Law Enforcement Mutual Aid"<br />
<br />
== [[National Incident Radio Support Cache]] ==<br />
== Search and Rescue ==<br />
* 155.160 is used in many areas for search and rescue.<br />
<br />
<br />
==Related Links ==<br />
=== References ===<br />
* [http://www.apcointl.com/new/commcenter911/documents/APCO-NPSTC-ANS1-104-1web.pdf APCO/NPSTC ANS 1.104.1-2010 Standard Channel Nomenclature for the Public Safety Interoperability Channels]<br />
* [http://www.dhs.gov/files/publications/gc_1297699887997.shtm USDHS National Interoperability Field Operations Guide (NIFOG) v 1.4] - Page also has programming guide and programming template (Excel spreadsheet).<br />
* [http://www.npstc.org/channelNaming.jsp NPSTC interoperability channel name standardization]<br />
* [http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1621A1.pdf FCC DA-01-1621 Federal Government Spectrum Available for Public Safety Interoperability Communications]<br />
* [http://www.fcc.gov/pshs/ FCC Public Safety & Homeland Security Bureau]<br />
** [http://transition.fcc.gov/pshs/techtopics/techtopics12.html Topic 12: National Interoperability Channels]<br />
* [http://www.apcointl.org/frequency/interoperability.php APCO Interoperability Resources]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr;sid=17215d8c8052bfef50e5299b335bd82c;rgn=div8;view=text;node=47%3A5.0.1.1.3.2.110.4;idno=47;cc=ecfr 47CFR90.20 Public Safety Pool Frequency Table]<br />
* [http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=17215d8c8052bfef50e5299b335bd82c&rgn=div8&view=text&node=47:5.0.1.1.3.17.114.7&idno=47 47CFR90.531 Public Safety 700 MHz band Plan]<br />
* [http://www.apco911.org/frequency/documents/700_NB_channel_centers.pdf 700 MHz Narrowband Public Safety band plan (.PDF file) from APCO web site]<br />
* [http://www.apco911.org/frequency/documents/700_channel_centers_WB.pdf 700 MHz Widewband Public Safety band plan (.PDF file) from APCO web site]<br />
* [[Federal/Non-Federal Interoperability]]<br />
<br />
=== State Interoperability Web Sites ===<br />
* [http://www.dhs.alabama.gov/interopcomm.aspx?sm=b_d Alabama]<br />
* [http://ready.alaska.gov/SERC/committee_interop.htm Alaska]<br />
* [http://www.azgita.gov/psic Arizona]<br />
* [http://www.awin.arkansas.gov Arkansas]<br />
* [http://www.calema.ca.gov/TechnologyOperations/Pages/Communications-Interoperability-%28CICO%29.aspx California]<br />
* Colorado: [http://www.ccncinc.org CCNC], [http://www.colorado.gov/cs/Satellite/OIT-ServicesApps/CBON/1251575060697 OIT]<br />
* [http://www.ct.gov/demhs/cwp/view.asp?a=1923&q=287892&demhsNav=| Connecticut]<br />
* [http://divcomm.delaware.gov Delaware]<br />
* [http://www.capwin.org DC]<br />
* [http://www.dms.myflorida.com/suncom/public_safety_bureau/radio_communications Florida]<br />
* [http://www.gainterop.com Georgia]<br />
* Hawaii: need link<br />
* [http://www.bhs.idaho.gov/Pages/Communications/IdahoSIEC.aspx Idaho]<br />
* [http://www.state.il.us/IEMA/SCIP.asp Illinois]<br />
* [http://www.in.gov/ipsc Indiana]<br />
* [http://isicsb.iowa.gov Iowa]<br />
* [http://www.kansastag.gov/siec.asp Kansas]<br />
* [http://www.kwiec.ky.gov Kentucky]<br />
* [http://gohsep.la.gov/commo.aspx Louisiana]<br />
* [http://www.state.me.us/mema/programs/mema_prog_icomm.shtml Maine]<br />
* [http://doit.maryland.gov/interoperability/Pages/default.aspx Maryland]<br />
* [http://www.mass.gov/?pageID=eopssubtopic&L=3&L0=Home&L1=Homeland+Security+%26+Emergency+Response&L2=Other+Statewide+Homeland+Security+Information&sid=Eeops Massachusetts]<br />
* [http://www.michigan.gov/mpscs Michigan]<br />
* [http://dps.mn.gov/divisions/ecn Minnesota]<br />
* [http://www.wcc.ms.gov Mississippi]<br />
* [http://www.dps.mo.gov/HomelandSecurity/Communications.htm Missouri]<br />
* [http://pssb.mt.gov/pscommunications.mcpx Montana]<br />
* [http://its.ne.gov/network_serv/wireless/wireless.html Nebraska]<br />
* [http://homelandsecurity.nv.gov/NCSC.htm Nevada]<br />
* [http://www.nh.gov/safety/divisions/homeland/psic/index.html New Hampshire]<br />
* [http://interoperability.nj.gov New Jersey]<br />
* [http://www.nmdhsem.org/Statewide_Communications_Inoperability_Plan.aspx New Mexico]<br />
* [http://www.dhses.ny.gov/oiec New York]<br />
* [https://secure.nccrimecontrol.org/hsb/Pages/InteroperableCommunications.aspx North Carolina]<br />
* [http://www.nd.gov/des/state-radio North Dakota]<br />
* Ohio: [http://ema.ohio.gov/PlanForOhioMainPage.aspx EMA], [http://das.ohio.gov/Divisions/InformationTechnology/MARCSServices/tabid/124/Default.aspx MARCS]<br />
* Oklahoma: [http://www.ok.gov/homeland/Interoperable_Communications/Statewide_Communications_Interoperability_Plan_/index.html SCIP], [http://www.ok.gov/okwin OKWIN]<br />
* Oregon: [http://www.oregon.gov/SIEC/SCIP_Page.shtml SEIC], [http://www.oregon.gov/ODOT/HWY/StateRadioProject/index.shtml State Radio Project]<br />
* [http://www.portal.state.pa.us/portal/server.pt/community/public_safety_radio Pennsylvania]<br />
* Rhode Island: need link<br />
* South Carolina: [http://www.sled.sc.gov/HSOfficeHome.aspx?MenuID=HSOffice SLED HSO], [http://www.cio.sc.gov/councilscommittees/palmetto800 Palmetto]<br />
* [http://www.sdpscc.sd.gov South Dakota]<br />
* [http://www.region39.org Tennessee]<br />
* Texas: [http://tsiec.region49.org TSIEC], [http://txrc.region49.org TRC]<br />
* [http://siec.utah.gov Utah]<br />
* [http://vcomm.vermont.gov Vermont]<br />
* Virginia: [http://www.commonwealthpreparedness.virginia.gov/Initiatives/Interoperability CICO], [http://www.vsp.state.va.us/stars.shtm STARS]<br />
* [http://siec.wa.gov Washington]<br />
* [http://www.wvirp.com West Virginia]<br />
* [http://interop.wi.gov Wisconsin]<br />
* [http://wyolink.state.wy.us Wyoming]<br />
<br />
{{Refreshpage<br />
|Pageurl=http://wiki.radioreference.com/Common_Public_Safety}}<br />
<br />
Search:Interoperability<br />
[[Category:US and Canadian Common Frequencies]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=General_Mobile_Radio_Service_(GMRS)_(US_Nationwide)&diff=85118General Mobile Radio Service (GMRS) (US Nationwide)2011-09-16T16:23:47Z<p>Loumaag: Fixing Redirect</p>
<hr />
<div>#REDIRECT [[General Mobile Radio Service]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Family_Radio_Service_(FRS)_(US_Nationwide)&diff=85117Family Radio Service (FRS) (US Nationwide)2011-09-16T16:21:19Z<p>Loumaag: Redirecting to the already established page</p>
<hr />
<div>#REDIRECT [[Family Radio Service]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=General_Mobile_Radio_Service_(GMRS)_(US_Nationwide)&diff=85116General Mobile Radio Service (GMRS) (US Nationwide)2011-09-16T16:17:52Z<p>Loumaag: Redirecting to the already established page</p>
<hr />
<div>#REDIRECT [[GMRS]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Multi-Use_Radio_Service_(MURS)_(US_Nationwide)&diff=85115Multi-Use Radio Service (MURS) (US Nationwide)2011-09-16T16:13:21Z<p>Loumaag: Redirecting to the already established page</p>
<hr />
<div>#REDIRECT [[Multi-Use Radio Service]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Citizens_Band_(CB)_(US_Nationwide)&diff=85114Citizens Band (CB) (US Nationwide)2011-09-16T16:10:55Z<p>Loumaag: Setting a Redirect to the already established page</p>
<hr />
<div>#REDIRECT [[Citizens Band]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Trunking_Basics&diff=84228Trunking Basics2011-08-21T14:16:25Z<p>Loumaag: Changed "CC" to "CCh" to follow the recommended abbreviation on the site.</p>
<hr />
<div>== Early attempts at spectrum management ==<br />
=== Repeaters ===<br />
To understand trunking, one must first understand the concept of [[repeater]] operation. Straight repeater operation isn't especially complicated: place a remotely controlled receiver and transmitter on a high point somewhere in the area. The repeater receives all the signals transmitted on one frequency known as the input frequency (call this channel "A") and takes what it hears and retransmits it on another frequency known as the output frequency (call this channel "B") at the same time. All mobile and base stations listen on channel "B" and transmit on channel "A." <br />
<br />
This system allows units across a wide area to communicate with each other via the repeater (called a mobile relay by the [[FCC]]). <br />
<br />
=== Tone-controlled access ===<br />
The first way interference was solved was by the use of [[CTCSS]] or [[DCS]] (more commonly called PL or DPL tones). These are subaudible (and in the case of DCS, digitally encoded) signals sent out along with the radio signal carrying the voice transmission. Radio receivers are set to only open squelch when a specific CTCSS or DCS is detected. This meant, for example, that two counties near each other could use the same frequency (for example, 155.25 [[MHz]]) with different tones and would not normally interfere with each other. One organization could be using 155.25 MHz with a CTCSS tone of 114.8 [[Hz]] and in the next county over, another organization could be using 155.25 MHz with a CTCSS tone of 110.9 Hz and for the most part they would not hear each other. <br />
<br />
CTCSS, of course, does not actually keep stations in different nets from interfering with one another ''if they transmit at the same time'', but at least one net's users won't open the other net's repeater.<br />
<br />
== Trunking ==<br />
While the use of CTCSS and DCS proved to be a good solution for a while, [[spectrum]] crowding, especially in urban areas, overwhelmed such solutions, and eventually led to the development of [[trunked radio systems]]. Trunking is the use of several repeaters, on different frequencies in the same band, operating together under computer control to allow the pooling of resources for several agencies. A presentation on the basics of trunked radios systems was done at Defcon 15 and a video of that presentation is available [http://video.google.com/videoplay?docid=2933067560876937617&hl=en here].<br />
<br />
The trunking radio, in a patrol car for example, is much more sophisticated than the simple [[transceiver]] previously used in a [[simplex]] or [[repeater]] configuration. A [[trunking]] transceiver is a microprocessor-controlled radio capable of receiving instructions from the system controller and changing frequencies on the fly. All trunked radios operate in a similar manner although the type of trunking technology used by each type of trunked radio system differs greatly.<br />
<br />
In the trunked radio environment, each agency is assigned one or more [[talkgroups]] that the agency's communications will use. All agencies on the system will have different talkgroups but all will share the same pool of frequencies. For simplicity I will use an example of a [[control channel]]-based type of trunked radio system as an example. (Some trunking systems don't use a dedicated control channel.) In this type of system, all the radios on the system (except the computer controlled set of repeaters, of course) listen to a common control channel (CCh) output frequency and transmit (initially) on a common control channel input frequency, unless they are listening to a conversation on a talkgroup. <br />
<br />
Let's say that Patrolman Bob (from Smalltown Police Department) wants to tell the dispatch office that he is now in service. The following actions take place in a very short time--much less time than it takes you to read this. <br />
<br />
*He picks up his microphone and keys the mike, his radio sends a signal on the CCh input frequency, which the controlling computer understands as a request for a channel grant for the talkgroup assigned to Smalltown Police.<br />
*His radio then instantly goes back into receive mode, ''while he's still holding down the PTT switch''. The computer looks at the system for an empty channel pair and issues that channel grant on a specific channel pair and sends that channel grant information out on the CCh output channel. This channel grant information tells all radios on the system: "if you are listening (monitoring) for communications on the Smalltown Police talkgroup: change to channel pair XX on the system for a communication". <br />
*All radios tuned to Smalltown Police's talkgroup, including Patrolman Bob's, then switch frequencies to that channel pair granted by the computer. <br />
*Patrolman Bob's radio, after changing frequencies, goes into transmit mode and he can start to talk. Generally, the radio will generate a "talk-permit tone" to tell him that it has tuned to a channel, and is now in transmit mode.* As he talks, all the radios monitoring the Smalltown Police's talkgroup are now listening on the assigned repeater output channel and are ready to talk on the assigned repeater input channel. This continues until Patrolman Bob has finished his transmission. On some types of systems, further communication may be on the initially assigned channel pair or it may move to another, but the process stays the same.<br />
<br />
[ *If you think this sounds similar to the Nextel chirp, it is: Nextel (iDEN) is essentially a digital trunking radio system licensed as Specialized Mobile Radio -- they bought up lots of licenses in that non-cellular band Way Back When. ]<br />
<br />
A trunk-tracking scanner is designed to follow those same instructions (except, of course, it ignores the instructions relative to the input side of the repeater pair) so that it will also follow the conversations by changing frequency to the appropriate repeater output frequency. Each type of trunked radio system operates a little differently, and some cannot be monitored by current trunk-tracking scanners at all. <br />
<br />
Please take a look at detail information in regard to the type of system that you are attempting to monitor and the instructions that come with your scanner in regard to that type of system.<br />
<br />
==Networked Systems==<br />
A trunking system that uses more than one site is either a multi-cast (sometimes referred to as [[simulcast]]) system covering a larger but restricted area, like a mid-sized city; or a networked system. A multi-cast system could also be part of a larger networked system. <br />
<br />
Networked systems typically are made up of a trunked system that uses control channels as opposed to a [[LTR]] type system. The reason this is important to you the scanner user is that you must accommodate the use of multiple control channels in your scanner programming. For the purposes of this discussion on networking, we will only consider those systems that use control channels to manage usage (as described in the above section.) Also, in networked systems that also have multi-cast systems, consider the multi-cast system as a single site within the network.<br />
<br />
===Affiliation===<br />
An important concept to understand with networked systems is '''affiliation'''. Affiliation is what happens when a specific subscriber's radio is using a specific site to communicate with the trunked system; it "checks in", and this causes talkgroup traffic for the talkgroup to which that radio is "tuned" to appear on that particular site/tower.<br />
<br />
To explain this further let us consider a very large system, say a statewide system. Using our example above, let's consider that Smalltown has a local site on the statewide system. Normally all the traffic for Smalltown PD would probably be carried on the Smalltown tower. If patrolman Bob had to take a prisoner to a detention facility in Big City then as he traveled from Smalltown toward Big City he probably would leave the range of the Smalltown site and pass into other towers' range as he travelled. <br />
<br />
Assuming he kept his radio tuned to the Smalltown Dispatch channel as he travelled, into the range of each site, his radio would automatically affiliate with the closest (or strongest) site and unaffiliate from the site he previously was on. This means that as patrolman Bob travels, he is causing the Smalltown Dispatch channel to be able to be heard (by anyone who's selected it) on each site as he affiliates with it. <br />
<br />
This is important to you, the scanner user, because you are using a passive device to listen to this trunking network. You cannot force traffic from a desired talkgroup to appear on the site that you can hear, because you don't actively communicate on the system. You must rely on actual subscribers to cause desired traffic to appear on the site you are listening to.<br />
<br />
This concept affects you in two ways and both are best presented by examples. <br />
* Say you grew up in Smalltown and would like to hear it to keep up with what is going on, but you moved to Big City for a job. Unless patrolman Bob (or someone else) comes to Big City and keeps his radio tuned to Smalltown Dispatch, you will never hear it because no one in Big City has a radio affiliated with the Smalltown Dispatch talkgroup on the Big City site, and therefore, the system controller doesn't '''send''' the Smalltown Dispatch audio to your tower.<br />
* Say you are listening to a couple of state policeman who are doing some surveillance many miles away and they are communicating on the regular dispatch channel for the local state police station. They can be heard, even though they are not affiliated on the local site, because the local state police station's radio is affiliated with the dispatch channel. If the two state policemen (who are affiliated with some other site you can't normally hear) decide to switch channels to a TAC (talk around channel) that no one in your area has tuned, then you will lose the conversation because it will not be carried on the local site.<br />
<br />
These two circumstances are why you, the scanner user, should try and set up as many sites as you can hear in your scanner. And if you are traveling, program all the sites that you will come within range of on your trip. The actual programming of many sites within specific trunking systems becomes too complicated to discuss in this basic article. It depends on your scanner and the type of system you are attempting to monitor, so once again take a look at detailed information in regard to the type of system that you are attempting to monitor and the instructions that come with your scanner in regard to that type of system.<br />
<br />
==The Technical Jargon==<br />
'''[[Trunked Radio Systems]]''' share a small pool of frequencies among a large number of users. They can do this because communications are typically less than 5 seconds long, and a particular channel might be busy less than 5% of the time. System users are assigned to "talk groups" which function as virtual channels. When a user makes a call, the radio transmits a unique radio ID number and current talk group ID and a request for a radio channel (frequency pair) to the computer which controls the trunking system.<br />
<br />
The controller then sends out a “channel grant” specifying which frequency pair to use, and telling every other radio in that user group to also switch to that frequency pair for the duration of the transmission. When the user stops transmitting, the assigned frequency pair is released so that it is available for the next group to use, which can be any other users of the system. On a trunking radio, a “channel” is not a specific frequency pair, but instead determines the affiliation of that radio with a talk group assigned to a particular group of users on the system.<br />
<br />
The benefit of this technology to the agencies is that many more virtual channels are available for specialized traffic than there are frequencies. For example, the Fort Worth trunked system has only 20 frequencies, but services over 400 talkgroups. All radio channels in a trunking system are repeaters, so system traffic can be widely heard.<br />
<br />
The down side for scanner users is that, because a new frequency is assigned every time a user keys his radio, an exchange of communications can occur across several different system frequencies. If you just program the RF frequencies for your local trunking system directly into your scanner channels, you’ll get a mix of all the users on the system and have a very difficult time hearing any one particular communications exchange.<br />
<br />
Trunk Tracking lets a scanner monitor the system's digital [[control channel]], so it can watch for the channel assignments and follow individual communications (or scan for communications of interest) on such systems.<br />
<br />
[[Category: RR Glossary]]<br />
[[Category: FAQ]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=St_Charles_Parish_Public_Safety&diff=80024St Charles Parish Public Safety2011-05-26T00:47:39Z<p>Loumaag: </p>
<hr />
<div>Collaboration: <br />
<br />
The following are TGs on this system which have not been identified but are being removed from the DB page since they are against policy to have them in the DB:<br />
<br />
TG:<br><br />
528<br><br />
818<br><br />
1264<br><br />
4816<br><br />
4848 - checking the recieving distance on this talkgroup<br><br />
5104<br><br />
5296<br><br />
<br />
-------------</div>Loumaaghttps://wiki.radioreference.com/index.php?title=St_Charles_Parish_Public_Safety&diff=80023St Charles Parish Public Safety2011-05-26T00:44:23Z<p>Loumaag: Created page with "Collaboration: The following are TGs on this system which have not been identified but are being removed from the DB page since they are against policy to have them in the DB: ..."</p>
<hr />
<div>Collaboration: <br />
<br />
The following are TGs on this system which have not been identified but are being removed from the DB page since they are against policy to have them in the DB:<br />
<br />
TG:<br />
528<br />
818<br />
1264<br />
4816<br />
4848 - checking the recieving distance on this talkgroup<br />
5104<br />
5296<br />
<br />
-------------</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Cuyahoga_County_(OH)_Southwest/South_Central_Region&diff=45629Cuyahoga County (OH) Southwest/South Central Region2009-10-26T13:39:14Z<p>Loumaag: </p>
<hr />
<div>==Fire/EMS Tones==<br />
<br />
;Frequency 154.280 <br />
*CECOMS IMABAS Regional Alert - (3 sec/1 sec) <br />
*CECOMS IMABAS All-Call - 615.8/2807.0 (3 sec/1 sec)<br />
<br />
Search:OhioFTO<br />
<br />
[[Category:Midwest Region]]<br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Somerset_County_(PA)_Fire_Tone_Outs&diff=45626Somerset County (PA) Fire Tone Outs2009-10-26T13:38:19Z<p>Loumaag: </p>
<hr />
<div>Fire Departments Sta. # Name Pager Tones <br />
* 601 Somerset VFD 1756.9/2379.7 (Custom frequencies) <br />
* 602 Listie VFD 441.6/1011.6 <br />
* 603 Friedens VFD 358.9/489.8 <br />
* 604 Stoystown VFD 688.3/602.6 <br />
* 605 Boswell VFD 398.1/668.3 <br />
* 606 Jennerstown VFD 543.3/489.8 <br />
* 607 Sipesville VFD 543.3/441.6 <br />
* 608 Acosta VFD 358.9/398.1 <br />
* 610 Ideal VFD 691.8/562.3 <br />
* 611 Windber VFD 445.7/422.1 <br />
* 612 Confluence VFD 358.9 + 1122.1/441.6 + 741.3 (2+2) <br />
* 613 Addison VFD 398.1 + 1122.1/441.6 + 741.3 (2+2) <br />
* 614 Hooversville VFD 412.1/562.3 <br />
* 616 Scalp Level/Paint VFD 787.4/741.3 <br />
* 617 Meyersdale VFD 489.8/398.1 <br />
* 618 Salisbury VFD 1084.0/881.0 <br />
* 619 Conemaugh Twp. VFD 691.8/562.3 <br />
* 620 Garrett VFD 398.1/543.3 <br />
* 622 New Centerville VFD 489.8/441.6 <br />
* 623 Rockwood VFD 489.8/543.3 <br />
* 624 Bakersville VFD 543.3/1011.6 <br />
* 625 Seven Springs VFD 602.6/1011.6 <br />
* 626 Central City VFD 358.9/1011.6 <br />
* 627 Shanksville VFD 543.3/398.1 <br />
* 628 Berlin VFD 339.6/358.6 <br />
* 629 New Baltimore VFD 489.8 + 1122.1/1011.6 + 741.3 (2+2) <br />
* 630 Wellersburg VFD 543.3 + 1122.1/822.2 + 741.3 (2+2) <br />
* 631 Jerome VFD 787.4/507.0 <br />
EMS Departments Sta. # Name Pager Tones <br />
* 200 Team 200 SAR 339.6/349.0 <br />
* 240 Meyersdale Ambulance 569.1/349.0 <br />
* 312 Confluence Ambulance 433.7/368.5 <br />
* 500 Berlin Ambulance 378.6/358.6 <br />
* 618 Salisbury VFD Ambulance 1084.0/1285.8 (Disp. on 33.70) <br />
* 622 New Centerville VFD Ambulance 602.6/398.1 (Disp. on 33.70) <br />
* 640 Conemaugh Twp. Ambulance 810.2/903.2 <br />
* 655 Northern EMS 349.0/368.5 900 Somerset Ambulance 569.1/410.8 <br />
* 902 Somerset Ambulance (Stoystown) 569.1/979.9 --- <br />
* Medstar 1 (Helicopter)* 979.9/607.5 (B tone is not Motorola) *Medstar is dispatched by Cambria County 911 on 155.340, but their base site is located in Somerset, Somerset County. <br />
<br />
NOTES:<BR> <br />
All tones are standard Quick Call 1 / Quick Call 2 tones, except where indicated otherwise. Most are of the format 1+1, and some are 2+2, as noted. Frequencies are specified in hertz, and are listed as "A" tone / "B" tone (or "A" + "C" tones / "B" + "D" tones). <br />
Fire department tones are transmitted on 33.70 Mhz (Somerset County fire dispatch), EMS department tones are transmitted on 155.175 Mhz (Som. Co. Ambulance dispatch) Team 200's tones are transmitted on 155.955 (Local Government Radio). <br />
Exceptions are noted.<br />
<br />
Search:PennsylvaniaFTO<br />
<br />
'''Return to''' [[Somerset County (PA)]]<br />
[[Category:Mid Atlantic Region]]<br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Simcoe_County_(ON)_Fire_Code_List&diff=45621Simcoe County (ON) Fire Code List2009-10-26T13:35:57Z<p>Loumaag: </p>
<hr />
<div>===Codes List: Simcoe County Fire Information===<br />
<br />
==Adjala - Tosorontio== <br />
Station Toneout A Toneout B<br />
<br />
*Everett Station <br />
<br />
*Loretto Station 358.6 339.6 <br />
<br />
<br />
==Barrie==<br />
Station Location Toneout A Toneout B<br />
<br />
*Station 1 65 Vespra Street <br />
<br />
*Station 2 15 Bellfarm Road <br />
<br />
*Station 3 340 Big Bay Point Road <br />
<br />
*Station 4 250 Ardagh Road <br />
<br />
*Fulltime Callback � 330.5 483.5 <br />
<br />
<br />
==Bradford==<br />
Station Location Toneout A Toneout B<br />
<br />
*Station 1 75 Melbourne Drive 339.5 358.6 <br />
<br />
<br />
==Clearview==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Stayner <br />
<br />
*Station 2 Sunnidale Corners 349.0 368.5<br />
<br />
*Station 3 New Lowell <br />
<br />
*Station 4 Creemore 389.0 368.5 <br />
<br />
*Station 5 Singhampton <br />
<br />
*Station 6 Nottawa <br />
<br />
<br />
==Essa==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Thornton <br />
<br />
*Station 2 Angus <br />
<br />
*Station 1&2 � 483.5 457.9 <br />
<br />
<br />
==Innisfil==<br />
Station Location Toneout A Toneout B<br />
<br />
*Station 1 Alcona 288.7 1092.4 <br />
<br />
*Station 2 Lefroy 980 1092.4 <br />
<br />
*Station 3 Stroud 1035 1092.4<br />
<br />
*Station 4 Cookstown 1007 1092.4<br />
<br />
*Unknown 1 1035 1092.4<br />
<br />
*Unknown 2 954 1092.4<br />
<br />
*Unknown 4 980 1092.4 <br />
<br />
Note: the above tones were heard during station testing but are not confirmed as being in the correct order. <br />
<br />
==Midland==<br />
Station Location Toneout A Toneout B <br />
<br />
*Unknown 1 � 727 554 <br />
<br />
*Unknown 2 767 554<br />
<br />
*Unknown 3 810 554<br />
<br />
*Unknown 4 865 554 <br />
<br />
<br />
==New Tecumseth==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Alliston 980 1007 <br />
<br />
*Station 2 Beeton 349 368 <br />
<br />
*Station 3 Tottenham 339 358 <br />
<br />
*Chief Tottenham 955 1007 <br />
<br />
<br />
==Oro Medonte==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Shanty Bay � 1286 <br />
<br />
*Station 2 Hawkestone <br />
<br />
*Station 3 Horseshoe Valley <br />
<br />
*Station 4 Rugby <br />
<br />
*Station 5 Warminster <br />
<br />
*Station 6 Moonstone <br />
<br />
<br />
==Penetang==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Station 1 330.5 349.0 <br />
<br />
<br />
==Ramara Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Brechin 584.8 688.3<br />
<br />
*Station 2 Atherly 617.4 688.3 <br />
<br />
*Station 3 Washago 651.9 688.3 <br />
<br />
<br />
==Severn==<br />
Station Location Toneout A Toneout B <br />
<br />
*Unknown 1 Unknown 617.4 651.9<br />
<br />
*Unknown 2 Unknown 651.9 584.8 <br />
<br />
*Unknown 3 Unknown 617.4 584.8 <br />
<br />
<br />
==Springwater==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Vespra Centre (Georgian College Training Facility <br />
<br />
*Station 2 Midhurst<br />
<br />
*Station 3 Minesing<br />
<br />
*Station 4 Hillsdale<br />
<br />
*Station 5 Elmvale<br />
<br />
*Station 2-5 Group Call? 1092.4 <br />
<br />
<br />
==Tay Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 4 Port McNicoll <br />
<br />
*Unknown 1 Unknown 602 584.8 <br />
<br />
*Unknown 2 Unknown 602 616 <br />
<br />
*Unknown 3 Unknown 602 651<br />
<br />
*Unknown 1 Unknown 602 687 <br />
<br />
*Unknown 2 Unknown 602 730<br />
<br />
*Unknown 3 Unknown 602 555 <br />
<br />
<br />
==Tiny Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Lafontaine 600.9 584.8 <br />
<br />
*Station 2 600.9 617.2<br />
<br />
*Station 3 600.9 651.9<br />
<br />
*Station 4 600.9 688.3 <br />
<br />
*Station 5 Woodland Beach 600.9 728.6 <br />
<br />
*Chief Toneout? 634.5 553.9 <br />
<br />
*All call? 634.5 <br />
<br />
<br />
==Wasaga Beach==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 16 2nd Street 651.9 553.9<br />
<br />
*Station 2 3050 Mosely Street 651.9 553.9 <br />
<br />
*Volunteers? 584.8 553.9<br />
<br />
<br />
==Another tone out list for Simcoe County==<br />
<br />
City Pager Frequency Pager type Tone A Tone B Notes <br />
<br />
ALGONQUIN HIGHLANDS 154.7550 MOT 457.9 330.5 Dorset <br />
<br />
ALGONQUIN HIGHLANDS 154.7550 MOT 483.5 330.5 Oxtongue <br />
<br />
ALGONQUIN HIGHLANDS 154.7550 MOT 1153.4 1122.5 Stanhope <br />
<br />
HUNTSVILLE FIRE 153.1400 MOT 600.9 569.1<br />
<br />
INNISFIL FIRE 154.8600 MOT 288.7 1092.4 Stn 1 <br />
<br />
INNISFIL FIRE 154.8600 MOT 296.5 1092.4 Stn 2 <br />
<br />
INNISFIL FIRE 154.8600 MOT 304.7 1092.4 Stn 3<br />
<br />
INNISFIL FIRE 154.8600 MOT 313.0 1092.4 Stn 4 <br />
<br />
ORILLIA FIRE 157.5150 MOT 617.3 553.8 Full Time - Long B <br />
<br />
ORILLIA FIRE 157.5150 MOT 617.3 584.8 Volunteer - Long B<br />
<br />
ORO-MEDONTE FR 152.1800 MOT 445.7 746.8 Stn's 1-6 <br />
<br />
RAMA FIRE 152.3150 MOT 321.7 524.6 <br />
<br />
RAMARA FIRE 158.2950 MOT 617.4 688.3 Atherly district 2 <br />
<br />
RAMARA FIRE 158.2950 MOT 584.8 688.3 Brechin <br />
<br />
RAMARA FIRE 158.2950 MOT 651.9 688.3 Washago<br />
<br />
SEVERN FIRE 155.4300 MOT 651.9 584.8 Stn 1 <br />
<br />
SEVERN FIRE 155.4300 MOT 617.4 584.8 Stn 2 <br />
<br />
SEVERN FIRE 155.4300 MOT 688.3 584.8 Stn 3 <br />
<br />
SEVERN FIRE 155.4300 MOT 617.4 651.9 Chief<br />
<br />
Search:OntarioFTO<br />
<br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Simcoe_County_(ON)&diff=45618Simcoe County (ON)2009-10-26T13:34:54Z<p>Loumaag: </p>
<hr />
<div>{{Canada Collaboration<br />
|ProvinceDB=[http://www.radioreference.com/apps/db/?stid=109 {{color|white|Ontario DB]}}<br />
|Canadaforum=[http://www.radioreference.com/forums/eastern-canada-radio-discussion-forum/ {{color|white|Eastern Canada Forum}}] <br />
|Province=Simcoe County}}<br />
<br />
<br />
==Simcoe County Information/Overview==<br />
<br />
'''Simcoe County'''<br />
<br />
Simcoe County is located in the area generally referred to as Central Ontario. It is bordered by Muskoka to the north, York to the south and east and Grey County to the west.<br />
<br />
'''Public Safety'''<br />
<br />
Most policing of Simcoe County is done by the Ontario Provincial Police. They are dispatched from the Orillia Comm Centre on the [http://www.radioreference.com/apps/db/?sid=861 Fleetnet].<br />
<br />
<br />
The exceptions are the City of Barrie, South Simcoe and the Town of Midland. Interagency communications are normally done on OPC Common 142.7700Mhz.<br />
<br />
Fire Service is provided by each municipality within Simcoe County. Each utilizes it's own frequency however a County Wide mutual aid channel is also available.<br />
<br />
Toneouts and Station Lists for the various municipalities within the County can be found on the County 10 Code and Unit Lists page.<br />
<br />
EMS is provided by the Ministry of Health. Ambulances are paged out on 149.4400Mhz and respond on [http://www.radioreference.com/apps/db/?sid=861 Fleetnet].<br />
<br />
==Countywide Agencies==<br />
<br />
===Ontario Provincial Police===<br />
The Ontario Provincial Police use the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Zone 1] system for most of their communications. All communications on the Operational Talkgroups are APCO25. Interagency talkgroups are generally analog but are rarely used. The OPP also make use of analog mobile repeaters and wide area analog repeaters for portable coverage.<br />
<br />
The following detachments are located within Simcoe County:<br />
<br />
Collingwood, Dufferin, Huronia West, Orillia and South Georgian Bay.<br />
<br />
They are active on the following digital APCO25 talkgroups:<br />
<br />
<tg>861|4997-OPP Central Region</tg><br />
<br />
<br />
During normal operations, the Orillia Comm Centre will patch two talkgroups together. The following patches are usually in place on the system:<br />
<br />
Barrie is normally patched with Southern Georgian Bay and Collingwood is normally patched with Huronia West. Due to a bug in Uniden scanners, make sure you program in both talkgroups. If you only program Barrie in and the patch is setup on Southern Georgian Bay's talkgroup, you will not hear anything.<br />
<br />
The Orillia talkgroup is usually not patched. <br />
<br />
Mnjkaning (Rama First Nation) units are generally heard on the Orillia talkgroup although at times, they will use their own talkgroup. <br />
<br />
Special Operations and Events will be found on the Tactical talkgroups. Orillia Comm Centre is assigned 1TAC04 - 1TAC08.<br />
<br />
====Soft ID's for Simcoe County====<br />
*1Alpha - Orillia Regoion Headquarter Units<br />
*1Bravo - Barrie Detachment - Hwy 400 Units<br />
*1Hotel - Huronia West Detachment - Springwater units<br />
*1Kilo - Southern Georgian Bay Detachment<br />
*1Lima - Nottawasaga Detachment<br />
*1Mike - Orillia Detachment<br />
*1Oscar - Collingwood Detachment<br />
*1Papa - Rama Reserve Detachment<br />
<br />
<br />
Most communications can be heard on the Edgar Site while within Simcoe County: <site>861|946</site><br />
<br />
Other sites in the area that carry Simcoe County traffic are: Penetang, Primrose, Kimberley, King City and Sunderland.<br />
<br />
If you do not have a digital scanner, it is sometimes possible to still listen to the OPP using one of their mobile analog repeaters (VR 01, VR02 or VR03) or a wide area analog repeater (BEAT 01, BEAT 02 or URBAN).<br />
<br />
The mobile and wide area analog repeater frequencies can be found on the [http://www.radioreference.com/apps/db/?aid=577 Fleetnet Conventional Frequencies Page].<br />
<br />
Collingwood and Alliston use BEAT 01, Huronia West and Casino Rama use BEAT 02 and Orillia uses URBAN. Barrie and Southern Georgian Bay do not utilize wide area analog repeaters.<br />
<br />
The mobile repeater channel VR01 is the main channel for all mobile repeaters in Simcoe County.<br />
<br />
VR02 is used by the Highway Safety Division units which patrol Highway 400.<br />
<br />
VR03 is used for special events and for aircraft intercepts.<br />
<br />
==Ministry of Health (EMS Services)==<br />
<br />
Ambulance Service is provided throughout Simcoe County by the Ministry of Health. Communications will be found in analog on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Zone 1] system. The two talkgroups used for Simcoe County are Georgian North and Georgian South.<br />
<br />
The Georgian North talkgroup covers the municipalities of: Orillia, Severn Township, Town of Midland, Town of Penetang, Oro-Medonte Township, City of Barrie, Tay Township, Tiny Township, Town of Wasaga Beach, Town of Collingwood and the Township of Clearview.<br />
<br />
The Georgian South talkgroup covers the municipalities of: Bradford West Gwillimbury, New Tecumseh, Essa Township, Springwater Township and Adjala-Tosorontio Township.<br />
<br />
The Ministry of Health also utilizes several conventional frequencies <freqsubcat>2342</freqsubcat><br />
<br />
<br />
These include several vehicular repeater frequencies utilized when ambulance personnel are away from their vehicles, station paging, a common simplex channel and a backup tactical channel. The station paging frequency is used by Georgian CACC to page the appropriate station with details of the call. When in the vehicle, the crew will respond on the appropriate dispatch talkgroup.<br />
<br />
If an accident is serious enough, the Air Ambulance could be called in. In the southern part of Simcoe County, listeners might be able to hear the output of the repeater located near Aurora in York Region. If not able to hear the output of the repeater, then listening to the input will allow the helicopter to be heard. Communications between Georgian CACC, land ambulances and the Air Ambulance generally take place on Provincial Common, 150.1000.<br />
<br />
Once enroute to the hospital, the crew will request a patch to the hospital. Generally Tac 1 and Tac 2 are used for patches to hospitals within Simcoe County. Georgian CACC will call alert the hospital and then patch the Tac channel assigned with the specific hospital talkgroup. Normally, it is only necessary to program in the Tac channels although sometimes, the hospital talkgroup is the talkgroup the patch is setup on. Tac 5 is sometimes used for special events and is worth programming in.<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Countywide_Public_Safety?action=purge Refresh] this page with the latest data</small><br />
<br />
<br />
==City/Township Information/Region Specific Frequencies/Fire Toneouts/Codes/Units/Station Lists==<br />
<br />
==Township of Adjala-Tosorontio==<br />
<br />
===Policing===<br />
<br />
Policing for the Township of Adjala-Tosorontio is handled by the Ontario Provincial Police and is dispatched on the 1OPS36 talkgroup on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Zone 1] system by the Orillia Comm Centre. The Nottawasaga talkgroup is generally patched with the Dufferin 1OPS34 talkgroup. Both talkgroups can be generally heard on the Edgar, King City and Primrose sites. A fulltime BEAT repeater on the BEAT 01 frequency is provided for officers walking the downtown area in Alliston.<br />
<br />
===Fire Service===<br />
<br />
Adjala-Tosorontio Fire Service utilizes a repeater for fire operations.<br />
<br />
<freqsubcat>4590</freqsubcat><br />
<br />
===Adjala-Tosorontio Fire Toneouts===<br />
<br />
Station Toneout A Toneout B<br />
<br />
*Everett Station <br />
<br />
*Loretto Station 358.6 339.6 <br />
<br />
<br />
* Station #1 6234 County Rd 13, Everett<br />
* Station #2 2821 County Rd 50, Loretto<br />
<br />
===Public Works===<br />
<freqsubcat>30693</freqsubcat><br />
<br />
<small>[http://wiki.radioreference.com/index.php/Township_of_Adjala-Tosorontio?action=purge Refresh] this page with the latest data</small><br />
<br />
==City of Barrie==<br />
<br />
===Overview===<br />
<br />
The City of Barrie is the largest municipality within Simcoe County. Police Services and Fire Services within the City are provided by the Barrie Police Service and the Barrie Fire Service with the exception of Highway 400 which the Ontario Provincial Police handle. <br />
<br />
<br />
<freqsubcat>4544</freqsubcat><br />
<br />
===Policing===<br />
<br />
Barrie Police Service's regular operations are conducted on 2 conventional P25 frequencies. Currently OPS02 is the main channel while OPS1 is only used for special events or operations . BPS also has a few talkgroups in use on the [http://www.radioreference.com/apps/db/?sid=1388 City of Barrie Trunk System]. The only one in regular use is the Court Services talkgroup. Other talkgroups are used for Special Events and a Citywide Common Channel. With the exception of the Court Services, these talkgroups are not in regular use.<br />
<br />
Barrie OPP are dispatched on the 1OPS30 talkgroup on [http://www.radioreference.com/apps/db/?sid=861 Fleetnet]<br />
===Fire Services===<br />
<br />
Barrie Fire Service's regular operations are conducted on Tac 1 and Tac 2 which are conventional APCO25 channels.<br />
<br />
Barrie Fire Service also has a conventional frequency dedicated to paging offduty personnel.<br />
<br />
Station dispatching is done on the City of Barrie trunk system using an analog talkgroup. Training and Fire Prevention also utilize talkgroups on the trunk system:<br />
<br />
<tg>1388|5973</tg><br />
<br />
Talkgroup 49328 is used for Moscad and is active during initial dispatches.<br />
<br />
===Barrie Fire Toneouts===<br />
<br />
Fulltime staff can be called back to duty using the 153.980Mhz callback frequency. MOSCAD Station Data also makes use of this frequency.<br />
<br />
*Fulltime Callback � 330.5 483.5 <br />
<br />
====Fire Station Locations====<br />
* Station 1 - 65 Vespra Street<br />
* Station 2 - 15 Bellfarm Road<br />
* Station 3 - 340 Big Bay Point Road<br />
* Station 4 - 250 Ardagh Road<br />
<br />
<small>[http://wiki.radioreference.com/index.php/City_of_Barrie?action=purge Refresh] this page with the latest data</small><br />
<br />
==Town of Bradford==<br />
<br />
===Policing===<br />
<br />
Policing for the Town of Bradford is provided by the South Simcoe Police Service. The South Simcoe Police Service dispatches for the Town of Innisfil as well as Bradford.<br />
<br />
<freqsubcat>6932</freqsubcat><br />
<br />
===Fire Service===<br />
<br />
Bradford Fire Service utilizes a VHF conventional narrowband repeater for day to day operations. Dispatch is via the repeater. MDC signalling is used to identify radios.<br />
<br />
<freqsubcat>4586</freqsubcat><br />
<br />
====Bradford Fire Toneout====<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 75 Melbourne Drive 339.5 358.6<br />
<br />
===Public Works===<br />
<br />
<freqsubcat>41255</freqsubcat><br />
<br />
===EMS Paging Tones===<br />
<br />
ToneA ToneB Station <br />
<br />
668.2 602.5 Bradford1 <br />
<br />
877.4 667.5 Bradford2 <br />
<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Bradford?action=purge Refresh] this page with the latest data</small><br />
<br />
==Township of Clearview==<br />
<br />
===Policing===<br />
Policing for the Township of Clearview is provided by the Ontario Provincial Police's Huronia West detachment. Communications are on Huronia West 1OPS33 talkgroup on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet System] and the units identify themselves with 1Hotel200 callsigns. The 1OPS33 talkgroup is usually patched with the Town of Collingwood 1OPS31 talkgroup. These talkgroups can be generally heard on the Edgar, Penetang, Kimberly, Primrose and King City sites. It is sometimes possible to monitor policing in the area without a digital scanner by listening to the BEAT 01 repeater located in Collingwood or the BEAT 02 located in Huronia West.<br />
<br />
===Fire Service===<br />
<freqsubcat>4583</freqsubcat><br />
The Township of Clearview utilizes a Simulcast repeater system with repeaters in Duntroon and Crremore. Dispatch is provided by the City of Barrie Fire and Emergency Services.<br />
<br />
MDC1200 unit id's are heard at the beginning of most transmissions.<br />
<br />
Clearview tests it's fire pagers at 6:35pm.<br />
<br />
====Fire Station Locations====<br />
* Station 1 - Stayner<br />
* Station 2 - Sunnidale Corners<br />
* Station 3 - New Lowell<br />
* Station 4 - Creemore<br />
* Station 5 - Singhampton<br />
* Station 6 - Nottawa<br />
<br />
====Clearview Fire Station Toneouts====<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Stayner ?? <br />
*Station 2 Sunnidale Corners 349.0 / 368.5 (Station closed)<br />
*Station 3 New Lowell ?? <br />
*Station 4 Creemore 389.0 / 368.5 <br />
*Station 5 Singhampton ?? <br />
*Station 6 Nottawa ??<br />
<br />
===EMS===<br />
<br />
Georgian CACC provides ambulance services for Clearview Township. Communications are found on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Trunk System].<br />
<br />
Generally vehicles are paged out on 149.440Mhz and respond on the Georgian Simcoe North talkgroup. <br />
<br />
Patches to Collingwood General and Marine hospital or Barrie Royal Victoria hospital are done on Georgian Tactical 1 or Georgian Tactical 2.<br />
<br />
<br />
<tg>861|5004-MOH Georgian CACC</tg><br />
<br />
===Public Works and Utilities===<br />
<freqsubcat>30694</freqsubcat><br />
<br />
<small>[http://wiki.radioreference.com/index.php/Township_of_Clearview?action=purge Refresh] this page with the latest data</small><br />
<br />
==Town of Collingwood==<br />
<br />
<freqsubcat>4546</freqsubcat><br />
<br />
===Policing===<br />
<br />
Policing for the Town of Collingwood is handled by the Ontario Provincial Police and is dispatched on the 1OPS31 talkgroup on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Zone 1] system by the Orillia Comm Centre. The Collingwood talkgroup is generally patched with the Huronia West 1OPS33 talkgroup.Both talkgroups can be generally heard on the Penetang, Edgar, Kimberley and Primrose sites. A fulltime BEAT repeater on the BEAT 01 frequency is provided for officers walking the downtown area. Collingwood units utilize the 1Oscar series of soft id's. The Collingwood detachment also serves as home for the Town of the Blue Mountains OPP units who are also dispatched on 1OPS31 and utilize the 1Oscar series of soft id's.<br />
<br />
===Fire===<br />
Collingwood Fire Service has one station which is cosited with the OPP detachment. Main fire operations are on the VHF conventional repeater channel. Since fire dispatch is located at the fire station, no fire toneouts are generally heard.<br />
<br />
The fireground frequency was recently discovered during mutual aide operations with Clearview FS.<br />
<br />
Collingwood FS tests it's pagers at 6:45pm.<br />
<br />
===Collingwood Fire Toneouts===<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
SEE ABOVE Fire<br />
<br />
===Public Works===<br />
<freqsubcat>43594</freqsubcat><br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Collingwood?action=purge Refresh] this page with the latest data</small><br />
<br />
<br />
<br />
==Township of Essa==<br />
<br />
===Policing===<br />
<br />
<br />
Policing for the Township of Essa is provided by the Ontario Provincial Police's Nottawasaga detachment. <br />
<br />
Communications are on the 1OPS36 talkgroup on [http://www.radioreference.com/apps/db/?sid=861 Fleetnet] and the units identify themselves with 1Lima callsigns. The 1OPS36 talkgroup is usually patched with the Dufferin 1OPS32 talkgroup (Dufferin County). It is sometimes possible to monitor policing in the area without a digital scanner by listening to the BEAT 01 repeater located in Alliston. A community policing office is located Angus.<br />
<br />
Canadian Forces Base Borden is also located within Essa Township and is policed by the Military Police. Their communications can be heard on the [http://www.radioreference.com/apps/db/?sid=2325 Base Borden Trunk System].<br />
<br />
===Fire Service===<br />
<br />
The Township of Essa Fire Service is dispatched by the City of Barrie Fire Service and all toneouts and operations are on their conventional VHF repeater.<br />
<br />
<freqsubcat>4577</freqsubcat><br />
<br />
===Essa Fire Toneouts===<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Thornton <br />
*Station 2 Angus <br />
*Station 1&2 � 483.5 457.9 <br />
<br />
<br />
====Station Locations====<br />
*Station 1 - Thornton<br />
*Station 2 - Angus<br />
<br />
CFB Borden has a separate fire department and their operations can be found on the [http://www.radioreference.com/apps/db/?sid=2325 Base Borden Trunk System].<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Township_of_Essa?action=purge Refresh] this page with the latest data</small><br />
<br />
==Innisfil==<br />
'''South Simcoe Public Safety'''<br />
<br />
The South Simcoe area encompassses the municipalities of Innisfil in the north and Bradford-West Gwillimbury in the south. South Simcoe Police Service provides policing throughout the area while each individual municipality provides it's own fire service.<br />
<br />
===South Simcoe Police Service===<br />
<br />
South Simcoe Police Service utilizes one conventional analog channel for it's normal operations. A second conventional channel is used for tactical operations.<br />
<br />
<freqsubcat>6932</freqsubcat><br />
<br />
North Division is located on Innisfil Beach Road in the Town of Innisfil while the new South Division is located on Melbourne drive in the Town of Bradford. A substation is located at the Cookstown Outlet Mall. Info on the teams they have to support the community [http://www.southsimcoepolice.on.ca/public/index.php?option=com_content&view=article&id=54&Itemid=63 Here]<br />
<br />
<br />
===Innisfil Fire Service===<br />
<br />
The Town of Innisfil Fire Service uses one conventional VHF frequency for it's day to day operations:<br />
<br />
<freqsubcat>4585</freqsubcat>.<br />
<br />
===Innisfil Fire Toneouts===<br />
<br />
Innisfil<br />
Station Location Toneout A Toneout B <br />
<br />
Station 1 Alcona 288.7 1092.4 <br />
<br />
Station 2 Lefroy 980 1092.4 <br />
<br />
Station 3 Stroud 1035 1092.4 <br />
<br />
Station 4 Cookstown 1007 1092.4 <br />
<br />
Unknown 1 1035 1092.4 <br />
<br />
Unknown 2 954 1092.4<br />
<br />
Unknown 4 980 1092.4 <br />
<br />
Note: the above tones were heard during station testing but are not confirmed as being in the correct order. <br />
<br />
<br />
====Fire Station Locations====<br />
* Station 1 - Alcona<br />
* Station 2 - Lefroy<br />
* Station 3 - Stroud<br />
* Station 4 - Cookstown<br />
<br />
==Town of Midland==<br />
<br />
<freqsubcat>4580</freqsubcat><br />
<br />
===Midland Police Service===<br />
<br />
The Town of Midland currently uses two VHF frequencies. Unfortunately for scanner hobbiests, both use AEGIS modulation which is currrently undecodable by any scanners. It is rumoured the Operational channel is clear AEGIS while the Tactical Channel is Encrypted AEGIS.<br />
<br />
===Midland Fire Service===<br />
<br />
Midland Fire Service utilizes two VHF conventional simplex channels. Channel 1 seems to be for dispatch purposes while apparatus responding generally shows up on Channel 2.<br />
<br />
====Midland Fire Toneouts====<br />
<br />
Station Location Toneout A Toneout B <br />
*Unknown 1 727 554 <br />
*Unknown 2 767 554 <br />
*Unknown 3 810 554 <br />
*Unknown 4 865 554 <br />
<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Midland_Public_Safety?action=purge Refresh] this page with the latest data</small><br />
<br />
==New Tecumseth==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Alliston 980 1007 <br />
<br />
*Station 2 Beeton 349 368 <br />
<br />
*Station 3 Tottenham 339 358 <br />
<br />
*Chief Tottenham 955 1007<br />
<br />
==Town of Orillia==<br />
<br />
<freqsubcat>4589</freqsubcat><br />
<br />
===Policing===<br />
Policing for the Town of Orillia is provided by the Ontario Provincial Police's Orillia detachment. Communications are on the Orillia Detachment's 1OPS37 talkgroup on the [http://www.radioreference.com/apps/db/?sid=861 Bell Mobility Fleetnet Zone 1] and the units identify themselves with 1Mike callsigns. The 1OPS37 talkgroup is sometimes patched with the MnJkning 1OPS34 talkgroup. Mnjking First Nations units normally use the Orillia 1OPS37 talkgroup but at times, the two talkgroups are patched together. <br />
<br />
For hobbiests with analog only scanners, the URBAN01 repeater on 410.4125Mhz provides a simulcast of the 1OPS37 Fleetnet talkgroup.<br />
<br />
The Ontario Provincial Police's General Headquarters is located within Orillia and many different frequencies can be heard from the facility.<br />
<br />
===Fire===<br />
<br />
Orillia FS uses a VHF repeater for dispatch and operations. MDC unit ID's can be heard on the beginning and end of each transmission.<br />
<br />
===Orillia Fire Toneouts===<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*617.3 553.8 Full Time - Long B <br />
*617.3 584.8 Volunteer - Long B <br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Orillia?action=purge Refresh] this page with the latest data</small><br />
<br />
<br />
==Township of Oro-Medonte==<br />
<br />
<freqsubcat>4588</freqsubcat><br />
<br />
===Policing===<br />
Policing for the Township of Oro-Medonte is provided by the Ontario Provincial Police's Barrie detachment. Communications are on the Barrie 1OPS30 talkgroup and the units identify themselves with 1Bravo callsigns. The 1OPS30 talkgroup is usually patched with the Southern Georgian Bay 1OPS35 talkgroup. Unfortunately, no BEAT repeaters exist within this or Southern Georgian Bay's area so listeners with analog scanners will have to try and catch one of the vehicular repeater (VR) frequencies.<br />
<br />
===Fire Service===<br />
The Township of Oro-Medonte Fire Service is dispatched by the City of Barrie Fire Service on a conventional vhf simulcast repeater system. Repeater locations are at Edgar and Hawkestone.<br />
<br />
====Oro-Medonte Fire Toneouts====<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Shanty Bay � 1286 <br />
*Station 2 Hawkestone ?? <br />
*Station 3 Horseshoe Valley ?? <br />
*Station 4 Rugby ??<br />
*Station 5 Warminster ?? <br />
*Station 6 Moonstone ?? <br />
<br />
<br />
====Station Locations====<br />
*Station 1 - Shanty Bay<br />
*Station 2 - Hawkestone<br />
*Station 3 - Horseshoe Valley<br />
*Station 4 - Rugby<br />
*Station 5 - Warminster<br />
*Station 6 - Moonstone<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Township_of_Oro-Medonte?action=purge Refresh] this page with the latest data</small><br />
<br />
==Town of Penetang==<br />
<br />
<freqsubcat>4584</freqsubcat><br />
<br />
===Policing===<br />
<br />
Policing for the Town of Penetang is provided by the Ontario Provincial Police's Southern Georgian detachment. Communications are on the Southern Georgian Bay Detachment's 1OPS35 talkgroup and the units identify themselves with 1Kilo callsigns. The 1OPS35 talkgroup is usually patched with the Barrie 1OPS30 talkgroup. Unfortunately, no BEAT repeaters exist within this or Southern Georgian Bay's area so listeners with analog scanners will have to try and catch one of the vehicular repeater (VR) frequencies.<br />
<br />
The Central North Correctional Centre (Superjail) resides in the Town of Penetang and has several analog frequencies. Superjail vehicles use the Bell Mobility Radio Fleetnet system when outside of the facility.<br />
<br />
===Fire Service===<br />
<br />
Penetang FS uses a VHF repeater for all dispatch and operations. Toneouts are on the repeater.<br />
<br />
====Penetang Fire Toneouts====<br />
<br />
Station Location Toneout A Toneout B<br />
<br />
*Station 1 Station 1 330.5 349.0 <br />
<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Penetang?action=purge Refresh] this page with the latest data</small><br />
<br />
==Ramara Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Brechin 584.8 688.3<br />
<br />
*Station 2 Atherly 617.4 688.3 <br />
<br />
*Station 3 Washago 651.9 688.3<br />
<br />
==Severn==<br />
Station Location Toneout A Toneout B <br />
<br />
*Unknown 1 Unknown 617.4 651.9<br />
<br />
*Unknown 2 Unknown 651.9 584.8 <br />
<br />
*Unknown 3 Unknown 617.4 584.8<br />
<br />
==Township of Springwater==<br />
<br />
<freqsubcat>4578</freqsubcat><br />
===Policing===<br />
<br />
Policing for the Township of Springwater is provided by the Ontario Provincial Police's Huronia West detachment (also located in Wasaga Beach). Communications are on Huronia West 1OPS33 talkgroup and the units identify themselves with 1Hotel100 callsigns. The 1OPS33 talkgroup is usually patched with the Town of Collingwood 1OPS31 talkgroup. It is sometimes possible to monitor policing in the area without a digital scanner by listening to the BEAT 01 repeater located in Collingwood or the BEAT 02 located in Huronia West. A community policing office is located at the Minesing Fire Station.<br />
<br />
===Fire Service===<br />
The Township of Springwater has fire stations located in Minesing, Snow Valley and Elmvale. They are dispatched by the City of Barrie Fire Service on a conventional vhf repeater.<br />
<br />
An onscene frequency has been mentioned but has not been found. 154.0900Mhz is licenced to Springwater FS and could be the onscene frequency.<br />
<br />
===Springwater Fire Toneouts===<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Vespra Centre (Georgian College Training Facility) <br />
*Station 2 Midhurst <br />
*Station 3 Minesing <br />
*Station 4 Hillsdale <br />
*Station 5 Elmvale <br />
*Station 2-5 Group Call? 1092.4 <br />
<br />
<br />
====Fire Station Locations====<br />
*Station 1 - Decommissioned (now in use by Georgian College as a training facility)<br />
*Station 2 - Midhurst<br />
*Station 3 - Minesing<br />
*Station 4 - Hillsdale<br />
*Station 5 - Elmvale<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Township_of_Springwater Refresh] this page with the latest data</small><br />
<br />
==Tay Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 4 Port McNicoll <br />
<br />
*Unknown 1 Unknown 602 584.8 <br />
<br />
*Unknown 2 Unknown 602 616 <br />
<br />
*Unknown 3 Unknown 602 651<br />
<br />
*Unknown 1 Unknown 602 687 <br />
<br />
*Unknown 2 Unknown 602 730<br />
<br />
*Unknown 3 Unknown 602 555<br />
<br />
==Tiny Township==<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 Lafontaine 600.9 584.8 <br />
<br />
*Station 2 600.9 617.2<br />
<br />
*Station 3 600.9 651.9<br />
<br />
*Station 4 600.9 688.3 <br />
<br />
*Station 5 Woodland Beach 600.9 728.6 <br />
<br />
*Chief Toneout? 634.5 553.9 <br />
<br />
*All call? 634.5<br />
<br />
==Town of Wasaga Beach==<br />
<freqsubcat>4587</freqsubcat><br />
===Policing===<br />
Policing for the Town of Wasaga Beach is provided by the Ontario Provincial Police's Huronia West detachment (also located in Wasaga Beach). Communications are on Huronia West 1OPS33 talkgroup and the units identify themselves with 1Hotel300 callsigns. The 1OPS33 talkgroup is usually patched with the Town of Collingwood 1OPS31 talkgroup. It is sometimes possible to monitor policing in the area without a digital scanner by listening to the BEAT 01 repeater located in Collingwood or the BEAT 02 located in Huronia West. During special events and long weekends in Wasaga Beach, a tactical talkgroup is usually utilized along with special 1Hotel callsigns. <br />
<br />
Also worth listening to (especially on a long weekend) is the Ministry of Natural Resources lowband vhf conventional repeater. Provincial Park Wardens provide policing throughout the many beach areas located in Wasaga.<br />
<br />
===Fire Service===<br />
<br />
The Town of Wasaga Beach fire service has two stations dispatched by the City of Barrie Fire service. Toneouts for both stations can be heard on the conventional analog vhf operations repeater.<br />
<br />
Two separate toneouts are used for fulltime fire fighters and volunteers. The tone combination of 651.9/553.9hz has been identified but it's unknown which toneout it is.<br />
<br />
===Wasaga Beach Fire Toneouts===<br />
<br />
Station Location Toneout A Toneout B <br />
<br />
*Station 1 16 2nd Street 651.9 553.9 <br />
*Station 2 3050 Mosely Street 651.9 553.9 <br />
*Volunteers? 584.8 553.9 <br />
<br />
<br />
====Fire Station Locations====<br />
*Station 1 - 16 2nd Street<br />
*Station 2 - 3050 Mosely Street<br />
<br />
<small>[http://wiki.radioreference.com/index.php/Town_of_Wasaga_Beach?action=purge Refresh] this page with the latest data</small><br />
<br />
==Another tone out list for Simcoe County==<br />
<br />
City Pager Frequency Pager type Tone A Tone B Notes <br />
<br />
INNISFIL FIRE 154.8600 MOT 288.7 1092.4 Stn 1 <br />
<br />
INNISFIL FIRE 154.8600 MOT 296.5 1092.4 Stn 2 <br />
<br />
INNISFIL FIRE 154.8600 MOT 304.7 1092.4 Stn 3<br />
<br />
INNISFIL FIRE 154.8600 MOT 313.0 1092.4 Stn 4 <br />
<br />
ORILLIA FIRE 157.5150 MOT 617.3 553.8 Full Time - Long B <br />
<br />
ORILLIA FIRE 157.5150 MOT 617.3 584.8 Volunteer - Long B<br />
<br />
ORO-MEDONTE FR 152.1800 MOT 445.7 746.8 Stn's 1-6 <br />
<br />
RAMA FIRE 152.3150 MOT 321.7 524.6 <br />
<br />
RAMARA FIRE 158.2950 MOT 617.4 688.3 Atherly district 2 <br />
<br />
RAMARA FIRE 158.2950 MOT 584.8 688.3 Brechin <br />
<br />
RAMARA FIRE 158.2950 MOT 651.9 688.3 Washago<br />
<br />
SEVERN FIRE 155.4300 MOT 651.9 584.8 Stn 1 <br />
<br />
SEVERN FIRE 155.4300 MOT 617.4 584.8 Stn 2 <br />
<br />
SEVERN FIRE 155.4300 MOT 688.3 584.8 Stn 3 <br />
<br />
SEVERN FIRE 155.4300 MOT 617.4 651.9 Chief<br />
<br />
==Georgian CACC EMS Paging Tones==<br />
<br />
ToneA ToneB Station <br />
<br />
*645.7 507 Coldwater <br />
<br />
*967 667.5 Washago1<br />
<br />
*668.2 398 Washago2<br />
<br />
*543.2 668.2 Orillia<br />
<br />
*489 358 Rama First Responders<br />
<br />
*668.3 741.2 Midland<br />
<br />
*602.4 398 Midland2<br />
<br />
*787.4 667.5 Midland1<br />
<br />
*359 489.7 Craighurst<br />
<br />
*441.7 543.2 Wasaga1<br />
<br />
*937.4 712.5 Wasaga2<br />
<br />
*740.5 359 Angus<br />
<br />
*543.2 358 Collingwood1<br />
<br />
*937.4 712.5 Collingwood2<br />
<br />
*937.4 712.5 Craigleith1<br />
<br />
*562.5 862.5 Craigleith2<br />
<br />
*668.2 441.5 Barrie Base<br />
<br />
*473.2 767.4 Barrie North<br />
<br />
*741.2 543.2 Stroud<br />
<br />
*668.2 602.5 Bradford1<br />
<br />
*877.4 667.5 Bradford2<br />
<br />
*441.4 398 Alliston1<br />
<br />
*802.4 622.5 Alliston2<br />
<br />
*877.1 667.5 Newmarket1<br />
<br />
*741.1 822.2 Newmarket2<br />
<br />
*489.7 741.2 Keswick<br />
<br />
*491 543 Sutton<br />
<br />
*532 607 Mount Albert<br />
<br />
*668.2 822.2 Pefferlaw<br />
<br />
*604.2 Queensville <br />
<br />
==OPP Soft ID's==<br />
<br />
*1A000 - Orillia Headquarter Units Canine, Inspectors, etc.<br />
<br />
*1A200 Orillia Headquarter Units - Traffic units <br />
<br />
*1B400 - Barrie Detachment - Hwy 400 Units <br />
<br />
*1H100 - Huronia West Detachment - Springwater units <br />
<br />
*1H200 - Huronia West Detachment - Clearview units <br />
<br />
*1H300 - Huronia West Detachment - Wasaga Beach units <br />
<br />
*1K000 - Midland Detachment 1L000 - New Tecumseth Detachment <br />
<br />
*1L500 - New Tecumseth Detachment - Angus units <br />
<br />
*1M000 - Orillia Detachment <br />
<br />
*1N000 - Dufferin County Detachment <br />
<br />
*1O000 - Collingwood Detachment <br />
<br />
*1P000 - Rama Reserve Detachment <br />
<br />
==Simcoe County EMS Apparatus==<br />
<br />
*3049 3201 3202 3203 3204 3205 3206 3209 3210 3212 3213 3214 3215 3217 3220 3225 3226 3253 3256 3257 3258 3278 3279 3281 3282 3283 3284 3310 3341 3342 3343 3345 3398 3399 3402 3403 3409 3652 - Chevrolet Cheyenne Emergency Communications Unit - based at communications centre <br />
<br />
Search:OntarioFTO<br />
<br />
<br />
[[Category:Province Data]] <br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Shawnee_County_(KS)&diff=45613Shawnee County (KS)2009-10-26T13:33:13Z<p>Loumaag: </p>
<hr />
<div>==Shawnee County Sheriff==<br />
=== Sheriff/Topeka Police Radio Code List ===<br />
*SIG 1- Armed-Dangerous<br />
*SIG 2- Resists Arrest / Violent<br />
*SIG 3- Mental<br />
*SIG 4- Suicidal<br />
*SIG 5A- Felony Offender<br />
*SIG 5B- Misdemeanor Offender<br />
*SIG 5C- Traffic Offender<br />
*SIG 5D- Narcotics<br />
*SIG 5E- Explosives<br />
*SIG 5F- Fraud<br />
*SIG 5G- Gang member<br />
*SIG 5I- Illegal Alien<br />
*SIG 5J- Juvenile / Runaway<br />
*SIG 5K- Kidnapper<br />
*SIG 5L- Larceny<br />
*SIG 5M- Murder / Homicide<br />
*SIG 5O- Other / Contact Dispatch<br />
*SIG 5P- Parole / Probation<br />
*SIG 5R- Robbery<br />
*SIG 5S- Sex Offender<br />
*SIG 5T- Terrorist affiliation<br />
*SIG 6- Intelligence Suspect<br />
*SIG 7- Sniper in the area<br />
*SIG 8- Arsonist in area<br />
*SIG 9- Wanted Felony Warrant<br />
*SIG 10- Wanted Misdemeanor Warrant<br />
*SIG 11- Stolen<br />
*SIG 12- Bomb Explosion<br />
*SIG 13- Officer needs help<br />
*SIG 14- Riot<br />
*SIG 15- Drug Material<br />
*SIG 20- Crime Scene Unit call<br />
*SIG 21- Stolen Car Report<br />
*SIG 22- Stolen Car Recovery<br />
*SIG 23- Assault / Battery<br />
*SIG 24- Animal Call<br />
*SIG 25- Assist the citizen<br />
*SIG 26- Unknown Trouble<br />
*SIG 27- Open Door<br />
*SIG 28- Pick up an article<br />
*SIG 29- Disturbance<br />
*SIG 30- Suspicious Person<br />
*SIG 31- Missing Person<br />
*SIG 32- Juvenile<br />
*SIG 33- Trouble at the station<br />
*SIG 34- Casualty report<br />
*SIG 35- Rape / Sex Offense<br />
*SIG 36- Check Welfare<br />
*SIG 37- Dead body<br />
*SIG 39- Theft<br />
*SIG 40- Forgery / Bad Checks<br />
*SIG 41- Receive Information<br />
*SIG 42- Relieve officer<br />
*SIG 43- Service request<br />
*SIG 44- Notify<br />
*SIG 45- Misc<br />
*SIG 46- Out of car with canine<br />
*SIG 48- Shoplifter<br />
*SIG 49- Out of car on portable radio<br />
*SIG 50- Out at the garage<br />
*SIG 51- Call home<br />
*SIG 52- Intoxicated subject<br />
*SIG 53- Money escort<br />
*SIG 55- Backup requested<br />
*SIG 57- Vandalism<br />
*SIG 58- Relief<br />
*SIG 60- Gang activity<br />
*SIG 63- Traffic stop<br />
*SIG 64- Traffic problem / stalled car<br />
*SIG 65- Emergency medical call<br />
*SIG 67- Building check<br />
*SIG 68- Area check<br />
*SIG 69- Out at crime scene office<br />
*SIG 90- Out at the jai<br />
<br />
<br />
== Topeka Police ==<br />
=== Map of Patrol Districts ===<br />
[[Image:Topekia_pd.gif]]<br />
<br />
== Shawnee County Fire ==<br />
=== County/Topeka Fire Radio Code List ===<br />
*10-6 Out of station, available for call<br />
*10-7 Out of service, unavailable for call<br />
*10-8 In service,<br />
*10-9 In quarters<br />
*SIG 1 Working fire, can be controlled with available resources<br />
*SIG 2 Working fire, need additional resources<br />
*SIG 8 Person trapped (used for fires and auto accidents)<br />
*SIG 42 Out of service for training<br />
*SIG 99 Nothing showing- no smoke or fire<br />
=== County Fire Paging Tones on 158.835MHz ===<br />
*147- Silver Lake Fire District<br />
*401- Mission Township Fire Dept.<br />
*402- Auburn Fire District<br />
*403- Dover Fire District<br />
*404- Rossville Fire District<br />
*405- Soldier Township Fire Dept<br />
*406- Shawnee Heights Fire District<br />
<br />
Search:KansasFTO<br />
<br />
[[Category:Great Plains Region]]<br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Shawano_County_(WI)&diff=45610Shawano County (WI)2009-10-26T13:32:09Z<p>Loumaag: </p>
<hr />
<div>{{Collaboration<br />
|Statename=Shawano County Wisconsin<br />
|StateDB=[http://www.radioreference.com/apps/db/?ctid=3110 {{color|white| Shawano County DB]}}<br />
|Stateforum=[http://www.radioreference.com/forums/wisconsin-radio-discussion-forum/ {{color|white|Wisconsin Forum}}] }}<br />
<br />
==Fire and EMS Pager Tones==<br />
<br />
<pre><br />
Mattoon Fire Department 1743.0 1985.0 (Plectron)<br />
</pre><br />
<br />
*Remaining agencies use Motorola QuickCall II, Reed Group 2<br />
<br />
<pre><br />
Belle Plaine FD 707.3 / 788.5<br />
Birnamwood FD 600.9 / 746.8<br />
Birnamwood EMS 600.9 / 707.3<br />
Bonduel FD 746.8 / 832.5<br />
Bonduel EMS 746.8 / 788.5<br />
Bowler, WI DNR 832.5 / 669.9<br />
Bowler FD 832.5 / 832.5<br />
Cecil FD 634.5 / 879.0<br />
Grant FD 707.3 / 634.5<br />
Gresham FD 707.3 / 879.0<br />
Gresham EMS 707.3 / 746.8<br />
Hartland FD 746.8 / 746.8<br />
Navarino FD 879.0 / 746.8<br />
Navarino EMS 928.1 / 928.1<br />
Pella FD 788.5 / 832.5<br />
Pella EMS 788.5 / 879.0<br />
Shawano FD 788.5 / 788.5<br />
Stockbridge FD 928.1 / 634.5<br />
Stockbridge EMS 928.1 / 600.9<br />
Tigerton FD 669.9 / 600.9<br />
Tigerton EMS 669.9 / 634.5<br />
Wittenberg FD 634.5 / 669.9<br />
Wittenberg EMS 634.5 / 707.3<br />
</pre><br />
<br />
==Unit Numbering==<br />
<br />
<pre><br />
114 Shawano Police Parking Enforcement<br />
400's Wisconsin State Patrol Troopers<br />
DA500 District Attorney<br />
EG500 Emergency Management<br />
501-548 Shawano County Sheriff<br />
549 Birnamwood Police<br />
550-570 Shawano City Police<br />
578-579 Coroner<br />
580-585 Mohican Nation Police<br />
588 Paper Service<br />
590 Gresham Ambulance<br />
<br />
91 Med 1: Wittenberg Ambulance<br />
91 Med 2: Wittenberg Ambulance<br />
592 Med 1: Tigerton Ambulance<br />
592 Med 2: Tigerton Ambulance<br />
63 Med 1: Birnamwood Ambulance<br />
63 Med 2: Birnamwood Ambulance<br />
594: Mattoon Ambulance<br />
595: Shawano Ambulance<br />
596: Shawano Ambulance<br />
597: Shawano Ambulance<br />
598: Shawano Ambulance<br />
599: Shawano Ambulance<br />
<br />
N.E.W. 50: North East Wisconsin Rescue-Pulaski<br />
N.E.W. 51: North East Wisconsin Rescue-Pulaski<br />
<br />
601-602 County Park Rangers<br />
61x Bonduel Police<br />
651 Tigerton Police<br />
697-698 Mohican Nation Conservation Wardens<br />
800's Sheriff Administration<br />
900's Sheriff Corrections Units<br />
4400's Wisconsin State Patrol (Motor Carrier Inspectors)<br />
C-#'s Wisconsin DNR Units<br />
</pre><br />
<br />
Search:WisconsinFTO<br />
<br />
[[Category:Midwest Region]]<br />
[[Category:FTOs]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Medevac_(TX)&diff=36672Medevac (TX)2009-06-29T14:14:27Z<p>Loumaag: /* Unconfirmed Frequencies */ Adding suplemental instruction</p>
<hr />
<div>== Unconfirmed Frequencies ==<br />
The following unconfirmed frequencies are not listed in the RadioReference Database.<br />
<br />
If you can '''confirm''' that any of these are used, please [http://www.radioreference.com/apps/submit/?aid=1581 submit] the info, including any PL tones/DPL codes to the database; do not edit these entries except to remove them entirely once you have submitted the data properly.<br />
=== Air Evac Lifeteam ===<br />
* Big Spring [http://www.radioreference.com/apps/db/?cs=WQIF745 152.375]<br />
* Brownwood (2 listings, unknown if either is current)<br />
* Carrizo Springs [http://www.radioreference.com/apps/db/?cs=WQIA711 160.080]<br />
* Hondo (unknown)<br />
* Killeen [http://www.radioreference.com/apps/db/?cs=WQJU811 160.170]<br />
* Lufkin [http://www.radioreference.com/apps/db/?cs=WQFK913 159.705]<br />
* Marble Falls (unknown)<br />
* San Marcos (unknown)<br />
* West [http://www.radioreference.com/apps/db/?cs=WQFK912 159.690]<br />
* Wharton [http://www.radioreference.com/apps/db/?cs=WQIA711 153.215]<br />
<br />
=== Southwest Med Evac ===<br />
* Abilene [http://www.radioreference.com/apps/db/?cs=WQFU808 160.020]<br />
* Midland [http://www.radioreference.com/apps/db/?cs=WQFU808 151.580]<br />
* Snyder [http://www.radioreference.com/apps/db/?cs=WQFU808 151.520]<br />
<br />
== Related Links ==<br />
* [http://www.aerocare.org Aerocare] Lubbock<br />
* [http://www.lifeteam.net Air Evac Lifeteam]<br />
* [http://www.txairlife.com AirLIFE] San Antonio<br />
* [http://www.careflite.org CareFlite] Dallas/Fort Worth<br />
* [http://www.mchodessa.com/services/carestar/front CareStar] Odessa<br />
* [http://www.etmc.org/air1.htm East Texas Medical Center Air 1]<br />
* [http://www.haloflight.org HALO-Flight] Corpus Christi<br />
* [http://www.lifestar1.org/index.htm Lifestar] Amarillo and the entire TX panhandle<br />
* [http://www.memorialhermann.org/workarea/linkit.aspx?linkidentifier=id&itemid=3550 Memorial Hermann Life Flight] Houston<br />
* [http://www.wnj.org/lifestar.asp North Texas Life Star] (Air Evac Lifeteam)<br />
* [http://www.phihelico.com/Aeromedical_Services.html PHI Air Medical]<br />
* [http://www.phiairmedical.com PHI Air Medical]<br />
* [http://www.omniflight.com/southwestmedevac Southwest Med Evac]<br />
* [http://www.starflightrescue.com STAR Flight] Austin<br />
<br />
<br />
<br />
[[Category:Southern Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Medevac_(TX)&diff=36671Medevac (TX)2009-06-29T14:12:15Z<p>Loumaag: Changed an edited entry back to the way it was to begin with. Some clown changed it to something strange.</p>
<hr />
<div>== Unconfirmed Frequencies ==<br />
The following unconfirmed frequencies are not listed in the RadioReference Database.<br />
<br />
If you can confirm that any of these are used, please [http://www.radioreference.com/apps/submit/?aid=1581 submit] the info, including any PL tones/DPL codes to the database.<br />
=== Air Evac Lifeteam ===<br />
* Big Spring [http://www.radioreference.com/apps/db/?cs=WQIF745 152.375]<br />
* Brownwood (2 listings, unknown if either is current)<br />
* Carrizo Springs [http://www.radioreference.com/apps/db/?cs=WQIA711 160.080]<br />
* Hondo (unknown)<br />
* Killeen [http://www.radioreference.com/apps/db/?cs=WQJU811 160.170]<br />
* Lufkin [http://www.radioreference.com/apps/db/?cs=WQFK913 159.705]<br />
* Marble Falls (unknown)<br />
* San Marcos (unknown)<br />
* West [http://www.radioreference.com/apps/db/?cs=WQFK912 159.690]<br />
* Wharton [http://www.radioreference.com/apps/db/?cs=WQIA711 153.215]<br />
<br />
=== Southwest Med Evac ===<br />
* Abilene [http://www.radioreference.com/apps/db/?cs=WQFU808 160.020]<br />
* Midland [http://www.radioreference.com/apps/db/?cs=WQFU808 151.580]<br />
* Snyder [http://www.radioreference.com/apps/db/?cs=WQFU808 151.520]<br />
<br />
== Related Links ==<br />
* [http://www.aerocare.org Aerocare] Lubbock<br />
* [http://www.lifeteam.net Air Evac Lifeteam]<br />
* [http://www.txairlife.com AirLIFE] San Antonio<br />
* [http://www.careflite.org CareFlite] Dallas/Fort Worth<br />
* [http://www.mchodessa.com/services/carestar/front CareStar] Odessa<br />
* [http://www.etmc.org/air1.htm East Texas Medical Center Air 1]<br />
* [http://www.haloflight.org HALO-Flight] Corpus Christi<br />
* [http://www.lifestar1.org/index.htm Lifestar] Amarillo and the entire TX panhandle<br />
* [http://www.memorialhermann.org/workarea/linkit.aspx?linkidentifier=id&itemid=3550 Memorial Hermann Life Flight] Houston<br />
* [http://www.wnj.org/lifestar.asp North Texas Life Star] (Air Evac Lifeteam)<br />
* [http://www.phihelico.com/Aeromedical_Services.html PHI Air Medical]<br />
* [http://www.phiairmedical.com PHI Air Medical]<br />
* [http://www.omniflight.com/southwestmedevac Southwest Med Evac]<br />
* [http://www.starflightrescue.com STAR Flight] Austin<br />
<br />
<br />
<br />
[[Category:Southern Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Medevac_(TX)&diff=36670Medevac (TX)2009-06-29T14:07:54Z<p>Loumaag: /* Unconfirmed Frequencies */ corrected spelling</p>
<hr />
<div>== Unconfirmed Frequencies ==<br />
The following unconfirmed frequencies are not listed in the RadioReference Database.<br />
<br />
If you can confirm that any of these are used, please [http://www.radioreference.com/apps/submit/?aid=1581 submit] the info, including any PL tones/DPL codes to the database.<br />
=== Air Evac Lifeteam ===<br />
* Big Spring [http://www.radioreference.com/apps/db/?cs=WQIF745 152.375]<br />
* Brownwood (2 listings, unknown if either is current)<br />
* Carrizo Springs [http://www.radioreference.com/apps/db/?cs=WQIA711 160.080]<br />
* Hondo (unknown)<br />
* Killeen [http://www.radioreference.com/apps/db/?cs=WQJU811 160.170]<br />
* Lufkin [http://www.radioreference.com/apps/db/?cs=WQFK913 159.705]<br />
* Marble Falls (unknown)<br />
* San Marcos (unknown)<br />
* West [http://www.radioreference.com/apps/db/?cs=WQFK912 151.4000]<br />
* Wharton [http://www.radioreference.com/apps/db/?cs=WQIA711 153.215]<br />
<br />
=== Southwest Med Evac ===<br />
* Abilene [http://www.radioreference.com/apps/db/?cs=WQFU808 160.020]<br />
* Midland [http://www.radioreference.com/apps/db/?cs=WQFU808 151.580]<br />
* Snyder [http://www.radioreference.com/apps/db/?cs=WQFU808 151.520]<br />
<br />
== Related Links ==<br />
* [http://www.aerocare.org Aerocare] Lubbock<br />
* [http://www.lifeteam.net Air Evac Lifeteam]<br />
* [http://www.txairlife.com AirLIFE] San Antonio<br />
* [http://www.careflite.org CareFlite] Dallas/Fort Worth<br />
* [http://www.mchodessa.com/services/carestar/front CareStar] Odessa<br />
* [http://www.etmc.org/air1.htm East Texas Medical Center Air 1]<br />
* [http://www.haloflight.org HALO-Flight] Corpus Christi<br />
* [http://www.lifestar1.org/index.htm Lifestar] Amarillo and the entire TX panhandle<br />
* [http://www.memorialhermann.org/workarea/linkit.aspx?linkidentifier=id&itemid=3550 Memorial Hermann Life Flight] Houston<br />
* [http://www.wnj.org/lifestar.asp North Texas Life Star] (Air Evac Lifeteam)<br />
* [http://www.phihelico.com/Aeromedical_Services.html PHI Air Medical]<br />
* [http://www.phiairmedical.com PHI Air Medical]<br />
* [http://www.omniflight.com/southwestmedevac Southwest Med Evac]<br />
* [http://www.starflightrescue.com STAR Flight] Austin<br />
<br />
<br />
<br />
[[Category:Southern Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Medevac_(TX)&diff=36669Medevac (TX)2009-06-29T14:06:05Z<p>Loumaag: /* Related Links */ Added the Lifestar entry</p>
<hr />
<div>== Unconfirmed Frequencies ==<br />
The following uncomfirmed frequencies are not listed in the RadioReference Database.<br />
<br />
If you can confirm that any of these are used, please [http://www.radioreference.com/apps/submit/?aid=1581 submit] the info, including any PL tones/DPL codes to the database.<br />
=== Air Evac Lifeteam ===<br />
* Big Spring [http://www.radioreference.com/apps/db/?cs=WQIF745 152.375]<br />
* Brownwood (2 listings, unknown if either is current)<br />
* Carrizo Springs [http://www.radioreference.com/apps/db/?cs=WQIA711 160.080]<br />
* Hondo (unknown)<br />
* Killeen [http://www.radioreference.com/apps/db/?cs=WQJU811 160.170]<br />
* Lufkin [http://www.radioreference.com/apps/db/?cs=WQFK913 159.705]<br />
* Marble Falls (unknown)<br />
* San Marcos (unknown)<br />
* West [http://www.radioreference.com/apps/db/?cs=WQFK912 151.4000]<br />
* Wharton [http://www.radioreference.com/apps/db/?cs=WQIA711 153.215]<br />
<br />
=== Southwest Med Evac ===<br />
* Abilene [http://www.radioreference.com/apps/db/?cs=WQFU808 160.020]<br />
* Midland [http://www.radioreference.com/apps/db/?cs=WQFU808 151.580]<br />
* Snyder [http://www.radioreference.com/apps/db/?cs=WQFU808 151.520]<br />
<br />
== Related Links ==<br />
* [http://www.aerocare.org Aerocare] Lubbock<br />
* [http://www.lifeteam.net Air Evac Lifeteam]<br />
* [http://www.txairlife.com AirLIFE] San Antonio<br />
* [http://www.careflite.org CareFlite] Dallas/Fort Worth<br />
* [http://www.mchodessa.com/services/carestar/front CareStar] Odessa<br />
* [http://www.etmc.org/air1.htm East Texas Medical Center Air 1]<br />
* [http://www.haloflight.org HALO-Flight] Corpus Christi<br />
* [http://www.lifestar1.org/index.htm Lifestar] Amarillo and the entire TX panhandle<br />
* [http://www.memorialhermann.org/workarea/linkit.aspx?linkidentifier=id&itemid=3550 Memorial Hermann Life Flight] Houston<br />
* [http://www.wnj.org/lifestar.asp North Texas Life Star] (Air Evac Lifeteam)<br />
* [http://www.phihelico.com/Aeromedical_Services.html PHI Air Medical]<br />
* [http://www.phiairmedical.com PHI Air Medical]<br />
* [http://www.omniflight.com/southwestmedevac Southwest Med Evac]<br />
* [http://www.starflightrescue.com STAR Flight] Austin<br />
<br />
<br />
<br />
[[Category:Southern Region]]</div>Loumaaghttps://wiki.radioreference.com/index.php?title=Medevac_(TX)&diff=36667Medevac (TX)2009-06-29T13:58:54Z<p>Loumaag: /* Air Evac Lifeteam */ Fixed a link entry</p>
<hr />
<div>== Unconfirmed Frequencies ==<br />
The following uncomfirmed frequencies are not listed in the RadioReference Database.<br />
<br />
If you can confirm that any of these are used, please [http://www.radioreference.com/apps/submit/?aid=1581 submit] the info, including any PL tones/DPL codes to the database.<br />
=== Air Evac Lifeteam ===<br />
* Big Spring [http://www.radioreference.com/apps/db/?cs=WQIF745 152.375]<br />
* Brownwood (2 listings, unknown if either is current)<br />
* Carrizo Springs [http://www.radioreference.com/apps/db/?cs=WQIA711 160.080]<br />
* Hondo (unknown)<br />
* Killeen [http://www.radioreference.com/apps/db/?cs=WQJU811 160.170]<br />
* Lufkin [http://www.radioreference.com/apps/db/?cs=WQFK913 159.705]<br />
* Marble Falls (unknown)<br />
* San Marcos (unknown)<br />
* West [http://www.radioreference.com/apps/db/?cs=WQFK912 151.4000]<br />
* Wharton [http://www.radioreference.com/apps/db/?cs=WQIA711 153.215]<br />
<br />
=== Southwest Med Evac ===<br />
* Abilene [http://www.radioreference.com/apps/db/?cs=WQFU808 160.020]<br />
* Midland [http://www.radioreference.com/apps/db/?cs=WQFU808 151.580]<br />
* Snyder [http://www.radioreference.com/apps/db/?cs=WQFU808 151.520]<br />
<br />
== Related Links ==<br />
* [http://www.aerocare.org Aerocare] Lubbock<br />
* [http://www.lifeteam.net Air Evac Lifeteam]<br />
* [http://www.txairlife.com AirLIFE] San Antonio<br />
* [http://www.careflite.org CareFlite] Dallas/Fort Worth<br />
* [http://www.mchodessa.com/services/carestar/front CareStar] Odessa<br />
* [http://www.etmc.org/air1.htm East Texas Medical Center Air 1]<br />
* [http://www.haloflight.org HALO-Flight] Corpus Christi<br />
* [http://www.memorialhermann.org/workarea/linkit.aspx?linkidentifier=id&itemid=3550 Memorial Hermann Life Flight] Houston<br />
* [http://www.wnj.org/lifestar.asp North Texas Life Star] (Air Evac Lifeteam)<br />
* [http://www.phihelico.com/Aeromedical_Services.html PHI Air Medical]<br />
* [http://www.phiairmedical.com PHI Air Medical]<br />
* [http://www.omniflight.com/southwestmedevac Southwest Med Evac]<br />
* [http://www.starflightrescue.com STAR Flight] Austin<br />
<br />
<br />
<br />
[[Category:Southern Region]]</div>Loumaag