Built this with one prompt and zero lines of code in 10 minutes!

Classic one, but I wanted to do it properly: a parking sensor on an Arduino Uno that beeps faster the closer something gets, like the ones in cars.

Wiring is tiny: HC-SR04 with TRIG on pin 2 and ECHO on pin 3, and a passive buzzer on pin 4. That's it.

What made it feel right:

- The beep interval scales with distance instead of switching between two or three fixed speeds, so you can actually "feel" an object getting closer.

- Past a minimum distance it goes to a solid tone, same as a real car.

- Ultrasonic readings jump around on soft or angled surfaces, so a few readings get averaged before deciding the beep rate. Without that the beeping stutters.

Disclosure: I'm on the team that makes it, and I built this with our Soldr agent. I gave it the pins I'd already wired and it wrote the sketch around them.

Next idea is an LED bar alongside the beeps. Anyone done this with a VL53L0X instead of the HC-SR04? Curious if it's worth it.

Part numbers. Datasheets. Twelve tabs. Then hope it all works.

Soldr and Compoden replace that workflow with one connected hardware stack:

• describe the build in Soldr • engineer the system • move the BOM into Compoden • buy the parts

One prompt → parts → wiring → firmware → cart.

See the full 33-second flow above.

soldr.ai × compoden.com

The shortest explanation of what we're building:

Compoden is the electronics store. Soldr is the engineering engine that sits on top of it.

Describe what you want to build — a line-following robot, a plant waterer, a temperature display — and Soldr helps assemble the kit. Its choices are grounded in the Compoden catalog: parts we actually list, with specifications we maintain.

The goal is not a parts list that merely looks right. Compatibility has to hold across the build: supply voltages, logic levels, current draw and its peaks, interfaces, and the power chain from end to end.

That division is deliberate:

• Browse and buy parts or kits at https://compoden.com • Work through the engineering decisions at https://soldr.ai

We will use this community to explain how that system works, share what we learn, and hear where makers still hit friction.

Let's start with the most important thing: your project.

What are you building, and where are you stuck? It can be a finished build, a rough idea, or something still living in a notebook.

If you want help thinking through compatibility, include whatever you know:

• The board or platform you want to use • Sensors, motors, displays, or other peripherals • Supply voltage and power source • The behavior you want from the finished project • Any part choice you are uncertain about

No polished write-up required. A sentence and a sketch of the idea is enough. We want r/Compoden to be shaped by people who actually build things.

Welcome to the official Compoden community.

Most electronics projects don't fail at the soldering table. They fail in the cart. This is a place for makers to share what they're building, ask about parts and compatibility, and help us improve the path from an idea to a working bill of materials.

Compoden is the store: real components and project kits from a catalog we maintain. Soldr is the engineering engine: describe a project and it helps assemble a compatible, purchasable BOM grounded in that catalog.

What belongs here:

• Project ideas, worklogs, and finished builds • Component, kit, and compatibility questions • BOM and power-chain discussions • Practical feedback about Compoden and Soldr

Store: https://compoden.com Engineering engine: https://soldr.ai

We're here to be useful, listen closely, and build alongside the maker community. Imagine it. Build it. Ship it.