MDO3000 Programmer Manual.pdf - 第900页
Commands Listed in A lphabetical Order TRIGger:A:BU S:B<x>:USB:SPLit:PORT :V ALue When triggering on a high-speed USB s plit transaction, this command speci fies the split transaction port a ddress value to trigger …
Commands Listed in Alphabetical Order
Arguments
NOCARE —anyend
point type.
CONTRol — control endpoint type.
ISOchronous — isochronous endpoint type.
BULK — bulk endpoint type (BULK-IN or BULK-OUT).
INTERRUPT — interrupt endpoint type (Interrupt-IN).
Examples
TRIGger:A:BUS:B1:USB:SPLit:ET:VALue iso sets the endpoint type to
trigger on to isochronous.
TRIGger:A:BUS:B1:USB:SPLit:ET:VALue? might return BULK, indicating
that the bulk endpoint type has been specified to trigger on.
TRIGger:A:BUS:B<x>:USB:SPLit:HUB:VALue
When triggering on a high-speed USB split transaction, this command specifies
the split transaction hub address value to trigger on. The value can be up to 7
characters long. The default is all X’s (don’t care).
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:SPLit:HUB:VALue <QString>
TRIGger:A:BUS:B<x>:USB:SPLit:HUB:VALue?
Related Commands
TRIGger:A:BUS:B<x>:USB:SPECIALType
Arguments
QString is a quoted string of up to 7 characters. The valid characters are 0 and 1.
Examples
TRIGger:A:BUS:B1:USB:SPLit:HUB:VALue “001010” sets the split
transaction hub address to trigger on to 001010.
TRIGger:A:BUS:B1:USB:SPLit:HUB:VALue? might return XXXXXXX,
indicating that the hub address value to trigger on doesn’t matter.
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-869
Commands Listed in Alphabetical Order
TRIGger:A:BU
S:B<x>:USB:SPLit:PORT:VALue
When triggering on a high-speed USB split transaction, this command specifies
the split transaction port address value to trigger on. The value can be up to7
characters l
ong. The default is all X’s (don’t care).
B<x>
Conditions
This command requires the DPO4USB application module to be installed, except
for MDO30
00 models, which require the MDO3USB. Note that 1 GHz bandwidth
models are recommended for high-speed (HS) USB.
Group
Trigge
r
Syntax
TRIGger:A:BUS:B<x>:USB:SPLit:PORT:VALue <QString>
TRIGger:A:BUS:B<x>:USB:SPLit:PORT:VALue?
Related Commands
TRIGger:A:BUS:B<x>:USB:SPECIALType
Arguments
QString is a quoted string of up to 7 characters. The valid characters are 0 and 1.
Examples
TRIGger:A:BUS:B1:USB:SPLit:PORT:VALue “001010” sets the split
transaction hub address to trigger on to 001010.
TRIGger:A:BUS:B1:USB:SPLit:PORT:VALue? might return XXXXXXX,
indicating that the hub address value to trigger on doesn’t matter.
TRIGger:A:BUS:B<x>:USB:SPLit:SC:VALue
When triggering on a high-speed USB split transaction, this command specifies
whether to trigger on the start or complete phase of the split transaction, based
on the Start/Complete bit field value. (0 = Start, 1 = Complete). The default is
NOCARE.
B<x>
Conditio
ns
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:SPLit:SC:VALue {NOCARE|SSPLIT|CSPLIT}
TRIGger:A:BUS:B<x>:USB:SPLit:SC:VALue?
2-870 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual
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