Today I checked voltages just to understand what might be wrong in the setup. As the motor looks good AND works in the "diagnose" area when I apply the duty cycle (,20-0,50 tested) just as it should and smooth (,35A at 29V with no load). Current works as well, just the RPM function does not produce a movement but rattles. With the cursor keys the motor does nothing but consuming power, so I didn't fiddle around with them, as I do not know what they should do.
I'm using the "Current noReverse Brake ADC2" setting, which I understand to apply a voltage at ADC1 (in my case a HALL throttle with 0,9V-3.3V output) and have the ADC2 with my brakes connected (low active)
When I'm in the Input Wizard and chose the "Current noReverse Brake ADC2" setting for ADC the ADC1 jumps to 1,34V with no input connected. With a 22k PullDown resistor the voltage sinks to 1,22V. This does sound wrong at start. As I have two identical VESCs I tested the second one with the same app settings and it behaves the same. In addition the ADC1+2 is directly connected to the STM32 so no possible wrongdoing (PCB) here. When I connect the throttle the startup/running problems occur but the motor does not start until it reaches 2,3V.
What am I doing wrong?
Is maybe my Firmware (3.40) incompatible to my Hardware (4.10) as I could not explain the biased voltage (1,34V) at startup with fitting setup values from the right firmware.
Hope someone can explain the (for me) strange ADC1+2 bias. It might be the key to my stuttering of my BLDC.