Sprint contribu�on Report

Sprint 1
To do

-Come up with a design problem rela�ng to the “box” theme

-Choose a design idea

-Figure out components

-Choose a target audience

My contribu�on

Came up with the whistle box idea in group idea�on stage:

My idea was to create a novelty box that could be opened by whistling a certain frequency. I came up
with a sensor to use, and found examples of whistling projects for Arduino to control lights such as
the following: htps://github.com/ArminJo/Arduino-FrequencyDetector

Word document with box idea info

During our mee�ng I realised the fealty of my idea, it was overly complex to code and beyond the
capabili�es of an Arduino and the sensors we had access to. There was also some tension when
choosing between two of the other group members ideas, the fridge security detector, and the
moving desktop pet. To consolidate this, I listened to both group members ideas and presented them
with the limita�ons of their ideas and how they would overcome this. However, as a group we went
with a moving car idea instead as it was more atrac�ve to us and seemed more prac�cal and
achievable.

Retrospec�ve 1 takeaways:

Group members were too atached to their individual ideas, should’ve listened to each other more
and chose ideas that would work the best not personal preferences. In the group mee�ng this was
improved as we considered the pros and cons of each idea and decided on one together. Assigning
tasks did not go well and our target audience was difficult to specify.

Sprint 2
To do

-Figure out how the car will move forward

-Figure out how the wheels change direc�on

-Figure out if two motorised rear wheels have enough power to carry phone, wallet, water botle

-Figure out what components need to be used

My contribu�on

Found and studied code for dexter GoPiGo3 motor driver:

We had been given a motor by the teacher that could be used for our car and studied a manual on
how to code it, but our group ended up not going with that type of motor.

I helped ideate solu�on to user problem with our car idea:

Answered an in-class ques�onnaire to come up with basic func�onality of our user following car idea
“A moving robot that detects a person’s heat signature and follows behind them, can carry a water
botle. The 'head' has sensors, and it turns to con�nually detect where the user is. The car will turn.”

Also came up with component list by answering ques�onnaire and defined data types and ranges of
sensors/components. As seen in showcase 2.
In-class ques�onnaire
Retrospec�ve 2 takeaways:

Beter assigning of tasks and more communica�on would’ve saved me �me trying to learn that
manual.

Sprint 3
To do

- The basic frame structure of the cart. Batery, wheel, Arduino board, and l298N motor driver
installed.

- Ge�ng the automated box prototype working

- Code for the three components: Flame sensor, automated box, and obstacle avoidance example
code

My contribu�on

Came up with the idea of using a grove flame sensor to poten�ally detect people via infrared light.

Found example code for the L298N motor driver.

Found example code and tested flame sensor and decided against it because it only works with
objects emi�ng high levels of infrared light

I thoroughly researched into infrared sensors and presented one to the group to purchase. A lot of
considera�ons went into it, including the range of the sensor.

Retrospec�ve 3 takeaways:

Finally decided on the design idea and to go through with it despite previous apprehensions that it
wouldn’t work. Unfortunately, the car was not working with example code once assembled.

Sprint 4
To do

- Basic func�onality in the car via code

- Build the main func�ons of the car

- Fix func�on which uses a switch to turn the car on and off

- Test obstacle avoiding func�on

My contribu�on

Fixed the car:

I took the car to a Jaycar store to diagnose the problem and got it working by replacing the exis�ng
12v batery pack with the correct 9v one. I then implemented the correct wiring configura�on for
motor as it was wrong before. A�er tes�ng the car with basic example code, the wheels were
working.

Edited ques�onnaire:

A�er the research design I edited them to make them more detailed, relevant and to get more
insight.

Created first instance of working code for our idea:

I tested the obstacle avoidance example that group members found online and then, a�er many
itera�ons, adapted the code to pursue obstacles instead of avoiding obstacles and addi�onally, to
stop in front of them. I then created a turning func�on to find objects and ended up with a working
prototype using the ultrasonic sensor for detec�on. I then met with the group bringing the car to test
it at university campus and showed it worked. Below are the code itera�ons from planning to the
final working code.

Retrospec�ve 4 takeaways:

Switch for on/off func�on was not created, more group collabora�on needed.
First code itera�on (ultrasonic only)
Second code itera�on
Third code itera�on (First �me implemen�ng “void turnCar” func�on to
add more parameters when car turns to achieve basic func�onality)

Also added a while statement whilst going forward to ensure target was
s�ll in front of the car (otherwise car stops and returns to loop)
Code tes�ng controlling movement with Infrared
 Final itera�on with both infrared and ultrasonic

In this code I changed condi�onals from && to || in the while statements to make sure all cases
were covered in terms of the car stopping pursuing and returning to the start of the loop
Ini�al writen “code logic plan” that led to the third itera�on of code
Sprint 5
To do:

-Improve speed variables and stop func�ons in the code

-3D print box

-User tes�ng

-Designing ques�onnaire

My contribu�on:

Added infrared component: A�er receiving the component via post I edited the code to get the
infrared working and it was successful in working in tandem with the ultrasonic.

Performed user tes�ng on User 2: At university I performed tes�ng on user 2 and recorded the data.

Edited code based on user tes�ng: Based on user tes�ng I atempted to edit the code further to
improve the prototype but was unsuccessful.

Retrospec�ve 5 takeaways:

Coding went well, succeeded in crea�ng a complete and working prototype according to our plan.