Our six disciplines

We write firmware and embedded Linux, design circuit boards and housings, build end-of-line test stations, and do the validation work a standard asks for. You can hire us for one of these or for the whole device. When we do several, the board, its software and its production test are planned together.

Hand-overs

Where the disciplines meet

Many faults in a device sit where one discipline hands its work to the next. The firmware expects a signal on another pin. A connector misses its opening. The tester can't reach a contact. When we do both sides of a hand-over, these are settled before anything is built.

3ELECTRONICSthe circuit board6VALIDATION ANDCOMPLIANCEproof it works1FIRMWAREsoftware in the chip2EMBEDDED LINUXthe operating system4MECHANICAL DESIGNthe housing5TEST AND PRODUCTIONthe factory test
  • ElectronicsFirmware

    The schematic, which tells the firmware which pin does what.

  • ElectronicsEmbedded Linux

    The device tree, which tells Linux what is on the board.

  • ElectronicsMechanical design

    Board outline and connector positions, so the openings in the housing fit.

  • ElectronicsTest and production

    Test points, where the tester's probes touch the board.

  • FirmwareEmbedded Linux

    How the two processors of a device talk to each other.

  • ValidationFirmware

    Numbered requirements, each with its own test.

  • ValidationEmbedded Linux

    Automatic checks that run on every change.

  • ValidationTest and production

    Requirements and limits that become the steps of the factory test.

Illustration: the main hand-overs between the six disciplines. Most projects have more.
Oleksii Kvasnikov

Oleksii Kvasnikov · Founder and lead engineer

You don't need to know which discipline your problem belongs to

Describe the device and where it stands. Working out who does what is our job.