@runger Trying not to threadjack from the C3 support thread since my problem seems to be more involved.
I’m trying to follow the different threads of the conversation
The communications breaking down would seem to be unrelated to SimpleFOC if it also happens with other sketches? Then I would treat that issue seperately from the motor related problems…
you seem to have a number of different issues… the weirdest one to me is the two second thunk that occurs independently of speed. Do you run the WiFi on the C3?
I should mention that you’ve chosen a really hard combination to run:
stepper with 50PP requires high accuracy sensors, and high speed MCU to run the commutation
AS5600 is very slow due to I2C and isn’t very accurate compared to other solutions
L298N is a very old and slow switching driver, which you generally can’t run at high PWM frequencies, and has trouble outputting high resolution PWM (when the duty cycles are very high or low it can’t switch fast enough)
So doing this combination as your first test of SimpleFOC is not recommended…
I am not actively using the wifi on the C3 and have not done anything to it. Maybe it’s trying to connect in the background by default? Would it do that if not commanded by the sketch?
Thank you for the critique of my hardware; I’ll go back to the drawing-board and get MCUs, motors, drivers, and encoders better suited for FOC purposes. My application will be low speed and relatively high torque, which is why I thought steppers would be well-suited. I won’t need particularly high accuracy for my application, I don’t think. I do want the MCU/driver/encoder package to be as small as possible, though, ideally fitting into the same footprint as the motor.