Week 5

What was accomplished?

Goal: Start testing with the physical circuit and in Fusion360. Wrap up any online tests
- Allison: Assign models on Kicad to final schematic draft and run simulation
- Samantha: Continue troubleshooting on Fusion360 to link all VREF components.
- Claire: Connect the entire MATLAB to arduino to circuit system and try to measure signals
Team accomplishment: Transitioned out of online testing and started working on the manufacturing process (Samantha and Allison), while Claire still troubleshoots and works on the circuit testing with MATLAB and Arduino.
- Samantha:
  - Created a formal testing document to brainstorm the best ways to test the various aspects we need to measure (signal validity, noise, outputs are accurate, etc.).
- Allison: Made a dummy PCB in coordination with learning how to CNC and make a PCB.
- Claire: Progressed in MATLAB with Simulink models, started trouble shooting the values going from MATLAB to Arduino with a mini LCD display test to 'see' what the circuit 'sees'.

W6 - Weekly Report

Progress:
- Learned how to download and create a GERBER file
- Started the setup for CNC manufacturing in Fusion360
- Made a dummy PCB to practice the assembly process with
Plan for next week:
- Learn how to manufacture and physically build a PCB on the CNC machines at school.

Problem: Can't run tests on Fusion360 due to the lack of absolute identfication for GND, power sources, and Vref.
Solution / Findings:
- Using the Name tool in Fusion360 and clicking on the nets related to the problems the Fusion error has identified and linking any two inputs together helped reduce the immediate errors.
Plan for next week:
- With this aspect finished, this area has been concluded indefinitely.

Findings / Progress:
- Simulink models are capable of sending data to the Arduino R4 Minima in real time.
Plan for next week:
- Finalize the Simulink Model and test the circuit with the entire MATLAB system I've built.
- Continue onto the second stage of the MATLAB algorithm with more randomized data and functions that take artifact and other external factors into account with the data.

Lead: Samantha for documentation and operation | Claire for overall design and goals

Breadboard Testing Procedure

Goal: See signals (just one for this week) on the oscilliscope
Findings / Progress:
- Due to problems with the Arduino data values (translating the data into acceptable data types for the breadboard), testing has been delayed.
- However, the team is assembling various tests to conduct immediately.
Plan for next week:
- Over the weekend, Claire will wrap up the Arduino data-type problem, and the team can utilize the oscilliscope to see signals.
- Over the course of the week, Samantha and Claire will conduct the tests

Page updated

Report abuse