Above: On the left is the UM982 GPS board, center is the Carry Board that mounts the UM982, and on right is the Raspberry Pi Pico and takes the GPS signals and sends them to the Raspberry Pi5.
Above: Here is the RPi5, and the UM982 and Pi Pico in their enclosure.
Above: The master GPS antenna (location) is to the rear of the roof, and the slave antenna (heading) is to the front.
Greetings to all Kraken users!
Now some questions about the Kraken soft have moved from a private conversation to a public space. Diesel_Tech wrote: «The bug is that if the Kraken is not detecting any signals above the squelch threshold, only your location point updates on the map, and the DOA lobes, bearing lines and log file plots stay at the last place it detected a signal at. So, you can drive 5 miles, and it will look like you haven’t moved. it seems that you have not moved from your place».
At this point, I want to ask the developers of the Kraken software. Is this a software error or such a strange logic? I am asking this question because my DATHFK does not change the logic of the software in any way. I’m only doing an unconditional substitution of the HEADING value (and of course I’m transmitting GPS data from Pi5).
Making sure that @krakenrf_carl sees this.
That is correct logic. If you’ve set a squelch level, and the signal is below the squelch, the data will be frozen from the last valid reading.
As you don’t want to be getting random direction lobes that you’d get from pushing the noise floor through the MUSIC algorithm.
If you don’t want the squelch you can disable it by setting a very low value so nothing ever squelches.
