Robotics
h1. QtonPi Robotics Group
Aim
The aim of this robotics group is to utilize the Raspberry Pi hardware and the Qt software to create innovative and useful robotics and automation applications that can benefit the community and accelerate the adaption of Qt and Raspberry Pi in real world applications.
Projects
Below are the candidate projects that will receive the Raspberry Pi, this list might change in the future:
- Monitoring I/O real-time robot's system by "Jorge Acosta":http://wiki.qt.io/User:Jgeact
- Mill Machine by "Enrico Miglino":http://wiki.qt.io/User:Alicemirror
- Kiosk-like interface for user interaction and GPIO interfacing by "Nicholas Kell":http://wiki.qt.io/User:Monkeyknight
- Robot controlling and monitoring device using touchscreen interface by "Carver Deacon":http://wiki.qt.io/User:Carverdeacon
- Arduino IDE for Raspberry Pi by "Ujwal Shrestha":http://wiki.qt.io/User:Ujwal2
- Qt-ROS port by "Fredb52":http://wiki.qt.io/User:Fredb52
- Flying Robot by "Tuomas Kulve":http://wiki.qt.io/User:Kulve
- Monte Carlo Localization (Particle Filter) by "Patricia González":http://wiki.qt.io/User:Clandestinahds
- Humanoid Robot Control by "Miguel Landa":http://wiki.qt.io/User:Eroland
- Autonomous assistive robotic interface system by "Tarek Taha":http://wiki.qt.io/User:blackcoder
- Fuzzy controller for water level and flow control by "Samim Konjicija":http://wiki.qt.io/User:Samimk
- Light-weight front-end interface for an anthropomorphic flute playing robot by "Klaus Petersen":http://wiki.qt.io/User:Trilion99
- Ground Control Station application for Autonomous Rove by "Rosia Nicolae":http://wiki.qt.io/User:Rosia.nicolae
- Portable Robot Controller by "Nicola Corna":http://wiki.qt.io/User:Korna
- Home Service Robot by "Lee Sangdon":http://wiki.qt.io/User:Qqsunqq
- IMU Hardware Expansion board by "Rkekki":http://wiki.qt.io/User:Rkekki
Components
Regardless of the nature of the robotics application targeted by the above projects, certain components can be used among different projects to accelerate the progress and to avoid having to "re-invent the wheel". Below are few suggested components that can be used among the projects.
I/O Interfacing
This involves using the GPIO port on the Raspberry Pi to interface with electronic circuitry in order to read or write digital or analog data.
Sensors Interfacing
Interfacing the Raspberry Pi with various sensors similar but not limited to:
- - Sonars
- - Lasers (range finders)
- - IMU units (Inertial Measurement Units)
- - GPS
- - Acceleration
- - Gyroscopes
- - Digital compasses
- - Temperature sensors
- - Encoders
- - Cameras
- - Microphones
Arduino Interfacing
The flexibility and power of the Raspberry Pi board can be increased by interfacing it with Arduino boards and shields. This interface can be used using USB/Serial ports or via the "Ethernet":http://arduino.cc/en/Main/ArduinoEthernetShield or "Wireless":http://arduino.cc/en/Main/ArduinoWirelessShield shields.
Motor Controllers
Majority of robotics application involve moving and controlling various motors and stages. Time can be saved if motor control components can be shared across projects. This include feedback software algorithms (PID, Fuzzy logic control …) and hardware components like motor drivers and boards.
Software Components
Software components used to control certain aspects of the robots or provide intelligence can also developed in collaboration. Priority should be given to port well known robotic platforms like "PlayerStage":http://playerstage.sourceforge.net/ and "ROS":http://www.ros.org/wiki/ to Raspberry PI to allow the usage of well developed and maintained algorithmic solutions by worldwide robotic researchers and developers.