R&S RTO6 - Page 828

Protocol analysis
R&S
®
RTO6
828User Manual 1801.6687.02 ─ 05
●
if no PID error is found, no trigger is set, even if other selected conditions are met.
Otherwise, the trigger instant is defined by the first occurrence of any of the specified
additional conditions.
Remote command:
TRIGger<m>:
USB:SPEC
on page 2159
PREamble or ERR ← Special PID
For the Trigger Special Types "PREamble" and "ERR", the following condition can be
set:
See "PID error " on page 829
SPLIT ← Special PID
For the Trigger Special Type "SPLIT", the following conditions can be set:
You can refine the trigger condition:
●
See "Address" on page 829
●
See "SC" on page 830
●
See "Port" on page 830
●
See "SEU" on page 831
●
See "ET" on page 831
●
See "PID error " on page 829
PING ← Special PID
For the Trigger Special Type "PING", the following conditions can be set:
You can refine the trigger condition:
●
See "Address" on page 829
●
See "End Point" on page 829
●
See "PID error " on page 829
Error condition
Sets the trigger in case of one of the following eight different error condition types.
The trigger instant is the first occurrence of the specified error.
"Any error"
Triggers on any of the errors listed below.
"PID error"
Triggers on any packet identifier error.
"CRC5 error"
Triggers on any CRC5 error event
"CRC16 error"
Triggers on any CRC16 error event
"Bitstuff error"
Triggers in the event of an erroneous or missing bit stuffing sequence
(see USB standard).
"Unexpected
PID error"
Triggers on any illegal PID. This is a PID that is not allowed in USB
low speed and USB full speed protocols, especially PID's announcing
packets such as SPLIT
, DA
TA2, MDATA, or other noncompliant pack-
ets.
"SE1 error"
Triggers on the illegal bus state Single Ended 1 (SE1 = both lines
high).
"Glitch error"
Triggers on an error in the bit period (see USB standard for the defini-
tion of glitch).
USB (option R&S R
T
O6-K570)