Vedder and Apple are no good friends and he coded his stuff alone. He owns the copyright for his code. Benjamin is very serious about what he is doing and he is very serious about the GPL-license. E-skaters better get an Android phone sooner than later.
Apple and freedom are fundamentally incompatible at the very core. This is one manifestation of that. You can run the tool on an Apple laptop (for now)
True, you canāt go back on the GPL. But if Vedder was the sole copyright he could give an alternate license. Heās not though, as others have made contributions and thereās no mention that you hand over copyright when making a contribution.
@Deodand ha, the official docs make no mention of this support, I swear it previously stated partial support for Android . Hereās a thread with some indication it existed. Looks like that support may be getting dropped, may mean a port over to the Bluetooth module needs to happen regardless of iOS support.
Actually the GPL covers all of that
Serial port already doesnāt work on android. If you use a phone variant you use bluetooth anyways.
Its true though that QT partially supports serial on android but it doesnāt work on many many phones and the mobile version of the vesc-tool doesnāt have a serial connect button.
Can anyone give me some instructions on how to flash the Vedderās firmware to a hm10 module?
I donāt know why, but just kind of assumed it used that serial port library for Bluetooth connections too. Thereās a single line in the Qt Creator project file you need to comment out to not import this module, after that thereās a few methods that need to be removed that wouldnāt work on iOS anyway.
Then you get thisā¦
I donāt have my iPad handy, just the simulator, but layout looks a lot more usable on the iPad. Iām guessing this is because I havenāt told it to use the mobile specific layout.
Will try to connect it later on tonight when I get home. Thereās a stack of warnings being printed out, and Iād be very surprised if it worked first time. Still promising for the 5 minutes (excluding the hours it took to download Qt) effort I put in.
Cool, Iāve been playing around with this code for awhile. Let me know if you get hung up on something.
Just flashed a nrf module. Very easy everything is done just need to run the script.
Didnāt work first time on iOS, but Iād be worried if it did.
Thereās a ākind ofā bug in the Bluetooth code on MacOS/OSX, I say kind of as its not really a bug more that BT support was never tested on MacOS. This same bug affects iOS. Iād really like to get this fix into the official repo as Iām currently running the VESC Tool in an Ubuntu VM with a USB dongle, whereas I could just use a native MacOS build and the inbuilt Bluetooth. I havenāt tested it, but am pretty sure the Mac issue is fixed.
I did test it on my iPad though
Lots of little issues; UI rendering, have to click through license agreement each launch, where to save motor/app config files, etc. As I said before itās in a pretty good state considering how little effort it took.
Iām also a Mac user, and need to have a Ubuntu VM as well. Could you make a pull request of your changes ?
Yeah. Will tidy it up over the weekend and do a bit of testing just to make sure it doesnāt break other platforms, etc.
You might be aware of this but commenting or un-commenting #CONFIG += build_mobile in the .pro file will build the mobile UI. In my opinion this UI needs a lot of love before it will feel good to use but it is at least workable on the phone screen.
Thatās good to know. Iāve spent a bit of time looking through the VESC protocol stuff, but the UI and QT Creator is something new to me.
VESC Tool UI does look to be lagging a lot of the other options available, but it seems like the right spot to focus development. Thereās probably 5-6 apps on this forum that all seem to do the same thing but not everything we want, itād be nice if it was a little less fractured.
Of course the GPL issue gets in the way a bit. One possible workaround would be to distribute a compiled ipa/app file, would skip the requirement to install Qt (16GB WTF!) and maybe even Xcode. BUT, theyād still need to signup for a dev account (free) and jump through a bunch of provisioning hoops and these can be a real PITA.
Honestly, as you stated above Vedder needs to get in contact with all other contributors/copyright holders and ask for different licensing terms for this to end up on iOS āproperā. Iād go so far as to say he should also require copyright assignment (just like Qt does). Oh and someone will need to get him on a Mac with iPhone/etc for testing. Probably wonāt hold my breathā¦
Yeah imagine if your software had a bug that you knew how to fix that prevented a large percentage of your user base from using it. Then you just told people rather than fixing it to just buy different $500+ electronics.
I think if Vedder could figure out the legal side he could rely on someone to help him test/debug the ios implementation, obviously it canāt be too insane if it only took you a bit to get one semi-functioning. I canāt imagine there would be a huge outcry against a careful dual license to enable app store distribution and maintain GPL everywhere else. Licensing isnāt my area of expertise though
Is this new VESC tool software compatible and work well with the Maytech VESC?
Hi, Benjamin always assures max compatibility with all Hardware revisions. Latest Firmware for all Hardware revisions is included. Itās lots of extra work for Benjamin to make this happen. If you like the App please consider to give Benjamin some support.
Frank
Hey, Iām confused: which Bluetooth modules besides the trampa one work with the mobile vesc-tool, and what exactly do I have to do to get them to work? I have one of @JLabs modules which Iām hoping I can use with this.
Our modules have a custom Firmware, written by Benjamin, and they have the correct connectors and pin connections. So that is plug and play for our VESC 6. We ordered more connection cables so that you can connect them to any HW 4.xx ESC (plug and play). Cables should arrive within the next weeks. You can also use the current cable, get yourself a female JST-PHR 7 Pin connector and pop that onto the cable ends. A needle does the trick to get the individual cables out of the 8 Pin connector we supply. No big issue, 5 mins job. Frank