Master Slave Software Distribution in Vehicle Control Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating software in networked control devices of motor vehicles, such as electronic braking systems, are time-consuming and costly due to the need for manual compatibility checks and version management across multiple control units, which hinders efficient maintenance and development.
Innovation Solution
A system where a master device stores and manages software and parameters for slave devices, ensuring compatibility by transferring necessary software and parameters automatically via a network, using a basic software module that remains unchanged across generations, allowing for independent programming of slave devices based on their hardware and software requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual compatibility checks and version management are performed across multiple control units, then software compatibility is ensured, but the updating process becomes time-consuming and costly
Solution Approach 1:
The master control unit stores multiple software versions in advance for different slave control units. Before actual updates are needed, compatibility is pre-established by maintaining a repository of verified software versions, eliminating the need for time-consuming manual compatibility checks during update operations.
Solution Approach 2:
The master control unit acts as an intermediary between software developers and slave control units. It centralizes the storage and management of software versions, automatically selecting and distributing compatible software to slave units, thereby eliminating manual compatibility verification across multiple control units.
2Reliability
If manual compatibility checks and version management are performed across multiple control units, then software compatibility is ensured, but the process becomes costly
Solution Approach 1:
The master control unit serves as a central intermediary that automates the software distribution process. It stores multiple software versions and automatically selects compatible versions for slave control units, eliminating the need for costly manual compatibility verification and reducing maintenance expenses.
Solution Approach 2:
The system enables self-service software updates where the master control unit autonomously manages software version distribution. The automated selection and distribution of compatible software versions eliminates the need for expensive manual intervention, allowing the system to maintain compatibility independently.
3Device complexity
If a basic software module remains unchanged across generations, then programming complexity is reduced, but software functionality may become limited
Solution Approach 1:
The software architecture is segmented into a stable basic module that remains unchanged across generations and variable software versions that provide updated functionality. The master control unit stores multiple versions of the variable software, allowing slave control units to maintain simple, unchanged basic modules while still accessing updated functionality through version selection.
Solution Approach 2:
The unchanged basic software module is designed to be universal and compatible across multiple generations of slave control units. By maintaining a core module that works with different hardware versions and storing multiple software versions at the master unit, the system achieves both simplicity and adaptability.
Data Source
Figure 1
Figure 2
AI summary
A method for distributing and/or updating software in interconnected control devices, in particular those of a motor vehicle, involves; storing at least one factory-side preprogrammed base module for the initialisation and programming of one of a plurality of programmable sub-control devices, forming part of an interconnected system of control devices, in a respective first storage region of each sub-control device; storing factory-side preprogrammed operating modules for all of the plurality of programmable sub-control devices of the interconnected sub-system in at least one main control device, in turn forming part of the interconnected sub-system of control devices, in second storage region of the main control device, at a predetermined time; and/or optionally transmitting at least one operating module, provided for at least a determined one of the plurality of programmable sub-control devices, independently from the main control device to the at least one determined sub-control device; and independently and operationally programming the at least one determined sub-control device with the at least one operating module received from the main control device, using the base module. An underlying system can be an electronic brake system of a vehicle, in which the main control system forms a central and/or a master device, which is connected via a CAN bus as a network to at least one wheel pressure regulation module (EPM), a foot brake module (FBM) and/or a trailer control module (TCM) as programmable sub-control devices, each forming slave devices.