Target audience
We recommend this software upgrade for MiR robot users who have already migrated to SW 3.x and have experienced any of the issues described, or who want to migrate from SW 2.x to 3.x.
Description
This software upgrade includes cybersecurity improvements for MiR Fleet, a new feature that makes it possible to change the default path to store MiR Fleet logs and solved issues.
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 robots 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.
New features
- MiR Fleet now supports changing the location of the persistent storage (MIRS-15093)
You can now change where MiR Fleet stores its persistent storage using the fleet_config file outside the mir_persistence folder. By default MiR Fleet uses the path /mir_persistence for storage.
-
- In case of a clean install, it is possible to change the default path by editing the fleet_config file that is shipped together with the installer.
- In case of updating the default path of an existing MiR Fleet, it is possible to do it by editing the fleet_config file located in the /mir_fleet_config folder.
Updating the default path of an existing MiR Fleet can be a destructive operation. We recommend only doing this during a clean install of the system.
Cybersecurity improvements
- Updated and patched operating systems and software packages across all MiR Fleet containers (PSEC-584, PSEC-518, PSEC-443)
Operating systems and software packages have been updated and patched across all MiR Fleet containers. This includes security patches for over 200 software packages.
Issues solved
- Battery firmware update was applied without warning and could cause battery issues (MIRS-15622)
The 1.2.2 firmware update of 48V batteries could in rare cases be unintentionally triggered on the robots whose batteries run firmware version 1.1.10 or lower. This could cause the battery to permanently shut down.
- Mission with pick and place cart variables were not included (NEX-3881)
Sometimes, if you created a mission with pick up cart and place cart as variables, created a dashboard with a mission button and then set this to the mission with pick and place variables, the positions were missing. This meant that you were sometimes not able to run missions that included cart variables as intended.
|
Comments
0 comments
Article is closed for comments.