I had just updated SDRC to 3.0.25 on the same day. I had resisted the Windows 10 update to v2004 for a few months but the inevitable happened and I was told that I needed to re-boot. All 5 cables are working perfectly with the 2 radios and their native software
Both the Perseus and Discovery are producing full decodes all night using their native software (Perseus v5 and SDR#) I can’t isolate what the trigger might be.Īfter many days of uninstalling and re-installing VB-Cables and SDRC and running parallel comparisons I have eliminated the following
Just occasionally it flips back to good decodes for a while. Sometimes the overnight session would start off just fine and then return to gibberish late at night or in the early morning. I assumed it was just additional noise on 518 until I noticed that quite often the ZCZC identifier would come through clear together with the 2nd line and then it would turn to rubbish.
And then it all went bad…….Įven strong signals were decoding as gibberish with the occasional clear text for 1 or 2 words. All worked very well and my only bother was qrm on 490. Until about 2 weeks ago I had been using the HF+ Discovery, SDRConsole driving 3 receivers on 518, 490 and 486 through VB-Audio Cables into 3 instances of YaND.
0 kommentar(er)
