This is related to, but also a bit different from, the Force Feedback Flight Yoke project.
I fly gliders. For training purposes, my gliding club is trying to build a simulator with a mock 2-seater cockpit (similar to the ASK21 gliders that the club uses for instruction). There will be a cylindrical screen and 3 (or possibly more) projectors, the mock cockpit in the center.
To get a good feel for the controls, and the interaction between instructor and student, they will likely be built much like the actual controls in a glider - physically connected together between front and rear cockpit, and resulting in movements of either push rods (for elevator, aileron and airbrakes) or steel cable (rudder) - there are some instructive diagrams in the ASK21 maintenance manual. Of course, for a simulator cockpit, everything behind the cockpit can be immensely simplified into something that can be connected to a sensor (to report the control position to the simulator) and a motor (for offering some form of force feedback).
The ODrive of course offers both a position measurement (the ‘pll_pos’ value that can be read back) and the option to apply some suitable amount of force (depending on choice of motor, etc) by specifying the current to provide to the motor – if I understand correctly?
The suitability of this solution also depends a bit on the rates at which the position measurements can be read back from, and new force-feedback instructions can be issues to, an ODrive or two, but over USB I don’t believe that should be a huge problem.
Another thing is that it might be useful to have a different kind of calibration option, where the absolute position is relative not to an index pulse, but relative to the physical range of motion that is available – perhaps if it were possible to detect when there is resistance against a motor moving further in either direction, and allowing one of those limits to the range of movement to be used as a substitute “index” of sorts, to define position zero – and possibly even allow reporting the available range after calibration.
(As a small aside; only three of the controls really need force feedback - elevator, ailerons and rudder - so a variant of ODrive that offered three axes would have been useful, and possibly less expensive than buying 2 ODrives, which would also leave one channel ‘wasted’. I’m guessing a 3-channel version of ODrive could also be useful for any kind of 3-axis CNC or similar but I understand that ship has sailed ).