Re: [A-DX] USAF-HFGCS Logs

Roger Thauer
Sonntag, 13. Februar 2022, 14:41 Uhr

Am 13.02.2022 um 00:36 schrieb Thomas M. Rösner:
> Bei FAA erinnere ich mich, dass ich vor ein paar Jahren mal in der UDXF-Liste gelesen zu haben, dass u.U. eine systematische Fehlinterpretation der Dekoder sein könnte, bzw. ein Fehler oder Besonderheit in der Kodierung beim Sender ist. Ich finde leider das Posting nicht mehr.

War kein Problem......


Am 04.02.2018 um 01:54 schrieb russell.gary@...:
> Below is a FAA decode from MULTIPSK on 5708.0
> <23:58:26> ~_[Sounding THIS IS ] [from FAA         ] (his BER=22 + SINAD=07)
> I was also running SORCERER (on same SDR) at the time and there was no FAA decode but a decode of MCC at 23:59:43  (SORCERER wouldn't allow me to copy of the line).
> There is no decode for the MCC transmission on MULTIPSK that was decoded by SORCERER
> I have found SORCERER to be as sensitive to ALE and MULTIPSK and perhaps a bit more.
> I am not sure how to account for the time gap between the FAA/MCC decodes. Maybe inherent in the programs? Certainly sufficient time for additional ALE decodes.
> Not definitive but lends evident to support the bad decode theory?
> I will continue to run both programs through the night to determine if there are additional such scenarios.
> Also running PCALE which failed to decode either and only decode 3 of about 20 transmission decoded by the other programs.  May have had audio input set too high for PCALE and swamped it but in general I get far fewer decodes from PCALE when running all three simultaneously.
> Gary

FAA ist demnach ein "bad decode" von MCC bei MULTIPSK.

Und bevor jemand nach MCC fragt:     McClellan Air Force Base, 
California, USA

Hier nachzulesen:
http://www.udxf.nl/USAF-HFGCS.pdf

;-)



roger