The custom firmware is supposed to fix this. It’s on the product webpage.
4 Likes
not since the 5.2
on the 5.2 no limits from the page and have the same issue
2 Likes
Build has been great thus far but every single time I power up the remote and VESC I need to bind them… Is this common? Using the Ubox with the included remote. Not a deal breaker to have to bind but a bit of an annoyance.
Are you turning on the remote first before turning on the board? For some reason it’s really picky about ordering.
3 Likes
I agree. Remote must be fully booted then power up the esc shortly after.
4 Likes
Yup. Took me a bit to figure this out.
1 Like
Easy solution — never turn off the board.
7 Likes
Please measure the voltage by multimetor, I did test and check the 5.2 custom firmware, no such big tolerance. please let me know the result by multimeter. thanks!
5 Likes
Oops please delete
2 Likes
will try the custom firmware
currently on stock
What, he warned everyone over 9000 times to only use the custom firmware. 
5 Likes
What is it now, are you running the firmware the Ubox came with (custom) or stock VESC firmware?
2 Likes
the one shown above is what i am running. i dunno if its custom or stock
it calls it 75/300 firmware on the vesc tool app if thats any help
1 Like
k will check and try again
thanks
Use the one that says recommended
4 Likes
will do thanks
gonna change it later
Even I knew that and I’ve never bought one
@Halbj613 cmon lmao how are you going to use stock firmware and wonder why there are problems
1 Like