Greensbor EMS Dispatch Trunk
- Thread starter crazyccrn
- Start date
- Status
8880 is the correct fleetcode for Guilford EMS, 8883 I think was entered in error
jeffmulter
Member
- Joined
- Apr 29, 2001
- Messages
- 1,456
- Reaction score
- 0
I'm not familiar with the Greensboro system, but 8883 might be correct, if the talkgroup is being crosspatched to another talkgroup on the system.
Within the Uniden I-D number format, there are 16 variations for a Motorola talkgroup I-D ... 8880, 8881, 8882, etc. These are often referred to as status bit variations.
When a talkgroup is being operated in a normal mode - no crosspatching, no multiselect, no encryption, etc - the talkgroup will decode as 8880.
When the talkgroup is being operated in one of the special modes, the I-D number will increase by a number related to which special mode is in use.
A talkgroup being operated as crosspatched to another talkgroup will decode as having a status bit variation of +3, or 8883.
The first trunktrackers could not adjust for the variation. If a talkgroup was sometimes used in both normal and a special mode, you had to program in both I-D numbers to hear the talkgroup in scan mode.
Of the newer trunktrackers, some will adjust for the I-D variations by default. Others, like the Uniden 250 or 246T, can be programmed to recognize or ignore the variation.
Here's the status bit variation chart posted with the trunking system information, from the information section on RadioReference at:
http://radioreference.com/modules.php?name=Content&pa=showpage&pid=1
TTID + # 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
Jeff Multer
Fort Mill, S.C.
Within the Uniden I-D number format, there are 16 variations for a Motorola talkgroup I-D ... 8880, 8881, 8882, etc. These are often referred to as status bit variations.
When a talkgroup is being operated in a normal mode - no crosspatching, no multiselect, no encryption, etc - the talkgroup will decode as 8880.
When the talkgroup is being operated in one of the special modes, the I-D number will increase by a number related to which special mode is in use.
A talkgroup being operated as crosspatched to another talkgroup will decode as having a status bit variation of +3, or 8883.
The first trunktrackers could not adjust for the variation. If a talkgroup was sometimes used in both normal and a special mode, you had to program in both I-D numbers to hear the talkgroup in scan mode.
Of the newer trunktrackers, some will adjust for the I-D variations by default. Others, like the Uniden 250 or 246T, can be programmed to recognize or ignore the variation.
Here's the status bit variation chart posted with the trunking system information, from the information section on RadioReference at:
http://radioreference.com/modules.php?name=Content&pa=showpage&pid=1
TTID + # 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
Jeff Multer
Fort Mill, S.C.
ScannerMan929
Member
Guilford County\Greensboro does not use crosspatching at all; or, if they do, I have not seen it used before. 8880 is the correct talkgroup ID for GC EMS Dispatch, which is operated in analog mode.
jeffmulter
Member
- Joined
- Apr 29, 2001
- Messages
- 1,456
- Reaction score
- 0
An opportunity to "preach" here, folks ...
Occasionally, monitor your local Motorola systems in search - rather than scan - mode.
If your scanner has the option of turning off / on the status bit correction, set the scanner so that it will not adjust for altered status bits when you do the search.
I can't tell you how many times people haven't realized some their their local system's talkgroups are being patched, simply because they have the scanner set to automatically adjust for the status bit variations.
In my area, both Charlotte-Mecklenberg Police and the South Carolina Highway Patrol use patching full-time on some dispatch talkgroups.
Jeff Multer
Occasionally, monitor your local Motorola systems in search - rather than scan - mode.
If your scanner has the option of turning off / on the status bit correction, set the scanner so that it will not adjust for altered status bits when you do the search.
I can't tell you how many times people haven't realized some their their local system's talkgroups are being patched, simply because they have the scanner set to automatically adjust for the status bit variations.
In my area, both Charlotte-Mecklenberg Police and the South Carolina Highway Patrol use patching full-time on some dispatch talkgroups.
Jeff Multer
As far as I know, and I may be dead wrong and may have missed your question's intent and may also be trying to tell Noah about the flood, but the "bare" Guilford EMS dispatch is 8880, it's analog, and it's the talkgroup that's continuously system-patched to the SIM (Switched Interface Module) that produces the 155.115 csq transmitter audio. The 8880 shouldn't change unless there's "add-on" cross patching going on, which is entirely possible.
thumbtrap
Member
I set my 246T to set status bit, search, and it stops on 8880. I'm not certain why it would be helpful to crosspatch it to another talkgroup on the same system, AFAIK all radios in the guilford system can at least talk on the dispatch frequencies for the other services (possibly excepting GSO PD, as they're digital, and I don't think our radios are digital capable. I do know I occasionally hear digital tx on MHFDTAC (15056).
It's quite common to patch an analog TG and a digital TG in co-located systems and create a single multi-level talkgroup for mutual aid purposes. In general, if one talkgroup is patched to another talkgroup, that's cross patching and implies an operator selected function and implies that the patch is temporary. If it's slaved to another group, it's considered multicasting and implies that it's a system interconnect, and also implies that it's more than temporary.
Some are intrasystem interconnects done at the base control level, some are intersystem interconnects at co-located sites, some are operator initiated thru a patch panel type of software at the consoles, and some are done by selective remote patching thru devices like the ACU-1000 from JPS. Remote selective devices and patch panel connections are rarely permanent.
Some are intrasystem interconnects done at the base control level, some are intersystem interconnects at co-located sites, some are operator initiated thru a patch panel type of software at the consoles, and some are done by selective remote patching thru devices like the ACU-1000 from JPS. Remote selective devices and patch panel connections are rarely permanent.
- Status
