Reception is available on every plan, Basic included: setting up RX
channels, running, comparing responses, seeing the diagnostics and exporting
with reception data.
Switching a channel
1
Open the channel settings
On the channel’s name card, the button on the right (the palette, or the
TX/RX label once the project already has receiving channels).2
Pick the direction
TX, RX or TX/RX. The drawing does not change.
Ctrl + Z, and it
travels when duplicating, sharing, saving as a template, importing and
exporting.
While no channel receives, the timeline looks as always. With at least one,
every channel shows its TX ↑ or RX ↓ label next to its name: you tell them
apart by the text and the arrow, not by color, which stays the signal’s.
Generators set the direction for you
The direction is set when the generator takes the channel. If you change
it by hand afterwards, it is kept: editing messages or regenerating does not
overwrite it. Channels you create by hand start as TX.
A TX/RX conversation with UART
1
Build the request
In the UART generator, write the message on TX (for example
AT\r).2
Draw the expected response
Write on RX the response the device should send back (
OK\r\n), where
you expect it in time. The RX channel is already set to receive.3
Run
Open Device, connect the ESP32 and press Start. The device outputs
TX and listens to RX during the signal’s first lap.
4
Read the result
The Reception section of the panel shows the verdict of each RX
channel, with what was expected and what was received. Capture another
lap repeats the test without stopping the signal.
Results
Each verdict comes with its cause when the capture shows it:
Oryx does not claim a cause the device cannot see: for example, it does not
report a CRC if the protocol has none.
How it compares
- UART, SPI and I2C are compared by content: bytes, MISO words, addresses, reads and acknowledgements, with the same interpreters that draw the editor’s bars. A response that arrives somewhat later than drawn is still correct.
- Signals without a protocol are compared edge by edge: each expected edge must show up, in the same direction, within 1 step of where it was drawn.
- Analog signals are compared against the curve: each sample must fall within 5 % of full scale (0.165 V) of the drawn curve, at some point within 1 step. Up to 2 % of samples outside is taken as noise and only flagged. Cycles are also counted to report a different frequency.
- Expected and received are shown together in a small drawing, with the differences marked.
SPI and I2C
- SPI: the device outputs clock, MOSI and CS, and compares every MISO word with the drawn one.
- I2C: the device outputs SCL and drives SDA open drain. On writes it releases the line on the acknowledgements; on reads, on the bytes the peripheral sends. What arrives is compared as transfers (address, data, ACK/NACK). The bus needs its pull-up resistors.
Analog signals
In an analog project, an RX channel is the curve you expect to measure. When running it is not output by the DAC: the device measures it with its ADC while playing the TX channels, one lap per start, like in digital. An analog project may have only RX channels: the device outputs nothing and measures for as long as the curve lasts.The ESP32-S3 has no DAC: in analog it outputs nothing, but it does
measure. With an S3, the TX channels of an analog signal are not output (the
panel says so) and RX channels are measured as usual. Handy to use it as a
meter for a signal another device generates.
- Each lap takes up to 2000 samples per input, spread across the lap and at most one every 200 µs (less often with several inputs). The panel says how many steps apart the samples were: if the curve changes faster than that, lower the speed.
- It measures with ADC1 and the chip’s calibration. The ESP32 ADC is inaccurate near 0 V and above ~3.1 V: leave some margin at the ends.
Requirements and limits
Exporting with reception
- Oryx Signal Format (.osf): when the whole signal is UART, SPI or I2C, it is offered as the recommended option. It describes operations (write, expect, read) with the expected responses. See Oryx Signal Format (.osf).
- Step-based TXT, CSV and JSON: they carry which columns are RX. See Digital format.