Released 2021-12-22
Joystick control on MiR100 and MiR200 inoperable at charging stations
If you tried to use the joystick to move a MiR100 or MiR200 robot that was charging at a charging station, the robot would enter Manual mode, but could not be driven from the charging station. This only occurred with robots that have replacement batteries installed and have a CAN bus connection to the battery. The issue has now been solved, so the robot stops charging and can be driven away safely.
Robots carrying full loads “wiggling” in place when arriving at positions
When a fully loaded robot reached a position, it could sometimes “wiggle” from side to side to adjust its position until it was within the allowed orientation tolerance. This has primarily been observed when robots moved to Entry positions for markers. The issue has now been solved by making sure the robot stops while it is within the allowed orientation tolerance.
This issue only affects 2.10.5 and 2.13 software versions and is also solved in the upcoming 2.10.5.x software release.
MiR100 and MiR200 taking longer time to undock from charging stations
Sometimes, when a MiR100 or MiR200 robot undocked from a charging station, it would take around 30 seconds longer to reverse from the charger. This has now been solved, so the robot undocks as expected.
This issue is also solved in upcoming 2.7.9.x, 2.8.3.x, and 2.10.5.x software releases.
MiR100 and MiR200 entering Error mode when undocking from a charging station
Sometimes, when a MiR100 or MIR200 robot undocked from a charging station, it would enter Error mode before finishing the undocking sequence and could report errors regarding a collision with the footprint or missing IMU data. This has now been solved so the robot undocks correctly.
This issue is also solved in upcoming 2.7.9.x, 2.8.3.x, and 2.10.5.x software releases.
MiR100 and MiR200 stop charging randomly at charging stations
Sometimes, when a MiR100 or MiR200 robot was charging at a charging station, it would stop charging for no apparent reason. This issue has now been solved.
This issue is also solved in upcoming 2.7.9.x, 2.8.3.x, and 2.10.5.x software releases.