DE102005051432A1 - Data transmission system for e.g. hybrid vehicle, has data transmission units structured in master-client-system architecture that enables flexible bidirectional data transfer between master-control unit and client-control units - Google Patents

Abstract

The system has data transmission units for transmitting and receiving data information. The data transmission units are structured in a master-client-system architecture (1), which enables a flexible bidirectional data transfer between a master-control unit (2) and client-control units (3, 5, 7, 9, 11) that are assigned in the master-control unit. A bidirectional transfer protocol for transmission of energy data to an electrical energy on-board supply system of a motor vehicle is defined in the master-client-system architecture.

Description

The The invention relates to a data transmission system for controlling and regulating operating procedures in motor vehicles, with Data transmission means for sending and receiving data information.

The increasing complexity and networking of electrical / electronic systems in motor vehicles requires a systematic structuring of all control functions. So have to reduce costs and improve compatibility in the Implementation of these systems already different car manufacturers as well as system suppliers in the industrial partnership AUTOSAR (Automotive Open System Architecture) merged to form a standardized Concept for to develop the vehicle electrics / vehicle electronics.

When a major problem has been the increasing bus load of the for data transmission usually used data bus (CAN bus, LIN bus) in the electrical system by rising to be transferred Amounts of data and suddenly occurring data aggregates, so-called data bursts, exposed. Specific solutions for new data buses are due to the high costs and the incompatibility to customary systems to cope with the data transfer rather suboptimal.

From the DE 101 48 331 A1 a data transmission system is known in which the bus load is reduced by reducing the interrupts.

The Using interrupts is necessary because of a microprocessor Only one statement can execute at a time. Meanwhile, meet important data these are treated immediately. The interrupt signals will be in the microprocessors of the connected bus subscribers (peripheral Control devices), if just a data packet according to the specified in its header priority Has access to the data bus. about a receive address of the data packet receive the microprocessors the peripheral units information, whether the respective data packet for her is relevant. While of an interrupt, the microprocessors interrupt their running Tasks. At an accumulation of rapidly consecutive data packets, this may be due to the limited microprocessor performance to an overload, with the risk of data loss. More powerful Microprocessors as an alternative are relatively expensive. Special address filters for interrupt reduction are also expensive and rather inadequate.

The known data transmission system acts however, a microprocessor overload by too fast consecutive interrupts thereby, that between a transmitted data packet and a time delay is introduced to a data packet to be transmitted.

These measure In particular, on slow buses to a limited extent the Reduce risk of data loss. Disadvantageous effect, that this transmission mechanism is more likely is too inflexible and insufficient to the increasing system complexity and amount of data to manage something. Rather, in particular, with regard to developments in the field AUTOSAR a standardized solution desirable.

task The present invention is therefore a data transmission system to create that more flexible, especially with regard to applications with standardized data buses and data bus users is, and with a relatively low cost, larger amounts of data and more complex data flows can handle.

These The object is in connection with the preamble of claim 1 solved by that the data transmission means in a master-client system architecture are structured, providing a flexible bidirectional data transmission between at least one master control unit and at least one allows the master control unit associated client control unit.

preferred embodiments The invention are described in the subclaims.

The invention is based on the recognition that a fundamental restructuring of all control and regulation processes can be realized by bidirectional communication in a network, which can be adapted to existing bus systems, such as CAN or LIN buses, which implement standardized peripheral units in a relatively simple manner can and which is easily expandable. This is essentially achieved by a software solution based on the master-client principle with a flexible bidirectional transmission protocol. The master-client system architecture reduces the bus load and reduces or prevents data bursts. In addition, this architecture offers a number of other advantages over conventional transmission systems in vehicles that operate with a quasi-static, unidirectional transmission protocol. It provides physical interfaces, such as power generator interfaces, energy storage interfaces, power consumer interfaces, and power function interfaces that can be defined in interface standards. The system is independent of the type of data bus used. The data can be centrally managed in a database and processed in tool chains. The architecture can be flexibly configured for different requirements, ie series, expansions, equipment, customer behavior, etc. and is easily verifiable. In particular, the inventive system architecture can be represented in an AUTOSAR concept.

