Transcription

CANoeProduct Information

CANoeTable of Contents1Introduction to CANoe . 51.1Bus Systems and Protocols . 61.2Product Concept and Variants . 61.3Product Components . 61.4System Requirements . 71.5Additional Usage Scenarios . 71.5.1CANoe under „EULA“. 71.5.2CANoe under “ELA” . 71.6Further Information . 72Functions. 82.1Special Functions . 92.2Database Support. 103Analysis . 103.1Measurement Setup. 113.2Trace Window . 123.3Graphics Window . 133.4Scope Window . 143.5Data Window. 153.6Statistics Window . 153.7State Tracker . 163.8Write Window . 173.9Video Window. 183.10Map Window . 193.11Scene Window . 193.12Triggers and Filters . 203.13Logging/Replay . 204Stimulation/Simulation . 214.1Variables and Generators . 214.1.1Interactive Generator . 214.1.2Signal Generator . 224.2Set Start Values . 234.3Symbol Mapping . 244.4Interaction Layer, Network Management, Transport Protocols . 244.4.1OEM-Specific Extensions . 244.4.2Configuration of the Interaction Layer . 254.5MATLAB/Simulink . 254.5.1Further Functions of the CANoe MATLAB/Simulink Integration . 264.5.2Further Information . 275Test . 275.1Testing ECUs and Networks . 275.2CAN/CAN FD Disturbances . 315.3Further Information . 326Diagnostics . 322

CANoe6.1Further Information . 367SOA and AUTOSAR Adaptive . 367.1Communication Concepts – Current Developement . 367.2The CANoe Communication Model . 368Connectivity. 388.1Connection to Broker or Backend . 388.2VH4110 Hardware – “IoT Enabler” . 389ADAS . 3810Programming . 3910.1CAPL Interface . 3910.1.1C-Like Syntax . 3910.1.2Event-oriented Control. 3910.1.3Symbolic Access . 4010.1.4Application-Specific Language Extensions . 4010.2CAPL Browser . 4210.3.NET Programming . 4310.4Debugging . 4410.4.1Further Information . 4510.5Visual Sequencer . 4511Panels . 4512Hardware Interfaces . 4613Interfaces to Other Applications . 4713.1COM Interface . 4713.1.1Further Information . 4713.2FDX . 4713.3ASAM XIL API . 4713.4FMI . 4713.5CarMaker . 4814Real Time Execution . 4814.1Real Time Area on Separate Hardware. 4814.2Vector Tool Platform . 4915Option Scope . 5015.1Application Areas . 5015.2Overview of Advantages . 5115.3Supported Protocols . 5115.4Supported Oscilloscope Hardware . 5115.5Oscilloscope Software . 5115.5.1Configuration Functions . 5215.5.2Trigger Functions . 5215.5.3Analysis Functions . 5215.5.4Offline Functions . 5216Option Sensor . 5316.1Application Areas . 5316.2Supported Sensor Protocols . 533

CANoe16.3Supported Serial Protocols . 5416.4Highlights . 5417Option SmartCharging . 5518Option AMD/XCP . 5618.1Application Areas . 5618.1.1Calibration Protocol (XCP) / CAN Calibration Protocol (CCP) . 5618.1.2AUTOSAR Monitoring and Debugging (AMD) . 5618.2ECU Access . 5718.2.1Supported Bus Systems and Protocols . 5718.2.2VX1000 Measurement and Calibration Interface . 5718.2.3CSM Measurement Module . 5718.2.4Hardware Debugger Support. 5718.3Overview of Advantages . 5818.4Functions. 5818.5Integration in CANoe . 5918.6Configuration . 5919Functional Extensions for Special Applications . 6019.1DiVa (Diagnostic Integration and Validation Assistant) . 6020Training . 60V6.4 10/2021Valid for CANoe from version 15.0.This document presents the CANoe use areas of analysis, stimulation/simulation, testing, diagnostics and their individualfunctions. The document also contains a brief overview of programming in CANoe, supplemental options and programs aswell as hardware and software interfaces.Product information and technical data on CANoe options are provided in separate documents.4

