[Quick Guide] Husky | Emlid RS2 | Phidgets

HUSKY-Emlid Reach RS2-Phidgets

This post is a quick and compact guide for working with Husky which uses an Nvidia Orin as the computing unit and Phidgets for orientation data.

Informative Links

Quick Start

Powering On

The robot is turned on via the power button, and the start-up of the Husky may take up to a minute to start. The green light indicates that the MCU has successfully started and connected to the onboard PC and is now able to receive commands from the onboard PC.

For software remote connection, the robot may be accessed via ethernet port.


Some quick useful commands in case there is an issue with the joystick is to ssh into the robot and teleoperated it via:

rosrun teleop_twist_keyboard teleop_twist_keyboard.py


Network configuration for the robot is.

Device Network Password
Main PC clearpath
Emlid-Reach -

Robot Interface

For software remote connection, the robot has to be accessed once to configure the WiFi network. This network configuration can take place in one of two methods, the first being via the static network connection and the second being through the screen, where the screen method is much quicker and easier for clients to set up.

Static Network Connection

For the first time, one needs to connect through a LAN cable to configure the robot’s WLAN network.

To create a static connection in your own PC (not the Husky), in Ubuntu go to Settings → Network then click on + and create a new connection.

  1. The first task is to go to IPv4 and change the connection to manual.

  2. The second task is to put the Address IP as (may differ from robot to robot) and the Netmask as 24.


Click save and restart your network. Next is to connect the LAN cable to the robot. After a successful connection let’s check the host’s local IP by typing in the Host PC’s terminal.


This should show the host IP which was assigned in the above step. Now its time to check if we can ping the robot or not, to do so type in your host pc


After a successful ping, it’s time to access the robot. To access the robot you can type the following command:

ssh -X administrator@

The password is


Screen Connection

An alternative for connecting to the Husky is by plugging in an HDMI cable as well as a mouse and keyboard. This will allow you to connect the Husky to your own local WiFi network and then you can connect later over the WiFi.

Husky PC

The procedure is simply to go to your networks and add your WiFi. Then in the terminal type:


The IP that comes with the initial characters of wl is your WiFi’s IP. e.g. wlps0. With this IP you can SSH to your robot via your host PC.

ssh -X administrator@ is just an example of this. IP is taken from the ifconfig.


Robot Software

The Husky drivers configured by MYBOTSHOP are located in the ros_ws. In the src folder, the third_party contains the drivers for the Husky.

As requirements vary from user to user, the setup has been left as default and the users can specify their own parameters in their own custom package. When connecting or ssh’ing to the robots pc, additional information regarding the robot will be displayed e.g.

 _  _  _  _  ____   __  ____  ____  _  _   __  ____   
( \/ )( \/ )(  _ \ /  \(_  _)/ ___)/ )( \ /  \(  _ \ 
/ \/ \ )  /  ) _ ((  O ) )(  \___ \) __ ((  O )) __/ 
\_)(_/(__/  (____/ \__/ (__) (____/\_)(_/ \__/(__)   
Current PC: Husky 

Husky IP:
Pswd:       clearpath

Emlid IP:


Husky status:     sudo service mbs_husky status
Husky start:      sudo service mbs_husky start
Husky stop:       sudo service mbs_husky stop
Husky restart:    sudo service mbs_husky restart

View robot:       roslaunch mbs_husky_viz viz.launch


Start Driver:     roslaunch reach_rs_driver reach_rs.launch

View Data:        rostopic echo /emlid/fix

Robot Startup

The start-up job is available for the onboard pc. The startup job launches two main components:

  1. Husky base drivers
  2. Phidgets IMU driver

The launch file system_bringup.launch in the ros_ws package of mbs_husky_startup includes everything which is being launched at the startup.

The Husky ordinarily utilizes Clearpath startup job unless otherwise specified. In this robot, we have our own upstart job for the custom auxiliary drivers. In case there is an issue with the robot not starting up. One can ssh into the Husky and verify if the startup job is working correctly.

sudo service mbs_husky status

The red marker in the service indicates that the startup job has failed. Green indicates everything is operating correctly. Grey indicates that the service has not started yet. In case of red or grey marker, you may restart the service via:

sudo service mbs_husky restart

New launch files and nodes can be added to the startup job by inserting them into the system_bringup.launch launch file for PC startup. Once added Run the following in ros_ws.

rosrun mbs_husky_startup startup_installer.py

It should now run with the updated additions.

Emlid Reach RS2

To obtain data, the device needs to be outdoors where it can receive GPS signals. The data from Reach2 can be visualized by following these steps:

First, run the Emlid drivers using the following command:

roslaunch reach_rs_driver reach_rs.launch

Once the Emlid driver is running, open a new window and subscribe to the specified rostopic:

rostopic echo /emlid/fix

By following the above procedure, you will be able to view the data coming from Emlid Reach.

Phidgets IMU

The provided Husky has a phidgets IMU integrated into it. The parameters for odometry can be tuned in the folder ros_ws/src/mbs/mbs_control/config/wheel_localization_config.yaml.

It is recommended not to change the parameters without a backup and without expert supervision.


In case of any issues please first try restarting the service of the robot via:

sudo service mbs_husky restart

In case of questions please contact support@mybotshop.de. For issues related to the software please attach a ros bag e.g.

rosbag record -a