You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The robot needs more than a single PixhawkInstruction to change its motion. On the actual codebase, we publish PixhawkInstructions continuously because the controller publishes state messages continuously.
To get bootcamp solutions working on the robot, I had to change their publishing functions to publish multiple (5-10) messages, sleeping in between. Doing that on the GUI thread freezes cam streams (not good). Doing that in a separate thread with Python (stackoverflow; don't use thread.join) doesn't freeze anything, but doesn't match how we do it in prod (okay).
Either use that threaded solution or figure out a different one that allows for continuous publishing.
The text was updated successfully, but these errors were encountered:
The robot needs more than a single
PixhawkInstruction
to change its motion. On the actual codebase, we publishPixhawkInstructions
continuously because the controller publishes state messages continuously.To get bootcamp solutions working on the robot, I had to change their publishing functions to publish multiple (5-10) messages, sleeping in between. Doing that on the GUI thread freezes cam streams (not good). Doing that in a separate thread with Python (stackoverflow; don't use
thread.join
) doesn't freeze anything, but doesn't match how we do it in prod (okay).Either use that threaded solution or figure out a different one that allows for continuous publishing.
The text was updated successfully, but these errors were encountered: