That’s an opinion, not one I share.
I told you he said it, I proved he said it, that’s still not enough. I’m done.
1 Like
Unless you’re willing to brazenly break the law, like enertion, you can’t do that.
The license on the software says it must stay open-source and any forks or changes must be published as open-source. If anyone doesn’t like that, they are free to just make their own software instead of using Ben’s.
2 Likes
Thanks for stating the facts in my support. That means cheap ESC’s will always be available, unlike Mike’s prophecy.
Thanks for the link, I will do a bit more reading. But I have seen the original author(of a lidar mapping application:loam) close source his code and starting a company. Forks existed so a lot of us started using and maintaining that. So you are saying Ben can’t close source future software( derivative of his current code) that would be used in a new ESC(again closed) ? What about if someone is the sole author?
You can keep breaking my balls all you want, it doesn’t change the facts. Frank has a history of using lawyers to enforce his desires.
Also, @Trampa I’m curious why they only reported motor and battery “bad values” from the latest version of the VESC-Tool Wizard are ALL from competitor products?
There are different kinds of open-source licenses.
Some “permissive” licenses, like the ISC License, allow you to closed-source a fork or derivative.
Some “copyleft” licenses, like the GPL License, do NOT allow you to closed-source a fork or derivative.
The VESC firmware is copylefted under the GPL.
Of course, if you’re Jason Potter, you just break the law. There’s always the crime option.
2 Likes
As I see it, Frank is always stating that he protected the Trademark VESC in the good for the community and Benjamin Vedder. But as someone new to e-skate and VESC’S you will likely relate VESC more to Trampa then to Ben. I have the impression that this whole protecting thing is more to boost the brand Trampa then doing good for Benjamin or the VESC project.
Frank was the person who introduced the new 2019 VESCtool to the community and several people raised their concerns about the battery amp values suggested by the VESCtool wizard. His reply was a rant against all moderately powered boards and the failure of the builder.
I was hoping as the person who sees himself as the voice of the VESC project in this community that he would pass our concerns on to Benjamin. Instead of saying go and reach him yourself.\
@mmaner thank you for the clear and understandable walk through which was much needed.
I personally use Ackmaniac 's software for nearly two years now and love it.
4 Likes
You are more than welcome. Happy to help.
3 Likes
Here we have set the Motor Max to 50a as that is the ESC’s limit and motor amps should always be of a higher value than battery amps.
@mmaner Could you expound on this for me?
We have defined the Battery Current Max Regen at -12a because that is low-speed breaks
I was under the impression that Max Battery Regen is high speed brakes and Max Motor Regen is low speed brakes. Could you clarify?
Thanks for the write up, it will be invaluable if I get something other than a Unity! 
2 Likes
Hi!
As promised I’ve updated the vesc tool, and the FW. Vedder/@trampa, seems eager to accept my PR!
I’ve built a macOS binary here: https://github.com/DAddYE/vesc_tool/releases/tag/1.14-beta
However please note that I haven’t tested it yet since I’m on UART.
Rember to update the firmware as well, so it can understand the new control type.
Here some screens:
If you test it, please let me know how it works.
Thanks!
Edit: yeah, I’ve to fix the description, and I’m looking for a better name 
10 Likes
That was very cool of you and I want you to know that I personally appreciate you putting in the time to do this.
I will test it this weekend and let you now the result.
3 Likes
I could, but instead I just fixed my screw up . @Dareno pointed it out and I got it taken care of the next day. Somehow I missed your message until just now.
1 Like
Regarding the Ackmaniac Android app, what can it do that the xmatic app for iOS can’t?
This may be of topic, but I haven’t found an answer on the other forum or in my googling. I can’t seem to get my bluetooth module to send data to the ackmaniac android app. When I start the app the bluetooth module is recognized and I give the board a name. However, once it’s connected, no data streams from the board to the app. I’ve also tried setting up the TCP connection to the ackmaniac app to no avail. My procedure for this has been:
- Connect master vesc to computer and read firmware
- Go to connections > TCP in the desktop app
- In the android app click ? > Start TCP connection
- Enter the IP and port in the desktop app and click connect
At this point the desktop app says that it is connected to the vesc via the IP and Port, but the app on the phone never acknowledges the connection. If I click away from the TCP connection modal in the phone app, the desktop app still says it’s connected, but none of the actions (mode setup, check faults) work. I get the ESC not connected toast message.
I’ve tried disconnecting and reconnecting to the WIFI (both phone and PC)
I’m using the flipsky fsesc 6.6, the flipsky hm-10 module which is connected to the master vesc. My phone is a samsung note 8 running android 9.
Any ideas?
2 Likes
Correct me if I’m wrong, but the FlipSky module is NRF correct? If so, it won’t work with the Ackimaniac firmware. You will need to get a true HM-10 module, @BuildKitBoards sells them.
If it is a true HM-10 module, make sure you set the control mode to PPM + UART on the master VESC and the baud rate to 9600bps.
Ah I think this is probably the issue then. Thanks! I’ll check out the build kit boards module.
1 Like