Changes between Version 1 and Version 2 of RegionVnine

Show
Ignore:
Author:
nstiurca (IP: 192.168.0.39)
Timestamp:
03/22/09 18:33:58 (8 months ago)
Comment:

updated to current robot status to reflect current todo list

Legend:

Unmodified
Added
Removed
Modified
  • RegionVnine

    v1 v2  
    1 Region V 2009 
     1= Region V 2009 = 
     2Competition Documentation  
     3    * [http://www.r5conferences.org/StudentCompetition/Robotics/IEEE%202009%20Robotics%20Rules%20-%20Rev.%203.pdf Region V 2009 Robotics Rules and Information] on Region V Conference website 
    24 
     5== Todo List == 
     6 
     7=== Software === 
     8 
     9 * using CodeSourcery Gxx Lite toolchain 
     10 * using serial bootloader 
     11   * code is in repository under users/nstiurca/boot_loader 
     12   * accompanying serial programming utility (sflash) comes included in DriverLib/StellarisWare 
     13   * SBL currently is 1.3KB, which leaves 2KB footprint. If it can be squeezed down to <1KB, it only needs to leave 1KB footprint 
     14     * perhaps remove some of the error checking? 
     15 * competition code is in repository under region5/region5_2009 
     16 * most of the drivers were copied/adapted from RASLib 
     17   * some parts need to be optimized/cleaned up/readapted for the new hardware (as opposed to the Roboathon hardware) 
     18   * encoder code needs to be optimized, and verify correctness/accuracy of position tracking using encoders 
     19 * using CMUcam for color detection and hopefully some basic vision as well 
     20   * interface through serial port 
     21   * CMUcam can operate in either polled or continuous data acquisition modes 
     22 * can't really begin work or make much progress on actual competition code until Mechanical and Electrical progress catches up 
     23 
     24=== Mechanical Parts === 
     25 * use a small bowl to "grab" the boxes in order to drag them to their destination 
     26   * mounted on a hinge 
     27   * comes up/down as powered by a servo 
     28 * mount encoders 
     29   * coaxial to the drive wheels, but not connected to the drive shafts/wheels 
     30   * track motion on table accurately without introducing error if drive wheels slip while ac-/de-celerating 
     31     (encoder wheels should never slip since they have relatively low inertia) 
     32 * mount battery 
     33   * mount on bottom so as to have a low center of mass 
     34 * mount CMUcam 
     35   * away from bowl if used for vision & to help navigate 
     36               --- OR --- 
     37    cut hole in top of bowl, and point camera into bowl if only used to detect cube colors 
     38 * mount blinking LED detector 
     39   * just less than 8" above table surface 
     40   * should be able to revolve, mounted on either a servo or stepper motor 
     41 * no part of the robot should rise 8" (or more) above the table surface 
     42 
     43=== Electronics === 
     44 * band pass filter to detect frequency of blinking LEDs 
     45 * redesign Intro Board 
     46   * add second serial port 
     47   * beefier motor controllers 
     48   * add switch for boot/program mode 
     49     * bootloader checks if a pin (currently PB4) is high or low to decide if it should await a software update, or load the application 
     50   * reposition pins to better accommodate current hardware 
     51     * change M1 and M2 pins to work with Faulhaber [http://www.faulhaber.de/uploadpk/EN_2224SR_DFF.pdf 2224 U006 SR] [http://www.faulhaber.de/uploadpk/EN_IE2512_DFF.pdf IE2-512] [http://www.faulhaber.de/uploadpk/EN_201_MIN.pdf 20/1 14:1] motors 
     52       * encoder pins are unused since we are using external encoders not attached to the drive shafts 
     53       * map old motor +/- pins to pins 1&2 on Faulhaber ports (see the Faulhaber encoder pinout diagram) 
     54     * make sure servo pins work with [http://www.hitecrcd.com/servos/show?name=HS-322HD Hitec HS-322HD servos] 
     55       * these are our standard servos, so this should already work 
     56     * make ports for [http://docs.bgmicro.com/pdf/oak-grigsby%20encoders.pdf encoders] 
     57       * each encoder needs 2 GPIO pins, 5V, and Gnd 
     58     * make JTAG pins more accessible 
     59   * if possible, put battery port sideways so as to reduce board height 
     60   * board may (should) be expanded (width & height) 
     61 
     62== Related Links ==  
     63 * [WikiStart RAS Wiki Home] 
     64 * [RegionVcompetition Region V Home] 
     65