JP2001239901A - Control method of vehicle and device therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an improved software structure identifier or soft architecture identifier in a control device for controlling a vehicle. SOLUTION: Respective components have base variants and functional variants, and are made to correspond to each other. A first identifier is univocally made to correspond to the respective components. A second identifier is made to correspond to the respective base variants and the respective functional variants of the respective components. A vehicle is controlled by using an identifier block of the respective components having components to which the first identifier, the second identifier and the first identifier of the respective components are made to correspond.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and a device for controlling a vehicle, and more particularly to a vehicle having a data structure and / or a program structure having a vehicle component, a coordination component, a functional component and a component interface. The present invention relates to a control method and an apparatus therefor.

[0002]

2. Description of the Related Art A conventional vehicle electronic system is disclosed in DE 41 11023 A1 (US Pat.
76). The system disclosed in the above publication is a device for executing at least a control task relating to an engine output, a drive output, and a braking process, and coordinating (coordinating) the cooperation of a control task execution device so as to control drive control of a vehicle according to a driver's intention. Device.

The above devices are arranged in a hierarchical manner, and at least one adjusting device in one hierarchical plane is a device of an adjacent hierarchical level (ie, a preset lower system of a driver-vehicle system). In order to provide the characteristics required for the lower system by the higher hierarchy, the intervention is performed by converting the driving characteristics into the driving characteristics corresponding to the driver's intention.

Furthermore, German Offenlegungsschrift DE 19709
No. 317A1 discloses a method and apparatus for controlling a vehicle having at least one source of at least one resource and at least one load consuming this resource. Such a control device allocates at least one resource to the load according to the source potential and the resource demand of the load.
There are two coordinators.

In the above prior art, the data structure and / or the program structure cannot be shown entirely using the control device software. Such controller software is usually divided into programs and data. Also, the program is usually provided with a dataset variant based on the selection of the dataset. The two parts (ie, program and data) are stored in the controller program or data memory.

[0006] In order to characterize and verify the program set and the data set, an identifier is stored in a hexadecimal file, for example. In the prior art, it usually comprises a software-program identifier with shorthand symbols for the project and program version, and a dataset identifier with shorthand symbols for the project and dataset variants. In this way, the functionality of the software residing in the control unit is derived using the above identifiers and the overall functionality of the defined program version from the software-function-documentation.

[0007]

However, at this time, since the single-source principle has not been provided, ie without the principle of combining change information, the program and the documentation must be supplied separately from different sources at different times. The compatibility check is very troublesome.

The prior art data structures and / or program structures and their representation correspond to a table of contents for functional documentation. It does not, for example, reproduce the functional content of the component with respect to the variant used. Thus, the prior art cannot obtain favorable results in every respect.

Accordingly, it is an object of the present invention to provide a new and improved vehicle control device capable of realizing an improved software structure identifier or software architecture identifier in a control device for controlling a vehicle. is there.

[0010]

According to another aspect of the present invention, there is provided a data structure and / or a program structure having a vehicle component, a coordination component, a functional component and a component interface. A control method for a vehicle as shown, wherein each component has a base variant and a function variant and is associated with each other, and each component is uniquely associated with a first identifier, A second identifier is associated with each of the base variants and each of the functional variants of the component, and a first identifier, the second identifier, and the component with which the first identifier of each of the components is associated. Has an identifier block for each component And use, to control the vehicle, the vehicle control method according to claim is provided that.

According to the invention described in this section, since each identifier can be transmitted to all the identifier blocks of each component together, the integration test and especially the application itself can be simplified. In particular, all the messages used by the component can be displayed in the application via the input of the component label or component identifier. Thus, especially in an application, all information about the functionality of the component is made visible through a small input in the application tool. Therefore,
No documentation is required or incomplete documentation of data and messages is recognized very quickly. Preferably, the source code structure and the data storage structure are consistent with the underlying data structure and / or program structure. This means that all processes of a component or the software files belonging to it have the labels or identifiers of the components of the underlying data structure and / or program structure (architecture).

Further, as in the second aspect of the present invention, the component interface is formed as a message exchanged between the components.
Preferably, the message comprises at least one identifier of the transmitting component identifier block and / or the receiving component identifier.

According to a third aspect of the present invention, the component interface is formed as a message exchanged between the components.
Preferably, the message comprises an identifier block of the transmitting and / or receiving component.

According to the present invention, a unique association between the components is guaranteed through the inspection of the identifier block, and an error response is generated when an error is detected. With such a configuration, the component identifier and the identifier of the base variant and the function variant arranged in association with this identifier at a higher level uniquely reproduce the component position and the functional content inside the architecture.

