Just use the free version. Works just fine. I’ve never used QT before this morning so I’m still learning about it and how things work. But I was able to compile a build for linux (something I need!!!) in about 3-5 minutes or so. I also removed the beginning pages so that I don’t have to read it every time I open the app. If I get a few minutes later I’ll compile you a Mac build. Gotta go ride before the rain hits!!!
I’m sticking with 3.1 firmware until metr and perimetr are compatible with 3.101 and until there is a Mac version of the tool.
Looking forward to this. @Ackmaniac
I am trying to use the latest version of VESC Monitor (V1.85) on a Galaxy S6 (Android 7.0), and although I see the bluetooth module, the second I select it in VESC Monitor, the App crashes. I didn’t have this issue a few weeks ago, so am wondering if there is a bug in the latest updated to VESC Monitor (V1.85). anyone else seeing this? @Ackmaniac
Fixed the issue already in the latest version 1.88.
3.101 is compatable with Metr mate, using it myself!
yes. it is now working. Thank you!
However, is there anything you can do to keep the app from crashing/freezing when the VESC is turned off? @Ackmaniac
Doesn’t happen with my phone. But i will have a look with my other one.
This might be a stupid question, but if I’d want to have a mode that’s using only one motor, would that be possible (and safe for the vesc) by adjusting settings in the app? Like maybe setting batt and motor max to zero but still having it connected and powered on?
If so, could one use two motors for braking, setting batt and motor min values, but using only one motor for acceleration?
If you press back multiple times it will close out correctly, but I get the same freeze when I click the disconnect button, and have to force close to get it running again.
Closing from the switcher when you have continual notification on doesn’t work, when happens when you hit disconnect, have to force close
Wouldn’t try. It also doesn’t make sense to use only one motor. It should be more efficient to run 2 instead of one if both need to move anyway. Because then they run with half current and that means lower heat losses.
Under certain circumstances it could make sense to run with one motor if there was some sort of malfunction happening and you were trying to get back home.
Also one thing I don’t understand why it hasn’t been integrated in the VESC firmware: Right now, every time you powercycle the board, the Watt-hour, Amp-hour, and distance data is lost (rezeroed). To make a useful battery gauge, that data should be stored in non-volatile EEPROM (on the VESC ST Microcontroller), and only rezeroed either via the app or whenever the voltage of the battery gets above let’s say 41.0V (for 10S pack), which indicates that the board has been recharged (just like when you rezero your trip odometer on your car after filling your tank with gas). Please try to implement this in the VESC firmware and App as it will make the battery gauge a lot more useful. @Ackmaniac
@ackmaniac sorry to bring this back again, but is there a fix for this issue? Problem does not happen in BLDC
@Eboosted Could you please describe that a little more? That sounds like a desirable feature, not a bug. I’m confused
What exactly is happening?
If you run FOC whenever you are braking and are approaching to a dead stop, let’s say 2km/hr, the brakes lock themselves at full brake and you get thrown forward.
This doesn’t happen on BLDC mode.
If you can adjust the speed the stop happens at, that sounds fucking fantastic for waiting at a red electric traffic signal. No more throttle, brake, roll back, throttle, brake, roll back, throttle, brake, roll back, throttle, brake, roll back
I have the same happening on regular firmware. When approaching to full stop speed wise the wheels blocks itself fully. It doesn’t block the wheels when your speed is zero and you have full brake engaged.
Doesn’t happen to me in unsensored FOC on FOCBOX’es 
ackmaniac v3.101
It is the normal behavior. At slow speed the VESC can’t detect the speed of the motor and does a full short when braking. It really depends on your motor at which speed that happens. That’s the reason some notice it and some not. My firmware mod does the same as the original when it comes o this behavior. With sensored motors it is much better. And it also depends on how many cells in series your battery has. Because at braking below 3% duty cycle the VESC will go into that block. And with a 12S battery that happens at 20% higher speed then for a 10S Battery.