Actions

Difference between revisions of "Motorola Type II"

From The RadioReference Wiki

Line 1: Line 1:
Motorola Type II systems refer to the the second generation Motorola Trunking systems that replaced Fleets and Subfleets with the concept of talkgroups and individual radio IDs. There are no dependencies on Fleetmaps, therefore there are no limitations to how many radio ids that can participate on a talkgroup. This allows for greater flexibility for the agency.
+
Motorola Type II systems refer to the second generation Motorola [[trunking|trunked radio systems]] that replaced fleets and subfleets with the concept of [[talkgroups]] and individual radio IDs. There are no dependencies on fleetmaps, therefore there are no limitations to how many radio ids that can participate on a talkgroup. This allows for greater flexibility for the agency.
  
 
----
 
----
Line 12: Line 12:
 
* [[APCO-16]] Compliant
 
* [[APCO-16]] Compliant
  
Type II Smartnet systems uses status bits for special transmissions such as Emergency, Patches, DES/DVP scrambled transmissions, and Multiselects on Motorola Trunking systems. Motorola Trunking radios directly interpret them for their special functions, thus no difference is noticed by the person with the radio. The Trunktracker scanners however interpret these special talkgroup status bits as different talkgroups entirely. Below is the conversion chart for these special status bits.
+
Type II Smartnet systems uses status bits for special transmissions such as Emergency, Patches, DES/DVP scrambled transmissions, and Multiselects on Motorola Trunking systems. Motorola Trunking radios directly interpret them for their special functions, thus no difference is noticed by the person with the radio. The Trunktracker scanners however interpret these special talkgroup status bits as different [[talkgroup|talkgroups]] entirely. Below is the conversion chart for these special status bits.
 
   
 
   
 
  Dec ID + # Usage
 
  Dec ID + # Usage
Line 19: Line 19:
 
  ID+1         All Talkgroup
 
  ID+1         All Talkgroup
 
  ID+2         Emergency
 
  ID+2         Emergency
  ID+3         talkgroup patch to another
+
  ID+3         Talkgroup patch to another
 
  ID+4         Emergency Patch
 
  ID+4         Emergency Patch
 
  ID+5         Emergency multi-group
 
  ID+5         Emergency multi-group
Line 33: Line 33:
 
  ID+15         Multi-select DES TG
 
  ID+15         Multi-select DES TG
  
Therefore, if a user was transmitting a multi-select call on talkgroup 1808, the trunktracker would actually receive those transmissions on 1815. Some common uses of these status bits are as follows:
+
Therefore, if a user was transmitting a multi-select call on [[talkgroup]] 1808, the trunktracker would actually receive those transmissions on 1815. Some common uses of these status bits are as follows:
  
* When a user hits their emergency button, all conversations on the talkgroup revert to the Emergency status talkgroup (ID+2) until the dispatch clears the emergency status. Therefore, if someone hit their emergency button and their radio was on talkgroup 16, all communications would switch to talkgroup 18.
+
* When a user hits their emergency button, all conversations on the [[talkgroup]] revert to the emergency status talkgroup (ID+2) until the dispatch clears the emergency status. Therefore, if someone hit their emergency button and their radio was on [[talkgroup]] 16, all communications would switch to talkgroup 18.
* A lot of Fire and EMS departments dispatch tone-outs and alarms as Multi-select communications (ID+7). Therefore, if your fire department dispatch talkgroup is 1616, and they do dispatch tone-outs and alarms as Multi-selects, then those communications will be on talkgroup 1623.
+
* A lot of Fire and EMS departments dispatch tone-outs and alarms as Multi-select communications (ID+7). Therefore, if your fire department dispatch [[talkgroup]] is 1616, and they do dispatch tone-outs and alarms as Multi-selects, then those communications will be on [[talkgroup]] 1623.
  
This can be a problem, because you will miss communications if you don't have those talkgroups programmed. By setting the Type II block you are monitoring with a fleetmap of S-1 (Mot Size A), you'll essentially get Type I subfleets for each Type II talkgroup - encompassing all of the status bits into one subfleet.
+
This can be a problem, because you will miss communications if you don't have those [[talkgroup|talkgroups] programmed. By setting the Type II block you are monitoring with a fleetmap of S-1 (Mot Size A), you'll essentially get Type I subfleets for each Type II [[talkgroup]] - encompassing all of the status bits into one subfleet.  Some scanners also allow you to disable the status bit information so that you will alwys see the ID+0 regardless of the status of the [[talkgroup]].

Revision as of 15:22, 7 February 2005

Motorola Type II systems refer to the second generation Motorola trunked radio systems that replaced fleets and subfleets with the concept of talkgroups and individual radio IDs. There are no dependencies on fleetmaps, therefore there are no limitations to how many radio ids that can participate on a talkgroup. This allows for greater flexibility for the agency.


The term Smartnet refers to a set of features made available for public safety users. This includes better security, emergency signaling, dynamic regrouping, remote radio monitoring, and other features.

The following is true of a Type II Smartnet system:

  • Up to 28 system channels
  • Up to 65535 unique radio ids
  • Up to 4000 talkgroups
  • APCO-16 Compliant

Type II Smartnet systems uses status bits for special transmissions such as Emergency, Patches, DES/DVP scrambled transmissions, and Multiselects on Motorola Trunking systems. Motorola Trunking radios directly interpret them for their special functions, thus no difference is noticed by the person with the radio. The Trunktracker scanners however interpret these special talkgroup status bits as different talkgroups entirely. Below is the conversion chart for these special status bits.

Dec ID + # 	Usage
-------------------------------------------------------
ID+0 	        Normal Talkgroup
ID+1 	        All Talkgroup
ID+2 	        Emergency
ID+3 	        Talkgroup patch to another
ID+4 	        Emergency Patch
ID+5 	        Emergency multi-group
ID+6 	        Not assigned
ID+7 	        Multi-select (initiated by dispatcher)
ID+8 	        DES Encryption talkgroup
ID+9 	        DES All Talkgroup
ID+10 	        DES Emergency
ID+11 	        DES Talkgroup patch
ID+12 	        DES Emergency Patch
ID+13 	        DES Emergency multi-group
ID+14 	        Not assigned
ID+15 	        Multi-select DES TG

Therefore, if a user was transmitting a multi-select call on talkgroup 1808, the trunktracker would actually receive those transmissions on 1815. Some common uses of these status bits are as follows:

  • When a user hits their emergency button, all conversations on the talkgroup revert to the emergency status talkgroup (ID+2) until the dispatch clears the emergency status. Therefore, if someone hit their emergency button and their radio was on talkgroup 16, all communications would switch to talkgroup 18.
  • A lot of Fire and EMS departments dispatch tone-outs and alarms as Multi-select communications (ID+7). Therefore, if your fire department dispatch talkgroup is 1616, and they do dispatch tone-outs and alarms as Multi-selects, then those communications will be on talkgroup 1623.

This can be a problem, because you will miss communications if you don't have those [[talkgroup|talkgroups] programmed. By setting the Type II block you are monitoring with a fleetmap of S-1 (Mot Size A), you'll essentially get Type I subfleets for each Type II talkgroup - encompassing all of the status bits into one subfleet. Some scanners also allow you to disable the status bit information so that you will alwys see the ID+0 regardless of the status of the talkgroup.