Cool dude. Did you do it with a computer or just with the phone app?
Computer and USB.
Itâs still not advisable to strap two big motors to a non capable battery. The output power of the motors should always be matched with a pack that is able to supply that power. Luckily VESC-Tool allows you to compensate a weak battery pack by lowering Battery Current Max to a value that doesnât let your pack sweat. Even the wizard has an advanced tab to enter the limits with ease during the setup process.
Frank, I am one of the few guys that agree with you on that matter.
However there are a couple of occasions where the stock 99A/-99A setting may cause harm.
Some use a discharge BMS (unnecessary and dangerous IMO), many of those limit regen current and if exceeded will shut down leaving you without brakes. The same during acceleration as the BMS would suddenly shut down.
Obviously there is no single value that would be appropriate for all the various setups.
How about having this value in the wizard for the user to specify accompanied with a big fat warning popup?
There is a warning pop up. And there is not general valuer that works. A discharge BMS can be dangerous, I agree. But that is a problem of the BMS, not the VESC. Luckily you can enter limiting values if needed.
One major problem with setting limits is: If you set the batt regen limits too low, you loose brakes at speed.
We did a manual to adjust things to your needs. I can add the BMS info in there:
Frank, as I said, I am one of the few guys that agree with you on this matter.
The sheer amount of comments on this should be enough of a hint that something has to be done.
As you say a low value can be dangerous.
This is why I propose a step where the user must input/modify these values accompanied by a warning like you have in the motor size selection.
Obviously the whole discussion is not about an experienced user but a beginner.
I took a look into the manual.
It is a good start. 
I really like the idea of integrating a database of known cells into the tool and battery max/min being calculated from that. I think thatâs a great idea @Trampa
It is a good idea.
However as you know a batteryâs discharge current capability depends on a lot more that the type of cells.
I have made batteries which are limited by the type of series connections because they were going on builds that would never need the full output of the cells.
And also some users may choose capable cells but a crap discharge BMS.
These things are true. I think there is no fix-all solution without integrating a lot of extra steps into the wizard.
And then Noobs have more problems to set things upâŚ
I would prefer to make good videos that address one thing at a time.
And videos that address things to avoidâŚ
At least metr stuff got some recognition
Unlike this forum which still gets no attention ![]()
Thatâs ironic since without this community metr stuff wouldnât be anywhere close to where it is now ![]()
Youâd have to meet Ben to understand this better I think. He is VERY committed to open source, even more than most open-source guys Iâve met. He pretty much eliminates any closed source software from his life as often as possible. Even the CAD software he uses etc. Itâs pretty impressive to see someone this committed to something in a time when itâs easier to bend your morals I think.
I know for a fact he respects roman and the app he has made, but I donât think he will ever see eye to eye with a closed source project. I donât think its surprising at all that he is disappointed to see that one of the more successful projects interfacing with vescs is closed source. Its more than just a different business model its a different world view on how intellectual property should be handled.
The world is cool place because people mostly have the freedom to conduct themselves as they please but that doesnât mean we all have to agree on how things are done.
This is definitely an area for improvement that I will be working at.
Thank you for this Jeff!
Yup user error of my behalfâŚ
I just couldnât fathom having a Unity with one MCU and one USB requiring having to set up both motors for HFI, with all the can-buss forwarding etc⌠honestly it never even entered my feeble mind⌠and yes I could see the two VESC IDsâŚ
Foolishly⌠I was running one motor HFI and one motor was running unsensored FOC⌠in my testing the non-HFI was actually running a bit hotterâŚ
@b264 my settings were basically a few volts higher that the default settings⌠I thinkâŚ
22âŚ8âŚ12
thanks guys for your help⌠Itâll be a while before Iâm able to test and tune HFI⌠real-life plopped right in my lap pushing skateboarding back to the peripheryâŚ
skateboarding is real life
Thanks for the support with USB update. I had to uninstall USB devices to be able to connect.
I have now updated my 2x 1.7 focboxes and it works great after limiting âDuty cycle limit startâ to 90%. otherwise i got speedwooble at full speed.
I have tried HFI some and got it working kind of good after some fiddling with the 3 different voltage values. It seems one of my motors will work well with low voltages and one needs almost double voltage.
One thing that i did not manage to get working good is breaks and reverse during HFI rpm. Brakes are kind of weak compared to without HFI and some time i canât reverse. Will try some different settings regarding smart revers and higher/lower voltages for HFI.
If you and Vedder have time to test out higher frequency I think it would make the function so much greater if it would works.
I just want to say you two are doing a great job, been reading some of your and Vedders posts and it seems like both of you are doing something you love :).
How can you connect Unity to the vesc tool app? What module/connector?
No module, just download the vesc tool app linked above and it will pick up your unity as a Bluetooth device.
Nice, thanks!