base on The VESC motor control firmware # VESC firmware [](https://www.gnu.org/licenses/gpl-3.0) [](https://travis-ci.com/vedderb/bldc) [](https://www.codacy.com/app/vedderb/bldc?utm_source=github.com&amp;utm_medium=referral&amp;utm_content=vedderb/bldc&amp;utm_campaign=Badge_Grade) [](https://github.com/vedderb/bldc/graphs/contributors) [](https://github.com/vedderb/bldc/watchers) [](https://github.com/vedderb/bldc/stargazers) [](https://github.com/vedderb/bldc/network/members) An open source motor controller firmware. This is the source code for the VESC DC/BLDC/FOC controller. Read more at [https://vesc-project.com/](https://vesc-project.com/) ## Supported boards All of them! Check the supported boards by typing `make` ``` [Firmware] fw - Build firmware for default target supported boards are: 100_250 100_250_no_limits 100_500... ``` There are also many other options that can be changed in [conf_general.h](conf_general.h). ## Prerequisites ### On Ubuntu (Linux)/macOS - Tools: `git`, `wget`, and `make` - Additional Linux requirements: `libgl-dev` and `libxcb-xinerama0` - Helpful Ubuntu commands: ```bash sudo apt install git build-essential libgl-dev libxcb-xinerama0 wget git-gui ``` - Helpful macOS tools: ```bash brew install stlink brew install openocd ``` ### On Windows - Chocolately: https://chocolatey.org/install - Git: https://git-scm.com/download/win. Make sure to click any boxes to add Git to your Environment (aka PATH) ## Install Dev environment and build ### On Ubuntu (Linux)/MacOS Open up a terminal 1. `git clone http://github.com/vedderb/bldc.git` 2. `cd bldc` 3. Continue with [On all platforms](#on-all-platforms) ### On Windows 1. Open up a Windows Powershell terminal (Resist the urge to run Powershell as administrator, that will break things) 2. Type `choco install make` 3. `git clone http://github.com/vedderb/bldc` 4. `cd bldc` 5. Continue with [On all platforms](#on-all-platforms) ### On all platforms 1. `git checkout origin/master` 2. `make arm_sdk_install` 3. `make` <-- Pick out the name of your target device from the supported boards list. For instance, I have a Trampa **VESC 100/250**, so my target is `100_250` 4. `make 100_250` <-- This will build the **VESC 100/250** firmware and place it into the `bldc/builds/100_250/` directory ## Other tools **Linux Optional - Add udev rules to use the stlink v2 programmer without being root** ```bash wget vedder.se/Temp/49-stlinkv2.rules sudo mv 49-stlinkv2.rules /etc/udev/rules.d/ sudo udevadm trigger ``` ## IDE ### Prerequisites #### On macOS/Linux - `python3`, and `pip` #### On Windows - Python 3: https://www.python.org/downloads/. Make sure to click the box to add Python3 to your Environment. ### All platforms 1. `pip install aqtinstall` 2. `make qt_install` 3. Open Qt Creator IDE installed in `tools/Qt/Tools/QtCreator/bin/qtcreator` 4. With Qt Creator, open the vesc firmware Qt Creator project, named vesc.pro. You will find it in `Project/Qt Creator/vesc.pro` 5. The IDE is configured by default to build 100_250 firmware, this can be changed in the bottom of the left panel, there you will find all hardware variants supported by VESC ## Upload to VESC ### Method 1 - Flash it using an STLink SWD debugger 1. Build and flash the [bootloader](https://github.com/vedderb/bldc-bootloader) first 2. Then `_flash` to the target of your choice. So for instance, for the VESC 100/250: ```bash make 100_250_flash ``` ### Method 2 - Upload Firmware via VESC tool through USB 1. Clone and build the firmware in **.bin** format as in the above Build instructions In VESC tool 2. Connect to the VESC 3. Navigate to the Firmware tab on the left side menu 4. Click on Custom file tab 5. Click on the folder icon to select the built firmware in .bin format (e.g. `build/100_250/100_250.bin`) ##### [ Reminder : It is normal to see VESC disconnects during the firmware upload process ] ##### **[ Warning : DO NOT DISCONNECT POWER/USB to VESC during the upload process, or you will risk bricking your VESC ]** ##### **[ Warning : ONLY DISCONNECT your VESC 10s after the upload loading bar completed and "FW Upload DONE" ]** 6. Press the upload firmware button (downward arrow) on the bottom right to start upload the selected firmware. 7. Wait for **10s** after the loading bar completed (Warning: unplug sooner will risk bricking your VESC) 8. The VESC will disconnect itself after new firmware is uploaded. ## In case you bricked your VESC you will need to upload a new working firmware to the VESC. However, to upload a firmware to a bricked VESC, you have to use a SWD Debugger. ## Contribute Head to the [forums](https://vesc-project.com/forum) to get involved and improve this project. Join the [Discord](https://discord.gg/JgvV5NwYts) for real-time support and chat ## Tags Every firmware release has a tag. They are created as follows: ```bash git tag -a [version] [commit] -m "VESC Firmware Version [version]" git push --tags ``` ## License The software is released under the GNU General Public License version 3.0 ", Assign "at most 3 tags" to the expected json: {"id":"5864","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"