Canoe - the third simulation project - bus simulation-1 overview

The following is from 《CANoe Development from entry to mastery 》

Catalog

Bus simulation engineering

General of simulation engineering development technological process

Development strategy

---

Bus simulation engineering

Bus simulation engineering runs through ECU The whole process of development , Involving demand analysis 、 software development 、 software test 、 Environmental testing 、 Hardware verification 、 Production inspection 、 Failure analysis 、 Customer support and other functional departments .

For complex functions ECU, Its requirements for the test environment are also very complex , Often more dependent on the simulation environment .

Bus simulation engineering ： Demand analysis 、 Planning and design 、 Code implementation 、 Test verification 、Bug Repair and project release .

 

General of simulation engineering development technological process

1. Vehicle factory input （ Network topology ,SIgnal Matrix, Product technical specifications ）
2. establish DBC file （DBC file ）（ Input of bus simulation requirements within the project --4 Network test demand analysis ）
3. Import DBC File to CANoe In simulation engineering （Simulation Setup Automatic generation of network topology ）
4. Network test demand analysis （ Simulation project design plan ： Simulation panel 、 Test node 、 Test module 、 Diagnostic criteria 、 Analysis window 、 Automation strategy ）
5. Modify or add nodes （Simulation Setup Network topology update ）
6. Add system variables （ System variables ）
7. Add simulation panel （ Simulation panel design ）
8. add to CAPL Code （CAPL Programming ）
9. Add graphical analysis window and Logging function （ Analysis window configuration ）
10. Add test cases and test modules （ Test function development ）
11. add to CDD File and diagnostic functions （CDD The document is provided by the developer ）（ Diagnostic test function ）
12. Add other accessibility （ External software control 、 Network communication, etc ）（ Other auxiliary functions ）
13. Simulation engineering test and release

Development strategy

In the face of different vehicle manufacturers and different products , We need to further analyze the needs and formulate some strategies , Otherwise, more simulation projects may not meet the needs of the project .

TIPS：

1. Strive to get the original vehicle factory Of DBC file ： It can save a lot of time , Ensure the accuracy of the database
2. Do a good job in the analysis of early product development documents ： Find the network —— Related functions 、 Related messages 、 Related nodes
3. Listen to the needs of project members ： The needs of software developers 、 Requirements of functional testers 、 The Internet \ Diagnostic testing shoe needs 、 The need for automated testing 、 Requirements for hardware verification and environmental testing 、 Needs of on-site technical support personnel
4. Understand the simulation of key nodes and the switching plan of real nodes ： Understand the sample plan of the project 、 Whether you can get others in the development stage ECU And whether the vehicle manufacturer provides test vehicles and other information .
5. For key nodes , Strive to get the corresponding ECU Module samples , Because simulation may not replace nodes in some cases , The existing risks must be avoided as far as possible
6. Simplify topology , Planning panel and code design
   1. For critical nodes , Guarantee its independence , Key functions can be simulated independently , It can also be closed at any time , Replace with real nodes
   2. For secondary nodes （ There is not much data exchange ） Or indirect nodes （ Not on the same bus ） Relevant simulation functions can be placed on a panel .
   3. For the node to be tested （ The project needs to be developed ECU）, According to the needs of xiangmanyuan , Decide whether to develop relevant simulation functions , If there is no need to do any preliminary simulation evaluation , Consider not developing （ Directly in Simulation Setup Turn this node off ）
7. Before release , Make the configuration , Different from giving consideration CANoe Version compatibility .
8. Before releasing the simulation project , You can take some protective measures against the code , Avoid arbitrary modification by others .
9. When releasing the simulation project , You need to attach the release document , And do a good job of version control .