Lab 4

The questions below are due on Friday March 03, 2023; 05:00:00 PM.

You are not logged in.
Please Log In for full access to the web site.
Note that this link will take you to an external site (https://shimmer.mit.edu) to authenticate, and then you will be redirected back to this page.

Learning Objectives

We're going to undertake Three activities in today's lab. It's gonna by fun and busy!

MCU and power-board PCB layout design review
Team agreements
Team work

MCU & power-board PCB layout design review

Same deal as with your sensor board. Now that your board schematic finished and now laid out, it's time to undertake a review of your layout. Everyone should have their PCB layout finished and submitted as part of EX03.

As before, we'll go through the layouts on A365 and review each one. A staff member should be able to go through them with you.

The layout issues here are the same as for the sensor board, with a few extra issues specific to these boards:

MCU board

Make sure there are headers or lots of test points for all the pins of the ESP32

Power board

Make sure to use 20 mil traces for 3V3, 5V, and VBAT nets
Make sure to use PH2.0 connector to Battery, regular (2.54mm) JST connectors for rest.

Team agreements

Based on Thursday's lecture, in lab we'll be filling out a team agreement. Please take a look at the instructions here. Create a Google Doc in your Google Drive folder and fill in, following the instructions.

Team meeting

Use this lab time to go over the feedback from yesterday's concept reviews. Over the next three weeks, your goal as a team is to downselect to a single concept, and to be actively prototyping to de-risk & implement.

As part of that concept, you will need to develop:

Industrial design for the HW node -- what does it look like?
A wireframe of the web front-end
A detailed functional block diagram of the HW, FW, and SW
Mostly filled-out specifications. It's ok to not have the specs 100% set, but try to get close, and for each spec that isn't set, or that you are concerned about how to achieve, there should be a plan
Research, modeling, and prototyping that helps de-risk your design
A project plan: a timeline with milestones, deliverables, and the person (or people) in charge
A filled-out Ethical Computing Protocol (ECP) (more details on this in EX04)
Any updates to your team roles

Checkoff 1:
Before heading out, discuss your team agreement and plan for the next 3 weeks with a staff member