I have El Capitan. I downloaded it. Opened it. Allowed it. Error. Move to Applications folder. Works!
Oh nice. It was opposite for me and the same error for Spotify. Looks like @lox897 way works for this one!
Yep! Try my way! Hehehe
Thanks everyone for the help. I am still unable to open BLDC tool unfortunately. I attempted to open the file as suggested and still the same issue. I noticed there are 2 folders to choose from after unzipping. One named __BLDC_Tool FW1.14.app and the other named BLDC_Tool FW1.14.app so I tried the second one and now it displays BLDC_Tool FW1.14.app quit unexpectedly
I may just wait until I have access to a PC because I feel it may be an issue with my computer
I used the OSX BLDC tool for the previous version(because I just downloaded it, and it worked without any troubleshooting), but then dug out my old windows laptop to use version 1.14.
It’s not that I don’t like the OSX version, it’s just that so far I’ve heard tons of people say the windows version “just works”, while the OSX one takes a little more fine tuning here and there. And it does just plain work by the way… even on my super old p.o.s laptop, it ran just fine.
litterally, if you just download the windows BLDC here:
it takes less than 10 minutes from downloading the file, to setting up your VESC. There is one driver (needed to run 1.14) that you need to install (easily labeled in the “BLDC Drivers” folder), and then it is just running the program (again, super easy to find) and you are in business!
Is there any way of setting port 301 by default, other than recompiling the code ?
Yes, as I set the default to 261 originally.
In the source code, open main window.cpp
The do a find search for /dev/tty.usbmodem261 then replace 261 with 301, but next updat I will change it to 301, or implement a way that it tries both.
Please download FW2.8 again, Iv added a second field, so if the first fails then the second is tried, please download it and test it.
The tool now connects to port 301 without having to type it. Thanks. I assume other functionality remains unchanged.
Every thing will work the same!
Recently i have setup a website for the use of downloading of BLDC-TOOL for windows and OS X and all VESC related Firmware and files, this link will soon be a fully set up website with active download links, support documents and videos as well as offering vesc support via remote access and video call. the new link for BLDC-TOOL updates is:
http://www.vesc.support or http://www.bldc-tool.support
if any one has the knowledge and wants to help me set this website up that would be great i will pay maybe in vesc!
also BLDC TOOL 2.10 is know available
check my latest updated OS X version of bldc tool.
iv actually been working on the installer so know it packed in a DMG NEW: if you plug in your vesc before loading bldc tool then bldc tool automatically detects the vesc and sets the correct serial port while tagging that serial port (vesc) so the user knows its detected. you simply just click connect. soon ill add auto connect. there is also a refresh button that locates the vesc just incase you didn’t plug it in before opening.
this is all apart of trying to reduce confusion with 261 and 301 address.
I’m about 2 weeks away from finishing a bldc tool esc setup wizard that will have a single button to detect foc and bldc settings and app data to make it easy for customers with no knowledge.
please every body i need feed back on my site.
3 Likes
fucking awesome!.. the simpler the better.
With all due respect @jacobbloy, I do not see the need for an OSX installer. If anything it just adds overhead. As far as I can see, the tool already came with all dependencies and doesn’t require registering anything with the OS. Clean, simple, easy to delete and replace by a next version. Click-and-play. I understand this may make things easier for new users. I assume we’ll still be able to extraxt the executble and the dependencies ? Are these code changes being published on Github ?
All i said @trbt555 is that OS X is know packed in a DMG, which in my opinion is better then a zip file and shows a degree of professionalism.
OSX is easy because all dependancies all packed in the .app and cam be extracted very easy.
the main work i have been doing with installation is for windows where drivers where required and there is more to do then simply double click like in OS X’s case.
all changes that i have made to the serial ports vender id detection will be published to github as soon as vedder accepts the pull request.
I see, thanks. I was under the impression you’d made an OSX installer. Good work.
Slightly off topic: wouldn’t it be great if the BLDC tool would be able to save entire configs (not just the MCC config, but also the app configs) to XML ? That would make swapping VESC’s and even sharing configs so much easier. Also, wouldn’t it be great if you click READ CONFIG, BLDC reads the whole config (also the app configs) and populates all tabs with only one click ? I’ve always found this clunky.
1 Like
I have always thought a beginner’s and advanced version of BLDC should exist.
The begginers interface could be very simplified. It could have scripts that run all the seperate tasks In the background but make it automated one button stuff on the front end…maybe have sliders or dials that represent the range of data that you can or should choose… out of the 100+ parameters available in BLDC we only ever tend to change 6 or 8 of them anyway. So they should all be on one screen. Save them all together once configuration is done, one save button. Load them all in one go from presets.
3 Likes