and don’t use your wife’s old shitty laptop to do it with bad USB ports. I was all ready for 2.17 goodness and had bldc tool compiled running and ready. then i had to downgrade to 2.16 using my mac because buggy windows but then used windows to do my settings because buggy mac.
i need a decent linux laptop with good USB ports i can keep in the garage. It will save me money on playstation controllers. (because that’s what i throw when i’m mad)
A crappy laptop will work too…Linux doesn’t care. Linux is the honey badger of the pc world.
i think it was more about the bad USB ports or possibly drivers than the general crappiness of this antique Compaq. My experience with linux is that it almost always breaths new life into 10 year old hardware.
I think you should mark that this is a beta software and the people using it be aware that they maybe damage something. I think it would be better to upload benjamins version of bldc-tool and not your beta software without saying that it isn’t the official.
Let me explain. I had a freak out with your version where the motor was spinning from one direction in the other without doing anything. I don’t touched my keyboard or mouse and the motor was doing what it wants to do. Dangerous when you didn’t expect that.
There are also other bugs I noticed just in a very short time of testing.
- The right and left arrow keys doing other things than in benjamins original firmware
- Tested BLE with my HM-10 module and it is useless, because writing is not possible
- After connecting over BLE once it isn’t possible to disconnect and using USB when you have it available. You need to reopen bldc-tool and then connect to USB without BLE first
All tested under Mac OSX.
I also compiled your GUI by myself and putted it on an iPhone, because you didnt share it after PMing you. There it is also not possible to write settings and after seeing some strange minimum duty cycle readings etc. its maybe better that this isn’t working and destroying some settings. 
(But there I know that I am a beta tester, because compiling it myself and that is ok for me) Not like the bldc-tool for Mac where no one knows that he maybe drive his board into the wall, because of a bug.
Just FYI: Calc CC in FOC mode is wrong (BLDC Tool V2.17 and V2.18) in those Win and OSX versions.
Thats right. In the newest version by benjamin vedder available on github that problem isn’t there. I can only recommend compiling the official source by yourself. I am tensed when the first one fries his VESC when testing the online firmware update thing. Hopefully there is now bug in that firmware tab. That would be annoying.
Could you elaborate please Are there settings that should be corrected?
The values which are calculated are wrong and then the wrong values are applied. Only work around is to either use Ubuntu 2.18 or to stay with 2.16 on those other OS.
Thank you! That’s pretty important stuff
Doesn’t seem to be important for others. The faulty and modified versions of the BLDC Tool are still up and being downloaded.
I only can urgently advice to use 2.16 Version of the BLDC Tool on OSX and Windows or go for the original one (currently V2.18) from Benjamin on Ubuntu! Using those faulty version of the BLDC Tool can cause fatal failures!
Has been done already, also by others.
hey guys yes this is correct but i am currently working on this as I’m typing, it is an error with FOC.
ok guys atm the BLDC TOOL will just be benjamins version for windows and OS X. i will fix the issue asap it will be done soon but i just ask if maybe 2 or 3 could jump on a pre release test group that i can send you the software before i release and you test as it is almost impossible for me to get all of these bugs out.
Does this mean Jacobs 2.16 version I downloaded 3 weeks ago has bugs ?
No! 2.16 was just behaving vedders code in 2.17 and 2.18 I interested some new features for those that wanted to use it but when doing so I have just over looked a few connections in the code!
1 Like
ugh i need a new laptop at home for this. i need to be running ubuntu, i’m tired of the osx/windows dance i have had to do the last couple of times.
whats been up with it?
except for this one version that was only available for 1 day, it is always built direct from benjamin vedders git hub project, the one problem might be drivers on windows.