Ah! That explains it 
Yeah that was something i had to get my head around. Your way of thinking is mathematically correct.
1 Like
Hi! I just finished remake my enclosure (fiberglass) and I took the oppurtunity to upload to 3.101 firmware during the process. I used the same parameter as before, but this morning I noticed that when I go full throttle on the fast mode (Nano-x remote) the board loses power for one second. I din’t have it this problem before, never had a single drop of signal or power. If I ride in the low speed mode that won’t happen. It’s sound like some current or watt limit reached but by the chart I am far away from the limit, moreover I never had in the past 1 month and a half that I used the board. Do you know what It could be? It’s quite scary! Thx a lot
PS: In the chart you can see when it happend.
Setup: Diyeboard 90mm hubmotor 2 Maytech VESC 10s3p 30Q battery Nano-x remote 60A BMS
Are you sure that you adjusted you ppm pulsewith with the fast mode active?
3 Likes
F…K me!!! You are right!!! ahahaahh Sorry sorry Sorry 
That’s what happen when yuo set things at 3am…
2 Likes
Just released the new Version 3.102:
- Fixed bug where motor did spin backwards when motor max is lower than motor min.
- Cruise control now takes latest motor amps to start the PID controller instead of starting from zero. This way cruise control starts extremely smooth when you accelerate up a hill (or at braking (only NRF)). If you did hold a constant speed uphill before activating cruise control you won’t even recognize that it became active. Old behavior always started form 0 and tried to balance the speed. But till you got there you lost already a lot of speed uphill. This way the PID controller could be set up less responsive so that it is even smoother at carving.
- Small change for start of sensorless openloop to take latest detected position instead of position of last calculation. (guess it’s not recognizable)
A easy way to update is to following:
- connect to the ESC
- read motor congig
- read app config
- update the firmware
- connect again after 10 seconds
- write motor config
- write app config
then do the same for the slave if it exists. It is important that you don’t close the application in between. or you can save the config via the menu in a xml file and the read it again after you flashed the firmware.
9 Likes
mac app always crashes so this is kinda difficult. I’ve sent numerous error logs in
Which mac App?
The compiled Vesc tool
You mean while firmware update? Yeah that happens. I don’t have a MAC so i can’t really analyse. If you have a error log that could help. Never seen one.
During update and anytime the Vesc is rebooted. The Mac application will restart. I’ll see if i can access a log the next time I’m playing around with my vescs
Is this just a ESC-Tool update to Version 3.102? Or Firmware? I’m still getting 3.101 in version 3.102 when flashing the firmware.
Tried it out. But it immediately closes when trying to connect. Thanks for compiling this though dude.
1 Like
Saw that also by now, seems that i mixed something up with the exe file. Will fix that soon.
1 Like
Thanks dude!
Strangely having problems compiling the version with the icon for the tool. So i just added the version without the icon for the moment. Firmware doesn’t care about the icon so you can use this one without issues. Will try to fix the icon version tomorrow.
2 Likes
guess i gotta download windows for this here macbook
Did you already upload it? Looks like the same version as before.
Does this VESC tool work on windows 10 as well?