HESC V1 150v 600Amp VESC based motor controller

Not too relevant in that video I guess, haven't even used Halls yet with this controller.
If you have Halls connected it should auto-detect them.
 
Depends on the motor, I am in the process of adding an encoder to a high voltage motor since it won't run well under load.
I do have a qs138 that I could test just sensorless, it would take a while though to set up though.
 
I would be using the halls for sure.
On one motor it took me lots of trial and error just to get the motor to spin.
With halls you are tracking of the rotor position so it'll tolerate incorrect parameters better.

I like sensorless (in theory) because if you lose halls during a drive you can change it to sensorless to get you home.
But you have to get it to work first, otherwise the motor will just be all over the place.
 
The app worked well, got it spinning after a few tries and it seems smooth. The PC software not so much, I'm not sure why it behaves differently when controlling it from the PC vs the app, I wonder if there may be a communication issue with the USB cable even though it's the one they sent me with the controller. I first tried setting up the motor with my laptop and had time out and disconnect issues, then when I finally got it the motor was really jerky and didn't sound good. Then I used the app and did it again, as I said it runs smooth on the app and now better with the laptop but not as smooth as the app. This is on the laptop:

 
.... I wonder if there may be a communication issue with the USB cable even though it's the one they sent me with the controller.

Mine had an issue with the USB connection disconnecting intermittently. I determined it was a bad connection on the controller's 3 pin connector for USB. Try enabling TCP bridge from the app and then connect from your PC using tcp (mobile app and pc have to be on the same subnet) instead of USB.
 
Last edited:
Mine had an issue with the USB connection disconnecting intermittently. I determined it was a bad connection on the controller's 3 pin connector for USB. Try enabling TCP bridge from the app and then connect from your PC using tcp (mobile app and pc have to be on the same subnet) instead of USB.
Do you mean a bad connection on the pcb in the controller? :oop:
JRP3, I havent seen the number anywhere. When I couldent connect I asked Hackey and got the number from him.
 
Seems as if that's an important data point they should include in documentation.
Yes, absolutely.
I think there is a lot that should be included in vesc documentation as well. If you find something it is 5years old, and 10 updates ago and not relevant any more.
 
Try enabling TCP bridge from the app and then connect from your PC using tcp (mobile app and pc have to be on the same subnet) instead of USB.
Does that entail something more than just being on the same wifi connection? I tried connecting as shown in this video and the laptop does not show the phone as a possible connection.

 
Back
Top