Robobot

From Rsewiki
(Difference between revisions)
Jump to: navigation, search
(→‎REGBOT USB as SOCKET)
(→‎Overview)
 
(219 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
This page is for ROBOBOT, an extension of REGBOT with a raspberry pi and three wheels.
 
This page is for ROBOBOT, an extension of REGBOT with a raspberry pi and three wheels.
  
−
==Installation observations==
+
<!--[[File:onshape-view.png|400px]] -->
 +
[[File:robobot_v5.png|400px]]
 +
[[File:melina_b.jpg|250px]]
 +
[[File:model-black.jpg | 450px]]
  
−
===Raspicam===
+
Figure 1. Robobot, The robot is a 3D-printed box with wheels and some electronics.
 +
The third, fourth and fifth generations are shown here.
 +
The 3D printed parts can be found here https://cad.onshape.com/documents/fef8699fcafb8aea780c8981/w/ce38e7fdd6cf8533b65e2c3c/e/4792e876b254f8e35059f863
  
−
A rather short raspberry pi camera API is available from https://www.uco.es/investiga/grupos/ava/node/40.
+
== Overview ==
−
And can be downloaded from https://sourceforge.net/projects/raspicam/files/?
+
  
−
Unpack and install:
+
Note: Not valid (mostly) for the 2024 version of the robot
−
unzip raspicam-0.1.3.zip
+
−
cd raspicam-0.1.3
+
−
mkdir build
+
−
cd build
+
−
cmake ..
+
−
make
+
−
sudo make install
+
  
−
===Userland-master===
+
===hardware ===
  
−
To be able to install mobotware
 
  
−
Follow the guide under REGBOT for userland-master install
+
ROBOBOT is based on a navigation box with a line sensor (Edge sensor), an IR distance sensor and possibly some servos, all controlled by a microprocessor.
 +
For more intelligent behaviour and more sensors, there is a Raspberry Pi in the box too,
  
−
===DNSMASQ===
+
The motors are JGB37-555-EN with an encoder and a 1:10 gearing (up to about 400RPM (or ~6 RPS (rotations per second) on the output axle).
  
−
Install DNSMASQ
+
There is a video introduction and demo here https://www.youtube.com/watch?v=6dNr_F0dsHw (from 2022 - slight changes since)
  
−
sudo apt install dnsmasq
+
=== Navigation box overview===
  
−
allow dnsmasq to provide IP to pear-to-pear networks
 
−
Edit the /etc/dnsmasq.conf and change/add the following line (for eth0)
 
  
−
dhcp-range=eth0,192.168.0.100,192.168.0.150,12h
+
[[File:robobot-overview.png | 500px]]
  
−
To work, the eth0 must have an IP, if noone provides one,
+
Figure 2. ROBOBOT is an extension of the robot REGBOT. The REGBOT part controls the wheels and interfaces to the sensors, like an IMU (6-axis accelerometer and gyro), IR distance sensors (2), and a line edge detector. The REGBOT further controls up to 5 servos and controls the battery supply. ROBOBOT is further equipped with a Raspberry Pi to allow more complicated missions. The Raspberry Pi runs an interface process called "Bridge" and is the main interface to the REGBOT. The mission process collects data from the bridge and the REGBOT and supplies small mission code snippets to be executed by the REGBOT part. The mission process may use the camera and the Open-CV library functions. The speaker allows debugging messages or other sound effects.
−
change /etc/dhcpcd.conf (dhcp client deamon) to have a default IP, if no DHCP server is available
+
  
−
Add the following lines at the end of /etc/dhcpcd.conf
+
The ROBOBOT functions are available on the net at port number 24001. The existing user interface for REGBOT can access REGBOT functions from this port.
  
−
  # define static profile
+
The gamepad can take control of the robot if the mission fails and can be used to initiate missions or other functions.
−
  profile static_eth0
+
 
−
  static ip_address=192.168.0.2/24
+
==Software description==
−
  static routers=192.168.0.1
+
 
−
  static domain_name_servers=192.168.0.1
+
 
 +
=== Bridge software ===
 +
 
 +
The Robobot bridge runs on the Raspberry Pi and is started when the Raspberry Pi starts, with initial commands from an initialization file (bridge.ini).
 +
 
 +
[[Robobot_bridge]] overview
 +
 
 +
A bridge autostart feature is implemented in the script 'start_bridge.sh' in the home directory of the user 'local'.
 +
The is executed after a reboot.
 +
 
 +
The script can be amended with other commands that should be started after a reboot.
 +
 
 +
=== Mission software ===
 +
 
 +
The mission application is the primary user control for the robot.
 +
 
 +
[[Robobot mission]] application overview.
 +
 
 +
The Mission application is started manually from an ssh console or added to the reboot script 'start_bridge.sh'.
 +
<!--
 +
===Python interface===
 +
 
 +
A python-based control example - including especially camera streaming and interface.
 +
 
 +
[[Python interface]]
 +
-->
 +
 
 +
==Setup issues==
 +
 
 +
===Installation instructions===
 +
 
 +
This installation should be done already, to update see next section.
 +
 
 +
[[Raspberry and ROS]] (not finished)
 +
 
 +
[[Network setup]] (Wifi)
 +
 
 +
[[Robobot camera]] camera setup
 +
 
 +
[[Access from Windows]] and Linux to Raspberry files (and graphics)
 +
 
 +
[[Other windows tools]] - show Raspberry Pi graphics in Windows (usually very very slow)
 +
 
 +
[[Regbot GUI]] python setup and GUI install
 +
 
 +
See [[Regbot calibration]] for sensor calibration.
 +
 
 +
===Software update===
 +
 
 +
Update of the maintained software is on the SVN (subversion) repository.
 +
 
 +
SSH to the robot and go to these directories and do an update
 +
 
 +
  cd
 +
  svn up svn/fejemis/ROS/catkin_ws/src/bridge
 +
  svn up svn/robobot
 +
svn up svn/regbot
 +
 
 +
An update could look like this
 +
$ svn up svn/fejemis/ROS/catkin_ws/src/bridge
 +
Updating 'svn/fejemis/ROS/catkin_ws/src/bridge':
 +
U    fejemis/ROS/catkin_ws/src/bridge/udataitem.h
 +
U    fejemis/ROS/catkin_ws/src/bridge/ujoy.cpp
 +
Updated to revision 228.
 +
 
 +
NB! this may cause a conflict if some of the files are changed locally.
 +
Look at the filename and if it is not one of yours, then reply 'tc' (short for their conflict solution)
 +
 
 +
=====Compile on bridge changes=====
 +
 
 +
If there are updated files for the bridge, then
 +
 
 +
cd
 +
cd catkin_ws
 +
catkin_make
 +
 
 +
=====Compile and upload on Teensy changes=====
 +
 
 +
cd
 +
cd svn/regbot/regbot/4.1
 +
make -j3
 +
 
 +
This makes a file "regbot.hex" that is then to be loaded as the new firmware on the Teensy processor.
 +
 
 +
There is a script that can do that from the command line:
 +
 
 +
./upload.sh
 +
 
 +
It will say something like
 +
 
 +
$ ./upload.sh
 +
Teensy Loader, Command Line, Version 2.2
 +
Read "regbot.hex": 314368 bytes, 3.9% usage
 +
Waiting for Teensy device...
 +
  (hint: press the reset button)
 +
 
 +
Press and hold the "POWER ON" and then press the button on the Teensy board.
 +
 
 +
The "POWER ON" button maintains power to the Raspberry Pi and the Teensy while uploading.
 +
 
 +
It will likely fail the first time but keep pressing "POWER ON" and repeat the command, and it should now say
 +
 
 +
$ ./upload.sh
 +
  Teensy Loader, Command Line, Version 2.2
 +
Read "regbot.hex": 314368 bytes, 3.9% usage
 +
  Found HalfKay Bootloader
 +
Programming.............................
 +
Booting
 +
 
 +
If you released the "POWER ON" in the process, the Raspberry Pi would power down. You then need to hold the "POWER ON" until the Raspberry has booted; you then re-login and rerun the script.
 +
 
 +
=====Make the upload.sh=====
 +
 
 +
If you have the "upload.sh", this step is not needed.
 +
 
 +
The command line upload is described here https://www.pjrc.com/teensy/loader_cli.html .
 +
 
 +
On a Raspberry you first need to install a USB library:
 
   
 
   
−
  # fallback to static profile on eth0
+
  sudo apt install libusb-dev
−
interface eth0
+
 
−
fallback static_eth0
+
Then get the code:
−
+
−
# define static profile
+
−
profile static_eth1
+
−
static ip_address=192.168.1.2/24
+
−
static routers=192.168.1.1
+
−
#static domain_name_servers=192.168.0.1
+
 
   
 
   
−
  # fallback to static profile on eth1
+
  cd ~/git
−
  interface eth1
+
  git clone https://github.com/PaulStoffregen/teensy_loader_cli.git
−
  fallback static_eth1
+
  cd teensy_loader_cli
 +
make
  
−
This will also give a default IP for an eventual second network (usb-to-cable) if needed
+
You should now have a "teensy_loader_cli" file; copy this to the svn/regbot/regbot/4.1 directory
  
−
Now, after a reboot, you should be able to connect a PC directly with at network cable to a PC, and the PC should get an IP from the raspberry, so now
+
cp teensy_loader_cli ~/svn/regbot/regbot/4.1/
  
−
ssh local@192.168.0.2
+
Make the "upload.sh" script
  
−
should work
+
cd ~/svn/regbot/regbot/4.1
 +
nano upload.sh
  
−
===Mobotware===
+
Insert the following into the script:
  
−
Requires a number of packages - see [[Install on raspberry]]
+
#!/bin/bash
 +
./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex
  
−
===ROBOBOT demo C++===
+
Save with ctrl-s and exit with ctrl-x
  
−
This is an examplesoftware in C++ to access both raspberry camera and REGBOT, and with an example mission controlled from the raspberry.
+
Make the script executable
  
−
Get the robobot software from the svn repository:
+
chmod +x upload.sh
  
−
svn checkout svn://repos.gbar.dtu.dk/jcan/regbot/robobot robobot
+
== old instructions ==
  
−
To be able to compile the demo software CMAKE needs also to use the user installed library (raspicam installed above),
+
Partially valid only.
−
so add the following line to ~/.bashrc:
+
  
−
export CMAKE_PREFIX_PATH=/usr/local/lib
+
[[Install on raspberry]] on a clean SD-card - raspi-config.
  
−
Then build Makefiles and compile:
+
[[Setup user local]] adding a new user.
  
−
cd robobot
+
[[Linux tools]] - packages to install.
−
cd build
+
 
−
cmake ..
+
[[Access from PC]] (Linux or Windows).
−
make
+
  
−
Then testrun the application:
+
[[Other windows tools]] - run graphics from Windows
  
−
./robobot
+
[[Instructions for getting started]] - primarily network, Linux intro and wifi setup.
  
−
It should print that the camera is open, save an image and print some data from the robot (e.g. position).
+
<!-- [[Full installation instructions]] - like Linux itself, sound and camera and how to connect the Raspberry disk to Windows and Linux computers. -->
  
−
===USB as SOCKET for REGBOT client===
+
==REGBOT setup ==
  
−
To use the REGBOT client through (not on) the raspberry pi, the serial connection /dev/ttyACM0 on the raspberry can be converted to a network port by SOCAT. So install:
+
Several parameters in the REGBOT part of the robot need setting.
  
−
sudo apt install socat
+
Some suggestions are provided here using the REGBOT GUI (available on the raspberry in the 'regbotgui' directory, and in a Windows version):
  
−
Add the following line to /etc/rc.local
+
[[Regbot settings]]
  
−
socat TCP-LISTEN:24001,fork,reuseaddr FILE:/dev/ttyACM0,raw,echo=0
+
=== Hardware ===
  
−
This creates a TCP socket server, listening to port 24001 and piping /dev/ttyACM0 to the socket (with no local echo). This only takes the data from the /dev/ttyACM0 when a client is connected to the socket.
+
The Robobot frame is 3D printed, the design is in onshape - see this link https://cad.onshape.com/documents/fef8699fcafb8aea780c8981/w/ce38e7fdd6cf8533b65e2c3c/e/4792e876b254f8e35059f863 , in the list of parts to the left it is possible to export (right-click) as STL files, that you can slice for your 3D printer.
  
−
This is good for configuring the REGBOT (connect wifi 192.168.0.2:24001).
+
=== Navigation box assembly ===
  
−
Works after a reboot, or the same line on the command prompt.
+
There are video-instructions on the course page.

Latest revision as of 14:45, 31 May 2024

This page is for ROBOBOT, an extension of REGBOT with a raspberry pi and three wheels.

Robobot v5.png Melina b.jpg Model-black.jpg

Figure 1. Robobot, The robot is a 3D-printed box with wheels and some electronics. The third, fourth and fifth generations are shown here. The 3D printed parts can be found here https://cad.onshape.com/documents/fef8699fcafb8aea780c8981/w/ce38e7fdd6cf8533b65e2c3c/e/4792e876b254f8e35059f863

Contents

[edit] Overview

Note: Not valid (mostly) for the 2024 version of the robot

[edit] hardware

ROBOBOT is based on a navigation box with a line sensor (Edge sensor), an IR distance sensor and possibly some servos, all controlled by a microprocessor. For more intelligent behaviour and more sensors, there is a Raspberry Pi in the box too,

The motors are JGB37-555-EN with an encoder and a 1:10 gearing (up to about 400RPM (or ~6 RPS (rotations per second) on the output axle).

There is a video introduction and demo here https://www.youtube.com/watch?v=6dNr_F0dsHw (from 2022 - slight changes since)

[edit] Navigation box overview

Robobot-overview.png

Figure 2. ROBOBOT is an extension of the robot REGBOT. The REGBOT part controls the wheels and interfaces to the sensors, like an IMU (6-axis accelerometer and gyro), IR distance sensors (2), and a line edge detector. The REGBOT further controls up to 5 servos and controls the battery supply. ROBOBOT is further equipped with a Raspberry Pi to allow more complicated missions. The Raspberry Pi runs an interface process called "Bridge" and is the main interface to the REGBOT. The mission process collects data from the bridge and the REGBOT and supplies small mission code snippets to be executed by the REGBOT part. The mission process may use the camera and the Open-CV library functions. The speaker allows debugging messages or other sound effects.

The ROBOBOT functions are available on the net at port number 24001. The existing user interface for REGBOT can access REGBOT functions from this port.

The gamepad can take control of the robot if the mission fails and can be used to initiate missions or other functions.

[edit] Software description

[edit] Bridge software

The Robobot bridge runs on the Raspberry Pi and is started when the Raspberry Pi starts, with initial commands from an initialization file (bridge.ini).

Robobot_bridge overview

A bridge autostart feature is implemented in the script 'start_bridge.sh' in the home directory of the user 'local'. The is executed after a reboot.

The script can be amended with other commands that should be started after a reboot.

[edit] Mission software

The mission application is the primary user control for the robot.

Robobot mission application overview.

The Mission application is started manually from an ssh console or added to the reboot script 'start_bridge.sh'.

[edit] Setup issues

[edit] Installation instructions

This installation should be done already, to update see next section.

Raspberry and ROS (not finished)

Network setup (Wifi)

Robobot camera camera setup

Access from Windows and Linux to Raspberry files (and graphics)

Other windows tools - show Raspberry Pi graphics in Windows (usually very very slow)

Regbot GUI python setup and GUI install

See Regbot calibration for sensor calibration.

[edit] Software update

Update of the maintained software is on the SVN (subversion) repository.

SSH to the robot and go to these directories and do an update 

cd
svn up svn/fejemis/ROS/catkin_ws/src/bridge
svn up svn/robobot
svn up svn/regbot

An update could look like this 

$ svn up svn/fejemis/ROS/catkin_ws/src/bridge
Updating 'svn/fejemis/ROS/catkin_ws/src/bridge':
U    fejemis/ROS/catkin_ws/src/bridge/udataitem.h
U    fejemis/ROS/catkin_ws/src/bridge/ujoy.cpp
Updated to revision 228.

NB! this may cause a conflict if some of the files are changed locally. Look at the filename and if it is not one of yours, then reply 'tc' (short for their conflict solution)

[edit] Compile on bridge changes

If there are updated files for the bridge, then 

cd
cd catkin_ws
catkin_make
[edit] Compile and upload on Teensy changes
cd
cd svn/regbot/regbot/4.1
make -j3

This makes a file "regbot.hex" that is then to be loaded as the new firmware on the Teensy processor.

There is a script that can do that from the command line: 

./upload.sh

It will say something like 

$ ./upload.sh
Teensy Loader, Command Line, Version 2.2
Read "regbot.hex": 314368 bytes, 3.9% usage
Waiting for Teensy device...
 (hint: press the reset button)

Press and hold the "POWER ON" and then press the button on the Teensy board.

The "POWER ON" button maintains power to the Raspberry Pi and the Teensy while uploading.

It will likely fail the first time but keep pressing "POWER ON" and repeat the command, and it should now say 

$ ./upload.sh
Teensy Loader, Command Line, Version 2.2
Read "regbot.hex": 314368 bytes, 3.9% usage
Found HalfKay Bootloader
Programming.............................
Booting

If you released the "POWER ON" in the process, the Raspberry Pi would power down. You then need to hold the "POWER ON" until the Raspberry has booted; you then re-login and rerun the script.

[edit] Make the upload.sh

If you have the "upload.sh", this step is not needed.

The command line upload is described here https://www.pjrc.com/teensy/loader_cli.html .

On a Raspberry you first need to install a USB library: 

sudo apt install libusb-dev

Then get the code: 

cd ~/git
git clone https://github.com/PaulStoffregen/teensy_loader_cli.git
cd teensy_loader_cli
make

You should now have a "teensy_loader_cli" file; copy this to the svn/regbot/regbot/4.1 directory 

cp teensy_loader_cli ~/svn/regbot/regbot/4.1/

Make the "upload.sh" script 

cd ~/svn/regbot/regbot/4.1
nano upload.sh

Insert the following into the script: 

#!/bin/bash
./teensy_loader_cli -v -w --mcu=TEENSY41 regbot.hex

Save with ctrl-s and exit with ctrl-x

Make the script executable 

chmod +x upload.sh

[edit] old instructions

Partially valid only.

Install on raspberry on a clean SD-card - raspi-config.

Setup user local adding a new user.

Linux tools - packages to install.

Access from PC (Linux or Windows).

Other windows tools - run graphics from Windows

Instructions for getting started - primarily network, Linux intro and wifi setup.


[edit] REGBOT setup

Several parameters in the REGBOT part of the robot need setting.

Some suggestions are provided here using the REGBOT GUI (available on the raspberry in the 'regbotgui' directory, and in a Windows version):

Regbot settings

[edit] Hardware

The Robobot frame is 3D printed, the design is in onshape - see this link https://cad.onshape.com/documents/fef8699fcafb8aea780c8981/w/ce38e7fdd6cf8533b65e2c3c/e/4792e876b254f8e35059f863 , in the list of parts to the left it is possible to export (right-click) as STL files, that you can slice for your 3D printer.

[edit] Navigation box assembly

There are video-instructions on the course page.

Retrieved from "http://rsewiki.elektro.dtu.dk/index.php?title=Robobot&oldid=6921"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox