Hi,
I have a small robot that uses two brushless 190kv outrunners as direct drive motors. I also have AS5047D encoders connected. After some changes I made, I ran motor detection and the first Flipsky 4.20/motor did not have a problem. Then I tried detection on the second VESC/motor and it went through R and I detection, the motor spun up and suddenly it stopped with a loud vibrating noise. The noise stopped after a few seconds. Vesc tool then showed "Flux linkage detection failed". I checked the motor cable connections, changed the cables around, used anti-corrosion spray and connected the VESC to the other motor. Same result.... I took one of my spare FlipSky VESCs and connected it, same result.... I then reconnected the first VESCs with the first motor, ran detection and it showed the same error and vibrating noise. All VESCs run firmware with hardware SPI activated. VESC tool is version 2.06. I will now connect the VESCs to one of my other robots, which uses hoverboard hub motors and hall sensors, to see what happens there.
Any help would be greatly appreciated!
This error seems to come up when you make changes to the setup. In my case it was changing from a 12S1P to a 8S2P battery. Just press the read default motor configuration and then write motor configuration and the exact same for the app. All found on the far left hand side of the Vesc PC tool. This basically wipes absolutely all of your old settings. Now you're ready for a fresh start with Auto Detection in the Setup Motors FOC tab.
Hi every body!
Have anyone fix this problem?
I have the same error message
Thansk for ur comments!
Usually this is because of Battery Cutout voltage set above the voltage being used. Lower battery Cutoff voltage start, and end inside the VOLTAGE tab in motor