Team 10A
The three weeks we had in Glasgow are a one of a kind experience, there had been ups and downs in our time here working on this project. Below are some of our proud moments that we are fortunate to experience in our time here!
One of the major concerns each of us had at the begining of this project was the unfamiliarality we had for one another. Before this, we had never worked together as a team before. However, it turns out that our strengths covered for each of our weakness in this team. Together, leveraging on each other strengths, we managed to bring this project to a success in these 3 weeks. We are proud that are able to overcome the challenges we faced as a team, and proud to finish this project as a team in a place far away from home.
When we first thought of the Tank idea and sketched it down. The idea of it becoming true feels distant, as crafting may not be our forte since we are Computer Science Students. But slowly, day by day, as we cut and glued pieces of cardboards together, the prototype and goal we had in mind droves closer and closer, and eventually, we managed to make it move and rotate exactly as we wanted to. That, in itself is a really proud moment for all of us.
We had multiple of these moments when we suddenly think of a bright idea that could lead us to advance the project. One of the most memorable ones is the 'teeth' that we made for the rotatable top which will be mentioned in the team's reflection. Another one was when the team was having problems with the instability of the cardboard wheels we had made. At first we thought of gluing the outer ring of the wheels to act as wheel tires so that the wheel can have more friction to the ground. The eureka moment happened when one of us plucked out the tires of the original curio bot and fit it to the wheels of our prototype. Surprisingly, it fit perfectly and we have ourselves an amazing set of wheels.
Throughout
our project, we embarked on an intensive exploration, learning, and adaptation
journey.
Our journey
kicked off in the first week when we met with our client and dove straight into
research and experimentation with the Smartibot, brainstorming ways to improve
upon it and engage other students. However, we soon realized that our focus had
veered from our actual project scope: to enhance the Curio bot and not the
Smartibot. This hiccup prompted a timely realignment of our goals and mental
models, leading us back to the drawing board to create design sketches.
Despite
initial frustration with this perceived detour, we appreciated the valuable
lesson it imparted: the importance of asking pointed, purposeful questions to
clients and comprehending the project scope before setting off to work.
As we
ventured into the prototyping phase, our approach was initially
improvisational. However, as we delved deeper, various challenges began to
surface. For instance, while we were fond of our first prototype for its
compact, straightforward design, it struggled with stability due to being
back-heavy. It also lacked adjustable angles, a key feature our client wanted
to retain.
Many
enlightening moments throughout the process have profoundly impacted our way of
thinking. One of the most memorable was the realization that we only needed a
single servo motor to rotate the platform, rather than aligning multiple
'teeth' for two servo motors - a discovery we made only after painstakingly
assembling them. This lesson proved invaluable when we later employed smaller
servos to adjust the phone camera angle remotely.
Additionally,
we had the unique opportunity to meet with the original creator of Curio. The
insights gained from understanding his thought process, the constraints he
encountered, and how he creatively maneuvered around them proved beneficial
when tackling our constraints.
At first
glance, our problems we had faced mentioned above seemed discouraging, but they proved to be our most
excellent teachers, helping us recognize that constraints can be leveraged to
our advantage and the paramount importance of careful planning. We learned the importance of asking the correct questions to our customer so that we will not get different ideas to what the customers actually want. We also learnt the importance of regularly consulting the customer to ensure that our project is on track. Lastly, probably the most valuable lesson learnt is that there is always more than one way to do things, like the case of the 'teeth' in our rotational top. This project
was not just simply a journey of design and development, it is additionally a
transformative lesson in problem-solving, resilience, and the power of
perspective.
The below slider illustrates the reflections the team had throughout each day in the span of the entire project.
Today is the first day, we have met the client (The prof), gathered requirements, clarified questions and we have also picked up the supplies we require for the project.
Additionally, we had crafted out our team contract as well.
These are the questions we asked:
1. What challenges have you faced while teaching or learning programming? How do you think Curio could potentially address these challenges?
2. In the past, what constraints have you encountered that have limited your ability to teach or learn programming?
3. Who usually uses Curio? Have you received any feedback about it from different types of users?
4. What specific issues have you encountered with the Curio robot's hardware?
5. Can you describe a specific instance where Curio helped you or someone you know learn about web development, UI/UX design, or AI/ML?
6. Could you share an instance where you or another user struggled with the design of the robot?
7. Can you share any experiences or observations on how the project sharing feature has been used in a learning environment?
8. Can you describe some specific improvements you would like to see in the Curio robot based on your past experiences with it?
9. In your experience, have there been any other tools or devices used alongside the Curio robot that have enhanced the learning experience?
10. Can you share how you've seen the Curio robot being used across different courses or modules?
11. Have you faced any compatibility issues with different operating systems while using the Curio platform?
12. Could you share a specific story about a time when you felt the Curio robot was particularly useful or frustrating?
13. Can you describe a memorable interaction that a student or teacher had with the Curio platform?
14. Have you ever had to choose a different tool or platform over Curio due to its cost?
15. In your experience, how does Curio compare to similar platforms like poppy-project.org or openbot.org?
16. Can you tell me about a time when understanding the Espruino project or the Smartibot platform was essential for using Curio?
17. Have you encountered a situation where Curio could have been useful outside the intended user group or educational level?
Lessons:
Today, we learn about how does sharing problems and providing feedback help us learn as it encourages more collaboration over competitiveness. It also give the team a better understanding of what the clients want.
Project:
Today we research more about what the Smartibot can do and how it works. We have also found past projects to gain inspiration on the improved design.
Tomorrow, we plan to come up with a few sketches for the prototype design and further research on how we can use the Smartibot to make lessons engaging to students.
Project:
Today we brainstorm possible ways to use smartibot to make teaching engaging. Here are some of our ideas.
1. AI Drawing Bot: Use artificial intelligence for the bot the learn and draw pictures
2. AI Race Cource: Use artificial intelligence to study and navigate around the course and race to see which team is the fastest.
3. AI Football: Use artificial intelligence to challenge teams in a robot football match
4. Obstacle Course: Use artificial intelligence to study and navigate a course and see which robot can navigate the most optimal way.
5. Paddle Boat Race: Create a AI paddle boat that is able to navigate the river and compete to see who is the fastest.
We have also identified some limitations of the smartibot. It does not have an area to secure the phone, the initial way was to tie a rubber band around it. We decided to change one of the pieces to allow the phone to be placed without the use of rubber bands.
Prototype V1:
Before:
After:
Experiment:
With phone
We today realise that we were going off track, we were too focus on how we make the lessons engaging instead of designing the Curio bot and we focus more on improving the Smartibot instead of the Curio.
We immediately rectify by meeting the client and clarify our doubts. After the meeting we managed to get everyone aligned and draft a suitable markup of the prototype.
Prototype:
After today, we have a first hand experience on why aligning with everyone in the team and
the customer is important as it saves time and effect in creating prototype and the final product.
Today, we manage to design new prototypes by combining ideas from the previous 3D model and also ideas provided by other teams.
3D model (Tank):
For this design we got the inspiration from a real life tank. Basically, we allow user to rotate the top
base to help them orientate the bot, so it does not matter which side of the bot is the front. The bot
would be able to rotate using servos which will fit to the teeth shape groves below.
Reliant Robin:
For this design, we asked group 9 about their proposal idea to draw inspiration for our design. They
were planning to create quizes and make the bots race. So we design one where it has car-like
shape. We based the design of the reliant robin as it is an iconic vehicle in the UK. We also can
save cost on material by making 2 wheels instead of 4.
Prototype:
We also manage to do up a working prototype of the Reliant Robin design. Although there are a
few kinks to fix like if the phone is place at the back it will be back heavy, motors will come loose
and most parts are glued so not a lot of ways to dismentle.
Tomorrow, we plan to continue working on the prototype for the tank design and improving the current prototype.
Today we managed to improve the Reliant Robin Prototype to move smoother and carry phones by
adding the tyres from Curio and adding some toothpicks at the back to act as a skeleton. There are
still some limitations, such as it can only support lighter phone and heavier phones will topple if
move at a fast speed and it's not able to change the angle of the phone.
We have also created a rotating base for the “Tank” design to withstand the weight of the phone
and rotate with it. We decided to use only 1 servo to rotate as the previous method using grove did
not work well. The limitations we notice for now is that it can only rotate up to 180 degrees.
Tomorrow, we will continue working on the Tank Model and try to improve on the reliant robin model.
We added some new features to the Tank design, after conducting a few testing, we realize that the
phone adjusting system does not have support to prevent the phone from toppling over so we
decided to add stoppers at the back to prevent the phone from falling. We also added an adjustable
stick to make the phone at a fixed angle.
For the prototype We finished creating the base and the wheels, so tomorrow we will assemble all
the parts together and conduct an initial test. We feel that we could do more today, however, there
are limitations in the glue gun provided as it only has a work time of 30 minutes and it cannot be
used while charging. But it was not much of a problem as we continued working on the other
deliverables like the website while waiting to charge.
We also emailed Gordon Williams, the main designer of Curio yesterday to organise a meeting to
give us possible feedback and better understand his thinking process and constraints he faced.
Currently waiting for a reply.
Had a group meeting with Gordon Williams the creator of the original Curio bot. We manage to
learn about his thinking process in creating Curio and the constraints he faced and how he use this
constraints to his advantage.
Here is a summary of what was mentioned in the meeting.
1. Stepper motor is the most cost-efficient to get the result he wants since precision is the goal
2. Constraints : being able to tilt the robot in various angles
3. A lot of the stuff being done is still experimental
4. Would be beneficial if parts are easily assembled and detachable, it takes a while to assemble the entire robot.
5. Trying to keep the material cost down to something sensible
for example servo motors with the electronic magnet are not practical as they cost 2/3 of the entire cost making sure the wheels and the back wheel are always in stock.
Try to keep the material used simple, might consider implementing 3d printing , consider using plastic for the wheel.
6. Another weak point would be the phone stand. (Very floppy)
7. Keep it to a reasonably small amount of parts
8. It is nice to have modularity as most universities are able to 3d print it
9. Curio does have a control board and it is not possible to get the user to make a new control board from scratch, so focus of robot main constraints are the hardware (specifically motor)
Designer Feedback for team 10A prototypes:
1. Appreciates the rotation of the 2nd prototype as that facing.so his consideration but advise to ensure the wheels are rotatable in the direction that the camera is facin
2. Reinstate to have easier alternative to tilt the angle of the phone which the team plans to overcome using servo motors to automate angle positioning of the phone
3. When using 3 wheels, need a steering wheel(ball bearing)
Designer Feedback for team 10B prototypes:
1. Could consider using a stepper motor rather than DC(smartibot) to aid with the precision.
2. He likes the versality aspect of the design and having the students to assemble to their liking rather than sending an assembled bot which might be damaged in transit.
3. He likes the clamp design and does not have a use case when designing curio, we should think about our use case and work towards it
4. Initially he did not have a use case so the advice was to have a use case to work on the problems, e.g., if speed is something we are working on then focus on that direction such as point 2.
Prototype
After the meeting we finish up the tank prototype and redesigned it base on Gordon's feedback.
Tomorrow we plan to improve on the prototype and conduct testing.
In today's lecture, we learned about how to conduct proper usability testing, to learn more about
what issues users faced when using the product. Our team plans to conduct it next week however
we are having a bit of trouble thinking of Task Scenarios since our project is mainly about creating
the robot. We were thinking maybe we can set up an obstacle course to see how the users feel
when controlling the bot.
For the prototype, we manage to finish it up by adding the 1 side servos to allow the phone mount
to adjust the angle remotely. However, we realize 1 servo is not enough to lift the phone back up if
tilted down so for now we tested with a power bank.
On Monday, we will try adding additional servo on the other side and start conducting usability tests
with some of our fellow classmates.
We added a second servo to able to support tilting of phone. We also receive feedback on how to conduct testing by the professor where the user can be at the other room controlling and looking at the camera of the bot to test the mobility and visibility.
We continued working on the website and poster design as well. Here is the initial design of the poster.
Tomorrow, we will start to conduct our usability testing, continue working on website and poster.
Received constructive feedback on the poster and the website. We have also plan to add instructions on how to build our prototype.
Website:
Home page Reflection Page
Poster:
Instructions
Tomorrow We will make finishing touches to the poster, website and testings before the big day on Thursday.
Today we receive constructive feedback regarding the website and executing Usability Testing for our project. For our usability testing, We create a task scenario where the tester would be in one room and the robot in another, then he will control the bot to find bottles, underneath those bottles there is a piece of paper with a number written on it and the tester is will identify the largest number.
Website feedback:
Make youtube video just background video/GIF and remove audio
add link to the design sketches
Change background of home page
Expand on the research and requirement gathering phase, what we learn when talking to client.
Get other people to help test to get their feedback
Problem. brainstorm, solution
Reflection:be specific like “what exactly was discouraging”
give example
personal experience?
Not too generic
Something we are proud of or have done.
Website URL: https://design-and-innovation-2023.github.io/CurioTank/
Tomorrow is the big day and we are excited to show off our efforts.
Finally, the day we have been waiting for, exhibition day. It was fun to see people showing interest and trying out the Curio Tank. It feels good when people approach us with questions about what we do and how we do it as there is a sense of accomplishment after 3 weeks of effort. We receive positive feedback when trying our the bot and they had alot of fun trying for team 10A and 10B’s robots.
created with
Static Site Generator .