MDO3000 Programmer Manual.pdf - 第902页
Commands Listed in A lphabetical Order Group T rigger Syntax TRIGger:A:BUS :B<x>:USB:SPLit: SE:VALue {NOCARE|FULLS Peed|LOWSPeed|IS OSTART|ISOMID|I SOEND|ISOALL} TRIGger:A:BUS :B<x>:USB:SPLit: SE:VALue? Relat…

Commands Listed in Alphabetical Order
Related Commands
TRIGger:A:BUS
:B<x>:USB:SPECIALType
Arguments
NOCARE — trigger on either the start or complete phase of the split transaction.
SSPLIT — trigger on the start phase of the split transaction.
CSPLIT — trigger on the complete phase of the split transaction.
Examples
TRIGger:A:BUS:B1:USB:SPLit:SC:VALue SSPLIT specifies to trigger on
the start phase of the split transaction.
TRIGger:A:BUS:B1:USB:SPLit:SC:VALue? might indicate NOCARE,
specifying that it doesn’t matter whether to trigger on the start or complete phase
of the split transaction.
TRIGger:A:BUS:B<x>:USB:SPLit:SE:VALue
When triggering on a high-speed USB split transaction, this command specifies
the split transaction start/end bit value to trigger on.
B<x>
NOTE. The start and end bits are interpreted based on the type of split transaction:
For Interrupt and control transactions, the S bit means Speed: 0 = Full Speed, 1
= Low Speed.
For bulk IN/OUT and isochronous IN start-split transactions, the S field must be 0.
For bulk/control IN/OUT, interrupt IN/OUT, and isochronous IN start-split
transactions, the E fi eld must be 0 .
For full-speed isochronous OUT start-split transactions, the S (Start) and E
(End) fields specify how the high-speed data payload corresponds to data for a
full-speed data packet as shown below:
S E High-speed to Full-speed Data Relation
0 0 High-speed data is the middle of the full-speed data payload.
01High-speeddataistheendofthefull-speeddatapayload.
1 0 High-speed data is the beginning of the full-speed data payload.
1 1 High-speed data is all of the full speed data payload.
Conditions
This command requires the DPO4USB application module to be installed, except
for MDO3000 models, which require the MDO3USB. Note that 1 GHz bandwidth
models are recommended for high-speed (HS) USB.
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-871

Commands Listed in Alphabetical Order
Group
Trigger
Syntax
TRIGger:A:BUS:B<x>:USB:SPLit:SE:VALue
{NOCARE|FULLSPeed|LOWSPeed|ISOSTART|ISOMID|ISOEND|ISOALL}
TRIGger:A:BUS:B<x>:USB:SPLit:SE:VALue?
Related Commands
TRIGger:A:BUS:B<x>:USB:SPECIALType
Arguments
NOCARE — any combination of S and E bits.
FULLSPeed —Sbit=0,Ebit=0.
LOWSPeed —Sbit=1,Ebit=0.
ISOSTART —Sbit=1,Ebit=0.
ISOMID — see note above.
ISOEND — see note above.
ISOALL — see note above.
Examples
TRIGger:A:BUS:B1:USB:SPLit:SE:VALue ISOEND specifies to trigger on
the ISOEND split transaction value.
TRIGger:A:BUS:B1:USB:SPLit:SE:VALue? might return FULLSPEED.
TRIGger:A:BUS:B<x>:USB:TOKENType
This command specifies the token type for the USB trigger. B<x>
Conditions
This command requires the DPO4USB application module to be installed, except
for MDO3000 models, which require the MDO3USB. Note that 1 GHz bandwidth
models are recommended for high-speed (HS) USB.
Group
Trigger
Syntax
TRIGger:A:BUS:B<x>:USB:TOKENType {ANY|SOF|OUT|IN|SETUP}
TRIGger:A:BUS:B<x>:USB:TOKENType?
Related Commands
TRIGger:A:BUS:B<x>:USB:CONDition
2-872 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual

Commands Listed in Alphabetical Order
Arguments
ANY
indicates any of the token types.
SOF indicates a SOF (start-of-frame) token type
OUT indicates an OUT token type.
IN indicates an IN token type.
SETUP indicates a SETUP token type.
Examples
TRIGGER:A:BUS:B1:USB:TOKENTYPE SETUP sets the token type to SETUP.
TRIGGER:A:BUS:B1:USB:TOKENTYPE? might return
:TRIGGER:A:BUS:B1:USB:TOKENTYPE SOF if the token type is SOF.
TRIGger:A:BUS:SOUrce
This command specifies the source for a serial or parallel bus trigger, with the
appropriate application module installed.
Conditions
For I
2
C or SPI bus signals, install the DPO4EMBD application module,
except for MDO3000 models, which require MDO3EMBD.
For RS-232, RS-422, RS-485, or UART bus signals, install the DPO4COMP
module, except for MDO3000 models, which require MDO3COMP.
For I
2
S, Left Justified (LJ), Right Justified (RJ), or TDM bus signals, install
the DPO4AUDIO module, except for MDO3000 models, which require
MDO3AUDIO.
For CAN or LIN bus signals, install the DPO4AUTO or DPO4AUTOMAX
module, except for MDO3000 models, which require MDO3AUTO.
For FlexRay bus signals, install the DPO4AUTOMAX module, except for
MDO3000 models, which require MDO3FLEX.
For Ethernet signals on the MDO4000/B/C and MSO4000B and DPO4000B,
install the DPO4ENET module. Note that ≥350 MHz bandwidth models
are recommended for 100BASE-TX.
For MIL-STD-1553 bus signals, install the DPO4AERO module, except for
MDO3000 models, which require MDO3AERO.
For USB bus signals, install the DPO4USB module, except for
MDO3000 models, which require MDO3USB. Note that 1 GHz bandwidth
models are recommended for high-speed (HS) USB.
A table is available listing the commands enabled by each application module.
(See page H-1, List of Beta Commands and Features.)
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-873