VESC FAQ | OSX MAC APPLE Version of BLDC tool

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.

http://vesc.support

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

@jacobbloy Thanks for the work you put into this community!

Al…

did you figure this out? if you did what did you do. i have same problem

You are referring to the missing bootloader? If so, an STlinkV2 (8€ at eBay) will do the job, but you have to work with Ubuntu and follow the steps mentioned at vedder.se.

Are you sure it only works with Ubuntu? I can upload bldc-firmware with OS X and I kinda can upload the bootloader, but it hangs after verifying the checksum OK, is that normal?

bldc-bootloader/ $ make upload 
#qstlink2 --cli --erase --write build/BLDC_4_Bootloader.bin
openocd -f interface/stlink-v2.cfg -c "set WORKAREASIZE 0x2000" -f target/stm32f4x_stlink.cfg -c "program build    /BLDC_4_Bootloader.elf verify reset"
Open On-Chip Debugger 0.9.0 (2015-11-15-05:34)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
0x2000
WARNING: target/stm32f4x_stlink.cfg is deprecated, please switch to target/stm32f4x.cfg
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <    transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain     JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.246592
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
target state: halted
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x0800c000 msp: 0x20000400
** Programming Started **
auto erase enabled
Info : device id = 0x10076413
Info : flash size = 1024kbytes
target state: halted
target halted due to breakpoint, current mode: Thread 
xPSR: 0x61000000 pc: 0x20000042 msp: 0x20000400
wrote 131072 bytes from file build/BLDC_4_Bootloader.elf in 5.563057s (23.009 KiB/s)
** Programming Finished **
** Verify Started **
target state: halted
target halted due to breakpoint, current mode: Thread 
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20000400
verified 4256 bytes in 0.076163s (54.570 KiB/s)
** Verified OK **
** Resetting Target **
^Cmake: *** [upload] Interrupt: 2 <-- Here it hangs and I interrupt it with Ctrl+C

That point with the hanging after reset the target is normal. I have the same behavior with my Mac (never tried Linux, just flashed with the Mac) and the firmware upload is completed. After that I can connect to the USB of the VESC normally.

Can someone tell me what these settings are for? And should they be left alone?

for testing the motor on the bench

For like motor detection?

more so to test the motor with various currents or speeds. You can see if your motor will spin up with lower currents or something.

I don’t get how you would use this panel. What button do you press to activate the motor with these settings?