PajoniiirStandalone DJ System

Choose your board

JC4880, JC1060 and M3 share the playback, library, controller, UI, web and OTA core. Their peripherals, USB connector labels, audio outputs and network providers differ.

JC1060 physical acceptance is NOT RUN, deferred to contributor Kayrosen. Its beta kit and first-test handoff define the bring-up scope. JC4880's later short Hercules checks are accepted on their recorded image; its long soak was explicitly waived, not passed. Historical M3/controller campaigns remain tied to exact images. See board policies and electrical/wiring instructions.

Supported DJ controllers

Use the matching compiled controller profile and firmware configuration. A profile being available does not establish complete physical support on every board.

Controller setup

1. Choose the appropriate board image and port policy. Keep the reference FLX4 arrangement unless using a documented experiment.
2. For S2 MK3, hold the left FLX button while connecting USB to enter MIDI mode; release after the green flash. Hercules connects normally without holding buttons.
3. Install only a matching compiled profile.s3bin through the profile service, then confirm the active profile and MIDI/audio availability. The beta includes profiles separately from firmware.
4. Raise headphone volume gradually. Enable D1/D2 PFL before judging cue sound; native Hercules headphone Mix/Volume controls act on the controller itself.

A limited S2 basic profile and generic MIDI-CI fixture are also supplied for development; these are not additional hardware-qualified DJ models. Full support and historical acceptance are detailed in the repository's controller records.

Quick start · JC4880 / FLX4 reference

The ESP32-P4 is the sole runtime authority. It plays the tracks, owns deck and mixer state, drives the display and communicates directly with the FLX4. The physical controller, touch UI and browser Remote Control all operate the same P4-owned state; no performance computer is required.

For M3 or JC1060, substitute the ports, audio and network provider in the board table; the steps below retain the JC4880 reference setup.

Connections and signal roles · JC4880 reference

Power note: downstream USB VBUS must be protected and current-limited. Do not join independent supplies with a passive Y-cable and do not inject raw 5 V into USB-C pins.

On-device display

The P4 LVGL interface provides the primary stand-alone visual surface. It remains independent of whether Wi-Fi Remote is enabled.

DDJ-FLX4 core controls

The DDJ-FLX4 is the main physical performance surface while the P4 owns playback, mixer state and DSP. Controller LEDs are driven from P4-owned state.

Mixer and monitoring

Performance pads and effects

Rekordbox USB library

Use the music port assigned to your board (USB0 on the JC4880 reference build). The P4 reads the exported library and analysis data, exposes tracks in Library, and uses available BPM, beatgrid, waveform and cue information.

For best results, prepare the medium with Rekordbox export before use. Do not remove USB0 while a track is loading unless you are intentionally testing recovery behavior.

Embedded Web Controller

Pajoniiir contains its own HTTP web server and browser-based remote interface. The page is served directly by the P4; it is not a cloud service and does not require an external web server. A phone, tablet or laptop connected to the device AP can become an additional operator surface.

Open the Web Controller

What the browser can control

The browser polls live status frequently and continuous sliders are rate-limited before commands are sent to the embedded HTTP server. If the connection indicator goes offline, stop issuing commands and verify the Wi-Fi state before continuing.

Wi-Fi AP and STA modes

The AP provides local browser control; the STA uplink reaches a service network. JC4880 temporarily leaves its AP during service visits. M3 keeps AP services alive while adding the STA uplink (AP+STA); clients may briefly reconnect when the radio changes channel.

AP / SoftAP — normal remote operation

The firmware also advertises the mDNS hostname pajoniiir.local. mDNS support varies by operating system and client configuration, so the fixed AP address 192.168.4.1 is the recovery/fallback address.

STA — temporary service/update network

STA exists so the deck can temporarily reach an external network, primarily for update-server connectivity. It is not the normal browser-remote mode. JC4880 stops its AP web/DNS services for the visit, waits for service-network DHCP, performs the operation and restores AP/web afterward. M3 retains its AP netif, lease and HTTP/DNS services during the added STA uplink; a radio channel change can briefly interrupt a client. Neither behavior makes the AP an Internet router.

Updates, beta installation and controller profiles

The current P4-only product has two signed firmware-update workflows: local browser upload while connected to the Pajoniiir AP, and a pull-update flow that temporarily joins a configured service network.

Before installing a beta

Download shared-p4-beta.2 from GitHub. The jc4880-beta-kit.zip, jc1060-beta-kit.zip and m3-beta-kit.zip include board identity, signed OTA, recovery files, configuration and SHA-256 inventories. Select by board/project, verify the signed manifest and checksums, and keep the matching debug archive. Beta2 retains the exact M3/JC4880 images with their recorded acceptance; JC1060 physical testing is still NOT RUN. After updating FLX4 firmware, start headphone LEVEL low and raise gradually: beta2 restores the cue level lost in the previous transport.

Historical M3 firmware named main-deck-p4 needs the preserving wired identity migration before main-deck-m3 OTA. Application OTA cannot change a partition table; verify board/layout before wired recovery and never perform an indiscriminate full-chip erase.

A. Local signed OTA upload

The P4 validates the signed package before activating the inactive OTA slot. The update design checks the embedded ECDSA signature and signed image metadata including image size/hash, chip, project and version. Wrong-target or tampered bundles are intentionally rejected.

B. Update Server / pull OTA

The UPDATE SERVER panel in the Web Controller configures the external network that the P4 may visit temporarily. It is separate from the normal Pajoniiir AP credentials.

C. Controller profile service

Upload only compiled profile.s3bin: M2.5 accepts S3CP v2/v3/v4. The compiler chooses the oldest representable version; bare historical M2.4 accepts v2 only. Never convert a profile by editing version bytes. Choose the SD profile ID and enable overwrite only intentionally. Length/CRC and binding epoch are validated; v4 initialization precedes LED feedback. Successful installation does not qualify a non-FLX4 controller.

D. API and remote-control safeguards

The embedded API accepts the canonical Pajoniiir host identity / active AP address and state-changing browser requests use a dedicated control-request marker. These checks are part of the current protection against accidental cross-site mutations and DNS-rebinding-style access. The AP is a local service surface. The shared service-password risk remains explicitly accepted for this deployment; firmware authenticity remains protected by signed OTA. Revisit per-device credentials before wider deployment if the exposure model changes.

Power, shutdown and handling

Stable M2.5 and shared P4 beta