Rohde & Schwarz RTP Series - LIN Decode Results

Protocol analysis
R&S
®
RTP
592User Manual 1337.9952.02 ─ 12
Error conditions
Triggers if one or more of the following errors occur:
●
Checksum error
The checksum verifies the correct data transmission. It is the last byte of the frame
response. The checksum includes not only the data but also the protected identifier
(PID). To identify checksum errors caused by data, additional settings are required:
Enter the bit pattern of the identifier ("Frame ID"), the number of data bytes ("Data
length"), and select the used "LIN standard".
See also: LIN standard.
●
Identifier parity error
Parity bits are the bits 6 and 7 of the identifier. They verify the correct transmission
of the identifier.
●
Sync error
Synchronization error
Remote command:
TRIGger<m>:LIN:CHKSerror on page 1664
TRIGger<m>:LIN:ERRPattern on page 1664
TRIGger<m>:LIN:CRCDatalen on page 1664
TRIGger<m>:LIN:STANdard on page 1665
TRIGger<m>:LIN:IPERror on page 1663
TRIGger<m>:LIN:SYERror on page 1663
13.6.3.2 Triggering on LIN signals
Prerequisites: An LIN bus is configured, see Chapter 13.2.2.3, "Configuring I²C proto-
col", on page 525.
1. Press the [Protocol] key and select the "Shortcuts" tab.
2. Press "Setup trigger".
3. Tap the "Source" button and select the "Serial bus" trigger source.
4. Select the serial bus that is set to LIN.
5. Select the "Trigger type".
6. For more complex trigger types, enter the address and/or data conditions: address,
identifier, frame ID.
For details, see Chapter 13.6.3.1, "LIN trigger settings", on page 588.
13.6.4 LIN decode results
When the configuration of the serial bus is complete, the signal can be decoded:
1. In the "Protocol" dialog > "Setup" tab, enable "Decode".
2. In the "Protocol" dialog > "Display" tab, select additional result display settings:
"Show decode table" and "Show binary signals".
LIN (option R&S
RTP-K3)