FT Bronco VTOL

tomlogan1

Elite member
Note from Heewing today that they are going to replace the flight controller without me having to ship the defective one back which will save me perhaps weeks because of the inefficiency of USPS. Hoping the second unit performs with no issues.
 

LitterBug

Techno Nut
Moderator
Note from Heewing today that they are going to replace the flight controller without me having to ship the defective one back which will save me perhaps weeks because of the inefficiency of USPS. Hoping the second unit performs with no issues.
There are things that can be done to possibly revive the "bad" one. Has it ever connected to MissionPlanner, or always been a dud? Do you hear the windows device detected sound when plugging in the USB port?
 

tomlogan1

Elite member
There are things that can be done to possibly revive the "bad" one. Has it ever connected to MissionPlanner, or always been a dud? Do you hear the windows device detected sound when plugging in the USB port?
Initially, it connected to Mission Planner, showed a GPS image of my neighborhood and spun the props. Now Windows does not recognize it nor does the USB connection emit any sound. I have used 4 computers (3 Windows 11 and 1 Ubuntu) and have the same results, so I believe the controller itself or the instance of Ardupilot somehow got corrupted. I followed an number of Youtube videos on how to unbrick a flight controller but since these is no "button" on this controller none of those remedies helped. If you have an idea on other avenues to take I would welcome the guidance, but since neither Windows or Linux could not connect I have no idea on how to proceed.
 

LitterBug

Techno Nut
Moderator
There may be boot pads on the main board that could be shorted together at power up to enter DFU mode. Usually there is a way to do that even if they did not include a button. Would have to remove the case from the board to find them.
 

tomlogan1

Elite member
The first version of the board does not come a correct Ardupilot bootloader (it may at some future point) so it cannot be upgraded with new versions of Ardupilot firmware. ANd cecause it has not boot pin exposed, DFU loading is not possible.

Instead a “transitional” firmware can be used and loaded like normal ArduPilot firmware (this is rev 4.3.7 Plane firmware) as a custom firmware file in Mission Planner.

This firmware contains the correct bootloader and it can be installed using the Mission Planner: SETUP->Install firmware “Bootloader Update” button after this firmware is loaded. From then on you can load any ArduPilot future firmware versions you desire, normally.
 

tomlogan1

Elite member
Heewing came through! Need to update a few parameters but the game is back on!
 

Attachments

  • Heewing.jpg
    Heewing.jpg
    626.8 KB · Views: 0

tomlogan1

Elite member
So as we muddle along, the mighty & mighty expensive TX-16s refuses to play nice with Ardupilot... will not arm or disarm. The lowly Flysky FS-16X handles Ardupilot with aplomb. A $50 snare off eBay to be the "backup" has now (for this project) become the master.

Go figure.:oops:
 

LitterBug

Techno Nut
Moderator
So as we muddle along, the mighty & mighty expensive TX-16s refuses to play nice with Ardupilot... will not arm or disarm. The lowly Flysky FS-16X handles Ardupilot with aplomb. A $50 snare off eBay to be the "backup" has now (for this project) become the master.

Go figure.:oops:
Are you using stick arming, or switch arming? If stick arming, you may need to calibrate the radio throws in mission planner.

I always use switch arming with Ardupilot. Last thing I want is to accidentally disarm because I am doing something crazy with my sticks.
 

tomlogan1

Elite member
Are you using stick arming, or switch arming? If stick arming, you may need to calibrate the radio throws in mission planner.

I always use switch arming with Ardupilot. Last thing I want is to accidentally disarm because I am doing something crazy with my sticks.
I am still getting things to move in the right direction. I will most likely arm via a switch but I had to start over after the first one failed. I still can't figure out what caused the old one to fail. It still "sorta" works, just can't get to it from Mission Planner. I do have to again credit Heewing. I might have somehow caused the problem with the old one but they stuck with me and after testing a lot replaced it. Gotta love that level of support.
 

tomlogan1

Elite member
Switch arming enabled and stick arming disabled. 30 seconds on the FlySky transmitter. Final hurdle is why the flight controller on its own moves back and forth between QLOITER, FBWA and QRTL. Incrementally issues are being resolved.
 

LitterBug

Techno Nut
Moderator
Switch arming enabled and stick arming disabled. 30 seconds on the FlySky transmitter. Final hurdle is why the flight controller on its own moves back and forth between QLOITER, FBWA and QRTL. Incrementally issues are being resolved.
Radio calibration in the ground control/configuration software.

Are you using a three position or five position switch?
 

tomlogan1

Elite member
Using a three position for now. Still on the bench. Radio has been calibrated. I have modes setup as QLOITER, FBWA & QRTL. The tilt servo moves as expected between these three modes but once I arm and start the motor (only using one on the bench) after a few seconds with no stick intervention, we will switch modes back and forth until we hit QRTL and the system is disarmed. Hunting this issue down.
 

tomlogan1

Elite member
Just treading water on the VTOL build. Still trying to figure out why the FC will switch between modes when the motor starts. Other than that it seems pretty solid. Ardupilot is (for me) pretty humbling. You fix one issue and another replaces it. Still going to tame the beast unless I get my other FC done and move this over to INAV. Seems to be a lot more (local) resources with INAV experience than those with Ardupilot.
Off my soap box.
 

tomlogan1

Elite member
As the project begins to mature I'm thinking of (not an original thought) using the Mellenium Flerkin as air frame and have ordered an updated power system. 3d printed the motor mounts just this morning.
 

Attachments

  • IMG_20260217_132802_1CS.jpg
    8.4 MB · Views: 0

FlyerInStyle

Master member
I made a boomin flerken VTOL, but have since disassembled it. there are two things to keep in mind. Put a really strong carbon spar in the wing before assembly. the Flerken center section likes to fold on itself, the reason why I disassembled mine and will be building a dedicated VTOL. Secondly, choose some low KV motors, but move the motor mounts further outward, with larger props. the small 5" Flerken props did not serve well for battery life with the aircraft blocking about half of the area. It worked. not terribly well. I was happy with it, but will try a dedicated VTOL and see what I can do. Otherwise, its a straight forward and easy project, and I did not even really have to tune. the auto tune in INAV did its job. It also is unstable lower than 2 ft to the ground, so get it above that and it will hover fine.
 

tomlogan1

Elite member
Thinking of throwing in the towel on the Heewing FC. Probably more accurate to say tossing Mission Planner. My Speedy Bee is ready for pickup so I will most likely do that. Heewing was GREAT on support but with the settings provided for their FC Mission Planner stumbles. As an example, when you move between modes with the motors off, the mechanisms pivot smoothly. When you ARM the motors, the modes move back and forth with no stick input. I've reflashed the FC per HEEWING instructions and the same issues arise. Can't get all 3 modes on my TX16S but I can on my ancient Flysky FS-IX 10 channel transmitter. The project creeps along.
 

FlyerInStyle

Master member
Thinking of throwing in the towel on the Heewing FC. Probably more accurate to say tossing Mission Planner. My Speedy Bee is ready for pickup so I will most likely do that. Heewing was GREAT on support but with the settings provided for their FC Mission Planner stumbles. As an example, when you move between modes with the motors off, the mechanisms pivot smoothly. When you ARM the motors, the modes move back and forth with no stick input. I've reflashed the FC per HEEWING instructions and the same issues arise. Can't get all 3 modes on my TX16S but I can on my ancient Flysky FS-IX 10 channel transmitter. The project creeps along.
See if you can flash INAV on it. I have found setup for VTOL to be much simpler in it, and unless you need the autonomous features, I am not sure there is a point for ardupilot's complexity.