You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have multiple RAK nodes with RTC's.
When the device is set with a fixed position (over bluetooth) the correct time is maintained on all future position packets that are sent. After rebooting (remotely) to update settings, the RTC still has a valid time but all future fixed position packets have their time set to zero.
Valid time properly found after fresh boot from RTC
DEBUG | ??:??:?? 1 Saved TZ: PST8PDT,M3.2.0,M11.1.0
DEBUG | ??:??:?? 1 Set Timezone to PST8PDT,M3.2.0,M11.1.0
DEBUG | ??:??:?? 1 Read RTC time from RV3028 getTime as 2024-11-05 22:07:46 (1730844466)
DEBUG | 14:07:46 1 NeighborInfoModule is disabled
DEBUG | 14:07:46 1 Rescanning for I2C keyboard
Time is then stripped off the position packet when it is requested from another node.
DEBUG | 14:08:48 63 [PositionModule] Setting local position: lat=49 lon=-123 time=0 timestamp=0
DEBUG | 14:08:48 63 [PositionModule] Sending location with precision 32
INFO | 14:09:16 92 [Router] Stripping time 0 from position send
INFO | 14:09:16 92 [Router] Position reply: time=0 lat=49 lon=-123
DEBUG | 14:09:16 92 [Router] Partially randomized packet id 1561338937
INFO | 14:09:16 92 [Router] Asked module 'position' to send a response
Screenshot from a little earlier in the day showing the issue in the android position log.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Done. I'll try to dig an RTC module out. I think I have one of the WisBlock ones. If not, I'll order one and try to work with one of the external modules
Done. I'll try to dig an RTC module out. I think I have one of the WisBlock ones. If not, I'll order one and try to work with one of the external modules
Category
Other
Hardware
Not Applicable
Firmware Version
2.5.9
Description
I have multiple RAK nodes with RTC's.
When the device is set with a fixed position (over bluetooth) the correct time is maintained on all future position packets that are sent. After rebooting (remotely) to update settings, the RTC still has a valid time but all future fixed position packets have their time set to zero.
Valid time properly found after fresh boot from RTC
DEBUG | ??:??:?? 1 Saved TZ: PST8PDT,M3.2.0,M11.1.0
DEBUG | ??:??:?? 1 Set Timezone to PST8PDT,M3.2.0,M11.1.0
DEBUG | ??:??:?? 1 Read RTC time from RV3028 getTime as 2024-11-05 22:07:46 (1730844466)
DEBUG | 14:07:46 1 NeighborInfoModule is disabled
DEBUG | 14:07:46 1 Rescanning for I2C keyboard
Time is then stripped off the position packet when it is requested from another node.
DEBUG | 14:08:48 63 [PositionModule] Setting local position: lat=49 lon=-123 time=0 timestamp=0
DEBUG | 14:08:48 63 [PositionModule] Sending location with precision 32
INFO | 14:09:16 92 [Router] Stripping time 0 from position send
INFO | 14:09:16 92 [Router] Position reply: time=0 lat=49 lon=-123
DEBUG | 14:09:16 92 [Router] Partially randomized packet id 1561338937
INFO | 14:09:16 92 [Router] Asked module 'position' to send a response
Screenshot from a little earlier in the day showing the issue in the android position log.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: