-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/head and sensorring #593
Feature/head and sensorring #593
Conversation
tested on cob4-10: OK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor/questions
@@ -116,21 +116,22 @@ | |||
<arg name="robot" value="$(arg robot)"/> | |||
<arg name="component_name" value="torso"/> | |||
<arg name="can_device" value="can0"/> | |||
<arg name="cartesian_control" value="true"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you not just set the value to false
?
here and wherever it applies...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the default be kept in a single place.
# sensorring: | ||
# type: diagnostic_aggregator/GenericAnalyzer | ||
# path: Sensorring | ||
# contains: 'sensorring/driver' | ||
# contains: 'sensorring/' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why keep it commented?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cob4-1 doesn't (yet) have a working sensorring hardware
type: diagnostic_aggregator/GenericAnalyzer | ||
path: twist_mux | ||
contains: 'twist_mux' | ||
contains: 'base/' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happened to the twist_mux diagnostics?
doesn't this contains
pattern conflict with e.g. base/light?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
light on base is using light_base
namespace, so filtering works as expected
I put a note about the high load problem observed on real hardware caused by the |
extends #568