It seems like first detection stuck the motor for some reason, so it won't be able to detect from the first place!
U first need to set up the app, PPM for me. write default motor setting than run the motor a bit.
Than come back to motor detection! It works in both BLDC and FOC now,
Phew~
Update, FOC is detected but not working, for bizar reason it shorts the motor and making tiny sound. does not respond to ppm... well BLDC for a while I guess
Update2: A side from initial setup bug, I noticed there is bug with ppm setting. for FOC it short the motor when connected to Receiver, regardless the remote on or off. It's like a failsafe mod. I couldn't figure out what the cause. But it clearly works well on BLDC. Note: I plugged our receiver to prevent interference during FOC set up.
Notice that I use mac ver,(not official) FOCBOX, sk3 260kv 10s5a, with unloaded motor.
I tested with both 2.18 and Akman's 2.54, both works fine.
And to go back to old fmw, u upload from vesc tool and use old tool.
Which hw version did you choose? I think it should be 4.12.
Have the same Issue with 4.12 Hardware and sensorless motors.
Since update from 3.27 to 3.28 FOC locks the motor. Maybe the root cause is also PPM because i tested FOC with 3.27 only with the keyboard. Also searching for the root cause in the software but could not find it yet.
When the Stator Saturation Compensation is set to 1% the motor starts to move. But that was not necessary with 3.27.
Maybe the PPM receiver is causing some interfearance. Could be a wrong PIN Mapping then.
Also in the motor wizzard resistance doesn't get updated. Only works from the FOC tab but not in the wizzard. It seems that the resistance doesn't get measured at all from the wizard because the motor clicking at start is missing.
I did choose 4.12 altho it showed up as 4.10. hear it's almost identical.
I agree with akman's idea, what ever the cause FOC interfere with PPM. the motor locks up if connected to receiver.
FYI I use the ebay mini RC remote :http://www.ebay.ca/itm/2-4GHz-Radio-Remote-Control-Receiver-Transmitter-...
for initial set up the clicking sound of measurement is not present as akman stated,
I did try both with wizard, and foc tap.
hope it helps!
Can we update to the new version of VESC Tool or is it preferable to wait for a corrected version?!
Have a Nice Day.
Thierry
@benjamin
focbox foc update.
I had time to use new 0.81 tool.
disconnect receiver, write bldc config, go to FOC config, flying pass.
soon as i plug receiver, (I didnt even select current brake option) motor high pitched, shorted.
no response from throttle.
try with motor saturation, but does nothing.
What did I learned: bug seems to do with sending packets from receiver to the vesc. In vesc tool when I try to control with keyboard, it acts to same.
Just test it with a normal 6355 motor which has a low resistance if you have one available. Because it works better with high resistance motors.
And just switch to BLDC, write motor settings and then back to FOC.
@benjamin
If it says vesc X and not focbox on the front. You dont have the Newest.
The problem definitely came with the changes from 3.26 to 3.27. Just tested with 3.26 and FOC has no issues at the FOCBOX. 3.27 has already all the describes problems.
Sadly the sources files for 3.26 are not available.
Just tested FOC detection on 3,29 with sensored 70kv hub motors. Same problem R = 0 bug..... And the motors locks.