You are here

Firmware 5.02

15 posts / 0 new
Last post
benjamin
Offline
Last seen: 6 days 21 hours ago
Joined: 2016-12-26 15:20
Posts: 378
Firmware 5.02

This is the beta testing thread for firmware 5.02, which will mainly contain bugfixes and small improvements. It would be nice to have some help testing it out. Here is a link to the new VESC Tool with the new included firmwares for all platforms:

http://home.vedder.se/tmp2/vesc_tool_test_2020-07-21.zip

So far, 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

 

ducktaperules
Offline
Last seen: 5 days 18 hours ago
VESC Free
Joined: 2017-12-11 12:48
Posts: 3

"VESC Tool does not allow uploading firmware to all VESCs on the CAN-bus if they have different hardware versions."

Just wondering is this a new feature . . . or a bug that has been fixed?

 

skitzor
Offline
Last seen: 2 months 3 weeks ago
VESC Free
Joined: 2018-01-30 14:20
Posts: 1

Updated my Raptor 2 to see if this Firmware fixes some issues.



My flipsky vx 2 remote is not reporting speeds anymore unless i put it on FSESC mode on the remote (Use to be Focbox mode to make it work with unity). -->UART changes ?

The motor temperature sensors are giving weird values. (I'm sure the hardware is fine as it worked on firmware 23.46) both displaying minus 89-90*C

I left the temperature sensors settings as is. (NTC 10k @25*C) 3380 beta



 

Andrewfpv
Offline
Last seen: 2 months 2 weeks ago
VESC Free
Joined: 2018-09-25 04:50
Posts: 2

Hello I have an 4x4 unity setup and I had just tried 5.02 yesterday and for some reason one of the two esc's will not pick up the hall sensor on one of my motor but if I flash 23.46 back to it just that one ESC it detected the hall sensors in that motor just fine don't know if this is a problem in the firmware but I figured I do the right thing and bring it to your attention also the original unity firmware when uploading new firmware to it it would automatically turn the unity off but In 5.02 The esc stay on I have to turn it off myself also experienced  after doing a software update and power cycling the ESC I couldn't connect to the VESC tool again unless I closed the program and reopened it I'm using the windows build ( when I was going back and forth with firmware I had the can-bus connector disconnected since the working yes he had no issue didn't see the point of me flushing and messing with that ESC) 

 

Andrewfpv
Offline
Last seen: 2 months 2 weeks ago
VESC Free
Joined: 2018-09-25 04:50
Posts: 2

Nvm found I have a bad hall sensor in one motor 

iulian207
Offline
Last seen: 1 month 1 week ago
VESC Free
Joined: 2018-08-27 14:44
Posts: 1

 

Hi Guys, I have the vesc 300 and i noticed that the RMS phase current is not calibrated properly and also not linear. For example up to 50-100Amps the values are closer to the RMS measured current, but when i go to 300Arms the current measured is only 200Arms. I have 2 questions here. how to calibrate this to show correct current. how to change the advance angle for sensor less commutation, since I think it can be improved form the encoder test i did. The Power factor of the motor can be improved if i add 30 degree advance angle. The power factor was 0.729. \

 

 

Power alalizer measurement

my website, www.masinaelectrica.com

I design my own motors. 

Iulian

vadicus
Offline
Last seen: 3 hours 10 min ago
VESC Free
Joined: 2018-08-17 07:26
Posts: 141

I noticed issues with the current measurements as well. I thought that was my custom hardware but seems like it can be in the firmware.

Here is one example: Running lower RPMs under load shows correct battery current, let's say 10A.

However, running full throttle with the the same load, shows batt amps about 25% less than actual draw from the battery. The meter shows 20A and VESC tool shows 14A. 

Filcas
Offline
Last seen: 1 week 6 days ago
VESC Free
Joined: 2019-06-03 21:16
Posts: 8

Hey guys!

I would like to thank you for all your hard work on this and I would like to give you also some feedback on recent builds.

Using FW 5.01 and 5.02 with 4.12 hardware, if you connect 2 or more VESC with CANbus, it has an erratic behavior that can be replicated every time:

If you have two motors connected to the same shaft (let's say, two skateboard wheels on the ground, so they don't have relative movement in between the two) if you accelerate the motors to the max speed, it becomes unstable and it starts dropping the speed to about 50-60% (and one motor appears with negative current - they are both spinning in the correct direction - and this only happens at duty cycle ove 85-90%). This took me a little bit to replicate because when tested on the table, having the motors free spinning (not locked together) it does not happen. But, as soon as you lock the motors together, this behavior appears. I tried the same with hardware 6 and there are no issues, but with the 4.12 it happens every time (regardless the motors or the setup, just locking any motor together it will happen)

When you guys have a little bit of time, maybe you can look into this so you make your firmware suitable for users with both 4 and 6 hardware.

Thanks again for your good work.

Cheers.

rpasichnyk
Offline
Last seen: 2 weeks 5 days ago
VESC Free
Joined: 2017-09-05 08:18
Posts: 3

I noticed similar erratic behavior @Filcas even without locking motors together on FOCBOX UNITY with FW 5.01. For me it only happened when using FOC without sensors. 

FOC + hall sensors = OK

FOC + HFI = OK

FOC sensorless = one motor locking + dropping speed

ducktaperules
Offline
Last seen: 5 days 18 hours ago
VESC Free
Joined: 2017-12-11 12:48
Posts: 3

hey,

Any chance to get an updated build that includes the current stuff from git?

Im keen to test some of the new IMU stuff that was added a few weeks ago.

benjamin
Offline
Last seen: 6 days 21 hours ago
Joined: 2016-12-26 15:20
Posts: 378

Updated now

rpasichnyk
Offline
Last seen: 2 weeks 5 days ago
VESC Free
Joined: 2017-09-05 08:18
Posts: 3

@Filcas several reports from https://forum.esk8.news confirm negative motor current for one of two motors in realtime data. I suspect this pull request was the reason https://github.com/vedderb/bldc/commit/dea04a5e229aab05b89c268a1b9e760eb8043f28

ducktaperules
Offline
Last seen: 5 days 18 hours ago
VESC Free
Joined: 2017-12-11 12:48
Posts: 3

Can confirm. Im also seeing this issue. Motor with direction inverted is reporting negative motor currents in both metr and Vesc Tool.

Im also seeing an issue where changing any setting from metr is messing something up in the VESC. The stormcore RGB light stops working and i cant make settings changes from the VESC tool. seems like doing a settings reset on the vesc fix's things.

benjamin
Offline
Last seen: 6 days 21 hours ago
Joined: 2016-12-26 15:20
Posts: 378

The current sign should be fixed now. Also merged the latest balance update.

linsus
Offline
Last seen: 1 week 2 days ago
VESC Free
Joined: 2017-10-25 09:21
Posts: 14

Tested the added support for MCU: STM32F30X

Setup:
individual 3.3V supply for the vesc and target(diebiems)
Ground shared via SWD interface. 
RST not connect as it yielded instant crash.

ended up with this: Skärmklipp3.PNG