Week 5 Signal Evidence Log

Week 5 ends with a fault trace.

Choose one simulated signal problem from the lessons and show exactly where the evidence moves from known-good to uncertain or wrong.

Draw the path

Use arrows to show the full route, for example:

sensor / receiver
→ interface
→ configuration
→ flight-controller processing
→ output mapping
→ ESC / actuator
→ physical response

Circle the last known-good boundary and box the first bad or uncertain one.

Hypothesis table

List at least three possible explanations.

Do not call a hypothesis “rejected” just because you dislike it. Reject it only when the supplied evidence contradicts it.

Configuration record

Name one invisible configuration value that mattered in your case: port assignment, protocol, output mapping, orientation, data rate, or another documented setting.

Explain why a wiring photo alone could not verify it.

Next diagnostic move

Write the single next check that would reduce uncertainty the most.

Avoid “check everything.” State the boundary and the evidence you expect to observe.

Debugging reflection

Answer briefly:

1. Where did you initially expect the fault to be?
2. Which evidence changed your mind?
3. What would the parts-cannon approach have replaced unnecessarily?

Exit standard

A reader should be able to follow your diagnostic logic without guessing which tests you already cleared. If your record only names a broken component, add the signal path that proves why.