Vehicle Serial Bus Analyzer SB5000

	Home / Our Businesses / Test & Measurement / Products / Digital Oscilloscopes /
	Vehicle Serial Bus Analyzer SB5000

Product Home

Specifications

· Features

Other Features

Features

1 2 3 4

FlexRay

CAN Bus

LIN Bus

UART

I²C, SPI Buses

LIN Bus

Figure.13 LIN trigger setting example

Comprehensive triggering, powerful analysis tools, and captured data searching functions are also provided for the LIN bus (body subnetwork). And speaking of triggers, the SB5710/SB5310 is equipped with not only Break + Synch and ID/Data (combinable) conditions, but also with a wealth of error triggers. This is one of the major features of the SB5000 series. You can capture bus waveforms when the various errors defined by the LIN protocol specifications (Parity, CheckSum, TimeOut, etc.) occur, and check those waveforms and the protocol analysis results (list) along with the error information. You can analyze both LIN revision 1.3 and 2.0 conformity data existing on the same bus line simultaneously.

Figure.14 LIN waveform, list, decode display example

Figure.15 LIN revision 1.3 and 2.0 simultaneous decode,
analysis display example

Combination Triggers: Create triggers consisting of in-vehicle bus events and events on other channels (e.g., a sensor input, or another in-vehicle bus event)
(Event Interval Trigger)

Trigger on Combinations with Non-in-vehicle bus Signals
Triggers can be activated on combinations of in-vehicle bus and analog signal trigger conditions. For example, you can debug a system by setting up a condition in which the trigger activates on a time difference between a LIN signal trigger condition and a signal input to another channel such as a sensor or actuator operation signal.
Trigger on Combination of Two in-vehicle bus Signals
You can set a condition in which a trigger activates on the time difference (delay time, etc.) between trigger conditions set on two separate in-vehicle bus networks. This is useful for verifying the complementary operation of two corresponding sub-networks.

Figure.16
Event Interval
trigger setting example