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|IDANDDA TA|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
To Next Page
Loading...
Need help?
General
