EP2005297A2 - Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique - Google Patents

Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique

Info

Publication number
EP2005297A2
EP2005297A2 EP07727136A EP07727136A EP2005297A2 EP 2005297 A2 EP2005297 A2 EP 2005297A2 EP 07727136 A EP07727136 A EP 07727136A EP 07727136 A EP07727136 A EP 07727136A EP 2005297 A2 EP2005297 A2 EP 2005297A2
Authority
EP
European Patent Office
Prior art keywords
eve
event
fct
ent
vehicle function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP07727136A
Other languages
German (de)
English (en)
Inventor
Carl-Eike Hofmeister
Michael KÄSBAUER
Ulrich Voll
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Continental Automotive GmbH
Original Assignee
Continental Automotive GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Continental Automotive GmbH filed Critical Continental Automotive GmbH
Publication of EP2005297A2 publication Critical patent/EP2005297A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • 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/0004—In digital systems, e.g. discrete-time systems involving sampling
    • 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/0043—Signal treatments, identification of variables or parameters, parameter estimation or state estimation
    • B60W2050/0044—In digital systems
    • 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
    • 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
    • B60W2050/0094—Priority selection of control units
    • 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
    • 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/0205—Diagnosing or detecting failures; Failure detection models
    • 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/035—Bringing the control units into a predefined state, e.g. giving priority to particular actuators
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/543—Local

