Skip to main content
The digital file holds one row per change. Between one row and the next the outputs stay as they are, so a thousand-step signal usually fits in a few dozen rows.

Structure

  • The first column is the step where the change happens.
  • The rest are the value of each channel, in timeline order, with the channel name as the header.

Reading rules

A new row appears only if some channel changed value. Repeating the previous state would add nothing.
If the last change happened before the end, a row is added with the final step and the values still in force. That way the total length is inside the table and not a separate piece of data.
A divided channel produces rows at positions like 3.333333. They are written with up to six decimals.
A channel split into thirds and another into quarters do not share a grid. At a time point that is not its own, a channel carries forward its last known value instead of being read at a position it does not have.

With metadata

At the end of the file, after a blank line:

How to play it back

The idea is straightforward: read a row, set the outputs to those values, wait until the step of the next row, and repeat. The time per step comes from STEP_TIME if you exported the metadata; otherwise you set it in the code. To play it from a microSD card with the Oryx firmware, see Generate the signal with an ESP32.

RX channels

If any channel is a receive channel (see Reception), the file says so at the end, after a blank line, on every plan (even without exporting metadata):
  • RX_CHANNELS: the columns (counting from 1, not counting the step column) the device does not output: it listens to them and compares them with their values.
  • IO_CHANNELS: shared lines, output open drain and listened to at the same time.
  • RX_TOLERANCE (steps): how far a received edge may shift.
The values of an RX column are what is expected on that line. Reception starts with the signal’s lap and ends at its last step. A table cannot say which stretches of a shared line belong to the other side (I2C acknowledgements): an executor reading this file outputs the drawing open drain and compares the line. For protocol-level execution use the Oryx Signal Format (.osf). In the step-based .json, the same information goes in reception:
If no channel receives, the file comes out exactly as before. Importing a file with these lines brings the channels back with their direction.