jks

About

Username
jks
Joined
Visits
34,185
Last Active
Roles
Member, Administrator, Moderator
Points
470
  • Software update in progress [not a problem]

    Faster rebuilds coming soon. We are switching compilers from gcc to clang.

    M0TAZ
  • GPS antenna alternatives

    Here's an example of all sats being available on all channels on a Kiwi in Iceland. As a bonus QZSS is being received (!) The signal is weak and only 9 degrees above the horizon. It only participated in this one GPS solution before sync was lost. But it was there!

    image
    ChristophPowernumptyM0TAZ
  • TDoA known location markers

    It does this already (if I'm understanding your question correctly -- morning coffee hasn't taken hold yet).

    Before you start the process single-click on a reference station so its information is copied into the field at the lower left of the TDoA control panel. Or optionally type your own reference info, format: lat lon id description. Then the result maps will show that info in a marker in addition to the "most likely" position computed. Also, if you're specifying everything from the URL, you can just list the reference station id to have it pre-selected. Just like the Kiwis to use are specified. See below. Using the Google map ruler we can see the difference in computed to actual location is a bit over 20 km.

    image
    M0TAZ
  • GPS antenna alternatives

    It's worth noting that four more Galileo satellites (23-26) were launched on Wednesday 25 July 2018 and are currently being commissioned.
    I'm a couple days into getting each GPS channel to allow all satellite types. Very difficult (for me at least) as expected. The old inefficient way would have required 12 memory blocks and we only have 5 available (4RX4WF config). The new scheme requires only 3. But I had to learn some new Verilog and employ some tricky sequential/producer, parallel/consumer logic with pipelining issues thrown in. It isn't working yet..
    Powernumpty
  • Recent problem with band pass in saved frequencies

    I think the answer here is that when "user preferences" are finally working the very first parameter needs to be "what would you like the tuning point to be?" (carrier or passband center or even something else).

    User preferences is like the admin configuration but for Kiwi users. Any user. Not just users who also own a Kiwi. The idea is that you should be able to set a preference once and then have it apply to any Kiwi you visit in the future. This is unlike the "last remembered" values (frequency, mode etc.) saved in cookies that are specific to the current Kiwi you're using. I don't want to keep having to set the carrier point preference the first time I visit a new Kiwi.

    User preferences is taking so long because it's tricky to implement. You have to side-step some browser security problems that upset getting the behavior you want (single storage applied to multiple domains).
    M0TAZ