Especially advantageous is the data transmission system, as in a preferred embodiment provided for the invention, for the transfer from energy data to the electrical energy on-board network with a so-called Energy flow interface (EFI) suitable. Basically, the data transmission system according to the invention but also to other comparable requirements, for example the transfer of heat data to a thermal management system transferable in motor vehicles.

The Data transmission means include in particular data bus, interfaces and peripheral units, i.e. ECUs for the individual functions, with microprocessor and controller. These components are integrated in the master client system architecture. It is the master is configured as a central microprocessor, with a Operating system, a data store and a software that communicates with the assigned and appropriately configured clients and distributes the work instructions. As a central data store and Data administrators may have a database available. The communication between master and client is running bidirectionally. This is for defines a record for each client. The records are in the master control unit and the respective client control unit stored in mirror image. In the dataset is written the respective setpoints (default values). After a release of the data bus access, the master sends setpoint data / work instructions to the client, receives feedback and possibly a release for a data override. In the event of a bus failure, the system switches to a default state (default) a new data transfer requesting. Therefore It is advantageous, if necessary, an instruction for data renewal on the Master control unit provided. In addition, it makes sense in the data sets measures for emergency running in the case of transmission disturbances. The setpoints of the clients can for example, at the same time its respective emergency behavior in the case of disorders describe. Each record can have a send / receive filter (record filter) be assigned. Thereby can in a simple way transmission criteria for distinguishing and fixing fast event data, slow Cycle data, necessary data and urgent data specified which, as a consequence, causes a further reduction of the bus load. In particular, safety-relevant functions are treated with a priority and unnecessary Data filtered out. The master control unit can display a message for Presentation and / or recording of a data transfer action to be carried out in each case which allows control of the data communication.

Further Details of the invention will become apparent from the following detailed Description and attached Drawings in which preferred embodiments of the invention are exemplified.

In show the drawings:

1 FIG. 1 is a block diagram of a master client system architecture for an energy flow interface (EFI) of a motor vehicle. FIG.

2 : a data flow schema between a master and a client,

3 : a block diagram of a software structure of master and client,

4 : a representation of master and client records,

5 : a flow chart for data transfer master client, and

6 : a flow chart for data transfer client-master.

The 1 shows a data transmission system for an energy flow interface (EFI) 15 for transmitting energy data to an electric power on-board network (not shown) of a motor vehicle, for example a hybrid vehicle, in a master-client system architecture 1 is structured. The system architecture 1 has a master control unit designed as an Advanced Electrical Power Management Master, AEP Master for short 2 and a number of client control units 3 . 5 . 7 . 9 . 11 , Clients for short. The client 3 includes power generator control units for regulating and detecting the state of electrical power generation in the vehicle. He is an energy producer control 4 in the AEP master 2 assigned. The client 5 includes consumer control units for regulation 13 , State detection 14 , Stand function logon and shutdown, function shutdown and power shutdown. He is a consumer controller 6 in the AEP master 2 assigned. The client 7 includes an energy management controller for the voltage recovery gel, terminal diagnosis and control and a quiescent current diagnosis. He is an energy manager 8th in the AEP master 2 assigned. The client 9 comprises a converter control unit for controlling and detecting the state of a DC-DC converter in the two-voltage electrical system of the hybrid vehicle. He is a converter controller 10 in the AEP master 2 assigned. The client 11 Finally, a memory controller includes an energy storage for quiescent current detection. It is a memory state detection 12 in the AEP master 2 assigned.

