Classifications

• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
  • B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
  • B60W30/02—Control of vehicle driving stability
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
  • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
  • B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
  • B60W50/029—Adapting to failures or work around with other constraints, e.g. circumvention by avoiding use of failed parts
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
  • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
  • B60W2050/0001—Details of the control system
  • B60W2050/0002—Automatic control, details of type of controller or control system architecture
  • B60W2050/0016—State machine analysis
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
  • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
  • B60W2050/0062—Adapting control system settings
  • B60W2050/0075—Automatic parameter input, automatic initialising or calibrating means
  • B60W2050/009—Priority selection

Definitions

• the invention relates to a method for determining a target state according to the preamble of claim 1, a corresponding device according to the preamble of claim 12, a computer program and a computer program product.
• DE 102 23 368 A1 describes a method with which system states of a control unit can be determined from read environmental conditions.
• ESP Electronic Stability Programs
• the term hardware component in this context sensors, actuators, data transfer controllers and ECU components of all kinds are summarized.
• the data transfer controllers may be, for example, CAN or Flex-Ray.
• the ECU components include, for example, ROM, RAM, EEPROM or A / D converter. All mentioned hardware components and the signals transmitted or supplied by the hardware components are monitored during their operation to detect any failures.
• a current state of a component or signal is referred to as status. Possible states are for example "valid", “temporarily invalid”, “not initialised” and “invalid". Under the status "not initialized” several stages are possible.
• system states which can be taken in the event of a fault.
• a system state is the combination of the states of all components present in the system. The components are, for example, regulators, model calculations, monitoring or signal conditioning.
• the driver e.g. With the so-called passive push-button “Pata” or “ESP-off", you can selectively deactivate individual parts of the ESP functional scope.
• This driver request can generally be called a "trigger.”
• the trigger is treated with separate algorithms as opposed to errors.
• a manufacturer of the system or a manufacturer of a higher-level system can make further specifications.
• the car manufacturer can program the ESP control unit in such a way that certain functions are deactivated because the end customer has not separately ordered and paid for them. Also these wishes of the manufacturer can be classified in the category "Trigger".
• Trigger the destination status is determined distributed in the ESP. This distribution of tasks and responsibilities makes the product configuration of the ESP and the processing of customer projects difficult.
• the use of tools for the automated generation of documentation in the three areas mentioned is not possible.
• the present invention provides a method for determining a target state in a multi-component system, wherein system states of different priorities are selectable in the system, depending on availability of the components. According to the method of the invention, it is determined whether a system state of highest priority can be selected. If the highest priority system state is selectable, the system state of highest priority is determined as the destination state. If the highest priority system state is not selectable, then a determination is made as to whether a system state of next highest priority is selectable and determining the system state of next highest priority as the destination state if the system state of next highest priority is selectable.
• the present invention further provides an apparatus for determining a target condition in a multi-component system that performs all steps of the method of the invention. - A -
• the computer program with program code means according to the invention is designed to perform all the steps of the method according to the invention when this computer program is carried out on a computer or a corresponding computing unit, in particular a device according to the invention.
• the computer program product according to the invention with program code means which are stored on a computer-readable data carrier is provided for carrying out the method according to the invention if this computer program is carried out on a computer or a corresponding arithmetic unit, in particular a device according to the invention.
• An essential aspect of the invention is a so-called release manager, also called system release manager, in which all available system levels are defined. In addition, for each system level, those signals are listed that are required for the operation of the respective level.
• Influencing factors include, for example, errors and specifications. Errors include, for example, errors in the system's own sensors or actuators as well as errors in sensors or actuators of third-party systems. Specifications include, for example, specifications made by the driver or the manufacturer. Defaults or triggers made by the driver naturally occur during operation of the system. Specifications made by the manufacturer may occur during production or during repair in garages. These too represent triggers to perform a system configuration. All these requirements must be evaluated in such a way that safe operation with the highest possible system availability is ensured at all times.
• the invention offers a number of implementation-independent advantages. This includes, for example, that defined system levels can only be assumed in a so-called inhibit handler. Other than the defined system levels are not possible. Furthermore, all system levels and the conditions under which the levels can be taken can be defined centrally. This greatly increases the clarity of the system. Dependencies that are stored in the System Release Manager are strongly project-dependent. The central definition of these dependencies greatly reduces the effort involved in project initiation and during the course of the project.
• the invention also offers a number of implementation-relevant advantages. For example, very efficient algorithms are used, with which errors and triggers can be further processed. This consumes less of the very limited resources of ROM, RAM and runtime or cycle time in a controller.
• a lower or lowest priority system state is determined to be the destination state if the next higher priority system state is not selectable.
• the target state with the best possible priority can easily be selected or set at any time in a simple manner, whereby a gradual check of the system states in the order of their priorities (with decreasing priority) can be carried out.
• the steps of the determination be made based on a central allocation table, the central allocation table being for each System state defines which of the components must be available for the system state to be selectable.
• this measure enables a central definition, review, readjustment and retrievability of all possible system states.
• the steps of determining include a step of analyzing whether the components required according to the central allocation table for the respective system state are available.
• the different priorities correspond to different availability of the system, whereby advantageously the highest priority system state corresponds to a maximum availability of the system.
• a selectability of the highest priority system state a first set of available components, and for a next higher priority system state selectability, a second set of available components be required, where the second set may be a subset of the first set. This measure allows an optimal tuning or grading of the respective states to each other.
• the target state of the system in response to a change in availability of one of the components, is retrieved based on the highest priority system state. This ensures that an optimal system setting is possible at any time.
• a change in availability of one of the components may be due to a malfunction of the components, an intervention of an operator of the system and / or a specification of a manufacturer of the system.
• This allows the inventive method an adaptation of the system to the most likely disorders or changes to be considered.
• FIG. 1 shows a flowchart of a method according to a preferred embodiment of the present invention
• Fig. 2 is a block diagram of an apparatus according to another preferred embodiment of the present invention.
• Fig. 3 shows an allocation table according to another preferred embodiment of the present invention.
• FIG. 1 is a flow chart illustrating a method for determining a target state in a multi-component system according to a preferred embodiment Embodiment of the present invention. Depending on the availability of the components, system states of different priorities can be selected in the system.
• a system state of highest priority it is determined whether a system state of highest priority can be selected.
• the highest priority system state is selectable when all the components of the system required to select that system state are available. If the highest priority system state is selectable, i. H. all required components are available, then in a method step 104 the system state of highest priority is determined as destination state. In this case, the method can be terminated without carrying out further method steps.
• the highest priority system state is not selectable, i. H. If not all required components are available, then it is determined in a method step 112 whether a system state of the next higher priority can be selected.
• the next highest priority system state is selectable if all the components of the system required to select that system state are available. Typically, fewer or different components are required for the next highest priority system state than for the higher priority system state. For example, the next highest priority system state may require a subset of the components required for the higher priority system state. If the next higher priority system state is selectable, i. H. if all the components required for this system state are available, in a method step 114 the system state of the next higher priority is determined as destination state. In this case, the procedure can be ended.
• system state of the next highest priority can not be selected, then in further method steps (not shown in the figures) further system states with respectively lower priorities can be checked for their selectability. It is checked in terms of priorities, in descending order, whether a system state is selectable. If a system state can be selected, this system state is selected as the destination state. Otherwise, it is determined whether the system state with the next lower priority can be selected. The procedure is continued until a selectable system state has been determined and determined as the destination state. If no system state of higher priority can be selected, that is to say the system state of the next higher priority can not be selected with reference to FIG. 1, then in a further method step 124 a system state of lowest priority can be determined as the destination state. For example, the lowest priority system state may be determined as a target state whenever insufficient components are available to select a higher priority system state.
• the method steps 102, 104, 112, 114, 124 can be carried out centrally in the system.
• a central allocation table (shown in FIG. 3) can be used for this purpose, in which it is defined for each system state which of the components must be available in order for the respective system state to be selectable. Using the central allocation table, it is possible to analyze whether the components required according to the central allocation table for the respective system state are available.
• the different priorities of the system states may correspond to different availabilities of the system, with the highest priority system state corresponding to the highest availability of the system.
• a change in the availability of a component can be done, for example, by a malfunction of the component, an intervention of an operator of the system or a specification of a manufacturer of the system.
• a subsequently required determination of a new target state can be carried out by carrying out the method according to the invention again. Referring to FIG. 1, this means that starting from the first method step 102, a new destination state is determined.
• FIG. 2 is a block diagram illustrating a device 200 for determining a target state in a multi-component system.
• FIG. 2 shows a system having a first component 230 whose availability in the system can be displayed by means of a first availability signal 235, a second component 240 whose availability can be displayed by means of a second availability signal 245, and a third component 250 whose availability by means of a second component third availability signal 255 can be displayed shown.
• the device 200 may be implemented as a unit, not distributed, in the system.
• the device 200 is configured to receive the availability signals 235, 245, 255.
• the device 200 may include an allocation table 262.
• the allocation table 262 all possible system states are defined. Further, in the mapping table 262, for each system state, it is defined which of the components 230, 240, 250 must be available for the particular system state to be selectable. For example, all components 230, 240, 250 may be required to select the highest priority system state.
• the device 200 is designed to determine, using the allocation table 262 and by evaluating the availability signals 235, 245, 255, which system state defined in the allocation table 262 can be selected. Furthermore, the device 200 is designed to determine the system state as target state, which, on the basis of the available components, can be selected and additionally has the highest priority of all selectable system states.
• the device 200 has means for displaying the target state in the form of a target state signal 265.
• the components 230, 240, 250 can be sensors, actuators, data transfer controllers, control unit components or signals that can be transmitted by such components.
• the system may be a dynamic system such as a mechatronically embedded system.
• the device 200 or the allocation table 262 can be implemented in the form of a system release manager, which defines all system levels.
• the System Release Manager determines, at system level, the signals required to operate this level.
• FIG. 3 shows a table, which may be the allocation table 262 described in FIG.
• the table has three columns and five rows. The last column is divided into three subcolumns. In the first column, beginning with field 301, the possible system states are defined. In the second column, which begins with field 302, the signals, components and triggers required for the respective system state are defined. These are collectively referred to as "guards".
• the third column beginning with field 303, defines states of the components of the system that depend on the signals, components, and triggers defined in the second column. Such dependent components may be an ABS system listed in the first subcolumn 304, an ASR system listed in the second subcolumn 305, or an ESP system listed in the third subcolumn 306.
• the second line beginning with field 307, describes a "system state 3" for which, according to field 308, the components “yaw rate”, “motor interface”, “4 speed sensors” and “! Pata” must be available Field 309, the component ABS in the “on” state, according to field 310, the component ASR in the “on” state and according to field 311, the component ESP in the "on” state.
• the third line describes a "System State 2" for which the "Motor Interface” and “4 Speed Sensors” components must be available according to Field 313 so that according to Field 314 the ABS component is in the "backup” state, According to field 315, the component ASR is in the state “backup” and according to field 316 the component ESP is in the state "off”.
• the fourth line beginning with field 317, describes a "System State 1" for which the "4 Speed Sensors” component must be available in accordance with block 318, so that according to block 319, the ABS component is in the "backup” state, according to field 320 Component ASR in the state “off” and according to field 321, the component ESP in the state "off”.
• the fifth row starting with field 322 describes a "System State 0" for which no component needs to be available according to field 323.
• the ABS component is in the "off” state, according to box 325 is the component ASR in the "off” state and according to field 326, the ESP component is in the "off” state.
• system states 307, 312, 317, 322 there are four system states 307, 312, 317, 322 stored according to their respective priorities in the table shown in FIG.
• the priorities correspond to a system availability.
• the system states 307, 312, 317, 322 are sorted in descending order in the table.
• this table is traversed from top to bottom and the required signals 308, 313, 318, 323 analyzed. If all parts of the corresponding guards are available or fulfilled in a strategy, this is the new target strategy and the search is aborted.
• the guards 302 include signals, for example the yaw rate, as well as triggers, for example Pata, as well as the availability of actuators, for example hydraulic valves. This shows that the Inhibit Handler makes no difference between these Guard elements. This greatly simplifies the inhibit handler because a solution algorithm can be used for all types.
• the invention can be implemented in software.
• the method according to the invention is a new concept for the management of system states of dynamic systems. This method involves the determination of the operating state, which is allowed and desired under the given boundary conditions and also has the highest system availability.
• the inventive approach is not limited to the vehicle dynamics control ESP. Rather, the use in all mechatronic embedded systems is conceivable. Such systems are in addition to the ESP, for example, the products ABS and ASR.
• the described embodiments from the field of application of the ESP are merely illustrative, but in no way limit the field of application of the invention.

Landscapes

• Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Transportation (AREA)
• Mechanical Engineering (AREA)
• Human Computer Interaction (AREA)
• Stored Programmes (AREA)
• Hardware Redundancy (AREA)
• Feedback Control In General (AREA)
• Testing And Monitoring For Control Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=38996501

Family Applications (1)

Country Status (5)

Family Cites Families (10)

• 2006
  • 2006-10-05 DE DE102006047141A patent/DE102006047141A1/de not_active Withdrawn
• 2007
  • 2007-09-20 JP JP2009530837A patent/JP2010506278A/ja not_active Ceased
  • 2007-09-20 EP EP07820420A patent/EP2079624A1/de not_active Withdrawn
  • 2007-09-20 US US12/308,202 patent/US20100037229A1/en not_active Abandoned
  • 2007-09-20 WO PCT/EP2007/059985 patent/WO2008040645A1/de active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events