On Chrome OS, the online version of mBlock needs to be used. There is no version that can be downloaded and installed on Chrome OS. However, you must install the mLink extension to communicate between the mBot and the web app.
Here, we will install the mLink extension to Chrome. If you think this has already been done, you can skip to Step 2 and come back as needed.
mLink for Chromebook.Download next mLink for Chromebook.Add to Chrome.Add App.<aside> ⚠️
Some school laptops are prevented from installing extensions to Chrome. If so, the Chrome Webstore will show a message that the extension cannot be installed. You should contact the people in charge of your school’s IT to address this.
</aside>
In Chrome, you can check which extensions are installed by clicking the 3 dots in the upper right corner of the window, selecting Extensions, and then Manage Extensions.
Find the extensions installed on Chrome.
mLink should be listed as one of the installed extensions.
In this step, we will ensure the robot runs the default firmware. The box below explains why we do this. This step is optional if you are sure the default firmware is running on the robot. However, if you are not sure, we recommend working through this step to ensure the robot is running the correct firmware to run the example program.
<aside> ℹ️
When you upload a program to the mBot, it replaces the robot's original firmware—the built-in software that lets it communicate with the mBlock app and respond to live commands. If you want to switch back to Live Mode, you must restore the original firmware. The mBlock app calls this "updating the firmware"—even though it’s just reinstalling the original software. This step is necessary because the custom code you uploaded takes over the robot, blocking live commands and resetting (or "updating") the firmware, bringing back the ability to control the mBot in real-time.
</aside>