Hello Ken,
> I've been using Linrad (first under Win 7 and now under Win 10) with an
> FCD+ for over a year now with very good results. However, out of nowhere,
> it seems as if the Linrad/FCD+ combo just doesn't work as well as it once
> did. And I've been noticing "RX_UNDERRUNS ERROR xxx" where the error
> reported changes. For example, I've seen Error 5, Error 23, Error 525 and a
> few others.
The message RX_UNDERRUN ERROR xxx indicates a SERIOUS error. The number
xxx simply tells how many times the error occured. It is OK if you
see this error while doing something CPU intensive in another application,
but you must be aware that the Linrad output is corrupted while RX_UNDERRUN
ERROR xxx is displayed with a new xxx.
You should NEVER see this message during normal operation - it means that
data is probably corrupted and in wsjt decodes will not be good.
> And by "doesn't work as well as it once did" means if doesn't seem to have
> the sensitivity it once did and I don't decode anywhere near as "easily" as
> it once did. My comparison is that my TS2k/WSJT 10 works as well as it ever
> did.
>
> I'm pretty sure I haven't added anything that using more resources in the
> computer
Never used Microsoft Update?? (Hard to avoid it in Win 10....)
I suggest you install dpclat:
http://www.thesycon.de/deu/latency_check.shtml
Excessive dpc latency could be a problem although not very likely.
A more common problem is that you are out of ram. The "clever" operating
system would then move Linrad data areas to the hard disk causing memory
access to become far too slow. (Some other application might use
a lot of ram or you have set very large storage times in Linrad.)
What do you see in the lower left corner? xx% (yy%)
Today you can run FCD Pro+ without an ExtIO dll with Linrad. In the setup
menu, select A to get a list of soundcards. The Funcube will be one of
the devices on the list. Select it. Then select FDC pro plus as the radio
hardware to use with your soundcard.
73
Leif