Damn I really have some fine tuning to do it rides like shit
Gotta figure what I need to tune
The brakes freak out a little coming to a stop
Which I’m assuming is just HFI behavior
But gonna really give it a test ride in a minute here
1 Like
Okay I lowered my negative ramping time as that fixed my throttle sticking problem.
It initially was at .50 I dropped it to .08
But idk if that caused my brakes to be super weak… or if it’s something else.
My motor braking current is -160A rn per motor so idk what’s up…
Throttle expo on brake was 0% I upped it to 25% I’m thinking about going to like 45% before I put it back together tho
It’s also currently set to polynomial what do you guys use exponential?
Edit
(here I go I set to exponential at 65%)
Okay well I’m like really not a fan of the dv6 pro
it just dumped me on a launch for no reason & pretty hard.
I’ve had this happen on the metroboard aswell which is running the same Vesc.
It’s gotta be a setting of some sort idk why they have both dumped me.
3 Likes
Thinking of raising my positive ramping time to .15 to strain it a little less? It’s currently at .10 on each side.
I believe the moderately low ramping time is causing the board to hit absolute max current (ABS) early & cutting out?
also maybe trying the “natural” braking expo or returning to polynomial my brakes are still absolute shit even after (exponential @ 65% )
What are your battery amp settings?
There’s your braking problem.
1 Like
My battery cannot handle more than 14a of regen / charging @glyphiks
But maybe you are right?
I know for a fact my brakes were extremely strong before
Is it okay to have the regen current value higher than speced because it’s a burst value?
1 Like
That’s charge current and could be limited by the bms, or the rating of the cells themselves.
But regen is a different beast. Type regen into the search bar here and do some reading, but general consensus is just to set your regen at whatever feels good and safe for your brakes and fuck the consequences.
Pro tip: there are no consequences.
5 Likes
Gotcha that would make a lot more sense these are like comically bad brakes I’m like borderline oh any day now in terms of stopping.
They must have been set much higher prior to this. I’m trying to reference old Vesc screenshots to see if it was. But I’m probably just gonna start at like 70a
Thank you
1 Like
70a per side will be crazy, i’d start at 35
3 Likes
It was atleast -40.00a as I found a screenshot from 2023 but I definitely think it was maybe 60-70 at one point.
As per the cut out problem I’m wondering if I should raise absolute max current value above 200a which that’s where it’s sitting right now.
when I ran my unity at had it at 400 per side and I never had a cutout.
but I believe trying to go above 200a in Vesc tool whilst using a dv6 pro and it wouldn’t let me?
we will see gonna open it back up for the 7th time lol
I didn’t loose enough blood on the first go around let’s do it again
Yeah i’m pretty sure those preset values are already maxed according to your hardware and vesc tool doesn’t let you go higher.. but my memory is pretty rusty at this point.
1 Like
in your eyes is raising positive ramp time to .15 still to low?
or is .2 more like it?
I ask this in reference to what I’m thinking it causing the cutout is hitting max Abs current limit by the board not being up to the speed I’m asking it to be it draws a ton a current trying to get to the speed asked of it?
I don’t think your ramp time has anything to do with the faults you are seeing.
The ramp time is the time between the signal being received by the esc and sending amps to the motor.
Increasing or decreasing this time isn’t going to have any bearing on the faults.
If you’re hitting abs max, that’s usually do to bad motor parameters (set during motor detection). Good threads around here on the forum and videos from Benjamin Vedder on YouTube about that. TLDR play around with the manual detection settings to best suit the motor
That charge current rating is for continuous. You’re never going to be continuously max braking, so your braking battery -current can be set way higher. The max value will be whatever you can dump into the cells…practically speaking this will cause a rise in battery voltage and overvoltage fault. However, with a 10p battery, you’re nowhere near that being a problem.
Ditto what @glyphiks said, better to have overpowered brakes and increase battery wear then underpowered ones.
Debugging vesc issues is a lot easier with a logging device like a Minnie/megan.
6 Likes
alright so I had a race against time this Morning as my laptop was at 8%
I returned the mapping expo % back to zero and changed to exponential.
moving to motor config
I changed Battery Current Max Regen to -40
On both sides
And decided to do something illegal
Bump the absolute max current to 300
But for some reason it only worked on on side
The non local side stayed at 250 as the highest value it could go up to.
fine
I’ll illegally only go 50 amps higher on both sides for a total of 500 absolute max current.
