Week 1

Progress - Week 1

***This is the beginning of our "Sonar Radar System" project!***

Lab Day: 30/01/2025

Basic Idea:

Our project is a sonar/radar tracking system designing to scan, identify and target objects within a certain vicinity. It will do this via an ultrasonic senor rotating 180 degrees across an open area, with an expected range 0-40cm. Our project will also consist of nerf dart-based projectile launcher that will be mounted alongside our sensor for easy targeting and launching.

The aim of this project is for us to build a cool and fun project whilst gaining much knowledge and experience with electronic circuitry, tools, computer-aided design, software, documentation, report writing, project presentation, communication and teamwork.

Plan:

1) We would start by reviewing our components, finding each set of measurements on their respective datasheets and beginning our 3D CAD software designs via designing around those certain dimensions.

2) We would also review and test each component via use of the lab equipment (such as multi-meters and power packs) as well as cutting suitable wiring for future use.

Main Components:

1) Arduino UNO R4 WIFI - x1

2) Servo Motor, SG90 - x1

3) Ultrasonic Sensor - x1

4) Breadboard - x1

5) 9V Battery, Duracell - x1

6) DC Gear Motors - x2

7) Plastic wheels - x2

Roles:

1) Project Manager = Oversees progress across the team, helps out team members in different areas, assists in documentation, design work, software and component testing and building.

2) Designer = Responsible for designing and printing the planned structural modules for the project. 

    Paper design + dimensions => 3D CAD => Real 3D models

3) Programmer = The leader in the project's software capabilities and functions. They are responsible for creating a strong and reliable codebase for the project to function correctly. As a result, they will also make extensive tests on the software throughout the development process, therefore often accompanied by our "tester".

4) Tester = Responsible for the extensive testing required for all of the project code, components and system functions. He is also the link between "expectation" and "reality" of our project modules throughout development and is usually accompanied by our "documenter".

5) Documenter = The lead for documentation: is responsible for documenting our project progress throughout development. This is usually done via logbook recordings, video recordings and photos. They will also work closely with the project manager to effectively understand what the development progress as well as who needs help and where.

Progress:

- Our components had not yet arrived, so our progress was quite staggered. However, we decided to shift our focus on what we could do whilst contacting our academic advisor and the lab team staff to sought out the issue.

- Our programmer got to work with learning and designing the starting code for a radar user interface (UI) which will act as the link between the user and the radar system.

- Accompanied with him was the tester, who could only test the software due to missing components but had a prime role in making sure the code worked perfectly. They formed a coding sub-team. The documenter also joined in the software sub-team and assisted in the code development.

- The software sub-team eventually created a working prototype of the radar UI. The whole

- Our designer and project manager worked together to study the dimensions of the components needed and designing (on paper) prototype designs for our project structure. They formed a design sub-team. The designer also started to learn how to use the CAD software for later and eventually finalised the first physical module design: the base. 

- The design sub-team also decided that 3 initial components may be to much, and it was successfully scaled down to 2.

- The documenter, as well as working with the software sub-team, was constantly working between both sub-teams, taking notes in a logbook, recording short and snappy videos and taking many photos.

- The project manager, though mainly working with the designer, also checked on and helped the software sub-team occasionally to make sure everyone was happy with what they were doing, as well as noting what was done, what was yet to do and what problems needed assistance with.  

Additional Notes:

- Extra components were ordered as backups if any of the main components failed or were damaged.

- We still needed to order nerf darts for our project, which we couldn't find with the correct suppliers, resulting in a delay.

- Roles and responsibilities are also shared amongst each other when necessary to maintain optimal team wellbeing.