scanvin said:Just got a bcd396. Purchased ARC396 and am happy with how it is. I had some trouble getting it to import the RR database correctly fot Tacoma, but did some pasteing and have it working. I keep hitting a couple of encrypted and 'lnk' conversations, but it's not being translated. I'm assuminig these are apco 25 digital, and that it should happen. Anyway, I'll be watching this trhead.
steve
scanvin said:I understand ID Scan and ID Search concepts, but how do you identify talkgroups, and does ID Search reveal new frequencies you haven't programmed in to the scanner?
Any help would be appreciated.
olowy said:Have you come across TGID 46000 and able to ID it?
Also let me know if you monitor Ft Lewis on the 300mhz. I am still having trouble monitoring it. I know Chris P had some success and I have tried to make some of his suggested chnages like playing with P25 level but it does not seem to work. I am trying to figure it out if it is a range issue or an issue with my scanner.
Mainsail said:Two of the IDs are completely out of what I would consider a normal TGID should be, specifically 16816 and 16818, both stopped the scan but didn’t transmit any audio.
Mainsail said:Ok, disregard my last. I didn’t have my notes in front of me when I wrote that.
43376 is what I believe to be CATM, using the call signs ‘Dragon’ and ‘Ammo’.
46000 I believe to be Munitions Maintenance. They test and repair the aircraft defensive systems (flares dispensing systems).
41008 is Command Post using the call sign ‘Cascade Ops’ – very infrequent use
42192 is the fire/crash net
I’m still working on about a dozen others.
SkipSanders said:16816 is a valid talkgroup. (If you can divide a talkgroup number you see displayed by 16, and it's an even multiple, it's valid for a Motorola smartnet)
15818 is actually the same talkgroup, with a status bit set, in this case, bit 2, which says that the talkgroup is currently in 'emergency' status.
The status bits work like this:
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 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
Just a bit of explanation, 'patched' means the system has tied together two or more talkgroups, anything said on any of them will come out on all. Patching is used when units on several talkgroups must be able to hear and talk to each other.
'Multi-select' is similar, but not quite. Multi means the dispatcher has selected several groups at once to talk out on, but what's said by units on one of the talkgroups will be heard only by the dispatcher and the other units on that talkgroup. Multi is often used for things like Fire Dispatching, where the department wants the dispatch heard on 1)The actual dispatch channel 2)Some admin channel where the big fellas can hear them without then having to listen to the followup traffic, and 3) Maybe some alternate channel they also want to know about dispatches as they occur.
Normally you should have your scanner set to ignore status bits, and it'll then report only the base group number, not the 'status bit enhanced' numbers. If you set the scanner to not ignore status bits, and you want to monitor only selected talk groups, you'll have to enter each seperate status bit modified number as a seperate talk group, as it'll only stop in talkgroup scan mode on group numbers you've actually entered.
Here's my notes so far:olowy said:I think 43312 is Aircraft Maintance Silver team. 41232 I thought might be related to dispatching busses to pickup crews, but if memorty serves me right there is other chatter on it as well. I also IDed 42192 after one of their exercises.
I also have picked up TGIDs that seem "outside the norm" of 4xxxx such as 58064, 59872, 12527, 35056, 64899, 65281.
mainsiail said:Originally Posted by Mainsail
Ok, disregard my last. I didn’t have my notes in front of me when I wrote that.
43376 is what I believe to be CATM, using the call signs ‘Dragon’ and ‘Ammo’.
46000 I believe to be Munitions Maintenance. They test and repair the aircraft defensive systems (flares dispensing systems).
41008 is Command Post using the call sign ‘Cascade Ops’ – very infrequent use
42192 is the fire/crash net
I’m still working on about a dozen others.
olowy said:So lets take TGID 43376 mentioned above. I have also picked up 43378. How do you tell whether it is a different TGID or one that you set up above? Is it simply if you are monitoring status bits or not?
Mainsail said:Here's my notes so far:
ID NAME Call Sign(s)
16816 ?
16818 ?
41008 COMMAND POST CASCADES OPS
41040 VOICE USER UNKNOWN sometimes encrypted
41048
41168 COMMAND POST?
41200 Appears to be exercise coordination HALO CALL SIGN
41232 ATOC
41264 BATTLEAXE? Penguin Cash Joker Panther
41272 ?
41296 EET Net XP call sign
41488 Munitions? Police Alternate?
41552 SECURITY POLICE
41744 TOWER/GROUND CONTROL NET
41808 CIVIL ENGINEERS
42064 FUELS
42128 AIRCREW TRANSPORTATION
42192 FIRE - CRASH NET
42224 Voice Decon? Tender
42256 COMMAND?
42320 CIVIL ENGINEERS, ELECTRICAL
42328 Encrypted?
42384 EOD Call Sign Crash?
42416 NAV AID MAINT NAV 1 call sign
42448 Telephone Maintenance Call sign Wire
42450 ? Stopped but no audio
42544 CE?
42992 NCC
43000 Encrypted?
43216 BLACKJACK or MIKE BASE MAINT SUPPORT
43218
43224 Encrypted?
43248 BLUE MAINT
43280 SABER LEAD PRO-SUPERVISOR
43312 SILVER MAINT
43344 MAINT - AIRCRAFT TOW
43376 CATM AMMO - DRAGON CALL SIGNs
45104 Voice Bulldog
45552 SOAP Call Sign HuskyDog
46000 MUNITIONS MAINT?
41520 ?
58064 Airevac Control Misty
45168 Voice
Is it possible to explain that in such a way that I could understand? I have no idea what a status bit is, or what that means.olowy said:Here are the status bits you are picking up and why so many of those are encrypted:
41272 - 41264+8 DES Encryption talkgroup
42328 - 42320+8 DES Encryption talkgroup
42450 - 42448+2 Emergency
43000 - 42992+8 DES Encryption talkgroup
43218 - 43216+2 Emergency
43224 - 43216+8 DES Encryption talkgroup
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 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 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.
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 pops up which is seen as a higher priority to 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 adminsitrator 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. With the early versions of the Radio Shack PRO-92 you saw this trouble as it used only the sub-audible data to track trunked systems.