LURCH - The autonomous wheelchair

From AIRWiki
Revision as of 12:34, 21 September 2009 by MatteoRossi (Talk | contribs) (Electronics development)

Jump to: navigation, search
LURCH in DEI exploration

L.U.R.C.H. is the acronym of "Let Unleashed Robots Crawl the House".

LURCH is an extended version of an commercial electric wheelchair (Rabbit by OttoBock) equipped with:

  1. An interface circuit for digital drive via a radio serial link (XBee modules)
  2. Two on-board computers (PCBricks), powered by wheelchair batteries
  3. A 7-inch touchscreen monitor (Xenarc 700TSV), 800x480 resolution (16:10 AR)
  4. Two laser scanners Hokuyo URG 04LX
  5. A colour camera FireI400 (resolution 640×480)
  6. An odometry system based on encoders applied to the rear wheels

Main goals of the LURCH project are:

  1. Add sensors and robotic functionalities to the powered wheelchair.
  2. Add various command interfaces, such as Joypad wireless, speech command, brain-computer interface.
  3. Semi-autonomous navigation with collision and obstacle avoidance.
  4. Autonomous navigation by path planning and localization.

Functions currently provided by LURCH:

  1. Driving by the original joystick or a Logitech RumblePad2 wireless joypad.
  2. Obstacle sensing using planar scanner lasers.
  3. Basic collision and obstacle avoidance behaviours.
  4. Indoor localization by a fiducial marker system
  5. Path planning and basic autonomous navigation.
  6. Brain-computer interface driving system

Media Coverage

Lurch project appeared in many national and international media. You can see the related articles and videos in the MediaCoverage page.

Available Documentation

- Documentation on the interface circuit between the wheelchair joystick and computer: Media:LurchCircuitDocument.pdf.

- WARNING: the circuit was modified and the documentation above is upgraded by this new file: Media:LurchXBee.pdf.

- How to modify the wheelchair joystick to connect to the interface circuit: Media:LurchCircuitJoystick.pdf.

- Brief discussion about the interface circuit between the wheelchair joystick and computer: Media:LurchCircuitJoystickBrief.pdf.

- Brief description of the LURCH project: Media:LurchBriefDesc.pdf.

- Brief description of the communication between the wheelchair interface circuit and a PC via RS232 port: Media:LurchProtocol.pdf.

- Source code for PIC 18F452 microprocessor and Eagle project (schematic and board): Media:LurchCircuitProject.zip.

- Battery replacement done on May 2009, description of work: Media:LurchBatteryReplacement.pdf.

- Thesis by Simone Ceriani, titled Sviluppo di una carrozzina autonoma d'ausilio ai disabili motori (Development of an autonomous wheelchair to help motor-disabled persons): Media:LurchThesisCeriani.pdf (in Italian)

