Closed GoogleCodeExporter closed 8 years ago
This is needed in order to control which safeties in RT Ops are or aren't
enabled. Therefore, it is being moved to high priority.
Original comment by jrvanwhy
on 7 Sep 2012 at 3:37
I'll be adding a new message type instead, so we can separate out failures
(missing sensors/erroneous readings) from configuration (1 leg? 2 legs?).
Original comment by jrvanwhy
on 7 Sep 2012 at 6:35
Original comment by jrvanwhy
on 7 Sep 2012 at 10:08
Michael had a really good idea -- put all safety enable/disable choices into
the GUI. I'm currently reporting the robot's configuration in a basic way --
we'll see how we can improve it as we use it. I'll go ahead and add in the
automatic safety configuration into RT Ops, and we'll switch it over to GUI
control when the GUI gains the necessary capabilities w/ the rewrite.
Original comment by jrvanwhy
on 10 Sep 2012 at 3:02
Original comment by jrvanwhy
on 10 Sep 2012 at 3:40
Original issue reported on code.google.com by
jrvanwhy
on 5 Sep 2012 at 8:27