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
When we tried naming commands with “s”, “p”, “m”, “ms”, “sh” and “switch”, we found that the pi was completely unable to connect with the servo board (“Connection refused”). When we tried “r”, “u” and “send_help”, though, it worked.
This is the name that the pi uses with direct_command.
The text was updated successfully, but these errors were encountered:
There's a lot of known weirdness with the servo board's command handling at the moment - for example #11 and #9 are similar and are likely related to this. I have some ideas (#7, #14) for what the root causes might be, but properly diagnosing and resolving this is something that would take a significant amount of time and is unlikely to get done before the end of this competition year; sorry! We'll try and take a look at this issue specifically in our meeting on Monday however.
When we tried naming commands with “s”, “p”, “m”, “ms”, “sh” and “switch”, we found that the pi was completely unable to connect with the servo board (“Connection refused”). When we tried “r”, “u” and “send_help”, though, it worked.
This is the name that the pi uses with direct_command.
The text was updated successfully, but these errors were encountered: