WO2006063924A1 - Verfahren zum initialisieren eines elektronischen systems umfassend mehrere plug-ins - Google Patents
Verfahren zum initialisieren eines elektronischen systems umfassend mehrere plug-ins Download PDFInfo
- Publication number
- WO2006063924A1 WO2006063924A1 PCT/EP2005/056224 EP2005056224W WO2006063924A1 WO 2006063924 A1 WO2006063924 A1 WO 2006063924A1 EP 2005056224 W EP2005056224 W EP 2005056224W WO 2006063924 A1 WO2006063924 A1 WO 2006063924A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- plug
- ins
- size
- interface
- functionality
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25093—During start, integration into machine, send module functionality to scheduler
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25101—Detect connected module, load corresponding parameters, variables into module
Definitions
- the present invention relates to a method of initializing an electronic system having a base interface and a plurality of plug-ins connected thereto.
- the invention also relates to a communication protocol for processing on at least one computing device of an electronic system during the initialization of the electronic system.
- the electronic system includes a base interface and several plug-ins connected thereto.
- the invention relates to a computer program for processing on a computing device of a data processing system.
- the computer program includes several plug-ins and a basic interface, with the plug-ins connected to the base interface.
- the present invention also relates to an electronic system with a
- the electronic system includes a base interface and several plug-ins connected thereto.
- an electronic system for vehicles which consists of first components for performing control tasks in operating procedures and second components that coordinate an interaction of the first components.
- the first components carry out the control tasks through a combination of operating functions and basic functions.
- the operating functions are implemented in operating submodules (so-called plug-ins) and can be modularly integrated into the electronic system, re-used and exchanged or changed at any time.
- the basic functions are summarized in a base layer, which communicates with the operating modules via a suitable interface.
- a system layer which comprises the second components for coordinating the interaction of the first components Implementation of the control tasks includes.
- an intelligence is present, which is required for integrating the plug-ins into the overall system.
- the functionalities of the plug-ins build on the functionalities of the system layer and even require it.
- the plug-ins must therefore be tailored to the functionalities of the system layer and can not easily in other electronic
- the initialization of the system and the linking of the plugins to each other are not realized by the plug-ins themselves, but only by the system layer and / or an underlying operating system layer.
- the initialization is thus controlled centrally, a communication between the plug-in of the system before or during initialization does not take place.
- the present invention has the object, the known method to design and further develop that the initialization of the electronic system can be performed much more flexible than before.
- the links of the plug-ins are to be generated automatically in the context of initialization, without the electronic system, the type and number of connected plug-ins and their functionality or processes must be known in advance.
- first of all the plug-ins connected to the basic interface are queried for specific information.
- This information relates, for example, to the functionalities realized in the plug-in or the corresponding processes.
- the information relates to the variables determined by the processing of the processes and provided by the plug-in, as well as the sizes that the plug-in needs to execute the functionalities or to process the processes.
- variables are, for example, variables, functions, structures, etc.
- the plug-ins of the electronic system according to the invention therefore have additional initialization functionality in order to respond to the corresponding requests from the basic interface and to transmit the desired information ,
- the base interface After receiving the information from a first plug-in, the base interface asks the remaining plug-ins if they can provide at least one of the required sizes. If this is the case, information is provided to the first plug-in through the base interface
- a plug-in of the electronic system according to the invention thus has the additional initialization functionality to save the received references to one or more plug-ins, which provide the required sizes of the plug-in, at a suitable location.
- At least one empty field is provided in the plug-ins, where the reference can be stored.
- the reference can be stored.
- the size is retrieved by the other plugin via the reference.
- references to various other plug-ins can also be stored in the plug-ins, especially if different sizes are required in a plug-in. References to the other plug-ins can be of any kind.
- the connections between the plug-ins can be created at runtime during the initialization of the electrical system, regardless of which plug-ins are actually connected to the base interface, and without having to know in advance which Plug-ins are connected.
- the method according to the invention allows maximum flexibility in terms of adding, removing and changing plug-ins of an electronic system.
- the plug-ins can be designed as hardware (for example as plug-in cards with additional input / output interfaces, additional drivers, additional memory or computing capacities, etc. for a control unit) or as software (for example as operating submodules of a computer program).
- the basic interface has no functionality to complement the
- the purpose of the basic interface concerns only the linking of the plug-ins during initialization and the communication between the plug-ins during operation of the electrical system.
- the necessary information about the plug-ins is obtained by the basic interface directly from the plug-ins during the initialization phase of the electronic system through a communication with the plug-ins.
- the at least a functionality is realized by at least one process. That is, the functionalities of the plug-ins are realized by one or more processes.
- the transmission of information regarding the functionality of the plug-ins thus concerns any information regarding the processes implemented in the plug-in.
- the information concerning the functionality of the plug-ins comprises a time frame in which the at least one process is processed, and a priority of the at least one process.
- a pointer to a memory location is stored as a reference, at which the required size is stored by one of the other plug-ins.
- the referenced memory space may be provided in one of the plug-ins, but also in the base interface or a subordinate base functionality or basic software.
- Working with pointers has several advantages. One advantage is that if the software is updated in a plug-in, the old software can remain in memory, the new software is stored in another new location in memory, and the pointer is simply converted to the new memory location. A reprogramming (so-called flashing) of the entire memory (deletion of the old content and writing with the new software) is not required.
- a pointer to a structure is stored, in which stored at a predetermined position, the required size by one of the other plug-ins becomes.
- a separate pointer is not stored for each required size on a memory location where the required size is stored, but only a single pointer stored on a structure where all the required sizes are stored.
- the structure comprises a certain number of fields, with certain sizes stored in certain fields. For example, it is defined in advance that a size A is always stored at the third position in the structure. When size A is needed in a plug-in, the plug-in jumps to the beginning of the structure pointed to by the pointer.
- the required size is read and then returned to the plug-in again.
- the structure may be included in the base interface or child base functionality or base software.
- the content of the structure is continuously updated by the plug-ins providing the appropriate sizes. This embodiment has the advantage that only one field is needed in the plug-ins for the pointer pointing to the beginning of the structure, even if more than one size is needed in the plug-in.
- the question is which plug-in should provide the size for the remaining plug-ins that need the size.
- the size of the plug-in for further processing is advantageously used, whose process for determining the size has the highest priority. Since this process has the highest priority, it will be able to provide the required size before the other processes.
- the size is provided by the plug-in from which the base interface first receives the information that the plug-in or a process of the plug-in -in the needed size can provide.
- the size be provided by the plug-in from which the base interface receives the last information that the plug-in or a process of the plug-in can provide the required size.
- the base interface has access to an initialization table with information on where the individual plug-ins are stored. If the plug-ins are software-designed, this table can be updated when flashing new plug-ins. In the case of plug-ins configured as software, but also as hardware, it is also conceivable that at the beginning of the initialization the plug-ins connected to the basic interface and their (initial) addresses are determined and the table is updated accordingly.
- the table is preferably stored in the basic interface. Based on this table, the base interface can then query the individual plug-ins and obtain the desired information.
- the electronic system is designed as a computer program, is a structuring of the computer program into basic software without plug-ins, a master interface arranged above and plug-ins and / or sub-interfaces connected thereto, to which further sub-interfaces and / or further plug-ins are connected conceivable.
- the basic software comprises a fixed, permanent part of the software, which is responsible, for example, for communication via bus drivers, etc. In this way, it is possible to achieve a cascaded structure of the electronic system. For this structure, a visibility concept can be realized, by means of which it is possible to limit the visibility of certain variables from below, that is, from higher-ranking areas, to certain lower-ranking areas of the structure.
- the interfaces are divided into different areas (eg private, public, protected, etc.). Only the variables within the same area of the interfaces (variables, functions, etc.) are visible to subordinate (ie higher ranking) interfaces and thus also accessible. The same size can be applied to different areas of an interface. As a result, the sizes can be encapsulated in certain areas and are somewhat similar to local variables.
- the interfaces are divided into a private area and a public area. Only the public variables (variables, functions, etc.) applied to the public area of an interface are visible to a subordinate interface and therefore also accessible. The private quantities applied to the private area of the interface are only visible in the relevant interface and public areas of interfaces located above.
- a subordinate interface only has access to the values applied to the public areas of the superordinate interfaces.
- the sizes applied to the private areas are not visible to the subordinate interface and therefore not accessible.
- an encapsulation of program areas or the functionalities realized therein is thus made possible in a simple manner.
- the externally developed program areas can also be easily and quickly integrated into an existing computer program with the help of this visibility concept.
- any size needed by the plug-ins or provided by the plug-ins be assigned a unique identifier for a defined area of the electronic system.
- the defined area is preferably the area of the electronic system completed by the visibility concept.
- the identifier includes, for example, an identification number and an indication of whether the size is public or private.
- the identifiers of the variables are stored in an identification list which can be accessed by the basic interface during the initialization of the electronic system. It is conceivable that all variables (variables, functions, etc.) theoretically available in the electronic system are listed and explained in the identification list. The list is created for the whole system and not for the currently connected plug-ins. Therefore, regardless of the type and number of connected plug-ins, it always has the same content.
- the base interface in advance no information about the plug-ins actually connected are available.
- the list preferably forms the basis for an interface agreement or interface definition and serves as the basis both for the supplier of software or plug-ins and for the integrator.
- the communication protocol be programmed in such a way that information is made available when the electronic system of the basic interface is initialized by the plug-ins concerning: + at least one functionality performed by the respective plug-in;
- the basic interface provides information to the individual plug-ins regarding: which of the remaining plug-ins needed a size required by the plug-in
- the electronic system is designed as a computer program, so that the plug-ins are operating submodules of a computer program. Accordingly, therefore, the invention is realized by the computer program.
- the plug-ins in the context of the initialization of the electronic system of the basic interface provide information concerning: + at least one of the respective Plug-in executed functionality; + Sizes used by the respective plug-in to execute the at least one
- FIGS. Show it: 1 shows an inventive electronic system according to a first preferred embodiment
- Figure 2 shows the structure of a plug-in
- FIG. 3 shows a flowchart of a method according to the invention in accordance with a preferred embodiment
- FIG 4 shows an inventive electronic system according to another preferred embodiment.
- plug-and-play mechanisms are realized from the prior art for both software and hardware.
- an additional or a different functionality can be made available in a control unit simply by programming an operating submodule (a so-called plug-in).
- the plug-in component would be designed as software.
- plug-in component would be designed as hardware.
- a particularly preferred field of use of plug-in components is in a control unit network, where additional control units can be added and connected, for example via a CAN bus with the other control units. As a result, additional or different functionalities can be made available to the ECU network.
- An example of such a known plug-in mechanism is, for example, the integration of an ACC (Adaptive Cruise Control) function into an existing control unit network in a motor vehicle.
- ACC Adaptive Cruise Control
- the hardware components required for the ACC function are installed in the motor vehicle, they either immediately or after a restart of the system send defined CAN messages, which in a motor control system provide the corresponding functionalities in a computer program or the interfaces of the functionalities , activated.
- ACC Adaptive Cruise Control
- Computer program or the corresponding operating sub-modules (plug-ins), must always be present in the engine control. That is, even if certain functionality is not realized in a motor vehicle, appropriate resources must be provided and maintained to enable the desired functionality when needed.
- the present invention enables a simple, fully automatic integration of new plug-ins into an existing system during initialization of the electronic system.
- the invention provides the prerequisite for a particularly advantageous visibility concept for the variables used in the system (eg, variables, functions, structures, etc.).
- new or modified functionalities can be integrated on a control unit via additional plug-ins without the interfaces, or processes, having to be known in advance to the rest of the system of this control unit.
- the proposed concept allows for subsequent updates and upgrades of functionalities, without having to reprogram (flash) the entire control unit, for example in a workshop. After downloading the new functionalities to the control unit, these automatically log on in the system and are then fully functional.
- mechanisms are proposed for automatically coordinating the variable accesses and automatically integrating the processes, taking into account priorities of processes and variables.
- Figure 1 is an inventive electronic system in its entirety with the
- the system 1 comprises a basic interface 2 and a plurality of plug-in components 3.1 to 3.n connected thereto.
- the electronic system 1 can be realized in terms of hardware, with the plug-in 3.1 to 3. n then representing hardware components that can be mechanically plugged into an existing system and electronically contacted.
- An example of such a hardware implemented plug-in is, for example, a plug-in card with processor, memory and computer program for controlling and / or regulating an ACC functionality in a motor vehicle.
- the additionally provided processor prevents that or the other processors of the electronic system 1 are stressed too much by the additional ACC functionality.
- the integration of an additional hardware plug-in is accompanied by the integration of a corresponding software plug-in.
- the plug-in 3.1 to 3.n realized by software.
- the entire electronic system 1 is thus a computer program whose functionality can be extended, changed or reduced by adding or removing plug-ins 3.1 to 3. n.
- basic software 4 is provided, which comprises a fixed, permanent part of the computer program, which is not changed by adding or removing plug-ins.
- the basic software relates, for example, to communication via bus drivers (for example, a CAN software).
- the basic software 4 defines the manner in which the plug-ins 3.1 to 3. n communicate with the rest of the computer program, regardless of the number and type of plug-ins 3.1 to 3.n.
- the base software 4 comprises a so-called identification list 5, to which the basic interface 2 can at least indirectly access during the initialization of the electronic system 1.
- identification list 5 all theoretically available variables (variables, functions etc.) are listed in the electronic system 1 (compare left column of FIG.
- Identification list 5 (IDl to IDm) and explained (see right column of the identification list 5; A, B, C to M).
- the identification list 5 is created for the entire system 1 and not for the currently connected plug-ins 3.1 to 3. n. Therefore, regardless of the number and type of connected plug-ins 3.1 to 3. n, it always has the same content. More precisely, the quantities are resolved via the corresponding names or Ids. These names or Ids are agreed in advance and managed in the identification list 5.
- the basic interface 2 is set up on the basic software 4 of the electronic system 1 and is responsible for the resolution of the interfaces between the individual plug-ins 3.1 to 3. n.
- the base software 4 represents the part of the computer program that is not structured according to the plug-in concept (for example, low-level software).
- the structure of the plug-in 3.1 to 3. n is shown in more detail in FIG. Part 9 of the plug-in 3.1 to 3. n contains the actual functionality of the plug-in 3.1 to 3. n and part 10 the actual initialization function.
- the part 9 of the plug-ins 3.1 to 3. n comprises at least one additional or changed functionality that is to be made available to the system 1 during runtime. This functionality may be realized by one or more processes included in the functionality part 9.
- the plug-in interface 10 has no functionality at runtime of the computer program, but contains the information 8 (such as the used sizes of the functionality 9), the Initialization of the function will be needed. The initialization itself takes over the basic interface 2.
- initialization table 22 Starting from the initialization function 10, a so-called initialization table 22 is called (reference numeral 23). Through the initialization table 22, the base interface 2 knows the addresses of the initialization functions. As an argument, call 23 contains a pointer to initialization routines stored in another table 24. The initialization routines from Table 24 contain the actual functionality of the initialization functions. The base interface 2 then returns an address (or a pointer) to the corresponding initialization routine in the table 24 to the initialization function 10 (reference numeral 25).
- FIG. 4 shows another electronic system 1 according to the invention in accordance with a further preferred embodiment.
- the system 1 comprises a plurality of base interfaces 2 arranged in cascaded fashion.
- a lower base interface 2 is designed as a master interface 2.1.
- the base interfaces 2 arranged above are designed as so-called subinterfaces 2.2.
- Plug-ins 3.1 to 3.n and / or sub-interfaces 2.2 are connected to all interfaces 2.1, 2.2.
- the connected to the interfaces 2.1, 2.2 plug-in 3.1 to 3. n are shown in Figure 4 only symbolically, dashed and in small numbers.
- FIG. 4 there are some embodiment of the system structure illustrated in FIG. 4, there are some
- Plug-ins 3.1 to 3. n not directly, but only indirectly connected via sub-interfaces 2.2 to the master interface 2.1.
- the interfaces 2.1, 2.2 comprise different areas.
- the visibility concept offers the possibility of using several mutually delimited variable areas, for example public, private, protected, etc.).
- the variables are encapsulated in the corresponding areas.
- the interfaces 2.1, 2.2 are subdivided into only two different areas, namely the public area 11 and the private area 12. Only the voltage applied to the public area 11 an interface 2.1, 2.2 public sizes are visible to a subordinate (and therefore higher-ranking) interface 2.1, 2.2.
- the public area 11 of the sub-interface F is visible to the public area 11 of the sub-interface D.
- the public area 11 of the sub-interface E is visible for the sub-interface C, but not for the master interface A. The reason for this is that the quantities applied to the public area 11 of the sub-interface E abut the private area 12 of the sub-interface C and are therefore not visible from the underlying interface A.
- the inventive initialization method for an electronic system 1 begins in a function block 30.
- the base interface 2 or the master interface 2.1 turns to a first plug-in 3.1 or to a sub-interface 2.2. of the electronic system 1.
- the plug-in 3.1 transmits to the basic interface 2 information regarding the processes that it carries out. This information relates, for example, to the time grid of the processes, the priorities of the individual processes, etc.
- the plug-in 3.1 communicates in a function block 32 which variables (variables, functions, structures, etc.) it needs to process the processes.
- Sub-interfaces 2.2. are treated the same as plug-ins 3.1 to 3.n.
- a sub-interface 2.2 sends information to the subordinate (ie, higher-level) base interface 2 regarding the processes executed by the plug-ins connected to the sub-interface 2.2.
- sub-interface 2.2 tells what sizes are needed by the plug-ins attached to them to process their processes.
- the plug-in 3.1 begins with the transmission of the first required size to the base interface 2. For this purpose, the plug-in 3.1 transmits the corresponding identifier of the size to the base interface 2. Then, in a function block 33 in turn For all other plug-ins 3.2 to 3.n or for all connected to the base interface 2 sub-interfaces 2.2 asked if they can provide the required size.
- the further search can be set. It can also be adjusted if one
- Sub-interface 2.2 was found, which can provide the needed size. In this case, the plug-in 3.2 to 3.n or the sub-interface 2.2 would then supply the required size, from which or from which the base interface 2 first learns that he or she needs the required size Can provide.
- the search will continue until all further plug-ins 3.2 to 3.n and all sub-interfaces 2.2 have been queried as to whether they can provide the required size. From all the plug-ins 3.1 to 3.n and sub-interfaces 2.2, which can provide the required size, the plug-in or the sub-interface 2.2 can be selected, the or the process for determining the required
- the plug-in 3.2 to 3.n or sub-interface 2.2 would be selected with the highest priority process for determining the required size.
- the base interface 2 can also be between public and private sizes. This means that the base interface 2 queries the plug-ins 3.1 to 3. n and the sub-interfaces 2.2, whether they can provide the required size in the desired (private or public) area.
- a plug-in 3.2 to 3.n or a sub-interface 2.2 is selected, which provides a certain size that the plug-in 3.1 needs during the execution of its processes. During the execution of its processes the plugin 3.1 must be able to access the provided size.
- a pointer 13 is stored in the first plug-in 3.1 (cf., FIG. 1), which points to a memory area 14 in one of the remaining plug-ins 3.2.
- the size required by the first plug-in 3.1 is stored by the other plug-in 3.2 and possibly updated regularly.
- a field 15 is provided in the plug-in 3.1, in which the destination address of the pointer 13 can be stored.
- more fields 16 are provided in which also pointers can be stored in memory areas where the required sizes can be picked up during the processing of the processes.
- a pointer 18 is stored, which refers to a structure 19.
- the structure 19 may be stored in any plug-in 3.1 to 3. n or in the base software 4.
- certain quantities are stored at predetermined positions or in predetermined fields.
- the sizes can either be stored directly in the fields of the structure 19, or in the fields further pointers 20 are stored, which refer to a corresponding memory area 21 in one of the plugins 3.1 to 3.n or in the base interface 2, where the required size is then stored.
- the plug-in 3.3 when a certain size is needed, first jump to the beginning of the structure 19. There is then jumped depending on the size required in the corresponding field of the structure 19. In the illustrated embodiment, the third field of the structure 19 is jumped, where an address of the pointer 20 is stored on the memory area 21 in the plug-in 3.n. From there, the current value of the required size is fetched. Thereafter, the processing of the interrupted process in the plug-in 3.3 continues.
- a query block 35 it is checked whether the plug-in 3.1 has been provided with information for all the quantities it requires, which allows it to access the sizes during the execution of its processes. If not, a branch is made to the function block 32, where the plug-in 3.1 continues with the transmission of the next required size to the base interface 2. The loop comprising the function blocks 32 to 34 and the query block 35 is run through until the plug-in 3.1 information has been transmitted for all sizes required by him.
- a branch is made to a further query block 36, where it is checked whether all plug-ins 3.1 to 3.sub.n connected to the base interface 2 and all sub-interfaces 2.2 have informed the basic interface 2 which sizes they are need to process their processes. If not, the system branches to the function block 31, where the next plug-in 3.2 or the next sub-interface 2.2 of the basic interface 2 informs about their processes. In the subsequent loop comprising the blocks 32 to 35, information is then transmitted to the next plug-in 3.2, where it can access the quantities it requires. The loop comprising the functional blocks 31 to 34 and the Query blocks 35 and 36 are run through until all connected to the base interface 2 plug-in 3.1 to 3. n and all sub-interfaces 2.2 have informed the base interface 2, which sizes they need to process their processes. As soon as this is the case, the method according to the invention is terminated in a function block 37.
- the connected to the system 1 plug-in 3.1 to 3. n information regarding the executed by them functionalities, that is, for example, in terms of priority, the time frame, etc. the in them realized processes, spend.
- the plug-ins 3.1 to 3.n would have to specify the quantities they need to process the processes they implement, and specify the sizes that they can provide by processing the processes they implement. All of this information flows together in the base interface 2 and is processed there in a suitable manner.
- the plug-ins 3.1 to 3.n which require certain sizes, become pointers
- the inventive method is realized by a communication protocol that is processed on at least one computing device of the electronic system 1.
- a computing device is in particular a microprocessor or a microcontroller.
- Such a computing device for Processing of the communication protocol is, for example, in the base interface 2 and in each of the plug-in 3.1 to 3. n or in the sub-interfaces 2.2 available.
- the communication protocol for processing by the computing devices is loaded in addition to the operating system and executed fully automatically.
- the communication protocol can also be executed after a reset of the system 1 (so-called reset), without requiring a complete restart of the system 1.
- the sub-interface 2.2 forwards the request Framework of the visibility concept to the plug-ins 3.1 to 3. n next.
- n and the basic software 4 are entered in lists. These lists are provided by the master interface 2.1 for certain operating system task periods (for example, 10 ms). During initialization, the processes to be called in the operating system tasks are entered in the corresponding lists of the scheduler. For split times (for example 30 ms), dividers are calculated which only start this call on the nth task pass (for example, in a 10 ms task every third time). The process lists of the master interface 2.1 are entered in the task management or the entries are retrieved from there.
- n does not necessarily have to include a process.
- the plug-in functions use the pointers 13, 18 to access the quantities they require.
- all variables are referenced via a unique identifier, a so-called identification number ID.
- identifiers include information about the physical content, unit, data type, and conversion formulas of the corresponding quantities.
- this requires a central point, which coordinates or manages all available identifiers. The coordination or management of all available identifiers is carried out by the base interface 2 with access to an identification list 5.
- the supplier is responsible for structuring the plug-ins according to the visibility concept presented above.
- the plug-in needs to be inserted into the rest of System 1. Everything else is handled master-interface 2.1 during initialization fully automatically. That is, the integrator no longer needs to make any adjustments to the residual system 1 (such as processes integration or the like).
- the system structure according to the invention can be used, for example, for a control unit, in particular for a motor vehicle control unit (for example an engine control unit), on which applications or functionalities are integrated by different suppliers.
- a desired functionality can be downloaded (flashed) to a defined area of the control unit. After initialization according to the method according to the invention, this functionality is available in the overall system 1 or in the vehicle without the customer having to intervene in any way.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05811127A EP1828886A1 (de) | 2004-12-15 | 2005-11-25 | Verfahren zum initialisieren eines elektronischen systems umfassend mehrere plug-ins |
CN2005800429552A CN101080692B (zh) | 2004-12-15 | 2005-11-25 | 用于初始化包含多个插件的电子系统的方法 |
US11/792,737 US20080155405A1 (en) | 2004-12-15 | 2005-11-25 | Method for Initializing an Electronic System Comprising Several Plug-Ins |
JP2007546011A JP2008523519A (ja) | 2004-12-15 | 2005-11-25 | 複数のプラグインを含む電子システムを初期化する方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102004060301A DE102004060301A1 (de) | 2004-12-15 | 2004-12-15 | Verfahren zum Initialisieren eines elektronischen Systems umfassend mehrere Plug-Ins |
DE102004060301.4 | 2004-12-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006063924A1 true WO2006063924A1 (de) | 2006-06-22 |
Family
ID=36123565
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2005/056224 WO2006063924A1 (de) | 2004-12-15 | 2005-11-25 | Verfahren zum initialisieren eines elektronischen systems umfassend mehrere plug-ins |
Country Status (6)
Country | Link |
---|---|
US (1) | US20080155405A1 (de) |
EP (1) | EP1828886A1 (de) |
JP (1) | JP2008523519A (de) |
CN (1) | CN101080692B (de) |
DE (1) | DE102004060301A1 (de) |
WO (1) | WO2006063924A1 (de) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009129083A (ja) * | 2007-11-21 | 2009-06-11 | Denso Corp | 車両制御装置およびそれを用いた車両制御システム |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008062255A1 (en) * | 2006-11-21 | 2008-05-29 | Renault Trucks | Truck and bodybuilder module for this truck, method, memory and software to configure the bodybuilder module |
DE102007039428A1 (de) | 2007-08-21 | 2009-02-26 | Beckhoff Automation Gmbh | Programmiervorrichtung für ein Netzwerk aus Steuerknoten und Anlage mit einer solchen Programmiervorrichtung |
JP4924373B2 (ja) * | 2007-11-14 | 2012-04-25 | 住友電装株式会社 | 通信ユニット及び通信システム |
US8155829B2 (en) * | 2007-11-21 | 2012-04-10 | Denso Corporation | Common control apparatus and vehicle control system |
CN101604371B (zh) | 2009-07-22 | 2012-02-08 | 阿里巴巴集团控股有限公司 | 插件权限的控制方法及系统 |
JP5891794B2 (ja) * | 2011-02-09 | 2016-03-23 | 株式会社リコー | 情報処理装置及びプログラム |
DE102011012187A1 (de) * | 2011-02-23 | 2012-08-23 | Continental Automotive Gmbh | Verfahren zum Konfigurieren einer Steuervorrichtung für ein Kraftfahrzeug, Computerprogramm und Steuervorrichtung |
JP6375310B2 (ja) | 2014-01-09 | 2018-08-15 | 川崎重工業株式会社 | 車両およびその運転支援方法 |
DE102016009857A1 (de) * | 2016-08-12 | 2018-02-15 | WAGO Verwaltungsgesellschaft mit beschränkter Haftung | Automatische Initialisierungsroutine in einem Automatisierungs-System |
CN115904544A (zh) * | 2022-12-27 | 2023-04-04 | 哈尔滨工大卫星技术有限公司 | 一种插件化的数字化卫星系统及其管理方法和介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10000997A1 (de) * | 1999-01-28 | 2001-01-04 | Ibm | Elektronisches Steuersystem |
US20020147903A1 (en) * | 2001-04-10 | 2002-10-10 | Discreet Logic Inc. | Initialising modules |
US20030078699A1 (en) * | 2000-09-07 | 2003-04-24 | Klaus Harms | Electronic system for a vehicle and system layer for operational functions |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5519866A (en) * | 1993-06-28 | 1996-05-21 | Taligent, Inc. | Method and apparatus of incrementally linking components of a modeled computer program |
EP1176496A1 (de) * | 2000-07-24 | 2002-01-30 | Hewlett-Packard Company, A Delaware Corporation | Spannungsregelung in einer integrierbaren Schaltungsanordnung |
US6842856B2 (en) * | 2001-05-11 | 2005-01-11 | Wind River Systems, Inc. | System and method for dynamic management of a startup sequence |
US7284246B2 (en) * | 2002-04-23 | 2007-10-16 | Canon Kabushiki Kaisha | Extensible device driver |
JP2003330756A (ja) * | 2002-05-14 | 2003-11-21 | Mitsubishi Electric Corp | 監視制御ソフトウェアの構成管理方法 |
US7584471B2 (en) * | 2002-09-23 | 2009-09-01 | Telefonaktiebolaget L M Ericsson (Publ) | Plug-in model |
US7509638B2 (en) * | 2004-08-02 | 2009-03-24 | International Business Machines Corporation | Method and apparatus for providing a pluggable and extendable J2EE architecture |
-
2004
- 2004-12-15 DE DE102004060301A patent/DE102004060301A1/de not_active Withdrawn
-
2005
- 2005-11-25 JP JP2007546011A patent/JP2008523519A/ja active Pending
- 2005-11-25 EP EP05811127A patent/EP1828886A1/de not_active Ceased
- 2005-11-25 US US11/792,737 patent/US20080155405A1/en not_active Abandoned
- 2005-11-25 WO PCT/EP2005/056224 patent/WO2006063924A1/de active Application Filing
- 2005-11-25 CN CN2005800429552A patent/CN101080692B/zh not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10000997A1 (de) * | 1999-01-28 | 2001-01-04 | Ibm | Elektronisches Steuersystem |
US20030078699A1 (en) * | 2000-09-07 | 2003-04-24 | Klaus Harms | Electronic system for a vehicle and system layer for operational functions |
US20020147903A1 (en) * | 2001-04-10 | 2002-10-10 | Discreet Logic Inc. | Initialising modules |
Non-Patent Citations (1)
Title |
---|
See also references of EP1828886A1 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009129083A (ja) * | 2007-11-21 | 2009-06-11 | Denso Corp | 車両制御装置およびそれを用いた車両制御システム |
Also Published As
Publication number | Publication date |
---|---|
JP2008523519A (ja) | 2008-07-03 |
EP1828886A1 (de) | 2007-09-05 |
CN101080692B (zh) | 2010-10-06 |
DE102004060301A1 (de) | 2006-06-22 |
CN101080692A (zh) | 2007-11-28 |
US20080155405A1 (en) | 2008-06-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1828886A1 (de) | Verfahren zum initialisieren eines elektronischen systems umfassend mehrere plug-ins | |
EP0577919A1 (de) | Zugriffssteuerung für gekoppelte maskenprogrammierte Mikrocontroller | |
EP3230856B1 (de) | Verfahren zum update von firmware von geräten | |
DE102005010476A1 (de) | Steuergerät mit konfigurierbaren Hardwaremodulen | |
EP2881858B1 (de) | Verfahren zur Änderung der Software im Speicher eines elektronischen Steuergerätes | |
EP3538960A1 (de) | Ablaufsteuerung von programmmodulen | |
EP1700211B1 (de) | Laden von software-modulen | |
DE102011007714B4 (de) | Verfahren für die Verwendung mit einem Batterieüberwachungssystem, Batterieüberwachungssystem und Verwendung des Verfahrens | |
WO2005078540A1 (de) | Verfahren zum konfigurieren einer automatisierungskomponente eines automatisierungssystems und entsprechendes automatisierungssystem | |
WO2019162122A1 (de) | System zum übertragen zumindest eines aktualisierungspakets für zumindest ein steuergerät eines kraftfahrzeugs sowie verfahren | |
EP3015995A1 (de) | Verfahren zum konfigurieren einer schnittstelleneinheit eines computersystems | |
DE102017130552B3 (de) | Verfahren zur Datenverarbeitung und speicherprogrammierbare Steuerung | |
DE102019117954A1 (de) | Laufzeitserver zum gleichzeitigen Ausführen mehrerer Laufzeitsysteme einer Automatisierungsanlage | |
EP4289123A1 (de) | Verfahren und vorrichtung zur konfiguration einer applikation | |
EP0499213A2 (de) | Modular strukturiertes ISDN-Kommunikationssystem | |
EP3285162A1 (de) | Verfahren zum projektieren eines projektes sowie anordnung zur durchführung des verfahrens | |
WO2012072180A2 (de) | Verfahren zum betreiben einer arbeitsmaschine und arbeitsmaschine | |
DE102012218665B4 (de) | Applikationssystem für Steuergeräte | |
DE60307172T2 (de) | Ein Verfahren und Netzwerkvorrichtung bestehend aus einem flexiblem EEPROM um Konfigurationseinstellungen einzustellen | |
DE10064339B4 (de) | Integrierte Schaltungsanordnung in einem Bremskraftregelsystem | |
EP3482467A1 (de) | Steckverbinderbauteil, steckverbinder, steckverbindersystem und verfahren zum zusammensetzen und betreiben eines steckverbinders | |
DE102016121542A1 (de) | Ablaufsteuerung von Programmmodulen | |
DE102017100118A1 (de) | Skalierbares Steuersystem für ein Kraftfahrzeug | |
DE102022132909A1 (de) | Orchestrierungssystem zum Aktualisieren von Containern mit darin enthaltenen Applikationen sowie hierauf basiertes Orchestrierungsverfahren | |
WO2016092006A1 (de) | Firmware-management-system sowie firmware-management-verfahren zum update von firmware von geräten |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2005811127 Country of ref document: EP |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11792737 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007546011 Country of ref document: JP Ref document number: 200580042955.2 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 3114/CHENP/2007 Country of ref document: IN |
|
WWP | Wipo information: published in national office |
Ref document number: 2005811127 Country of ref document: EP |