End code and status bit settings in the 396XT

Status
Not open for further replies.

bassman21

Member
Premium Subscriber
Joined
Feb 14, 2010
Messages
38
Location
Houston, TX
HI this is my first post here. This site has been a great help since I have gotten back into scanning.

I live in Harris County/Houston, TX and listen mostly to the Harris County analog trunking system. I have the Uniden BCD396XT and programmed it using Freescan and this sites database. By default the 396XT is set to ignore on the status bit setting and ignore on the end code setting. Having the end code on gets rid of that annoying popping sound when the site stops transmitting. What I was wondering is there any disadvantage of having this setting on? What about the status bit setting? Is there any disadvantage to having this set to on? I have search for other post on this, but these questions are not clearly answered.
Thanks in advance!
 

Kennrth

Member
Joined
Jul 24, 2006
Messages
143
Location
Bay Shore Long Island NY
[
The Following was cut and pasted from Wikipedia

edit] 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 these status bits for their special functions, therefore no difference is noticed by the user. The Trunktracker Scanner, 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.
When an emergency is declared, the system automatically strips any patches present on the talkgroup and places the talkgroup in emergency with +2 and any patched talkgroups as a Multiselect (+7) with the console repeating subscriber audio from the talkgroup in emergency.
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. Some scanners also allow you to disable the status bit information so that you will always see the ID+0 regardless of the status of the talkgroup.

SmartNet systems also added a scanning feature, called "Priority Monitor," which permitted priority scanning of talkgroups. The subscriber radio has the choice of selecting two priority talkgroups (one high and one low priority in addition to eight non-priority talkgroups). When the radio is in the middle of a voice call it is continually receiving sub-audible data on the voice channel indicating the talkgroup activity on the other channels of the system. If a talkgroup ID appears which is seen as a higher priority than the active call, the radio will switch back to the control channel to look for the late entry data word indicating which channel to tune to.

This voice channel sub-audible datastream has a limitation in the number of bits it can use to represent a talkgroup ID. Because of this the last digit of the talkgroup ID (right-most) is removed. The radio then presumes any ID it receives is an odd-numbered talkgroup ID. This is the reason behind odd numbering of talkgroups on SmartNet systems. If the systems administrator assigned odd AND even numbered talkgroups there would be a lot of confusion with the Priority Monitor feature when reading the data over the voice channel. This was a problem with the Radio Shack PRO-92 as it used only the sub-audible data to track trunked systems.
 
Last edited:

tampatracker

Member
Premium Subscriber
Joined
Dec 9, 2007
Messages
1,197
So as not to confuse you, and by the way welcome to radio reference, here is a link to a simpler way to describe the functions,(and a lot more), you're asking about. The author includes the 396T in his contents but simply go with whats there in lieu of your unit, the 396XT, as in this case the functions we're discussing here are the same. I hope this site ( both Radio Reference and Mark's scanners), helps you as much as they've helped me. Have fun! TT.http://marksscanners.com/index.shtml
 

bassman21

Member
Premium Subscriber
Joined
Feb 14, 2010
Messages
38
Location
Houston, TX
Does anyone have a quick answer as if there is any disadvantage of setting the End Code setting to on over having it set to ignore? I know that when it is on it reads the end of transmission command on the control channel and shut the audio off immediately rather than waiting for the site to stop transmitting. Like I said it gets rid of the loud popping sound and just sounds smoother after each transmission. However I wonder if I might be losing some of the conversation with it on.
 

UPMan

In Memoriam
Uniden Representative
Joined
Apr 19, 2004
Messages
13,296
Location
Arlington, TX
End Code should be on by default. It is remotely possible that the scanner could incorrectly detect End Code that isn't actually there, sending it back to the control channel. However, this might occur once every few months of scanning. Whereas, if you leave it off you will get annoying pops on every transmission. It is primarily left in as an option for certain diagnostic purposes.
 

SCOTTER

Member
Joined
Sep 6, 2007
Messages
257
Location
SOUTH BEND IN.
On Indiana`s SAFE-T system a MOT II smartzone if I dont set END CODE to on or to analog + digital on my XT it will get hung up on a control channel sometime that day or at night it happens all the time.
 
Status
Not open for further replies.
Top