CANoe1Introduction to CANoeCANoe is a versatile tool for the development, testing and analysis of entire ECU networks as well as individual ECUs. Itsupports network designers, development and test engineers at OEMs and suppliers over the entire development process –from planning to the start-up of entire distributed systems or individual ECUs.At the beginning of the development process, CANoe is used to create simulation models which simulate the behavior of theECUs. Over the further course of ECU development, these models serve as the basis for analysis, testing and the integrationof bus systems and ECUs. This makes it possible to detect problems early and correct them. Graphic and text based analysiswindows are provided for evaluating the results.CANoe contains the Test Feature Set for easy and automated test execution. It is used to model and execute sequential testsequences and automatically generate a test report. The Diagnostic Feature Set is also available within CANoe for diagnosticcommunications with the ECU.Figure 1: CANoe user interface5

CANoe1.1Bus Systems and ProtocolsIn CANoe, various options are available for the different bus systems and CAN-based protocols, and any combination of theseoptions may be used.CANoe supports the following bus systems: CAN, CAN FD, LIN, MOST, FlexRay, J1708, Ethernet, K-Line, A429, WLAN andAFDX 1Option CAN is the basis for these supported CAN-based protocols:J1939, ISO 11783, CANopen, GMLAN, CANaero.Others upon request.You will find detailed information on the options in separate product information documents.1.2Product Concept and VariantsCANoe is available in the following variants for special purposes at OEMs and suppliers: With full range of functionality As a Runtime (run) variant with unmodifiable simulations, full range of analysis functions and easyactivation/deactivation of individual network nodes. This variant is intended for users who wish to quickly and simplytest their ECU in interaction with a prescribed remaining bus simulation. As a Project Execution (pex) variant with just a graphic user interface. The test cases and results are very easy to controlwithout requiring special evaluation of the underlying messages.The CANoe/CANalyzer compatibility mode lets you use both programs, e.g. within a project or an organization, by exchanginguniform configurations. Then the appropriate program can be used in the optimal variant for each use case. During ECUdevelopment, the full variant of CANoe is used, while system integrators and test drivers can use the same configuration inCANalyzer to test the bus communications.1.3Product ComponentsThe product contents depend on the selected product variant. The full version contains the following components in additionto CANoe itself: Numerous sample configurations of the overall system, on all installed bus system options and on special use cases suchas testing and diagnostics Editors and display programs for various database formats, for panels and for CAPL programming Installation instructions, manuals and help functions Transport protocol (TP) per ISO/DIS 15765-2 and the interaction layer (IL) according to Vector specificationOther modules, such as OEM-specific TP or IL, are not included with the standard product, but they can be obtained fromSupport at no extra charge.1AFDX is a registered trademark of Airbus6

CANoe1.4System RequirementsComponentProcessorRecommendedMinimum Intel Core i7 or comparable Intel compatible 3 GHz 2 GHz 4 cores 2 coresCANoe benefits from higher clock rates rather than higher number of cores.Memory (RAM)Hard Disk SpaceScreen resolutionOperating system*1.5 32 GB4 GB 20 GB SSD/NVMe8 GB HD/SSDDepending on options used and required operating system components.Full HD1280 1024 PixelsWindows 10 64 bit ( version 1803) Windows 10 64 bit ( version 1803)* Not virtualized. Running in a virtual machine is possible but not tested. Operationwith Vector hardware may be affected by virtualization (e.g. higher latencies mayoccur).Additional Usage Scenarios1.5.1 CANoe under „EULA“In addition to Section 2.1 of the "End User License Agreement for Vector Standard Software Products", the following usagescenarios are permitted for CANoe; "CANoe automation or remote access to CANoe is allowed with a device license if CANoeis operated in order to access a real system with Vector hardware (VN, VT, VX) (for example at a test station or in a serverenvironment)".1.5.2 CANoe under “ELA”In Addition to Section 2.1 and 2.2 of the “Enterprise Licensing Terms and Conditions for Vector Standard Software Products”the following usage scenarios are permitted for CANoe; "Automation of CANoe or remote access to CANoe is allowed with adevice license and/or named user license if CANoe is operated to access a real system with Vector hardware (VN, VT, VX) (forexample at a test station or in a server environment).“1.6Further Information Vector Support & Downloads Demo versionA demo version is available on the web for CANoe. It contains sample configurations for the various application areasas well as a detailed help function, in which all CANoe functions are described. Application notesIn the following chapters, we refer to additional application notes that offer in-depth information on the individualapplication areas. CANoe Feature MatrixMore information on variants, channels and bus system support is presented in the feature matrix.7

