User Tools

Site Tools


projects:assembly_car

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
projects:assembly_car [2013/12/19 23:16]
cgoddard [Gotchas]
projects:assembly_car [2013/12/20 14:49] (current)
etappan [Files]
Line 159: Line 159:
 Venom does not document very well at all. [[http://​www.competitionx.com/​pdf/​esc/​venom-pro-brushless-esc-manual.pdf|This]] is not the electronic speed control (ESC) for our car. The programming is at least similar enough to let our car go backwards. If it is not in the correct mode, the car will only be able to go forwards. How can you go two steps forwards without at least one back? You can't. Venom does not document very well at all. [[http://​www.competitionx.com/​pdf/​esc/​venom-pro-brushless-esc-manual.pdf|This]] is not the electronic speed control (ESC) for our car. The programming is at least similar enough to let our car go backwards. If it is not in the correct mode, the car will only be able to go forwards. How can you go two steps forwards without at least one back? You can't.
 ==== Hardware Implementation ==== ==== Hardware Implementation ====
 +{{http://​cdn.instructables.com/​FTX/​AGWD/​H05NT69Z/​FTXAGWDH05NT69Z.LARGE.jpg?​200 }}
 Our robot is a Frankenstein of several components: an RC car chassis, an Arduino Uno, and two IR range-finder sensors. Our robot is a Frankenstein of several components: an RC car chassis, an Arduino Uno, and two IR range-finder sensors.
  
Line 169: Line 170:
  
 Mounted IR range-finding sensors using the sophisticated wonders of tape and cardboard. ​ Mounted IR range-finding sensors using the sophisticated wonders of tape and cardboard. ​
- 
-{{http://​cdn.instructables.com/​FTX/​AGWD/​H05NT69Z/​FTXAGWDH05NT69Z.LARGE.jpg?​200 }} 
  
 We used an [[http://​arduino.cc/​en/​Main/​ArduinoBoardUno|Arduino Uno]] with its [[http://​www.atmel.com/​Images/​doc8161.pdf|AtMega328 microcontroller]]. 90% of the information on the Arduino board is irrelevant if you're just using it as a platform for the AtMega but the schematics are there. The most significant detail is the connection between the raw AtMega pins and the I/O pins of the Arduino. We used an [[http://​arduino.cc/​en/​Main/​ArduinoBoardUno|Arduino Uno]] with its [[http://​www.atmel.com/​Images/​doc8161.pdf|AtMega328 microcontroller]]. 90% of the information on the Arduino board is irrelevant if you're just using it as a platform for the AtMega but the schematics are there. The most significant detail is the connection between the raw AtMega pins and the I/O pins of the Arduino.
Line 202: Line 201:
   * [[http://​extremeelectronics.co.in/​avr-tutorials/​timers-in-compare-mode-part-i/​ | AVR Timers]]: This series of articles is a good resource for timers and PWM in AVR. Read as far back as you need to given your application.   * [[http://​extremeelectronics.co.in/​avr-tutorials/​timers-in-compare-mode-part-i/​ | AVR Timers]]: This series of articles is a good resource for timers and PWM in AVR. Read as far back as you need to given your application.
 ==== Files ==== ==== Files ====
 +{{:​projects:​CompArchRobit.zip}}:​ A .zip archive with all of our assembly. robit.S is our main working build. Similarly-named files are backups of partially functional builds or else broken test builds. Running the following from a command line/prompt will build and deploy robit.S on Com10. Change the flash.bat file as needed to reflect the actual Com Port in use.
 +<​code>​
 +> cd "​CompArch Robit"
 +> make
 +Yes. Done. Good. :)
 +> flash
 +[...So much output... Holy cow...]
 +</​code>​
 +
 +{{:​projects:​Robit_Movie.zip}}:​ An early example of the car in motion. Later builds were less likely to capsize.
projects/assembly_car.1387512995.txt.gz ยท Last modified: 2013/12/19 23:16 by cgoddard