jks

@Martin The code isn't very robust yet against the various processing steps getting stuck or terminating without returning proper status. For example if the kiwirecorder run launched by the kiwisdr.com server doesn't act as expected there is no timeout detection. If you're zoomed out too far then the Octave TDoA process will run for a long time generating the long coastlines for the maps. There needs to be an abort/reset button and the associated cleanup.

@Jim Your Kiwi reports its status to kiwisdr.com every 15 minutes. A database is updated which is then used to build the kiwisdr.com/public page and is also used by the http://rx.linkfanel.net map. If your Kiwi has received no GPS fixes during the previous minute at the time of the report then it is removed from the database and will not be checked again until the next 15 minute reporting period. The period and the criteria are simply what was convenient at the time. With more work it could be changed.

@W1EUJ Currently position solutions requiring 4 or more satellites are needed to get timing solutions. Although Christoph has a method using a Kalman filter in which individual pseudo-ranges from a single satellite can generate subsequent timing solutions (if I remember correctly). This code is not yet integrated into a Kiwi release.

Interesting idea. Let me see what I can do. It's going to be a little while before I can release an update (things are torn apart at the moment -- lots of changes need testing).

I finally saw Oscar's latest YouTube video. Pretty neat. I've added CATSync to the list of Kiwi recommended accessories. To support the effort I bought a copy for myself even though I don't use Windows and don't own a traditional rig at present.

Nice article on rtl-sdr.com about the topic: https://www.rtl-sdr.com/locating-various-hf-transmitters-and-number-stations-with-kiwisdrs