EP2988278B1 - Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device - Google Patents
Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device Download PDFInfo
- Publication number
- EP2988278B1 EP2988278B1 EP14181862.5A EP14181862A EP2988278B1 EP 2988278 B1 EP2988278 B1 EP 2988278B1 EP 14181862 A EP14181862 A EP 14181862A EP 2988278 B1 EP2988278 B1 EP 2988278B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- vehicle
- data
- control unit
- configuration
- communication device
- 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
Images
Classifications
-
- 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/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- 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
- G07C2205/00—Indexing scheme relating to group G07C5/00
- G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool
Definitions
- the invention relates to a method for operating a device for requesting diagnostic data of a vehicle and a configuration system for operating a device for requesting diagnostic data of a vehicle, a communication device and a communication server.
- Today devices for requesting diagnostic data of a vehicle often communicate via a standardized connection with the vehicle, as, for example, defined by ISO15031. However, via such a standardized connection only little data can be requested, as, for example, emission related data.
- US 2009/276115 A1 discloses a method of diagnosing a vehicle having an onboard computer.
- the onboard computer is configured to transmit a vehicle identification number in response to receipt of an identification request. This document discloses the preamble of independent claim 1.
- US 2004/227523 A1 discloses a device for retrieving diagnostic information from a vehicle diagnostic system.
- the device comprises a cellular phone and an adaptor for connecting the cellular phone to the vehicle diagnostic system.
- US 2014/195099 A1 discloses a system for providing vehicle specific diagnostics for a vehicle using a smart phone.
- the system comprises a vehicle decoder, a diagnostic database and a computer readable medium downloadable onto the smart phone.
- US 2013/317694 A1 discloses a method comprising receiving, at a computing device, vehicle information comprising identification information of a vehicle and information describing condition of the vehicle, the method further comprising matching, by the computing device, the vehicle information to content of a vehicle repair database so as to identify repair information relating to the vehicle.
- the object of the invention is to provide a method and a system for operating versatilely a device for requesting diagnostic data of a vehicle and a communication device.
- the invention is distinguished according to a first aspect by a method for operating a device for requesting diagnostic data of a vehicle and a communication device according to claim 1.
- Identification data is requested from the vehicle by the device.
- the identification data is sent to a communication device.
- configuration data for a vehicle or manufacture specific communication is requested from a configuration server depending on the identification data by the communication device.
- the configuration data is sent to the device.
- the configuration data is stored in the device for requesting diagnostic data of the vehicle by use of the configuration data for the vehicle or manufacture specific communication.
- identification data which is requested from the vehicle is not sufficient, additional data for identification can be requested from a web server and/or from the communication device, wherein this additional request may be manually initiated.
- configuration data not only a standardized connection with the vehicle, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication.
- diagnostic data can be requested, as for example, information about a variable service and/or information about a given sensor of the vehicle.
- the identification data comprises a vehicle identification number and the configuration data is requested from the configuration server depending on the vehicle identification number.
- the configuration data for the vehicle or manufacture specific communication is requested from the configuration server depending on a vehicle identification number by requesting control unit detection data from the configuration server depending on the vehicle identification number by the communication device. Further, in response to receiving the control unit detection data by the communication device the control unit detection data is sent to the device. In response to receiving the control unit detection data by the device at least one control unit of the vehicle is identified by use of the control unit detection data and an information about the at least one control unit is sent to the communication device. In response to receiving the information about the at least one control unit by the communication device the configuration data for the vehicle or manufacture specific communication is requested depending on the information about the at least one control unit.
- control unit detection data By use of the control unit detection data it can be very exactly determined which diagnostic data can be requested from the vehicle.
- the diagnostic data of the vehicle in response to receiving a request for requesting diagnostic data by the device is requested by the device by use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data.
- the diagnostic data is sent by the device by use of a given universal protocol to the communication device, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
- the vehicle or manufacture specific communication is often not very efficient.
- a much more efficient communication between the device and the communication device is possible, especially for a wireless communication.
- 200 bytes can be necessary to send given requested diagnostic data, wherein only about 40 bytes are necessary by use of the given universal protocol.
- a start of a cranking phase of the vehicle is determined by the device.
- a transient minimum voltage in the cranking phase is determined by the device.
- the determined transient minimum voltage is compared by the device with a given limit minimum voltage which is given by the configuration data.
- the device can be used for a determination of the battery status.
- the device is, for example, directly connected with a battery supply voltage pin of the vehicle.
- the device is configured to determine a start of a cranking phase of the vehicle
- the invention is distinguished by a configuration system, wherein the configuration system comprises the device, the communication device and the configuration server comprising the configuration data for vehicle or manufacture specific communication, being configured to execute the method according to the first aspect or the advantageous embodiment of the method according to the first aspect.
- Figure 1 shows a network.
- the network comprises a diagnostic system 1.
- the diagnostic system 1 comprises a device 3 for requesting diagnostic data of a vehicle 10 and a communication device 5.
- the device 3 is, for example, built in a dongle.
- the communication device 5 is, for example, built in a smartphone, laptop, PC and/or telematics device.
- the device 3 can, for example, be plugged into an onboard diagnostic, OBD, plug of the vehicle 10 to communicate with control units of the vehicle 10.
- OBD onboard diagnostic
- the device 3 is further configured to communicate with the communication device 5, for example via a wireless communication as, for example, Bluetooth.
- the communication device 5 is configured to communicate with the device 3, for example, via a wireless communication as, for example, Bluetooth.
- the communication device 5 is configured to communicate with a configuration server 30 and/or with a customer server 40, for example, via internet 20.
- the configuration server 30 is configured to communicate with the communication device 5, for example, via internet 20.
- the configuration server 30 is further configured to communicate with a diagnostic database 35.
- Figure 2 shows a diagram of a measured battery voltage, which can be measured by the device 3.
- the device 3 is configured to determine a start of a cranking phase of the vehicle 10.
- the device 3 is further configured to determine a transient minimum voltage V1 in the cranking phase.
- the device 3 is further configured to compare the determined transient minimum voltage V1 with a given limit minimum voltage which is given by a configuration data, which will be later described.
- Dependent on the comparison a battery status to predict pending failure or insufficient capacity to start the vehicle 10 is determined by the device 3 and/or the communication device 5.
- the device 3 can be configured to determine an initial voltage V2 of a sustained cranking period of the cranking phase.
- the device 3 is, for example, further configured to determine an end voltage V3 of the sustained cranking period of the cranking phase.
- the device 3 is, for example, further configured to compare the determined initial voltage V2 and the determined end voltage V3 with a given limit initial voltage and a given limit end voltage which are given by the configuration data. Dependent on the comparisons a battery status to predict pending failure or insufficient capacity to start the vehicle 10 can be determined, for example, by the device 3 and/or the communication device 5.
- Figure 3 shows a first flowchart of a first program for operating the diagnostic system 1 for receiving the configuration data.
- the configuration data are used for a vehicle or manufacture specific communication of the device 3 with the vehicle 10.
- the configuration data are additionally used for the above explained determination of the battery status.
- the first program can be executed distributed on the device 3, the communication device 5 and the configuration server 30.
- a step S1 the program is started and, for example, variables are initialized.
- identification data is requested from the device 3 by the communication device 5.
- the identification data comprises for example a vehicle identification number.
- a step S5 the identification data is requested from the vehicle 10 by the device 3.
- a step S7 the identification data is checked by the device 3. If the identification data is not correct the program is continued in a step S9. If the identification data is correct the program is continued in a step S11.
- step S9 the identification data is requested from the vehicle 10 by use of a user input.
- step S11 the identification data is sent from the communication device 5 to the configuration server 30.
- step S13 the identification data is decoded by the configuration server 30.
- control unit detection data package is created by the configuration server 30 depending on the identification data by use of the diagnostic database 35 and the control unit detection data package is sent to the communication device 5.
- the control unit detection data package can comprise control unit detection data for one control unit or for more than one control unit.
- the control unit detection data package is, for example, encrypted, for example, by use of AES256.
- control unit detection data is send to the device 3 for identifying at least one control unit of the vehicle 10 by use of the control unit detection data.
- step S19 in response to receiving the control unit detection data by the device 3 at least one control unit of the vehicle 10 by use of the control unit detection data is identified and an information about the at least one control unit is sent to the communication device 5.
- control unit detection data package comprises further control unit detection data. If the control unit detection data package comprises further control unit detection data the program is continued in the step S19 and further control unit detection data is sent to the device 3, if not the program is continued in a step S23.
- step S23 it is checked by the communication device 5 if at least one control unit was identified. If at least one control unit was identified the information about the at least one control unit is sent to the configuration server 30 and the program is continued in a step S27, if no control unit was identified the program is continued in a step S25.
- step S25 the program is stopped and can, for example, be restarted in the step S1.
- step S27 configuration data for a vehicle or manufacture specific communication is requested by the communication device 5 from the configuration server 30 depending on the information about the at least one control unit, for example, by use of a web server.
- the web server for example, comprises a token-system for security.
- a step S29 the configuration data is built by the configuration server 30, in particular by the web server and the configuration data is sent to the communication device 5.
- step S31 in response to receiving the configuration data by the communication device 5, the configuration data is sent to the device 3.
- a step S33 the configuration data is stored and/or loaded into the device 3 for requesting diagnostic data of the vehicle 10 by use of the configuration data for the vehicle or manufacture specific communication.
- step S35 the program is stopped and can, for example, be restarted in the step S1.
- Figure 4 shows a second flowchart of a second program for determining a list of diagnostic data which can be requested from the vehicle 10.
- the second program is, for example, started at vehicle logon.
- the second program can be executed distributed on the device 3, the communication device 5 and the configuration server 30.
- a step S40 the program is started, for example, after the first program was stopped and, for example, variables are initialized.
- step S41 a security authentication is done by the communication device 5.
- step S43 a security authentication is done by the device 3.
- a request is sent from the communication device 5 to the device 3 for getting a list of supported diagnostic data which also can be called supported live readings.
- a vehicle or manufacture specific communication is started by the device 3 with control units for which the configuration data was stored.
- a standardized communication with other and/or the same control units is started by the device 3.
- a list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package.
- the list is, for example, separated in a part for diagnostic data which can be requested by a vehicle or manufacture specific communication and diagnostic data which can be requested by a standardized communication, as, for example, defined by ISO15031.
- the diagnostic data which can be requested by a standardized communication can also be called Level 1 diagnostics.
- the diagnostic data which can be requested by a vehicle or manufacture specific communication can also be called Level 2 diagnostics.
- a step S49 the list is sent to the communication device 5.
- a step S51 the list is, for example, displayed and or logged by the communication device 5 and the program is stopped.
- An example list is shown in the table 1.
- Table 1 list of all supported live readings Live reading Level 2 supported Level 1 supported Engine Speed YES control unit 1 YES Vehicle Speed YES control unit 1 YES Coolant Temp YES control unit 1 YES Intake Air Temperature YES control unit 1 YES Mass Air Flow NO NO NO Absolute Throttle Position NO NO NO Odometer YES control unit 3 N/A Brake Pedal YES control unit 2 N/A Fuel Level NO NO Distance till service YES control unit 3 N/A
- FIG. 5 shows a simplified flowchart of the second program.
- a step S60 the request is sent from the communication device 5 to the device 3 for getting the list of supported live readings.
- a step S61 the list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package.
- a step S63 the list is sent to the communication device 5.
- a step S65 the list is stored in the communication device 5 and the program is stopped.
- Figure 6 shows a flowchart of a third program to get diagnostic data.
- a step S100 the program is started and, for example, variables are initialized.
- a request for requesting diagnostic data is sent by the communication device 5 to the device 3.
- a step S103 the list of all supported live readings is provided by the device 3 which was built for example in the step S61 and/or S47.
- a step S105 it is checked by the device 3 if the requested diagnostic data is supported by use of the list. If the requested diagnostic data is not supported the program is continued in a step S160. If the requested diagnostic data is supported the program is continued in a step S107.
- a step S107 it is checked by the device 3 if the configuration data is needed or if the requested diagnostic data can be requested by use of a given standardized protocol. If the configuration data is needed the program is continued in a step S120. If the configuration data is not needed the program is continued in a step S109.
- a step S109 the diagnostic data is requested by the device 3 from the vehicle 10 by use of a given standardized protocol.
- a step S111 the request for diagnostic data is received by the vehicle 10.
- a step S113 the diagnostic data is sent back to the device 3 from the vehicle 10.
- a step S115 the diagnostic data is received by the device 3 and the diagnostic data is decoded and the program is continued in a step S150.
- step S120 the required configuration data is loaded for a vehicle or manufacture specific communication, in particular, for the use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data.
- a wakeup/start command is sent by the device 3 to the control unit from which the diagnostic data is requested.
- a wakeup sequence is started in the control unit.
- a step S127 the wakeup sequence is finished in the control unit.
- a diagnostic data request for the requested diagnostic data is loaded by the device 3 by use of the configuration data.
- a step S131 the diagnostic data request is sent by the device 3 to the control unit.
- step S133 the control unit receives the diagnostic data request.
- step S135 the requested diagnostic data is sent by the control unit to the device 3.
- a request is sent by the device 3 for stopping the communication with the control unit to the control unit.
- a step S139 the communication is stopped by the control unit.
- a stop acknowledgment is sent by the control unit to the device 3 and the program is continued in the step S150.
- step S150 the diagnostic data is stored by the device 3.
- a step S160 it is checked by the device 3 if further diagnostic data is requested. If further diagnostic data is requested the program is continued in the step S103. If no further diagnostic data is requested the program is continued in a step S161.
- the diagnostic data is sent by the device 3 to the communication device 5, in particular by use of a given universal protocol, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
- a step S163 the diagnostic data is displayed by the communication device 5 and/or stored in the communication device 5.
- a step S170 it is checked by the device 3 if the diagnostic data is to be requested again, for example, in a given interval. If the diagnostic data is to be requested again, the program is continued in the step S103. If the diagnostic data is not to be requested again, the program is continued in a step S173.
- step S173 the program is stopped and can, for example, be restarted in the step S1.
- the configuration data not only a standardized connection with the vehicle 10, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication.
- many different diagnostic data can be requested, as, for example, information about a variable service and/or information about a given sensor of the vehicle 10. Further, the battery status can be determined.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Small-Scale Networks (AREA)
Description
- The invention relates to a method for operating a device for requesting diagnostic data of a vehicle and a configuration system for operating a device for requesting diagnostic data of a vehicle, a communication device and a communication server.
- Today devices for requesting diagnostic data of a vehicle often communicate via a standardized connection with the vehicle, as, for example, defined by ISO15031. However, via such a standardized connection only little data can be requested, as, for example, emission related data.
-
US 2009/276115 A1 discloses a method of diagnosing a vehicle having an onboard computer. The onboard computer is configured to transmit a vehicle identification number in response to receipt of an identification request. This document discloses the preamble ofindependent claim 1. -
US 2004/227523 A1 discloses a device for retrieving diagnostic information from a vehicle diagnostic system. The device comprises a cellular phone and an adaptor for connecting the cellular phone to the vehicle diagnostic system. -
US 2014/195099 A1 discloses a system for providing vehicle specific diagnostics for a vehicle using a smart phone. The system comprises a vehicle decoder, a diagnostic database and a computer readable medium downloadable onto the smart phone. -
US 2013/317694 A1 discloses a method comprising receiving, at a computing device, vehicle information comprising identification information of a vehicle and information describing condition of the vehicle, the method further comprising matching, by the computing device, the vehicle information to content of a vehicle repair database so as to identify repair information relating to the vehicle. - The object of the invention is to provide a method and a system for operating versatilely a device for requesting diagnostic data of a vehicle and a communication device.
- This object is achieved by the features of the independent claims. An advantageous embodiment of the invention is given in the sub-claim.
- The invention is distinguished according to a first aspect by a method for operating a device for requesting diagnostic data of a vehicle and a communication device according to
claim 1. - Identification data is requested from the vehicle by the device. In response to receiving the identification data from the vehicle, the identification data is sent to a communication device. In response to receiving the identification data by the communication device configuration data for a vehicle or manufacture specific communication is requested from a configuration server depending on the identification data by the communication device. In response to receiving the configuration data by the communication device, the configuration data is sent to the device. In response to receiving the configuration data by the device, the configuration data is stored in the device for requesting diagnostic data of the vehicle by use of the configuration data for the vehicle or manufacture specific communication.
- If the identification data which is requested from the vehicle is not sufficient, additional data for identification can be requested from a web server and/or from the communication device, wherein this additional request may be manually initiated.
- By storing the configuration data not only a standardized connection with the vehicle, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication. Thus, many different diagnostic data can be requested, as for example, information about a variable service and/or information about a given sensor of the vehicle.
- The identification data comprises a vehicle identification number and the configuration data is requested from the configuration server depending on the vehicle identification number.
- By use of the vehicle identification number a very easy determination of the configuration data is possible.
- The configuration data for the vehicle or manufacture specific communication is requested from the configuration server depending on a vehicle identification number by requesting control unit detection data from the configuration server depending on the vehicle identification number by the communication device. Further, in response to receiving the control unit detection data by the communication device the control unit detection data is sent to the device. In response to receiving the control unit detection data by the device at least one control unit of the vehicle is identified by use of the control unit detection data and an information about the at least one control unit is sent to the communication device. In response to receiving the information about the at least one control unit by the communication device the configuration data for the vehicle or manufacture specific communication is requested depending on the information about the at least one control unit.
- By use of the control unit detection data it can be very exactly determined which diagnostic data can be requested from the vehicle.
- According to an embodiment, in response to receiving a request for requesting diagnostic data by the device the diagnostic data of the vehicle is requested by the device by use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data. In response to receiving the diagnostic data by the device the diagnostic data is sent by the device by use of a given universal protocol to the communication device, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
- The vehicle or manufacture specific communication is often not very efficient. By the given universal protocol a much more efficient communication between the device and the communication device is possible, especially for a wireless communication. For example, for the vehicle or manufacture specific communication above 200 bytes can be necessary to send given requested diagnostic data, wherein only about 40 bytes are necessary by use of the given universal protocol.
- According to the invention, a start of a cranking phase of the vehicle is determined by the device. A transient minimum voltage in the cranking phase is determined by the device. The determined transient minimum voltage is compared by the device with a given limit minimum voltage which is given by the configuration data.
- Normally a determination of a battery status by use of control units is not possible because of the low sampling rate of the control units, but the device can be used for a determination of the battery status. For these measurements the device is, for example, directly connected with a battery supply voltage pin of the vehicle.
- According to the invention, the device is configured to determine a start of a cranking phase of the vehicle,
- the device is further configured to determine a transient minimum voltage in the cranking phase,
- the device is further configured to compare the determined transient minimum voltage with a given limit minimum voltage which is given by the configuration data, wherein dependent on the comparison the battery status to predict pending failure or insufficient capacity to start the vehicle is determined by the device and/or the communication device.
- Hereby a very exact determination of the battery status is possible.
- According to a further aspect the invention is distinguished by a configuration system, wherein the configuration system comprises the device, the communication device and the configuration server comprising the configuration data for vehicle or manufacture specific communication, being configured to execute the method according to the first aspect or the advantageous embodiment of the method according to the first aspect.
- Exemplary embodiments of the invention are explained in the following with the aid of schematic drawings.
- These are as follows:
-
Figure 1 a network comprising a diagnostic system; -
Figure 2 a diagram of a battery voltage; -
Figure 3 a first flowchart for operating the diagnostic system; -
Figure 4 a second flowchart for operating the diagnostic system, which does not form part of the invention; -
Figure 5 a third flowchart for operating the diagnostic system, which does not form part of the invention; and -
Figure 6 a fourth flowchart for operating the diagnostic system, which does not form part of the invention. -
Figure 1 shows a network. The network comprises adiagnostic system 1. Thediagnostic system 1 comprises a device 3 for requesting diagnostic data of avehicle 10 and a communication device 5. The device 3 is, for example, built in a dongle. The communication device 5 is, for example, built in a smartphone, laptop, PC and/or telematics device. - The device 3 can, for example, be plugged into an onboard diagnostic, OBD, plug of the
vehicle 10 to communicate with control units of thevehicle 10. - The device 3 is further configured to communicate with the communication device 5, for example via a wireless communication as, for example, Bluetooth.
- The communication device 5 is configured to communicate with the device 3, for example, via a wireless communication as, for example, Bluetooth. The communication device 5 is configured to communicate with a
configuration server 30 and/or with acustomer server 40, for example, viainternet 20. - The
configuration server 30 is configured to communicate with the communication device 5, for example, viainternet 20. Theconfiguration server 30 is further configured to communicate with adiagnostic database 35. -
Figure 2 shows a diagram of a measured battery voltage, which can be measured by the device 3. For this, the device 3 is configured to determine a start of a cranking phase of thevehicle 10. The device 3 is further configured to determine a transient minimum voltage V1 in the cranking phase. The device 3 is further configured to compare the determined transient minimum voltage V1 with a given limit minimum voltage which is given by a configuration data, which will be later described. Dependent on the comparison a battery status to predict pending failure or insufficient capacity to start thevehicle 10 is determined by the device 3 and/or the communication device 5. - Additionally the device 3 can be configured to determine an initial voltage V2 of a sustained cranking period of the cranking phase. The device 3 is, for example, further configured to determine an end voltage V3 of the sustained cranking period of the cranking phase. The device 3 is, for example, further configured to compare the determined initial voltage V2 and the determined end voltage V3 with a given limit initial voltage and a given limit end voltage which are given by the configuration data. Dependent on the comparisons a battery status to predict pending failure or insufficient capacity to start the
vehicle 10 can be determined, for example, by the device 3 and/or the communication device 5. -
Figure 3 shows a first flowchart of a first program for operating thediagnostic system 1 for receiving the configuration data. The configuration data are used for a vehicle or manufacture specific communication of the device 3 with thevehicle 10. The configuration data are additionally used for the above explained determination of the battery status. - The first program can be executed distributed on the device 3, the communication device 5 and the
configuration server 30. - In a step S1 the program is started and, for example, variables are initialized.
- In a step S3 identification data is requested from the device 3 by the communication device 5. The identification data comprises for example a vehicle identification number.
- In a step S5 the identification data is requested from the
vehicle 10 by the device 3. - In a step S7 the identification data is checked by the device 3. If the identification data is not correct the program is continued in a step S9. If the identification data is correct the program is continued in a step S11.
- In the step S9 the identification data is requested from the
vehicle 10 by use of a user input. - In the step S11 the identification data is sent from the communication device 5 to the
configuration server 30. - In the step S13 the identification data is decoded by the
configuration server 30. - In the step S15 a control unit detection data package is created by the
configuration server 30 depending on the identification data by use of thediagnostic database 35 and the control unit detection data package is sent to the communication device 5. The control unit detection data package can comprise control unit detection data for one control unit or for more than one control unit. The control unit detection data package is, for example, encrypted, for example, by use of AES256. - In the step S17 in response to receiving the control unit detection data package by the communication device 5 control unit detection data is send to the device 3 for identifying at least one control unit of the
vehicle 10 by use of the control unit detection data. - In the step S19 in response to receiving the control unit detection data by the device 3 at least one control unit of the
vehicle 10 by use of the control unit detection data is identified and an information about the at least one control unit is sent to the communication device 5. - In the step S21 it is checked by the communication device 5 control unit detection data package comprises further control unit detection data. If the control unit detection data package comprises further control unit detection data the program is continued in the step S19 and further control unit detection data is sent to the device 3, if not the program is continued in a step S23.
- In the step S23 it is checked by the communication device 5 if at least one control unit was identified. If at least one control unit was identified the information about the at least one control unit is sent to the
configuration server 30 and the program is continued in a step S27, if no control unit was identified the program is continued in a step S25. - In the step S25 the program is stopped and can, for example, be restarted in the step S1.
- In the step S27 configuration data for a vehicle or manufacture specific communication is requested by the communication device 5 from the
configuration server 30 depending on the information about the at least one control unit, for example, by use of a web server. The web server, for example, comprises a token-system for security. - In a step S29 the configuration data is built by the
configuration server 30, in particular by the web server and the configuration data is sent to the communication device 5. - In a step S31 in response to receiving the configuration data by the communication device 5, the configuration data is sent to the device 3.
- In a step S33 the configuration data is stored and/or loaded into the device 3 for requesting diagnostic data of the
vehicle 10 by use of the configuration data for the vehicle or manufacture specific communication. - In the step S35 the program is stopped and can, for example, be restarted in the step S1.
-
Figure 4 shows a second flowchart of a second program for determining a list of diagnostic data which can be requested from thevehicle 10. The second program is, for example, started at vehicle logon. - The second program can be executed distributed on the device 3, the communication device 5 and the
configuration server 30. - In a step S40 the program is started, for example, after the first program was stopped and, for example, variables are initialized.
- In an optional step S41 a security authentication is done by the communication device 5.
- In an optional step S43 a security authentication is done by the device 3.
- In a step S44 a request is sent from the communication device 5 to the device 3 for getting a list of supported diagnostic data which also can be called supported live readings.
- In a step S45 a vehicle or manufacture specific communication is started by the device 3 with control units for which the configuration data was stored. Optionally a standardized communication with other and/or the same control units is started by the device 3.
- In a step S47 a list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package. The list is, for example, separated in a part for diagnostic data which can be requested by a vehicle or manufacture specific communication and diagnostic data which can be requested by a standardized communication, as, for example, defined by ISO15031. The diagnostic data which can be requested by a standardized communication can also be called
Level 1 diagnostics. The diagnostic data which can be requested by a vehicle or manufacture specific communication can also be called Level 2 diagnostics. - In a step S49 the list is sent to the communication device 5.
- In a step S51 the list is, for example, displayed and or logged by the communication device 5 and the program is stopped. An example list is shown in the table 1.
Table 1: list of all supported live readings Live reading Level 2 supported Level 1 supportedEngine Speed YES control unit 1YES Vehicle Speed YES control unit 1YES Coolant Temp YES control unit 1YES Intake Air Temperature YES control unit 1YES Mass Air Flow NO NO Absolute Throttle Position NO NO Odometer YES control unit 3 N/A Brake Pedal YES control unit 2 N/A Fuel Level NO NO Distance till service YES control unit 3 N/A -
Figure 5 shows a simplified flowchart of the second program. - In a step S60 the request is sent from the communication device 5 to the device 3 for getting the list of supported live readings.
- In a step S61 the list of all supported live readings is built by the device 3, for example, by interrogating all control units and attempting all live data commands which are given to the device 3 by a diagnostic package.
- In a step S63 the list is sent to the communication device 5.
- In a step S65 the list is stored in the communication device 5 and the program is stopped.
-
Figure 6 shows a flowchart of a third program to get diagnostic data. - In a step S100 the program is started and, for example, variables are initialized.
- In a step S101 a request for requesting diagnostic data is sent by the communication device 5 to the device 3.
- In a step S103 the list of all supported live readings is provided by the device 3 which was built for example in the step S61 and/or S47.
- In a step S105 it is checked by the device 3 if the requested diagnostic data is supported by use of the list. If the requested diagnostic data is not supported the program is continued in a step S160. If the requested diagnostic data is supported the program is continued in a step S107.
- In a step S107 it is checked by the device 3 if the configuration data is needed or if the requested diagnostic data can be requested by use of a given standardized protocol. If the configuration data is needed the program is continued in a step S120. If the configuration data is not needed the program is continued in a step S109.
- In a step S109 the diagnostic data is requested by the device 3 from the
vehicle 10 by use of a given standardized protocol. - In a step S111 the request for diagnostic data is received by the
vehicle 10. - In a step S113 the diagnostic data is sent back to the device 3 from the
vehicle 10. - In a step S115 the diagnostic data is received by the device 3 and the diagnostic data is decoded and the program is continued in a step S150.
- In the step S120 the required configuration data is loaded for a vehicle or manufacture specific communication, in particular, for the use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data.
- In a step S123 a wakeup/start command is sent by the device 3 to the control unit from which the diagnostic data is requested.
- In a step S125 a wakeup sequence is started in the control unit.
- In a step S127 the wakeup sequence is finished in the control unit.
- In a step S129 a diagnostic data request for the requested diagnostic data is loaded by the device 3 by use of the configuration data.
- In a step S131 the diagnostic data request is sent by the device 3 to the control unit.
- In a step S133 the control unit receives the diagnostic data request.
- In a step S135 the requested diagnostic data is sent by the control unit to the device 3.
- In a step S137 a request is sent by the device 3 for stopping the communication with the control unit to the control unit.
- In a step S139 the communication is stopped by the control unit.
- In a step S141 a stop acknowledgment is sent by the control unit to the device 3 and the program is continued in the step S150.
- In the step S150 the diagnostic data is stored by the device 3.
- In a step S160 it is checked by the device 3 if further diagnostic data is requested. If further diagnostic data is requested the program is continued in the step S103. If no further diagnostic data is requested the program is continued in a step S161.
- In the step S161 the diagnostic data is sent by the device 3 to the communication device 5, in particular by use of a given universal protocol, wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
- In a step S163 the diagnostic data is displayed by the communication device 5 and/or stored in the communication device 5.
- In a step S170 it is checked by the device 3 if the diagnostic data is to be requested again, for example, in a given interval. If the diagnostic data is to be requested again, the program is continued in the step S103. If the diagnostic data is not to be requested again, the program is continued in a step S173.
- In the step S173 the program is stopped and can, for example, be restarted in the step S1.
- By storing the configuration data not only a standardized connection with the
vehicle 10, as, for example, defined by ISO15031, is possible, but also a non-standardized vehicle or manufacture specific communication. Thus, many different diagnostic data can be requested, as, for example, information about a variable service and/or information about a given sensor of thevehicle 10. Further, the battery status can be determined.
Claims (3)
- Method for operating a device (3) for requesting diagnostic data of a vehicle (10) and a communication device (5), wherein- identification data is requested from the vehicle (10) by the device (3),- in response to receiving the identification data from the vehicle (10), the identification data is sent to the communication device (5),- in response to receiving the identification data by the communication device (5), configuration data for a vehicle or manufacture specific communication is requested from a configuration server (30) depending on the identification data by the communication device (5),- in response to receiving the configuration data by the communication device (5), the configuration data is sent to the device (3),- in response to receiving the configuration data by the device (3), the configuration data is stored in the device (3) for requesting diagnostic data of the vehicle (10) by use of the configuration data for the vehicle or manufacture specific communication,wherein the identification data comprises a vehicle identification number and the configuration data is requested from the configuration server (30) depending on the vehicle identification number, characterized in thatthe configuration data for the vehicle or manufacture specific communication is requested from the configuration server (30) depending on the vehicle identification number by- requesting control unit detection data from the configuration server (30) depending on the vehicle identification number by the communication device (5),- in response to receiving the control unit detection data by the communication device (5) sending the control unit detection data to the device (3),- in response to receiving the control unit detection data by the device (3) identifying at least one control unit of the vehicle (10) by use of the control unit detection data and sending an information about the at least one control unit to the communication device (5),- in response to receiving the information about the at least one control unit by the communication device (5) requesting the configuration data for the vehicle or manufacture specific communication depending on the information about the at least one control unit andwherein the configuration data is used for determination of a battery status, wherein- the device (3) is configured to determine a start of a cranking phase of the vehicle (10),- the device (3) is further configured to determine a transient minimum voltage (V1) in the cranking phase,- the device (3) is further configured to compare the determined transient minimum voltage (V1) with a given limit minimum voltage which is given by the configuration data,wherein dependent on the comparison the battery status to predict pending failure or insufficient capacity to start the vehicle (10) is determined by the device (3) and/or the communication device (5).
- Method according to claim 1, wherein- in response to receiving a request for requesting diagnostic data by the device (3) the diagnostic data of the vehicle (10) is requested by the device (3) by use of a given protocol for the vehicle or manufacture specific communication which is given by the configuration data and- in response to receiving the diagnostic data by the device (3) the diagnostic data is sent by the device (3) by use of a given universal protocol to the communication device (5), wherein the given universal protocol is different from the protocol for the vehicle or manufacture specific communication.
- Configuration system, wherein the configuration system comprises a device (3), a communication device (5) and a configuration server (30) comprising configuration data for a vehicle or manufacture specific communication, being configured to execute the method according to anyone of the claims 1 or 2.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14181862.5A EP2988278B1 (en) | 2014-08-21 | 2014-08-21 | Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device |
ES14181862T ES3010671T3 (en) | 2014-08-21 | 2014-08-21 | Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14181862.5A EP2988278B1 (en) | 2014-08-21 | 2014-08-21 | Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2988278A1 EP2988278A1 (en) | 2016-02-24 |
EP2988278B1 true EP2988278B1 (en) | 2024-11-20 |
Family
ID=51454543
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP14181862.5A Active EP2988278B1 (en) | 2014-08-21 | 2014-08-21 | Method, diagnostic system and configuration system for operating a device for requesting diagnostic data of a vehicle and a communication device |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP2988278B1 (en) |
ES (1) | ES3010671T3 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11024102B2 (en) * | 2018-05-10 | 2021-06-01 | Mahle International Gmbh | Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling |
FR3159942A1 (en) * | 2024-03-05 | 2025-09-12 | Stellantis Auto Sas | Method and system for communicating vehicle diagnostic data |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7209813B2 (en) * | 2003-05-13 | 2007-04-24 | Spx Corporation | Cellular phone configured with off-board device capabilities and starter/charger and battery testing capabilities |
US9117319B2 (en) * | 2005-06-30 | 2015-08-25 | Innova Electronics, Inc. | Handheld automotive diagnostic tool with VIN decoder and communication system |
US8977423B2 (en) * | 2012-05-23 | 2015-03-10 | Snap-On Incorporated | Methods and systems for providing vehicle repair information |
US8825271B2 (en) * | 2013-01-04 | 2014-09-02 | Innova Electronics, Inc. | Smart phone app-based VIN decoding and symptomatic diagnostic system and method |
-
2014
- 2014-08-21 ES ES14181862T patent/ES3010671T3/en active Active
- 2014-08-21 EP EP14181862.5A patent/EP2988278B1/en active Active
Also Published As
Publication number | Publication date |
---|---|
EP2988278A1 (en) | 2016-02-24 |
ES3010671T3 (en) | 2025-04-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107660335B (en) | Centralized management of mobility-assisted motor vehicle software upgrades and vehicle data analysis | |
CN110471393B (en) | Devices, systems and methods for remotely capturing automotive diagnostic information, monitoring and control | |
CN107547327B (en) | Method and system for protecting vehicle | |
US20140365064A1 (en) | Method and system for database compilation on a remote electronic device | |
CN1661352B (en) | Operator end system and pattern file recognition method | |
US10567550B2 (en) | Method for operating a server | |
US20150094929A1 (en) | Vehicle diagnostic and prognostic systems and methods | |
US10120030B2 (en) | Trace data recording system, trace data recording server, trace data recording method, and information storage medium | |
US20150094903A1 (en) | Vehicle diagnostic and prognostic systems and methods | |
US20140325602A1 (en) | Accessing system for vehicle network and method of controlling the same | |
JP2010064654A (en) | Repair replacement information management system of vehicle, and abnormality cause information management system of vehicle | |
CN104995044A (en) | Methods, systems and tools for programming tire pressure monitoring sensors | |
US20180081671A1 (en) | Program rewriting device and program rewriting method | |
CN103112324A (en) | Universal tire pressure monitoring sensor | |
CN114175598B (en) | Sensor device for transmitting sensor parameter settings | |
JP2018517603A5 (en) | ||
JP2017510504A (en) | Method for configuring tire pressure sensor | |
US20150088370A1 (en) | Systems and methods for identification of a compromised module | |
US20180018833A1 (en) | Vehicle Database Storage And Retrieval Methods And Systems | |
US20140316639A1 (en) | Data conversion apparatus and method of using a cell phone to update fault code data and maintain vehicles using on-board diagnostic systems | |
US8798854B2 (en) | Data recorder | |
KR101306149B1 (en) | Driving car information device with EDR and vehicle diagnosis function and, Method for data processing the same | |
CN105209310A (en) | Diagnostic tools with multiple operating systems | |
CN111176695A (en) | Vehicle ECU configuration method, server and terminal | |
KR20120019870A (en) | Software upgrade apparatus and method for a vehicle controller |
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): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
17P | Request for examination filed |
Effective date: 20160824 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: CONTINENTAL AUTOMOTIVE GMBH |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20200828 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH |
|
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 |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
INTG | Intention to grant announced |
Effective date: 20240618 |
|
INTC | Intention to grant announced (deleted) | ||
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: 20240802 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Free format text: CASE NUMBER: APP_48656/2024 Effective date: 20240826 |
|
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): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM 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: DE Ref legal event code: R096 Ref document number: 602014091193 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 3010671 Country of ref document: ES Kind code of ref document: T3 Effective date: 20250404 |
|
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: 20250320 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: 20250320 Ref country code: HR 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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20241120 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1744298 Country of ref document: AT Kind code of ref document: T Effective date: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO 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: 20250220 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20250221 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: 20241120 Ref country code: LV 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: 20241120 |
|
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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS 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: 20250220 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM 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: 20241120 |
|
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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20241120 |
|
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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20241120 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20241120 |