The current code check the health of the sensor packet just before it is used. And if it is not valid, it raises exception, but it cause the system reset and lost connection to Roomba (or Create) for seconds. As the result, the robot can be out of control for that duration.
This PR is raise DriverError which the code just ignored the current sensor packet if the sensor information is invalid. I confirmed it works and ease the problem I reported on #39 .
The current code check the health of the sensor packet just before it is used. And if it is not valid, it raises exception, but it cause the system reset and lost connection to Roomba (or Create) for seconds. As the result, the robot can be out of control for that duration.
This PR is raise DriverError which the code just ignored the current sensor packet if the sensor information is invalid. I confirmed it works and ease the problem I reported on #39 .