MDO3000 Programmer Manual.pdf - 第817页

Commands Listed in Alphabetical Order TRIGger:A:BUS :B<x>:CAN:CONDition ). B<x> is the b us number (1-4). 1-3 for the MDO4000C and 1-2 for the MDO3000. Conditions This command requires a DPO4AUTO or DPO4AUTOM…

100%1 / 1158
Commands Listed in Alphabetical Order
Conditions
This command re
quires a DPO4AUTO or DPO4AUTOMAX application
module on a DPO/MSO4000B and MDO4000/B/C models and a MDO3AUTO
application module on MDO3000 models.
FORMERRor, ANYERRor, FDBRS,andFDESIare supported only on MDO3000 and
MDO4000C models and available only when :BUS:B<x>:CAN:STANDard is
set to
CANFD.
Group
Trigger
Syntax
TRIGger:A:BUS:B<x>:CAN:CONDition
{SOF|FRAMEtype|IDentifier|DATA|IDANDDATA|EOF|ACKMISS|
ERROR|FORMERRor|ANYERRor|FDBRS|FDESI}
TRIGger:A:BUS:B<x>:CAN:CONDition?
Arguments
SOF enables triggering on the start of frame.
FRAMEtype enables triggering on the type of frame.
IDentifier enables triggering on a matching identifier.
DATA enables triggering on matching data.
IDANDDATA enables triggering on a matching identifier and matching data.
EOF enables triggering on the end of frame.
ACKMISS enables triggering on a missing acknowledge.
ERROR enables triggering on bit stuffing errors.
FORMERRor enables triggering on packet form errors.
ANYERRor enables triggering on any packet error (missing ACK, bit stuffing
error, or form error).
FDBRS enables triggering on a CAN FD frame’s BRS bit.
FDESI enables triggering on a CAN FD frame’s ESI bit.
Examples
TRIGGER:A:BUS:B1:CAN:CONDITION? might return :TRIGGER:A:BUS:B1:
CAN:CONDITION EOF indicating an end of file condition.
TRIGGER:A:BUS:B1:CAN:CONDITION DATA enables triggering on matching
CAN data.
TRIGger:A:BUS:B<x>:CAN:DATa:DIRection
This command sets the data direction (read, write or “nocare”) to be used to
search on a CAN bus signal. The trigger condition must be set to IDentifier (using
2-786 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual
Commands Listed in Alphabetical Order
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:DIRection {READ|WRITE|NOCARE}
TRIGger:A:BUS:B<x>:CAN:DATa:DIRection?
Arguments
READ sets the CAN data direction to READ.
WRITE sets the CAN data direction to WRITE.
NOCARE sets the CAN data direction to either.
Examples
TRIGGER:A:BUS:B1:CAN:DATA:DIRECTION WRITE sets the CAN data
direction to Write.
TRIGger:A:BUS:B<x>:CAN:DATa:OFFSet
This command specifies the data offset in bytes to search for in a CAN search.
The default value is 0. 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 a 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:OFFSet <NR1>
TRIGger:A:BUS:B<x>:CAN:DATa:OFFSet?
Related Commands
BUS:B<x>:CAN:STANDard
TRIGger:A:BUS:B<x>:CAN:CONDition
TRIGger:A:BUS:B<x>:CAN:DATa:SIZe
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-787
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