I've been trying to change the RX/TX pin assignments for the NRF52 code from Ben's Github repo. Unfortunately I think I'm doing something wrong because the code doesn't work after I compile the code and flash it to the NRF52832 module. I have installed the ARM and NRF52 SDK dependencies and also changed the IS_52832 variable in the makefile to 1.
Hi all,
I've recently spent some time figuring out how to unbrick the VESC6-MK-IV. To help others with the same problem, I'll share the procedure of how I did this, as there are many ways of doing this according to the forums. My current setup is that I have an STM32407 Discovery card that can be connected to the VESC6, and I used the ST-Link together with the STM card to write the firmware to the VESC. Most of the procedure can be done using an ST-Link dongle instead.
Procedure:
As i needed a complete overview over all can Messages, i started doing things properly following an accepted industry standard.
So i started building a dbc file for VESCs (and ofc. all other projects with the same or similar Firmware....).
Right now, there are not all messages in there, but the rest will follow over the course of this week. Also for now, the messages are only in there for one VESC with ID 1. So, it is far from done, but i wanted to share it anyways. If there are any thougths about posible improvements, please share them.
I found the post https://vesc-project.com/node/2010. Updated to gcc version 07-2018-q2
Hi I have a model Flipsky FSESC 4.12 50A 4.12
I wanted to see if I can modify the most current firmware 5.01 offered on Github.
Hi,
I need a developer to make a custom firmware with specific features. Please contact me for more information if you can do it.
Like my title states, i am very new to all of this. I have the stormcore beta on my phone, and i would love to use it but my unity esc is too out of date. I need to perform a software update but i am unsure on how to do this. Any warnings/imsight would be amazing because my prior nowlage is essentially 0 on this subject. Thank you all.
Hi guys,
recently I was developing an custom app for the VESC firmware.
I was uploading it through an raspberry pi connected to the swd port.
It went fine until I uploaded code with major changes. Since then I can't connect to the VESC.
Open OCD fails with "Info : SWD DPIDR 00000000". It is the same behavior as if nothing is connected.
On the Vesc only the blue led is lighting up. No red blinking as befor during programming.
Hello,
Thanks for the project. I put the VESC on my Hardware. Everything worked. :)
I have several questions and one bug.
I have compiled the latest farmware 5.1.
I have an LM61 temperature sensor near the transistors.
Tell me where to change the code for this sensor correctly.
I also had a problem with setting up the APP.
If you set the controll PPM + SERIAL. after reset, the controller no longer works not according to PPM and SERIAL.
I got around this problem. added for my motor.H and APP.H to the project.
hello everyone,
I have been working on gimbal stabilization, I am using vesc firmware to control bldc motor in position mode. I have some progress that I can control motor in position mode but my motor has high frequency vibration, what cause this, I do not know. I've tried so many thing to overcome this issue but I could not make it. Does anyone try to control motor in position mode? Could anyone please help me?
best regards,
Hello everyone!
I am working on an application to control an IPMSM and I am developing a firmware inspired by the VESC. I could not use the standard firmware because I need to design and implement more complex algorithms (MTPA, FW, optimizations,...), and I do not see a straightforward way of doing this in the firmware. If anyone has experience or any good tutorials on how to modify the VESC firmware to incorporate other algorithms please share!!
