PWM_type,DSHOT600 (tried DSHOT 300 and 150 as well without success)
SERVO_DSHOT_ESC,1
SERVO_BLH_POLES,12
It is a new build. One of the motors stutters during Motor Test and Arming. When I changed the stuttering motor with another motor, the new motor turns normally. Does this mean, as this post suggets, that the motor is faulty?
With 1s ESCs and batteries, that could have been just a motor that is a bit tough, and one may want to increase MOT_SPIN_ARM and MOT_SPIN_MIN to fix that.
But that’s 4s and based on other motors this is not a spin-arm issue. So, quite likely, either one of the three wires or one of the coils in the motor are severed. You can test the resistance between each pair of wires. If one is clearly disconnected, then it’s that wire, and you may try hunting down where the cut is. If not, and your ohm-meter is very sensitive, you may find out that for one pair the resistance is noticeably (like 2x) bigger than for others - then something is cut within the motor.
I tested the resistance for all 3 phases in the faulty motor. It was almost non existent at .006 to .007. This resistance is comparable to other motors that spin normally. I had an extra motor which again had comparable resistance that I am now using.
Any other suggestions before I chalk it up to a faulty motor? If so, is it worth reaching out to T-motor for replacement?
Hi @Allister , do you mean via AM32 web based configurator. Yes, I tried changing the KV form default of 2220 to 4600 and number of poles from 14 to 12. It did not help.
Worth a shot. May not have helped this problem, but it will fix or prevent others down the road.
If it’s only one motor causing problems, and the problem moves with the motor, it’s probably the motor.
edit: Just looking at your parameters, I noticed you have the loop rate at 800, might be quick but I can’t say for sure. But you do need to increase the SERVO_DSHOT_RATE. I often run it at 4 x loop, but since you’re at 800 you might get away with 2 or 3. AM32 want’s faster update rates and the 1KHz is absolute minimum. Probably won’t fix your motor issue though.
I moved ahead with competing the build. So did not get a chance to test this parameter. I will be building another one soon and will try it. Thanks kindly @kalai1219 !
Yes, I feel it may be just a faulty motor. PWM_Frequency is a parameter that I have not changed in the past, but it sounds like a great idea. I am trying to get the vibration level down (found that one of the connectors was touching the frame, so have raised the FC, need to test.). Once I have that down, I would like to change the PWM_Frequency level for testing.
Thanks for pointing out the SERVO_DSHOT_RATE parameter. I have raised it to 2.
