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

GarminHD Cannot change Range, Sea clutter. #121

Closed
SamHoulder opened this issue Sep 18, 2019 · 3 comments
Closed

GarminHD Cannot change Range, Sea clutter. #121

SamHoulder opened this issue Sep 18, 2019 · 3 comments

Comments

@SamHoulder
Copy link
Contributor

Report/Log
http://www.cruisersforum.com/forums/f134/radar-plugin-v5-0-0-released-216057-14.html#post2964910

Workaround/Fix for range:
Change range definitions.
http://www.cruisersforum.com/forums/f134/radar-plugin-v5-0-0-released-216057-16.html#post2977718

@Hakansv
Copy link
Collaborator

Hakansv commented Sep 28, 2019

@bdbcat
Dave..
Would you mind have a look at this observation of SamH? You're the G HD expertise here.
Thanks
Håkan

@SamHoulder
Copy link
Contributor Author

I gave this a little bit more thought and from what I figured out, the issue lays in that radar_pi use exact range_meter, where garminHD uses range_meter -1. That means "fixing" the garmin range definitions was a ugly hack, it was whats broke the nautical viewing in the control-window.

I have since reversed the rangedefinitions back to what it was, and instead adjusted the range_meter where it is beeing sent/received. That is range_meters -1 when changing/sending range, range_meter+1 when receiving the message. With that it works like a charm and displays correct.

For seaclutter there is something strange going on. In radar_pi it can show som-ething like Status calm 100% when Im changing it from my 3010 plotter. I havent been able to compare the actual packets yet, my onboard switch wasnt to happy with ettercap/arppoisening, Ill have to tap in to the network cable to catch packets. More results for that in a couple of weeks when Im back.

@keesverruijt
Copy link
Contributor

I'm closing this as we implemented the range fixes in PR #123

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

No branches or pull requests

3 participants