Comments (2)
You can read out the entire motor configuration over UART or USB using VESC Tool. If you want to make a config serializer/deserializer yourself that is possible too from the VESC Tool source code and config XML files. Another approach would be to upload a LBM-script that supports your UART-commands. You can also send REPL-commands directly over UART, they will respond with the values back on the UART. There are many ways to achieve this already and I don't want to use limited firmware space for adding even more commands. I also have to maintain them over the releases, which is an additional burden.
Personally I'm not a fan of tiny embedded linux boards for things like this as there are so many ways to corrupt the sd-card (or other memory chips) and something like buildroot is inconvenient to work with. If you run regular ubuntu you also get terrible boot time. Then even if you spend a lot of time setting up your perfect buildroot environment and get everything running somewhat smoothly that same linux board might not be available next year and you have to adapt to another one. I spent some time a while ago going down that path and even though I got it working I'm not a fan of it: https://github.com/vedderb/vesc-os-pi
from bldc.
You can read out the entire motor configuration over UART or USB using VESC Tool. If you want to make a config serializer/deserializer yourself that is possible too from the VESC Tool source code and config XML files. Another approach would be to upload a LBM-script that supports your UART-commands. You can also send REPL-commands directly over UART, they will respond with the values back on the UART. There are many ways to achieve this already and I don't want to use limited firmware space for adding even more commands. I also have to maintain them over the releases, which is an additional burden.
Personally I'm not a fan of tiny embedded linux boards for things like this as there are so many ways to corrupt the sd-card (or other memory chips) and something like buildroot is inconvenient to work with. If you run regular ubuntu you also get terrible boot time. Then even if you spend a lot of time setting up your perfect buildroot environment and get everything running somewhat smoothly that same linux board might not be available next year and you have to adapt to another one. I spent some time a while ago going down that path and even though I got it working I'm not a fan of it: https://github.com/vedderb/vesc-os-pi
Oh, I do understand all your points!! I think I will implement the LISP script that supports my UART-commands.
About the hardware changing, yes, I am seeing that a lot on the years I am being using the chinese motor controllers and displays - now even with chinese VESCs. I developed firmware for TSDZ2 ebike mid drive motor but then they changed to a different microcontroller, without SDK, no cheap available dev tools like the STM.
The same on the displays, the same display outside but different hardware versions that make the firmwares incompatible....
That is why I decided to move to VESC as the motor controller, then build my own DIY high level software EBike/SCooter/EMotorcycle board, as also my DIY display. If possible, I prefer to use well known hardware modules, that I can easily reuse over the projects and repair - even if that is not the most recent technology.
And about the Linux, I think it is inevitably, because of the demand for software complexity and more and more powerful, cheap and power efficient processors.
from bldc.
Related Issues (20)
- Feature Request: Disable Field Weakening at compile HOT 2
- Current control tuning HOT 1
- make qt_install failed
- Adding MakerX hardware HOT 1
- Lisp app-adc-override wrong values HOT 16
- TCP connection for VESC tools is unavailable when uart connection is established with Lisp
- Unexpected sensor port voltage on VESC 6 75V HOT 1
- Traction control on dissimilar motors. HOT 2
- CAN bus spamming
- Bug in release 6.02, in COMM_GET_IMU_DATA command handler, controller_id is never sent
- I ran into an error using make qt_install in Windos_PowerShell
- I ran into an error using make qt_install in Windos_PowerShell
- I ran into an error using make qt_install in Windos_PowerShell
- I ran into an error using make qt_install in Windos_PowerShell
- Support for bipolar BLDC motors?
- Feature request: updating c_libs interface header HOT 3
- Reverse Driving - Negative Duty Cycle Problem HOT 1
- make arm_sdk_install issues on windows HOT 1
- Get ESC faults via CAN HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bldc.