Then 40A * 3,6V * 8S = 1152 watts
O.K. thanks! But that 3.6v for lipo should be 3.7v?
That’s true. In watt control I set the maximum my battery can handle and then set the max watts lower so that I never have an issue with it. This way I have the same power output even when the battery gets lower. You could even set the battery max extremely high and then set the max watts to 250 watts and it would drive very gentle. Max battery in watt mode is only there to protect the battery if somebody enters crazy max watts values.
I see, so i’ll put those 1152 watts with my battery max. set at 40A and i’ll be on safe side isn’t it?
Lets say you put it to 2000 watts. In this case the calculation for the throttle would tell the VESC to draw 2000 watts which it tries. But the max battery value forbids that. So you would feel that more than 60% throttle doesn’t give more power. So you should not set it higher than my calculation to don’t loose throttle range.
I created a Android app that works together with my modded firmware to watch the actual motor values and to quickly change the motor settings. You need a standard HM-10 Bluetooth low energy device for that.
So you need the latest version of my firmware and a standard HM-10. If you are interested to test the app then send me your email via pm and i will send you the file.
But it really only works together with the HM-10. Otherwise you can’t see anything in the app because the connection to the module is the starting point. You also can then host multiple boards with different setups because each bluetooth module is handled individually.
The cool thing is that you can record the screen while you are riding with another app to analyse your ride later on. that also lets you understand much better how the VESC works.
The app looks like this (not a actual picture) Have to make a video this evening. I think you will love the features.
8 Likes
I decided to do it in another way. Currently i am adding the app as a beta version to my google play store account. So i will share the link here later so that anybody can try it.
My aim with this app is give it for free and count on donations. (I know that is a bloody stupid idea 
)
Because of that i add here the donation link again. Donations Or if you want to buy a Raptor 2 and want to save 100$ and support me with 100$. Raptor 2
1 Like
Does the app support dual vesc?
How about pushing the firmware and BLDC-tool code to github? They both are licensed under GPL, you are bound by this license. Please do it as soon as possible as you are violating our right (the end users) to
“study, share and modify the software”
1 Like
How can i know how much A my battery can handle?
@SageTX The app doesn’t really support dual VESC. It does update the slave vesc with the settings when the motor settings have been changed via the app. And it just doubles the realtime data values if you have 2 vescs. But it doesn’t detect the values of the second one individually.
@rmrf Do i have to share my code via Github or is it enough when i provide the code at my dropbox account? Never used Github before.
@ninja just take the C rating of the batery and multiply it by the amp hours and the bateries in parallel. A 10S4P with Samsung 25R cells (2500mah = 2.5ah) would be 2.5 * 8C * 4P = 80 amps.
Great! Was wanting the ability to change modes so that’ll do!
How did you get BLDC-tool source code then? 
GitHub is the best and recommended way to do it. Dropbox is kinda OK in a sense that you will at least stop violating the license. The downside of Dropbox is that it’s not easy to see the updates that you are making each time and contribute.
I got crazy number that way, so 8S1P 30c 8000mah = 30 * 8 * 1 = 240 A can i put this value like battery max.?
@Ackmaniac You don’t have to upload to git or any other source repository legally because you’ve already done that by releasing the zip with the source in your dropbox. It’s just easier if you upload to git so we will be able to see the changes you’ve made and we can submit code back to you. You’ll probably be receiving a ton of help if you do upload to git. It’s the spirit of opensource. 
Samsung does exactly what you did and release in one huge blob in your dropbox. They are forced by law (under gpl) to release source for their kernel. So what they do is release in a tar ball which is a mess and we can’t see their changes made. It’s a diffs worst nightmare most of the time.
Honestly it isn’t my aim to protect my source code. Just don’t find the time to deal with github. Tried once but failed. And i wanted to finish my changes and features before people begin to discuss about my code. And at the moment i am working in the app integration when i find the time.
All of the stuff from me is for free. Even the app.
The people who complained that i didn’t make it public are those who want to integrate it to their stuff where they charge money for it.
Till now i got 20 Euros of donations. Which is like 10 cent the hour or so. But i still continue for the fame
But money makes the world go round.
What makes me happy is that Benjamin Vedder took over a lot of my features to the new VESC tool. So everybody can profit by that. Sadly he never mentioned it before i pointed on it. Little thanks would have been cool. But on the other side i have to thank him for his amazing work that became my most beloved hobby.
9 Likes
The source code for firmware is missing. I would not write it here if the code was public. It is not.
This is not about free / non-free. This is about licensing and doing things right. Please let’s stay on topic. The source code for firmware must be published because of GPL.
1 Like
I’m definity going to donate when I get the module and tested everything. But because I ordered from aliexpress, it could take awhile