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

I think the problem is that vesc can’t measure current if it shorts the mosfets for full braking, and if it can’t measure stuff it’s easy to blow all of them if they pass their ratings

1 Like

Set your sensors or openloop to shut off at a lower erpm and you will face this issue at 1km/hr instead of 5. My motors seem to work fine with 2000erpm and i’ve done some testing down to 1100erpm for about 90% launch success rate (as in smooth start and no faults or screeching). Beyond that only mechanical brakes can help you

1 Like

Just so people know, (cause i didn’t) FW5.02 is now officially released and available for download from the VESC tool.

According to Vedder the changes are:

  • Bidirectional current mode for VESC Remotes.
  • Motor temperature measurement fix on unity and stormcore.
  • IMU calibration improvements.
  • VESC Tool does not allow uploading firmware to all VESCs on the CAN-bus if they have different hardware versions.
  • Added LSM6DS3 IMU support.
  • Added MTPA support. See See: https://github.com/vedderb/bldc/pull/179
  • App PPM rework. See https://github.com/vedderb/bldc/pull/192
  • SWDPROG (blackmagic probe) improvements
  • App Balance updates. See https://github.com/vedderb/bldc/pull/193
  • Motor current now based on magnitude of both axes.
  • Initial VESC BMS support.
  • Hall sensor interpolation improvement.
  • Made hall sensor filter configurable.
  • Added locking time and ramp up time parameters to sensorless startup.
  • Initial VESC IO-board support.
  • Added hall sensor interpolation ERPM config option.
  • Use fast speed estimator for RPM limit.
  • Avoid accumulated rounding error when using PID position angle division.
  • Added UAVCAN raw throttle drive mode (current or duty cycle control).
  • Added MT6816 encoder support. See https://github.com/vedderb/bldc/pull/238
  • Added modulation-based D axis current controller gain scaling. Addresses https://github.com/vedderb/bldc/pull/220
  • Added PAS app. See: https://github.com/vedderb/bldc/pull/243
  • Added 100k CAN-baudrate.
  • Added 100k NTC temperature sensor support.

Not listed but other changes of interest are:

  • large rework to the duty cycle soft limit that was causing street-face in previous builds.
  • Added support for Stormcore 60D+ (with fixed second uart)
  • Added support for Cheap FOCer 2
  • Added support for new NRF chips
  • Spelling fix’s by @b264 :wink:

If Anyone know of any changes missed then let me know and i will add them.

It may be official now but use with caution.

11 Likes

this.

2 Likes

Thank you for the update and rundown

4 Likes

Uh-oh another big update. Will I be finally able to use bluetooth connection with windows machine and OFFICIAL vesc-tool or do I still have to wait for someone to port it?

Sorry, I’m confused. Is this different than 5.1? Is this one the latest or is 5.1 the latest?

5.01 was the latest. This 5.02

But it lists it as 5.1 in Vesc tool, should that have been 5.01

think vesc tool removes the 0 :rofl:

4 Likes

Right then. That has always confused me haha

2 Likes

also, Vesc tool version number does not align with FW version number, just to keep things simple.

3 Likes

Yeah I know, the latest version I have right now is 2.06 and that installs fw 5.01

Can anyone expand on this?

Are you aware of the Duty Cycle Limit Start default issue that everyone was upset and concerned about with 5.01?

Default was 95% and needed to be reduced on some builds to as low as 85% to prevent the hard cut at 95% Duty Cycle.

1 Like

Yeah I’d like to know what was done, just set up my friend’s board on 5.01, don’t expect those speeds yet, but what was the determining factor in it causing street face

Was it speed? This build only maxes at like 29

3 Likes

Yeah I’m aware of the current problem I’d like to know what was changed in the update, whether its still safe to reduce duty cycle current limit start to 85% when trying to avoid faceplanting at high duty cycle %.

@Shuttershock, pretty sure its proportional to speed. Builds below 30mph seem to be immune but it gets incredibly violent on even v5.01 with regular duty cycle current limit start at 95% and duty cycle limit at 95%. Always right below top speed and just begins oscillating power back and forth between motors generally not quite shaking you off but enough to wake you up.

2 Likes

Definitely frightening. I just never wanted to deal with it so my main build and older builds are all on FW 3.62 haha but I just put a DV6 into my friend’s build last night and left it on 5.01 so I didn’t have to update it

It’s a 12s LifePo4 build so it’s basically 10s liion voltage range. With a 14:36 ratio, the speed doesn’t come out super high.

2 Likes

I have a 12s LifePo4 build on a DV6 as well, funny coincidence. From my experience, troubles start around 58-62kmh when that speed is near 92-94% duty cycle and the shakes are seemingly random with their timing and I’m really glad to see duty cycle current limit near 85% solve the problem completely albeit sacrificing top speed :frowning: and I’m hoping this update eliminates the need for us to sacrifice speed for safety not in the usual way.

3 Likes

Holy crap what is your gearing lol

1 Like