Instructions
Table Of Contents
- Cover
- Contents
- 1 For Your Safety
- 2 Getting Started
- 3 Waveform Setup
- 3.1 Connecting Probes
- 3.2 Vertical Setup
- 3.3 Horizontal Setup
- 3.4 Acquisition Control
- 3.5 Roll Mode
- 3.6 Trigger
- 3.6.1 General Trigger Settings
- 3.6.2 Edge Trigger
- 3.6.3 Glitch Trigger
- 3.6.4 Width Trigger
- 3.6.5 Video/TV Trigger
- 3.6.6 External Trigger (R&S RTH1002)
- 3.6.7 Pattern Trigger (R&S RTH-K19)
- 3.6.8 State Trigger (R&S RTH-K19)
- 3.6.9 Runt Trigger (R&S RTH-K19)
- 3.6.10 Slew Rate Trigger (R&S RTH-K19)
- 3.6.11 Data2Clock Trigger (R&S RTH-K19)
- 3.6.12 Serial Pattern Trigger (R&S RTH-K19)
- 3.6.13 Timeout Trigger (R&S RTH-K19)
- 3.6.14 Interval Trigger (R&S RTH-K19)
- 3.6.15 Window Trigger (R&S RTH-K19)
- 3.6.16 Protocol Trigger (R&S RTH-K1, -K2, -K3, -K9 and -K10)
- 4 Waveform Analysis
- 5 Mask Testing
- 6 Spectrum Analysis
- 6.1 FFT Mode
- 6.2 Spectrum Mode (Option R&S RTH-K18)
- 6.3 Harmonics Measurement (Option R&S RTH-K34)
- 7 Multimeter Measurements
- 8 Data Logging
- 9 Protocol Analysis
- 10 Logic Analyzer (R&S RTH-B1 MSO)
- 11 Frequency Counter (R&S RTH-K33)
- 12 Documenting Results
- 13 General Instrument Setup
- 14 Network Connections
- 15 Remote Control Commands
- 15.1 Conventions used in Command Description
- 15.2 Mode
- 15.3 Waveform Setup
- 15.3.1 Automatic Setup
- 15.3.2 Vertical Setup
- 15.3.3 Horizontal Setup
- 15.3.4 Acquisition Control
- 15.3.5 Trigger
- 15.3.5.1 General Trigger Settings
- 15.3.5.2 Edge Trigger
- 15.3.5.3 Glitch Trigger
- 15.3.5.4 Width Trigger
- 15.3.5.5 Video/TV Trigger
- 15.3.5.6 External Trigger (R&S RTH1002)
- 15.3.5.7 Pattern Trigger (R&S RTH-K19)
- 15.3.5.8 State Trigger (R&S RTH-K19)
- 15.3.5.9 Runt Trigger (R&S RTH-K19)
- 15.3.5.10 Slew Rate Trigger (R&S RTH-K19)
- 15.3.5.11 Data2Clock Trigger (R&S RTH-K19)
- 15.3.5.12 Serial Pattern Trigger (R&S RTH-K19)
- 15.3.5.13 Timeout Trigger (R&S RTH-K19)
- 15.3.5.14 Interval Trigger (R&S RTH-K19)
- 15.3.5.15 Window Trigger (R&S RTH-K19)
- 15.4 Waveform Analysis
- 15.5 Mask Testing
- 15.6 Spectrum Analysis
- 15.7 Digital Multimeter (R&S RTH1002)
- 15.8 Voltmeter (R&S RTH1004)
- 15.9 Counter Mode (R&S RTH-K33)
- 15.10 Data Logging
- 15.11 Protocol Analysis
- 15.12 Logic Analyzer (R&S RTH-B1 MSO)
- 15.13 Documenting Results
- 15.14 General Instrument Setup
- 15.15 WLAN Connection (Option R&S RTH-K200/200US)
- 15.16 User Scripting (R&S RTH-K38)
- Annex
- List of Commands
Protocol Analysis
R&S
®
Scope Rider RTH
215User Manual 1326.1578.02 ─ 15
9.5.4 CAN Label List
Label list files (symbolic data files) for CAN protocols are available in PTT and CSV file
formats, similar to other serial protocols. In addition, the R&S RTH can read and apply
DBC files to the decoded signal and use them for triggering.
For general information on label lists, see Chapter 9.1.3, "Label Lists", on page 179.
9.5.4.1 PTT and CSV Files for CAN
Label list files are protocol-specific. A PTT label file for CAN protocols contains three
values for each identifier:
●
Identifier type, 11-bit or 29-bit long
●
Identifier value
●
Label, symbolic name of the identifier, specifying its function in the bus network.
Example: CAN PTT file
# ----------------------------------------------------------------------------
@FILE_VERSION = 1.00
@PROTOCOL_NAME = can
# ---------------------------------------------------------------------------
# Labels for CAN protocol
# Column order: Identifier type, Identifier value, Label
# ---------------------------------------------------------------------------
11,064h,Diag_Response
11,1E5h,EngineData
11,0A2h,Ignition_Info
11,1BCh,TP_Console
11,333h,ABSdata
11,313h,Door_Left
11,314h,Door_Right
29,01A54321h,Throttle
29,13A00FA2h,LightState
29,0630ABCDh,Engine_Status
29,03B1C002h,Airbag_Status
29,01234ABCh,NM_Gateway
# ----------------------------------------------------------------------------
9.5.4.2 DBC Files for CAN
Industry-standard DBC files contain more information than PTT and CSV files and
translate the abstract decode results to human language. For each frame, the frame ID
and the symbolic name of the ID are given; the frames are also called messages in
CAN. The data of a CAN message can consist of several "signals". The DBC file pro-
vides the label, unit, start bit, length and other indicators for each signal. For state-
encoded signals, the meaning of the states is given.
In the demo example, the message "EngineData" has the decimal ID 2,166,573,756
and consists of 8 data bytes. These 8 bytes are defined as 6 signals. The first one,
CAN and CAN FD (Options R&S
RTH-K3, R&S RTH-K9)