Released 2022-06-23
1.2.2 battery firmware update failing on robots docked to 110 V chargers
If you were using a 110 V version of MiR Charge 48V to initiate the 1.2.2 battery firmware update, the update could sometimes fail. This has now been solved so the firmware update is applied correctly regardless of which version of MiR Charge 48V you are using.
MiR100 and MiR200 robots stop charging or do not begin charging at charging stations
In rare cases, MiR100 and MiR200 robots could stop charging while at a charging station for no apparent reason, or the robots wouldn't begin charging once docked to a charging station. This has now been solved so the robots reliably charge when they are docked to charging stations.
Robots losing their location on the map randomly
Sometimes, MiR robots could incorrectly localize themselves on the map due to unsynchronized IMU data. This would cause the robot to report a localization error, and you had to manually help the robot localize itself again before it could continue its mission. This has now been solved for MiR250, MiR500, MiR600, MiR1000, and MiR1350 robots so they navigate maps more reliably.
Ethernet connection to robot computer failing
Sometimes, the Ethernet ports on the robot computer were not handled correctly, meaning that the robot would not finish starting up, or you were not able to connect to the robot interface. This has now been solved.
Maps losing existing zones when being saved
In rare cases, when you saved changes to a map, it could result in some zones being deleted from the map. This could happen if a timeout in the browser caused there to be differences in the map data in the browser and the data in the database. This has now been solved by ensuring that the browser data can not affect the data on the MiR product’s database.
Aborting a mission in MiR Fleet causing MiR Fleet to stop sending missions to robots
Sometimes, if you aborted a mission from MiR Fleet, it could result in MiR Fleet entering a state where it could no longer send missions to robots. MiR Fleet had to be restarted before it could assign missions again. This has now been solved.
Removing a robot from MiR Fleet and then adding it again resulting in double metrics from the robot
If you removed a robot from MiR Fleet and then added it again shortly after, in some cases, MiR Fleet could record data twice from the robot, resulting in double data in the metrics from MiR Fleet. This has now been solved.
MiR100 and MiR200 robots with deprecated batteries starting up with error messages regarding a skipped firmware update
Sometimes, when you started up a MiR100 or MiR200 robot with a deprecated battery that had a state of charge outside of 45–95%, the robot would report that it has skipped a firmware update due to missing CAN communication to the battery, even though there was a connection and the firmware had already been updated. This has now been solved so the misleading errors are no longer reported at start-up.
Switching to or from Improved WiFi settings disconnecting the robot from WiFi
Sometimes, when you switched between the default and improved WiFi settings, the robot’s WiFi module would stop working and the robot could no longer connect to a WiFi network until it was restarted. This has now been solved.
Robots missing all Hardware health diagnostics and displays unstable driving behavior
Under System > Settings > WiFi, if you enabled one of the watchdogs and set an invalid IP address, the robot would sometimes continue to operate without checking if the IP address was valid. This would cause a delay in other diagnostics while the robot waited for a response from the invalid IP. When this happened, under Hardware health, many of the diagnostics would be missing and the delayed responses could also affect the robot’s driving behavior. This has now been solved.
MiR robots can enter Limit-robots zones to wait for a resource, provided the limit is not reached
If a robot is waiting in queue for a resource inside a Limit-robots zone, the robot used to wait outside the zone until the resource became available. Now, waiting robots can enter the zone, provided that any robots already ahead in the queue for the resource are already inside the zone and the zone’s limit is not exceeded.
MiR robots generate error logs if an auto charging mission fails
If a MiR robot is sent to charge at a charging station automatically and for some reason fails to start charging, it now generates an error log.