Using: Kakute H7 v1.8 Fc loaded with Copter/stable/KakuteH7-bdshot/arducopter.apj stacked with their Tekko F4 Metal 4in1 65A ESC loaded with AM32_AT32DEV_F421_2.17.hex. Motors are EMAX ECOII 14 pole 1300 KV. In MP, BDMASK is on for channels 1-4. Bench testing and props off.
On arming, all motors spin briefly, about one second, then stop. In the messages pane, there appears a warning “Potential Thrust Loss (2)” sometimes (4) when throttle is advanced, but the motors don’t spin at all.
On motor test with throttle and duration set to 15, motor A spins the longest, from 1 to 4 seconds. The others spin for one second or less.
The solder connections motor-ESC are solid. Battery is a 4S 3000 mAh Lumenier, and I’ve also tried this with a bench power supply. I am at a loss as to what can be the problem here and hope someone can help. Perhaps someone can supply a working params file for this type setup for me to compare. Thanks for any help.
Thanks, I looked at that software but the templates don’t include one similar to my setup. I’m not having any problems with using MP to set parameters; these just don’t seem to work as they should.
I open motor test in a separate window and watch the messages on the data screen. I set motor test to run for 60 seconds and try each motor in turn. Each motor will turn for times ranging from one to twenty seconds then stop. But according to the messages pane, the test continues for the full 60 seconds. Battery voltage is 14.7 while the motor is running and current draw is .6 amps.
So motor test tells the FC to run the motors and it starts to do that then quits, though motor test continues to run. What can cause this behavior? Is there any parameter in Arducopter that could cause the FC to cutoff the motors even though the test continues to run? Could the motors (link) be simply wrong for the FC somehow?
Is there anyone who has a working Kakute H7/Tekko 65A quadcopter? if so, could you post your params for me to compare?
Here is a peace of code with your errors it’s quite well commented.
A point seems to be “descending” but it’s on the desk … So it could be your baro has problem.
Are you sure your copter passes all arming test or you disabled it ?
// the aircraft is descending with low requested roll and pitch, at full available throttle, with attitude control
// we may have lost thrust
thrust_loss_counter++;
// check if thrust loss for 1 second
if (thrust_loss_counter >= (THRUST_LOSS_CHECK_TRIGGER_SEC * scheduler.get_loop_rate_hz())) {
// reset counter
thrust_loss_counter = 0;
LOGGER_WRITE_ERROR(LogErrorSubsystem::THRUST_LOSS_CHECK, LogErrorCode::FAILSAFE_OCCURRED);
// send message to gcs
gcs().send_text(MAV_SEVERITY_EMERGENCY, "Potential Thrust Loss (%d)", (int)motors->get_lost_motor() + 1);
// enable thrust loss handling
motors->set_thrust_boost(true);
// the motors library disables this when it is no longer needed to achieve the commanded output
a 4s lipo is empty at 14,8v (4 * 3,7v) and fully charged at 16,8v (4 * 4.2v).
Please read some more information about how to treat your battery .
So most likely your esc has a low voltage cut off which should be disabled for multicopter purposes.
In the description is no prove at all that he followed the methodic configurator, so we can’t know if the settings for the low voltage warning are correct.
Thanks for the help. I replaced the battery with a fully charged one with the same effects. I decided to try a whole different firmware so loaded INAV 8.0 on the FC. Hardware (Barometer, calibrated Accel, etc.) all reported good, tested motors on the output tab and same problem, brief spin and stop.
So the issue is not in whatever firmware is loaded on FC. Could it be the ESC? Using am32 configurator, I checked that the firmware version is the one recommended by the manufacturer and settings are good. They are:
The am32 (DEV_F421) firmware is the one recommended by the manufacturer. The configurator warns me if I start to load any other that I might brick the ESC. I’ve tried both the latest version ,2.17, and the one originally on the ESC, 2.10.
I’d like to try “plain old PWM”. What is the configuration setting for that?
Default Arducopter. Mot_pwm_type to pwm and the servo parameters back to default. After connecting to MP check the banner message for output protocol for your motor output channels and confirm they are pwm.
I tried MOT_PWM_TYPE set to 0 (Normal), 1 (OneShot), 4 (DShot150), 5 (DShot300), and 6 (DShot600). Each gives much the same result; motors run for a second or a few seconds, sort of stuttering, then stop.
One more thing to try.
Set MOT_SPIN_ARM and MIN back to default and then when running motor test increase the throttle percentage incrementally until all motors run. Set the run time to 30s or so. If they run what is that %?
The only odd thing I can see in parameters is you dont have the battery monitor set up BATT_MONITOR
yet you have the MOT_BAT values in place.
If that doesnt help then it’s probably a hardware fault - the next step would be to try another ESC (any old ESC) or another FC with that ESC.
.