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
When setting "Device GPS Enabled" in the iOS app settings to FALSE, the firmware will attempt to probe for a GPS module on startup, eventually fail, and then decide to shut down power to the IO rail, causing ALL, not just the GPS device to become inactive. In my case, this is the active Ethernet module.
An observation (and my current workaround as I don't have or want a GPS module for my base station) is setting "Device GPS Enabled" to TRUE, which results in the same probing attempts (trying different baud rates before giving up), but the logic decides to not go into power saving.
I understand from speaking to devs on Discord that the power rail shutdown is a solution to conserving power by hard-cutting the power to the GPS module, but I think this is a bit of a short-sighted approach without first checking the presence of anything else requiring power.
It would seem like a reasonable solution to either check first that nothing else is using the power rail before switching off the power or somehow regulate the power usage of the GPS module directly (I heard some chatter that this may be already happening and that the rail cut-off might be more of a legacy thing that may need re-addressing).
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Category
Other
Hardware
Rak4631
Firmware Version
2.2.19.8f6a283
Description
When setting "Device GPS Enabled" in the iOS app settings to FALSE, the firmware will attempt to probe for a GPS module on startup, eventually fail, and then decide to shut down power to the IO rail, causing ALL, not just the GPS device to become inactive. In my case, this is the active Ethernet module.
An observation (and my current workaround as I don't have or want a GPS module for my base station) is setting "Device GPS Enabled" to TRUE, which results in the same probing attempts (trying different baud rates before giving up), but the logic decides to not go into power saving.
I understand from speaking to devs on Discord that the power rail shutdown is a solution to conserving power by hard-cutting the power to the GPS module, but I think this is a bit of a short-sighted approach without first checking the presence of anything else requiring power.
It would seem like a reasonable solution to either check first that nothing else is using the power rail before switching off the power or somehow regulate the power usage of the GPS module directly (I heard some chatter that this may be already happening and that the rail cut-off might be more of a legacy thing that may need re-addressing).
Relevant log output
No response
The text was updated successfully, but these errors were encountered: