Cornerstone

Code written for the PM class' Cornerstone team WALL-E. All code done here is primarily completed and maintained by Caitlyn.

Code Notes:

This is just to track work flow for future reference if at all needed.

Process:

Since I'm most comfortable and familiar I will write a demo framework in MicroPython. Due to my familiarity with it, it will allow for quick production flow and debugging and understanding the task at hand. From there I will translate it into C or a C derivative for optimization purposes. C is more optimized and generally performs faster with less pull on memory. In short: MicroPython ==> C or C++ (if time allows)

Code Outline:

The code will be written in the following stages:

1. Set up Pico (I2C) and INA219 (sensor) communications (and a place holder for the relay)
2. Collect initial data (use time) and sleep (ex only collect a sample every 10 minutes)
3. Build an initial schedule
4. Perform periodic checks and adjust the schedule if needed
5. Test with mock data (mock work flow)
6. (post ML development) Communicate with the relay

New Code Outline:

The code development has taken a new path that follows this:

1. Everything will be seperated into classes that will be called into main just to make things cleaner.
2. Set up pin configuration for INA219 and place holder pins for the relay
3. Set up INA219 drivers to communicate the currents and voltage
4. Set up Relay communication (will likely have to be tweaked later on when relay is properly set up)
5. Build schedule class logic and ML
6. Write a clock logic since the pico's RTC is not reliable enough for this
7. Combine everything into a main function
8. Test with mock data
9. Translate it into C (if time allows)
10. Add in override and button logic so that the schedule is not completely overridden and will continue

Tests

Here is a personal list of tests that need to be checked in regards to the code. Written on the assumption that MicroPython will be the final choice:

Interface Tests

• Relay control works (on and off) without a schedule w Korben
• Relay control works (on and off) on a mock schedule w Korben
• Adjust the schedule building ML and run a schedule building over a few hours (Full System Test)
• Check flash memory (how long can it continuing persisting the data without power) (Full System Test) (Look at docs first)
• If snubber or some kind of surge protection is introduced, test reasonable levels w Blake (be gentle I only bought on microcontroller)

Individual Tests

• Keep passing in mock data to test the ML
• Check flash memory (how long can it continuing persisting the data without power) (Individual Test) (Looks at docs first)
• Python testing to check the basic functionality of the actual MicroPython
• Pass in invalid data to make sure the system is robust enough to not fail on error
• Collect some data and pass it into the pico (test sensor and pico communications) (adjust bounds as needed)