Pilotix H743 Firmware

Hardware UnSupported hardware
1

Hey, perhaps someone can help me with the following connection issue? I bought a Pilotix (H743) flight controller, assuming it was compatible with ArduPilot firmware—which turned out to be a mistake. Unfortunately, there was no support from the manufacturer, and I spent ages experimenting across Linux, Windows, and Cube Programmer to find a firmware target that would at least allow it to boot (Aocoda-RC H743Dual). However, it consistently refuses to connect to Mission Planner, even though tools like ArduPilot Bootloader DFU Loader are able to connect to it. I believe I’ve ruled out the usual driver issues. Could someone perhaps help me narrow down the problem based on the following connection log?

Timeout waiting for autoscan/no mavlink device connected

bei MissionPlanner.MainV2.<>c__DisplayClass124_1.b__6(IProgressReporterDialogue sender) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\MainV2.cs:Zeile 1495.
bei MissionPlanner.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Controls\ProgressReporterDialogue.cs:Zeile 111.

Thanks

2

To what end if the Flight Controller is not supported? What is Mission Planner going to do for you?

Did you try this firmware? Aocoda-H743

And what about these Pilotix FC’s? A couple of them look like clones of Matek boards.

3

Hi Dave, thanks for your reply. I’m not sure if I understand your question correctly — are you suggesting abandoning the project? That’s not an option for me yet. After all, the non-functional Ardupilot firmware is being distributed by Pilotix sales (hobbydrone cz). From the outside, the board they sell looks like a 100% copy of the Aocoda board, though I only realized that recently.They market it as being manufactured in the EU, which is highly questionable in my view. I wanted to configure the settings using MP. Right now, the board doesn’t have any working firmware at all; even Betaflight isn’t working. Yes, the firmware you mentioned is exactly the one I currently have installed.

4

That’s not the right path to take to get a new Flight Controller ported:
Porting

Pilotix has their own website, perhaps you can suggest to them that they follow the process?

The manual says this:
Firmware: In the configurator, look for the target PILOTIX_H743 or MATEKH743.

1 Like
5

Dave, I have 100% the same opinion :slight_smile:

I wasn´t thinking about getting it “ported”, as this is job of pilotix people, but trying to get this one controller running somehow even if this is only 90% for the moment. Its current status is e-waste.

So still a little help would be desired.

6

No joy with Matek H743?

7

I ´ve flashed Matek H743 target again, booting seems ok but still no connection to any AP GCS (failed Mavlink communication). This is the last error log:

Die Sequenz enthält keine Elemente.
bei System.Linq.Enumerable.Aggregate[TSource](IEnumerable1 source, Func3 func)
bei MissionPlanner.MAVLinkInterface.OpenBg(IProgressReporterDialogue PRsender, Boolean getparams) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\ArduPilot\Mavlink\MAVLinkInterface.cs:Zeile 960.
bei MissionPlanner.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o) in C:\Users\mich1\Desktop\CubePilot\MissionPlanner\ExtLibs\Controls\ProgressReporterDialogue.cs:Zeile 111.

8

@Marc_R Someone has to produce the firmware for this board. That’s it’s, nothing else to consider. If they are not willing to contribute you simply have an unsupported board. Stating “Ardupilot ready” or some such bullshit is meaningless.