Taking A Public Transit Display From Project To Product

We’ve noticed an uptick in “project to product” stories lately, which seems like a fantastic trend to us. It means that hackers are turning out projects that really resonate with people, to the degree that taking the leap and scaling up from a one-off to a marketable product is worth the inherent risk. And luckily enough for the rest of us, we get to learn from their experiences.

The latest example of this comes to us from [Stefan Schüller], who from the sound of things only reluctantly undertook the conversion of his LED matrix public transit sign into an actual product. The original project had a lot going for it; it looked fantastic, it was technologically simple, and it provided a valuable service. But as a project, it made certain assumptions and concessions that would cause problems when in the hands of a customer. Chief among these was the physical protection of the fragile LEDs, which could easily shear off the display modules if bumped or dropped. There were also firmware issues, such as access to the backend API that serves the transit data; requiring each customer to sign up for and configure their own API key is a non-starter for a product.

In the article, [Stefan] enumerates a long list of problems that going from project to product raises, as well as how he addressed them. The API issue was solved by implementing his own service, which acts as a middleman between the official API and his customers. A nice plexiglass and sheet-metal frame serves to protect the display, too. Design changes were made as well, not only to provide better functionality but to make manufacturing easier. [Stefan] also relates a tale of woe with regard to getting the display’s app into the app stores, something that few of us have to deal with when we’re just fiddling around with something on the bench.

All in all, [Stefan] does a great job walking us through the trials and tribulations of bringing a product to market. There are similar lessons in this production run scale-up, too, but with an entirely different level of project complexity.

Lessons In Mass Production From An Atari Punk Console

Sometimes the most interesting part of a project isn’t the widget itself, but what it teaches you about the manufacturing process. The story of the manufacturing scale-up of this Atari Punk Console and the lessons learned along the way is a perfect example of this.

Now, don’t get us wrong — we love Atari Punk Consoles. Anything with a couple of 555s that bleeps and bloops is OK in our books. But as [Adam Gulyas] tells the tale, the point of this project was less about the circuit than about the process of making a small batch of something. The APC was low-hanging fruit in that regard, and after a quick round of breadboarding to decide on component values, it was off to production. [Adam] was shooting for 20 units, each in a nice enclosure and a classy package. PCB assemblies were ordered, as were off-the-shelf plastic enclosures, which ended up needing a lot of tweaking. [Adam] designed custom labels for the cases, itself a fraught job; glossy label stock and button bezels apparently don’t mix.

After slogging through the assembly process, boxing the units for shipping was the next job. [Adam] sourced jewelry boxes just a bit bigger than the finished APCs, and rather than settle for tissue paper or packing peanuts, designed an insert to hold the units snugly. That involved a lot of trial and error and a little bit of origami-fu, and the results are pretty nice. His cost per unit came out to just a hair over $20 Canadian, including the packaging, which is actually pretty remarkable for such a short production run.

[Adam] includes a list of improvements for larger-scale runs, including ordering assembled PCBs, outsourcing the printing processes, and getting custom boxes made so no insert is needed. Any way you cut it, this production run came out great and teaches us all some important lessons.