It's possible that when the driver starts, a controller may still be running from a previous session which is sending LCM commands which will cause the robot to stop (e.g. joint positions significantly distant from the current pose). We should add an option to the driver to refuse to pass commands to the robot if this condition is detected.
It's possible that when the driver starts, a controller may still be running from a previous session which is sending LCM commands which will cause the robot to stop (e.g. joint positions significantly distant from the current pose). We should add an option to the driver to refuse to pass commands to the robot if this condition is detected.