The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz
kiwirecorder crash when no GPS lock on Kiwi
I don't know this is a high priority bug to fix, but we spent several hours today debugging a crash of kiwirecorder which we finally traced to the Kiwi not having a GPS signal.
So I thought I would post this warning in the hope I might save other kiwirecorder users some debug time.
So I thought I would post this warning in the hope I might save other kiwirecorder users some debug time.
Comments
python -u /home/pi/wsprdaemon/kiwiclient-jks-v0.1/kiwirecorder.py --freq=28124.6 --server-host=10.14.70.78 --server-port=8073 --user=wsprdaemon_v2.2h --password=none --agc-gain=60 --quiet --no_compression --modulation=usb --lp-cutoff=1250 --hp-cutoff=1750 --dt-sec=120
I execute "git clone git://github.com/jks-prv/kiwiclient" to load your recorder. Is that getting the latest version?
Yes, it occurred every time of the many it was tried it which is what prompted the investigation into why the 3rd kiwi didn't work. The only thing that was necessary to change from the non-working condition, which issued a 'string to float" conversion error, was the addition of a GPS signal on the failing kiwi. Up to the point where we discovered the problem we had been at a loss to determine what the difference was with the third receiver that kept it from working. We hadn't even considered that the presence/absence of gps would be relevant. The error seemed to be associated with the GPS and establishing gridsquare or something related.
If it is necessary, I may be able to recreate the condition and provide the output. I may need Rob's assistance to do that though.
python -v -u /home/ge/wsprdaemon/kiwiclient/kiwirecorder.py --freq=7038.6 --server-host=10.0.0.25 --server-port=8076 --user=UStest --password=kiwis_password --agc-gain=60 --quiet --no_compression --modulation=usb --lp-cutoff=1250 --hp-cutoff=1750 --dt-sec=120
Not only did it run flawlessly this time but when I looked I discovered that Rob's script, which also happened to be running with this kiwi still in the schedule *also* had successful WSPR sessions running on it. All with no GPS. The only difference was time and the fact that it had rebuilt to v1.277 .
Though repeated multiple times previously, the problem no longer seems to be reproducible.