R&S RTO6 - 24.17.17.4 Search settings

Remote control commands
R&S
®
RTO6
2049User Manual 1801.6687.02 ─ 05
24.17.17.4 Search settings
SEARch:
TRIGger:
MDIO:DATA...................................................................................... 2049
SEARch:TRIGger:MDIO:FRAMetype............................................................................. 2049
SEARch:TRIGger:MDIO:PHYS......................................................................................2050
SEARch:TRIGger:MDIO:REGI.......................................................................................2050
SEARch:TRIGger:MDIO:ST.......................................................................................... 2050
SEARch:TRIGger:MDIO:TYPE......................................................................................2051
SEARch:TRIGger:MDIO:DATA <SearchName>,<Data>
SEARch:TRIGger:MDIO:DATA? <SearchName>
Allows to define the 16-bit payload data pattern (both in Clause 22 or Clause 45) or the
address pattern (in Clause 45, only) to search for; available only in search criteria type
"Data".
Parameters:
<Data>
Parameters for setting and query:
<SearchName>
SEARch:TRIGger:MDIO:FRAMetype <SearchName>,<FrameT
ype>
SEARch:TRIGger:MDIO:FRAMetype?
<SearchName>
Allows to select the Type of Frame code (or OP code, OpCode, operation code); avail-
able only in search criteria type "Data".
Note that the same OpCode may have different meanings in Clause 22 and Clause 45.
Parameters:
<FrameType> OP00 | OP01 | OP10 | OP11 | OPXX
OP00
Address frame (in Clause 45, only)
OP01
Write frame (in Clause 22 or Clause 45)
OP10
Read frame (in Clause 22) or Post-Read increment address
frame (in Clause 45)
OP1
1
Read frame (in Clause 45)
OPXX
Any frame type
*RST: OPXX
Note that the user interface shows interpretations of the numeri-
cal OpCode values corresponding to Clause 45. Clause 22 is
not represented by this interpretation.
Also, note that OPXX will never be a result of decoding, but it is
still an option for triggering.
Protocols