Definitions

  • the invention relates to a method and a device for operating a motor vehicle, in which upon occurrence of at least one predetermined event of the motor vehicle at least one of the given event associated Fahr ⁇ zeugfunktion is determined. The determined vehicle function is started or inhibited. Furthermore, the invention relates to a method and a device for accessing an assignment rule of a control device of the motor vehicle. Further, the invention relates to a domestic product Computerprogrammpro ⁇ comprising a computer readable medium having program instructions.
  • programmable control devices in the automotive sector suitably assigned vehicle functions, for example emergency running reactions, diagnostic strategies and / or substitute value calculations, are activated or deactivated within the scope of the legally prescribed diagnostic processes depending on predefined events, for example fault events.
  • vehicle functions to the predefined events ordinances are integrated as part of an assignment rule in software and chert in the control devices vomit ⁇ .
  • the software is regularly supplied by the manufacturers of the control devices to car manufacturers who install the control devices in their vehicles.
  • the invention is characterized in terms of a first aspect of the invention by a method and an apparatus for operating a motor vehicle.
  • a predetermined event of the motor vehicle Upon the occurrence of at least one predetermined event of the motor vehicle is detected, an event of an event list entry that is associated with the pre- ⁇ given event, depending on the pre-NEN give ⁇ event.
  • a first adjacency list is determined, which is assigned to the determined event entry, depending on the determined event entry.
  • the first Adjazenzliste comprises at least one Adjazenzlisteneintrag.
  • Adja- to each of the first adjacency zenzlisteneintrag is a vehicle ⁇ function entry determined.
  • the vehicle function entry is assigned to the corresponding adjacency list entry and the predefined vehicle function.
  • the predetermined vehicle function is determined depending on the vehicle function entry. The determined vehicle function is started or inhibited.
  • accessing means reading and / or writing the allocation from or to the storage device. Furthermore, this makes it possible to easily change the assignment of the vehicle function to the given event. It also makes it easy to detect when the vehicle function has to be started or stopped.
  • an event quantity entry is determined, which is assigned to a predetermined event quantity.
  • the predetermined event set includes the predetermined event and at least one further predetermined event.
  • the event set is assigned to the entry Adjazenzlisteneintrag and telt ermit depending on the Adjazenzlisteneintrag the first adjacency ⁇ .
  • a second adjacency list is determined depending on the determined event quantity entry.
  • the second Adja ⁇ zenzliste is the determined event set entry zugeord ⁇ net and at least one second Adjazenzlisteneintrag the adjacency list.
  • the vehicle function entry is averaged, which is assigned to the corresponding adjacency list entry of the second adjacence list and the corresponding vehicle function. This simply allows the corresponding vehicle function to be assigned to the event set.
  • the first adjacency list and a third adjacency is determined which is assigned to the detected event ⁇ entry, depending on the detected event- - -
  • the third adjacency list includes at least one adjacency list entry. For each adjacency list entry of the first adjacency list and for each adjacency list entry of the third adjacency list, a respective vehicle function entry is determined, which is assigned to the corresponding adjacency list entry.
  • the first Adjazenzliste is changeable and the third Adjazenzliste is unchangeable. This simply makes it possible to temporarily change the assignment of the event to the vehicle function and / or to quickly switch between a changed assignment and an unchanged assignment.
  • an event counter is assigned to each determined vehicle function entry , which is assigned to the vehicle ⁇ function entry and which is representative of a number of predetermined events that are assigned to the determined function entry and have already occurred.
  • the corresponding vehicle function is started or inhibited if the number is greater than zero. This simply makes it possible to detect whether the corresponding vehicle function should be started or inhibited.
  • a state value is adapted if the corresponding event counter is greater than zero.
  • the Zu ⁇ value is assigned to the respective vehicle function and the corresponding event counter.
  • the respective vehicle function is started or inhibited depending on the state value. This makes it particularly easy and fast to detect whether the corresponding vehicle function should be started or inhibited.
  • the predetermined event is classified as having occurred only if the occurred predetermined event meets at least one predetermined condition. This makes it possible to evaluate the occurred event and to classify it as a given event only under the given condition, depending on which the vehicle function is to be started or inhibited.
  • the predetermined event is classified as having occurred only when the occurred predetermined event has occurred for a predetermined first period of time. This helps to classify the event very precisely.
  • the predetermined event only then classified to have occurred if the predetermined He ⁇ eignis has occurred with a predetermined frequency. This helps sify the event very accurately classified ⁇ .
  • the number of occurred predetermined events that can count the event counter limited by a maximum number of predetermined events occurred.
  • An auxiliary event counter is started when the number of occurred preset events for the corresponding vehicle function is greater than the maximum number of occurred preset events. This can contribute to a low memory requirement.
  • the first aspect of the invention is checked at a start of a control device of the motor vehicle for a predetermined amount of pre ⁇ given events, which predetermined event has actually occurred.
  • the vehicle function assigned to the currently occurring event is determined.
  • the event counter is adjusted accordingly, which is assigned to the vehicle function. This allows without delay ⁇ Lich after the start of the motor vehicle at any vehicle function display all event count the right number of events that have occurred.
  • the vehicle function via the first and / or second adjacency list is assigned to the specified differently surrounded event properly.
  • the assignment is checked by for the predetermined event, the current has occurred, checks whether the number of turned kick ⁇ NEN preselected events that are associated with the vehicle function and counted by the corresponding event counter is greater than zero.
  • it can be checked whether the number of occurred preset events to which the vehicle function is assigned and which has been counted by the corresponding event counter is zero or greater than zero.
  • the corresponding event counter can be reduced by one unit per given predefined event. Thereafter, it is checked whether the number of occurred ⁇ NEN predetermined events after the reduction is zero.
  • Event counter was counted, the actual number of occurred default events corresponds. This allowed ⁇ light to check with simple means, whether the adjacency list have been adjusted correctly.
  • the control device is restarted if the vehicle function is incorrectly assigned to the predetermined event via the first and / or the second adjacency list.
  • Misassigning in this context means that the verification of the number of occurred predefined events to which the vehicle function has been assigned and which has been counted by the corresponding event counter has failed. This simply enables the correct assignment of the vehicle function via the first and / or the second adjacence list to the predefined event, if only an error has occurred during the determination of the assignment and / or the event counter has incorrectly recorded the number of predefined events that have occurred.
  • the error of the control device is classified as a given predetermined event if the vehicle function is incorrectly assigned to the predetermined event via the first and / or the second adjacency list. This simply makes it possible to detect that the control device is not working properly.
  • the invention in a second aspect of the invention, is characterized by a method and apparatus for accessing the assignment rule of the control device of the motor vehicle.
  • the correlation least includes min ⁇ the assignment. Due to the assignment, the mini- least a first adjacency list, the direction on the Speichervor ⁇ the control device is stored at least allocated at least one vehicle function of the motor vehicle to a predetermined event of the motor vehicle.
  • a read access to the assignment rule a read access function is started. The read access function determines via the first adjacency list, the assignment of the riding ⁇ generating function to the predetermined event.
  • a write access to the assignment rule it is checked whether the assignment of the vehicle function to be written exists for the given event. If the assignment of the vehicle function to the given event does not exist, a write access function is started that adjusts the first adjacency list, depending on the assignment to be written. This makes it possible to access the assignment during operation of the motor vehicle.
  • a condition parameter is determined which is assigned to a predetermined condition.
  • the predetermined condition is associated with the given event and the vehicle function associated with the given event such that the associated vehicle function is started or inhibited only when the predetermined event satisfies the condition.
  • the condition parameter is assigned to the assignment of the vehicle function to the predetermined event.
  • the allocation rule of Be ⁇ is assigned to the corresponding dingungsparameter to be written assignment of the vehicle function to the predetermined event. This allows easy to evaluate the occurrence of pre-admit ⁇ nen event with the condition and start the vehicle function depending on the rating or inhibit.
  • a length of the first and / or second Adjazenzliste and / or a number of adjacency lists are given in the write access. This can help to save storage space and runtime.
  • the allocations of a plurality of vehicle functions are each adapted to at least one of the predetermined events with a write access. Furthermore, the address lists are adapted with one write access. This contributes to a processor of the tax advantage ⁇ direction is not unnecessarily burdened when adjusting the multiple assignments.
  • the determined assignment of the vehicle function to the given event by the read access function is written as an array on the storage device. Then the array is read with the assignment of the vehicle function to the given event.
  • the write access to the assignment rule to be written assignment of Fahr ⁇ zeugfunktion is written to the predetermined event as an array on the storage device. Then it is checked whether the assignment to be written exists depending on the array. The write function is started, the first Adja ⁇ zenzliste adapts depending on the array if the assignment of the vehicle function does not exist for the given event. This makes it particularly easy to access the assignment rule.
  • the assignment of a plurality of vehicle functions to the predetermined event is written onto a plurality of arrays on the storage device. This may be possible if the configuration program can only read arrays of a predetermined size, a very extensive planning Alloc ⁇ well as multiple arrays represent, so that the setup program to assign read.
  • the second aspect of the invention is checked regularly after the expiry of a pre ⁇ given second time period, whether the array has been updated on the Spei ⁇ chervorraum.
  • the array is read and / or the adjacency lists are adjusted, depending on the array, when the array has been updated. This can contribute to the fact that the processor of the control device is utilized to a predetermined extent.
  • the invention is characterized, in a third aspect of the invention, by a computer program product comprising a computer readable medium having program instructions.
  • the program instructions are executable by a computer and for creating at least one adjacency depen ⁇ gig formed of a matrix. Row values of the matrix are representative of at least the predetermined event of the motor vehicle, or for at least the predetermined vehicle ⁇ function of the motor vehicle.
  • the column values of the matrix are representative of at least the predetermined vehicle function or at least the predetermined event.
  • the vehicle function is assigned to the given event.
  • This makes it possible for a configurator of the control device to make the assignment clearly and simply on the basis of the matrix and nevertheless be able to subsequently store the favorable representation of the adjacency list on the storage device of the control device.
  • This contributes to a small storage space requirement in the storage device of the control device of the motor vehicle. Furthermore, this contributes to a quick access in determining the assignment.
  • FIG. 2 shows a first list of adjacency lists
  • FIG. 3 shows a second adjacency list representation
  • FIG. 4 shows a third adjacence list representation
  • FIG. 5 a first representation of an access to an additional regulation
  • Figure 6 prescribed voltage, a second representation of the access to the Alloc,
  • FIG. 7 shows a first program for determining a vehicle function, _ -
  • FIG. 8 shows a second program for determining the vehicle function
  • FIG. 9 shows a third program for determining the vehicle function
  • FIG. 10 shows a first program for activating and / or deactivating the vehicle function
  • FIG. 11 shows a first program for determining a state value
  • FIG. 12 shows a second program for activating and / or deactivating the vehicle function
  • FIG. 13 shows a first program for checking an assignment
  • FIG. 14 shows a second program for checking the assignment
  • FIG. 15 shows a first program for reading the assignment
  • FIG. 16 shows a first program for writing the assignment
  • FIG. 17 shows a second program for reading the assignment
  • FIG. 18 shows a second program for writing the assignment.
  • a motor vehicle 2 (FIG. 1) comprises an internal combustion engine 4 and a control device 6.
  • the control device 6 can also be used as a device for operating the motor vehicle 2. _ _
  • control device 6 may be referred to as a device for accessing an assignment rule.
  • the control device 6 may comprise a plurality of control units.
  • a memory device MEM of the control device 6 preferably comprises a plurality of storage media MEM1, MEM2 (FIG. 5, FIG. 6). Furthermore, the storage device 6 comprises a working memory. In particular, if appropriate, each control unit preferably comprises the storage media MEM1, MEM2 and the main memory.
  • the control device 6 serves to start a vehicle function FCT or to inhibit DEACT when a predetermined event EVE (FIG. 7) occurs.
  • the vehicle function FCT is assigned to the predefined event EVE via an assignment rule.
  • the predetermined event may be at EVE ⁇ game as an error event of the motor vehicle 2 to be.
  • the vehicle function FCT can be, for example, an emergency response, a diagnostic strategy and / or a replacement value calculation that is started ACT or inhibited DEACT. For example, when a faulty component is detected, a warning lamp associated with the component can be switched on. Further, for example, for examining emissions of the internal combustion engine 4, an exhaust gas probe of the internal combustion engine 4 can be turned off.
  • the assignment rule comprises at least one, preferably several LINK associations.
  • the assignment LINK assigns the vehicle function FCT to the corresponding predefined event EVE.
  • the assignment LINK takes place via at least one preferably several adjacency lists AD_LIST1, AD_LIST2, AD_LIST3 (FIG. 2, FIG. 3). _
  • a first or second event entry EVE_ENT1, EVE_ENT2 of an event list EVE_LIST is determined (FIG. 2).
  • the first or second event entry EVE_ENT1, EVE_ENT2 to ⁇ preferably take a first or second event-niskennung EVE_ID1, EVE_ID2 that one of the predetermined events EVE are each uniquely associated.
  • the first and second event entry EVE_ENT1, EVE_ENT2 respectively comprise a first and a second event pointer EVE_Z1, EVE_Z2 pointing to the first and second adjacency lists AD_LIST1, AD_LIST2, respectively.
  • the event pointers EVE_Z1, EVE_Z2 point to the beginning of the first and second adjacence lists AD_LIST1, AD_LIST2, respectively.
  • the first adjacency AD_LIST1 contains any number of ⁇ At Adjazenzlisteneinträgen AD_LIST1_ENT1, AD_LIST_ENT2.
  • the first and the second adjacency lists AD_LIST1, AD_LIST2 are combined in a link list LINK_LIST.
  • the first and the second adjacence list entry AD_LIST1_ENT1, AD_LIST1_ENT2 of the first adjacency list AD_LIST1 preferably comprise the position of the corresponding adjacency list entry AD_LIST1_ENT1, AD_LIST1_ENT2 in the link list LINK_LIST and a first or second adjacency list pointer AD_LIST1_Z1, AD_LIST1_Z2.
  • the first and second adjacency list pointers AD_LIST1_Z1, AD_LIST1_Z2 point to a first or second vehicle function ⁇ entry FCT_ENT1, FCT_ENT2.
  • the first vehicle function entry FCT_ENT1 is thus assigned to the first event entry EVE_ENT1 via the first adjacency list AD_LIST1, in particular via the first adjacence list entry AD_LIST1_ENT1 of the first adjacence list AD_LIST1.
  • the vehicle function entries FCT_ENT1, FCT_ENT2 are part of a vehicle function list FCT_LIST and are preferably numbered within the vehicle function list FCT_LIST.
  • the positions of the vehicle function entries FCT_ENT1, FCT_ENT2 in the vehicle function list FCT_LIST can be predefined by vehicle function identifiers FCTID1, FCTID2, for example, which are uniquely assigned to the corresponding vehicle function FCT.
  • each vehicle entry function FCT_ENT1, FCT_ENT2 depending on an event ⁇ counter associated with the first and second numbers EVE_COUNT1, EVE_COUNT2 are counts of events occurring EVE that the corresponding vehicle function entry FCT_ENT1 are assigned FCT_ENT2 and currently occurred.
  • the first or second number EVE_COUNT1, EVE_COUNT2 of the occurred events EVE are preferably stored in the main memory of the memory device MEM.
  • the first and second event entries EVE_ENT1, EVE_ENT2 may respectively include first and second additional event pointers EVE_Z1B, EVE_Z2B (FIG. 3).
  • the first and the second additional event pointers EVE_Z1, EVE_Z2B point to the third and a fourth adjacency lists AD_LIST3, respectively.
  • the third adjacency list AD_LIST3 comprises a first and a second adjacence list entry AD_LIST3_ENT1, AD_LIST3_ENT2 of the third adjacence list AD_LIST3.
  • the third and / or fourth Adja ⁇ zenzliste AD_LIST3 may be elements of a two ⁇ th link list LINK_LIST2 example.
  • LINK_LIST is then preferably referred to as a first link list ⁇ LINK_LIST1.
  • the adjacence lists AD_LIST3 of the second link list LINK_LIST2 can be stored on the memory device MEM in such a way that they are unchangeable. This allows only ei ⁇ nen part of the assignment rule can be customized and then easily and comfortable again the original settings can be made.
  • the adjacency list entries AD_LIST3_ENT1, AD_LIST3_ENT2 of the third adjacence list AD_LIST3 are assigned on / off values ON / OFF.
  • the respective assignment can LINK via the third adjacency AD_LIST3 on or out ⁇ be switched on.
  • a bit equal to one may be set to the first adjacence list entry AD_LIST3_ENT1 of the third adjacence list AD_LIST3 if the assignment LINK of the vehicle function FCT to the predetermined event EVE via the third adjacence list AD_LIST3.
  • the first and second adjacency list entries AD_LIST3_ENT1, AD_LIST3_ENT2 of the third adjacence list AD_LIST3 comprise a first and second adjacency list pointer AD_LIST3_Z1, AD_LIST3_Z2 of the third adjacence list AD_LIST3, which respectively point to the corresponding vehicle function entries FCT_ENT1, FCT_ENT2.
  • the adjacence list entries AD_LIST1_ENT, AD_LIST1_ENT1, AD_LIST1_ENT2, AD_LIST3_ENT, AD_LIST3_ENT1, AD_LIST3_ENT2 and / or adjacence list entries AD_LIST2_ENT, AD_LIST2_ENT1, AD_LIST2_ENT2 preferably each include a mask which contains a _
  • the condition CDN is preferably predetermined by at least one condition parameter.
  • the condition CDN serves to assign the vehicle function FCT to the predefined event EVE only as an entered predefined event EVE if the condition CDN is fulfilled.
  • the predefined event EVE can only be classified as having occurred when it has occurred, for example, during a first time period DUR1 (FIG. 7) and / or when it has occurred at a predefined frequency EVE_FREQ and / or during a current drive cycle of the motor vehicle occured.
  • the condition parameter with respect to the first period DUR1 is, for example, the length of the first period DUR1.
  • a list of state values EVE_STATE is preferably assigned to the vehicle function list FCT_LIST.
  • the state values are the vehicle EVE_STATE ⁇ operations related FCT_ENT1 assigned FCT_ENT2. For example, once the number EVE_COUNT of the occurred predetermined events EVE is greater than zero NULL, the corresponding state value EVE_STATE may be set to zero NULL (FIG. 11). To check which vehicle function FCT activates ACT or deactivates DEACT, now only the corresponding additional value EVE_STATE has to be checked (FIG. 12). This is particularly advantageous when the list of state values EVE_STATE is stored in the main memory of the memory device MEM of the control unit 6. Then the access to the state values EVE_STATE can be done very quickly and thus it can also be decided very quickly which vehicle function FCT has to be started ACT or inhibited DEACT. - -
  • an event set (FIG. 4) can be specified, which comprises a plurality of the predefined events EVE.
  • the vehicle function FCT can only be activated ACT or deactivated DEACT if every predetermined event EVE of the event quantity has occurred. This can be realized, for example, by creating an event set list EVE_SUM_LIST.
  • the ⁇ ⁇ Eistenelengenliste EVE_SUM_LIST includes at least one, preferably ⁇ be ⁇ several event set entries EVE_SUM_ENT, EVE_SUM_ENT1, EVE_SUM_ENT2.
  • the first and the second event quantity entries EVE_SUM_ENT1, EVE_SUM_ENT2 each include an event quantity pointer EVE_SUM_Z1, EVE_SUM_Z2.
  • the second event quantity pointer EVE_SUM_Z2 shows the beginning of the second adjacence list AD_LIST2.
  • the right set of events entry EVE_SUM_ENT1, EVE_SUM_ENT2 said predetermined event that occurred EVE is associated, for example, be found that the corresponding Adjazenzlisten enableer AD_LIST1_Z1, AD_LIST1_Z2 the first adjacency AD_LIST1 has a value that is greater than the maximum number k of the vehicle ⁇ functional listings FCT_ENT1, FCT_ENT2 ,
  • the Adja ⁇ zenzlisten Attacher AD_LIST1_Z1, AD_LIST1_Z2 to a memory area of the memory device MEM outside of the memory area in which the vehicle function items FCT_ENT1 are stored FCT_ENT2, as the predetermined event EVE is assigned to the event set list EVE_SUM_LIST and the value of Adjazenzlisten enableers AD_LIST1_Z1, AD_LIST1_Z2 the first adjacency AD_LIST1 is reduced by the number k of the vehicle function ⁇ entries FCT_ENT1, FCT_ENT
  • EVE_SUM_ENT2 is then started the corresponding vehicle function FCT ACT or inhibited DEACT. So the predetermined event EVE about the event set which includes the predetermined EVENT ⁇ nis EVE, the vehicle function FCT is assigned.
  • a configuration program CONF_PROG is preferably used (FIG. 5).
  • the configuration program CONF_PROG adapted to read array ARR at predetermined storage areas of the storage device MEM and write to predetermined memory areas of the Spei ⁇ chervorraum MEM.
  • the Configurati ⁇ onsprogramm CONF_PROG a matrix MATRIX.
  • Array ARR in this context means that the data of the array ARR have a uniform data type and are stored on the memory device MEM such that access to the array ARR via an index is possible.
  • the matrix MATRIX has column values COLUM and row values ROW.
  • the row values ROW can be repre ⁇ sentative for the specified events EVE.
  • the column values COLUM are then assigned to the vehicle functions FCT.
  • the assignment LINK of the vehicle function FCT to the predefined event EVE can simply be marked as a cross in the corresponding field of the matrix MATRIX.
  • the condition CDN, in particular the condition Para ⁇ meter is entered in the field that the assignment LINK-represented repre ⁇ .
  • the associations LINK which are represented by the entries in the matrix MATRIX, are actually stored on the memory device MEM.
  • the configuration program CONF_PROG communicates with the control device 6 via a protocol PROT.
  • the configuration program CONF_PROG sends a corresponding event identifier EVE_ID to the control device 6 via the protocol PROT.
  • a read access function RF is preferably started.
  • the Le ⁇ sezugriffsfunktion RF serves the corresponding assignment LINK of the vehicle function FCT to the predefined event EVE based on the adjacency AD_LIST1, AD_LIST2, AD_LIST3 be determined and these so via the protocol PROT to the confi ⁇ guration CONF_PROG to send that Configurati ⁇ program CONF_PROG can read the corresponding LINK assignment.
  • the corresponding assignment LINK to be written is entered in the matrix MATRIX.
  • the assignment LINK to be written means that the assignment LINK is to be created or changed.
  • the configuration program CONF_PROG sends the corresponding assignment LINK to the control device 6 via the protocol PROT. In this case, it is first checked whether the assignment LINK of the vehicle function FCT to be written already exists EXIST for the corresponding predefined event EVE. If the assignment LINK already exists EXIST terminates access the write ⁇ . If the association LINK does not exist, a write access function WF adapts the corresponding adjacence lists AD_LIST1, AD_LIST2 according to the new assignment. _ -
  • the write access function WF and / or the read access function RF are implemented in a code that is stored on the SpeI ⁇ chervorraum MEM.
  • own codes may be stored on the memory device MEM for the write access function WF and / or the read access function RF.
  • the write access function WF and / or the read access function RF can be implemented in a code for executing the protocol PROT.
  • the ER are sent over the protocol PROT to the control device 6 eigniskennung EVE_ID ( Figure 6).
  • the control device 6 via the Adja- zenzlisten AD_LIST1, AD_LIST2, AD_LIST3 that the memory device MEM are preferably stored in the non-volatile first storage medium Meml, the appropriate vehicle ⁇ function FCT by means of the read access function RF.
  • the read RF access function for example, the assignment LINK in the form of the ARRL first array on a second storage medium ⁇ to MEM2 of the memory device MEM store.
  • the first array ARRl can now easily from the configuration program _ -
  • the Konfigurationspro may simply represent ⁇ program CONF_PROG a corresponding function identifier FCT_ID and optionally the associated condition CDN.
  • the vehicle function FCT to be assigned can be input via the corresponding vehicle function identifier FCT_ID and / or the associated condition CDN and an action ACTION to be performed in the configuration program CONF_PROG.
  • This entire assignment LINK is sent from the Configurati ⁇ onsprogramm CONF_PROG via the protocol PROT to the controller. 6 There, this association LINK is stored in the form of a second array ARR2 on the second storage medium MEM2.
  • DUR2 (FIG. 18)
  • the read access function RF or write access function WF is started ent ⁇ speaking.
  • the write access function WF adjusts the adjacency lists AD_LIST1, AD_LIST2, AD_LIST3 in accordance with the current second array ARR2.
  • the first storage medium MEMl is preferably delivered to a car manufacturer by a manufacturer of the control device 6 such that the data structure is immutable, in particular the third adjacence list AD_LIST3, which is stored on the first storage medium MEM1.
  • the second storage medium MEM2 is designed so that the automobile can change ⁇ manufacturer, the data structure on the second storage medium MEM2.
  • the second storage medium MEM2 is formed so that the As ⁇ ten Modell and their data on the second storage medium MEM2 can not be changed.
  • a first program ( Figure 7) for operating the motor vehicle 2 ge preferably on the storage device MEM ⁇ is stored.
  • the first program is used to determine the Anlagenfunkti ⁇ on FCT, which is assigned to the predetermined event EVE. Furthermore, the first program that serves the ermit ⁇ Telte vehicle function FCT to start ACT or inhibit DEACT.
  • the first program is preferably started shortly after ei ⁇ nem starting the motor vehicle 2, in particular when starting the internal combustion engine 4 and / or the control device 6 in a step Sl. In step Sl who initialized ⁇ where appropriate variables.
  • the predetermined event EVE ermit ⁇ telt.
  • the predetermined event EVE can be detected, for example, by a sensor of the internal combustion engine 4.
  • an event entry is EVE_ENT ermit ⁇ telt, which is assigned to the predetermined event EVE, pending from ⁇ from the predetermined event EVE.
  • the event entry EVE_ENT can be determined, for example, using the event ID EVE_ID.
  • the first adjacency list is AD_LIST1 it averages ⁇ , the net is the determined event entry EVE_ENT zugeord ⁇ , depending on the event entry EVE_ENT.
  • the first adjacency AD_LIST1 is preferably determined on the basis of the event ⁇ pointer EVE_Z1, EVE_Z2 pointing to a beginning of the first adjacency AD_LIST1. _ -
  • an adjacency list entry AD_LIST1_ENT of the first adjacency list AD_LIST1 is determined as a function of the first adjacence list AD_LIST1.
  • steps S6 and S7 and, if appropriate, further steps all adjective list entries AD_LIST1_ENT, AD_LIST1_ENT1, AD_LIST1_ENT2 of the first adjacence list AD_LIST1 are processed.
  • a vehicle function entry FCT_ENT is determined, which is assigned to the adjacency list entry AD_LIST1_ENT of the first adjacence list AD_LIST1, depending on the adjacence list entry AD_LIST1_ENT of the first adjacence list AD_LIST1.
  • the vehicle function entry FCT_ENT it is also possible to determine only the vehicle function identifier FCT_ID, which is then assigned to the adjacency list entry AD_LIST1_ENT of the first adjacence list AD_LIST1.
  • the vehicle function entry FCT_ENT means of Adjazenzlisten container AD_LIST_Z1, AD_LIST1_Z2 the first adjacency AD_LIST1 is determined that the driving ⁇ generating function entry FCT_ENT or the corresponding vehicle ⁇ function identifier FCT_ID shows.
  • the vehicle function FCT is determined to the vehicle function entry FCT_ENT. This can play as gen at ⁇ based on the vehicle function list FCT_LIST SUC ⁇ in which the vehicle function FCT corresponding ⁇ de vehicle function identifier FCT_ID associated with the corresponding vehicle function entry FCT_ENT respectively.
  • step S10 the determined vehicle function FCT is started ACT or inhibited DEACT.
  • step S12 the processing can initially also be continued in a step S12. _ -
  • step S12 the condition CDN is determined which is assigned to the predetermined event EVE and from which the predefined event EVE can be classified as having entered.
  • the condition CDN is preferably determined as a function of the first duration DUR1 and the frequency EVE_FREQ with which the predetermined event EVE has occurred.
  • step S13 it is checked whether the condition CDN he fills ⁇ OK. If the condition of step S13 is satisfied, then the program is continued in step S10. If the condition is not satisfied CDN of the step S13, the Be ⁇ processing is continued in step S2.
  • the first program can be ended.
  • the first program may alternatively be so implemented in a program of the control device 6 that shortly after a start of the motor vehicle 2, in particular of the internal combustion engine ⁇ 4 of the motor vehicle 2, the first program for all predetermined events EVE is processed. This ensures that the number of EVE_COUNT specified differently surrounded events EVE is also true when the specified differently bene event EVE is already present in the starting of the motor vehicle 2.
  • a second program may be stored in the memory device MEM of the control unit 6.
  • the second program is used to assign the predetermined event EVE the predetermined amount of event and allocate the predetermined amount of event of the corresponding vehicle ⁇ function FCT.
  • steps S14 to S19 the second program is executed according to the steps Sl to S6 of th ers ⁇ program. - -
  • the event set entry EVE_SUM_ENT is determined which is assigned to the addiction list entry AD_LIST1_ENT of the first adjacence list AD_LIST1, preferably by means of the adjacency listen pointer AD_LIST1_Z1, AD_LIST1_Z2 of the first adjacence list AD_LIST1 shows the corresponding event set entry EVE_SUM_ENT.
  • the second adjacence list AD_LIST2 is determined, which is assigned to the corresponding event set entry EVE_SUM_ENT, preferably by means of the event set pointer EVE_SUM_Z1, EVE_SUM_Z2 of the event set list EVE_SUM_LIST, which points to a start of the second adjacency list AD_LIST2.
  • step S22 depending on the second adjacency list AD_LIST2, the adjacency list entry AD_LIST2_ENT of the second adjacency list AD_LIST2 is determined in accordance with step S18.
  • step S23 and if appropriate in the wide ⁇ ren steps further Adjazenzlisteneinträge AD_LIST2_ENT be found in the second adjacency AD_LIST_2 which are encompassed by the second adjacency AD_LIST_2.
  • step S24 depending on the adjacency list entry AD_LIST2_ENT of the second adjacence list AD_LIST2, the vehicle function entry FCT_ENT is determined, which is assigned to the adjacence list entry AD_LIST2_ENT of the second adjacency list AD_LIST2. _ -
  • step S25 the vehicle function FCT is determined according to the step S9 of the first program.
  • the number of events EVE_COUNT detected by the event counter is matched to the events EVE associated with the vehicle function FCT, preferably by increasing the number EVE_COUNT of the occurred predetermined events EVE by one unit.
  • a step S27 the second program can be ended.
  • step S28 it is checked whether the number EVE_COUNT of the occurred predetermined events EVE is greater than a maximum number EVE_COUNT_MAX of the occurred events EVE that the event counter can count. If the condition of step S28 is not satisfied, the processing in step S26 is continued. If the condition of step S28 is fulfilled, it means that the corresponding ⁇ de event counter can not further specified events EVE count. Therefore, the processing is continued in a step S29.
  • an auxiliary event counter EVE_COUNT_ADD is started and adjusted, preferably by being raised by a standardized ⁇ A. Subsequently, the second program may be terminated in step S27. For example, if the condition of step S28 is satisfied, the number EVE_COUNT of the occurred predetermined events EVE may be subtracted from the maximum number EVE_COUNT_MAX of the events EVE entered and the result may be used as an index of the corresponding auxiliary event counter EVE_COUNT_ADD. - -
  • a third program for operating the motor vehicle 2 may be stored in the control device 6.
  • the third program is ent ⁇ speaking the first program to determine the vehicle function FCT depending on the event that has occurred EVE.
  • Steps S30 to S35 of the third program are entspre ⁇ accordingly tet the steps Sl to S6 toarbei ⁇ the first program.
  • a step S36 it is ⁇ telt dependent ermit of the event entry EVE_ENT a start of the third AD_LIST3 adjacency list, which is assigned to the event entry EVE_ENT.
  • an adjacency list entry AD_LIST3_ENT of the third adjacency list AD_LIST3 is determined, which is included in the third adjacency list AD_LIST3.
  • the remaining adjacency list entries AD_LIST3_ENT1, AD_LIST3_ENT2 of the third adjacence list AD_LIST3 are determined accordingly.
  • step S39 the step S8 in accordance with the first program of the vehicle function entry FCT_ENT ermit ⁇ telt.
  • a step S40 the vehicle function FCT is determined according to the step S9 of the first program. _ -
  • step S41 according to the step S26 of the second program, the number EVE_COUNT of the occurred events EVE is adjusted.
  • the third program may be terminated in accordance with the step S11 of the first program.
  • a fourth program for starting ACT or for inhibiting DEACT of the vehicle function FCT is stored on the memory device MEM.
  • the fourth program is used to activate the vehicle function FCT ACT or to deactivate DEACT depending on the number EVE_COUNT of the occurred predetermined events EVE.
  • the fourth program is started in a step S43 in accordance with the step S1 of the first program.
  • a step S44 it is checked whether the number EVE_COUNT of the entered predetermined events EVE is greater than zero NULL.
  • step S44 If the condition of step S44 is not satisfied, the fourth program may be terminated in a step S46. If the condition of step S44 is satisfied, the processing is continued in step S45.
  • step S45 to the step S9 of the f ⁇ th program the vehicle function FCT started ACT or inhibited DEACT will accordingly.
  • step S46 the fourth program may be ended.
  • the fourth program is restarted and so preferably all vehicle functions FCT, in particular _ _
  • a fifth program of the control device 6 is stored ( Figure 11) on the SpeI ⁇ chervorraum MEM.
  • the fifth program is used to set the state value EVE_STATE ⁇ .
  • the fifth program is started in a step S48 ent ⁇ the step S1 of the first program.
  • step S49 it is checked whether the number EVE_COUNT of the occurred predetermined events EVE is greater than zero NULL. If the condition of step S49 is not met, the fifth program in a step S51 terminates the ⁇ . If the condition of step S49 is satisfied, the processing is continued in step S50.
  • step S50 the state value EVE_STATE associated with the corresponding event counter is set equal to zero NULL.
  • step S51 the fifth program can be terminated .
  • the fifth program is ent ⁇ speaking to the fourth program is started again, and so before ⁇ preferably all state values of the vehicle functions EVE_STATE FCT adjusted.
  • a sixth program of the motor vehicle 2 is stored ( Figure 12) on the SpeI ⁇ chervorraum MEM.
  • the sixth program is in accordance with the fourth program as ⁇ to inhibiting the vehicle function FCT to start or ACT _ _
  • the sixth program is started in a step S52 ent ⁇ the step S1 of the first program.
  • step S53 it is checked whether the state value EVE_STATE is zero. If the condition of the step S35 is not satisfied, the sixth program may be terminated in a step S55. If the condition of step S53 is satisfied, the processing is continued in step S54.
  • step S54 according to the step S45 of the fourth program, the vehicle function FCT is started ACT or inhibited DEACT.
  • the sixth program can complete the ⁇ .
  • the sixth program entspre ⁇ accordingly the fourth and the fifth program of allmaifunktio ⁇ is again executed NEN FCT preferably for all state values EVE_STATE.
  • a seventh program is stored ( Figure 13) on the SpeI ⁇ chervorraum MEM.
  • the seventh program is to check whether the vehicle functions FCT are correctly assigned to the corresponding predetermined event EVE.
  • the seventh program is entspre in a step S56 ⁇ accordingly started to step Sl of the first program.
  • a step S57 the number of the pre-EVE_COUNT is determined give ⁇ NEN event EVE.
  • step S58 it is checked whether the number EVE_COUNT of the corresponding given predetermined events EVE is greater than zero NULL. If the condition of step S58 is fulfilled, can the sieve ⁇ th program in a step S60 are terminated. Is the _ _
  • step S58 the machining ⁇ tung is continued in a step S59.
  • step S59 an error message ERROR is generated and preferably stored in an error memory of the memory device MEM.
  • the control device 6 can be restarted as a function of the error message ERROR and / or, if appropriate, the predetermined event EVE, which relates to the faulty control device 6, can be classified as having entered.
  • step S60 the seventh program may be ended.
  • the seventh program is continued again in step S56 so that all numbers EVE_COUNT of the occurred predetermined events EVE can be checked.
  • the processing after step S56 may also be continued in a step S61.
  • step S61 it is checked whether the number EVE_COUNT of the occurred predetermined events is greater than or equal to zero NULL. If the condition of the step S61 is satisfied, the seventh program may be terminated in a step S63. If the condition of step S61 is not satisfied, the Be ⁇ processing is continued in a step S62.
  • step S62 the Def ⁇ lermeldung ERROR is generated corresponding to the step S59.
  • an eighth program may be stored in the memory device MEM (FIG. 14).
  • the eighth program is used according to the seventh program to check whether the assignment of the vehicle function LINK LINK to the predetermined event EVE is correct.
  • the program is started in a step S65 in accordance with the step S1 of the first program.
  • step S66 according to the step S57 of the seventh program, the number EVE_COUNT of the occurred predetermined events EVE is determined.
  • a step S67 the number EVE_COUNT of the occurred predetermined events EVE is reduced by one unit.
  • step S68 it is checked whether the number EVE_COUNT of the entered predefined events is greater or equal to zero NULL. If the condition of step S68 is not satisfied, the error message ERROR is generated in step S69 according to step S59 of the seventh program. If the Be ⁇ dingung of step S68 are met, the eighth program is started again with the next execution of the eighth program to another predetermined event EVE is checked as in the previous execution of the eighth program.
  • the eighth program is preferably not terminated in a step S70, when all the numbers EVE_COUNT the pre ⁇ passed in the intervening EVE were reviewed. This simply makes it possible to check whether all predefined events EVE were correctly recognized during operation of the motor vehicle 2 and the assigned vehicle functions FCT were started ACT or inhibited DEACT accordingly.
  • step S65B the eighth program can be continued in a step S65B, in which the number EVE_COUNT of the entered predefined events EVE is assigned a current number EVE_COUNT_AV of the entered predefined events EVE. _ _
  • step S66B the number EVE_COUNT of the occurred predetermined events EVE is set equal to zero.
  • step S67B according to the step S57 of the seventh program, the number EVE_COUNT of the occurred predetermined events EVE is determined.
  • step S68B it is checked whether the number EVE_COUNT of the occurred predetermined events EVE corresponds to the current number EVE_COUNT_AV of the occurred predefined events EVE. If the condition of step S68b fulfilled, the eighth program is preferably started again, in which case a different number is checked EVE_COUNT of another predetermined event occurred EVE than the scaffoldi ⁇ gen execution of the eighth program. If the condition of step S68B is not met, the error message ERROR is generated in a step S69B according to step S69.
  • the eighth program is preferably ended only when all the numbers EVE_COUNT of the predefined events EVE have been checked.
  • a ninth program ( Figure 15) stored in the memory device MEM.
  • the ninth program is used to read the assignment LINK of the assignment rule.
  • the ninth program is accordingly started in a step S71 entspre ⁇ step Sl of the first program.
  • step S72 the read access function RF is started to read the association LINK of the vehicle function FCT _ _
  • the ninth program may be ended.
  • a tenth program (FIG. 16) is preferably stored on the memory device MEM of the control unit 6.
  • the tenth program is used to store the assignment LINK of the vehicle function FCT to the predetermined event EVE on the memory device MEM.
  • the tenth program is started in a step S74 in accordance with the step S1 of the first program.
  • the assignment LINK is created CREATE vehicle ⁇ function FCT to the predetermined event EVE.
  • CREATE in this combination means that in the configuration program CONF_PROG a matrix entry corresponding to the assignment LINK is made in the matrix MATRIX.
  • the assignment LINK is given the condition CDN and / or a length AD_LIST_LEN of the adjacency lists AD_LIST1, AD_LIST2.
  • step S76 it is checked whether the association with ge ⁇ optionally the condition exists EXIST CDN. If the Be ⁇ dingung of step S76 are met, the tenth program can be ended in a step S78. If the condition of step S76 is not satisfied, the processing is continued in step S77.
  • step S77 the write access function WF is started to write the association LINK into the first adjacency list AD_LIST1, if necessary together with the condition - -
  • step S77 can also be continued again in step S75.
  • a different assignment LINK is written to the memory device MEM than in the previous execution.
  • an eleventh program (FIG. 17) may be stored on the memory device MEM.
  • the eleventh program is accordingly started in a step S80 entspre ⁇ step Sl of the first program.
  • a step S81 according to the step S72 of the ninth program, the assignment of the vehicle function FCT to the predetermined event EVE is read from FROM the first adjacence list AD_LIST1.
  • a step S82 the assignment LINK of the vehicle function FCT to the predetermined event EVE is written to the second storage medium MEM2 as an array ARR.
  • a step S83 the array ARR can be read from the Configurati ⁇ onsprogramm CONF_PROG.
  • the eleventh program may be ended.
  • a twelfth program (FIG. 18) can be stored on the memory device MEM to write the association LINK.
  • the twelfth program is started in a step S85 corresponding to step Sl of the first Pro ⁇ program. _ _
  • a step S86 the assignment LINK is created CREATE vehicle ⁇ function FCT to the predetermined event EVE.
  • the association LINK is written to the second storage medium MEM2 as the array ARR.
  • the assignment LINK can also be divided into several arrays ARR1, ARR2.
  • a step S88 it is checked if the association LINK of the array ARR exists EXIST. If the condition of the step S88 is satisfied, the twelfth program may be terminated in a step S91. If the condition of step S88 is not satisfied, then the processing in a step S89 sets fortge ⁇ .
  • the first adjacency list is AD_LIST1 pending adjusted by the assignment LINK from ⁇ , which is presented by the array ARR.
  • step S91 the twelfth program may be ended.
  • the twelfth program however during loading ⁇ drive of the motor vehicle 2 periodically executed repeatedly, for example, after expiry of the second time period DUR2.
  • step S93 the processing in step S87 is continued.
  • the adjacence lists AD_LIST1, AD_LIST2, AD_LIST3 can be created with a computer program product for creating the adjacency lists AD_LIST1, AD_LIST2, AD_LIST3, depending on the matrix MATRIX (FIG. 5).
  • the computer program product includes program instructions, a computer readable medium having Pro ⁇ that are executable by a computer.
  • the program instructions are designed to create at least the first adjacence list (AD_LINK1) depending on the matrix MATRIX.
  • the computer program product may in ⁇ play as well as the configuration program CONF_PROG umfas ⁇ sen.
  • the entire adjacency AD_LIST1, AD_LIST2, AD_LIST3 that the complete mapping ⁇ prescribed include, sent from the configuration program CONF_PROG to the controller.
  • the Computerprogrammpro ⁇ domestic product is preferably delivered from the manufacturer of the control device 6 to the automotive manufacturers, in particular to the configu- gurateur the control device.
  • the invention is not limited to the specified personssbei ⁇ games.
  • all or more of the programs may be implemented in a main program.
  • only individual programs can be implemented differently.
  • the programs can be divided into further subroutines.
  • programs can be implemented in standard processes of the control device 6 and / or standard processes for processing the protocol PROT.
  • another Adjazenzlisten representation can be selected as described.
  • the first three Adjazenzlisten representations can be combined.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Debugging And Monitoring (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Safety Devices In Control Systems (AREA)

Abstract

La présente invention concerne un procédé permettant de faire fonctionner un véhicule à moteur (2). Ce procédé consiste, lorsqu'au moins un événement prédéfini (EVE1) du véhicule à moteur (2) se produit (ACT), à déterminer au moins une fonction de véhicule (FCT) associée à l'événement prédéfini (EVE1) par association (LINK) par le biais d'au moins une première liste d'adjacence (AD_LIST1). La fonction de véhicule déterminée (FCT) est ensuite lancée ou bloquée.
EP07727136A 2006-04-04 2007-03-20 Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique Withdrawn EP2005297A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102006015677A DE102006015677A1 (de) 2006-04-04 2006-04-04 Verfahren und Vorrichtung zum Betreiben eines Kraftfahrzeugs, Verfahren und Vorrichtung zum Zugreifen auf eine Zuordnungsvorschrift, und Computerprogrammprodukt
PCT/EP2007/052659 WO2007115910A2 (fr) 2006-04-04 2007-03-20 Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique

Publications (1)

Publication Number Publication Date
EP2005297A2 true EP2005297A2 (fr) 2008-12-24

Family

ID=38229459

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07727136A Withdrawn EP2005297A2 (fr) 2006-04-04 2007-03-20 Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique

Country Status (5)

Country Link
US (1) US20100292866A1 (fr)
EP (1) EP2005297A2 (fr)
CN (1) CN101416162A (fr)
DE (1) DE102006015677A1 (fr)
WO (1) WO2007115910A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102012005197B3 (de) * 2012-03-16 2013-06-13 Iav Gmbh Ingenieurgesellschaft Auto Und Verkehr Verfahren zur Optimierung einer Brennkraftmaschine
DE102012208179A1 (de) * 2012-05-16 2013-11-21 Robert Bosch Gmbh Verfahren zum Betreiben einer Elektronikeinrichtung eines Kraftfahrzeugs sowie eine entsprechende Elektronikeinrichtung

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6259981B1 (en) * 1999-06-17 2001-07-10 Thomas J. Wilcosky Caution/warning system for displaying system malfunctions/faults in a night-time viewing mode
DE19941440B4 (de) * 1999-08-31 2006-10-19 Siemens Ag Verfahren zum gesteuerten Betrieb einer Vorrichtung
DE10051781A1 (de) * 2000-10-19 2002-04-25 Daimler Chrysler Ag Systemdiagnoseverfahren und Vorrichtung zur Durchführung eines Systemdiagnoseverfahrens
US20030125993A1 (en) * 2001-12-27 2003-07-03 Ho Chi Fai Method and system for event distribution
JP2004017676A (ja) * 2002-06-12 2004-01-22 Denso Corp 車両用通信システム、初期化装置及び車両用制御装置
US8069415B2 (en) * 2003-09-30 2011-11-29 International Business Machines Corporation System and method for generating perspectives of a SAN topology
DE10354471A1 (de) * 2003-11-21 2005-06-30 Siemens Ag Verfahren und Vorrichtung zur Fehlerdiagnose in Steuereinrichtungen einer Brennkraftmaschine eines Kraftfahrzeugs
KR20060047436A (ko) * 2004-04-23 2006-05-18 니혼 소아 가부시키가이샤 2차원 및 3차원 도형의 데이터를 컴퓨터의 메모리에기록하는 데이터 구조, 프로그램 및 기록 매체
DE102004046874A1 (de) * 2004-09-28 2006-04-13 Robert Bosch Gmbh Verfahren zum Betreiben eines Verwaltungssystems von Funktionsmodulen
DE202006003273U1 (de) * 2005-12-06 2006-06-01 Volkswagen Ag Diagnosevorrichtung in einem Fahrzeug für eine funktionsorientierte Diagnose
WO2007076598A1 (fr) * 2005-12-31 2007-07-12 Intelligent Mechatronic Systems Inc. Systeme de lecture de contenu personnalisable commande par un evenement

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2007115910A2 *

Also Published As

Publication number Publication date
WO2007115910A2 (fr) 2007-10-18
WO2007115910A3 (fr) 2008-04-03
US20100292866A1 (en) 2010-11-18
CN101416162A (zh) 2009-04-22
DE102006015677A1 (de) 2007-10-18

Similar Documents

Publication Publication Date Title
DE102005013285B4 (de) Verfahren zum Konfigurieren eines Steuergeräts und Steuergerät
DE102008021030B4 (de) Verfahren zum Betreiben eines Fahrzeugs sowie entsprechende Vorrichtung und entsprechendes Fahrzeug
DE102008041360A1 (de) Steuergerät für ein Fahrzeug und Verfahren für eine Datenaktualisierung für ein Steuergerät für ein Fahrzeug
DE102017217668A1 (de) Verfahren und zentrale Datenverarbeitungsvorrichtung zum Aktualisieren von Software in einer Vielzahl von Fahrzeugen
DE102005040142A1 (de) Verfahren zur Identifikation komplexer Diagnosesituationen im Kundendienst
DE19653429C2 (de) Verfahren zur Überprüfung der Funktionsfähigkeit einer Recheneinheit
DE19736231C2 (de) Verfahren zum Ändern von Daten eines Steuergeräts für ein Kraftfahrzeug
EP2005297A2 (fr) Procédé et dispositif permettant de faire fonctionner un véhicule à moteur, procédé et dispositif permettant d'accéder à une consigne d'association et produit programme informatique
EP3014372B1 (fr) Système diagnostique d'un atelier
DE102012000539A1 (de) Diagnosewerkzeug für ein Fahrzeugsteuersystem
DE10340372A1 (de) Verfahren zur Installation einer Programmkomponente
EP3073438B1 (fr) Procede de determination d'une appartenance d'un vehicule automobile a une norme relative aux gaz d'echappement et ordinateur de bord
DE102022110251A1 (de) Ota-master, center, system, verfahren, nicht-transitorisches speichermedium und fahrzeug
EP1241570A2 (fr) Analyse automatique de version des composants d'un logiciel appartenant à une application de logiciel
DE102018117509A1 (de) Verfahren, Vorrichtung, Computerprogramm und Computerprogrammprodukt zum Überwachen einer Wirkkette eines Wirknetzes eines Fahrzeuges
EP1733284A2 (fr) Commande d'execution de fonctions sur des appareils qui interagissent les uns avec les autres
DE102009002898A1 (de) Verfahren zur Aktualisierung eines Steuergeräts eines Fahrzeugs
WO2021239281A1 (fr) Procédé, système, programme informatique et support d'enregistrement pour la documentation d'une actualisation de logiciel d'un composant de véhicule
WO2007065585A1 (fr) Procede et dispositif de diagnostic oriente fonction d'un systeme comportant des composants mis en reseau
DE102020108142A1 (de) Verfahren, Vorrichtung, Computerprogramm und computerlesbares Speichermedium zur Ermittlung einer Maßnahme zum verkehrssicheren Betreiben eines Fahrzeuges mehrerer Fahrzeuge
EP2569763A1 (fr) Procédé de surveillance assistée par ordinateur de la puissance fonctionnelle d'un système technique
WO2024132506A1 (fr) Procédé et système de distribution de composants logiciels à des véhicules
DE102022110824A1 (de) Ota-master, system, verfahren, nicht-transitorisches speichermedium und fahrzeug
DE102021112661A1 (de) Verfahren, Vorrichtung, Computerprogramm und computerlesbares Speichermedium zur Ermittlung von fehlerbehafteten Fahrzeugen
DE102022134027A1 (de) Computer-implementiertes Verfahren zum Bestimmen Algorithmusversions-kompatibler Test- und/oder Simulationsdaten und entsprechendes System

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20081104

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20090824

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20100105