So I just completed my dual motor build and I took it out for a test ride around my neighborhood. As I was going down one of the hills the brakes started and after about two seconds they went out completely. Thankfully I was able to jump off before I fell but the board hit a curb and flipped over a couple times, but it was pretty dang scary. I’d really like to figure out why this happened and fix it before I move to San Francisco where I’d prefer not to die going down the hills. These are the settings I was able to grab from the BLDC tool:
While I was putting the board together I noticed that both of the motors didn’t brake at the same speed, I would go full throttle and then full brake but one of the motors came to a complete stop much before the other. I’ve checked multiple times to make sure that both VESCs are configured with the same settings and everything seems to match up, I just assumed that it was because one of the motors was reused from a previous build and one of them was brand new, both 6355 torqueboards motors. I’m using a 10S4P battery.
I’m running BLDC. I tried to run on FOC hybrid but every time I connect my sensor wires to either of my VESCs it disconnects from the BLDC tool and I can’t get it to reconnect without unplugging the sensor wires.
Sounds like your sensor wires are hooked up wrong. You didn’t apply your motor detection values, after detection you have to hit “apply” AND “write config”. If you want a reliable system stick with just BLDC.
maybe it’s decided by how high you set the regen then the voltage maybe follows. so if you set a low regen maybe the spike wouldn’t be as high. a total guess. other guess being it’s determined by your rpm when you brake.
Thought already about a automatic regulation of the voltage when it goes too high at braking.
But finally it doesn’t make sense to have that.
Because normally your system should not reach this high voltages. It only touches them when something is wrong. For example when the BMS cuts off because the charge voltage us too high during braking. But in this case there is nothing the vesc can do about it.
The value should not be editable. Only makes sense to change it when you vesc components can’t handle 60V.
Hey @oct0f1sh thought I’d chime in cause I’m having the same problem. I personally have a Carvon Single Hub running 6S and am using a GT2B remote in a BadWolf housing. Pretty much with my GT2B I had to adjust my minimum and maximum pulsewidth to make it so my center throttle would actually be center. But what that means is that when I push my trigger all the way up to fully brake, it goes under 1ms pulsewidth down to 0.8 which the VESC takes as having no input and just stops braking as if the controller lost signal. I’m not sure how I’m gonna fix this yet but maybe your having the same issue.
I had same issue with my GT2B in a babybuffalo case. Ackmaniac’s firmware was the only proper way to fix it. Or you can add a physical bump stop to prevent the trigger being pushed all the way in. I think the adjustable end points is one of the greatest things about his firmware. Really should be a standard feature. If your in this situation going down a hill you can move the brake back to the mid area and the breaking will come back.
