All you would need is a stable FW since VESC tool basically adopts to the FW it finds on the ESC. So once you have created that FW, VESC-Tool needs a coordinating file and will then set itself up to match the FW. If you would like to work on that FW and coordinating Vesc-Tool settings, you should contact Benjamin to integrate them.
If you load FW3.61 for example, the motor detection is done the 3.61 style, the menus are 3.61 style, basically you go back in time, except that new features like eg better data analysis, logging,ConfigBackup etc. are available with the latest tool.
I appreciate the input but I donât need any assistance in understanding how the software/firmware works or how to develop on it. I think youâre aware of my background.
I am more than happy to sync with BV on these efforts but I have zero expectation of it as heâs a busy guy.
The very purpose of a community fork is to add value and feedback to a codebase, so my hope is that it can provide beneficial input & potentially code PRs. I hope it helps.
But sometimes it feels a bit strange when almost reaching top speed. It affects both motors at the same time so it is not really dangerous.
After looking at at the logs I can see what the âstrange feelingâ was. Sometimes motor and battery current drops exactly at the speed where the wobbles started before but I can keep accelerating. The current drops about 1.5 seconds before I stop accelerating at about 50km/h.
I just had a strange issue with uncensored foc.
I have a 750w onewheel hub motor that im running off of fsec 6.6⌠with the vesctool1.1 uncensored foc runs the motor great. I updated and tried vesctool2.0 and the motor will not run. It just cogs⌠attempted hfi, same issue. Downgraded back to old firmware and motor runs great again. Also motor detection provided very different results
If you use the new VESC Tool you should be able to use FW 3.55 onwards. The detection results depend on the FW on the VESC. After the detection you can save the configuration (confgBackuo), update to the latest FW and then reload the old configuration.
If you have a well tuned system, it is advisable to backup the configuration prior to the FW update. It allows you simply load the old parameters with a single click. Itâs also fast and convenient.
The cogging is probably due to the resistance value being off. Iâll try to figure out why itâs measured differently in between the FW versions.
Which picture is the 1.1x Vesc Tool?
which firmware should we use for the most accurate detection results? by accurate, I mean the values that when applied to the motor config will result in the most optimal operation. i am happy to run one firmware to do motor detection, save the config, upgrade to the latest firmware, and then apply the config that was previously saved. these additional steps would be worth it to me to enjoy the latest version firmware and its features.
3.61 or 3.65 should give you the same results as the working setup. Once the results have proven a flawless operation, you can use the Motor config over and over.
I did the detection with the T = 1000uS, but at 39 km/hr I have wobblesâŚalways the sameâŚa bit frustratingâŚUsed the Vesc-tool for android mobil, FW 4.01 (when the FW 4.02 with the changelog will be available please?)âŚTwo Vesc6+, PPM, 6380 TB motors, canbus.
I get this error when attempting to flash new FW (tried 4.x and 3.65 as they were what I had on hand). The firmware upload process looks normal and says that it completes successfully, but then gives me this error when the VESC reboots. I also tried flashing the bootloader, and it did not fix the problem. I had several successful firmware flashes before I started getting this problem, and now that it is appearing, I am also have CANBUS issues.
I am using brand new VESC 6 MK3. Any ideas what iâm doing wrong?
I was also getting all kinds of bad motor detection results that vary too wildly for me to want to get into tonight. I have lots of pictures of the inconsistent results I was getting that I can show when I wake up tomorrow, but I would like to know where these CANBUS issues are coming from as well.
Yes with 4.X firmware it slightly slowdowns when pushing trigger at max. This makes me a little bit out of balance at full speed because naturally you donât expect that.
As reported, I also had this kind of whooble at 60-80% and at least one ABS OVER CURRENT fault at each ride.
I have FSESC 6.6 DUAL.
All trouble were gone with downgrading to ACKMANIAC.
This is no error, it is a warning. If the FW version doesnât change after an upload, the Bootloader is corrupted and SWD Prog is the way forward to reinstall the FW.
3.55 to 3.65 uses the older style motor detection and in consequence the motor should run totally smooth. A fix is on the wayâŚ
The config from a 3.6x detection resolves any described issues.
In general a working configuration should be kept and restored after a FW update. Itâs fast, convenient and everything stays as it was before.
The FW version does change. Im still getting CANBUS issues. And I dont know how the bootloader would have gotten corrupted when the only things i have done with these VESCs is flash firmware, run many unsuccessful motor detections, and flash the bootloader. I never unplugged power or USB after doing these updates, I always gave the units much more than 10 seconds to reboot.
No, I just can say that before my board was running full speed wobbleless⌠Yesterday went to the Vesc-tool site, vedder it is woking to change this on FW 4.02 (think he is going to go back to the last motor detection settings)âŚThats why I am kind of anxious to solve this. Also, I change my motors recently, so there it is no old detection usefull for me to use as back upâŚ
Can anyone tell me which I/O pin the âAuxillary Output Modeâ feature engages with? This is useful for higher powered VESC applications.
EDIT: I think I figured it out. Itâs a feature specific to the VESC 75 300. The I/O pin is PC12 which is used for SPI between the MCU and DRV for the VESC 6. Iâm going to see if I can reassign this to PB12.
