Still thinking about this; not sure if it makes sense.
The router has a setting called ignition park mode, which makes it so the database doesn't update the lat/lon for any fixes it receives when the ignition is off. We currently use this setting. It has some unintended consequences, such as, if the router reboots while the ignition is off, it will not get a fix so long as the ignition is off. It will be reset to 0,0.
What if we reverted back to the old setting (where it will still update its internal database), but njord checks the ignition status. If it detects GNSS-based movement while the ignition is off, it doesn't report it, but rather re-reports the last sent fix.
Not sure if this is a good idea, but right now, Semtech/Sierra's toggle is a black-box that may not be functioning as expected, so I'm thinking about eliminating it.
Still thinking about this; not sure if it makes sense.
The router has a setting called ignition park mode, which makes it so the database doesn't update the lat/lon for any fixes it receives when the ignition is off. We currently use this setting. It has some unintended consequences, such as, if the router reboots while the ignition is off, it will not get a fix so long as the ignition is off. It will be reset to 0,0.
What if we reverted back to the old setting (where it will still update its internal database), but njord checks the ignition status. If it detects GNSS-based movement while the ignition is off, it doesn't report it, but rather re-reports the last sent fix.
Not sure if this is a good idea, but right now, Semtech/Sierra's toggle is a black-box that may not be functioning as expected, so I'm thinking about eliminating it.