KDE Direct
KDE Direct, LLC.
Hey Guys,
Customers forwarded this thread to me, experiencing similar issues with startup-idle RPM on motors with the KDE Direct XF ESCs. Since we can directly control the RPM of the motor with the XF ESCs through a receiver direct with no issues, something was changing in the response of the flight-controller to effect the Motor Idle Speed with the DJI controllers.
We tested multiple systems, using the DJI Naza-M V2 and A2 controllers. Here's what we have found, and it appears ONLY with the A2 controller (latest firmware v2.3).
On the Naza-M V2 controller, Motor Idle Speed works great, and there is a noticeable change in startup RPM when shifting the setting from LOW to HIGH, and is working in all three flight modes: Manual, ATTI, and GPS. No problems throughout, working great with the KDE Direct XF ESCs. :tennis:
On the A2 controller, there is a major bug in the Motor Idle Speed programming. When changing the Motor Idle Speed setting from LOW to HIGH, the startup RPM works great in the Manual mode ONLY. High setting is extremely high and I DO NOT recommend using this, use LOW or RECOMMENDED only, to prevent premature take-off in Manual mode. When starting the motors in ATTI or GPS mode, there is NO CHANGE when adjusting the Motor Idle Speed and it seems locked at the "RECOMMENDED" RPM speed . This is a major issue of concern for customers, as this can lead to a faster-than-desired startup RPM for some setups (especially on very light and overpowered setups).
In this regard, when running the A2 controller until the firmware is fixed, I am instructing customers to take-off ONLY in Manual mode and make sure to set Motor Idle Speed to LOW. With the Naza-M V2, this problem does not exist, and any of the three flight modes work great as programmed.
This is not an issue with the KDE Direct XF ESCs (they are factory-programmed to Futaba 1100ms to 1900ms pulse-ranges as standard), but an issue with the A2 programming for the Motor Idle Speed. I hope DJI will acknowledge this and work to solve this ASAP for customers, as the A2 is a great flight-controller and this is an open issue of concern. If you have any questions, please feel free to e-mail me at support@kdedirect.com and also, if anyone wants to discuss this with me from DJI, please contact me as well.
Thanks,
Patrick Koegler
Owner, KDE Direct
Customers forwarded this thread to me, experiencing similar issues with startup-idle RPM on motors with the KDE Direct XF ESCs. Since we can directly control the RPM of the motor with the XF ESCs through a receiver direct with no issues, something was changing in the response of the flight-controller to effect the Motor Idle Speed with the DJI controllers.
We tested multiple systems, using the DJI Naza-M V2 and A2 controllers. Here's what we have found, and it appears ONLY with the A2 controller (latest firmware v2.3).
On the Naza-M V2 controller, Motor Idle Speed works great, and there is a noticeable change in startup RPM when shifting the setting from LOW to HIGH, and is working in all three flight modes: Manual, ATTI, and GPS. No problems throughout, working great with the KDE Direct XF ESCs. :tennis:
On the A2 controller, there is a major bug in the Motor Idle Speed programming. When changing the Motor Idle Speed setting from LOW to HIGH, the startup RPM works great in the Manual mode ONLY. High setting is extremely high and I DO NOT recommend using this, use LOW or RECOMMENDED only, to prevent premature take-off in Manual mode. When starting the motors in ATTI or GPS mode, there is NO CHANGE when adjusting the Motor Idle Speed and it seems locked at the "RECOMMENDED" RPM speed . This is a major issue of concern for customers, as this can lead to a faster-than-desired startup RPM for some setups (especially on very light and overpowered setups).
In this regard, when running the A2 controller until the firmware is fixed, I am instructing customers to take-off ONLY in Manual mode and make sure to set Motor Idle Speed to LOW. With the Naza-M V2, this problem does not exist, and any of the three flight modes work great as programmed.
This is not an issue with the KDE Direct XF ESCs (they are factory-programmed to Futaba 1100ms to 1900ms pulse-ranges as standard), but an issue with the A2 programming for the Motor Idle Speed. I hope DJI will acknowledge this and work to solve this ASAP for customers, as the A2 is a great flight-controller and this is an open issue of concern. If you have any questions, please feel free to e-mail me at support@kdedirect.com and also, if anyone wants to discuss this with me from DJI, please contact me as well.
Thanks,
Patrick Koegler
Owner, KDE Direct
Last edited by a moderator:
