Super interesting project and impressive engineering. It wasn't quite clear to me how he solved the problem with
> Their motors are designed for slow, dampened pans across a stage, not for tracking a jet moving at 300 knots. The mechanical and electronics latency is significant; if you simply tell the camera to “follow that plane,” by the time the motors react, the target has often moved out of the frame.
Is he able to move the motors faster than they are designed to be moved? Is this the __Control (PID + Feed-Forward Loop)__ fix?
I don't really buy this argument. What counts is angular motion as seen from the camera, not absolute speed.
In terms of angular speed, unless you have a helicopter flying super low, I doubt aircraft move significantly faster than a preacher or a teacher, which are the intended use case according to the article.
Yes! So I probably over-simplified a bit in the language there... it's not just the physical motors, but the control electronics and logic on the cam itself doing the interpolation of receive VISCA commands that reduce overall responsiveness. And that lack of responsiveness not just absolute speed that causes issues. I sort of lump that all into hardware limitations since it's not something I can directly configure.
> Their motors are designed for slow, dampened pans across a stage, not for tracking a jet moving at 300 knots. The mechanical and electronics latency is significant; if you simply tell the camera to “follow that plane,” by the time the motors react, the target has often moved out of the frame.
Is he able to move the motors faster than they are designed to be moved? Is this the __Control (PID + Feed-Forward Loop)__ fix?