Hello all, I am using 850mm x 850mm frame with hobby wing Xrotor 60amps 4 in 1 ESC with t-motor 7005 230kv motor, 2480 inch foldable prop, MTOW 5.6kg. After mission plan I was testing obstacle avoidance while testing at 5m altitude suddenly motor(1) experienced potential thrust loss and crashed. Cross verified the hardware soldering and joints no loose connections found. Gone though the log observed saturation at motor 1
Firmware 4.5.6 and earlier used dshot 600 while doing bench test at 60% throttle one of the motor is getting jerk and overheating but when testing at below 50% working fine. Sometimes we are observing these. So later changed to dshot 300 we didn’t observed such thing. after few days when checked at 60% throttle observed the same thing motor getting overheat and getting jerk and not rotating enough later if we slowly increase the throttle percentage it vanished.
Earlier I was using normal instead of dshot and motors are connected to servos but I didnot face such issue until and unless voltage is too low but when i started using bidirectional dshot configuration facing problem with potential thurst loss and jerks at 60% throttle while doing bench test. I am stuck and unable to find the problem , if it is with esc or motor is not matching with esc. Below is my esc overview.
Motors rotate and wear. Just because it worked fine a year ago does not mean it is not damaged today. PWM, Dshot300 or dshot600 makes no difference if the motor is damaged.
So replace defective motors if they get too hot or show signs of damage, before they loose trust causing a crash.
The crash was not caused by the firmware detecting an error.
The loss of trust caused the crash and the firmware to detect the error.
So not it was not A that caused B, but B that caused A.
Motors are new just have flown for 10 flights. And moreover it is getting hot only sometimes in bench test at 60% throttle . But in outdoor we didn’t face any issues but today while testing lidar it experience a thrust loss. I don’t think motors are defective.
Using Mission Planner motor test page to test all motors under the same conditions and with the same thrust levels, at the same time causes motor 1 to get warmer than the others
Or do all motors get equally warm?
On the crash flight motor 1 saturated (a clear indication that it was not responding and was not providing enough thrust) and the FC detected a thrust lost and could not recover.
You tested motor 1 and it is working fine now
You assume that the lidar caused the firmware to saturate the output to motor 1 and that caused the FW to detect a thrust lost and the saturation caused the vehicle to crash.
It is not that every time it will get heat only one time we observed later I changed dshot600 to dshot300 I assume it solved the issue.
Then onwards I didn’t observe any issues but today at while doing bench test at 60% I observed the same. But later it vanished.
Not all the motors getting warm only the one.
Yes motor 1 caused the thrust loss.
After the crash i tested the motor but it is rotating good but hearing metal sound.
Firmware 4.5.6 and earlier used dshot 600 while doing bench test at 60% throttle one of the motor is getting jerk and overheating
Here you get first indication that something is wrong with the motor1
but when testing at below 50% working fine
and ignored it
Sometimes we are observing these.
So you get thies more than once
after few days when checked at 60% throttle observed the same thing motor getting overheat and getting jerk and not rotating
again you get a massive indication
Was all this before or after the flight?
Your log shows no increasing BATT current after commanding motor1 to maximum thrust but changing BATT current on changinging the thrustlevel of the others motors, why you think this happens?
Your log shows ERR-message THRUST_LOSS_CHECK-1 clearly before the crash, why you think the FC initiated this message?
So why you still think that motor1 was not the root cause?
Because when I tested with bench test it was motor 3 which got jerk not the motor 1. And after bench test have done tuning and multiple missions but when we were testing lidar it should be the motor 3 which should get thrust loss. Here case is different.
The log file shows quite clearly a loss of thrust on Motor1. The FC tries to counteract this but the motor does not respond properly and the crash occurs.
This has nothing to do with the lidar test itself and would probably have happened on any other flight.
If this has occurred before with other motors, there is generally something wrong with the drive system (ESC, motor, propeller).
You did not write which motors were conspicuous in the bench test. In order to provide good help, good and precise information from you is also necessary beforehand.
Definitely, I am going to do test bench again and will check which motor is experiencing jerk or defective. My question is, if there is any motor that made the motor 1 thrust loss or only the motor 1 is defective?
What caused the engine’s loss of thrust cannot be determined from the data provided. However, it is primarily due to the respective drive system consisting of ESC, engine and propeller including the mechanical suspension.
Servo_BLH_AUTO=1 I used for changing the use settings
Servo_BLH_MASK= 3840 for bidirectional dDSHOT
Servo_dshot_esc=0 I set dshot600
Psc_accz_p= 0.15 but the value is not taking instead 0.20
So Psc_accz_i= 0.30
Today I did changed this parameter and did bench test at 60% throttle from motor 1 smoke come out. Disconnected battery and tried again but this time another motor is experiencing a jerk. I don’t think this might be the reason.
I have followed ardupilot methodic configurator and tuned my drone but as my 4in1 esc doesn’t support ESc telemetry I have changed few parameters. Does 4in1 60amps esc supports 7005 230kv tmotor for a long run?
