SCAN-AID

1/24 - THIS PAGE IS UNDER CONSTRUCTION.

Please do not edit anything on the page. If you have ideas or questions, please message me on the forums or email me at starcom21@RadioReference

---

Related wiki pages https://wiki.radioreference.com/index.php?title=Scanning_101&action=edit

Monitoring MOTOTRBO (DMR) and NEXEDGE (NXDN)

Discriminator Tap "Output" https://wiki.radioreference.com/index.php/Discriminator_output

DSD Plus https://wiki.radioreference.com/index.php/DSDPlus

DMR Tier III Hytera vs Tier III CapMax (Motorola)

https://forums.radioreference.com/threads/fastlane-errors.466165/

Then, throw in a system like Selex / Leonardo ( search here for: Goosetown Tier III ). It is not a CAPMAX system, but it does not use an Area ID and does not require +1'ing the bits in the Syscode. Unfortunately, there is no OTA information sent that allows DSDPlus to distinguish that it is a Selex system, so DSDPlus presumes its a DMR TIII Standard system and shows AreaID+SiteID and +1's the bits.

I agree, after a few years of seeing TIII systems now, that it would be better to never present the AreaID+SiteID information for a system -- and instead they should be presented as just a model, network ID, and SIte ID. But, I have a feeling DSDPlus would require a significant revamp to do this, and would then require everyone to change how they present aspects of a TIII system in the DSDPlus.* files.

But let's assume that miraculously every piece of software was on the same page using Network Model, Network ID, Site ID. There is still the issue of any software knowing precisely when a SysCode is not presenting "the facts", for every TIII system variant, and thus needing to be +1'd.

I don't think any software developer is every going to get DMR TIII (including all variants -- standards compliant, Capmax, Selex, etc) 100% all the time because we do in fact know that in the DMR TIII standards there is actually an Area ID and a Site ID, and that there is a very important variable (LA -- length of Area) that is not sent over the control channel / not sent in the SysCode information -- there making it impossible to get the Area ID + Site ID combination correct 100% of the time.

GRE/Whistler scanners can't tell the difference and don't truly trunk track and maybe can't even handle TIII. Uniden scanners can't tell the difference between 100% standards compliant TIII systems and variants like CapMax and Selex. Uniden treats them all the same. SDRTrunk appears to treat them all the same (taking in no account for Area ID+Site ID or +1'ing), but I may be wrong about that -- there may be circumstances where SDRTrunk does +1'ing . I do not use it enough to know. And for anything else handling TIII, I'm pretty sure they aren't attempting to display AreaID+SiteID. 

DMR Networks

• T (Tiny) S (Small) L (Large) H (Huge)
• Huge network model we can set up up to a total of 1024 sites

Note

• I have yet to have time to get an SDR dongle working. All of my decoding is done through scanners with DSD+ and pro96com
• DSDplus FastLane Updated 2.457 12/27/23 https://forums.radioreference.com/threads/dsd-2-457-availible.467125/
• pro96com

Other Programs

• UniTrunker
• SDRtrunkers

• Channel Extractor Pro v1.0.2.4 (in development 1/24)

UNKNOWN FREQUENCY USAGE

• How to search. RR, FCC, etc.
• Antennas on a vehicle or at a building/tower site https://forums.radioreference.com/threads/identifying-unused-antennas-at-tower-site.467317/

Towers in your areas

• Try this to locate towers in your locale. ASR Registration Search https://wireless2.fcc.gov/UlsApp/AsrSearch/asrRegistrationSearch.jsp

---

Notes

• I DO NOT monitor Aircraft or MilAir. I have made attempts on monitoring Railroads, but can never find interesting to keep me listening

---

My History of Scanning

Former ScanIllinois.com website (hosted by unknown user on Angelfire hosting

---