AI Craft Pad

FixtureOS — Production Testing for Small Hardware Teams

FREE DOWNLOAD · WINDOWS 10/11 · VERSION 0.1.0

FixtureOS

One clear test record for every board.

Flash firmware, run checks in order, record operator decisions and save PASS or FAIL with the device serial number. Built for small electronics teams and repair workshops.

✓ Runs locally on your PC   ✓ CSV and PDF reports   ✓ No account required
FixtureOS logo

Production testExample · NANO-001 · Batch TEST-01
01   Program firmwarePASS
02   Identify devicePASS
03   Protocol responsePASS
04   Visual inspectionPASS
Example shown for illustration. Your recipe defines the actual checks.
Arduino + ESP32Board and flashing profiles
Step-by-stepAutomatic and manual checks
PASS / FAILEvery run saved locally
CSV + PDFExport records when needed

From connected board to recorded result

Give each device the same repeatable sequence. The operator sees what to do next and the history keeps the outcome tied to its serial number.

1

Prepare the station

Choose a board and COM port, load a recipe and select the compiled firmware file. Check setup before starting.

2

Run the recipe

FixtureOS flashes the board, checks serial replies and values, then asks the operator for visual decisions where needed.

3

Keep the evidence

Review PASS or FAIL by step. Save the run locally, then export CSV history or a PDF report.

Built for everyday production

Firmware flashing

Use avrdude for Arduino AVR or esptool for Espressif boards with a prepared HEX or BIN image.

Serial checks

Send a command and compare the device response with the value your recipe expects.

Numeric checks

Check values reported over the device protocol against configured limits. A protocol reply is not an independent voltage measurement.

Operator inspection

Add a clear manual step for LEDs, buttons, enclosure condition or another visible check.

Traceable history

Keep serial number, batch, board, firmware digest and individual step results together.

Reusable recipes

Create and save test sequences so the next unit follows the same process.

Board profiles

Arduino AVR

Uno, Nano, Nano old bootloader, Pro Mini, Mega 2560, Mega ADK, Leonardo and Micro.

Espressif

ESP32, ESP32-S2, S3, C2, C3, C5, C6, H2 and P4 profiles.

Board profiles select flashing parameters. Verify each production recipe and firmware on the actual hardware before relying on the result. The Nano workflow has been physically exercised; other profiles still need board-specific validation.

Two starting examples

Arduino Nano

Load recipes/nano.json, select Nano, its COM port and a compiled .hex file. The sample firmware answers PING → PONG and returns a 5V protocol value before visual inspection.

ESP32-S3

Load recipes/esp32s3.json, select ESP32-S3, its COM port and a merged .bin at offset 0x0. The sample sequence checks the serial reply and a 3.3V protocol value.

FREE WINDOWS DOWNLOAD

Start a repeatable test station

FixtureOS 0.1.0 installer for Windows. Install it, connect one board and run a recipe. The test history stays on your computer.

Download FixtureOS ZIP ↓

Publisher: AI Craft Pad. The ZIP contains the Windows installer. Firmware files and physical boards are supplied by you.

Get started in three steps

  1. Download the ZIP and extract the installer.
  2. Install FixtureOS and open the application.
  3. Choose a recipe, board, COM port and firmware file; press Check setup, then Start test.

Questions before you start

Does FixtureOS test several boards at once?

Version 0.1.0 runs one board at a time on one workstation. Each unit receives its own serial-numbered result.

Do I need to write a program?

You can edit recipes in the visual editor. Automatic serial checks still require firmware that speaks the commands your recipe expects.

Does the 5V or 3.3V check measure the physical rail?

The included sample recipe checks a value returned by the device protocol. A physical voltage measurement needs a suitable external measuring circuit and a corresponding recipe step.

Is an internet connection required?

No account or cloud service is required for testing and local reports. Board tools such as avrdude or esptool must be available on the station.

Scroll to Top