MDO3000 Programmer Manual.pdf - 第819页
Commands Listed in Alphabetical Order Syntax TRIGger:A:BUS :B<x>:CAN:DATa:Q UALifier {LESSthan|Tha n|EQual|UNEQual| LESSEQual|EQual} TRIGger:A:BUS :B<x>:CAN:DATa:Q UALifier? Arguments LESSthan sets the oscill…
Commands Listed in Alphabetical Order
TRIGger:A:BUS
:B<x>:CAN:DATa:VALue
Arguments
<NR1> is a number specifying the data offset. It can be set to -1 to 7 for CAN 2.0
and-1to63forCANFD.Theserangesaremodifiedbythefollowing:
A value of -1 signifies “don’t care” and the instrument will match any byte value
that satisfy the match criteria.
A value of 0 signifies the start of the data field. If matching N bytes of data,
the system will only produce a match if the first N bytes of the data field satisfy
the match criteria.
The maximum is dependent on the number of bytes being matched and the CAN
standard selected. Its value is calculated as “[Absolute Maximum] – [Data Match
Size]”. For CAN 2.0, the absolute maximum is 8 bytes. For CAN FD, the absolute
maximum is 64 bytes. The minimum data match size is 1 byte, which produces
the ranges listed above. Increasing the data match size above 1 byte will adjust
the range of valid data offset values accordingly.
Trying to specify a data offset above the current maximum will result in the offset
being set to the current maximum.
Examples
TRIGger:A:BUS:B<x>:CAN:DATa:OFFSet 5 sets the CAN data offset to
5 bytes.
TRIGger:A:BUS:B<x>:CAN:DATa:OFFSet? might return 7, indicating that
CAN data offset is 7 bytes.
If the CAN standard is set for CAN 2.0 and the search data size is set to 3, the
maximum value for the data offset will be 5 (8 – 3 = 5).
If the CAN standard is set for CAN FD and the search data size is set to 8, the
maximum value for the data offset will be 56 (64 – 8 = 56).
TRIGger:A:BUS:B<x>:CAN:DATa:QUALifier
Thiscommandsetsthequalifier(<,>,=,not=,<=)tobeusedwhentriggeringon
a CAN bus signal. The trigger condition must be set to IDANDDATA OR DATA
(using TRIGger:A:BUS:B<x>:CAN:CONDition).
B<x> is the bus number (1-4).
1-3 for the MDO4000C and 1-2 for the MDO3000.
Conditions
This command requires a DPO4AUTO or DPO4AUTOMAX application module
on DPO/MSO4000B and MDO4000/B/C models and a
MDO3AUTO application
module on MDO3000 models.
Group
Trigger
2-788 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual
Commands Listed in Alphabetical Order
Syntax
TRIGger:A:BUS
:B<x>:CAN:DATa:QUALifier
{LESSthan|Than|EQual|UNEQual|LESSEQual|EQual}
TRIGger:A:BUS:B<x>:CAN:DATa:QUALifier?
Arguments
LESSthan sets the oscilloscope to trigger when the data is less than the qualifier
value.
Than sets the oscilloscope to trigger when the data is than the qualifier value.
EQual sets the oscilloscope to trigger when the data is equal to the qualifier value.
UNEQual sets the oscilloscope to trigger when the data is not equal to the qualifier
value.
LESSEQual sets the oscilloscope to trigger when the data is less than or equal
to the qualifier value.
EQual sets the oscilloscope to trigger when the data is than or equal to the
qualifier value.
Examples
TRIGGER:A:BUS:B1:CAN:DATA
:QUALIFIER LESSTHAN
sets the oscilloscope
to trigger when the data is less than the qualifier value.
TRIGGER:A:BUS:B1:CAN:DAT
A:QUALIFIER?
might return
:TRIGGER:A:BUS:B1:CAN:DATA:QUALIFIER THAN, indicating that the
oscilloscope is set to trigger when the data is than the qualifier value.
TRIGger:A:BUS:B<x>:CAN
:DATa:SIZe
This command sets the length of the data string, in bytes, to be used when
triggering on a CAN bus signal. The trigger condition must be set to
IDANDDATA OR DATA (usin
g TRIGger:A:BUS:B<x>:CAN:CONDition).
B<x> is the bus number (1-4). 1-3 for the MDO4000C and 1-2 for the MDO3000.
Conditions
This command requires a DPO4AUTO or DPO4AUTOMAX application module
on DPO/MSO4000B and MDO4000/B/C models and a MDO3AUTO application
module on MDO3000 models.
Group
Trigger
Syntax
TRIGger:A:BUS:B<x>:CAN:DATa:SIZe <NR1>
TRIGger:A:BUS:B<x>:CAN:DATa:SIZe?
Arguments
<NR1> is the length of the data string in bytes.
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-789
Commands Listed in Alphabetical Order
TRIGger:A:BU
S:B<x>:CAN:DATa:VALue
This command sets the binary data value to be used when triggering on a CAN
bus signal. The trigger condition must be set to IDANDDATA OR DATA (using
TRIGger:A:B
US:B<x>:CAN:CONDition).
B<x> is the bus number (1-4). 1-3 for
the MDO4000C and 1-2 for the MDO3000.
Conditions
This command requires a DPO4AUTO or DPO4AUTOMAX application module
on DPO/MSO4000B and MDO4000/B/C models and a MDO3AUTO application
module on MDO3000 models.
Group
Trigger
Syntax
TRIGger:A:BUS:B<x>:CAN:DATa:VALue <QString>
TRIGger:A:BUS:B<x>:CAN:DATa:VALue?
Arguments
<QString> is the data value in binary format. The only allowed characters in
the
QString are0,1,andX.
Examples
TRIGGER:A:BUS:B1:CAN:DATA:VALUE 1011 sets the CAN data value to 1011.
TRIGger:A:BUS:B<x>:CAN:FD:BRSBIT
This command specifies the binary data value to be used to search on CAN FD
BRS bits. This only applies if the search condition has been set to FDBRSBIT
(using
TRIGger:A:BUS:B<x>:CAN:CONDition).
B<x> is the bus number (1-3) for the MDO4000C and 1-2 for the MDO3000.
Conditions
This command requires a DPO4AUTO or DPO4AUTOMAX application module
on MDO4000C models and a MDO3AUTO application module on MDO3000
models.
Group
Search
Syntax
TRIGger:A:BUS:B<x>:CAN:FD:
BRSBIT{ZERo|OFF|0|ONE|ON|1|NOCARE|X|x}
TRIGger:A:BUS:B<x>:CAN:FD:BRSBIT?
Related Commands
TRIGger:A:BUS:B<x>:CAN:CONDition
2-790 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual