SHOP News & Articles Contact Impressum

DINGO-D Quick Guide Tutorial

DINGO-D

This post is a quick and compact guide for working with the Dingo-D.

The Dingo-D (differential robot) is an indoor compact development platform of the Canadian manufacturer Clearpath Robotics. ROS Noetic is pre-installed, so after receiving the robot the user can start developing algorithms right away.

DINGO-D Informative Links

Quick Start

The robot is turned on via the power button, and the start-up of the Dingo-D may take up to a minute to start.

Depending on the configuration of the Dingo, auxiliary sensors software drivers such as LiDar may start with the robot but often do not run as disconnection or damage of the wire of the sensor can cause the robot to startup incorrectly.

When the Dingo has flashing yellow lights or white lights in the front and red lights in the back, it means that it has correctly, started up. At this moment, the controller can be used for movement. For software remote connection, the robot has to be accessed once to configure the WiFi 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.

Dingo-D 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 Dingo-D), in Ubuntu goto 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 192.168.132.1 (may differ from robot to robot) and the Netmask as 24.

network

Click save and restart your network. Next is to open up the dingo as shown, and 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.

ifconfig

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

ping 192.168.132.1

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

ssh -X administrator@192.168.132.2

The password is

clearpath

Dingo-D Screen Connection

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

DINGO-D PC

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

ifconfig

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.

ssh -X administrator@192.168.0.228

192.168.0.228 is just an example of this. IP is taken from the ifconfig.

clearpath

Network

This robot has an industrial-grade computer on board with the MCU port being on 192.168.131.1, and the Hokuyo Lidar port being on 192.168.132.1.

Device Network
Dingo 192.168.131.1
Hokuyo Lidar 192.168.132.1

Dingo-D Software

The Dingo-D drivers configured by MYBOTSHOP are located in the catkin_ws. In the src folder, the third_party contains the drivers for the Dingo-D and its Puma motors as well as any auxiliary sensors such as the Hokuyo Lidar.

For a configuration of auxiliary sensors, the following link provides useful information, especially for navigation. 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.

Start-up Job

The Dingo-D ordinarily utilizes Clearpath startup job unless otherwise specified. In case there is an issue with the robot not starting up. One can ssh into the Dingo and verify if the startup job is working correctly.

sudo service ros status

The red marker in the service indicates that the startup job has failed. Green indicates everything is working 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 ros restart

Hokuyo Lidar

The Lidar drivers are started via:

roslaunch urg_node  urg_lidar.launch

Debugging Controller

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

Dingo-D: Debugging

Dingo-D: Robot not starting

Common issues that prevent the Dingo-D from not starting or continuously restarting may be due to the following reasons:

  1. The Dingo MCU is not connected to the PC.
  2. The Dingo MCU is not connected to the correct Ethernet port.
  3. The main PC has not established a static connection to the MCU.

To resolve the issue of point 1 and point 2, please refer back to the main post.

Dingo-D: PC not connecting to MCU

In case the PC is unable to detect the MCU on startup, the robot may be stuck on a constant reboot cycle. To resolve this issue:

  1. Disconnect the main PC cable:

  1. Connect it with a 12V, 5A power supply.

  1. At this stage you can directly connect to the PC using either the static connection or screen connection methods as described in the main post.

  2. Plug in an ethernet cable and make sure that the port is detected either through the GUI, of through ifconfig. If the port connection is not static, you can follow this guide.

  3. While the main PC is connected to the power supply, connect the MCU’s ethernet to the main PC and power on the Dingo-D to verify it is starting correctly.

  4. If it turns on then re-plug the main PC to the Dingo-D and you should be good to go.

dingo-compress

  • If the ethernet port is not visible, it means that there is an issue with Network manager. As the network manager is actually an Ubuntu issue and is commonly caused by the user, we can provide a general direction on what to look for to get it back running:

I. Reinstalling the network manager.
II. Ensuring the /etc/NetworkManager/NetworkManager.conf has managed=true
III. Replacing the /etc/network/interfaces with the default configuration.
IV. Missing port configuration

sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
sudo systemctl restart NetworkManager

Once the static connection is established then the provided ROS packages should interface with the drivers. Be sure to reconnect the LiDar once connected to the WiFi and check the LiDar with rviz.

Footer With Address And Phones