I’m right with you on that one! The number of parameters that you can configure is overwhelming 
I know that once you run the motor and the input wizard, a lot of parameters get set up automatically but there are still some stuff to set up manually like battery current etc. So yeah, if anyone with good knowledge of the VESC 75/300 would be willing to share all essentials parameters to set up, that would be great! In the meantime, I’ll further explore it and share my findings here!
Yes that’s true. It would be a great help. I also use the combination of FR Motor and Vesc 75/300.
Alexandre has a good idea of the Vesc and also the combination VESC-FR.
@alexandre: It would be great if you could post some screenshots or other hints here. That would make life easier for us laymen … 
Thanks for your help
I recommend using FOC (so there is no timing). It is more quite and more efficient. Disadvantage is higher peak currents (since you use a sine wave you need a higher peak current for the same RMS current) and slightly lower max RPM.
How did you do the motor detection? I guess the reason is a non proper carried out motor detection.
E.g. weak test cables or weak connectors destroy the model of the motor when the FOC motor detection runs (e.g. the resistance of the motor is measured, if you use only probing wires and crocodile clamps the resistance will be far off).
BLDC algorithm is much simpler, so much more forgiving (thus I guess it was a user error 
) so that might be the reason why FOC didnt work and BLDC worked.
Then you got 2 options:
-
VESC-Tool App: simple logging, CSV file on your phone, easy to analyse by the VESC-Tool on the PC.
Disadvantage: (IMHO) not so nice design and so far no automatic reconnect. So you got to place your phone inside the board (otherwise you got to reconnect manually after every “crash”). -
Metr App: user friendly, nice design, Web based analyse tool including calendar based logging history, automatic reconnect, watch support, video overlay support etc.
Disadvantage: you need a external BT dongle from the Metr.at shop for around 50€
Well, the VESC75/300 is not very different from all other VESCs software wise. It does have higher hardware limits and no DRV chip.
So here some basic tipps:
-
I recommend doing the configuration on a PC/MAC and not by the phone (although it is possible to do it by phone as well). After writing the configuration, also save it on your PC as XML, so you can always reopen it and check the parameters (e.g. after updating the firmware and losing all your settings).
-
There is a “?” at every parameter you can change. Press it and there will be information displayed about what this parameter does.
-
Also at the VESC-Project are numerous tutorials about how to set up the VESC.
-
After going through the wizards you will only need to adjust the Motor current max and the Battery current max.
-
All other parameters should be set to get you flying. Still there might be some parameters you might want to change (e.g. failsafe or temp limits).
I don’t want to go through every parameter since you can easily do that by yourself (if you are interested; it is really time consuming since there are many).
So if you really bother about the other parameters and you got questions, just ask them.
2 Likes
Thx for writing this up.
I don’t know why my 65150 motor failed the motor detection to use FOC. But, you are right about that happening. I tried several times. Kept failing. I will double check connectors and try again. I just figured the 65150 motor doesn’t work with FOC. Are you saying you have this motor working with the FOC control?
I dont have this motor, so cant say anything about that.
Which part of the detection keep failing? What did the motor do? Do you get any (other) errors?
Maybe screenshot the error/fail message.
Did the resistance and inductance test work?
If not, either your motor might be bad, or anything in your setup.
If the flux linkage failed and your motor didnt spin you can try a small steps up in detection current (current in FOC->Detect and Calculate Parameters). This will help to get the motor spinning, but don’t go to high, since when the motor doesnt spin this current will be used to heat it up…
1 Like
This is the biggest challenge of the VESC: Sometimes it is darn hard to get the detection to work. I’ve built around 30, and some of my boards detect easily, some have trouble, and some are wrong. A big help for me is that I use the same motor for testing, so I know what the numbers are supposed to be, and I have a lot of experience. Sometimes a resistor is soldered wrong or something and I can see there is a problem because the detection comes out different.
If I just got my first VESC, and a new motor, it would be really frustrating if it couldnt detect. And if it was my first time, I wouldnt know that 30mOhm or 10mOhm was correct or not for my motor. I wouldnt know what changing the current and duty cycle and speed settings and all that, or what correct flux linkage was.
Perhaps motor vendors should list appropriate detect values for a few vesc variants for their motors? Or someone could host a cloud database for different motors and we all together provide data for it so new customers arent in such an atomized state. or something…
I got it to work.
Not sure what I did different.
Need to shape a board. Not much time for this project this month. I’ll b back at it next month.
Has anybody used this extension of the VESC Tool called Ackmaniac ESC Tool on 65150 motors ? This tool can do plenty of things but for the FOC matter seems to be handy to tune both Hall sensored and sensorless motors in FOC mode ?
For PC: How to: Ackmaniac ESC Tool
For Android version see @Giga’s post https://efoil.builders/t/vesc-6-4-cables/1761/4?u=soefoil
This tool is a massive APP on the electric-skateboard.builders site but nearly unknown on the efoil side. This post by Nico ACKerman, the designer:
Never heard of it. I’ll read up.
unfortunately not anymore…
Since the VESC-Tool is out there is an app with capability of tuning all parameters. Also there are more and more bugs found for in the (not longer developed) ACKMANIAC-Tool. The one with most impact is that the old FW revisions don’t measure the motor resistance correctly. There was a bug in the motor detection.