Skip to content

Ask HN: End-of-Line Testing Solution

1 pointstefanhoelzldiscuss
On HN

Hello HN,

I am interested in how other small electronics companies handle their End-of-Line testing and programming.

I am working for a small company (2.5 firmware devs, 2.5 software devs and 1 hardware guy)

We design and sell small electronic devices (RFID Reader), let them produce by a partner company but provides them with custom hardware and software to perform End-of-Line testing and programming.

I have inherited this EOL testing software and now need to maintain and implement new features, but it is a huge mess. So we are looking into replacing everything.

Currently everything is written in Python (the main language for software in the whole company) We flash a custom test firmware the DUT and perform different tests LED flashing Buzzer working RFID range Various Interfaces (USB, Erhernet/PoE, Rs485, Rs232, Bluetooth …) At the end we program the final firmware and configuration into the device and print labels.

Currently everything is homebrewed (software and hardware) and I am interested in more off the shelf solutions which can be customized.

How are you tackling this in your company?

Comments

No comments yet.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.