Target audience
We recommend this software upgrade for MiR robot users who have experienced the issues described in this release note and who wish to stay on SW 2.x.
If you decide to migrate to SW 3.x, you will, however, get both the fixes and the added benefits of SW 3.x.
If you have not upgraded from software 2.x to 3.x yet, MiR still provides help with your transition.
To help you seamlessly transition to MiR software 3.x and make the most of its benefits, we offer Upgrade Support Service. This service is designed to minimize site downtime and reduce the risk of unforeseen issues during the upgrade process. You will get assistance from our team of application engineers who have in-depth knowledge of the migration process. MiR Upgrade Support Service consists of two steps: Step 1 is a site assessment and recommendations from
MiR, and Step 2 is optional on-site support from MiR.
Until June 28 2024, we offer you Step 1 of the Upgrade Support Service for free when you buy and add new robot(s) to your MiR Fleet. This can help you decide the strategy of migration from software 2.x to 3.x. Contact your MiR representative for more information.
For more information on how to upgrade and migrate to software 3.x—see MiR Migration Guide 2.x to 3.x. You can find this guide on MiR Support Portal.
Description
This software upgrade resolves several issues regarding MiR products.
New features
- New SICK configuration file for MiR600 and MiR1350
The software includes a new SICK configuration file for MiR600 and MiR1350 robots that makes it easier to diagnose SICK related issues and have a more robust turn-speed logic. There are no software changes for the new hardware version.
Issues solved
- The license activation link for MiR Fleet led to a wrong domain not owned by MiR (MIRS-15145)
When trying to activate a license for a new MiR Fleet, the link to the activation page would lead to a domain that Mobile Industrial Robots no longer owned. This has been solved, and the link to the activation site for MiR Fleet is now correct.
- SICK configuration file for MiR250 Shelf Carrier and MiR250 hardware version 2.0 did not show the correct version (MIRS-15469)
Under System > Robot Setup > Download SICK configuration for current robot software version, the SICK configuration file for MiR250 Shelf Carrier and MiR250 hardware version 2.0 said 2.14.0. This was incorrect as MiR250 Shelf Carrier and MiR250 hardware version 2.0 are only supported from software 2.14.5. This has now been solved so the configuration file for MiR250 and MiR250 Shelf Carrier hardware version 2.0 says 2.14.5.
- Robots continued to drive after losing connection to the power board (MIRS-15514)
In rare cases, if the connection to the power board was lost for a longer period of time while the robot was driving, the robot would continue driving. The safety system of the robot was not affected by the issue, so robots would stop for obstacles. This would manifest itself in inaccurate driving patterns and failure to complete missions. This issue has now been solved.
- Laser scanners would not connect after upgrading to software 2.14.4 or rolling back to software 2.14.3 (MIRS-15490)
After upgrading to software 2.14.4 or rolling back to software 2.14.3, the laser scanners would not connect, and the robot could therefore not move. Restarting the robot would clear the error. This issue has now been solved.
- Power board fails to connect to light controller after upgrade (MIRS-15190)
In rare cases, the power board would fail to connect to the light controller and would instead report the errors 'Connecting to Light control', 'Firmware upgrade failed', and 'Missing: Firmware upgrade failed'. To clear the errors, the robot had to be shut down and the battery disconnected for at least 15 s before restarting the robot. This issue has now been solved.
|
Comments
0 comments
Please sign in to leave a comment.