The question is if we really need them. So here goes:
Altitude is probably useful for some statistics in the long run, so let's keep that.
TimeToFix - with powersave, this becomes '1' very quickly, so it feels that with powersave modes enabled, this one is a bit useless.
Nr of satellites - Useful to see how it goes, but do we (in the long run) use it? I don't think so. We expect the ublox to decide if the hdop and fix is OK. So why send this?
FixType - this was useful when our code still relied on that, but we have a situation where fixtype can be 3, but we do not have a valid fix. Furthermore, what do we do when we do with fixtype? Yes, we check it in some of our code, but we just ignore everything which is not a '3'. Our code should actually care about it being a valid fix.
We could replace nr of satellites & fixtype with one flag that tells us something about the valid fix and hdop.
Do we want to always do that? Not sure. Ideally we'd just send a 'debug on' message and then start sending it out, which means supporting more message formats in the code.
Leads me to think that we can leave out the motion flags and just have a tracker that always has that? Even if it's disabled we can just send 00's maybe?
One thing that we really should do is introduce a 'debug' mode for at home/lab. Because we do see differences with on the USB cable and int he field. So what is the HDOP value in the field? Was GNSSFIXOK true or false? These flags should be added. Adding this to a 'debug' message might make sense.
Currently ,we send a few GPS details:
The question is if we really need them. So here goes:
We could replace nr of satellites & fixtype with one flag that tells us something about the valid fix and hdop. Do we want to always do that? Not sure. Ideally we'd just send a 'debug on' message and then start sending it out, which means supporting more message formats in the code.
Leads me to think that we can leave out the motion flags and just have a tracker that always has that? Even if it's disabled we can just send 00's maybe?
One thing that we really should do is introduce a 'debug' mode for at home/lab. Because we do see differences with on the USB cable and int he field. So what is the HDOP value in the field? Was GNSSFIXOK true or false? These flags should be added. Adding this to a 'debug' message might make sense.