VESC-Tool 2.0 and Firmware 4.0 - The beginning of a new era - (SERIOUS)

That is also one of the goals I want a dyno, teste between sensorless, hall sensors, encoder and now HFI

Before I say anything, this is just an edge case, VESC and VESC derivatives is still the best we have, and is really few scenarios that this is an issue

That the VESC has lower torque at really low speeds is a fact that anyone can test. Find the steepest hill that you can climb at speed, it has to be on the edge of what your board is capable, or lower the motor current until it’s just enough for you to climb it at speed

Now try to climb at walking pace or slower, it won’t be capable, while in theory it should since torque is directly proportional to current, and the current your are applying is the same

Or it’s due the hall sensors due to it’s nature not being capable of reporting exact position and so the maximum torque isn’t being produced, if that is the case a encoder will solve, or is something deeper

@Deodand and @Gamer43 am I right in saying that the new HFI offer better angular estimation than hall sensors? And if that’s the case should low speed performance be better with it?

Genuinely asking, I haven’t had time to update anything to 4.0

Amazing work guys, hope to see this trend continue on the future

Also since you are here, @Deodand what do you have to say about the temperature measurement using motor resistance? Is it feasible now the the whole project is more mature? It would be in line with your thinking of less wires = more reliable

4 Likes