option - vector informatik
TRANSCRIPT
V0.1 | 2017-04-04
Automated Analysis for Vehicle Communication
Option .Scope
2
u Product Concept
Use Cases
Analyzing, Debugging, Tracing
Configuration
Measurement / Analysis
Supported Hardware
Summary
Agenda
3
Delays
Timebase-Controller
CAN_H
CAN_L
CAN_H
CAN_L
CAN-Bus
Benefits of an Tool-Integrated Oscilloscope Solution
Product Concept
Analysis Tool
u Trace logical bus data
u Debugging
u Test Environment
RRS-Bit Identifier 0x64
0 0 0 0 S 1 1 1 0 0 0 0 0
Scope HW
u Time Base, Sampling Rate
u Measure Voltage, Trigger
u Optional Frame Parser (CAN,CANFD…)
Timebase-Oscilloscope
CAN Interface HW
u Time Base
u Time Sync (optional)
u Logical Interpretation (0,1,0,0,1,1,1..)
Trigger Time SYNC
Timebase-Controller
RRS-Bit Identifier 0x64
0 0 0 0 S 1 1 1 0 0 0 0 0
Timebase-Controller
RRS-Bit Identifier 0x64
0 0 0 0 S 1 1 1 0 0 0 0 0
4
Prerequisites for this Tool Concept
Product Concept
u Analysis Tool
u USB Hub, USB cables
u CAN-Bus Interface (with HW-Sync)
u Scope device
u Bus Probe Connector (DSUB)
u Y-Trigger cable
u Optional CAN Stress Tool
CAN Disturbance
6
u Triggers are used to synchronize the bus interface with scope device (Sync-Line)
u All scope analysis is reflected to trigger time stamp
u Time Drift Compensation (HW-Clock-Drifts, Transceiver delays, USB-latencies)
u Reflect analysis to time base of network interface
u Overlay physical scope data with logic controller data
u Trigger Types
u Bus-Triggers: CAN, CAN FD, LIN, FlexRay, SENT, PSI5, …
u IO-Trigger (Waveforms, Edges and Pulses)
u CAPL Trigger > User defines trigger conditions with CAPL code
> Raise trigger using ‘scopeTriggerNow()’ (like manual trigger)
u Trigger Modes
u Manual (snapshot)
u Protocol specific trigger conditions (single / repeat mode)
u Protocol errors
Indispensable Trigger Options
Product Concept
8
Product Concept
u Use Cases
Analyzing, Debugging, Tracing
Configuration
Measurement / Analysis
Supported Hardware
Summary
Agenda
9
Use Cases in Automotive Development
Use Cases
u Analysis and triggering of CAN FD, FlexRay und LIN
u Analysis of PSI5- and SENT-signals (VT-System)
u Time/voltage triggering and measurement of signals (bus, sensor, I/O)
u Detection and triggering protocol errors (e.g. CAN Error Frames)
u ECU conformance testing according to OEM specifications
u Proof of network design concepts (bus topology, cables, resistors)
u Tracing EMC problems and other physical effects (reflections, ringing, crosstalk)
u Automated analysis using eye diagram, bitmask analysis or time transition measurements
10
Product Concept
Use Cases
u Analyzing, Debugging, Tracing
Configuration
Measurement / Analysis
Supported Hardware
Summary
Agenda
11
Scope Main View
Analyzing, Debugging, Tracing
Measurement History
Eye Diagram (Bit Layer)
Chart Bit Legend
Scope Trace
Devices & Trigger
Eye Diagram Config
Scope Diagram (Protocol/Physical View)
Cursor Legend
12
Trace/Debug logical data Network signals with controller data highlights
Protocol trace view: Reflects all frames
Time Synchronized Roundtrip Analysis
Analyzing, Debugging, Tracing
Eye Diagram with Bitmask
Bit per Bit Analysis
All views have the CAN controller time base !
TES
T A
UT
OM
AT
IO
N
Pro
gra
m I
nte
rface
Frame-Layer Bit-Layer Data Link-Layer
13
u Frame Interpretation (CAN, LIN, FlexRay, SENT, PSI5)
u Overlay of protocol layer (controller data) and physical layer (scope data)
u Eye Diagram and Bit Mask Analysis
u Online and Offline analysis
u Transition Time Measurement of falling and rising edges
u Min, Max Values
u User can create application specific bus statistics (Program-API)
u Measurement Evaluation
u Local Measurement Cursors, Global Markers
u Measurement Legend (Time, Voltage Values)
u Signal Interpretation (Bit Interpretation Tooltips)
u CAN Common Mode Voltage
u Acquisition Info (Scope Settings, Network Settings, Triggers, Signals…)
u Automation
u Programming Interface (CAPL)
u Loop Tests
u HTML Test Reports (with test cases, screenshots)
Analysis Features Overview
Analyzing, Debugging, Tracing
14
Product Concept
Use Cases
Analyzing, Debugging, Tracing
u Configuration
Measurement / Analysis
Supported Hardware
Summary
Agenda
15
Configuration Overview
Configuration
u Measurement History
u Time Stamps, ID, Signals
u Import / Export
u Compare Mode, Additional Signals (e.g. CMV)
u Acquisition Info
u Eye Diagram Configuration
u Online Mode
> Record Persistency
u Offline Mode with Analysis Filter Options
> Frame Type
> Channel
> ECU
> Bit Sequences (e.g. Data Phase, ARB-Phase, ACK)
u Scope Device Configuration
u HW-Type, Sample Rate, Resolution, Measurement Channels, Bus-Probe, Signal Source
u Trigger Configuration
u Bustype, Frametype, Bitfield Scaling (used by Eye Diagram)
16
Hardware Configuration Dialog
Configuration
u Mapping of scope inputs to bus channels (see Devices and Triggers)
u Automatic according to available channels
> In a CAN/CANFD configuration CAN-signal elements are automatically mapped to scope inputs A and B
> User can map additional signals using Scope Hardware Dialog
17
Global Scope Configuration – Acquisition Settings
Configuration
u Configuration of acquisition time
u Automatic according to protocol and baudrate
u Or user-defined (max. 1s)
u Configuration of sampling rate in min. samples per bit
u Adjustable pre-trigger time from 10% to 90%
u And much more …
18
Trigger Configuration Dialog
Configuration
u Protocol Triggers for CAN/CAN FD, FlexRay, LIN
u Any valid frame and error frame
u ID
u ID Range
u Frame-Type-Filter (e.g. CAN, CAN FD, ALL)
u Defines bit fields for eye diagram analysis and scaling
u Sensor Triggers for SENT and PSI5
u IO-Trigger conditions for triggering
u Analog or digital I/O’s (sensors, interrupts)
u Output of a CAN Disturbance Hardware
u Edges an Pulses of bus signals
(CAN/CAN FD, LIN, FlexRay) with signal decode
19
Product Concept
Use Cases
Analyzing, Debugging, Tracing
Configuration
u Measurement / Analysis
Supported Hardware
Summary
Agenda
20
Chart View – Frame Interpretation
Measurement / Analysis
u Acquired data can be analyzed with scope graph and scope trace view
u Bidirectional synchronization of scope graph and scope trace view
u Time-based synchronization with other tool windows (e.g. State Tracker)
u Export of scope’s diagram data as CSV, MAT or bitmap.
CAN High
CAN Low
CAN Diff
u Chart View shows signal interpretation at bit-level
u Trace shows logical data of all frame fields (CRC, Payload, ID, SOF….)
u Measurement cursors (time, voltage, bit information)
u Signal ground marker bar
21
Trace View - Frame Interpretation
Measurement / Analysis
u Protocol decode of standard bus frames and errors frames
u Tree view shows several frame field layers (Event->Field Groups->Fields)
u Start times and data for each frame field, e.g. ARB, CTRL or DATA field
u Duration and bit count for each event/field group/subfield
u Explicit DATA FIELD representation
u Application Channel (e.g. CAN1….CANn)
u Shows event and node names when database is attached
22
Eye Diagram - Example Network Termination Measurement
Measurement / Analysis
Baud rate Sampling point
Arbitration 500 kbit/s 0.70
Data phase 4000 kbit/s 0.85
u Rise and fall time of bit edges change with resistors (like discharging RC-element)
u Transitions from dominant to recessive levels take longer time with single termination
u Controller settings (sample point) compensate single termination issues to a definite degree
u Test single- and double-ended termination
u Node 3 sends cyclical CAN FD frames
u Resistors changed from 60Ω (120||120) to 120Ω
u Take eye diagram of CRC-Field (data phase, bit time: 125ns)
Double ended termination (60Ω)
Single ended termination (120Ω)
Sample Point
23
u Analysis covers
u CAN, CAN FD, FR, LIN Frames
u Single / Multi Frame Analysis
u Database related analysis of frame(s) according to defined filter options: > Frame type, Application channel, ECU‘s, Bit fields (Analyzed Bits, predefined in GUI, variable in CAPL)
u Analysis works on imported scope data
u Bits of eye diagram can be highlighted in measured data buffer
u Analyzed bits are reflected to controller bit settings of CANoe/CANalyzer: > Sync Field
> TSEG1
> Sample Point
> TESEG2
u Additional analysis > Bit Rise Time
> Bit Fall Time
> Min/Max voltage values of analyzed bit field range
u Dedicated Eye Diagram Export
Eye Diagram - Analysis Overview
Measurement / Analysis
28
Compare Mode
Measurement / Analysis
u Compare mode for easy comparison of scope signals
u E.g. Comparison of protocol errors
Capture data ID=1
Capture data ID=1
(compared)
Measurement Cursors
29
Global Markers
Measurement / Analysis
u Use global markers (time, name and comment) to annotate/label your scope measurements (e.g. critical bus voltage levels)
u Each scope measurement has its own separate group of markers
u Markers are exported and imported with each scope measurement
u Scope Global Markers are time synchronized with Trace, Graphics, State Tracker of CANoe/CANalyzer
30
u Export of captured scope data
u CSFX (binary format, entire measurement)
u CEYE (binary format, a stack of measurements) > Imported eye diagram is replayed
u MAT (Matlab format, only export for graph-data)
u CSV (ASCII format, only export for graph-data)
u HTML-Test-Report
u Reports created with Program API can be stored for documentation
Data Reproducibility
Measurement / Analysis
31
Product Concept
Use Cases
Analyzing, Debugging, Tracing
Configuration
Measurement / Analysis
u Supported Hardware
Summary
Agenda
32
Vector PicoScopes
Supported Hardware
u PS5444B-034 with 4 channels and 200 MHz bandwidth
u 500 MS/s sampling rate with 512 MS buffer
u Recommended for LIN, CAN, CAN FD and FlexRay
u 4 channels available for bus systems and IO > e.g. 2 CAN/FR or 4 LIN/IO
u PS5242B-034 with 2 channels and 60 MHz bandwidth
u 500 MS/s sampling rate with 32 MS buffer
u Recommended for LIN and CAN
u 2 channels available for bus systems and IO
> e.g. 1 CAN/FR or 2 LIN/IO
u Scalable oscilloscope solution
u Requires identical scope devices e.g. 2 PS5444B for 4 CAN/FR or 8 LIN/IO
u Triggering and parallel acquisition of multiple bus channels, bus systems and IO
u Multi-scopes of same type behave like one large scope with more channels
33
Supported Network Interfaces
Supported Hardware
1) Scope hardware must be connected via USB to the GUI PC!
2) Special Scope Trigger Cable required (available on request)
HW / Bus system LIN CAN CAN FD FlexRay
VN1610/11(A), VN7610
VN1630/40(A) • • • -
VN89001
, VN7572 • • • •
VT System1,2
• • • •
VN5610, VN5640 - • • -
VH6501 (CAN Disturbance) - • • -
Not supported (due to missing sync line)
34
Summary
Summary
u All-in-one solution to analyze, debug and trace issues for CAN/CAN FD and other networks
u Many uses cases in automotive development profit from a common time base for physical and data link layers
u Proof design concepts of ECUs and network topologies
u Full roundtrip analysis of data link layer and physical layer
u Programming API to implement automated test scenarios
35 © 2017. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2017-04-04
For more information about Vector and our products please visit www.vector.com
Author: Mirko Donatzer Vector Germany