Wednesday, 30 March 2016

Weekly Schedule

Welcome back.

This week's schedule follows:


  • Tuesday - Work period for project. Electronics Review.
  • Wednesday - Coding review. Work period for project.
  • Thursday - Module Quiz. Remaining time to complete Work Habits/Employability Survey.
  • Friday - Safety Meeting. Final work period to submit project.


Tuesday, 15 March 2016

Weekly Reminders: March 14-17th

This week we are going to focus primarily on the Blinking Lights Game Project.

All material for that project must be handed in at the end of class Thursday.

The projects will be marked and entered into Homelogic over Spring Break.

You may finish any missing parts once we come back from break.

As a reminder, the unit one and two module quiz has been moved to Wednesday March 30th. A review pamphlet will be published no later than Thursday the 17th of March.

Wednesday, 9 March 2016

Reminder: Assignment Check

from xkcd.com
Just a friendly reminder that I will be taking in everyone's checklists at the end of class today.

They will be returned tomorrow after being entered in HomeLogic.

You may complete them at any time and the marks will be updated.

Happy Wednesday

Friday, 4 March 2016

Robotics Timelines

from xkcd.com
Here are the Robotics due dates up until Spring Break:


  • Wednesday March 9th: Arduino Programming assignments due
  • Wednesday March 16th: Module one and two final project due
  • Thursday March 17th: Module one and two quiz

Friday Funny: Travelling in Groups

Tuesday, 1 March 2016

Blinking Lights Final Project

arduino-ide.png
Arduino Assignment (Alternate Final Assignment)

Purpose: In this assignment you will be creating an interactive game using the following parts:

  • Arduino Uno(R3) (or Sketchboard, or Redboard)
  • USB Programming Cable
  • 1 Protoboard
  • 5 Green LEDs
  • 1 non-Green LED
  • 6 weak resistors (100Ω-1kΩ, all same value)
  • 1 strong resistor (10kΩ)
  • 1 Strip of 90° pin headers
  • 1 pushbutton

The game should blink the five green leds in order and should stop the blinking at the currently blinking light when the button is pushed.

One of the lights should be the “winning light” and when that light is stopped at with the push button is pressed another LED should turn on.(again, different coloured LED).

You should also plan to integrate a potentiometer(trimpot) controlled speed dial to the circuit.

To receive full marks, your group must submit the following:

  • The pseudocode you based your code on.
  • The Arduino code written in text and submitted through your Google Drive Assignment Folder.
  • An electrical diagram (created with Fritzing) the shows the layout of the hardware board.
  • A demonstration of the working game.


Assessment

Four things must be submitted at the end of the project:
  • The pseudocode(flowchart) used to program the robot.
  • The soldered circuit board.
  • The electrical schematic of the board (Done in Fritzing).
  • A copy of the code used to program the robot.
  • The Teamwork Rubric (please note that your teamwork rubric may be modified if Mr.Way feels that you aren’t being truthful.)


4 - Excellent
3 - Good
2 - Basic
1 - Needs Improvement
Pseudocode (flowchart)
The psuedocode matches the programming perfectly and reflects the program used in the project.
The psuedocode matches the programming with a few errors and reflects the program used in the project.
The psuedocode matches the programming in spirit and reflects the program used in the project.
The psuedocode does not match the program
Hardware
The hardware is connected in a logical way that demonstrates clear knowledge of how each part works. All parts have been included.
The hardware is connected in a way that shows how each part works with some redundant or illogical parts. Most parts have been included.
The hardware is connected but only one part (input/output) works or the documentation is partially incomplete.
The documentation is incomplete and/or the system does not function properly.
Electrical Schematic
The electrical schematic follows all conventions properly and is easy to understand.
The electrical schematic most conventions properly and is somewhat easy to understand.
The electrical schematic has multiple errors but follows most conventions properly.
The electrical schematic is missing significant circuits.
Arduino Code
All software conventions are followed and the program is easy to understand because of proper commenting. All features are present.
Almost all software conventions are followed and the program is understandable due to satisfactory commenting.
Either the software conventions aren’t followed or the program is difficult to understand due to poor commenting.
Only one part of the program functions (Input or output) and the commenting is poor.
Teamwork*
You were engaged as a teammate and helped to lead or follow in completing the task.
You were engaged but frequently distracted from completion of the project.
You were mostly disengaged or distracted from the project but contributed somewhat.
You were absent from or completely disengaged from the process of finishing the project.

*Teamwork scores will be an individual mark while the other assessments are group-based.