trending
•

1mo ago

Hardwave's Product Hunt launch, a quick reflection..

Launched Hardwave yesterday.

This has been a solo build for a while, mostly heads-down, mostly alone with the problem. Getting to actually share it, and have people look at it, use it, question it, was the real win for me.

This launch was one data point, not a finish line. Back to building. If you tried it and have thoughts, good or bad, I'd love to hear them.

Thanks to everyone who checked it out.

•

1mo ago

Hardware Builders: What's the last thing that surprised you after assembly, not before?

Motor pulling more current than expected? Thermal issue that only showed up once things were running? A mechanism that worked on paper but not once the electrical and mechanical sides met?

Curious where this bites people most: motor sizing, thermal, control loops, or something else entirely?

•

2mo ago

Building an open source tool to simulate hardware before you build it, I would love early feedback

Hey everyone!!
I'm David the founder of Hardwave.

I came from software into hardware, and the thing that got me was how slow the feedback loop is. In software an IDE yells at me before I even hit run. If I mess something up, I usually know within minutes.

•

1mo ago

Hardwave - Simulate hardware failures before they cost a respin

Know your motor will overheat, your battery will sag, or your drivetrain won't couple, before you spend weeks and a BOM finding out on the bench. Hardwave lets you compose your actual hardware system in Python and stress-test it in software first. As real bench data comes in, fold it back into the model so every iteration starts smarter than the last one.