Skip to main content
Oryx can send the open signal to an ESP32 generator for playback on its outputs.
The link is point to point: everything happens between your computer and the device. There is no server in between and nothing goes out to the internet.

Requirements

Safari does not support Web Serial. Use a compatible browser for USB.

Connecting over USB

1

Connect the board and open Device → USB → Choose port

Select the board’s port in the browser dialog. It may appear as CP210x or CH340; on an ESP32-S3 with native USB, as USB JTAG/serial.
2

Wait for the connection

Oryx retries while the board finishes booting.
Opening the port may reset the board. Oryx retries until the firmware responds.

If something fails

Connecting over WiFi

WiFi connection requires the Pro plan.
The WiFi list shows generators found on the network. When you connect to one, Oryx sends it the open signal. To switch generators, select Back and choose another from the list.
Oryx controls one generator at a time. Disconnecting it stops playback and sets its outputs low.

The first time: put the device on your network

Each device brings up its own network, called Oryx-Signal- followed by four characters that differ on each device. In Device → WiFi, the First time? Put the device on your WiFi row opens a separate window with these three steps and the values to copy; when you are done, Done, search for devices takes you back to the list.
1

Join the device's network

From the computer, join Oryx-Signal-XXXX (password oryx1234). Your system will warn that the network has no internet: that is expected.
2

Pick your WiFi network

The device page opens by itself; if it does not, go to http://192.168.4.1. Pick your network, enter its password and save.
3

Go back to your usual network

The device restarts and joins your network. From then on it shows up in the app’s list by itself.
The network is stored on the device; you change or forget it from the same page. You can also skip the setup and always use it over its own network, but then the computer has to switch networks each time.

Pick the device

In Device → WiFi, the Devices on the network list is searched and refreshed by itself: there is no address to type. If you have several devices, the list displays each one by name.
  • Click one to connect (Connecting to Oryx-Signal-XXXX…).
  • One marked In use has someone else connected: it accepts one link at a time.
  • Back, once connected, lets go of that device and takes you back to the list to pick another, without closing anything.
In browsers that already allow local network links from a secure page, the first time the browser asks whether the site may access devices on your local network: accept and the app talks to the devices directly, with no extra windows. The app detects it on its own; until the browser allows it, it uses the window below.
Otherwise, or if you denied that permission, the search runs in a small window the app opens, served by one of the devices: that is what allows the link from a secure page. Leave it open while you use the devices; if you close it, the search stops. If the browser blocks it, allow pop-ups for the site.

If the device does not appear

Sending the signal

If the signal fits in the device memory (up to 2048 state changes), the device plays it from its own memory: first it receives the whole signal and only then starts. Once loaded, it keeps playing even while you edit something else on screen. If it is longer —millions of steps— the app sends it while it plays: the device has an event buffer (up to 32 768 on the ESP32-S3, fewer on the classic ESP32) that the app keeps full. It never sends more than fits: the device reports every 25 ms how much room it has left. The signal’s timing still comes from the device clock; the link only has to arrive in time. If it does not (very fast signals, or a WiFi that stalls), the output holds for a moment until more data arrives and the signal block warns in red: lower the speed or, if you are on WiFi, connect over USB. Restart from the beginning sends the signal again from the start. The signal is sent by itself: when you connect and every time it changes while you are connected. There is no send button. The signal block shows its name in large type and, below it, the type, channels and steps —“Digital · 3 channels · 240 steps”—, which GPIO each channel comes out of, and a status icon:
What comes out of the device is exactly what you drew, including the analog curves with their rounding.

Adjustment notices

If what you see on screen does not fit into the device as is, the app tells you before sending:

Controlling playback

Return to the editor during playback

While the signal is running, Back to editing offers two choices: The Device button brings the generator back without stopping the signal. If the connection drops or the device reports a problem while you are in the editor, the generator window opens again.

Live parameters

There are two, side by side: voltage and speed. The app remembers them between connections and sends them along with the signal.
From 0 to 99.99 V, with two decimals; it starts at 3.30 V. It is only sent and kept on the device: the firmware does not use it at all, it changes neither the pulse height nor the analog amplitude. It is there for your own code to read and use as your circuit needs.
A single box, with the unit to pick next to it:Switching units converts the number and the signal keeps the same speed. RPM turns an engine sensor signal into an engine speed sweep; bps and Hz are for serial buses (UART, CAN, Modbus) and clocked ones (I2C, SPI). Below the box, the app shows how many µs per step that is.
Changing the speed adjusts playback immediately, like an engine: the pass carries on from where it was. The lap counter is not zeroed: that is what Restart is for.

If the cable comes loose

The signal stops on its own and the outputs go low. It is on purpose: the device cannot find out that you closed the tab, so if it goes a while without receiving anything it treats the link as finished. Connect again to carry on: the signal is sent by itself again.

Board outputs