So for something different I bought a CUAV Pixhack (the real one) for this current H4 Alien 680 build. To head off criticism, it is not a cheap Pixhawk clone. It is high quality hardware in a machined aluminum case with IMU dampening and no connectors on the top. It's quite nice. Whether the latest version will result in good vibration levels without foam remains to be seen.
Next I bought the tried and true KDE 2814XF-515 motors and decided to go with KDE 35A ESC's. After going through all the instructions, warnings, updating firmware etc., I was happy to see it arm properly. However, the joy turned to frustration when one of the motors puttered off. With a bit more throttle, the motor turned on, then a few seconds later stalls out. Rinse and repeat.
First thought: power wiring to the FC wrong, as that has been a bone of contention with KDE ESC's. However, the PM is connected along with a 5v UBEC on the power rail. It should work right?
As the affected motor was #3, I swapped with #4 and yep, now #4 does it. Bad ESC? I'm not convinced yet.
Next I tried a genuine Pixhawk. Same thing. Sigh.
I'm tempted to buy a replacement ESC but have heard others having problems with getting their KDE ESC to play nice with a Pixhawk, yet others have no issues.
My question for you KDE guys, how did you wire the power to the FC? Here is KDE's diagram for 3DR products: http://www.kdedirect.com/blogs/news/18220995-xf-uas-esc-and-flight-controller-compatibility-list
Also, how did you set up your radio (Taranis) and any settings in MP?
Thanks.
BTW, I did not buy these ESC's from KDE; bought them from classifieds at RCG. The guy swore they were never fired. The wiring looked untouched, but you never know.
Replies