jks
About
- Username
- jks
- Joined
- Visits
- 31,829
- Last Active
- Roles
- Member, Administrator, Moderator
- Points
- 312
Reactions
-
Direction Finding and linking existing KiwiSDRs
Wow -- check Christoph's latest post: https://github.com/jks-prv/Beagle_SDR_GPS/issues/130#issuecomment-347206064It's a plot of a ground wave TDoA solution for DCF77 using three Kiwis relatively close by. -
Direction Finding and linking existing KiwiSDRs
Christoph's latest post on https://github.com/jks-prv/Beagle_SDR_GPS/issues/130 shows how his GPS timestamps are within 20 usec of DCF77 (77.5 kHz) as received by a couple of Kiwis a few hundred km distant. Really fantastic work! -
Sound recording from multiple opened browse windows for diversity reception?
-
Sound recording from multiple opened browse windows for diversity reception?
You can't run the old kiwirecorder with v1.151 Use the current one. And you can't use the latest one from my branch on Kiwis running earlier than v1.151 See the comments above. I haven't tested the latest one with the GPS timestamp support with DRM -- and there are no DRM transmissions on right now.. -
Direction Finding and linking existing KiwiSDRs
There have been three or four people recently express interest in working on HFDF. Some on here or on Github issues or in private emails to me. I'll try and point everyone to this thread.It is important to note that V/UHF DF is significantly different from the HFDF problem due to the issues imposed by the nature of the ionosphere at HF. It is much more complicated than you would expect. But we have this wonderful resource: lots of geographically diverse Kiwi installations and now GPS timestamped IQ data thanks to Christoph's recent work (https://github.com/jks-prv/Beagle_SDR_GPS/issues/130)A recent example of V/UHF DF using RTL-SDRs: https://www.rtl-sdr.com/localizing-transmitters-to-within-a-few-meters-with-tdoa-and-rtl-sdr-dongles/Slideshow about HFDF techniques: http://www.g4axx.com/HF_Radio_Direction_Finding.pdf -
Clock drift in WSPR mode
When I connect to your Kiwi, and look at the status panel at lower left, it shows a passband center frequency of 14097.26 for your 20m WSPR connection. Why is that? It's supposed to be 14097.10 Did you bump the "dial"? The WSPRs on 30m (10140.20) and 40m (7040.10) were fine. This is exactly the 160 Hz error you see in the wsprnet.org database.Note that for the WSPR extension the freq shown in the status panel, admin page, etc. is the PB center instead of the carrier freq (dial freq) The dial freq for WSPR should be 14096.35 (750 Hz lower than 14097.10) unless you've changed the WSPR offset value on the admin page. You will see the dial freq in the frequency entry box when the WSPR extension is closed. I can't remember exactly why I did this, but my guess is that I thought it made sense to show the more familiar PB center freq for WSPR that everyone is used to.WWVH @ 15 MHz was only off 8 Hz. There were no recent GPS solutions because all the sats had drifted out of range and the acquisition process was getting locked out by the three running WSPRs. -
HF Broadcast Schedules
It's buried in the bug list, but there is an entry that says:- Use info from public databases, e.g. shortwave broadcast schedules (EiBi)
-
WSPR and who is logged on
-
DRM demod? [yes, external app Dream now working!]
-
"Initial mode" & "Initial BCB channel spacing" [fixed in v1.150]
Ugh. You are absolutely correct. Looks like I broke admin page menu select callbacks when I did a code cleanup a little while ago. I'm surprised no one else has complained about this until now. It affects 8 different menu selects on the admin pages. I'll release a fix for this right away. Thanks for mentioning it!