Hi everyone,
I have a FSeESC 6.7 Pro with 12s3p batteries and FD motor. Occasionally, I am getting a stuttering motor when slowly initiating throttle…but sometimes also when I go 0-100% throttle.
Please see the link below.
I did everything what is shown in the video below. But on the handy app, which seems a bit limited…or I am looking at the wrong place.
Any ideas/explanation what the reason for this could be?
Thanks,
P
Other users will ‘throw rocks’ at me for this, but just use ChatGpt for another go at setting it up.
It will ask for image uploads, but it will let you do it once then time you out for 6 hours.
I programmed a 75200 twice from videos, having no idea, and they didn’t work until I went through and maxed out a few values. There was a post of people having problems, but not everyone.
With my latest build using a 75100 and a 6384, I let ChatGpt know the hardware details and asked what to do with the setup, then entered some values to ChatGpt after to check them.
I also saved the motor setup and uploaded it to ChatGpt to check it, but it will likely time you out after the answer.
I learnt a lot and it ran well.
I asked ChatGpt about your issue, as I do with all the problems here to get a better understanding of how things work, and if all the connections are good it is a configuration issue.
Lower inductance value in the motor config by 50% and try again, alternatively post the motor values tab here to have a closer look
With the newest VESC firmware I find the automatically measured values to all be too high by 30-50% for the motor to run nicely
Seems a lot better without load now. Will check shortly. Thanks heaps!
Now I only need to find out why my remote only sometimes shows battery stats etc instead of 0. But this is a big step forward.
If you mind asking. What are the impacts if this value isn’t set proper? Any hardware damages? Is this related to the start only or would this impact over the whole range?
Improved values will change efficiency by ~1% in my experience.
If you have severely wrong values maybe more… but that’s unlikely with the auto detection.
Hardware damage from this is unlikely, just bad startup/running behavior usually