Vehicle Control Unit Programming via Persistent Bus Idle Mode
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of vehicle control units requires efficient methods for programming multiple control units simultaneously, as existing methods often necessitate updating one unit to adapt to others, and serial writing processes are time-consuming and prone to errors due to limited bus capacity.
Innovation Solution
A method and system that place control units in a persistent bus idle mode, allowing for quasi-parallel firmware writing by overlapping writing processes in time, with a tester managing the process and setting flags to maintain idle mode, and specifying maximum execution times to prevent endless loops, while dividing software into sub-units for efficient transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If serial writing processes are used for control units, then transmission errors are avoided, but programming time increases significantly
Solution Approach 1:
The system places control units into a persistent bus idle mode before the writing process begins. This preliminary action ensures that control units do not send spontaneous messages during firmware transmission, preventing transmission errors while enabling parallel writing operations to reduce programming time
Solution Approach 2:
The system dynamically manages bus access by switching control units between persistent bus idle mode during writing and normal operation mode afterward. This dynamic state management allows the system to achieve both reliability during transmission and efficiency through parallel processing
2Loss of time
If multiple control units are programmed in parallel, then programming time is reduced, but bus capacity limitations cause transmission errors
Solution Approach 1:
The persistent bus idle mode is activated before parallel writing begins, creating a controlled environment where control units will not initiate spontaneous communications. This preliminary configuration enables safe parallel programming without exceeding bus capacity
Solution Approach 2:
The system uses a persistent flag mechanism that provides feedback about the bus idle state. This flag ensures that control units remain in the required state throughout the writing process and are only switched back to normal operation after successful firmware transmission, maintaining reliability during parallel operations
3Reliability
If control units are switched to programming mode individually, then transmission reliability is maintained, but the programming process becomes complex and time-consuming
Solution Approach 1:
The system merges the state management of multiple control units by using a persistent bus idle mode that applies to all units simultaneously. This eliminates the need to individually manage programming modes for each control unit, reducing process complexity while maintaining transmission reliability through parallel operations
Data Source
Figure 1
Figure 2
AI summary
The invention relates to a method for programming a plurality control units (5a, 5b, 5c, 5d, 5e) of a vehicle by means of a bus (10), wherein the control units (5a, 5b, 5c, 5d, 5e) are each put into a mode of persistent bus idle, in which mode the control units (5a, 5b, 5c, 5d, 5e) each send messages on the bus (10) only when the messages are requested from outside of the particular control unit (5a, 5b, 5c, 5d, 5e). While the control units (5a, 5b, 5c, 5d, 5e) are in the mode of persistent bus idle, new firmware (FW_i) is written to the control units (5a, 5b, 5c, 5d, 5e) in a writing process (10) of the particular control unit (5a, 5b, 5c, 5d, 5e), wherein at least a subset of the control units (5a, 5b, 5c, 5d, 5e) is written to in such a way that the particular writing processes of the subset of the control units (5a, 5b, 5c, 5d, 5e) overlap in time.