This quick start guide assumes you will be running mBlock, the software to program the robot, in a browser. You can also download and install mBlock locally on your computer through Windows. We have a different quick-start guide for that.

When you use mBlock in the browser, you must download and install mLink. mLink is necessary because it acts as a bridge between your web browser and the physical hardware of the mBot robot, bridging the gap between web-based software and physical hardware.

Step 1: Install mLink

<aside> ⚠️

Some school laptops are prevented from installing software. If so, you should contact the people in charge of your school’s IT to address this.

</aside>

Here, we will install the mLink for Windows. If you think this has already been done, you can skip to Step 2 and come back as needed.

A view of the installer running.

A view of the installer running.

If the driver is already installed, you might see the error above. You can select  before clicking  again to ensure the driver is installed.

If the driver is already installed, you might see the error above. You can select Uninstall before clicking Install again to ensure the driver is installed.

At the end of the installation process, a window will pop-up offering to install a driver. Click  to install the driver.

At the end of the installation process, a window will pop-up offering to install a driver. Click Install to install the driver.

A pop-up showing the driver is uninstalled. Do not forget to re-install the driver if you uninstall it.

A pop-up showing the driver is uninstalled. Do not forget to re-install the driver if you uninstall it.

image.png

image.png

This window indicates you have succesfully installed mLink. You can simply close it.

This window indicates you have succesfully installed mLink. You can simply close it.

Step 2: Resetting the firmware

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.