I want to run 'kiwiwspr.sh -w ' at Linux startup, but the old rc.local mechanism has been supplanted since Jessie OS. Implementing a command to configure this to run at startup is my next goal.

I think it may also help towards implementing any further automation of the overall process and allow John to analyse the server stats in order to determine the 'best' KiWi's to use for TDoa.

At first I want to thank you so much for your work, I was waiting for a long time for the working files from your blog & git and now my HFDF dream came true. Also thanks to John with his KiwiS

Sometimes when Galileo sats are used the positions don't agree with Navstar/QZSS (i.e. the green and red/yellow pins will be spaced some distance apart). This may be due to the well known false-peak l

I don't think Audacity is designed to us I/Q audio. HDSDR or Dream is what I use to play those files back.RonKA7U

Yeah I've been looking at that. The section about the PRN code generation is ambiguous. What I've tried implementing so far hasn't worked.

I think the fix may be for the extension to set a default waterfall speed whilst running, but there may be other ways of implementing a fix.

Fun stuff to work with. I took a screenshot of the Dream receiver working the file.RonKA7U

3965 came back on and I tested the latest kiwirecorder using southwest.ddns.net:8073 which is running v1.151 Dream worked fine for me using data played back from the recorded file.

I'll let it run another 24 hours on the new receiver and see what I get. I find I can load these files in Audacity to inspect the audio amplitude prior to running in Dream. This gives me the recording

Another interesting aspect to this kiwirecorder.py is that the Dream receiver will play the file while the file continues to be recorded. This effectively makes a near real time connection for replay

I tried this and the file plays in my Dream receiver just fine. I am currently recording and when I open a web browser pointed to the above URL, it opens and works just fine, but there is no indicatio

Which sets a DSB passband from -5 to +5 kHz for use with DRM. Using this I was able to feed the recorded file to Dream with no problems decoding at all.

And that must be okay for IQ data because Dream works when VAC'd to the browser audio output. The python code isn't doing this of course -- it just stores the IQ stream in the .wav file directly with

and my blog post "how to", for whomever might benefit.http://ka7u.us/2017/11/17/kiwisdr-setup-to-use-the-dream-receiver/

Martin,The Dream receiver is working well on my openSUSE sytem, but SoDiRa is much more difficult with DRM, it does very well with all other modes. So I use Dream for this service exclusively and thin

Today I finally managed to get every good DRM decodes (no dropouts) using both Dream and Sodira from Radio Kuwait on 15109.70KHz (yes it does seem to be slightly off-frequency).

In case this may help to explain the cause of occasional dropped-out in Dream: when dream dropped-out is internet related (packet loss, network congestion etc.), watch out for the momentous blackout i

and installed libfaad for the AAC Mono codec. No Dream plays like a dream. I'm listening to it, uninterrupted while typing this message. Oops it dropped out. The cursed audio under run strikes again.

I made a video of running Dream on Linux Mint 18. I suspect most of the DRM audio dropouts were caused by CPU usage bursts and/or hard disk I/O activity when I did the screen recording.