- Optimi
- Services
- Embedded systems and hardware
- Test every device automatically with a report for each serial number
Test every device automatically with a report for each serial number
A test system that measures each device in a few minutes, says pass or fail right away, and stores the readings by serial number.
You build a device, a controller, or a sensor module, and before it ships, someone has to check that it works. Today that is a technician with a multimeter, a power supply, and a paper checklist. They measure a few voltages, check that the LED lights up, and sign off. With ten units, that works. At a hundred units a month, it becomes a full-time job. And when a device comes back from the field six months later, nobody knows what was measured on that serial number.
Test what can fail in use
Manual testing has two problems. The first is time: every measurement a person makes costs minutes, and those minutes add up with every device you build. The second is that it never goes the same way twice. One colleague measures strictly by the list, another skips a step because it is always fine anyway. A device that sits just inside the limit passes one day and fails the next. And the result exists nowhere except on that sheet of paper in a binder.
We build a system that does the measurements itself, and we start with the faults you actually see today: the loose connector, the misplaced component, the sensor just outside its specification. A handful of measurements separates a good device from a bad one. Voltages at the right points, current draw at rest and under load, communication with the sensors, and whether the firmware does what it should when you send it a command. Not a hundred things: a system that measures a hundred things is slow and breaks at the first change to your product.
Make the fixture easy to operate
The device goes into a fixture, you press one button, and a minute later the screen shows green or red, with the readings next to it. The same measurements, the same limits, every time. What your team keeps is the work a person is actually needed for: looking at the device that got red.
The hardware is usually less exciting than you think. A fixture the circuit board clicks into in one motion, a few test probes, and instruments you often already have on the bench: a power supply, a multimeter, an oscilloscope, controlled over USB or Ethernet. We write the software around it, readable, so your own people can adjust a limit without calling us. If you are working on a new design with our PCB and electronics design service, we plan the test points on the board right away, because a trace you want to measure later has to be there.
Store more than pass or fail
Every test writes its readings away, linked to the serial number of the device. That seems like a detail, until a client calls. Then you can look up what that one device did when it left the building, and whether the devices from the same batch have something in common. You also see trends: a current draw that slowly climbs over the weeks, before it becomes a problem.
That data lives in a database of your own, on a server in the EU or simply on the test system itself, and you get the source code and the drawings with it. You are the owner.
Keep the test system trustworthy
We do not start with a forty-page test plan. We come by, watch the person who tests today, and pull out the devices that came back recently. That tells us which measurements really matter. Within ten business days, there is a first setup on your bench that runs those measurements on your own devices. No nice enclosure, but real readings.
You run a batch with it. Usually something comes up that we had not foreseen: a limit set too tight, a measurement that says more than we thought, a device that gets green and still does not work. That is exactly what the prototype is for. We tighten the setup, and only then make it final, with a sturdy fixture, a calibration procedure, documentation, and short instructions for the people who use it every day. We use the same setup at the end of the line when we build for you in Small-batch manufacturing. And if your product has to be certified, part of these measurements shows in advance whether you will pass what CE and EMC certification asks. The formal measurement is done by a lab, but you want the surprises out of the way before then.
01, RESULT
- A test fixture the device connects to in one motion
- Test software that runs the measurements and reports pass or fail
- A measurement report per serial number in your own database
- A calibration procedure and the limits on paper
- Source code and drawings that you own
Process diagram
02, HOW WE WORK
-
We watch how you test today and which faults only show up at the client.
-
We decide which measurements really say something and which limits go with them.
-
Within ten business days, we build a first setup that you run on real devices.
-
You test a batch with it, and we tighten the measurements and the limits.
-
We deliver the final setup with software, documentation, and instructions for your team.
FAQ
FAQ
We only make a few hundred devices a year. Is a test system worth it?
Often it is, because one return from the field quickly costs more than a day of testing. We work it out with you in the free intake. If a better checklist and a few fixed measuring points turn out to be enough, we tell you right away.
How does a test system help with certification?
We build setups that show in advance whether your product will pass what CE and EMC certification requires, so you do not face surprises in the lab. The formal measurement is done by an accredited laboratory, and we support it.
Which measuring equipment do you use?
Usually the instruments already on your bench: a power supply, a multimeter, and an oscilloscope, controlled over USB or Ethernet. Only when a measurement really needs something special do we buy extra. We use the same setup at the end of the line in Small-batch manufacturing.