• 1) Konsistenzkriterium: Master 2 und der jeweilige Client 3, 5, 7, 9, 11 haben den gleichen Datensatz DS1_M, ..., DS5_M, bzw. DS1_C, ..., DS5_C.
• 2) Default-Werte: Der Client 3, 5, 7, 9, 11 schreibt beim Systemhochlauf seinen Datensatz DS1_C, ..., DS5_C.
• 3) Default-Werte: Der Master 2 schreibt beim Systemhochlauf seinen Datensatz DS1_M, ..., DS5_M.
• 4) Default-Werte: Die Default-Werte im Client 3, 5, 7, 9, 11 beschreiben zugleich sein Notlaufverhalten.
• 5) Datenübertragung: Der Master 2 erhält die Default-Werte des Client 3, 5, 7, 9, 11 (Erstabholung, Zyklus/Ereignis, Monitoring).
• 6) Datenüberschreibung: Der Master 2 überschreibt bei Vorgabe einzelne, erlaubte Client-Daten.
• 7) Datenfilter: Der Client 3, 5, 7, 9, 11 weist einen Sende-/Empfangsfilter SE1_C, ..., SE5_C auf.
• 8) Datenfilter: Der Master 2 weist einen Sende-/Empfangsfilter SE1_M, ..., SE5_M auf.
• 9) Anzeige: Eine durchzuführende Master-Aktion (reset, overwrite, etc.) muss angezeigt sein.
• 10) Refresh: Der Master 2 muss einen Refresh (Datenerneuerung) abgeben (ein Busausfall führt zu einem Default-Zustand).
• 11) Datennotwendigkeit: Es werden nur notwendige Daten übertragen (Buslastreduzierung durch Auswahlkriterien).
• 12) Datenart: Es gibt schnelle Daten (Ereignisdaten) und langsame Daten (zyklische Daten).

For communication between the AEP master 2 and the clients 3 . 5 . 7 . 9 . 11 a set of design rules are set:

• 1) Consistency criterion: Master 2 and the respective client 3 . 5 . 7 . 9 . 11 have the same data record DS1_M, ..., DS5_M, or DS1_C, ..., DS5_C.
• 2) Default values: The client 3 . 5 . 7 . 9 . 11 writes system record its record DS1_C, ..., DS5_C.
• 3) Default values: The master 2 writes system record its record DS1_M, ..., DS5_M.
• 4) Default values: The default values in the client 3 . 5 . 7 . 9 . 11 describe at the same time his emergency behavior.
• 5) Data transfer: The master 2 gets the default values of the client 3 . 5 . 7 . 9 . 11 (First pickup, cycle / event, monitoring).
• 6) Data Override: The Master 2 overrides individual, permitted client data.
• 7) Data Filter: The client 3 . 5 . 7 . 9 . 11 has a transmit / receive filter SE1_C, ..., SE5_C.
• 8) Data Filter: The Master 2 has a transmit / receive filter SE1_M, ..., SE5_M.
• 9) Display: A master action to be performed (reset, overwrite, etc.) must be displayed.
• 10) Refresh: The master 2 must give a refresh (data refresh) (a bus failure leads to a default state).
• 11) Data necessity: Only necessary data are transferred (bus load reduction by selection criteria).
• 12) Data Type: There are fast data (event data) and slow data (cyclic data).

• a) Anmeldung des Client 5 beim Master 2
• b) Datensatzübertragung vom Client zum Master 2 (gleiche Datensätze DS2-M, bzw. DS2_C)
• c) Zyklus (langsam) vom Client 5 zum Master 2
• d) Ereignis (schnell) vom Client 5 zum Master 2
• e) Master-Solldaten (Arbeitsanweisung an den Client 5)
• f) Datenübertragung/Refresh (Antwort vom Client 5 an den Master 2).

