Introduction to Arduino workshop: Difference between revisions
No edit summary |
Ranthalion (talk | contribs) No edit summary |
||
Line 69: | Line 69: | ||
5. What to Bring - A laptop with the Arduino software installed. A willingness to have fun and make mistakes. | 5. What to Bring - A laptop with the Arduino software installed. A willingness to have fun and make mistakes. | ||
6. Cost - $ | 6. Cost - Determined by components. $80 if providing full kit, otherwise it is to be determined. | ||
==Learning Goals and Objectives or Scope== | ==Learning Goals and Objectives or Scope== | ||
Line 97: | Line 97: | ||
* I'd like everyone to walk away with something. Maybe a certificate with a picture of the thing they made. | * I'd like everyone to walk away with something. Maybe a certificate with a picture of the thing they made. | ||
* Need to edit and clean up this wiki, but I'm tired and it's late | * Need to edit and clean up this wiki, but I'm tired and it's late | ||
===Feedback=== | |||
* There were some silences and participants may have been uncomfortable with the direction to follow the book without being engaged. It just seems to be the opposite of a guided workshop. Maybe a slide, gif, or video of the completed task(s) would pull it together. | |||
* The lack of name plates or name tags made it difficult to interact with people. | |||
* The help sign seems like it was a good idea, but didn't get used. Maybe it should just be a 2 sided card with QUESTION on it instead of HELP. | |||
* It might have been helpful to show the internals of the controllers; it could make the way it works a little more clear. | |||
* Transistors were hard to understand. The jump from LED to motor to RC car was tough. Good Luck? | |||
* It might be beneficial to do a 5 minute overview of programming and code. Introduce method, variables, #include, and loops. Or not - maybe it's better to learn them like a spoken language... | |||
* The RC car destruction competition was awesome! It might have been nice to have a space to see the car move. The 2 cars on the same frequency was kind of a problem. | |||
* Multiple sources of information was a problem. It would be better to use a single source for schematics and programs. | |||
* The cost went way over the budget, so we'll have to figure that out. | |||
* I loved the TORNADO KICK!!! (We need the videos!) | |||
* The intro should also include their past experience with electronics, microcontrollers, and programming. That would help when determining the level of detail to provide when offering help. | |||
* 6-8 participants is definitely the upper limit and requires 2 assistants. |
Revision as of 23:03, 29 July 2014
The Introduction to Arduino Workshop is a beginners workshop designed to get newcomers up and running with Arduino microcontrollers.
Resources for Workshop Participants
Workshop
1. Blink LED [adafriut experementers kit 1]
- sketch is located under examples basics blink
- circuit 1 in book
2. Single Servo [adafriut experementers kit 4]
- Copy and Paste sketch from oomlout
- circuit 8 in book
3. Using a NPN transistor to switch led's on and off
- see the blackboard --> turning two leds on and off
- will prepare us for controlling the RC car later
- similar to [circuit 3 in oomlout]
- similar to circuit 10 in book
- use blink sketch
- for extra difficulty use a motor in place of one of the leds
- [npn transistor pins]
What to Expect
- A fun participatory workshop
- Hands on practice
- Opportunities for active problem solving (,istakes are encouraged!)
- To work together to make something original that completes a task
- To know what to do next to keep learning/playing
Before the Workshop
- Thanks for signing up. If you have problems with anything, don't worry. We'll take some time at the beginning to get everyone ready.
- Bring your laptop if you have one
- Go ahead and download the software for your operating system.
- Install it on your laptop.
- Feel free to explore the links a little and take a look around the internets for cool projects.
- Edit this wiki!!! Put some comments under the links if you want. List what you'd like to learn. Whatever!
- [What NOT to DO!!!]
Follow- up/ Resources:
- Tutorials
- Instructional Videos:
- Projects:
Resources for Planners
General Links for lesson plans/tutorials
- Adafruit
- Blink an Arduino Lesson
- www.ieee.org/education_careers/education/preuniversity/tispt/tispt_lesson.html
- www.annroot.com/Intro/Arduino/ArduinoLessonPlans.html
- playground.arduino.cc/Projects/ArduinoUsers
Meetup description
1. Background - A little bit about the arduino and open source hardware.
2. Arduino Basics - How to blink LED's, upload code, simple control of servos, etc.
3. Original Fun - Create something original to compete in a simple project based competition. Don't worry, you'll be provided with plans and materials that will work. The only goals are originality and fun. Completion of the task is optional.
4. Learning Beyond the Workshop - Information on how to participate in the Arduino community so you can flex your new-found powers beyond the hack.rva workshop. Including websites to find projects, parts, additional shields, and code. 5. What to Bring - A laptop with the Arduino software installed. A willingness to have fun and make mistakes.
6. Cost - Determined by components. $80 if providing full kit, otherwise it is to be determined.
Learning Goals and Objectives or Scope
- Have fun and make something with other people. Encourage participants to become active learners in the Maker tradition of try-fail-try, share, and participate.
- Each participant:
- will leave the workshop with a working knowledge of how to get started using Arduino
- will know what to do next to keep learning and working with Arduino
- will learn and apply at least 3 basic arduino programming skills
Learning Plans or Outlines
We're using a google doc folder at the moment to collaborate. Arduino Workshop Folder. Beth made the lesson plan from a conversation we had during open house and research on her own. The Journal is my ranting so far.
- Kramer's rough plan:
I'm planning
- 15 min intro
- 45 min follow along (blink led....read sensor...move servo)
- 15 min Where to find more info
- 30min build for competition (radio controlled vehicle using servos from the arduino to control it. Decorate vehicle (LEDs).
- 30 min competition (how many pegs can you knock down in the most ridiculous way possible. 1 award for pins. 1 award for originality.)
- 15 min close and clean up
That leaves 30 minutes cushion. I'm sure I'll need it.
Concerns and Ideas
- doing the original task could take a while
- I'd like everyone to walk away with something. Maybe a certificate with a picture of the thing they made.
- Need to edit and clean up this wiki, but I'm tired and it's late
Feedback
- There were some silences and participants may have been uncomfortable with the direction to follow the book without being engaged. It just seems to be the opposite of a guided workshop. Maybe a slide, gif, or video of the completed task(s) would pull it together.
- The lack of name plates or name tags made it difficult to interact with people.
- The help sign seems like it was a good idea, but didn't get used. Maybe it should just be a 2 sided card with QUESTION on it instead of HELP.
- It might have been helpful to show the internals of the controllers; it could make the way it works a little more clear.
- Transistors were hard to understand. The jump from LED to motor to RC car was tough. Good Luck?
- It might be beneficial to do a 5 minute overview of programming and code. Introduce method, variables, #include, and loops. Or not - maybe it's better to learn them like a spoken language...
- The RC car destruction competition was awesome! It might have been nice to have a space to see the car move. The 2 cars on the same frequency was kind of a problem.
- Multiple sources of information was a problem. It would be better to use a single source for schematics and programs.
- The cost went way over the budget, so we'll have to figure that out.
- I loved the TORNADO KICK!!! (We need the videos!)
- The intro should also include their past experience with electronics, microcontrollers, and programming. That would help when determining the level of detail to provide when offering help.
- 6-8 participants is definitely the upper limit and requires 2 assistants.