Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Re: Drift
Good morning Alan (and all),
toggle quoted message
Show quoted text
Agreed with all you said. This discussion has gotten me wondering just how the WSPR does determine the reported figure for DRIFT and SNR. There are documents with the details, I guess I will just have to do some reading to get a better understanding. Perhaps we need to stop making this so complicated and just accept that for our simple amateur use that whatever is reported as SNR or DRIFT is OK and is acceptable and has more value as a relative figure of merit? within +/- X of the reported value rather than a absolute and precise value. VAC's add another layer of uncertainty. Yes, you can adjust sample rates in and out but I don't know enough about how it's done to feel comfortable that any loss in the conversion will have no impact. I use a couple of Lexicon Alpha USB sound cards. These have a max sample rate of 48k. However, if I just plug and go on a Windows machine I find that when I look at the properties of these devices under recording devices that Windows has defaulted them to a 44,100 sample rate.? Even though the WSPR/WSJT-X programs state that a requirement for the program is a sound card having a 48k sample rate, they work just fine with my Alpha USB sound card. I have for some time been running an experiment comparing my 40m off center fed dipole (apex just over 7 meters) and my short unterminated beverage on 40m.? One is connected to my Yaesu FT-950 and the other to my FT-817. I spent some time ensuring each radio was set up so as to be as nearly the same as the other. Each radio feeds an Alpha USB sound card, one to a Windows 10 machine and the other to a Raspberry Pi. WSJT-X v1.7.0 is used on both the Windows 10 and Raspberry Pi where the setting for each program are the same. I don't know if you are familiar with KB9AMG's WSPR statistics web page. This is the link to the one showing 40m listed are callsigns and counts relative to the placing for that specific band. I am using both of my callsigns ve3gtc and ve3ghm, stats for each here: ,281676 ,281369 Those last two links may not work from day to day. I don't know if they are more or less static based on callsign or dynamically created every day. In any case, you can see that the counts for 40m for these two calls various from day to day, sometimes a little, sometimes a lot. You too have noted this phenomenon in some of your comparisons. More interesting is that for the same date-time, one will report stations that the other does not and vice versa, not always but sometimes. And there does not seem to be a preference for one over the other to be providing decodes that the other is not. Are these differences the result of propagation and antenna characteristics (most likely) or the result of differences in processing (Windows PC vs Linux Raspberry pi) and other hardware (FT-950 vs FT-817) (not as likely unless the software and hardware are grossly and differently configured). Spot checking of wspr spots has shown that when the same TX is received at the same time by both that DRIFT is never different but SNR is sometimes the same, sometimes different where sometimes the dipole has provided the highest SNR and other times not. I have read through G3ZIL's report but need to spend some more time with it; I am not yet quite sure what is being reported. Cheers, Graham ve3gtc On 2017-11-24 10:54, Alan G4ZFQ wrote:
?A quickGraham, |
to navigate to use esc to dismiss