# Microcontroller Sensor Reading Lab

Project path: /projects/wire-a-sensor-to-microcontroller/
Video-note path: /youtube-notes/wire-a-sensor-to-microcontroller/

## Lab purpose

Practice documenting a first sensor reading without guessing at wires or voltage.

You have a microcontroller board and one simple sensor. The lab asks you to prove what each wire is supposed to do, what voltage the sensor expects, and what reading you expect before moving jumpers or adding more parts.

Use this note as a working sheet. The useful outcome is not a polished paragraph; it is a record that proves what you checked, what result you expected, what happened, and what you will do next. Keep the note next to the project path so the practice stays attached to a real maker outcome.

## Starter state

The board, sensor, datasheet or module page, and a project note are available. Power is off while wiring is inspected or changed.

## Target finished state

The note contains a pin table, voltage expectation, measured or observed reading, test condition, and one next safe adjustment.

## Before starting

- Power off before changing wiring.
- Check voltage requirements before connecting parts.
- Do not assume wire color proves function.
- Use this as a learning checklist, not as a guarantee for a specific board or sensor.
- Keep the first circuit low-voltage and simple.

## Step-by-step lab

1. Write the sensor purpose in one sentence.
2. Copy the board voltage and sensor voltage requirements into the note.
3. Identify power, ground, and signal pins from the source material.
4. Sketch the intended connection before moving wires.
5. Power off and connect only the minimum circuit.
6. Power on and record the expected reading under one test condition.
7. Record the observed reading under the same test condition.
8. If the reading is wrong, check ground and voltage before code changes.
9. Change only one thing: wire, setting, sample condition, or code path.
10. Write the next safe adjustment and stop before adding a second sensor.

## Finished-state checks

- [ ] Sensor purpose is clear.
- [ ] Board voltage is written.
- [ ] Sensor voltage is written.
- [ ] Ground path is identified.
- [ ] Power and signal pins are named.
- [ ] Expected reading and observed reading use the same test condition.
- [ ] The next adjustment changes one thing.
- [ ] The project note says when to stop and verify with a source.

## Common mistakes

- Assuming jumper color proves the pin purpose.
- Connecting power before reading voltage requirements.
- Changing code and wiring at the same time.
- Adding more sensors before the first value is explainable.
- Treating a noisy reading as a software bug before checking ground and measurement conditions.

## Answer key

- A strong answer starts with the source material: pinout, voltage, and signal purpose.
- The first physical action is not wiring; it is a sketch and a power-off check.
- Expected and observed readings must share a test condition, otherwise they cannot be compared.
- If the value is wrong, power, ground, and signal path should be checked before broad code changes.
- The lab is complete when one reading is explainable and the next adjustment is small.

## Commands, artifacts, or checks to inspect

```text
Record board voltage from documentation.
Record sensor voltage from documentation.
Measure voltage with a multimeter before changing the circuit.
Run the smallest read sketch or serial monitor check.
```

## Safety notes

- Power off before changing wiring.
- Check voltage requirements before connecting parts.
- Do not assume wire color proves function.
- Use this checklist for learning, not as permission to work outside your skill or equipment limits.

## Reflection questions

- What did the first check prove?
- Which output, reading, signal, or artifact changed your next step?
- Which tempting shortcut did you avoid?
- What should you study before expanding the project?
- What should be copied into your long-term project notebook?

## Related TopicLadder links

- [Wire a Sensor to a Microcontroller](/projects/wire-a-sensor-to-microcontroller/)
- [Video notes for Wire a Sensor to a Microcontroller](/youtube-notes/wire-a-sensor-to-microcontroller/)
- [Microcontroller Wiring First Checks](/learn/microcontroller-wiring-first-checks/)
- [Multimeter First Measurements Cards](/downloads/multimeter-first-measurements.anki.tsv)
- [Read a datasheet first pass](/learn/read-a-datasheet-first-pass/)
- [Practice index](/practice/)
- [Start Here](/start-here/)

## Project note template

Question:

Expected result:

Actual result:

Interpretation:

Next safe step:

This lab should leave behind a note that can be reopened later. If the note only says that something worked, it is not enough. Write the proof, the boundary, the thing you did not change, and the next step that would make the project easier to continue.

## How to judge the finished note

A finished note should let a future session restart the work without guessing. It should name the original question, the starting condition, the exact check that was performed, the result that was expected, the result that actually appeared, and the reason the next step follows from that result. If another learner cannot tell whether the project is blocked by knowledge, setup, parts, files, configuration, or safety boundaries, the note needs one more pass before the lab is complete.

The note should also keep scope small. A practice lab is not a full course, repair manual, or build diary. It is a checkpoint that proves one layer of understanding. When the lab exposes a missing prerequisite, link the next TopicLadder page instead of copying large source material. When the lab exposes a safety-sensitive question, write the question and stop before the page turns into instructions for work that requires manuals, supervision, or equipment-specific procedures.

## Repeatable run log

Run date:

Project state before the lab:

Smallest check performed:

Expected signal:

Actual signal:

Mistake avoided:

Related note, deck, or reference opened:

Next project action:

## Obsidian backlinks

Use these wiki links to connect this note inside a local maker vault:

- [[TopicLadder]]
- [[Maker Learning]]
- [[Microcontroller Sensor Reading Lab]]
- [[Wire a Sensor to a Microcontroller]]
- [[Project Practice]]
- [[Careful low-voltage electronics practice]]
- [[Sensor purpose board voltage sensor voltage ground power signal pin expected rea]]
- [[Obsidian Project Notes]]
- [[Anki Review Cards]]
- [[Practice Tasks]]

## Source and next routes

Source: https://topicladder.com/practice/microcontroller-sensor-reading-lab/

- [Wire a Sensor to a Microcontroller](/projects/wire-a-sensor-to-microcontroller/)
- [Microcontroller Wiring First Checks](/learn/microcontroller-wiring-first-checks/)
- [Read a datasheet first pass](/learn/read-a-datasheet-first-pass/)