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?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.
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.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?
Are you using stick arming, or switch arming? If stick arming, you may need to calibrate the radio throws in mission planner.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.![]()
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.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.
Radio calibration in the ground control/configuration software.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.
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.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.
Tried to flash INAV but INAV didn't recognize it. Gonna use INAV on the Speedy Bee.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.