Bad drift but ALL 12 CHANNELS GPS GOOD
Hoping for help to get my remote Kiwi receive for my 630m station going
You can find me on the Kiwi web page as FLORES AZORES
Bad drift of up to 30 Hz randomly comes and goes and makes decoding wspr or FST4 impossible
I worked hard on antenna placement to get an excellent RSSI for up to 12 CHANNELS.
But on user page stay it still shows acq pause?
Am I missing some obvious setting?
Thanks
Ron
CU8/NU6F
Comments
Hi Ron. I replied to your email just now before I saw this post. This should not be happening if you have continuous GPS solutions. Your Kiwi just now has good cal. I'm looking at a time station carrier on 15 MHz zoomed into level 14 and it's dead on -- under 1 Hz error.
Make sure on the admin GPS tab the checkbox "Acquire if Kiwi busy" is checked. Otherwise I think if you have more than one connection acquisition of new sats will be paused so as to not slow down the performance of those multiple connections. The problem with that is that when all the current sats become no longer visible you will get no new acquired sats and timing solutions. You will if the number of connected users drops below 2 however. But if that doesn't happen then freq cal will stop at some point. That checkbox will overcome the problem.
Hi Ron. I think you must have checked "acquire if busy" because I now see "GPS acq yes" in the user control panel "Stat" tab with 3 users connected.
One better way to assess frequency cal / drift than simply using zoom level 14 is to use the WSPR extension since it has an FFT display that has very good resolution. In the screenshot below I have set it to run on 30m. But tuned to a dial frequency of 14999.25 so that the time station carrier is in the middle of the display (200 Hz offset). Notice that it looks pretty good. Maybe just a tiny bit low. What's important is how stable that carrier is in the WSPR display over time with the GPS "good" sat count being a relatively large value (say larger than 4).
Hi,
Of course this option in page admin/config (bottom right) has to be in "continuous", right ?
(in the case it's been changed)
He mentioned in his email to me (but not in the post above) that it was set in continuous mode.