I downgraded using vesc tool 0.91 and bam it all works again. I repeated and switched between the two to verify. Happens on both my vescs, both my bluetooth adapters and both phones. For whatever reason data isnt being sent on the latest firmware. Im using HK vesc 4.10 and genuine keyes hm-10s. Anyone any ideas why?
I edited the FW and compiled a 100% throttle limit VESC6. Then I ran a motor at 100% throttle and it seems to run fine. However, the current measurements in VESC-Tool are all wrong. The average current at 100% throttle is very different from the average current at 99% throttle. And the sampled data makes no sense at all. Here on the left is the sampled data. On the right is oscilloscope traces of the phases showing the vesc is indeed running at 100%.
Since the generator usecase seems pretty common I wrote a custom app for that:
Uzip it to get generator_app.patch (unfortunately ordinary text files are not allowed here, so I had to zip it) and apply to a current firmware (current = 3.40, but older should work too) with
I see that in BLDC control there are two parameters for switching frequency: max and min. Is that because the PWM frequency is adapted on the go?
Can I put max and min the same value to keep a constant frequency?
Hi all.
Apologies if this is a known issue or has been talked about before.
Hi all,
I have two problems with a motor using FOC.
I'm controlling via PPM mapped into duty cycle. It's a small motor (max 300W) with KV=380.
The first problem is that giving 0.050 ms increments in the ppm (in a range 1-2ms ie steps of 5% of the total range) it happens that the motor stops completely as in the following figure.
Hi,
I see the maximum Switching Frequency I can set is 150k, but can it really work at that frequency the driver?
My goal is to run at 68k, can I test it without problem? I'm using a relatively small motor (max 15A @24V) for multicopters.
Hi,
I'm in the process of writing a mode feature and need to hook a button up.
Since I want my firmware to be compatible with all app (PPM, ADC...), mapping change across the mode selected.
I also use ADC3 for external temperature monitoring (and cutoff if too high).
Based on FW3.40, I obtain this mapping table :
Hi All, recently I have replaced the original ESC in my Evolve Gen2 Carbon board with a VESC. The performance increase is enormous, much of which I attribute to a higher motor current setting than perhaps the original controller was using. I also guess that Evolve did not use current-control, but rather some kind of hybrid duty control.
Hi all,
i build a custom VESC Board and stripped down a few functions. Now i want to use the D2 Pin as FAULT Input (PB7 originally)
I found the #define in the hw_xx.h file to define the FAULT pin, but how can i disable the nrf part ? Just comment out the nrf part in the hw_xx.h file ?
Thanks in advance
Georg
