circuit-debugger_skill

This skill guides you through systematic hardware debugging for Arduino projects, enabling power checks, signal tracing, and component isolation with
  • Python

6

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill wedsamuel1230/arduino-skills --skill circuit-debugger

  • SKILL.md7.2 KB

Overview

This skill is a systematic hardware debugging guide for Arduino, ESP32, and RP2040 circuits. It helps makers diagnose power, grounding, signal, and component faults using step-by-step multimeter and isolation techniques. The goal is to get you from symptom to root cause quickly and safely.

How this skill works

The guide walks through five focused phases: power checks, ground continuity, signal verification, component isolation, and differentiating hardware vs software issues. It explains what to measure, expected values, and concrete fixes for common failures like no power, hot components, intermittent behavior, and nonresponsive sensors. Included are practical multimeter procedures, simple test sketches to upload, and a divide-and-conquer workflow for isolating faults.

When to use it

  • When a board shows no power or wrong voltage levels
  • If components are heating or drawing excessive current
  • When sensors, displays, or motors do not respond
  • For intermittent or random failures that are hard to reproduce
  • When I2C or other buses show communication errors

Best practices

  • Start with a fast visual inspection for damage or reversed polarity
  • Always verify VCC and GND voltages before probing signals
  • Ensure all grounds are common and check continuity with beep mode
  • Isolate the MCU by disconnecting external modules and add parts one-by-one
  • Use proper current-rated supplies and separate motor power from logic

Example use cases

  • Diagnose a sensor that returns no data: check VCC, GND, pull-ups, and run an I2C scan
  • Fix a motor that stalls or jerks: confirm driver wiring, add flyback diode and separate supply
  • Resolve an LED that won’t light: verify polarity, resistor, and PWM vs digitalWrite behavior
  • Track intermittent resets: measure voltage under load to find brownouts
  • Validate pin states with a simple heartbeat sketch to distinguish software from hardware

FAQ

Expect ~4.5–5.5V for 5V logic and ~2.8–3.6V for 3.3V logic as HIGH; LOW should be near 0V.

Why do I2C devices sometimes disappear?

Common causes are SDA/SCL swapped, missing pull-ups, address conflicts, long noisy cables, or weak pull-ups—try a scanner and 4.7kΩ pull-ups.

How do I safely measure current?

Measure current in series with the load using the proper meter input and range. Never place the meter across a power supply like a short.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational