Skip to main content
This is the help that opens from the question mark in the export window. The exported file is played from a microSD card with the Oryx firmware: it turns an ESP32 into a standalone unit that reads the digital and analog files exactly as the app writes them, and is driven with an OLED screen and encoder or over the serial monitor.
This is a different firmware from the one in Connect the device. Here the micro reads a file from a card and plays it on its own; there the app sends it the signal live and controls it. Each board holds one at a time: with this one flashed, the board does not appear in Connect device. In the app, the question mark next to the guide’s title is a reminder.
It runs on the classic ESP32 and on the ESP32-S3. The S3 has no DAC: with it the player only plays digital files, and says so on screen if you open an analog one.

Flash the firmware

In Export, the code icon next to the title opens the guide. With the ESP32 plugged in over USB, Flash from the browser → Flash and pick its port. It flashes the latest published version, the one for the board’s chip (ESP32 or ESP32-S3). Works in Chrome, Edge and Opera.
The code lives on GitHub (oryx_signal_sd.ino), and the help reads it from there every time it opens.

Wiring

In the app, the guide has this wiring in the Wiring block, with a switch for each board.
The ESP32 outputs are 3.3 V. If your circuit runs at 5 V you need a level shifter.

Use

Copy the exported .txt files to the microSD card. The unit lists them by folder and tells digital from analog on its own. At power-up it shows Oryx Signal Studio and, below it, TEST CODE. It reads digital files with up to 16 channels. The first 4 go out on their pins; channels 5 to 16 are kept in memory only when the file has them, and in the sketch they sit in extraChannels (bit 0 = channel 5) and the empty writeExtraChannels function, for your code to send them wherever you need. Opening a file starts playback right away. Speed is set in the unit you pick, same as in the app: With the screen, opening a file shows Speed unit: the four units, each with the speed it would start at, with the last one you used highlighted (it is remembered even after a power cycle). Pick one with the encoder and click to play; hold to go back to the files. While playing, the speed is edited digit by digit: turning moves the cursor between the digits, the unit and Pause; clicking a digit starts editing it (it blinks) and turning raises or lowers it, with the signal changing live; another click finishes. Clicking the unit switches it without changing the speed (a double click does too). Over the serial monitor, play starts right away in the last unit, and unit and speed change it. The starting amount of speed comes from the file: its STEP_TIME (us) first; if it has none, its RPM; with neither, the last speed used. It is shown converted to the unit you pick. VOLTAGE is read and kept in the firmware but does not change the output: it is there for your own code to use.
The microSD player does not receive. If the file has receive channels (RX_CHANNELS or IO_CHANNELS, see Reception), their pins stay inputs and are never driven, so they do not fight whatever drives the line. To compare responses, use the generator over USB or WiFi.

Big files

A digital file is first read once, in blocks, with the progress on screen (Reading 37%). If its events fit in memory, it plays from there as always. If not —millions of steps, for example— it plays while being read from the card: a 4096-event buffer keeps filling behind the playback and, at the end of the file, it goes back to the start without cutting the signal. Every event lasts exactly what it would from memory. The card has a read limit (around 1 MB/s, about 50 000 events per second with 4 channels). Faster signals outrun it: the output holds for a moment until more data arrives, the screen shows SD too slow: lower speed and status counts those gaps as underruns. The screen and the encoder keep responding. While a big file plays, ls and cd wait until you stop it. The shortest steps (down to 2.5 µs: 200 kHz clocks, 400 000 bps) only hold with files that fit in memory. Time is measured with the processor’s cycle counter, so every edge lands within a fraction of a microsecond of where it should.

With screen and encoder

Over the serial monitor

At 115200 baud. It is always on, with or without a screen. On the ESP32-S3 it answers on both connectors of the board: the native USB one and the bridge one.