According to a fifth aspect of the present invention, all the identifier blocks are stored at predetermined addresses in a memory area of a control unit for controlling the vehicle, and the identifier blocks are generated by an auxiliary component. With such a configuration, for example, it is taken in by Makelan (Makelauf) and all the identifier blocks are stored at a predetermined address (for example, a hexadecimal file), so that the software in the field can be used at any time. Can be quickly identified.

According to a sixth aspect of the present invention, the data structure and / or the program structure may be output using the identifier block or displayed on a display means. Auxiliary components or other auxiliary components can read the identifiers in an efficient manner, for example to provide a graphical representation of the architecture (ie, data structure and / or program structure). For example, an error message can be displayed to the vehicle occupant in the vehicle. Similarly, other people (especially factory people)
Can better track the structure.

According to another aspect of the present invention, there is provided a semiconductor device comprising:
A vehicle control device comprising a vehicle component, a coordination component, and a functional component, wherein each of the components exchanges messages via a component interface, wherein each of the components includes a base variant and a functional variant. A first identifier is uniquely associated with each component, a second identifier is associated with each base variant and each functional variant of each component, A first identifier of each of the components,
A vehicle control device comprising an auxiliary component for storing, in a memory in a control unit for controlling a vehicle, a component associated with an identifier of the component and an identifier block having a second identifier of the component. Is provided.

In the invention described in this section, the component blocks for each component can be used for vehicle control.

[0019]

Preferred embodiments of the present invention will be described below in detail with reference to the accompanying drawings.
In the following description and the accompanying drawings, components having the same functions and configurations are denoted by the same reference numerals, and redundant description will be omitted.

(First Embodiment) First, a first embodiment will be described with reference to FIG. Figure 1
FIG. 2 is a block circuit diagram illustrating a configuration of a control system according to the first embodiment.

First, as shown in FIG. 1, a control unit 100 for controlling an engine or a drive unit includes, as hardware, an air system control (particularly, air amount measurement)
101, an injection system control (especially fuel quantity measurement) 102, optionally, for example, ignition control 1 of a gasoline internal combustion engine
02o or a glow system for a diesel internal combustion engine.

Furthermore, the drive mechanism or engine mechanism control calculates, for example, engine drag torque, prevents mechanical overload, and determines the engine speed and crankshaft angle.

A control unit 105 for controlling the braking or braking process, a control unit 104 for controlling the automatic transmission and / or a control unit 106 for controlling the chassis adjustment or controlling the driving dynamics are provided. In the control unit 106, a steering control (steer-by-wire) 106o that can selectively intervene in the steering system is provided.

Further, in a vehicle electric system which is electronically controlled, a control unit 116 for controlling the vehicle electric system can be used. A control unit for controlling each or a plurality of sub-aggregates or a display device is built therein. In addition, the control unit 116o of the air conditioner can be selectively built in the unit 116.

Each control unit or control device is connected via a wire system or a bus system 111 (for example, a CAN bus), and information and data are exchanged with each other.

Various measuring devices 109 and 110 are connected to the conductor system or the bus system 111 via, for example, two suitable conductors 114 and 115. In the present embodiment, a configuration employing two various measuring devices will be described as an example, but any measuring device can be installed. Each of the measuring devices 109 and 110 detects a driving amount of a vehicle (particularly, an engine and a drive train).

At this time, the detected drive amount includes, for example, engine speed, engine temperature, driven speed, transmission position or gear ratio, gear stage information, converter slip, turbine speed, generator speed, running speed, battery speed. This is a general driving amount such as a voltage. In addition,
The operating devices 107 and 108 are connected to the bus system 111 via suitable conducting wires 112 and 113. Such an actuator corresponds to, for example, an actuator in a vehicle.

Such actuators include, for example, an ignition system, an electrically controllable throttle valve, a fuel injection system, an actuator of an automatic transmission such as a clutch or a chassis actuator such as an electrically controllable spring damper member, a pressure system for brake operation, a steering area. For example, an electric window lifter, a sliding door of a vehicle body, a servo motor of an indoor electronic device, and the like correspond to the servo pump in the inside. In the present embodiment, two operation devices (actuators) are illustrated, but any number of operation devices (actuators) can be installed.

For example, two display members 117, 118, optical or acoustic, are connected to the bus system 111 via suitable conductors 119, 120 and are provided, for example, in the body electronics and the room electronics.

The control unit detects a corresponding function and a required drive amount, and forms operation values of various operation devices and display members. With such a complex system, each member or functional unit is not separate but can be considered integrally as a whole concept. Furthermore, for example, environmental quantity,
By accessing data and information of other functional units and systems, such as vehicle state variables, vehicle variables and user variables, vehicle control optimally adapted to each condition can be performed.

Next, a data and / or program structure or a software architecture according to the present embodiment will be described with reference to FIG. FIG. 2 is an explanatory diagram generally showing a software structure or an architecture (a data structure and / or a program structure of a vehicle). Such a structure reflects the functionality of the software.

First, as shown in FIG. 2, the basic device having such a structure is a vehicle component or an engine component-oriented component (a so-called vehicle component). Furthermore, it has a component (so-called adjustment component) for adjusting the cooperation of the components that execute the control task.

Further, it has function-oriented components (so-called function components) instead of hardware, and represents functions. The interface of each component is defined as a message. The message first checks the information (the question mark is the identifier),
Alternatively, it can be set (the exclamation point is the identifier). Note that the direction of message transmission is indicated by an arrow.

The messages are denoted by reference numerals 414 and 41.
5,416,408,409,410,421,42
2, 423 and 421a through 423a and 306.

The components 300, 301, 302,
303, 304, 305, 400, 401, 402, 4
03,404,405,406,407,411,41
The labels 2,413,417,418,419,420 are simultaneously used as their first identifier. Generally, an identifier is realized by one or more digits, a number, a character, or a combination of a number and a character.

That is, the entire vehicle system is composed of components / vehicles, component / vehicle coordinator, body and interior 301, vehicle motion 302, vehicle electric system 303.
And drive 304, or are associated with them. Other components are further associated with such components.

The vehicle electric system 303 is associated with switching means 411 such as a start switch or an ignition switch, a generator 412, at least one battery 413, and their functions. The component vehicle electric system 303 inquires of the start permission 414 from the switching means 411. Similarly, components 413 and 41
The output is queried at 4,415,416.

The output is sent from the component vehicle electric system 303 to the component 412 by the message 415.
Is transmitted to In component vehicle motion 302, functional or hardware components for propulsion 405, braking 406, and steering 407 are added. Similarly, the coordinator vehicle motion 404 is also associated. Propulsion sets the torque on vehicle motion 302 via message 408. Vehicle motion 302 queries braking information from component 406 via message 409.

Similarly, the vehicle motion 303 is the message 41
Use 0 to inquire about the output of steering 407 or the output capture. For example, the component comfort electronic device 400 and the air conditioner 40
1, a telecommunication and multimedia 402 and a display member 403 are additionally provided.

The component vehicle sends a message 3 from the component drive 304 or the drive train.
Query the output via 06. For driving, the component drive coordinator 417 and the transmission 41
8, a converter 419 and an engine 420 are provided.

The gear ratio information is queried from the component transmission 418 via the message 421 by the component 304, and at the same time, the drive 304 sets the conversion ratio in the component 421a in the transmission 418.

The component interface between components 304 and 419 determines a friction inquiry via message 422 and optionally selects message 4
22a determines the setting of the slip. Similarly, a torque or a rotation speed is set to the engine component 420 via the interfaces 423 and 423a.

The above-described component division is shown as an example, and it is possible to further divide the components.

The components 300, 301, 302,
Labels such as 303, 304, and 305 are used as more specific clear identifiers. This is because each component of the architecture has a distinct first identifier (especially sign numbers 300, 301, 302, 303, 304, 30).
5,400,401,402,403,404,40
5,406,407,411,412,413,41
7, 418, 419, 420).

The first identifier is further generally indicated by the identifier 1K1. Each base variant and function variant of the embodiment is provided with an identifier K2 for each component.

These identifiers K2 are divided into a base variant identifier K2b and a function variant identifier K2f. An identifier block KB is generated for each component to uniquely identify the location and functional content of each component within the architecture.

Therefore, the identifier block KB303 of the component vehicle electric system is K2b (for example, 0
0), K2f (for example, 01), an identifier K1 of the vehicle electrical system 303, and an identifier K1Z300 of the associated component vehicle. Therefore, the vehicle electrical system identifier block KB
Is as follows.

300 303 01 00

For the component engine 420, the identifier block KB420 having the base variant 02 and the function variant 04 is as follows, for example.

304 420 04 02

In general, the identifier block KB is composed of an identifier KZ1 of the associated component (a component arranged higher in the hierarchical system), an identifier K1 of the component itself, a base variant identifier, and a function variant identifier K2 (K2b, K2f). ).

K1Z K1 K2f K2b

The identifier block KB is generated for each component by the auxiliary component.
This auxiliary component may be implemented in software or hardware, may be shown in the architecture as a unique component, or may be included in the central component (eg, vehicle) 300.

However, this tool can also be incorporated in a Makelanf by an external control unit and all identifier blocks KB
For example, it is stored at a predetermined address (for example, a hexadecimal file) in the memory of the control unit shown in FIG. This allows software that is always in the field to be quickly identified using the identifier block.

The other auxiliary component or the auxiliary component preferably reads out these identifier blocks or identifiers and, for example, graphically displays the architecture. These are useful in the application, and can display an error in the vehicle to the vehicle occupant via the display member 403. Similarly, other people (especially factory people) can better track the structure.

