Working on the Brick

First login

After you established a connection to the EV3 you can manually initiate a ssh session. Therefore, take a look at the bricks upper left screen where you can find the IP address and run the following command:

ssh robot@<Brick IP>

The user “robot” is already created for you and “maker” is the initial password.
The first time you log into the brick you will be forced to change the default password and set your groups ID:

ssh robot@<Brick IP>

Hello, it's your first login or you have not changed your password yet!
Please change the default password now!

Changing password for robot.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully

You also need to set your group ID for this brick if not already done.
Please enter your group ID (e.g. 001):

Don’t worry if you have entered a typo for your password. The message will show up again on the next login.


With Great Power Comes Great Responsibility
As you are the robot’s master for the next days, the user account has been equipped with sudo permissions for some commands.
Invoking a command with the prefix sudo unleashes them. Make sure you know what you’re doing from this point on.

Optional: SSH Public Key


This section is entirely optional. Chances are you won’t ever need this during RoboLab as you are using the deploy-script.


For this to work, has to be run at least once.

If you are using our Deploy-Script a SSH key pair has been generated and installed for you. Using the key you can connect to the Brick without being asked for a password again. It is stored in your project directory under robolab-deploy/.bin/brick_id_rsa.

ssh -i your/path/robolab-deploy/.bin/brick_id_rsa robot@<Brick IP>

To add it to your SSH agent simply run this in your console:

ssh-add your/path/robolab-deploy/.bin/brick_id_rsa

Important for Windows:
By now, this step does not work out-of-the-box in GitBash/Win-CMD environments!
You need a ssh-agent running (e.g. Putty-Agent) and some manual tweaking.
Please see the following Tutorial for manual configuration and/or the FAQ for Gitbash.