Hello, I found another problem with my Teltonika ATC700 tracker (previous reports: stops sending after queued commands, setparam response lost). With Saving/sending mode “After Time Sync” (107:2), movement does not wake the device from Online Sleep, so GNSS stays off and the position freezes for days.
Setup
Device: ATC700 (Hw:ATC700 Mod:21), FW 3.20.0-rc.1+7.exp.autonomous, modem FW EG915UEUABR03A01M08_01.215.01.215
Configuration: Asset movement mode Movement (12150:1), Online Sleep (102:3), records every 30 s when moving and 300 s when stopped, Send period 0, 107:2 (“After Time Sync”).
Problem
After the device falls asleep, movement is detected, the device switches to OnMove and saves a record every 30 s, but it sends only the last retained position (io69 = 0, GNSS Fix: 0) even when the device is outside with good visibility of the sky. GNSS is never powered on. The only GNSS wake-ups come from GPSD_PWU_CTRL: once per hour for 60 s, cancelled after 3 failures (e.g. indoors). If the device falls asleep without a fix (PWU no fix before activation), there are none at all. The position stays frozen until a reboot, which helps only if GNSS gets a fix before the device sleeps again.
With 107:0 (After Position Fix) and otherwise the same configuration, movement wakes the device (Reason: GNSS Fix) and GNSS turns on as expected.
Steps to reproduce
- Set
107:2, get a GNSS fix and leave the device indoors until it goes to sleep and the PWU attempts fail. - Walk outside.
- The records arrive every 30 s, but GNSS stays off and the position does not change.
With 107:2 this happened every time between 16 and 20 Oct (4 occurrences, one of them a whole-day trip). With 107:0 GNSS turned on at every movement (7 times in 2 days).
Logs (from the Dump)
With 107:2, falling asleep with a fix and PWU giving up:
[M:SLEEP_MNG]: All sleep conditions met and TMO reached. Going to sleep...
[M:GPSD_PWU_CTRL]: PWU schedule wait due to fix
[M:GPSD_PWU_CTRL]: PWU scheduled timer for 3600s (state 1)
[M:GPSD_PWU_CTRL]: PWU sleep period elapsed, turn on GNSS
[M:GPSD_PWU_CTRL]: PWU wait fix failure - 1/3
...
[M:GPSD_PWU_CTRL]: PWU wait fix failure - 3/3
[M:GPSD_PWU_CTRL]: PWU cancel (1)
Then walking outside, 107:2 (no wake-up, no GNSS power transition):
[M:SCENARIOS_STATIC__ASSET_MOVEMENT]: Switching to OnMove state
[M:SCENARIOS_STATIC__ASSET_MOVEMENT_MODE_MOVEMENT]: GNSS source is Retained, switching to Main for OnMove state
[M:GPSD]: GNSS source changed to -> 1
[M:RECGEN]: Record Saved! ID:853
GNSS Fix: 0
[M:SLEEP_MNG__SEND_IN_SLEEP]: Send in sleep requested
The same situation with 107:0:
[M:SCENARIOS_STATIC__ASSET_MOVEMENT]: Switching to OnMove state
[M:RECGEN]: Wake-up needed for GNSS fix
[M:SLEEP_MNG]: Wakeup triggered. Current Mode: Online Sleep, Reason: GNSS Fix
[M:SLEEP_MNG]: Woke up from Sleep Mode:
[M:GPSD]: GNSS power transition 0 -> 1
Dumps from both configurations are available. I can send them privately.
Expected
In OnMove state the device should wake up and turn on GNSS regardless of the Saving/sending mode. With 107:2 the mode should only allow saving records without a fix, not stop GNSS from being used.