KDE ESC and xxxHawk (Arducopter) will not work properly, period.

For details, see http://multirotorforums.com/threads/kde-direct-xf-uas-esc-and-flight-controller-compatibility-list.20587/page-3

Following KDE's instructions, the other day I thought it was fixed, but spoke too soon.

The copter arms, but the motors will not spin correctly. One motor will slow down and stop after a number of seconds. Giving it more throttle, the motor spins up again, but repeats slowing down/stopping. It's not always the same motor. I have tried various parameter settings for THR_MIN, MOT_SPIN_ARMED

Right now the settings to keep all motors spinning are:
THR_MIN 0
MOT_SPIN_ARMED 130
THR_MID 500

I know MOT_SPIN_ARMED is supposed to be below THR_MIN, but I've tried that and every other combination I could think of.

After arming with above settings, all 4 motors spin up at min throttle and stay running for 15 seconds, then turn off and disarm. This is normal.

However, while moving the throttle up, at about 1/2 throttle, maybe a bit more, the motors go to what sounds like max throttle. Not good.

Would you guys using KDE ESC's with a Taranis tx and Pixhawk detail how you got everything to work properly? Did you need to change settings for the KDE ESC firmware?

Thanks.

It's a shame because the throttle response on these KDE's are amazing, but something is really wrong. I don't believe the ESC's are bad (tested each individually), and definitely not the motors. The ESC's have the latest firmware with default settings per KDE manual.

I am just about ready to take these KDE ESC's out and replace with HobbyWing Quattro which work perfectly on another quad with the same KDE 515 motors, although are not as responsive as the KDE's.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hey DG,

    So I have a similar setup to you. 

    KDE motors

    KDE ESCs

    Pixhawk.

    5v bec plugged into main out 8 on Pixhawk

    I also has similar issues as you and followed your little thought process/guide at the link you provided above.  Didn't quite work out for me, *BUT* I seem to have solved the issue for me. Mind you, this is bench only at the moment so who knows if problems will present themselves once airborne.  I'll detail my steps:

    Fresh install of copter 3.3 and reset all parameters to their default.  (I notice that RC_MINx & RC_MAXx all seem to be 1100-1900 by default now)

    Do mandatory setup for frame type, compass and accel calibration.

    *Radio Calibration* is where I had success.  I noticed that if I set my throttle min max in my Taranis transmitter to 1100-1900, the radio calibration screen in Mission Planner/APM Planner would show a different value. 989-2015 let's say.

    I navigated to page 7/12 'SERVOS' of the Taranis and adjusted the min-max for the throttle while looking at the radio calibration screen of Mission Planner.

    On the Taranis my throttle min is -79.6% for a value of 1132us

    my throttle max is 77.2% for a value of 1932us

    and my ppm center is 1539 delta.

    On the radio calibration page of Mission planner though, throttle min is exactly 1100, throttle max is exactly 1900, and the midpoint is exactly 1520.

    When I power up, the motors make that familiar beep every half second.  When the arm button is pressed, beeps double in speed before a confirmation tone.  Throttle down right then sees the motors spin up.

    I had no need to change any of THR_MIN, MOT_SPIN_ARMED, or THR_MID.

    This has worked flawlessly every single time since I've done it so for me, at the moment anyway, this seems to be the key to get the KDE stuff and the Pixhawk to play nice.


    Hopefully this helps someone out!

  • Wow, did I jump the gun on this. Someone replied to me in the above link and said they had the same odd behavior at startup, but once in the air was fine. So I decided to try it, and it flew very well except for some wobble, but I suspect that is a PID as there was no detectable sync issues. Vibration levels were fantastic.

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @chr1sa: The next @DIYRobocars virtual AI race is tomorrow morn at 9:00am PT. You can watch live on Twitch https://www.meetup.com/DIYRobocars/events/275268196/
1 hour ago
DIY Robocars via Twitter
New version of Intel OpenBot! This resolves many of the issues with the first version, including a much smoother tr… https://twitter.com/i/web/status/1352395636369313798
20 hours ago
DIY Drones via Twitter
Using ArduRover with an RTK GPS https://ift.tt/2N9I3RO
Tuesday
DIY Drones via Twitter
Monday
DIY Robocars via Twitter
Monday
DIY Robocars via Twitter
Jan 15
DIY Robocars via Twitter
Jan 15
DIY Drones via Twitter
Jan 14
DIY Robocars via Twitter
RT @Heavy02011: @diyrobocars : A Home-brew computer club* for Connected Autonomous Driving on Jan 23rd, 2021 https://www.meetup.com/Connected-Autonomous-Driving/events/275728684/ #Meetu…
Jan 14
DIY Robocars via Twitter
Jan 14
David Hori liked Isabella Domi's profile
Jan 12
DIY Robocars via Twitter
RT @Heavy02011: ⁦@diyrobocars⁩ Autonomous Driving Assembly at #rC3. join us at https://rc3.world/rc3/assembly/diyrobocars-f1tenth/ ⁦@f1tenth⁩ ⁦@DAVGtech⁩ ⁦@DWalmroth⁩…
Jan 11
DIY Robocars via Twitter
RT @chr1sa: New car designs coming for our next @DIYRobocars @donkey_car virtual race on the 23rd. Choose any one you want at race time Le…
Jan 11
DIY Robocars via Twitter
RT @RoboticMasters: Thanks to @EllerbachMaxime and the Sydney Uni Capstone Students the @donkey_car @diyrobocars simulator is getting a ma…
Jan 11
DIY Robocars via Twitter
Jan 6
DIY Robocars via Twitter
Dec 28, 2020
More…