CANoe2FunctionsBasic CANoe functions include: Use of databases that describe the specific network (e.g. DBC, FIBEX, LDF, NCF, AUTOSAR System Description, MOSTFunction Catalog) Simulation of entire systems and remaining bus simulations Analysis of the bus communications Testing of entire networks and/or individual ECUs Diagnostic communication per KWP2000 and UDS and use as a fully functional diagnostic tester User programmability using the CAPL programming language to support simulation, analysis and testing Creating customized user interfaces to control the simulation and tests or to display analysis data Integration of additional I/O hardware and/or special test hardware (VT System) Intuitive user interface with flexible docking concept and user-friendly menu structures Support of new Vector bus hardware: VN1610 (2 channels – CAN) VN1611 (2 channels – CAN and LIN/K-Line) VN1630 (4 channels – CAN and LIN/K-Line) VN1640 (4 channels – CAN and LIN/K-Line)8

CANoe2.1Special FunctionsCANoe highlights include: For critical, real-time relevant simulations and tests, CANoe operates in a distributed mode on two PCs Numerous add-ons make it easy to adapt to OEM-specific services and protocols (transport protocols, networkmanagement, Interaction Layer, etc.) Diagnostic functions: Parameterization of diagnostics by diagnostic descriptions as ODX 2.0.1/2.2.0, MDX 2.0/3.0 or CDD Definition of simple diagnostic services with the Basic Diagnostic Editor Support of physical and functional addressing Quick and simple On-Board Diagnostics with built-in OBD-II tester Diagnostic observer for UDS and KWP2000 based on parameterizable diagnostic descriptions Transport protocol observer for ISO/DIS 15765-2 Support of DoIP (Diagnostics over IP) and HSFZ (High-Speed Fahrzeugzugang) Special diagnostic CAPL functions for simulating and testing ECUs The Vector VT System enables comprehensive ECU tests in which I/O lines are used in addition to bus access Test cases may be linked to requirements using commonly used requirements tools such as Telelogic DOORS CANoe supports integration of MATLAB/Simulink models CANoe can be used as a runtime environment for the ECU code of AUTOSAR or OSEK-OS applications Access to internal ECU signals over XCP/CCP including protocol disassembly and analysis for CAN, CAN FD, FlexRay andEthernet Control of digital and analog I/O modules as well as measurement hardware permits processing of real signal values insimulations and test environments Open software interfaces, such as Microsoft COM, FDX, FMI or ASAM XIL API, enable integration in existing systemenvironments. Access to connected systems with IoT protocols and back end with the Connectivity Feature Set (CFS)9

CANoe2.2Database SupportCANoe supports system descriptions based on the following formats: DBC (CAN), LDF (LIN), XML (MOST), FIBEX (FlexRay)and AUTOSAR descriptions (CAN/FlexRay/Ethernet).CANoe can process the following diagnostic descriptions: CDD (CANdelaStudio), ODX 2.0.1/2.2.0 as PDX files and MDX2.0/3.0.Information of these databases can be symbolically displayed and used in CANoe.Figure 2: Trace Window with analysis filters3AnalysisThe basis for analysis in CANoe is the data flow from the data source to its display or logging. The data may also be processed.For example, filters can be integrated that define which data should be considered in an analysis and which data should not.Highlights Easy to configure the analysis window by drag and drop. For example, this method can be used to copy or movemessages or signals from one analysis window to another. For a multifunctional analysis, one type of window (e.g. Graphics Window) can be integrated multiple times in the dataflow, which enables parallel analysis. Easy start and stop logging directly from the status bar.CANoe supplies the user with windows and blocks such as those described below.10

CANoe3.1Measurement SetupThe data flow is graphically represented and configured in the Measurement Setup. Define data source (online/offline)The simulated bus or the real bus connected via the hardware (e.g. VN1630) serves as the online data source.A file with logged data serves as the offline data source. Insert analysis windowsData can be shown differently in the individual windows depending on analysis requirements, e.g. to graphicallyrepresent signal waveforms or to display signal values. Insert CAPL program nodesA CAPL program node can be used for such tasks as filtering data or

CANoe 5 1 Introduction to CANoe CANoe is a versatile tool for the development, testing and an