SOFTWARE

Every device we build runs code we wrote for it. Firmware is where the hardware stops being a schematic and starts being a product.

It is responsible for device logic, communication, configuration, and real-time operation — reading sensors and controls, driving outputs on a deadline, holding settings across power cycles, and keeping the device answering while it does all of it.

Because the firmware and the board are developed together, neither has to work around a decision the other made in isolation.

On top of the firmware we create dedicated software for managing and controlling our hardware from computers, mobile devices, or web interfaces.

These tools can provide detailed configuration, monitoring, data gathering, and real-time status information — the settings a front panel has no room for, the live view of what the device is doing, and a record of what it did.

The same device can be addressed from a desktop application in the workshop, a phone on the floor, or a browser on the network, depending on where the work actually happens.

Where needed, we also develop systems for processing, analyzing, and visualizing the data generated by our devices.

A stream of readings is not a result. These systems take what the hardware captures and put it into a form a person can act on — logged, filtered, aggregated, plotted, and exported into whatever the next step expects.

Our software can communicate through USB, MIDI, Bluetooth, network protocols, and other interfaces depending on the application.

The protocol is chosen for the job rather than for our convenience: a controller that has to appear as a standard instrument speaks the standard, a device on a bench speaks whatever the bench already runs, and a device on a network is reachable from anywhere on it.

Where a system uses no standard protocol at all, the necessary bridge can be written on the software side.

We create custom integration solutions that allow our hardware and software to work with existing systems and workflows.

Most of the time a new device is not arriving into an empty room. It has to sit alongside equipment, software, and habits that are already working, and the integration is what decides whether it extends that setup or fights it.

The aim is always to extend what is already in place rather than to replace it.

Beyond customer-facing products, we develop internal tools and utilities whenever existing software cannot meet a specific requirement.

These solutions help us with development, testing, calibration, production, and specialized in-house workflows — the test rigs, the calibration routines, and the production utilities that make a small run repeatable.

In this way, software becomes a natural extension of our hardware, allowing us to build complete, connected, and purpose-driven systems.