Regbot: Difference between revisions
No edit summary |
|||
Line 30: | Line 30: | ||
http://aut.elektro.dtu.dk/staff/jca/regbot/regbot.exe | http://aut.elektro.dtu.dk/staff/jca/regbot/regbot.exe | ||
====Before windows 10==== | |||
A USB driver must be installed to get in contact with the robot - see [[installation in windows]] - should be OK in Windows 10 | A USB driver must be installed to get in contact with the robot - see [[installation in windows]] - should be OK in Windows 10 | ||
The driver will (on Windows) create a | The driver will (on Windows) create a COM-port when connected - most likely com3 or any higher number. | ||
When the robot is disconnected by unplugging the cable, then the client may need to be restarted if it was connected when the cable was unplugged (no connection detect in windows). | When the robot is disconnected by unplugging the cable, then the client may need to be restarted if it was connected when the cable was unplugged (no connection detect in windows). | ||
Revision as of 09:53, 5 December 2016
REGBOT is a small robot designed for exercises for our linear control course (PID control) (author).
Introduction
Design overview can be found here.
User interface with configuration using the client, and how to write a mission.
REGBOT comes in 4 versions:
- version 1A - with robot numbers 1..15 (to be upgraded to version 3)
- version 2B - with robot numbers 16..52
- version 2.9 - last prototype before version 3
- REGBOT version 3 - first version 3 prototype
Video presentation https://www.youtube.com/watch?v=mOz4eNkjTM0
Use software as is
To use regbot two software parts are needed - one for the robot (regbot.hex) and the client (regbot.exe (for windows)).
Client software
Get the client software (regbot.exe) from file sharing on campusnet, place it in a directory, this directory will be default for configuration file and result files from the robot.
Get the client software here (as of 4/12/2016) http://aut.elektro.dtu.dk/staff/jca/regbot/regbot.exe
Before windows 10
A USB driver must be installed to get in contact with the robot - see installation in windows - should be OK in Windows 10
The driver will (on Windows) create a COM-port when connected - most likely com3 or any higher number. When the robot is disconnected by unplugging the cable, then the client may need to be restarted if it was connected when the cable was unplugged (no connection detect in windows).
Software download
The source code for the robot and the client is available here. NB! the software source can not be compiled without the proper tool-chain (compiler and library for the robot and python and libraries for the client)
repository for software - client and robot (version 3)
- client: svn://repos.gbar.dtu.dk/jcan/regbot/qtgui
- A windows executable version in the "dist" of "qtgui" (updated 4/12 2016)
- robot: svn://repos.gbar.dtu.dk/jcan/regbot/regbot
On a Linux computer do something like this:
svn co svn://repos.gbar.dtu.dk/jcan/regbot/regbot . svn co svn://repos.gbar.dtu.dk/jcan/regbot/qtgui .
- Robot software (including regbot.hex): version 3.500 (as of 4 December 2016) - more complete - but missing a few items related to access from raspberry pi, and added first version of software for robobot).
- Robot software (including regbot.hex): version 3.484 (as of 15 November 2016) - modular control implement done, new mission elements and servo control, adaption for hardware version 3 incl wifi and battery shutdown control.
- Robot software (including regbot.hex): version 3.371 (as of 9 August 2016) - changed to more modular control implement - not finished - use version 2 for demos
- Robot software (including regbot.hex): version 2.301 (as of 10 February 2016) - fixed error in disabling faulty velocity estimator.
- Robot software (including regbot.hex): version 2.290 (as of 5 February 2016) - fixed loss of ID if saved mission has more than a few lines.
- Robot software (including regbot.hex): version 2.285 (as of 31 January 2016) - ready for F16 course
- Client software : 3.484 (as of 15 November 2016) - adapted to hardware 3, modular control settings and wifi access
- Client software : 3.371 (as of 9 August 2016) - changed to more modular control implement - not finished - use version 2 for demos
- Client software : 2.290 (as of 5 February 2016) - fixed tilt offset error en saved configuration file (regbot.ini)
- Client software (including regbot.exe for windows): 2.285 (as of 31 January 2016) - ready for F16 course
Older version
repository for software - client and robot (version 2)
- client: svn://repos.gbar.dtu.dk/jcan/regbot/version2/qtgui
- robot: svn://repos.gbar.dtu.dk/jcan/regbot/version2/regbot
Install software tools
The software tools to modify the software requires some tools.
- Software installation and tool-chain - Linux
- installation in windows with some of the tool-chain
- Schematic
Extensions
Camera based line follower
This extension adds a Raspbery Pi with a Raspberry Pi camera on top of the robot. The Raspberry Pi is connected to the robot base through the UART serial connection.
The Camera based line follower detects a tape line in front of the robot and controls the robot to follow the line through the serial connection.
Go to Vision based Line Follower for detailed information on the project and instructions on how to setup a new Line Following RegBot.
ESP8266
This extension adds wireless communication to the robot through the Teensy's UART serial connection.
Go to ESP8266 for instructions on how to add the ESP8266 to the Teensy board.