VESC-Tool 2.04: FW 5 >> A BIG STEP FORWARD

I got really bad motor oscillating/wobbling approaching 95% duty cycle current limit

Backing duty cycle current limit start off to 85% made the board feel weak.

I’ve bumped it up to 90% and it’s tolerable but I’m too askeered to try higher for now.

Bring it in guys :hugs:

5 Likes

Anyonehaving issues with the VESC tool not opening?

as of recently no version loads on windows 10 anymore … Played with my screens too hoping to resolve the white screen of death.

1 Like

I had this problem on a Win10 virtual machine and didn’t figure out why. Same executable works on other copies of Windows.

Man i wish i had other versions…

One day it just stopped working, finished my build and cant ride lol…

My Win10 VM did the exact same thing. One day it just stopped working. But only for the VESC executables, nothing else. I thought it was my VM, as it works everywhere else.

@Trampa not sure if you guys are aware but it seems like there are a few users having firmware timeout issues when trying to upgrade to FW5.2 using the current newest vesc tool.

I had this issue whilst trying to upgrade a stormcore 100D from one of the FW5.2 beta builds to the official FW5.2 over bluetooth from the current vesc tool android app. i tried multiple times with no success.

I know that @glyphiks and @skate420 have also experienced this. maybe you guys can also report on what hardware you are using to see if we can work out whats going on here.

1 Like

My set up was dual escapes on 5.1 with freesk8 robogotchi.

Using windows pc with vesc tool 3.0

Tried connecting robo via tcp bridge. It connected fine and read all values no problem, but would not write any values and firmware update just resulted in this after several tries

Next i tried vesc app on android 10 using robogotchi as bluetooth connection. Read and write of values worked perfectly, but firmware update resulted in the same thing.

Finally i managed to update to fw 5.2 by opening the enclosure and installing onto each vesc seperately, not over CAN.

Worth noting that even in vesc tool 3, it says available FW versions 5 and 5.1, but actually installs 5.2 even though there is no mention of it.

Edit: fully aware that robogotchi is still beta hardware and is possibly contributing to these issues, just reporting my findings.

3 Likes

Just upgraded from 3.57 to 5.2, works, I had one instance that I may have experience the wobbles but not sure, was full throttle and got over a bump that the tires skipped a little, so probably was that together with traction control doing it’s thing

Also, first time using smart reverse, to make it brake normally until a lower speed I should just lower the direction change ERPM? Right now it has strong brakes until almost zero but for a bit the brakes get weak as the duty cycle of smart reverse ramps up, does not feel good

Will try all that anyway, but easier to ask to test a bunch of combinations

I tried smart reverse on a mate’s board yesterday. I don’t like that if you are already gravity rolling in reverse and you try to reverse, that it still applies ‘brakes’ before it reverses.

4 Likes

That’s gotten me a few times as well

Current Hyst Reverse With Brake mode

If you’ve just powered into reverse, and you freeroll for a moment, then you press reverse again, sometimes it brakes if you’ve crossed l_min_erpm * -1 already, at least that’s what I think might be happening. I’d expect it to not brake again until I cross 0

1 Like

Same here I think, don’t remember exactly

@b264 only thing I don’t like about that is that as soon as the motor is slow that the braking current you command can’t be reached it switches to active braking, probably is insignificant the amount of energy it takes, but o like the feel of the brake getting weaker as it gets close to zero, but no as smart reverse that it suddenly gets weak

Latest version kinda broke smart reverse. Before it would brake then reverse, but start reversing if it can’t stop at a more sensible (speed 0.5km/hr?). Now if it’s anywhere near 2km/hr it starts the reversing sequence which is unexpected every time

I usually just use forwards throttle and that works fine

Sensors or bust.

You forward throttle to reverse? :woozy_face:

Oh I read your post wrong. I use forward throttle to go forwards again since if you’re rolling backwards and brake it doesn’t actually stop you.

I don’t mind it braking before reversing when I’m rolling backwards personally. Usually I’ll just let the board roll backwards and then use forwards throttle to slow myself down, no need to use reverse if you’re already rolling backwards

1 Like

There is if you wanna reverse faster/further!

2 Likes

Yeah that’s the other case haha but I suck at riding switch so that would not be great for me

1 Like

Anyone have hoyt puck disconnects with the 5.2 or specifically ppm disconnects

I discussed this issue before a while back.

AFAIK @Deodand agreed that the behaviour is odd and coded a fix. I believe there was a PR for the fix.

BV wasn’t happy with the behaviour change so it never got merged, but I think it was tested and working.

IMO forward should only give you forward acceleration and reverse should only ever give you backward acceleration.

I will see if I can hunt down the PR.

5 Likes

Software versioning is funny.

In between each period, it’s treated as its own number. 01 = 1

Don’t ask why; I don’t know.

It’s confusing. 5.10 is more than 5.2 and 5.05 is more than 5.2 and 5.2 is less than 5.03.