Wizard, 1 minute, job done.
Someone summon me? How can I help you ?
7 Likes
Hi Frank, just curious about foc, got improvements for 4.12 with the new vesc-tool? Aside of the bootloader trough usb. Thanks
And is there a date for this release??
Beside FW 3.26 support, wizards, bootloader upload, different throttle curves, well improved FOC, VESC-Tool interface with tons of explanations and a comprehensive documentation, there is nothing new for HW 4.xx.
Betas can download it on Friday. After a short BETA phase Benjamin wants to release it. Reference HW designs will follow as soon as finished and tested.
Frank
1 Like
FML. I’ve been following this thread and I was on the fence with which is better. I do like having the ability to change settings through one USB with can bus, but also dread the day a belt breaks and have no power on either motor (right?). Do have dual 15mm so it’s not to much of a concern. So today I was connecting my focboxes and connected my master through antispark xt90. My slave was disconnected from the power so I connected (not thinking) it how I usually have it in parallel. Guess what both my focers are fried. All because can bus I’m told. So that’s $100 down the drain if they can be repaired and $250 if they can’t. 
Just going to drive with a remote in each hand and turn like a tank from now on 
#TwoWheels
4 Likes
By that logic, a single drive board should constantly be turning in one direction 
1 Like
Oh man…That sucks
1 Like
Scratch that last part. What if I made it 2wd tho? TwoWheels
You mean dual remotes? A bit ridiculous, imo, but I guess the redundancy is extra safe!
RIP your Foc boxes 
Very sorry to hear your VescX’s are fried. Sounds like there are more ways that canbus can fry a vesc than we realized. That does it, I am never gonna get on the canbus
P.S. You don’t need 2 remotes. Just 2 receivers both paired to the same remote. Now thats redundancy
I did have my receiver shut off on me, leaving me brake-less. In that case dual remote would help, but still ridiculous.
why did your receiver go out
No, the receiver acted like it wasn’t bound. Restart of the board fixed it, but it happens sporadically so I changed it to the nano v2 remote.
So that happened with the Nano v1
Nope benchwheel controller. It only happens on my Carbonated build though, never once happened on my Honey Driver build. No idea what causes it.
isn’t the benchwheel remote a bluetooth system?
Nope standard 2.4ghz radio
Foreal that fkn sux, I’m sorry.
I got a spare vesc 4 if u wanna get up and going quckly. Barely used, friend prices.
3 Likes
In the VESC app config you can set the time for it to go idle if it doesn’t get a signal from the receiver, can also give it a braking amperage I’m pretty sure though I don’t set that value myself since I’d rather coast for a second in case the connection reestablishes instead of being ground to a halt and possibly tossed. Don’t have any dual motor setup so can’ t speak to the CANbus issues with it spinning out when one disconnects or whatever the case may be but it does seem if the 5V regulators are too far off from each other or the voltage supplied to them is too far off for some reason then they could be interpreting the same signal differently and like he says the mcu components they a no like the reverse polarity.
I ought to replace the cable between the ESC and receiver just for the sake of making it look nice, but as is I haven’t had a problem I just used a the regular JST connections and hot glued them into the 3D printed plastic parts wrapping the VESC and receiver box. Hot glue isn’t usually great but it does stick to the plastic really well and since it can ooze into the containers a bit that helps.