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

Matek h743 mini #18730

Merged
merged 137 commits into from
May 6, 2022
Merged

Matek h743 mini #18730

merged 137 commits into from
May 6, 2022

Conversation

taileron
Copy link
Contributor

support for Matek H743 Mini (with AP bootloader)

In principle, the Matek h743 slim target could also be expanded, as it can also manage 10 pwm outputs. If it were possible to operate/flash different board IDs with the same code.

Describe problem solved by this pull request
I have been looking for a 20x20 target without many restrictions for a very long time. And it looks like everything including 10 pwm outputs will work.

taileron added 30 commits June 28, 2021 16:56
Mamba F405 Mk2 is very close to Omnibus F4
I only want to share it with the community
There is a great nano version that is fully flight tested incl. voltage/ current sensor
folder names changed
correct names
corrected names
corrected names
corrected names
doesn´t flash anymore
test mro ctrl zero classic
timer pwm out 10
compiling error
remove tim15
tim15 ch1 on PE5 is the right combination for pwm out 10 but NuttX does not want timer 15
update names
remove MRO from Diatone Branch
@dagar
Copy link
Member

dagar commented May 5, 2022

Do you still want this one?

@taileron
Copy link
Contributor Author

taileron commented May 5, 2022

Do you still want this one?

the final goal is to bring mini, slim, and wing with all emu variants into one code base.

At the moment there are still different objectives.
As an example, I see mini vtols here.
finally the target folder should be renamed to Matek-H743 (without slim or mini) as an unified target folder
with all needed modules for fw , vtol and copters

but the source should be the current slim in master. After that a I would delete this branch. #19562 #19443

@matthewoots
Copy link
Contributor

I can help to contribute too, I've got a 'H743-Wing V2' with me, if @dagar change the target to a H743 instead of slim, then I think we can start helping to support the variants

I've got some changes to add with some external sensors I have (for the fixed wing side of things)

@dagar
Copy link
Member

dagar commented May 6, 2022

I don't have a good understanding of the minor differences yet, so whatever works.

At this point I'd be fine if we want to do completely separate boards for each and then come back later to either refactor into a single unified target or create new mechanisms to share subsets of the board support.

Is there any mechanism we can use to detect if it's a slim vs wing vs mini?

@@ -69,4 +69,9 @@ param set-default VT_TYPE 1

set MIXER vtol_convergence

set PWM_OUT 1234
if ! ver hwcmp MATEK_H743
Copy link
Member

Choose a reason for hiding this comment

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

I don't like board specifics slipping into airframes like this, but we can live with it short term as it can all go away with control allocation soon. #19596

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is the only approach at the moment to deal with the io timer change between pwm 1,2 and 3,4 of these boards. Even for a simple multicopter small changes in the defaults would be necessary.

@dagar dagar merged commit fc887a2 into PX4:master May 6, 2022
@taileron taileron deleted the Matek-H743-Mini branch May 6, 2022 14:11
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.

4 participants