-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove gps_attempt_time and use broadcast interval instead #3064
Conversation
I believe that this change will not finally fix the issue but move the problem to another variable. |
If position_broadcast_secs is 0, wouldn't the problem be moot? That's the basis for sending positions in the module in the first place. |
Tried your code change in my master branch. I see two different behavior now when
IMHO, the code needs some sanity check for all configuration values the are coming from user inputs or via OTA transfer. Keep in mind that a Protobuf value defaults to zero (0). While this is a valid number, it is not a valid value for certain configuration parameters. So sanity checks should fix any configuration parameter into its valid range on configuration load and change. |
I just committed a change that aligns it with the coalesce to the default interval like we have in Position (and other modules). That seems like a sensible choice. |
|
Take another look at the implementation of getConfiguredOrDefaultMs. We use it specifically because it converts our seconds based intervals to milliseconds |
The code change works. Detects GPS module and gets position lock on
Position broadcast interval is set to zero in app during testing. |
This pull request has been mentioned on Meshtastic. There might be relevant details there: https://meshtastic.discourse.group/t/no-gps-module-t-echo/8824/5 |
No description provided.