Skip to content
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

Don't send me to null island, please #1576

Merged
merged 4 commits into from
Jul 30, 2022
Merged

Conversation

thebentern
Copy link
Contributor

@garthvh I think this should fix the null island brigade

@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2022

🤖 Pull request artifacts

file commit
pr1576-firmware-1.3.27.4ee0a05.zip 4ee0a05

thebentern added a commit to meshtastic/artifacts that referenced this pull request Jul 29, 2022
thebentern added a commit to meshtastic/artifacts that referenced this pull request Jul 30, 2022
Copy link
Member

@caveman99 caveman99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like a good catch - however there are similar checks all over the GPS code. Our 'Null Island' on T-Echo was not always 0.00/0.00 but 0.something/0.something


sendOurPosition(NODENUM_BROADCAST, requestReplies);
}
} else {
DEBUG_MSG("Channel utilization is >50 percent. Skipping this opportunity to send.\n");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completely unrelated to the PR, why does it say 50% down here when it's 40% up there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol, that's a nice misleading typo

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 40%

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo fix made it into the merge :-)

@thebentern
Copy link
Contributor Author

looks like a good catch - however there are similar checks all over the GPS code. Our 'Null Island' on T-Echo was not always 0.00/0.00 but 0.something/0.something

Garth was reporting zeros on non-smart broadcast position packets, but I think that was for mostly for non T-Echo devices. I'm gonna add this guard for now just to be consistent, since we have the same on smart broadcast.
Do you have some example values for what to look for in the T-Echos? Is it close enough to do some fuzzy truncation logic? I can do a follow up ticket to address it.

@thebentern thebentern merged commit fd27a81 into master Jul 30, 2022
@thebentern thebentern deleted the fix-empty-position-packets branch July 30, 2022 12:36
@caveman99
Copy link
Member

I haven't seen the specific T-Echo problems since i swapped out the math in TinyGPS. Fingers crossed. Just adding the note to keep your eyes peeled if this is happening again.

@geeksville
Copy link
Member

This pull request has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/meshtastic-1-3-29-public-preview/6241/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants