Actions

SCAN-AID

From The RadioReference Wiki

Revision as of 21:08, 6 January 2024 by Starcom21 (talk | contribs) (Created page with "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@Radi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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







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.



Note




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