/motor_x/feedback topic silent when Jeeves is started via upstart job
Also, sometimes this happens when we start manually. It appears the issue was that the MicroBasic script running on the motor controllers was stopping/crashing due to a USB state that it didn't like. Solution was to
1) Add a line to the roboteq_driver node in channel.cpp that sends a "re-initialize the script" command to the motor controllers, in addition to the existing "enable feedback" command that is part of the recovery behavior if feedback isn't coming out of the controller.
2) While I was at it, I updated the driver with a recent bugfix from upstream, and un-did the hack that I had to use on the MicroBasic script early-on in the project. The upstream fix made this possible.
Note: the roboteq/ directory in our repo is a /copy/ of the original upstream repo, not a clone. I /manually/ merged the change into our 'sort-of' fork.