Aquaharmonics
commented
9 months ago Just saw this note and thought I would post this to prevent others from making the same mistake. I just destroyed a brand new 100/250 by writing custom firmware in version 6.02 and uploading the firmware to the drive. I have been using 100/250s for mostly everything I am doing with custom firmware. I checked for all current hardware compile versions and only saw the 100_250 so thought it was the most up to date.... aaaaand I was wrong. I only had the drive connected to battery power with no motor at the time, and saw the errors come up on boot and knew something was wrong. I turned it off, and tried re-connecting but it wouldn't connect to VESC tool. I tried to use the SWD port and ST Link V2 to fix it, but it won't even detect the STM32 anymore. The blue LED comes on with power up, however. I would use the 75/300 mkiii instead, but they do not have an IMU AFAIK. Anyways, hopefully someone reads this before making a similar mistake.
Both bldc and vesc tool official version are 6.02 (March 12th) : https://github.com/vedderb/bldc/commit/f7c2b34e1cff2234cae98be3abf0cd50e249558f
But support for 100_250_mkiii has been added later (June 8th) : https://github.com/vedderb/bldc/commits/master/hwconf/trampa/100_250_MKIII
An official 100_250_mkiii.bin is available from Vesc tool firmware archive, but doesn't match any branch from github repo.
That makes it impossible to build a custom version for 100_250_mkiii working with official vesc tool version since the serializer for motor configuration has been modified in-between.