SDR Console 10-23-2017 64-bit Release with ANAN-200D
Posted: Thu Oct 26, 2017 3:45 pm
I'm not sure if what I am seeing is due to a firmware timing issue, or if I have possibly missed a setting somewhere that is causing my issue. With the ANAN-200D running protocol 2 firmware version 1.1 (the newest available) the SDR-Console definition search function correctly locates my rig. As can be seen in the video, the software starts up and receives fine for roughly 3 seconds, then it freezes up. Hitting the "Stop" button and then hitting "Start" repeats the 3 second run and lockup scenario.
I ran the 64-Bit DxDiag and it flagged the following device drivers:
1. The file umc_audioks_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
2. The file vrtaucbl.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
The NVIDIA diagnostic came up clean with a "no error" report and indicated that my NVIDIA driver and runtime files were current. Note that I am not using the CUDA core implementation in SDR Console.
So, anyone have any thoughts on something I may have missed? Although THETIS runs quite well with the current protocol 2 firmware, if it's a matter of firmware timing with my particular 200D then I'm fine with being patient!
73,
Rob W1AEX
I ran the 64-Bit DxDiag and it flagged the following device drivers:
1. The file umc_audioks_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
2. The file vrtaucbl.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
The NVIDIA diagnostic came up clean with a "no error" report and indicated that my NVIDIA driver and runtime files were current. Note that I am not using the CUDA core implementation in SDR Console.
So, anyone have any thoughts on something I may have missed? Although THETIS runs quite well with the current protocol 2 firmware, if it's a matter of firmware timing with my particular 200D then I'm fine with being patient!
73,
Rob W1AEX