At this time, it is preferable that a function variant of the architecture can be set from the beginning. In this case, the difference between the target architecture and the actual architecture can always be compared and corrected in the make run. . Therefore, when the number of projects is large and diverse, the architecture is prevented from collapsing in the course of development time.

In addition, the underlying relationships in the architecture (eg, the relationship of component engine 420 to component drive or drivetrain 304) can be monitored when developing software or its control tasks to check for consistency. . This can be done, for example, in the case of an identifier (ie, a sign number) by forming a checksum of the basic relationship or by a comparison routine.

With the method described above, the software structure or architecture can also be proven, generally in the control unit.

The method according to the present embodiment is applied to the interface of each component (ie, the component interfaces 306, 414, 415, 416, 408,
409). At this time, the interface of each component is defined as a message. The message sent from the component has the component label or identifier in its label.

However, which message is received is usually only revealed from software code or documentation. Preferably, only one auxiliary means or auxiliary component is created, which generates data with information about the component interface, for example for an application. At this time, each identifier can be transmitted together up to all the identifier blocks of each component. Such a measure simplifies the integration test and especially the application itself.

In particular, all messages used by the component can be displayed in the application via input of the component label or component identifier. Thus, especially in an application, all information about the functionality of the component is made visible through a small input in the application tool. Thus, no documentation is required or incomplete documentation of data and messages is recognized very quickly.

Although the preferred embodiment according to the present invention has been described above, the present invention is not limited to this configuration.
Those skilled in the art can envisage various modified examples and modified examples within the scope of the technical idea described in the claims, and those modified examples and modified examples are also included in the technical scope of the present invention. It is understood to be included in.

[0063]

According to the present invention, each identifier can be transmitted together to all the identifier blocks of each component, thereby simplifying the integration test and especially the application itself. In particular, all the messages used by the component can be displayed in the application via the input of the component label or component identifier. Thus, especially in an application, all information about the functionality of the component is made visible through a small input in the application tool. Thus, no documentation is required or incomplete documentation of data and messages is recognized very quickly. Preferably, the source code structure and the data storage structure are
Overlaps the underlying data structure and / or program structure equally. This means that all processes of a component or the software files belonging to it have the labels or identifiers of the components of the underlying data structure and / or program structure (architecture).

[Brief description of the drawings]

FIG. 1 is a block circuit diagram showing a configuration of a control device for a vehicle according to a first embodiment.

FIG. 2 is an explanatory diagram showing a general software structure or architecture (vehicle data and / or program structure) according to the first embodiment;

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 Control unit 102 Injection system control (particularly fuel amount measurement) 104 Control unit 105 Control unit 106 Control unit 107, 108 Operating device 109, 110 Various measuring devices 111 Bus system 114, 115 Conductor 116 Control unit 117, 118 Display member

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Volker Pitzal, Germany 73550 Waldstetten / Wisgoldingen, Uhlandstrasse 21 (72) Inventor Ud Schulz, Germany 71665 Feichingen / Enz, Kornblumenweg 34

Claims (7)

[Claims] 1. A method for controlling a vehicle, represented by a data structure and / or a program structure having a vehicle component, a coordination component, a functional component and a component interface, wherein each component has a base variant and a functional variant. And each component is uniquely associated with a first identifier; each base variant and each functional variant of each component is associated with a second identifier; A first identifier of the component, said second identifier,
A method for controlling a vehicle, comprising: controlling the vehicle using an identifier block of each component having a component associated with the first identifier. 2. The component interface is configured as a message exchanged between the components, the message including at least one identifier of an identifier block of a transmitting component and / or an identifier of a receiving component. The method for controlling a vehicle according to claim 1, wherein: 3. The component interface according to claim 1, wherein the component interface is formed as a message exchanged between the components, and the message includes an identifier block of a component to be transmitted and / or received. A vehicle control method according to any one of the preceding claims. 4. The method according to claim 1, wherein an unambiguous association between the components is ensured through a check of the identifier block, and an error response is generated when an error is detected. Vehicle control method. 5. The method according to claim 1, wherein all identifier blocks are stored at predetermined addresses in a memory area of a control unit for controlling the vehicle, and the identifier blocks are generated by auxiliary components and stored in the memory area. The vehicle control method according to claim 1, wherein 6. The control method according to claim 1, wherein the data structure and / or the program structure is output using the identifier block or displayed on a display unit. 7. A control device for a vehicle, comprising a vehicle component, a coordination component and a functional component, wherein each component exchanges messages via a component interface, wherein each component has a base variant and a functional variant. And each component is uniquely associated with a first identifier; each base variant and each functional variant of each component is associated with a second identifier; An identifier block having a first identifier of the component, a component associated with the first identifier, and a second identifier of the component;
A control device for a vehicle, comprising an auxiliary component for storing in a memory in a control unit for controlling the vehicle.