The 2 shows, as an example of a timing of bidirectional data communication taking into account the design rules, a data flow scheme between the AEP master 2 and the consumer client 5 , master 2 and client 5 each have a COM interface 16 (standardized serial interface) for data transmission via a (not shown) CAN data bus on. The communication between master 2 and client 5 is in the EFI 15 described on both sides. On the master page will be the powermanager 8th and the consumer control 6 , on the consumer side, consumer regulation 13 and the consumer state detection 14 activated. The communication takes place sequentially in a few milliseconds in five steps:

• a) Registration of the client 5 at the master 2
• b) Data record transfer from the client to the master 2 (same data records DS2-M or DS2_C)
• c) Cycle (slow) from the client 5 to the master 2
• d) Event (fast) from the client 5 to the master 2
• e) master target data (work instruction to the client 5 )
• f) Data transmission / refresh (response from the client 5 to the master 2 ).

The 3 illustrates a software structure from the master 2 and client 5 , The software is essentially divided into three blocks: Master 2 and client 5 each have their data sets DS2_M, or DS2_C and their transmit / receive filters SE2_M, or SE2_C. Furthermore, a so-called "instruction look up table" IL_M or IL_C is provided, which is a table structured identically for each data record, in which a clear assignment between command, data content, data position (address) and data length is stored.

• – Soll-Leistung
• – Soll-Spannung
• – Minimal-Leistung
• – Maximal-Leistung
• – Minimal-Spannung
• – Maximal-Spannung
• – Ist-Leistung
• – Wunsch-Leistung
• – Ist-Spannung
• – Genauigkeit Ist-Spannung
• – Priorität Energie elektrisch
• – Peak-Leistung
• – Peak-Energie
• – ...

The 4 shows for clarity the data sets DS1_M, DS2_M, DS3_M, DS4_M, DS5_M, or DS1_C, DS2_C, DS3_C, DS4_C, DS5_C of Master 2 and client 3 . 5 . 7 . 9 . 11 , Further data sets, eg for unrecognized consumers, are possible. For example, a typical record might include:

• - Target power
• - Target voltage
• - Minimal performance
• - maximum performance
• - minimum voltage
• - maximum voltage
• - Actual performance
• - Desired performance
• - actual voltage
• - Accuracy actual voltage
• - Priority energy electric
• - Peak power
• - Peak energy
• - ...

It makes sense to agree on a sign definition that states that a power, in which energy flows into the electrical system (generator, storage, converter) receives a negative sign and a power in which energy is taken from the electrical system (consumer, memory, converter) receives a positive sign.

In the 5 and 6 is a flow chart for communication from the master 2 to a client 3 . 5 . 7 . 9 . 11 ( 5 ) and from the client 3 . 5 . 7 . 9 . 11 to the master 2 ( 6 ). A data transfer from the master 2 to the client 3 . 5 . 7 . 9 . 11 starts with the startup (wake up) of the master 2 in block 17 , The master 2 writes the default values (setpoints) to the corresponding data records DS1_M ..., DS5_M and sets the associated data filters SE1_M, ..., SE5_M (block 18 , Block 19 ). In block 20 the record DS1_M ..., DS5_M becomes the client 3 . 5 . 7 . 9 . 11 sent, or overwritten by default. This is in the right half of the diagram 5 shown in detail. First, in block 20a , respectively. 20b Checked whether it is event data or cycle data, or whether a cycle has expired. In block 20c the authorization for data transfer is checked. If the check is positive, the data record DS1_M ..., DS5_M is sent (block 20d ) and, if necessary, the cycle is reset (block 20e ). If the data has been transferred / overwritten, or if the cycle has ended and been processed (block 20f ), goes the master 2 into a state of rest (block 22 ), if previously a sleeping condition (block 21 ), otherwise other pending records DS1_M ..., DS5_M will be transferred.

