Flexbot

From Rsewiki
(Difference between revisions)
Jump to: navigation, search
(Current state of Flexbot)
Line 19: Line 19:
  
 
=Current state of Flexbot=
 
=Current state of Flexbot=
 +
This section presents a '''very''' short summary of the current state of Flexbot. When a new change (of relevance i.e. no minors) is made, please update this section by adding a new line on top of the existing.
 +
 +
* 23/07 2017: The mechanics from wheel to knee is finished. Electronics including external sensors have been mounted. Software supports basic functionality for interfacing, control, test and logging of each actuator (wheel, heading, height) and sensor.
  
 
=Software terminal interface=
 
=Software terminal interface=

Revision as of 09:39, 23 July 2017

Introduction

Hardware design overview and open items (to-do).

Mechanical design modification to do list - design change request list (please amend when you note a problem / and delete when solved)

Software to do list - change request and to do (please amend when you note a problem / and delete when solved)

Flexbot parts list (please note, when you know)

Documents, drawings and software (git repository)

Project plan notes

Importing model from OnShape being written.

Flexbot-rendered-115678 gi tonemapped reinhard05.png

Current state of Flexbot

This section presents a very short summary of the current state of Flexbot. When a new change (of relevance i.e. no minors) is made, please update this section by adding a new line on top of the existing.

  • 23/07 2017: The mechanics from wheel to knee is finished. Electronics including external sensors have been mounted. Software supports basic functionality for interfacing, control, test and logging of each actuator (wheel, heading, height) and sensor.

Software terminal interface

Each Teensy can be interfaced separately via USB communication. Simply plug in a USB cable, open a serial communication in Putty, Arduino or whatever you prefer and type

help

This should return a menu with all options for the connected device. This should include:

  • Changing controller and reference parameters
  • Starting and stopping
  • Printout of sensor data (to be used for debugging)
  • Adding and removing items for logging
  • Logging features (start logging, log interval and retrieve log in a MATLAB compatible format)
  • Save and load to and from EEPROM (holds logging parameters and controller setting)
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox