Spinners

Tier 1: the open safety controller

The Tier 1 design includes a recording interlock, a firmware heartbeat timeout, and console E-STOP and fault acknowledgement. Electrical qualification, station integration and physical stop verification remain incomplete.

The controller is an ESP32-S3 board running firmware published with the product. It connects to the base station over USB-C serial, sends telemetry (current, bus voltage, rpm, fault code) fifty times a second while spinning, and expects a heartbeat from the base station every 200 ms. An active firmware task checks a 500 ms heartbeat timeout and requests stop/fault handling; this is not an independent hardware watchdog or a measured stopping-time guarantee. The intended host interlock requires a recording camera; startup Tier 1 serial selection is wired in spin-server, while runtime UI motor switching and physical-device qualification remain incomplete.

The reference electrical design is unqualified: the former TVS, buck and gate substitutions do not establish a valid protection envelope. Do not use the historical build video to energize or commission a platform. Electrical redesign and assembled-rig testing remain required.

The Operator Console shows a general fault and recovery control. Displaying controller-specific fault codes requires the unfinished controller integration. E-STOP is available on the console.

Tier 2: commercial Bluetooth controllers

Bluetooth controller profiles are planned; station integration and a verified commercial controller remain open. planned Profiles describe controller commands, but the supplied profile is synthetic and no commercial controller has been qualified.

Which should I use?

Neither path is ready to recommend for an event. Tier 1 requires electrical qualification and station integration; Tier 2 requires an integrated adapter and verified controller profile.