Also make sure to apply your changes so they are saved.
1 Like
oh yes fuck i keep forgetting about this flipsky crap 
2 Likes
did that now, still nothing. this is very frustrating
Try PPM then
1 Like
well i rewired and swiched connector and ports i can now control it with the controller but only one wheel, is it supposed to be like that when connected to the computer
Do you have 2 separate vescs?
Connect the can bus wires if you didn’t before.
I don’t remember how to set it up again, just rerun the wizard now that you wired it correctly
i have a single double vesc ( makerx DV4)
When you run motor detection, both motors spin up?
1 Like
had to run it 2 times then it worked
1 Like
Great!
Those 4.10 vescs can act a bit weird sometimes.
Make sure to do some bench tests before going out
thank you for wanting to waste your time on helping me 
got it to work guys thanks for the help, one last question. why have two different methods of connecting the remote, ppm and uart what is the benefits and or negatives?
2 Likes
Uart can send more data, allowing more functions.
Ppm “is dumb”
2 Likes
@xsynatic knows, no throttle mapping is possible through uart and ppm is more reliable imo. Both good, just different protocols, ppm is one way.
1 Like
its fine, that’s what we do here
3 Likes
This is not time wasted, people helped us before, and hopefully you help others later
3 Likes
What do you mean exactly? You mean calibrating end points?
And glad to see OP got it figured out haha
Just for others that might be searching, and for closure, what exactly “did it”
2 Likes
I thought so?
Yeah not like on PPM where you have to write the values, it just “knows” or however that works
In UART, the calibration is done on the remote side. On PWM, it’s done on the ESC side.
“PPM” on VESC is just mislabeled PWM.
1 Like