Protocol analysis
R&S
®
RTO6
765
User Manual 1801.6687.02 ─ 05
●
Set a byte count condition to trigger only on command sequences that send the
specified number of data frames.
See:
●
Set a register address condition to trigger only on command sequences that write
data to the specified register.
See:
●
Set a data pattern condition to trigger on data patterns expected in the message.
See:
Master Context Transfer Read ← Type
Available only for "Version"= "2.1".
Triggers on "Master Context Transfer Read" command sequences.
You can refine the trigger condition:
●
Set an MID condition to trigger only on command sequences that are sent to the
specified MIDs.
See:
●
Set a byte count condition to trigger only on command sequences that send the
specified number of data frames.
See:
●
Set a register address condition to trigger only on command sequences that write
data to the specified register.
See:
●
Set a data pattern condition to trigger on data patterns expected in the message.
See:
Error conditions ← Type
Triggers if at least one of the selected errors occurs in a frame. The instrument triggers
on the first detected error.
"SSC error"
Triggers when no valid SSC sequence has been found after the idle
time. The instrument triggers at the invalid sequence.
"Length error"
Triggers on an incorrect length of the command sequence - when
additional or missing bits are detected and the sequence of bits is not
as expected.
"No response"
Triggers on any No Response Frame. All 9 bits of a No Response
Frame, including the parity bit, are zero.
"Bus park error"
Triggers on an incorrect bus park cycle - when the instrument expects
a low bit in bus park but detects high bit.
"Parity error"
Triggers on incorrect parity bits.
"Unknown sequence"
Triggers when the instrument cannot detect any supported command
sequence.
"Gap error"
Triggers when timing gap error occurs.
"Version error"
Triggers on any version errors.
RFFE (option R&S
RTO6-K550)
