教案m学习汇总vehicle network toolbox

1、Vehicle Network ToolboxCommunicate with in-vehicle networks and access ECUs using CAN and XCP protocols® and Simulink® usingfunctions and Simulink blocks to send,Vehicle Network Toolbox provides connectivity to CAN devices fromindustry standard CAN database files. The toolbox provides Mrec

2、eive, encode, and decode CAN and XCP messages, enabling you to exchange messages between a CAN bus andyour programs and ms. You also can connect to an ECU via XCP on CAN using A2L description files.Fromor Simulink, you can monitor, filter, and analyze live CAN bus data or log and record CANmessages

3、for later analysis and replay. You also can simulate message traffic on a virtual CAN bus or connectSimulink ms to a live network or ECU. Vehicle Network Toolbox supports CAN interface devices fromVector, Kvaser, and National Instruments.Key Featuresfunctions for transmitting and receiving CAN and X

4、CP messagesSimulink CAN and XCP blocks for connecting a mto a CAN bus or ECUVector CAN database (.dbc) file and A2L description file supportSignal packing and unpacking functions and blocks for simplified encoding and decoding of CAN messagesMessage filtering, logging, and replay functionsVehicle CA

5、N Bus Monitor app to configure devices and visualize live CAN network trafficSupport for Vector, Kvaser, and National Instruments® CAN interface devices1Simulink millustrating a host mfor host-target CAN communication. This host menables the exchange ofCAN messages between the host mon your PC

6、and a target mrunning on your target hardware.CAN Bus Communication fromand SimulinkVehicle Network Toolbox lets you interact directly with a CAN bus fromor Simulink. You can executeprograms. The toolbox also containstoolbox functions from thecommand line and throughSimulink blocks that enable you t

7、o conneimulink mto a CAN bus.Configuring CAN ChannelsCAN channel functions inand CAN configuration blocks in Simulink enable you to define aconnection to Vector CAN interface hardware that establishes a physical connection with a CAN bus. The toolboxprovides CAN channel functions to query and config

8、ure CAN interface hardware settings, such as bus speed and transceiver settings. You can also verify other CAN channel properties, such as the number of messages available and the number of messages received or transmitted on the channel. By attaching Vector CAN database files to CAN channels, incom

9、ing messages are automatically presented using information stored in the database. After defining a CAN channel, you can send and receive CAN messages on the channel.Sending and Receiving CAN PacketsCAN messages contain properties for storing the CAN message identifier (standard 11 bit or extended 2

10、9 bit), thetime stamp, and up to 8 bytes of CAN data. Transmit and receive functions and blocks in the toolbox enable the sending and receiving of CAN messages over CAN channels. For large data sets, you can log CAN messages for offline analysis.2Building and Extracting Signals from CAN MessagesVehi

11、cle Network Toolbox provides functions and blocks for encoding and decoding CAN messages. CANmessage data may contain data representing multiple signals. Unpack functions and blocks let the user specify start bit, signal length, data type, and byte ordering. Pack functions and blocks provide the sam

12、e options for building up data for CAN message transmission.Logging and Replaying CAN messagesUsing the CAN Log block in the toolbox, you can save CAN messages received by your mto a MAT file. Youcan then use the CAN Replay block to replay the messages in another Simulink m. The CAN Replay blockpres

13、erves the time stamps of the logged data so the replayed data will have the same timing characteristics as therecorded data.Communicating over the XCP ProtocolVehicle Network Toolbox provides functions and blocks for communicating with ECUs via XCP an automotivecalibration protocol over CAN bus. Whe

14、n communicating with ECUs over XCP,or Simulink is themaster and the ECUs are slave devices. You can communicate with multiple ECUs by opening multiple XCPchannels. For each ECU, you can read and write data to specific memory locations within the ECU. When secured access to an ECU exists, you can use

15、 seed and key security to open access to the ECU. The toolbox also provides functions and blocks for linking A2L database files and for creating and viewing dynamic DAQ and STIM measurement lists for an XCP channel. These lists are established based on measurement and event information from the link

16、ed A2L file.Mfor acquiring measurements from an ECU slave device. The muses XCP Configuration and XCP TransportLayer blocks (top left), and XCP Data Acquisition blocks (bottom left) to set up the acquisition of the PWM signal (right).3Visualizing CAN Traffic and Handling CAN MessagesThe toolbox prov

17、ides a Vehicle Network CAN Bus Monitor app for visualizing active traffic on a particular CANchannel. You can use the app while performing other tasks inor Simulink. For CAN database filesassociated with your CAN channel, the app decodes the messages and displays them in their correct engineeringuni

18、ts.When traffic on the network contains more information than needed for your application, you can limit thenumber of CAN messages received by a CAN channel to a defined range of CAN message identifiers. Using filter functions and mask settings in the toolbox, you receive only the messages needed fo

19、r your application.Live CAN bus traffic on the network displayed by the Vehicle CAN Bus Monitor app. The display shows raw data; it can be configured to show decoded data when the CAN channel is associated with a .dbc database file.Using Vector CAN Database FilesVehicle Network Toolbox lets you asso

20、ciate a Vector CAN database file with a CAN channel or message fromor Simulink, enabling you to encode and decode CAN messages using application specific message and signal names such as EngineMsg and EngineRPM, as well as scaled engineering units. The ability to work with industry standard database

21、 files simplifies the interaction with the CAN bus because the database not only specifies the message list and component signals, but also provides the bit packing and unpacking rules for the associated signals. Because signal data type, start bit, length, and byte order are all predefined for the

22、messages in the database, you can focus on analyzing your signals rather than on defining them.4Code example showing how to view messages using information stored in CAN database files.Using A2L Description FilesVehicle Network Toolbox lets you use industry standard A2L (also known as ASAP2) descrip

23、tion files tocommunicate with ECUs over the XCP protocol fromyou to access internal ECU parameters from aor Simulink. Using A2L description files enablesprogram or a Simulink m. A2L description filescontain information about the associated memory address for a particular parameter, the storage structure, andthe data type. The files also contain rules for converting stored values such as system parameters, sensor characteristics, and correction factors into physical units such as