Hi all,
I'm seeing some bugs manifesting as replies being sent to the wrong channel and occasional CRC errors when using both UART and USB (VESC tool) at the same time.
I think I got most of them fixed, so if you encounter the same issues maybe this will come useful : https://github.com/Flytrex/bldc/tree/serial-thread-safety
It can probably use some more stress testing before it's PR-worthy.
hi,
Has someone changed the firmware to use a PT-1000 temperature sensor instead of a 10k ohm NTC, to measure motor temperature?
I imagine it is only a small change in te firmware, but maybe more people are interested in using different temperature sensors.
Hello
Iv'e been "designing" an 10s compatible esc so I was looking through the firmware source but I find it hard to get a grasp on where to find what.
I'd for example want to edit:
Hi!
Is there any timers left on STM32 that could be used for generating PWM to control an external fan in closed loop with pcb temperature? Is this feature interesting enough to be supported in official firmware?
Thanks.
Hey guys,
I have a few questions to the PID Position Controller. I have setted up my BLDC Motor with an ABI Encoder, everything is fine. I can reach the positions from 0 to 360° correctly, if the Position Division Angle is 1 ! With the realtime data I can see that the PID_pos_now value is also zero when I set the position control to 0°.
Hello,
I am using the VESC Tool 0.95 and the last version of the VESC firmware (dowloaded from github in November 2018). I am dialoguing to the VESC through the GPIO_AF_USART3 (UARTD3),
From the VESC Tool I am able to write the App configuration to the VESC flash and read it. But I am not able to write the motor configuration (but I am able to read it).
The issue is here: "packet.c"
Dear all,
i want to use a pin change interrupt in a custom application. There is less documentation, but i figured out how to set up the interrupt, but the vesc crashes when the interrupt occours.
Do i have to configure GPIOC 14/15 in a special way because the pins are OSC_OUT ? Or is the interrupt init at the wrong place ?
Thanks in advance
GEorg
hwconf/hw_gsvesc.h:
Hi all,
I have a different kind of motor that I would like to drive with this controller. The current firmware is not suitable for this.
Is anyone interested in customizing the firmware according to my specifications? I guess it is not a too big deal - so you don't need to start from scratch. THe Windows/Linux software is not interesting for me; so there need to be modifications on the whole software.
Is there anyone here that can change the code and compile a new firmware file for me that uses ADC2 for the throttle instead of ADC1?
For some reason ADC1 has stopped working. I read 2.8V on that pin and my hall effect throttle will no longer change it. This happened after hitting a hard bump a few times. I tested the throttle on ADC2 and it seems to work just fine there, the same way ADC1 worked before I hit those bumps.
Looking for some thoughts on this data. On my dual vesc based dyno, i'm getting this data when changing switching frequency. Anything other than 20khz is distinctly and repeatably lower efficiency than 20khz. Why would this be? Is there something in hardware or firmware that's preset for that switching rate? Anyone have any ideas?
Interestingly, the test motor seems to be more stable and consistent above 20khz, but less efficient.
Could get more data easily with community setting recommendations in VESC-TOOL.
