DISTRIBUTED SHOW CONTROL · ESP32

Run the show.
Not the browser.

Showduino separates creative control from live runtime. Build a production in Studio, operate from the Director, and let the ESP32-P4 Show Engine remain authoritative when the browser, Wi-Fi or touchscreen are nowhere to be found.

PHYSICAL SYSTEMThe current enclosure and Director exist as real development hardware.
LOCAL AUTHORITYThe ESP32-P4 owns show state, safety, timeline execution and cue dispatch.
SPECIALIST NODESRelay, MOSFET, pixel and audio roles stay separate and diagnosable.
Showduino control hardware with touchscreen Director, emergency button, antennas and accessible connections
Current Showduino hardwareProduct visual based on the development unit
THE CURRENT ARCHITECTURE

Four jobs. Clear responsibility.

The current Showduino system is deliberately split so operator controls, transport, show decisions and physical outputs cannot accidentally become the same job.

01 / DIRECTOR

ESP32-S3 Director

The 800×480 touchscreen is the operator desk. It requests actions, displays state and keeps the live controls clear.

ESP-NOW →
02 / TRANSPORT

S3 Comms Controller

A dedicated bridge between wireless devices and the P4. It transports messages; it does not make show decisions.

UART 115200 →
03 / AUTHORITY

ESP32-P4 Show Engine

The runtime authority for state, timeline, safety, cues and emergency behaviour. The show lives here.

COMMANDS →
04 / ACTION

Specialist Nodes

Relay, MOSFET, pixel and audio nodes perform commanded work and report results back to the system.

ACTUATE + REPORT
Studio creates it. Director operates it. P4 runs it. A live production does not need the browser, internet or touchscreen to keep the timeline alive.
PHYSICAL PRODUCT

The enclosure follows the architecture.

The current controller is built around practical operation and serviceability, with the touchscreen Director, physical emergency control and accessible equipment connections treated as deliberate parts of the system.

Operator hardware

Adjustable touchscreen Director

The interface is a real physical operator surface, not the thing responsible for continuing show execution.

Physical safety

Emergency control stays obvious

The dedicated emergency control is deliberately separated from touchscreen UI actions and normal show cues.

Serviceability

Connections stay accessible

Pluggable terminals, USB, Ethernet and antennas are treated as equipment interfaces rather than development-board clutter.

PIXEL SYSTEM

Segmented in the show. Unmistakable in an emergency.

Pixel lines can be divided into logical segments for show effects, while the emergency state overrides every line and drives every pixel bright white.

SHOW MODE · EXIT SIGN SEGMENTSexample: pixel 0 / 10 / 20 green

The same physical line can remain visually useful during a production while preserving logical emergency-sign groupings.

EMERGENCY OVERRIDEall pixels · bright white

Emergency state wins over show effects. The visual override is system-wide, not limited to a decorative emergency strip.

CURRENT ROLLOUT

Finish the useful core first.

The current development path concentrates on the systems that already matter to a real attraction.

RLY

Relay outputs

Commanded switching with node state and fault reporting as the target behaviour.

MOS

MOSFET outputs

Efficient control of compatible low-voltage effects and loads.

PIX

NeoPixel lines

Segment-aware effects plus a hard emergency-white override.

AUD

Audio node

Dedicated show audio nodes alongside local P4 system sounds.

SOFTWARE

Create separately. Run locally.

CREATION

Showduino Studio

Build productions, arrange timeline events, define routing, preview effects and export portable `.shdo` project files. Studio is a creator and deployment tool — not the live show engine.

PROJECT HUB

HauntSync

Keep track of projects and the real Showduino hardware roles: Director, Comms Controller, Show Engine and specialist nodes.

Want the architecture without the marketing?

The System page breaks down responsibilities, transports, emergency behaviour and the current hardware scope.

Open System Guide