Is Arduino fast enough to monitor and control stepper motor as a closed loop control system?
The Arduino will use a magnetic angle sensor (such as TLE5012B) and will fix the requested motor position using this sensor and a stepper motor control driver (The stepper motor driver isn't chosen yet.).
How can I evaluate the responsive time from getting the angle information from the magnetic sensor till sending commands to the motor driver?
Yes.
Hundreds (thousands?) of 3D printers and small CNC mills use Atmega microprocessors to control 3 or 4 stepper motors.
Why is there a need for a closed loop system? All of those 3D printers work very well without it.
...R
Robin2, in 3D printer there could be a layer shift - 3D Printer Troubleshooting Guide: Layer Shift - YouTube
But anyway, my motor should drive an element that will be under a lot of external forces such as friction strong wind and etc.
itaycarpis:
Robin2, in 3D printer there could be a layer shift
That can happen, but it is not common.
But anyway, my motor should drive an element that will be under a lot of external forces such as friction strong wind and etc.
The correct solution is to choose a motor with sufficient torque to deal with those loads. If the motor does not have enough torque then knowing that it has lost position will not help it to regain position in the face of an excessive load.
There are drivers available (Trinamic?) that can sense a step failure and if you really need to have feedback that might be a better option with less computation load on the Arduino compared with an encoder.
...R
itaycarpis:
Is Arduino fast enough to monitor and control stepper motor as a closed loop control system?The Arduino will use a magnetic angle sensor (such as TLE5012B) and will fix the requested motor position using this sensor and a stepper motor control driver (The stepper motor driver isn't chosen yet.).
How can I evaluate the responsive time from getting the angle information from the magnetic sensor till sending commands to the motor driver?
Well the TLE5012B seems to support 8MHz SPI, so a few microseconds for that, and the latency for
talking to a stepper driver depends a bit on the library used and how you ramp and smooth step rates,
but that's more like milliseconds. And the time it takes the motor's rotor to move is also measured in
milliseconds typically.
With 16 million instructions per second, the motor and the scheme for generating steps is the bottleneck
on even a lowly Uno.
Note that if a stepper skips, its not likely to recover till the load is reduced, whatever you try to
do in software.