Closed gavanderhoorn closed 8 months ago
@ted-miller: could you address this now that you've merged #155?
In the absence of a ROS API for "FSU status" (#50), documentation is the next best thing, and #155 changed the default behaviour of MotoROS2.
Sure. Just gimme a few days to finish up some other tasks.
I removed PFL from the title of this issue. We haven't done any PFL testing on an HC. I'm concerned because PFL can not only limit robot motion, but also generate motion.
As evidenced by #155, the fact the FSU/PFL can interfere with trajectory execution by MotoROS2 is not obvious to users.
We have an open issue tracking this (#50), but that's not user-facing documentation.
We should add a section to the Known issues & limitations section instead.
Refer to #50 in the new section, to keep discussion centralised, but clarify FSU/PFL support in MotoROS2 in the text itself.