Another possibility is some code that attempts to detect a Datum Starloc
receiver. These look like Thunderbolts, but have VERY buggy firmware. If
Heather sees a condition where all satellites are being reported at az/el = 0,
Heather sets a flag that the device is a Starloc and attempts to work around
the firmware bugs (the Starloc does not calculate sat az/el info and always
sends 0,0).
I noticed that in the log dump that the problem started when the receiver was
tracking only 3 satellites. Perhaps your antenna is not very good and that
caused a signal dropout and the Tbolt started sending null satellite position
info and that triggered the Starloc (aka Craploc) mode. The next version of
Heather tightens up the constraints for Starloc detection and also only will
switch modes if the receiver type has been auto-detected... there is now a
receiver type setting that forces Starloc mode.
---
> Attached is the log and it seems that the end near the crash begins with
> skipped time stamps and
changes in receiver mode.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
