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

Update common-marvelmind.rst #6475

Merged
merged 1 commit into from
Dec 20, 2024
Merged

Update common-marvelmind.rst #6475

merged 1 commit into from
Dec 20, 2024

Conversation

smoker771
Copy link
Contributor

We propose these changes, because previous version of the article is not actual, the recommendations were obsolete and don't work correctly with last versions of the Ardupilot and Marvelmind software. The proposed version includes link to tested sets of settings which we will continue update in future for new versions of software

We propose these changes, because previous version of the article is not actual, the recommendations were obsolete and don't work correctly with last versions of the Ardupilot and Marvelmind software. The proposed version includes link to tested sets of settings which we will continue update in future for new versions of software
@Hwurzburg Hwurzburg requested a review from rmackay9 December 19, 2024 23:10
@rmackay9
Copy link
Contributor

This is a very different setup and means that the marvelmind acts like a GPS which is OK but removes the ability to do GPS-to-NonGPS transitions.

I thought @amilcarlucas knew the most about the marvelmind but I see that @peterbarker actually wrote the driver here

@smoker771 do you work at Marvelmind?

@smoker771
Copy link
Contributor Author

Yes, I'm working in Marvelmind.
We really appreciate this article. This article was valid some time ago, but now it is not valid for some reasons. Many Ardupilot users try to use it without success, ask us to help and we recommend switching to NMEA mode. Reason of changes to the article was to help Ardupilot users integrate with Marvelmind system successfully.
Thank you

- Set :ref:`SERIAL1_BAUD <SERIAL1_BAUD>` to 115 to set telemetry1's baud rate to 115200 (if using Telem2 set :ref:`SERIAL2_BAUD <SERIAL2_BAUD>` instead)
- Set :ref:`SERIAL1_PROTOCOL <SERIAL1_PROTOCOL>` to 13 to enable receiving data from the marvelmind (If using Telem2 set :ref:`SERIAL2_PROTOCOL <SERIAL2_PROTOCOL>` instead)
- Set :ref:`BRD_SER1_RTSCTS <BRD_SER1_RTSCTS>` to 0 to ensure telem1 does not use flow control (If using Telem2 set :ref:`BRD_SER2_RTSCTS <BRD_SER2_RTSCTS>` instead, not required if using Serial4/5)
- Here is a package with tested param files for the Autopilot and Marvelmind hedge: <https://marvelmind.com/pics/marvelmind_ardupilot_settings.zip>
Copy link
Contributor

Choose a reason for hiding this comment

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

I've approved but this line looks a little odd. I think there should be some single quotes around it.

I also think that we probably need to set the GPS1_TYPE = 5 (NMEA)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for approving.
We included all settings into the "param" files available by the link and "GPS_TYPE = 5" is also set there.
I will make an additional pull request to fix this odd line and some small changes in the design.

@Hwurzburg Hwurzburg merged commit fe48f57 into ArduPilot:master Dec 20, 2024
5 checks passed
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.

3 participants