- Thesis presentation by Simone Ceriani (note: Videos don't work, you can found similar videos below): Media:LurchPresentazioneThesisCeriani.zip

- Thesis by Marco Dalli, titled Sviluppo di un sistema di controllo basato su odometria per una carrozzina robotica (Development of a control system based on odometry for a robotic wheelchair): Media:LurchThesisDalli.pdf (in Italian)

- Thesis presentation by Marco Dalli: Media:LurchPresentazioneThesisDalli.zip

- Pdf with ArtoolKitPlus Fiducial Markers collection. Dimension are 160x160mm. Media:ArtoolKitPlusMarkers-160mm.pdf.zip

PCBricks Configuration

PCBrick-03 and PCBrick-05 feature Xubuntu Linux 7.10, Xfce Window Manager, Openchrome graphics drivers and eGalax touchscreen drivers v1.08.1227 (Drivers here). The touchscreen is configured and calibrated on both machines, hence it can be used with either one or the other indifferently.

Electronics development

We are currently designing a new electronic main board for the wheelchair. The idea is to base the whole system on a CAN bus, allowing a complete modularization of the on-board electronics.

We are now evaluating the CANOpen standard, that provides high-level communication layers by implementing the ISO/OSI stack over the CANbus.

One of the modules that will be connected to the CAN bus is the USB mouse. For development and debug purposes, a simple master/slave system has been put together using two PIC18F4550 microcontrollers

Master/slave prototype board. The LCD (managed by the master PIC) is showing symbols indicating the successful connection to the USB host and the correct initialization of the serial port.

The USB mouse is emulated by a PIC18F4550 microcontroller; this unit features an on-board USB module that can be controlled by the HID (Human Interface Device) Library provided with the mikroC PRO for PIC compiler.

The USB HID Class Definition states that the device must provide the host a descriptor in which it informs the lattest on which kind of informations it will generate.

The Device Descriptor identifies which other class descriptors are present, and indicates their size (for example, Report and Physical descriptors).

A Report Descriptor describes each piece of data that the device generates, and what the data is actually measuring;

A Physical Descriptor (optional) provides information about the part(s) of the human body used to operate the device.


An appropriate USB mouse descriptor was generated using the HID Descriptor Tool provided by the USB organization.

A simple circuit has been designed to test the mouse firmware:

Circuit for the USB mouse emulation firmware.

All the components have been placed on a small piece of perfboard to test the circuit on different computers and operating systems:

Prototype board for the USB mouse emulation firmware.

The mouse emulator was instantly recognized by all the operative systems we tested it on:

  • Microsoft Windows XP SP2
  • Microsoft Windows Vista
  • Ubuntu Linux 9.04
  • Mac OS X 10.5.8
The USB mouse emulator recognized by Windows XP.
The USB mouse emulator recognized by Ubuntu Linux.
The USB mouse emulator recognized by Max OS X.
The USB mouse emulator managed by Parallels Desktop on Mac OS X while virtualizing Windows XP.

LURCH YouTube Videos

Software Installation [TODO: complete]

This guide is tested on Ubuntu 8.10, 9.04 and Xubuntu 8.10. GCC version in 4.3.

  • Install the following packages:
    • qt3-dev-tools
    • qt4-dev-tools
    • build-essential
    • flex
    • bison
    • libjsw-dev
    • libboost-dev
    • libdc1394-13-dev
    • libgsl0-dev
    • libgtk2.0-dev
    • libncurses5-dev

If you want you can cut and paste this command line: sudo apt-get install ...

  • Download this file: [TODO], which contains ARToolKitPlus Libraries
    • unpack it in /opt folder
    • go into /opt/ARToolKitPlus_2.1.1
    • export ARTKP=/opt/ARToolKitPlus_2.1.1
    • qmake
    • make
    • sudo make install
  • download lurch-control.tar.gz
    • extract it in your home folder
    • make cleanall
    • make ROBOT=wheelchair MODULE=misc
    • make ROBOT=wheelchair
    • cd wheelchair
    • ln -s ../logExtract.sh ./
    • ln -s ../run.sh ./
  • download lurch-wheelchair-standalone.tar.gz
    • extract it in your home folder
    • go into lurch-wheelchair-standalone/config
    • edit config.ini
      • replace line with hostname=airlab-blackbox with hostname=<yourhostname>
    • edit agent.ini
      • find and replace all "airlab-blackbox" with <yourhostname>
  • download the server for simulation (you need sun-java6-jdk installed and Eclipse is suggested)

...

  • from lurch-wheelchair-standalone
    • sudo ./run.sh

People Involved

Andrea Bonarini

Matteo Matteucci

Davide Migliore

Giulio Fontana

Bernardo Dal Seno

Marco Dalli (ex-Tesista)

Simone Ceriani (Assegnista di ricerca)

Matteo Rossi (Tesista)

Marco Assini (Tesista)

Mauro Brenna (Tesista)

Laboratory work and risk analysis

Laboratory work for this project is mainly performed at AIRLab/Lambrate. It includes some mechanical work and electrical and electronic activity. Potentially risky activities are the following:

  • Use of mechanical tools. Standard safety measures described in Safety norms will be followed.
  • Use of soldering iron. Standard safety measures described in Safety norms will be followed.
  • Transportation of heavy loads (e.g. robots). Standard safety measures described in Safety norms will be followed.
  • Robot testing. Standard safety measures described in Safety norms will be followed.