Examples

Button counter

Every press adds one, shown on a four-digit seven-segment display.

Arduino Uno R31 libraries29 linesOverall confidence 100%

SourceRead onlyuno_button_counter.ino

// Counter: every press of the button adds one, shown on a 4-digit display #include <TM1637Display.h> #define DISP_CLK 4 #define DISP_DIO 5 #define BTN_PIN 2 TM1637Display display(DISP_CLK, DISP_DIO); int count = 0; bool wasDown = false; void setup() { Serial.begin(9600); pinMode(BTN_PIN, INPUT_PULLUP); display.setBrightness(4); display.showNumberDec(0, true); } void loop() { bool down = digitalRead(BTN_PIN) == LOW; if (down && !wasDown) { count = (count + 1) % 10000; display.showNumberDec(count, true); Serial.print("count "); Serial.println(count); } wasDown = down; delay(30); // crude debounce: the contacts settle well inside this }

What the parser saw

Extracted from #include · #define · pinMode · constructor arguments. The output of a deterministic parser, not an AI.

Parts

tm1637#include <TM1637Display.h>

90%

buttonidentifier BTN_PIN

60%

Buses

—

Libraries

#include <TM1637Display.h>

Pin contract

An immutable contract owned by the project. It survives level changes; on a target board only the physical pins are remapped.

Logical name	Pin	Direction	Signal	Declared as
BTN_PIN	D2	in	digital	#define
DISP_CLK	D4	unknown	digital	#define
DISP_DIO	D5	unknown	digital	#define

This page passes no verification gate. Logic (simulator), electrical (ERC · DRC) and physical (your confirmation) verification each run separately inside a project.

Next step

Same sketch, from simulation to PCB

The code stays as it is. Run it on avr8js in the Playground; import it into a project and the 8-pass electrical verification, KiCad board generation and Gerber export follow.

Run in Playground Import into a project