A data transfer, for example from the client 5 to the master 2 works the same way ( 6 ). After the start (block 17 ' ) writes the client 5 his record DS2_C (block 18 ' ), sets its record filter SE2_C (block 19 ' ). Then the client sends 5 his data to the master 2 (Block 20 ' ) according to the test scheme in the right half of 6 , If there is an event (block 20a ' ), after release (block 20c ' ) sent the data (block 20d ' ). In the case of cyclic data, the cycle is repeated accordingly and after expiration (block 20b ' ) and broadcast (block 20d ' ) of the data set DS2_C (block 20e ' ). Then the record transfer is completed (block 20f ' ) and the client 5 goes with set sleeping condition ( 21 ' ), or otherwise sets data transfer to the master 2 continued.

1

Master-client system architecture

2

AEP-Master

3

client Power generator control units

4

Power generator control

5

client Load control devices

6

Consumer Control

7

client Energy Management Control

8th

energy Manager

9

client Converter control device

10

Converter control

11

client Memory controller

12

Memory status recognition

13

consumer control

14

Consumers state recognition

15

Energy Flow interface

16

COM interface

17 17 '

Flowchart block

18 18 '

Flowchart block

19 19 '

Flowchart block

20 20 '

Flowchart block

20a, 20a '

Flowchart block

20b, 20b '

Flowchart block

20c, 20c '

Flowchart block

20d, 20d '

Flowchart block

20e, 20e '

Flowchart block

20f, 20f '

Flowchart block

21 21 '

Flowchart block

22 22 '

Flowchart block

a

communication step Client Master

b

communication step Client Master

c

communication step Client Master

d

communication step Client Master

e

communication step Master client

f

communication step Client Master

DS1_M, ..., DS5_M

Records Master

DS1_C, ..., DS5_C

Records client

SE1_M, ..., SE5_M

Transmit / receive filters master

SE1_C, ..., SE5_C

Transmit / receive filters clients

IL_M

Instruction look up table Master

IL_C

Instruction look up table client

Claims (10)

Data transmission system for the control and regulation of operating processes in motor vehicles, having data transmission means for transmitting and receiving data information, characterized in that the data transmission means are in a master-client system architecture ( 1 ), which allow flexible bidirectional data transmission between at least one master control unit ( 2 ) and at least one of the master control units ( 2 ) associated client control unit ( 3 . 5 . 7 . 9 . 11 ). Data transmission system according to claim 1, characterized in that in the master-client system architecture ( 1 ) a bidirectional transmission protocol for the transmission of energy data to an electrical power system of the motor vehicle is defined. Data transmission system according to claim 1 or 2, characterized in that in the master control unit ( 2 ) and the client control units ( 3 . 5 . 7 . 9 . 11 ) are each mirror images of the same data sets (DS1_M, ..., DS5_M, DS1_C, ..., DS5_C) are stored. Data transfer system according to one of the claims 1 to 3, characterized in that in the data sets (DS1_C, ..., DS5_C) Measures for emergency running behavior in case of transmission disruptions are. Data transmission system according to one of claims 1 to 4, characterized in that from the master control unit ( 2 ), given data of the client control unit ( 3 . 5 . 7 . 9 . 11 ) are overwritable. Data transmission system according to one of Claims 1 to 5, characterized in that the master control unit ( 2 ) and / or the client control units ( 3 . 5 . 7 . 9 . 11 ) have a transmit / receive filter (SE1_M, ..., SE5_M, SE1_C, ..., SE5_C). Data transmission system according to one of Claims 1 to 6, characterized in that the master control unit ( 2 ) has a display for displaying and / or detecting a data transfer action to be performed in each case. Data transmission system according to one of claims 1 to 7, characterized in that via the master control unit ( 2 ) If necessary, a data renewal is feasible. Data transfer system according to one of the claims 1 to 8, characterized in that transmission criteria for distinguishing and definition of fast event data, slow cycle data, necessary data and urgent data are given. Data transmission system according to one of Claims 1 to 9, characterized in that in the master-client system architecture ( 1 ) a bidirectional transmission protocol for the transmission of heat data to a thermal management system of the motor vehicle is defined.