EP1583039B1 - Vehicle and method for a vehicle - Google Patents
Vehicle and method for a vehicle Download PDFInfo
- Publication number
- EP1583039B1 EP1583039B1 EP05101655.8A EP05101655A EP1583039B1 EP 1583039 B1 EP1583039 B1 EP 1583039B1 EP 05101655 A EP05101655 A EP 05101655A EP 1583039 B1 EP1583039 B1 EP 1583039B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- vehicle
- specification file
- information
- data bus
- vehicle specification
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 17
- 230000015654 memory Effects 0.000 claims description 37
- 238000012423 maintenance Methods 0.000 claims description 30
- 238000004891 communication Methods 0.000 claims description 24
- 238000012986 modification Methods 0.000 claims description 24
- 230000004048 modification Effects 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 21
- 230000006870 function Effects 0.000 description 29
- 238000013475 authorization Methods 0.000 description 7
- 238000010276 construction Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 230000008901 benefit Effects 0.000 description 4
- 230000008439 repair process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000003292 diminished effect Effects 0.000 description 2
- 239000002828 fuel tank Substances 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000008672 reprogramming Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000009423 ventilation Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/006—Indicating maintenance
Definitions
- the present invention relates to an apparatus, a method and a computer program for maintenance of a motor vehicle comprising a communication bus.
- the transportation technology has developed towards an increased use of network solutions for controlling various kinds of units and processes in the vehicles.
- CAN Controller Area Network
- Keyword 2000 renders it possible to interconnect different CANs to form a joint network (a Keyword 2000 network).
- the joint network may include multiple CANs, which are operated and controlled simultaneously.
- So-called on-board diagnostic (OBD) systems may be used to perform tests whether a specific control unit connected to a CAN is operating properly.
- An on-board diagnostic facility such as a dashboard mounted video display, may provide access to information generated by the OBD system.
- vehicle control units There might be a number of vehicle control units arranged on each CAN and being controlled by the network. It is well known to have vehicle component modules arranged to control various vehicle components such as lights, brakes and automatic transmission. Usually the vehicle component modules are programmable so that the functions of the vehicle may be slightly amended depending on the demands of the buyer. In the vehicle modules fault codes are usually stored, which fault codes indicate when any vehicle component has operated erroneously.
- vehicle module codes Due to the complexity of modern vehicles and the large number of functions available to the consumers the vehicle module codes become very extensive. When the vehicles are at service it may be possible to connect a computer to the vehicle and retrieve information from the vehicle modules. This information may include the earlier mentioned fault codes as well as the vehicle module codes. However, the extensive vehicle module codes make it cumbersome for service personnel to get an overview of how the vehicle is intended to function.
- DE 197 28 083 A1 in turn describes a system for vehicle data communication comprising a vehicle data transmission bus to which electrical control devices of the vehicle are connected.
- a communication module is connected to the data bus and constitutes an autonomous interface for the transmission of data between an external communications post and one or more of the control devices.
- a transmission path that comprises the data bus and a wireless transmission section is thus formed for external access to read/download vehicle data from/to the vehicle control devices.
- the integrated communication module together with the data bus connection of the control devices aims at providing a communication system of high capacity and enabling that specific data need only be stored in one place (control device) to be accessible both internally by the other control devices as well as externally through the wirelessly connected communication stations for e.g.
- vehicle manufacturing and service purposes road toll data collecting, vehicle pool related data collecting and for enabling remote vehicle control.
- vehicle control data also can be inputted to the control devices through the communication system from the external stations e.g. for the purpose of setting vehicle speed reference values either for vehicle internal speed control or for remote controlled distance regulation to surrounding vehicles.
- the present invention aims at providing an apparatus, a method and a computer program that solves at least one of the problems indicated above. This is achieved with an apparatus, a computer program or a method according to the appended independent claims.
- An apparatus for maintenance of a motor vehicle comprises at least one controllable vehicle component, a data bus, a memory connected to the data bus for storing a vehicle specification file, and at least one programmable electronic control unit arranged to control at least one of the controllable vehicle components.
- Each electronic control unit is connected to the data bus and is programmed with a respective parameter set, the apparatus comprises an apparatus connector for connection of the apparatus to the data bus of the motor vehicle.
- the apparatus is characterised in that the apparatus comprises a parameter setting module for deriving the parameter set from the vehicle specification file.
- the apparatus When the apparatus is connected to the data bus through the apparatus connector and on receipt of a programming command, it is arranged to read the vehicle specification file from the memory, to derive the parameter set from the vehicle specification file using the programming module and to program the electronic control unit with the derived parameter set through the data bus.
- a vehicle to be serviced by an apparatus comprises a number of electronic control units which control different electrical functions in a vehicle.
- the vehicle specification file is stored in at least one electronic control unit but may also be stored in more than one place in the vehicle.
- the vehicle specification file comprises information about the electronic control units in the vehicle, technical information on the vehicle and product specifications for the functions of the vehicle.
- An apparatus provides a robust solution for maintenance of the vehicle.
- a vehicle specification file from which it is possible to derive the parameter sets used to program the ECU:s it is easily overviewed by a service man who is going to work with the vehicle.
- a parameter setting module for deriving the parameters of the vehicle it is only a matter of updating the parameter setting module to be able to use new electronic control units that have hit the market after release of the vehicle.
- an apparatus according to the invention provides freedom for modifying the motor vehicle.
- the apparatus may be arranged to read information from each one of the electronic control units connected to the data bus through the apparatus connector. This provides a possibility to recreate at least a part of the vehicle specification file in case the vehicle specification file should be corrupted.
- the information from the electronic control units may comprise an identification number from each electronic control unit. This information may be used to electronically control that the electronic control units are the same as are specified by the vehicle specification file.
- the apparatus may also comprise a communication connector for connection of the apparatus to a central server. This may be used to provide updates of the parameter setting module to the apparatus.
- the apparatus may be arranged to read the vehicle specification file from the memory through the apparatus connector and the data bus and to send the vehicle specification file as an e-mail through the communication connector to a central server, on a command from a user.
- the sending of the vehicle specification file as an e-mail is an effective, fast and reliable way to provide the vehicle specification file to a central server.
- the parameter setting module may be implemented with a computer program within the apparatus, wherein the apparatus is arranged to receive an update to the parameter setting module through the communication connector and wherein the apparatus is arranged to implement the update to the parameter setting module.
- the parameter setting module as a computer program it is of course also possible to implement the parameter setting module as hard-wired electronics.
- the implementation in the form of a computer program provides, however, a much more flexible solution.
- the vehicle specification file may further comprise at least one of the types of information from the group comprising, information on the dimensions of the vehicle, information on the chassis of the vehicle, information on the engine of the vehicle, information on the length of cables in the vehicle, information on the arrangement of the cables in the vehicle, the arrangement of the cables, information on electrical components in the vehicle, and information on updates of the vehicle.
- the list above is not exhaustive but other types of information may be included in the vehicle specification file.
- the apparatus may comprise a user input device for input of information from a user.
- the user input device may be an ordinary keyboard but the input device may also be any other form of input device as known to a man skilled in the art, e.g. a microphone, a digitiser board or a touch screen.
- the apparatus comprises a graphical user interface which is arranged to control a display connected to the apparatus.
- the display may of course be any kind of display known to a man skilled in the art.
- the apparatus may be arranged to receive through the communication connector, alert modifications to be made on a vehicle type and an alert identifier identifying such vehicles.
- the apparatus When connected to a vehicle, the apparatus is arranged to read the vehicle specification file from the vehicle, to compare the alert identifier with the identifier in the vehicle specification file, to compare the alert modifications with the vehicle specification file if the identifiers correspond to each other for identifying modifications still remaining to be performed, and to output a notification to a user on such modifications to be performed.
- the problem with uncorrected construction errors is diminished as most vehicles are serviced regularly and as the construction errors then may be corrected at those instances.
- the staff at the workshop may get information on the vehicle from the vehicle specification file. This might be very valuable in order to be able to correct any problems with the vehicle as the information in the vehicle specification file may give guidance to whether there have been made any modifications to the vehicle. If modifications have been made at a non-licensed workshop it is probable that the vehicle specification file has not been updated. Thus, the modification may be detected through the discrepancy between the vehicle specification file and the status of the physical vehicle. If , for example, an electronic control unit (ECU) has been replaced with a non-standard ECU this may be detected by comparing the information in the vehicle specification file with the actual ECU arranged on the vehicle.
- ECU electronice control unit
- the apparatus may be arranged in such a way that it, when connected to a vehicle, reads the vehicle specification file from two different memories connected to the data bus of the vehicle, and compares the vehicle specification files to determine whether any one of the vehicle specification files has been changed and outputs a signal indicating any discrepancy between the vehicle specification files on the display.
- the apparatus may further be arranged to control at least one check sum of each one of the vehicle specification files in order to control which vehicle specification file is correct, in case there is a discrepancy between the vehicle specification files. This allows the apparatus to check which one of the vehicle specification files is correct.
- Each vehicle specification file may have more than one check sum. This makes it possible to control parts of the vehicle specification file and further makes it possible to combine a correct part of the first version of the vehicle specification file with a correct part of the second version of the vehicle specification file.
- the apparatus may further be arranged to retrieve information on the mileage of the vehicle from the vehicle specification file, to use the mileage of the vehicle and the programming module to provide information on the service rules and to output the service rules on the display.
- An apparatus arranged in this way may automatically provide the service rules on the display and make it easy for a service man to get information on what has to be done on the vehicle.
- the mileage may be provided to the apparatus as an input through the input device.
- a computer-readable memory media on which a computer program for maintenance of a motor vehicle is stored, which motor vehicle comprises at least one controllable vehicle component, a data bus, a memory connected to the data bus for storing a vehicle specification file comprising information about electronic control units (3), and at least one programmable electronic control unit arranged to control at least one of the controllable vehicle components, wherein each electronic control unit is connected to the data bus and is programmed with a respective parameter set.
- the computer program comprises instructions which when run on a computer allows the computer to communicate with the data bus of the motor vehicle.
- the computer program is characterised in that the program also comprises a programming module for deriving the parameter set from the vehicle specification file, and that the program, on receipt of a programming command, makes the computer send signals, for reading the vehicle specification file from the memory, through the data bus, to derive the parameter set from the vehicle specification file using the programming module and to program the electronic control unit with the derived parameter set by sending them through the data bus.
- a computer program may be implemented on a standard computer to implement the apparatus according to the invention.
- a method for maintenance of a motor vehicle comprising at least one controllable vehicle component, a data bus, a memory connected to the data bus for storing a vehicle specification file comprising information about electronic control units (3), and at least one programmable electronic control unit arranged to control at least one of the controllable vehicle components, wherein each electronic control unit is connected to the data bus and is programmed with a respective parameter set.
- the method is characterised in that it comprises the steps of providing a parameter setting module for deriving the parameter set from the vehicle specification file, reading the vehicle specification file from the memory through the data bus of the motor vehicle, deriving the parameter set from the vehicle specification file using the parameter setting module, and programming of the electronic control unit with the derived parameter set through the data bus.
- This method is preferably implemented using an apparatus as described above.
- the ECU:s are programmed with a large number of codes in order to achieve the desired functions.
- the vehicle specification file describes the vehicle in a high level language.
- the vehicle specification file is then transformed into codes for programming the ECU:s.
- a motor vehicle 1 according to an embodiment of the present invention is shown.
- the motor vehicle is shown as a truck but the motor vehicle may also be any other kind of motor vehicle.
- the motor vehicle comprises a number of controllable vehicle components 2, wherein each one of the vehicle components 2 is controlled by a programmable electronic control unit (ECU) 3.
- the electronic control units (ECU:s) are all connected to a data bus 4.
- all ECU:s are connected to a common data bus 4, but as will be described below it is possible to have the ECU:s grouped and each group of ECU:s connected to a respective data bus.
- the number of groups and data buses may be any number.
- the vehicle components 2 may for example be the tail lamp 13 or the head light 14 of the motor vehicle 1.
- a vehicle connector 5 which is connected to the data bus 4 and which is connectable to an apparatus 6 for maintenance of the motor vehicle 1.
- CECU central electronic control unit
- a central server 21 which comprises a memory 8 for storing a vehicle specification file.
- the connection to a central server 21 makes it possible to send data relating to the motor vehicle 1 to the central server 21 and to send data relating to the vehicle 1 from the central server 21 to the motor vehicle.
- the connection between the vehicle connector 5 and the apparatus 6 as well as the connection between the apparatus 6 and the central server 21 may be wireless.
- the wireless connections may be provided in any way known to a person skilled in the art.
- the data network comprises a first data bus 9, a second data bus 10, and a third data bus 11, wherein all three buses 9, 10, 11, are connected to a central electronic control unit (CECU) 7, which in turn is connected to a vehicle connector 5 arranged on the vehicle for connection of an apparatus 6 for maintenance to the data buses 9, 10, 11.
- CECU central electronic control unit
- a memory 8 is arranged within the CECU 7 in which various data may be saved. According to the invention a vehicle specification file is saved in the memory 8.
- the principal layout of the apparatus 6 for maintenance of the motor vehicle is shown in fig 1 .
- the apparatus 6 comprises an apparatus connector 17 for connection of the apparatus 6 to the vehicle connector 5 on the vehicle.
- the apparatus 6 comprises a number of modules 23, 24 which are implemented by computer programs within the apparatus.
- a display 16 is connected to the apparatus for display of information to the service personnel using the apparatus 6.
- the apparatus 6 for maintenance further comprises a communication connector 18 for connection of the apparatus 6 to a network such as the internet or any other network.
- the apparatus 6 may communicate with a central server through the communication connector 18.
- the apparatus 6 also comprises an input device 19, such as a keyboard for input of information from the service person using the apparatus 6.
- the apparatus 6 for maintenance is provided with an input 20 for a dongle 22 used to provide access to the modules of the apparatus, which modules may be implemented by computer programs. Access to the apparatus may be permitted at different authorisation levels, depending on the code comprised within the dongle 22.
- the coding system used in the dongle and the apparatus may be any of the coding systems known to a person skilled in the art.
- the coding of the dongle may be implemented in hardware or software.
- a first level of authorisation may for example authorise a service person only to read information from the motor vehicle, while a second level of authorisation may authorise a service person to change a limited amount of data in the motor vehicle. Finally, a third level of authorisation may authorise a service person to change all possible information in the motor vehicle.
- the vehicle specification file 25 is shown schematically in fig 3 and is divided into a number of blocks for programming reasons. Each block in the vehicle specification file has its own checksum, its own identification and information on the version, so that each block may be handled separately.
- the head 26 of the vehicle specification file 25 also comprises pointers to the other blocks within the vehicle specification file 25 so that all blocks may be easily accessed.
- the head also comprises an identification name, that identifies the vehicle specification file 25, and a version number. If, in the future, further blocks are included into the vehicle specification file 25, the version number is updated.
- the head comprises a digital fingerprint that has information on who created the vehicle specification file 25 and when it was created by writing the date, identification on the application that created the vehicle specification file 25, the version of the application and the serial number of a USB-key that is used for authorisation purposes.
- ECU-block 27 Also included in the vehicle specification file 25 is an ECU-block 27, an FPC-block 28, an XPC-block 29, UFC-block 30, a CABL-block 31 and a version-block 32, which will now be explained in more detail in turn.
- the ECU-block 27 comprises a list over the ECU:s of the vehicle. This list includes the address of each ECU, an identification number for each ECU, function parameters describing possible functions for each ECU, the part number of each ECU, configuration checksum and adjustment values.
- a vehicle identification number VIN
- VIN vehicle identification number
- the FPC-block 28 comprises a product specification of the vehicle.
- This product specification contains information on which type of vehicle it is and comprises the functional product characteristics of the vehicle. It is used during the production of the vehicle and is abstract in that it does not comprise article numbers on the parts but has information on the vehicle from a functional perspective. Examples of such functional product characteristics is the wheel base of the vehicle, the wheel configuration, i.e. the number of wheels on each axle and their size, the size of the fuel tank, the type of gear box and the colour of the vehicle. Due to the design of the FPC-block 28 the values of the different functional product characteristics cannot be saved in the FPC-block 28. In the FPC-block 28 only codes are saved which represents different values.
- the main task for the FPC-block 28 is to serve as in data when programming spare parts or when adjusting the ECU:s.
- Programming of a spare ECU means a full configuration of all configurable functions in an ECU. In a normal vehicle about 1000 parameters in ECU:s are configured from about 100 functional product characteristics. The conversion of the functional product characteristics to the programming parameters is made by the apparatus for programming the vehicle.
- the XPC-block 29 comprises information relating to the vehicle, which information cannot be contained within the FPC-block 28, i.e. values for the different product characteristics. Thus, information on values corresponding to the different codes in the FPC-block 28 is stored in the XPC-block 29.
- the XPC-block 29 may be used to store different new information when demands for the storage of new information arises.
- the information in the XPC-block 29 may be used in programming of spare ECU:s. Examples on the information in the XPC-block 29 is information on the gear ratio of the final drive and the volumes of the left and right fuel tanks. Apart from information that may be used for programming a spare ECU the XPC-block 29 may also comprise information of administrative character.
- the UFC-block 30 comprises information on the functions experienced by the user of the vehicle, such as the function of an automatic gearbox, the function of the ventilation system and the function of the cruise control.
- the UFC-block 30 also comprises the information on implementations of each one of the functions for the vehicle. By information on implementation is meant information on how ECU:s are programmed in order to provide the functions.
- information on implementation is meant information on how ECU:s are programmed in order to provide the functions.
- the information in the UFC-block 30 is displayed to the service technician.
- Comprised within the UFC-block 30 is all electric system functions and information on their implementation in the vehicle. This individualised information makes fault-tracing easier.
- the information in the UFC-block 30 is only references to the information in the form of graphical pictures and describing text that is implemented in the apparatus for maintenance.
- the CABL-block 31 comprises all the information on the cables of the vehicle. This information includes data on the lengths of the cables and how they are connected. As in the case with the UFC-block 30 this is an individualised amount of information in the form of a list over the cables that are incorporated in the vehicle.
- the information in the CABL-block 31 together with information in the apparatus for maintenance provides a maintenance technician with sufficient information for a fast and reliable fault-tracing.
- the version-block 32 contains information on the modifications made on the vehicle. This information is valuable to have as this makes it possible to control the original specifications of the vehicle.
- a new version-block 32 is created which indicates what has been made on the vehicle together with a new fingerprint with information on which application that was used to update the version-block 32, information on the version of the application, the date of the update and the serial number of the USB-key.
- the vehicle specification file 25 also comprises a campaign-block 33, which is similar to the version-block 32 but which comprises information over performed campaigns that are to be conducted instead of rebuilds.
- the information in the campaign-block 33 indicates which modifications that has been made on a vehicle.
- the vehicle specification file 25 There are a number of reasons for updating the vehicle specification file 25.
- One such reason may be the failure of one of the ECU:s.
- the type of ECU that has failed is out of stock it has to be replaced by another one which is compatible with the old one.
- the parameter sets used to program the ECU differs between different ECU:s.
- the parameter setting module in the apparatus for maintenance.
- Such support is provided by the parameter setting module, which comprises information on a large number of different ECU:s and how their parameter sets should be arranged to provide different functions.
- a new version of the ECU supports more functions than the original version of the ECU.
- the parameters are set so that the original functions are achieved.
- the hardware permits new functions to be implemented this may also be done.
- the replacement of a broken ECU 3 controlling an automatic gearbox will be described.
- the motor vehicle When the motor vehicle is at the workshop it will be connected to the apparatus 6 for maintenance of the motor vehicle 1.
- the apparatus will read the vehicle specification file 25 from the motor vehicle and identify the identification numbers of all ECU:s 3 in the vehicle from the vehicle specification file 25.
- the identification numbers will be displayed on the display connected to the apparatus for maintenance.
- a broken ECU 3 may be identified in a number of different ways known to a person skilled in the art. This may for example be accomplished by comparing a fault description, provided by a user of the motor vehicle, with different fault scenarios. If the ECU 3 itself is not responding, this may also be an indication on that the ECU 3 is broken. Furthermore, a broken ECU 3 may be identified by fault codes that may be registered with a fault detection system separate from the network 12 of ECU:s 3 or integrated with that network 12.
- the service person using the apparatus 6 for maintenance may choose that ECU 3 in the apparatus 6 using the input device 19 and the display. After having chosen a specific ECU 3 the apparatus 6 may suggest a replacement ECU 3 that may be used in place of the broken ECU 3 and may also display information describing the functions of the ECU 3 on the display. After having replaced the ECU 3 the service person may input information, through the input device 19 to the apparatus 6, that the ECU 3 has been replaced. Then updating of the parameter set for the replaced ECU 3 may commence.
- the apparatus 6 for maintenance derives a new parameter set using the vehicle specification file 25 from the motor vehicle 1 together with information on the ECU 3. The derived parameter set is then transferred from the apparatus 6 for maintenance to the motor vehicle 1.
- the modification of the motor vehicle will be described.
- the owner of the motor vehicle 1 modifies the motor vehicle 1 by adding a second rear axle.
- the apparatus 6 for maintenance which reads the vehicle specification file 25 from the memory 8 of the central ECU 7.
- the apparatus for maintenance updates the version block of the specification file.
- the updated vehicle specification file 25 is saved in the vehicle again.
- the vehicle specification file 25 is sent to a service central with a request for a specific rebuild of a vehicle.
- a new vehicle specification file 25 is provided, which is sent back to the person modifying the vehicle in order to save it into the vehicle.
- the vehicle specification file 25 is also very valuable when servicing the motor vehicle 1.
- the person responsible for the service connects the apparatus 6 for maintenance of the vehicle to the motor vehicle 1.
- the apparatus 1 reads the vehicle specification file 25 from the memory 8 of the central ECU 7 in step 1001 in fig 10 .
- the mileage of the vehicle is either entered into the apparatus 6 by the service man with the input device or is automatically read from the motor vehicle 1 apparatus in step 1002.
- the mileage may be stored in the memory 8 of the central ECU 7.
- From the version block of the vehicle specification file 25 the apparatus 6 extracts in step 1003 information on service that has been performed on the motor vehicle 1 and an identification number identifying the person that has performed the service on the motor vehicle 1.
- the apparatus 6 determines in step 1004 the service that is to be performed on the motor vehicle 1 based on the identification number and the mileage of the motor vehicle 1. The apparatus 6 then compares the service that is to be done with the service that has already been performed on the motor vehicle 1 and display the discrepancy on the display 16 in step 1005. After the service has been performed the vehicle specification file 25 is updated and stored in the memory 8 in step 1006.
- the vehicle specification file 25 is read from the memory 8 of the central ECU 7 and is compared with the information regarding the campaign related to the motor vehicle 1.
- fig 9 the process of investigating a need for a modification due to a campaign is shown.
- the campaign block is read from the vehicle 1.
- the campaign block is compared with information on all campaigns that have been issued in order to determine which campaigns that have not been executed for the vehicle.
- a consistency check may be performed.
- the consistency check comprises a number of steps that will be explained below in connection with the flow diagram in fig 4 .
- the motor vehicle 1 may be subject to different conditions, during which there is a risk that the vehicle specification file 25 is corrupted. This means that it is not possible to be certain about the contents of the vehicle specification file 25. According to an embodiment of the present invention this problem may be diminished by providing two copies of the vehicle specification file 25 within the vehicle, saved at different locations.
- the first version of the vehicle specification file 25 may be saved in the memory 8 of the central ECU 7.
- the second version of the vehicle specification file 25 may be saved in any one of the other ECU:s.
- a first step 401 the vehicle specification file 25 is retrieved from the central ECU 7 as well as the other ECU in which the vehicle specification file 25 is saved.
- the consistency of the two versions of the vehicle specification files may be checked by comparing them. Thus, if there is a discrepancy between the two different versions of the vehicle specification file 25 one may determine that at least one of them is incorrect. If this is the case the checksums of the vehicle specification file 25 are checked. As the vehicle specification file 25 has one checksum for each block it is possible to check each block separately.
- the apparatus 6 may be arranged to retrieve some information from each one of the ECU:s in order to recreate at least some of the vehicle specification file 25.
- blocks having a correct checksum may be retrieved from one of the vehicle specification files 25 while the other blocks may be retrieved from the other vehicle specification file 25 under the provision that they have correct checksums.
- the information read from each one of the ECU:s may for example be an identification number of the ECU:s.
- a second step 402 it is controlled whether it is possible to connect to all ECU:s that are defined in the vehicle specification file 25. If an ECU is missing there are reasons to believe that it does not function in other ways either.
- a third step 403 it is checked whether all ECU:s have the same vehicle identification number as the vehicle specification file 25. In case any of the ECU:s has a different vehicle identification number it is probable that it origins from another vehicle. Thus it probably has to be reprogrammed in order to function properly. In case the vehicle identification number is missing it is probable that a spare ECU has been inserted without having been programmed. This fact is displayed to the person servicing the vehicle.
- a fourth step 404 it is checked whether the ECU:s have the article numbers that are defined in the vehicle specification file 25. There is only a small probability that the vehicle identification number is correct but that the article number is incorrect. However, the main reason for having the article numbers saved in the vehicle specification file 25 is to be able to easily order the correct components when they have to be replaced.
- a control of a checksum is performed. Based on the parameters of the ECU:s that are programmed, a checksum is created which is saved under the respective ECU:s. This checksum is correct only if the ECU:s have been programmed with an authorised apparatus for maintenance.
- the apparatus 6 may comprise a communication connector 18 which is connected to the Internet. The apparatus may then be connected to a central server 21 through the communication connector 18.
- information may also be sent in the opposite direction.
- An example of such transmission is when the computer program in the apparatus has to be updated. The reason for such an update may be that new versions of ECU:s 3 have been released or that new functions have been implemented into the motor vehicles 1. Updates to the program may be sent from the central server 21, via the Internet, through the communication connector 18 to the apparatus 6.
- the vehicle specification file 25 may be forwarded in an e-mail to the central server 21.
- the vehicle specification file 25 is read from the vehicle with an apparatus .
- the apparatus is controlled by a number of program modules. The function of these different program modules will be described in the following.
- a first program module 503 provides for the reading of the vehicle specification file 505 from the vehicle 501.
- the first program module 503 has to be provided with an electronic key 502.
- a second program module 504 has an electronic library which is used to interpret the vehicle specification file and to display a readable version to the operator of the computer,
- a first program module 602 reads the vehicle specification file denoted 603 from the vehicle 601.
- a second program module denoted 604 converts the vehicle specification file 603 to a readable format.
- the first program module 602 also reads the identification for the new ECU from the vehicle 601 and sends it to a third program module denoted 605.
- the third program module 605 is in contact with a database denoted 606. With the information on the identity of the ECU, the vehicle specification file and the database 606 the third program module 605 derives program data to be used for programming the ECU.
- fig 7 the display of information from the UFC-block 30 is displayed.
- the UFC-block 30 of the vehicle specification file 704 is read by a first program module 701 and is sent to a second program module 702, which by using a database 703 provides text and graphics to the operator of the computer.
- a first program module 801 is used to read the CABL-block 31 from the vehicle specification file 802.
- the CABL-block 31 is sent to a second program module 803 which uses a database 804 to collect text and graphics connected to the CABL-block 31.
- a graphical representation is then shown to the operator of the computer.
- the motor vehicle 1 may for example have less than the six wheels shown on the motor vehicle 1 depicted in fig 1 .
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Primary Health Care (AREA)
- Tourism & Hospitality (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Health & Medical Sciences (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Medicines Containing Antibodies Or Antigens For Use As Internal Diagnostic Agents (AREA)
- Combined Controls Of Internal Combustion Engines (AREA)
- Testing And Monitoring For Control Systems (AREA)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE0400828 | 2004-03-30 | ||
SE0400828A SE526826C2 (sv) | 2004-03-30 | 2004-03-30 | Apparat, förfarande och datorläsbart minnesmedium på vilket är lagrat ett datorprogram för underhåll av ett motorfordon |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1583039A1 EP1583039A1 (en) | 2005-10-05 |
EP1583039B1 true EP1583039B1 (en) | 2018-07-04 |
Family
ID=32105787
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05101655.8A Active EP1583039B1 (en) | 2004-03-30 | 2005-03-03 | Vehicle and method for a vehicle |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1583039B1 (sv) |
KR (4) | KR20060045045A (sv) |
BR (1) | BRPI0501073B1 (sv) |
NO (1) | NO332046B1 (sv) |
SE (1) | SE526826C2 (sv) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102006017644B4 (de) * | 2006-04-12 | 2008-04-17 | Dr.Ing.H.C. F. Porsche Ag | Erfassung und Diagnose von Fahrzeugdaten |
KR101583838B1 (ko) * | 2010-06-30 | 2016-01-08 | 현대자동차주식회사 | 네트워크를 이용한 와이어링 회로 검증 시스템 및 방법 |
US9268882B2 (en) | 2011-01-20 | 2016-02-23 | Paccar Inc | System and method for analyzing a powertrain configuration |
JP5939655B2 (ja) * | 2011-03-29 | 2016-06-22 | ボルボ ラストバグナー アーベー | 安全な修理データパッケージ |
DE102012025033B4 (de) | 2012-12-19 | 2018-03-15 | Audi Ag | Verfahren zur Ferndiagnose eines Fehlerzustands in einem Kraftfahrzeug mittels einer fahrzeugexternen Serveranordnung |
SE539785C2 (sv) | 2013-12-02 | 2017-11-28 | Scania Cv Ab | Installation av trådlösa noder i motorfordon |
EP3318448B1 (en) * | 2015-06-30 | 2023-12-06 | Hitachi Astemo, Ltd. | Vehicle data rewrite control device and vehicle data rewrite authentication system |
KR102464013B1 (ko) | 2017-08-18 | 2022-11-04 | 주식회사 엘지에너지솔루션 | 표준 부품 관리 시스템 및 방법 |
KR102552488B1 (ko) * | 2017-12-14 | 2023-07-06 | 현대자동차주식회사 | 차량 제어기의 앱 관리 장치 및 그 방법 |
CN111428892B (zh) * | 2020-03-24 | 2024-01-02 | 深圳市易孔立出软件开发有限公司 | 一种车辆控制单元更换方法、系统及电子设备和存储介质 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1089179A1 (en) * | 1999-08-06 | 2001-04-04 | Eaton Corporation | Vehicle component diagnostic and update system |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3313481C2 (de) * | 1983-04-14 | 1985-02-14 | Daimler-Benz Ag, 7000 Stuttgart | Einrichtung zur Kennzeichnung und Indentifizierung von Kraftfahrzeugen |
DE19728083A1 (de) * | 1997-07-02 | 1999-02-04 | Mc Micro Compact Car Ag | Fahrzeug-Datenkommunikationssystem |
US6370449B1 (en) * | 1999-06-14 | 2002-04-09 | Sun Microsystems, Inc. | Upgradable vehicle component architecture |
DE10021733A1 (de) * | 2000-05-04 | 2001-11-29 | Siemens Ag | Integriertes, Datenbank-gestütztes Dokumentations- und Management-System für Kraftfahrzeuge |
KR100362260B1 (ko) * | 2000-07-13 | 2002-11-23 | 김재우 | 네트워크를 이용한 자동차 진단과 정비서비스 방법 및 그장치 |
CA2420046A1 (en) * | 2000-08-18 | 2002-02-28 | Nnt, Inc. | System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming |
DE10323384A1 (de) * | 2003-05-23 | 2004-12-16 | Daimlerchrysler Ag | Diagnosesystem |
-
2004
- 2004-03-30 SE SE0400828A patent/SE526826C2/sv not_active IP Right Cessation
-
2005
- 2005-03-03 EP EP05101655.8A patent/EP1583039B1/en active Active
- 2005-03-21 NO NO20051499A patent/NO332046B1/no not_active IP Right Cessation
- 2005-03-29 BR BRPI0501073-0A patent/BRPI0501073B1/pt active IP Right Grant
- 2005-03-30 KR KR1020050026765A patent/KR20060045045A/ko active Search and Examination
-
2012
- 2012-08-24 KR KR1020120093283A patent/KR101379942B1/ko active Application Filing
-
2013
- 2013-05-13 KR KR1020130054039A patent/KR20130073921A/ko not_active Application Discontinuation
-
2014
- 2014-01-27 KR KR20140009948A patent/KR101476806B1/ko active IP Right Grant
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1089179A1 (en) * | 1999-08-06 | 2001-04-04 | Eaton Corporation | Vehicle component diagnostic and update system |
Non-Patent Citations (1)
Title |
---|
KREUZ I ET AL: "EXACT CONFIGURATION ONBOARD ONBOARD DOCUMENTATION OF ELECTRICAL AND ELECTRONIC SYSTEMS CONSISTING OF ECUS, DATA BUSES AND SOFTWARE", ERA CONFERENCE. EUROPEAN CONFERENCE EXHIBI, XX, XX, 9 June 1999 (1999-06-09), pages 5.2.01 - 5.2.08, XP009048707 * |
Also Published As
Publication number | Publication date |
---|---|
KR20140044343A (ko) | 2014-04-14 |
SE0400828D0 (sv) | 2004-03-30 |
KR101476806B1 (ko) | 2015-01-02 |
BRPI0501073A (pt) | 2005-11-01 |
KR20120112299A (ko) | 2012-10-11 |
KR20060045045A (ko) | 2006-05-16 |
NO332046B1 (no) | 2012-06-11 |
BRPI0501073B1 (pt) | 2018-07-03 |
NO20051499D0 (no) | 2005-03-21 |
KR101379942B1 (ko) | 2014-04-01 |
EP1583039A1 (en) | 2005-10-05 |
NO20051499L (no) | 2005-10-03 |
SE526826C2 (sv) | 2005-11-08 |
SE0400828L (sv) | 2005-10-01 |
KR20130073921A (ko) | 2013-07-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1583039B1 (en) | Vehicle and method for a vehicle | |
US20070100519A1 (en) | Diagnostic system | |
US8082076B2 (en) | Visual diagnostic system and subscription service | |
You et al. | Overview of remote diagnosis and maintenance for automotive systems | |
CN102262404B (zh) | 整车下线配置系统及其配置方法 | |
WO2015017711A1 (en) | Systems and methods of creating and delivering item of manufacture specific information to remote devices | |
CN101458525B (zh) | 一种电控单元配置自动识别方法 | |
CN104488004A (zh) | 用于提供车辆维修信息的方法和系统 | |
CN104950700A (zh) | 用于车辆控制的电子控制器软件编码系统和方法 | |
CN113597545A (zh) | 用于车辆的便携式无线连接诊断系统 | |
US20070093924A1 (en) | Telediagnosis viewer | |
EP1139217B1 (de) | Verfahren zur Abspeicherung von Daten | |
CN101490718B (zh) | 带有电子控制式制动系统的商用车挂车 | |
US20230153097A1 (en) | Devices and method for managing electronic control units of a motor vehicle | |
DE102022000040A1 (de) | Verfahren zur Bereitstellung, Aktivierung und/oder Verwendung mindestens einer Software-Anwendung in einem Fahrzeug | |
KR102406525B1 (ko) | 차량 제어 장치 및 그 방법 | |
CN116822036A (zh) | 一种汽车线束设计方法 | |
US20230315440A1 (en) | Vehicle software compatibility | |
JP2022150141A (ja) | プログラム更新管理システム、移動体故障診断装置、プログラム更新管理方法 | |
EP2175424B1 (de) | Verfahren zur Steigerung der Effizienz von Fahrzeugen bzw. Fahrzeugsystemen mit und ohne Waffensysteme | |
CN117120307A (zh) | 车辆异常检测装置及车辆异常检测方法 | |
DE102019208134A1 (de) | Off-Board-Diagnosevorrichtung, Off-Board-Diagnosesystem und Verfahren für eine vorbeugende Wartung | |
CN112805185A (zh) | 故障诊断装置 | |
DE102017216797A1 (de) | Verfahren zum Durchführen einer Eigendiagnose eines Steuergeräts sowie Steuergerät und Kraftfahrzeug |
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 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR LV MK YU |
|
17P | Request for examination filed |
Effective date: 20060405 |
|
AKX | Designation fees paid |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20061005 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20180213 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1015322 Country of ref document: AT Kind code of ref document: T Effective date: 20180715 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602005054205 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20180704 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1015322 Country of ref document: AT Kind code of ref document: T Effective date: 20180704 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20181005 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20181004 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20181104 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PK Free format text: BERICHTIGUNGEN |
|
RIC2 | Information provided on ipc code assigned after grant |
Ipc: G07C 5/00 20060101AFI20050525BHEP |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602005054205 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
26N | No opposition filed |
Effective date: 20190405 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20190303 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190303 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20190331 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190331 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190303 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190331 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190303 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190331 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190331 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20181105 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180704 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20050303 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230518 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240130 Year of fee payment: 20 |