Goal: Officiate testing with documents detailing what was recorded, what the goal of the test is (what we are checking for, expected results, etc.), and our methodology. Testing needs to start, and work should accelerate faster than it is currently.
Team accomplishment: Progressed in individual assignments and tasks that relate to testing.
Samantha worked on troubleshooting a key issue preventing the team from testing the schematic in Fusion360: tying the Vref to a common point or component.
Allison is conducting isolated tests on Kikad to identify why our potential electrical values are not being transmitted from the input to the output of one stage.
Claire is creating the Simulink model to send live data values from MATLAB to the Arduino IDE. This week has included learning how to create the models and take the algorithm from MATLAB to Simulink to the Arduino R4 Minima's DAC.
Lead: Allison in Multisim
Findings:
On the computer simulation of the circuit, the voltage across the circuit does not change despite the input fluctuating.
Plan for next week:
I plan on running a simulation on Kicad, where I can get a graph of voltage. I will have more parts accurate to our project there.
This week's notes are under Week 5 of the document. They will be transferred to a physical notebook soon.
Problem: Can't run tests on Fuion360 because Fusion can't tell what our Vref (voltage reference) is referring to. We must find a way to link all the VREFs together and to reference the same source or system.
Solution / Findings:
Initial research documented on the document above.
Troubleshooting on Fusion360:
first, tried renaming the VREF components. An error occured stating you can't rename power supplies.
After looking at the properties of the components and doing some research, I believed that I need to figure out how to change the reference destination of each VREF. They each have labels matching it (Ex. "Supply 1").
Different sources stated that changing the prefix of the power supply (Located in the component library) would change the ref. des. but this failed to change it.
After working on editing different things in the component liibrary, I believe we need to troubleshoot more in the library to edit the component and hopefully find a way to link each VREF. We could edit th ecurrent one or create our own.
Plan for next week:
Continue to troubleshoot on Fusion360 electronics and the Fusion360 Component library.
Lead: Claire in Simulink (toolbox of MATLAB) & Arduino IDE
Translated to regular voltage (1 volt =1000000 microvolts)
In Microvolts
Findings / Progress:
Developed the band equations further w/ angular frequency constants
Determined the best way to actively transfer MATLAB data points into the Arduino
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.