Skip to main content
In digital mode, Oryx can read a channel’s cells as the bits of a protocol frame, one bit per cell, and display its fields on the signal.
Protocols are interpreted in digital mode only.

How a frame is written

1

Draw the bits

Every step is one bit: nothing needs to be divided. Set each step to the required high or low level.If you split steps with Division (D), every sub-step becomes one bit. Use it to fit a whole frame into a few steps.
2

Pick the protocol

With the Protocol control in the header: None, UART, CAN, I2C or Modbus.
3

Read the interpretation

The interpretation appears below the channel, divided into fields.

A full example: sending the letter “A” over UART

The letter A is 0x41, or 01000001 in binary.
1

Set the protocol to UART

The Protocol control in the header. Leave the default format: 8 data bits, no parity, 1 stop bit, LSB first, idle high.
2

Work out how many bits you need

With that format, one character takes 10 bits: 1 start + 8 data + 1 stop.
3

Use 10 consecutive steps

Every step is one bit, so the character takes 10 steps of the channel. If you’d rather fit it into a single step, split it into 10 with Division (D): each sub-step is then one bit.
4

Draw the bits, left to right

  • Bit 1 — start: low.
  • Bits 2 to 9 — data, least significant first: since A is 01000001, reversed it reads 1000 0010.
  • Bit 10 — stop: high.
5

Check the result

The bars appear under the channel: Start, Data and Stop. Hovering the data bar shows 0x41 · 65 · 01000001 · "A".
If the result is incorrect, check the order of the data bits. UART sends the least significant bit first, so draw the bits in reverse order from the usual written form of the byte.

What you see

The band under the channel

One bar per frame field, with:
  • A short label: SOF, ID, DLC, CRC.
  • The value written out to read: 0x1A3, 8, FF.
  • A color according to the role the field plays.
  • On hover, the long text explaining what it is.
While a protocol is being read, its reading takes the place of the step numbers.

The colors

The color does not belong to the protocol but to the role the stretch plays, so two different protocols paint alike what is alike: the start is always the same color, the data always another.

The status box

A summary appears on the channel’s name card: how many frames there are and whether they are all fine —“3 frames · all OK”— or how many failed —“3 frames · 1 with errors”. Expand it to see the full reading, frame by frame, with the problems listed. When the channel has nothing yet, the box explains how to start, with text of its own for each protocol.

The four protocols

UART

One channel. Configurable character format: data bits, parity, stop bits, bit order and idle level.

CAN

One channel. Standard and extended frames, with the CRC checked, stuff bits and error flags.

I2C

Two channels per bus: SDA and SCL. Several buses at once.

Modbus

RTU, ASCII and TCP, with the function codes and the exceptions translated.

Where they are configured

The Protocol control in the header opens the window with every setting. Each protocol has its own, and they are stored in the browser with the rest of the configuration.