EP2718908B1 - Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule - Google Patents
Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule Download PDFInfo
- Publication number
- EP2718908B1 EP2718908B1 EP12722395.6A EP12722395A EP2718908B1 EP 2718908 B1 EP2718908 B1 EP 2718908B1 EP 12722395 A EP12722395 A EP 12722395A EP 2718908 B1 EP2718908 B1 EP 2718908B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- vehicle
- mobile communication
- communication interface
- workshop
- tester
- 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
- 238000010295 mobile communication Methods 0.000 title claims description 66
- 238000000034 method Methods 0.000 title claims description 19
- 238000012360 testing method Methods 0.000 claims description 142
- 238000004891 communication Methods 0.000 claims description 76
- 238000003860 storage Methods 0.000 claims description 12
- 238000003745 diagnosis Methods 0.000 claims description 10
- 238000013500 data storage Methods 0.000 description 27
- 230000008439 repair process Effects 0.000 description 13
- 238000007689 inspection Methods 0.000 description 12
- 238000012423 maintenance Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 238000011161 development Methods 0.000 description 6
- 230000018109 developmental process Effects 0.000 description 6
- 238000005259 measurement Methods 0.000 description 6
- 238000010998 test method Methods 0.000 description 5
- 230000001502 supplementing effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 238000011144 upstream manufacturing Methods 0.000 description 3
- 238000004378 air conditioning Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000002950 deficient Effects 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000004886 process control Methods 0.000 description 2
- 208000024891 symptom Diseases 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 239000006096 absorbing agent Substances 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion 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
- 238000011156 evaluation Methods 0.000 description 1
- 239000012530 fluid Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 230000035939 shock Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000013022 venting Methods 0.000 description 1
- 238000005303 weighing Methods 0.000 description 1
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
- 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/0841—Registering performance data
- G07C5/085—Registering performance data using electronic data carriers
Definitions
- the invention relates to a mobile communication interface, a system with a mobile communication interface and a method for identifying, diagnosing, maintaining and repairing a vehicle via a mobile communication interface, in particular in a motor vehicle workshop.
- the publication DE 44 46 512 A1 discloses a device for performing a vehicle test with a mobile radio part, which transmits diagnostic data from a vehicle to a workshop.
- the publication DE 199 21 846 A1 discloses a diagnostic tester with a portable automotive tester.
- vehicle testers used for this purpose are highly specialized and adapted to the corresponding vehicle components.
- vehicle testers are used at specific workstations in a workshop or testing center, for example because the vehicle testers are permanently installed in the workshop.
- a vehicle which is located in the workshop for fault diagnosis and / or repair is moved from workstation to workstation, depending on the test or repair to be performed.
- the electronic control units In today's motor vehicles many functions are performed by electronic control units that are connected to the vehicle electronics.
- the electronic control units often also take onboard diagnostic functions of the vehicle systems and store special diagnostic and / or operating status data. So that the data of the diagnostic functions are evaluated from the control units can, universal diagnostic tester have been developed, which allow communication with the in-vehicle control units.
- the functionality of the communication can be very different and relates, for example, to the reading out of stored error codes, the transmission of actual values, the execution of complex actuator tests, the resetting of the service intervals, the training of built-in spare parts and similar tasks.
- Diagnostic testers usually include an assembly that is responsible for communication with the vehicle.
- This module is usually referred to as a vehicle communication interface or, as is customary internationally, as a vehicle communication interface, abbreviated to VCI.
- VCI vehicle communication interface
- Such VCI can also be arranged in a separate housing, and wired or wirelessly communicate with universal control and display devices such as laptops, PDAs or smartphones.
- the diagnostic functionality of universal diagnostic tester or operating and display devices is ensured via a corresponding diagnostic software, which allows the operation, display, diagnostic sequence control and communication with the electronic control units via the VCI.
- Fig. 6 shows a vehicle 61 in a workshop.
- the vehicle 61 in this case comprises one or more electronic control units 62, which are installed in the vehicle 61.
- the vehicle 61 is moved to different workstations 65a, 65b and 65c, which may be spatially separated.
- workstations 65a, 65b, 65c there is a specific vehicle test device or universal operating and display device 64a, 64b, 64c assigned to the respective workstation.
- the specific vehicle testers 64a, 64b, 64c may be connected to components of the vehicle 61, such as the exhaust, the engine, the air conditioner, or other components for testing purposes.
- each workstation has a respective workstation 65a, 65b, 65c associated universal diagnostic tester 63, with which the communication with the electronic control units 62 of the vehicle 61 is established via a standardized vehicle interface, not shown.
- the workshop only has a universal diagnostic tester 63, which is then passed on from work to work if necessary.
- Fig. 7 shows a different approach: A vehicle 71 with one or more installed electronic control units 72 passes through the workstations 75a, 75b, 75c in a workshop. At workplaces 75a, 75b, 75c there is a specific vehicle test device 74a, 74b, 74c. Each of the specific vehicle test devices 74a, 74b, 74c respectively comprises an integrated VCI 73a, 73b, 73c, by means of which a communication with the electronic control devices 72 in the vehicle 71 is established via a standardized vehicle interface (not illustrated). This eliminates the need to operate a separate universal diagnostic tester in parallel with the vehicle tester as in Fig.
- FIG. 8 shows an improved vehicle inspection equipment in a workshop.
- a vehicle 10 in particular a motor vehicle, comprises one or more electronic control units 10a.
- the electronic control unit (s) 10a may include specific vehicle specific component control units or universal electronic control units 10a of the vehicle 10.
- the electronic control units 10a can, via a standardized vehicle interface, not shown, provide diagnostic data, Have error data, actual values, operating state data or similar vehicle-related data available for specific vehicle components and be put into specific operating states or processes.
- the electronic control unit or units 10a are connected to a VCI 1 via a standardized vehicle interface (not shown).
- the VCI 1 can be connected to the vehicle 10 at the beginning of a workshop run, for example in the vehicle acceptance.
- the VCI 1 may be configured to store unique identification data of the vehicle 10, such as vehicle owner, registration number, vehicle brand, vehicle make, chassis number or similar identification data.
- the unique identification data can be reentered in the vehicle acceptance of the workshop by means of a universal control and display device or taken from a previous workshop visit from a central workshop database.
- the VCI 1 is configured to be carried with the vehicle 10 in the workshop when the vehicle 10 passes through the workstations 42, 43, 44.
- each specific vehicle test equipment or universal control and display devices 3a, 3b, 3c which are equipped with a single diagnostic server device 2.
- the diagnostic server device 2 is in each case designed to establish communication with the VCI 1 and thus with the electronic control unit or devices 10 a of the vehicle 10.
- the specific vehicle testing devices 3 a, 3 b, 3 c can be connected to respective vehicle components of the vehicle 10 at each workstation for performing the diagnostic and / or repair work on the vehicle 10.
- the identification of a vehicle which is required for a variety of operations in a workshop or testing center, is performed only once at the beginning of the workshop run or the fürcertainen presslaufs.
- the unique identification data is stored in a VCI connected to the vehicle and carried along with the vehicle from workstation to workstation in the workshop. For this purpose, the VCI remains in the respective vehicle until the end of the workshop run.
- the invention is based on the idea of using the VCI, which in any case is carried along with the vehicle in the workshop, as a temporary data memory for the customer order, diagnosis, maintenance and repair results or respectively associated data and parameters of the respective vehicle.
- VCI which in any case is carried along with the vehicle in the workshop
- the VCI is a temporary data memory for the customer order, diagnosis, maintenance and repair results or respectively associated data and parameters of the respective vehicle.
- the customer order agreed with the customer is added to the central customer database and then all now available in the customer database for the vehicle in question stored in the VCI, which is installed in the vehicle in question for the duration of the workshop stay or is already installed there.
- existing vehicle test devices and / or universal operating and display devices can initiate communication with the VCI of the vehicle located at the workstation, retrieve the unique identification data of the vehicle, the customer order and already existing diagnostic results of temporally upstream work steps and, for example, diagnostic information replace with the vehicle control units.
- all results, data and parameters generated at the respective workstation can be stored in the VCI vehicle-specific. This saves the respective user ofajiprüfêts and / or the universal control and display both the installation and removal of the VCI and the times for a complex identification of the vehicle and for establishing communication with the built-in control units in the vehicle and the backup of Workplace-related data at a central location such as a shop server. In this way, the efficiency of work processes, especially in smaller workshops without its own workshop network can be significantly increased.
- the present invention thus provides a method for identifying, diagnosing, maintaining, and repairing a vehicle in a workshop comprising the steps of: storing customer, vehicle, and shop order data for the vehicle from a central customer database into a working data storage device of a mobile communication interface; Connecting the mobile communication interface to the vehicle and connecting a first vehicle test device at least to the mobile communication interface at a first workstation; Reading out the customer, vehicle and workshop order data from the working data storage device of the mobile communication interface into the control computer of the first vehicle testing device; Performing first tests on the vehicle with the first vehicle test device and / or the mobile communication interface; Storing first test results in the working data storage device of the mobile communication interface by the first vehicle inspection device; Disconnecting the first vehicle inspection device from the vehicle; Connecting a second vehicle tester to the vehicle and reading the Customer, vehicle and workshop order data and the first test results from the working data storage device of the mobile communication interface in the second vehicle test device at a second workstation; Performing second tests on the vehicle with the second vehicle test apparatus and / or the mobile
- the present invention provides a mobile communication interface for identifying a vehicle and communicating with the in-vehicle electronic control units in a workshop having a connection device configured to connect a vehicle in a workshop to the mobile communication interface; a communication device configured to receive customer, vehicle, and shop order data from a central customer database, a work data storage device configured to store the received customer, vehicle, and shop order data to the vehicle, the communication device further is configured to transmit the customer, vehicle and workshop order data read from the working data storage device to a first vehicle test device and to receive first test results from the first vehicle test device, wherein the work data storage device is further configured to store the received first test results, wherein the communication device is further developed to transmit the customer, vehicle and workshop order data read from the work data storage device and the first test results to a second vehicle test device and from the second vehicle test device to receive second test results, wherein the working data storage device is adapted to store the second test results and wherein the communication device is further adapted to transfer the read customer, vehicle and workshop order data and the first and
- the present invention provides a system for identifying, diagnosing, maintaining and repairing a vehicle in a workshop, having a mobile communication interface according to the invention, a plurality of vehicle testing devices, each having a diagnostic server device for establishing communication with the mobile communication interface and by means of the mobile communication interface with electronic control units installed in the vehicle; an operating and display device for controlling the vehicle inspection device and the mobile communication interface; and different vehicle test modules configured to perform tester specific vehicle tests on the vehicle based on the test, diagnostic, and / or maintenance results data.
- Vehicle testing devices in the sense of this application are not specified on special vehicle testing devices. They may include, for example, wheel alignment testers, engine testers, emissions testers, brake testers, shock absorber testers, lane checkers, weighing devices, brake fluid testing devices, sound level meters, diesel smoke tester, chassis gauges, toe angle testers, steering angle testers, air conditioning testers, and the like. These vehicle testing devices can be used in workshops, in particular motor vehicle workshops, testing stations or similar facilities. In particular, the methods and devices of the invention are equally useful in these devices.
- VCI vehicle communication interface
- these communication interfaces are mobile interfaces that can be carried with the vehicle in a workshop from workplace to workplace.
- Fig. 1 shows a schematic representation of a VCI 1 according to an embodiment of the invention.
- the VCI 1 is arranged in a housing 11 and comprises a microprocessor 12, a connection device 13 with a connector 14 for connecting the VCI 1 to a standardized vehicle interface in a vehicle, a memory device 15 for storing unique identification data of the vehicle to be connected, a communication device 16 for establishing a communication link with diagnostic server devices 2 of specific vehicle testers, and a working data storage device 18 connected to the microprocessor.
- the microprocessor 12 is designed to evaluate control commands for the VCI 1 and to control the connection device 13, the memory device 15, the communication device 16, and the working data memory device 18.
- the microprocessor 12 may of course also include a microcontroller, an ASIC or similar device.
- connection device 13 can be designed to have interfaces for diagnostic bus systems of the vehicle to be connected on a lower communication layer, in particular the physical layer provide.
- the diagnostic bus systems can be used to address vehicle electronic control units.
- the storage device 15 may have an increased storage volume compared to conventional VCI in order to provide correspondingly much storage space for the unique identification data of the vehicle and to store configuration data of the microprocessor 12, the connection device 13 and the communication device 16.
- the memory device 15 comprises corresponding software 17, which is specific to the operation of the VCI 1.
- the software 17 is below Fig. 2 described in more detail.
- the communication device 16 is designed to establish a communication link with diagnostic server devices 2 of specific vehicle test devices and the central customer database.
- the communication device 16 may comprise means for establishing a wired or wireless connection, for example a radio module for Bluetooth or WLAN, an infrared interface, an RFID transponder or the like.
- the VCI 1 does not include any operating and display elements in the present example.
- the operating and display elements can be provided, for example, via the vehicle testers or universal operating and display devices to be connected to the VCI 1. Of course, it may also be possible to equip the VCI 1 with its own operating and display elements.
- the working data storage device 18 is designed to store all the data necessary for carrying out all the diagnostic, maintenance and repair steps at workstations in a workshop.
- customer data such as name, telephone number, mail address, address or the like
- order data such as the order number, the order date, information on agreed services and subsequently agreed steps and the like
- information about the vehicle such as number plate, serial number, mileage, detailed operating parameters of the vehicle, such as year of manufacture, model series, transmission type, engine type, control parameters for built-in control units in the vehicle, already performed maintenance, information on replaced parts or the like, after-identification data of the vehicle, and Documentation data of all diagnostic, maintenance, test and repair results, such as sequence of operations, measurement parameters, replacement part numbers, adjustment parameters of newly installed, serviced or repaired vehicle components, and the like.
- the data stored in the work data storage device 18 are basically intended to provide all necessary information about the assigned vehicle at each workstation of the workshop for vehicle testers or universal display and operating devices located there and for the workshop computer with the central customer database, without an exchange of information on a Workshop network must be made.
- the vehicle data are also intended to uniquely identify the vehicle with regard to important operating parameters, setting parameters and control parameters of all components and components installed in the vehicle.
- the working data storage device 18 can also be merged with the storage device 15, whereby, for example, a correspondingly larger storage volume and a storage division between data of the storage device 15 and data of the working data storage device 18 can be provided.
- the working data storage device 18 may also have software, similar to the software 17 of the memory device 15. It may also be provided that the software 17 is extended in a common embodiment of the memory device 15 and the working data storage device 18 so that both memory operated and controlled accordingly can be.
- Fig. 2 shows a schematic representation of the software architecture of a VCI, in particular the VCI 1, and a diagnostic server device 2.
- the software 17, which in a memory device 15 of the VCI 1 from Fig. 1 may be stored, a first communication layer 25, a memory software 26, a protocol software 27 and a second communication layer 28.
- the individual software components 25, 26, 27 and 28 may be combined in a software code. It is also possible that the software has 17 additional software components.
- the first communication layer 25 is designed to establish a communication with a communication layer 24 of a diagnostic server device 2 or a communication layer of a central customer database, not shown, and to control the VCI.
- the storage software 26 is configured to receive, store, and manage unique identification data for the vehicle 10.
- the unique identification data can preferably be held for the duration of a workshop stay of the vehicle 10 and output as needed via the diagnostic server device 2 to specific vehicle test equipment. It may further be provided to transfer data from the working data storage device 18 as needed via the diagnostic server device 2 to the vehicle test devices.
- the protocol software 27 is designed to provide necessary protocols for communication with the vehicle 10 and / or the diagnostic server device 2.
- the second communication layer 28 is designed to be connected via the connection device 13 in FIG Fig. 1 to control with the control devices in the vehicle 10 established communication links.
- the diagnostic server device 2 comprises as software components a communication layer 21, a software interface 22, a diagnostic server software 23 and a second communication layer 24.
- the second communication layer 24 may be used for communication with the first communication layer 25 of the software 17 of the VCI 1.
- the second communication layer 24 of the diagnostic server device 2 may further be configured to register which VCI 1 are within range of the vehicle testing device including the diagnostic server device 2. This information may change dynamically with the movement of a plurality of VCI 1 vehicles within a workshop.
- the VCI 1 can be designed via communication devices 16 to display their presence via beacon signals to the respective diagnostic server devices 2 in a workshop.
- the range of the VCI 1 can be predetermined.
- the first communication layer 21 of the diagnostic server device 2 may be configured to provide an interface for specific vehicle test devices, in particular for the vehicle test device in which the diagnostic server device 2 is integrated.
- the first communication layer 21 may be configured to provide functions of the controller communication. This includes, for example, the reading out of errors, actual values, operating state data, the deletion and overwriting of values in control devices, for example service intervals, Error registers, actuator controls, performing complex test procedures such as steering angle calibration, ABS sensor testing, pump testing, brake circuit venting, and the like.
- the first communication layer 21 is further configured to forward unique vehicle identifications from the electronic controllers of the vehicle 10 to be connected to the specific vehicle testers and the VCI.
- the first communication layer 21 can be tuned to the specific vehicle tester, for example by a preconfigured tester parameter set, which can be retrieved from the vehicle tester.
- Fig. 3 shows a schematic representation of the structure of a workshop workstation with a system with mobile communication interface.
- the vehicle 10 Shown are a vehicle 10 to which a VCI 1 to Fig. 1 connected.
- the vehicle 10 is located on a workstation in a workshop or testing center on which a corresponding vehicle test device 3 is present.
- the vehicle test device 3 comprises a test module 31, a control computer 32 with control software 33, an operating device 34 and a display device 35.
- the vehicle test device 3 can be connected via cables, sensors, hoses and similar suitable connection means 37 to the vehicle 10 or to vehicle components of the vehicle 10 For example, be connected to the exhaust, the engine, the air conditioner, the brake system or the like.
- the vehicle inspection device 3 can be arranged in a housing 36.
- the vehicle testing device 3 may be housed, for example, in a carriage or be firmly connected to the workshop floor at the workplace.
- the test module 31 may include a specific vehicle test module that may perform predefined tests or diagnostics on particular vehicle components of the vehicle 10, such as engine tests, chassis measurement, air conditioning maintenance, or the like.
- the control computer 32 may be configured to control the corresponding specific functions of the test module 31 using the control software 33.
- the control software 33 is in the remote box in Fig. 3 shown in greater detail.
- the control software 33 comprises a software layer 33a for operating the vehicle test device 3 and for visualizing the test procedures and results, a software layer 33b for controlling the test procedures, a first communication layer 33d, which establishes communication between the test process control by the software layer 33b and the test module 31, a second communication layer 33e, which establishes communication of the test process control by the software layer 33b and the diagnostic server device 2, a diagnostic server device 2 according to FIG Fig. 2 and a detection software component 38.
- the software layers 33a and 33b for operation, display and test sequence control can also be integrated in a common software layer 33c.
- the second communication layer 33e may include a software component for communicating with the user, a software component for establishing communication with the diagnostic server device 2, a software component for communicating the test flow control with the diagnostic server device 2 during a test procedure, and a tester parameter set.
- the communication layer 33e may be configured to display to a user of the vehicle testing device 3 via the display unit 35 a list of vehicles 10 whose VCI 1 is within range of the diagnostic server device 2 or the respective workstation.
- the user can select the correct vehicle from the list of candidate vehicles 10 via the operating device 34.
- the corresponding VCI 1 can be disabled for selection at other workstations or with other vehicle test devices.
- errors in a vehicle selection can be prevented.
- the communication layer 33e can receive already stored identification data from the VCI 1 of the vehicle 10 in upstream working steps of the workshop sequence and forward it to the software layer 33b for test sequence control.
- the test procedure can advantageously be adapted automatically to the vehicle 10.
- the communication layer 33e can control functions in electronic control units of the vehicle 10 and forward diagnostic data dynamically from the electronic control units of the vehicle 10 to the software layer 33b during the test run.
- the communication layer 33e may further advantageously receive preconfigured parameters of the specific test module 31 to perform certain functions of the to selectively activate or deactivate electronic control units of the vehicle 10.
- the usually large range of functionality of the electronic control units can advantageously be broken down to the functions required for the respective test run in order to avoid errors in the operation of the vehicle test device 3 by the user.
- the communication layer 33e can also be designed to store data, work results and parameters which occur when working with the vehicle test device 3 on the vehicle 10 via the diagnostic server device 2 in the working data memory device of the VCI 1. It may furthermore be possible to read data, work results and parameters already stored in the work data storage device, which have been stored at other work stations of the workshop in previous work steps, for example, via the communication layer 33e into the vehicle test device 3.
- the read-in data can be used, for example, as the basis for testing, maintenance or repair work with the vehicle test device 3.
- FIG. 2 shows a schematic representation of a method for identifying, diagnosing (testing), maintaining and repairing a vehicle 10 in a workshop with a VCI 1 Fig. 1 according to a further embodiment of the invention.
- the course of the procedure after Fig. 4 will be in relation to the steps of in Fig. 5 illustrated schematic representation of a method for identifying, diagnosing, maintaining and repairing a vehicle in a workshop via a VCI 1 according to another embodiment of the invention explained in more detail.
- a workshop order is created and stored in the customer record in the central customer database (step 51 c).
- the workshop order for example, can be printed and signed by the customer.
- the customer record with the customer and vehicle data, the trouble symptoms and the shop order are stored in a working data storage device of the VCI 1 (step 51d).
- the vehicle 10 to be serviced or repaired can be connected to the VCI 1 (step 51 e).
- a first vehicle testing device 3a may be provided be, which is equipped with a common diagnostic server device 2.
- the first vehicle testing device 3 a may, for example, be a universal operating and display device which is used for a quick diagnosis of the vehicle 10.
- step 51f further unique vehicle identification data are determined (step 51f) and transmitted to the VCI 1 via the vehicle testing device 3a with the diagnostic server device 2 in which the identification data are stored at least for the duration of the workshop run.
- step 51f further unique vehicle identification data are determined
- step 51f further unique vehicle identification data are determined
- step 51f further unique vehicle identification data are determined
- the VCI 1 via the vehicle testing device 3a with the diagnostic server device 2 in which the identification data are stored at least for the duration of the workshop run.
- step 51f further unique vehicle identification data are determined (step 51f) and transmitted to the VCI 1 via the vehicle testing device 3a with the diagnostic server device 2 in which the identification data are stored at least for the duration of the workshop run.
- step 51 g with a detection of all fault memory entries
- the vehicle 10 is transferred to a second workstation 42 within the workshop.
- the VCI 1 is not separated from the vehicle 10 and carried along with the vehicle 10.
- the second workstation 42 may be, for example, a workstation for diagnosis and troubleshooting (step 52).
- the second vehicle inspection device 3b establishes communication with the VCI 1, and reads the stored unique identification data and those previously stored in the working data storage device of the VCI 1 stored vehicle-related data automatically from the VCI 1 (step 52a).
- the vehicle 10 may optionally be further analyzed and post-identified (step 52b).
- a faulty steering angle sensor may be identified (step 52d).
- a memory entry in the working data memory device of the VCI 1 is created via the result of the diagnosis and optionally the post-identification data (step 52e).
- the third workstation 43 can be, for example, a repair workstation.
- a replacement part for example, a defective vehicle component, for example, a defective steering angle sensor, may be removed (step 53b) and replaced with a spare part (step 53c).
- Step 53d first all vehicle-related data from the VCI 1 can be read (step 53d) and then, for example, the new steering angle sensor in the corresponding electronic control unit of the vehicle 10 registered or trained (step 53e ).
- the result of the learning and adjusting step is again stored in the working data memory of the VCI 1 (step 53f).
- the vehicle 10 is moved to a fourth workstation 44, at which initially the previously stored data is read from the working data memory device of the VCI 1 again (step 54a). Thereafter, at the fourth work station after an optional post-identification, for example, the vehicle geometry of the vehicle 10 can be measured and the chassis can be adjusted (step 54b).
- a fourth vehicle test device 3d for example a test device for chassis measurement, is provided at the fourth workstation 44.
- the newly installed steering angle sensor can be automatically calibrated by the vehicle tester 3d after completion of the wheel alignment and adjustment (step 54c), since the required identification and diagnostic result data of the vehicle 10 is already in the VCI 1 present.
- the identification data of the vehicle 10 can also be used already for the preparation of the measurement and adjustment of the chassis.
- a test drive (step 54e) may be performed.
- the VCI 1 can be disconnected from the vehicle 10 again upon completion of the workshop run (step 54f). All of the audit, maintenance, repair, diagnostic, and identification data collected in the scratch data storage facility of the VCI 1 until then may then be transferred from the VCI 1 to a customer database (step 54g).
- the shop order can then be completed and the data and result logs of the workshop run are stored in a central workshop system for reuse at a repeat visit to the customer or the vehicle 10.
- the VCI 1 and the method for identifying, diagnosing, maintaining and repairing a vehicle in a workshop are associated with a number of advantages.
- the required for the ECU communication identification of the vehicle is performed only once per workshop visit and only when needed to individual jobs or with extended to individual vehicle testers. This leads to a considerable saving of time in the workshop cycle.
- the once recorded vehicle identification data are equally available at each workstation, since they are carried by the vehicle via the VCI from workstation to workstation.
- the risk of incorrect operation or incorrect entries in the identification of vehicles is reduced because on the one hand, the identification data can be automatically retrieved from the VCI and on the other hand, each vehicle in the workshop can be actively called for editing only at a single workstation.
- Specific vehicle testing devices and universal operating and display devices can be equipped with a uniform diagnostic server device, and no complex adaptation process to the particular circumstances of the individual vehicle test device is necessary.
- the control software of the vehicle tester can only activate those functions in the communication with the electronic control units of the vehicle, which are also required for the respective workstation. This allows a simple and convenient handling of the specific vehicle testers or universal operating and display devices at specific workstations in the workshop. For the users of the vehicle test equipment at the workplaces, the necessary qualification in dealing with the control unit communication is reduced, since the communication between the electronic control units in the vehicle and the vehicle test equipment can run largely automatically and in the background.
- the central customer database can thus be operated, for example, as a minimal solution on only one or two workstations. It is of course also possible to provide a workshop network in addition to the storage of the data on the VCI, for example to provide greater data security or to keep a reserve solution available in the event of defects or failures.
- the selection of job and / or vehicle to be performed at different workstations can be dispensed with since all necessary information for this is already carried in the VCI with the vehicle from workstation to workstation.
- a dynamic update of the order status is guaranteed, since at each Workplace achieved results and identified parameters can be stored in the VCI.
- redundant post-identification can be omitted at some workstations if this has already been done in an upstream work step.
- the present invention provides a mobile communication interface for identifying a vehicle and for communicating with the vehicle-mounted electronic control units in a workshop, with a connection device that is designed to connect a vehicle in a workshop to the mobile communication interface
- a working data storage device configured to store vehicle records from a central customer database or from a vehicle inspection device for additional vehicle identification data, inspection, diagnostic, and / or maintenance result data from vehicle inspection, diagnostic, and / or maintenance steps performed in the workshop on the vehicle
- a communication device that is adapted to provide these enhanced vehicle records to vehicle testers or the central customer database preferably to transmit wirelessly and to exchange information between the electronic control units installed in the vehicle and theajiprüfausn at different workplaces in the workshop.
- the present invention provides a system for identifying, diagnosing, maintaining and repairing a vehicle in a workshop, having a mobile communication interface according to the invention, a central customer database and a plurality of vehicle test devices, each having a diagnostic server device for establishing communication with the mobile Communication interface and by means of the mobile communication interface with built-in electronic control units in the vehicle, an operating and display device for controlling the vehicle tester and the mobile communication interface, and different vehicle test modules, which are designed based on the examination, diagnosis and / or maintenance result data perform vehicle-specific vehicle tests on the vehicle.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Claims (8)
- Procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule (10) dans un atelier, comprenant les étapes suivantes :mise en mémoire de données de client, de véhicule et d'ordre d'atelier relatives au véhicule (10) à partir d'une base de données de clients centrale dans un dispositif d'enregistrement de données de travail (18) d'une interface de communication mobile (1) ;raccordement de l'interface de communication mobile (1) au véhicule (10) et connexion d'un premier appareil de contrôle de véhicule (3a) au moins équipé de l'interface de communication mobile (1) à un premier poste de travail (41) ;chargement des données de client, de véhicule et d'ordre d'atelier depuis le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) dans l'ordinateur de commande (32a) du premier appareil de contrôle de véhicule (3a) ;exécution de premiers contrôles sur le véhicule (10) avec le premier appareil de contrôle de véhicule (3a) et/ou l'interface de communication mobile (1) ;mise en mémoire des résultats des premiers contrôles dans le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) par le premier appareil de contrôle de véhicule (3a) ;déconnexion du premier appareil de contrôle de véhicule (3a) du véhicule (10) ;raccordement d'un deuxième appareil de contrôle de véhicule (3b) au véhicule (10) et chargement des données de client, de véhicule et d'ordre d'atelier ainsi que des résultats des premiers contrôles depuis le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) dans le deuxième appareil de contrôle de véhicule (3b) sur un deuxième poste de travail (42) ;exécution de deuxièmes contrôles sur le véhicule (10) avec le deuxième appareil de contrôle de véhicule (3b) et/ou l'interface de communication mobile (1) raccordée au véhicule (10) sur la base des résultats des premiers contrôles ;mise en mémoire des résultats des deuxièmes contrôles dans le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) par le deuxième appareil de contrôle de véhicule (3b) ; etchargement des données de client, de véhicule et d'ordre d'atelier ainsi que des résultats des premiers et des deuxièmes contrôles depuis le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) dans la base de données de clients centrale.
- Procédé selon la revendication 1, comprenant en outre les étapes suivantes :raccordement d'un appareil de commande et d'affichage universel (3c) au véhicule (10) et chargement des données de client, de véhicule et d'ordre d'atelier ainsi que des résultats des premiers et des deuxièmes contrôles depuis l'interface de communication mobile (1) dans l'appareil de commande et d'affichage universel (3c) ;exécution de contrôles supplémentaires sur le véhicule (10) avec l'appareil de commande et d'affichage universel (3c) et l'interface de communication mobile (1) raccordée au véhicule sur un troisième poste de travail (43) ; etmise en mémoire des résultats des troisièmes contrôles dans le dispositif d'enregistrement de données de travail (18) de l'interface de communication mobile (1) par l'appareil de commande et d'affichage universel (3c).
- Procédé selon la revendication 2, le premier appareil de contrôle de véhicule (3a) et/ou le deuxième appareil de contrôle de véhicule (3b) et/ou l'appareil de commande et d'affichage universel (3c) disposant d'un dispositif serveur de diagnostic uniforme (2) destiné à établir une communication avec l'interface de communication mobile (1) et, au moyen de l'interface de communication mobile (1), avec les contrôleurs électroniques montés dans le véhicule (10).
- Procédé selon la revendication 3, les données d'identification des véhicules (10) qui se trouvent dans l'atelier mises en mémoire dans les interfaces de communication mobiles (1) étant affichées à l'attention de l'utilisateur du premier (3a) ou du deuxième appareil de contrôle de véhicule (3b) respectif ou de l'appareil de commande et d'affichage universel (3c) au premier (41), au deuxième (42) et au troisième poste de travail (43).
- Procédé selon la revendication 4, l'affichage des données d'identification au premier (41), au deuxième (42) ou au troisième poste de travail (43) s'effectuant en fonction de la proximité du poste de travail (41 ; 42 ; 43) du véhicule (10) correspondant auquel est raccordée l'interface de communication mobile (1).
- Interface de communication mobile (1) destinée à identifier un véhicule (10) et à communiquer avec les contrôleurs électroniques montés dans le véhicule (10) dans un atelier, comprenant :un dispositif de connexion (13) qui est conçu pour raccorder un véhicule (10) dans un atelier à l'interface de communication mobile (1) ;un dispositif de communication (16) qui est conçu pour recevoir des données de client, de véhicule et d'ordre d'atelier de la part d'une base de données de clients centrale, un dispositif d'enregistrement de données de travail (18) qui est conçu pour mettre en mémoire les données de client, de véhicule et d'ordre d'atelier à propos du véhicule (10), le dispositif de communication (16) étant en outre conçu pour transmettre les données de client, de véhicule et d'ordre d'atelier chargées depuis le dispositif d'enregistrement de données de travail (18) à un premier appareil de contrôle de véhicule (3a) et pour recevoir de la part du premier appareil de contrôle de véhicule (3a) des résultats de premiers contrôles, le dispositif d'enregistrement de données de travail (18) étant en outre conçu pour mettre en mémoire les résultats de premiers contrôles, le dispositif de communication étant en outre conçu pour transmettre les données de client, de véhicule et d'ordre d'atelier ainsi que les résultats de premiers contrôles à un deuxième appareil de contrôle de véhicule (3b) et pour recevoir de la part du deuxième appareil de contrôle de véhicule (3b) des résultats de deuxièmes contrôles, le dispositif d'enregistrement de données de travail (18) étant conçu pour mettre en mémoire les résultats de deuxièmes contrôles et le dispositif de communication (16) étant en outre conçu pour transmettre les données de client, de véhicule et d'ordre d'atelier ainsi que les résultats de premiers et de deuxièmes contrôles à la base de données de clients centrale.
- Interface de communication mobile (1) selon la revendication 6, l'interface de communication mobile (1) étant conçue pour être emportée dans l'atelier avec le véhicule (10) à connecter.
- Système pour identifier, diagnostiquer, entretenir et réparer un véhicule (10) dans un atelier, comprenant :une interface de communication mobile (1) selon l'une des revendications 6 et 7 ; etune pluralité d'appareils de contrôle de véhicule (3 ; 3a ; 3b ; 3c ; 3d) comprenant respectivement :un dispositif serveur de diagnostic (2) destiné à établir une communication avec l'interface de communication mobile (1) et, au moyen de l'interface de communication mobile (1), avec les contrôleurs électroniques montés dans le véhicule (10) ;un dispositif de commande et d'affichage (34 ; 35) destiné à commander les appareils de contrôle de véhicule (3 ; 3a ; 3b ; 3c ; 3d) et l'interface de communication mobile (1) ; etdifférents modules de contrôle de véhicule (31) qui sont conçus pour, sur la base de données de résultat de contrôle, de diagnostic et/ou d'entretien, exécuter des contrôles de véhicule spécifiques à l'appareil de contrôle sur le véhicule (10).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102011077196A DE102011077196A1 (de) | 2011-06-08 | 2011-06-08 | Mobile Kommunikationsschnittstelle, System mit mobiler Kommunikationsschnittstelle und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs |
PCT/EP2012/059541 WO2012168071A1 (fr) | 2011-06-08 | 2012-05-23 | Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2718908A1 EP2718908A1 (fr) | 2014-04-16 |
EP2718908B1 true EP2718908B1 (fr) | 2017-02-01 |
Family
ID=46146897
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12722395.6A Active EP2718908B1 (fr) | 2011-06-08 | 2012-05-23 | Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule |
Country Status (7)
Country | Link |
---|---|
US (1) | US9317977B2 (fr) |
EP (1) | EP2718908B1 (fr) |
CN (1) | CN103582904B (fr) |
BR (1) | BR112013031482B1 (fr) |
DE (1) | DE102011077196A1 (fr) |
ES (1) | ES2623940T3 (fr) |
WO (1) | WO2012168071A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107547108A (zh) * | 2017-08-26 | 2018-01-05 | 南京天普机电产品制造有限公司 | 客车轴报通讯综合测试仪 |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9646432B2 (en) * | 2008-04-14 | 2017-05-09 | Innova Electronics Corporation | Hand held data retrieval device with fixed solution capability |
DE102011004205A1 (de) * | 2011-02-16 | 2012-08-16 | Robert Bosch Gmbh | System und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs |
DE102011004207A1 (de) * | 2011-02-16 | 2012-08-16 | Robert Bosch Gmbh | Mobile Kommunikationsschnittstelle, System mit mobiler Kommunikationsschnittstelle und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs |
DE102011077196A1 (de) * | 2011-06-08 | 2012-12-13 | Robert Bosch Gmbh | Mobile Kommunikationsschnittstelle, System mit mobiler Kommunikationsschnittstelle und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs |
DE102013004917A1 (de) * | 2013-03-22 | 2014-09-25 | Deutsche Telekom Ag | Verfahren und System zur Fernauslesung von Daten eines Fahrzeugs zur Unterstützung der Wartung und/oder der Reparatur des Fahrzeugs, Telekommunikationsendgerät, Computerprogramm und Computerprogrammprodukt |
DE102015212558A1 (de) * | 2015-07-06 | 2017-01-12 | Bayerische Motoren Werke Aktiengesellschaft | Kommunikation einer Fahrzeug-Serviceanlage mit einem Fahrzeug |
DE102015010042A1 (de) * | 2015-08-01 | 2017-02-02 | GM Global Technology Operations LLC (n. d. Ges. d. Staates Delaware) | Prüfanordnung zur Prüfung mindestens einer Verbindungsschnittstelle und Verfahren zur Prüfung mindestens einer Verbindungsschnittstelle mit einer Prüfanordnung |
CN105208080A (zh) * | 2015-08-14 | 2015-12-30 | 深圳市元征科技股份有限公司 | 一种解决方案的获取方法、移动终端、车载终端及系统 |
US10399706B1 (en) * | 2016-06-22 | 2019-09-03 | Amazon Technologies, Inc. | Unmanned aerial vehicle maintenance troubleshooting decision tree |
DE102016220015A1 (de) * | 2016-10-13 | 2018-04-19 | Trumpf Werkzeugmaschinen Gmbh + Co. Kg | Handarbeitsplatzeinheit, Abseits-Datenverarbeitungsvorrichtung, Handarbeitsplatzbetreibungssystem, Handarbeitsplatzbetriebsverfahren und Handarbeitsplatzbereitstellungsverfahren |
DE102016125294A1 (de) * | 2016-12-22 | 2018-06-28 | Dr. Ing. H.C. F. Porsche Aktiengesellschaft | Verfahren und System für die Diagnose oder Konfigurierung eines Fahrzeugs |
KR102506932B1 (ko) * | 2018-04-24 | 2023-03-07 | 현대자동차 주식회사 | 차량 쏠림 검사 장치 및 그 방법 |
US11651628B2 (en) | 2020-04-20 | 2023-05-16 | Innova Electronics Corporation | Router for vehicle diagnostic system |
US11967189B2 (en) | 2020-04-20 | 2024-04-23 | Innova Electronics Corporation | Router for communicating vehicle data to a vehicle resource |
US11995616B2 (en) * | 2020-10-09 | 2024-05-28 | ANI Technologies Private Limited | Asset health management for vehicles |
FR3115910A1 (fr) | 2020-10-30 | 2022-05-06 | France Atelier | Système intégré de diagnostic et de maintenance de véhicules et de leur gestion dans un atelier de réparation de véhicules |
WO2022091017A1 (fr) | 2020-10-30 | 2022-05-05 | France Atelier | Système intégré de diagnostic et de maintenance de véhicules et de leur gestion dans un atelier de réparation de véhicules |
US11702082B2 (en) | 2020-11-19 | 2023-07-18 | Toyota Motor North America, Inc. | Virtual sim for vehicle |
CN113377079B (zh) * | 2021-05-28 | 2022-06-28 | 东风柳州汽车有限公司 | 试验样车里程管理系统及方法 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7103460B1 (en) * | 1994-05-09 | 2006-09-05 | Automotive Technologies International, Inc. | System and method for vehicle diagnostics |
DE4446512A1 (de) | 1994-12-24 | 1996-06-27 | Sel Alcatel Ag | Vorrichtung zur Durchführung eines Fahrzeugtests oder zur Auswertung von Fahrzeugfehlern |
US5717595A (en) * | 1995-01-12 | 1998-02-10 | Cherrington; John K. | Integrated automated vehicle analysis |
US5657233A (en) * | 1995-01-12 | 1997-08-12 | Cherrington; John K. | Integrated automated vehicle analysis |
JP4015744B2 (ja) * | 1997-07-24 | 2007-11-28 | 本田技研工業株式会社 | 車両診断装置 |
DE19921846A1 (de) | 1999-05-11 | 2000-11-23 | Bosch Gmbh Robert | Diagnosetestvorrichtung mit portablem Prüfgerät für Kraftfahrzeuge |
JP4168866B2 (ja) * | 2003-07-25 | 2008-10-22 | トヨタ自動車株式会社 | 車両情報通信方法、車両情報通信システムおよびセンター |
US8296008B2 (en) | 2007-03-14 | 2012-10-23 | Spx Corporation | Programmable function key on wireless OBDII interface |
US20090216584A1 (en) * | 2008-02-27 | 2009-08-27 | Fountain Gregory J | Repair diagnostics based on replacement parts inventory |
US8340855B2 (en) * | 2008-04-22 | 2012-12-25 | Spx Corporation | USB isolation for vehicle communication interface |
US20100292890A1 (en) * | 2009-05-12 | 2010-11-18 | Morris William S | Vehicle Rules Engine |
US8443301B1 (en) * | 2010-09-27 | 2013-05-14 | Darek Easterly | Inspection reporting including a 3D vehicle model |
DE102011077196A1 (de) * | 2011-06-08 | 2012-12-13 | Robert Bosch Gmbh | Mobile Kommunikationsschnittstelle, System mit mobiler Kommunikationsschnittstelle und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs |
-
2011
- 2011-06-08 DE DE102011077196A patent/DE102011077196A1/de not_active Withdrawn
-
2012
- 2012-05-23 US US14/124,336 patent/US9317977B2/en active Active
- 2012-05-23 BR BR112013031482-6A patent/BR112013031482B1/pt active IP Right Grant
- 2012-05-23 WO PCT/EP2012/059541 patent/WO2012168071A1/fr active Application Filing
- 2012-05-23 EP EP12722395.6A patent/EP2718908B1/fr active Active
- 2012-05-23 CN CN201280028156.XA patent/CN103582904B/zh active Active
- 2012-05-23 ES ES12722395.6T patent/ES2623940T3/es active Active
Non-Patent Citations (1)
Title |
---|
None * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107547108A (zh) * | 2017-08-26 | 2018-01-05 | 南京天普机电产品制造有限公司 | 客车轴报通讯综合测试仪 |
CN107547108B (zh) * | 2017-08-26 | 2020-11-03 | 南京天普机电产品制造有限公司 | 客车轴报通讯综合测试仪 |
Also Published As
Publication number | Publication date |
---|---|
BR112013031482B1 (pt) | 2020-11-24 |
EP2718908A1 (fr) | 2014-04-16 |
WO2012168071A1 (fr) | 2012-12-13 |
CN103582904A (zh) | 2014-02-12 |
CN103582904B (zh) | 2016-01-20 |
US9317977B2 (en) | 2016-04-19 |
BR112013031482A2 (pt) | 2016-12-13 |
ES2623940T3 (es) | 2017-07-12 |
US20140188331A1 (en) | 2014-07-03 |
DE102011077196A1 (de) | 2012-12-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2718908B1 (fr) | Interface de communication mobile, système ayant une interface de communication mobile et procédé d'identification, de diagnostic, d'entretien et de réparation d'un véhicule | |
EP2676115B1 (fr) | Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule | |
DE102011004207A1 (de) | Mobile Kommunikationsschnittstelle, System mit mobiler Kommunikationsschnittstelle und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs | |
EP2721586B1 (fr) | Procédé et système d'établissement automatique d'une liaison de communication avec un véhicule | |
DE102014105674A1 (de) | Online-fahrzeugwartung | |
US20090204287A1 (en) | Diagnostic System and Diagnostic Test with a WLAN Transmission Module | |
EP2614350A1 (fr) | Dispositif de surveillance de véhicule à moteur et procédé de surveillance de véhicule à moteur | |
DE102015214739A1 (de) | Bestimmung einer Fehlerursache bei einem Fahrzeug | |
WO2001043079A1 (fr) | Procede de reconnaissance de defauts d'un vehicule automobile | |
DE102014109594A1 (de) | Prüfsystem für ein Fahrzeug und Steuerverfahren dafür | |
WO2021084065A1 (fr) | Système de gestion d'une flotte de véhicules | |
DE102012011538A1 (de) | Verfahren und System zur Telediagnose von Fahrzeugen | |
DE102014114202A1 (de) | Verfahren zum Prognostizieren einer Panne und/oder eines Reparatur- und/oder Wartungsbedarfs | |
EP1597117B1 (fr) | Dispositif et procede de diagnostic embarque central pour vehicules automobiles | |
WO2014177309A1 (fr) | Système d'information et procédé de traitement de l'information, en particulier pour assister des travaux dans un atelier de réparation automobile | |
EP2284631A1 (fr) | Procédé de fonctionnement d'un système de diagnostic de véhicule, programme de commande et système de diagnostic de véhicule | |
EP2175334A2 (fr) | Procédé d'augmentation de l'efficacité de véhicules ou de systèmes de véhicules, avec et sans systèmes d'armement | |
DE10307344A1 (de) | Vorrichtung und Verfahren zur dezentralen On-Board-Diagnose für Kraftfahrzeuge | |
DE102015100072B4 (de) | Überprüfungsverfahren für Identifizierungsnummern bei Reifenwechsel nach der Einrichtung von Reifendrucküberwachungsvorrichtungen in einem Kraftfahrzeug | |
DE102017217873A1 (de) | Fahrzeug mit integriertem Fahrzeugdiagnosesystem | |
DE102016223973A1 (de) | Konzept zum Prüfen eines Sensorsystems zum Erfassen eines Belegungszustands eines Stellplatzes auf Fehler | |
DE102004052780B4 (de) | Fahrzeugservicesystem sowie Verfahren zur Durchführung einer Fahrzeugdiagnose | |
EP3002715A1 (fr) | Méthode pour pronostiquer une panne et/ou un besoin d'une réparation et/ou de maintenance |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140108 |
|
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 |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20150210 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G07C 5/08 20060101AFI20160728BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20161014 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
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 Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 866120 Country of ref document: AT Kind code of ref document: T Effective date: 20170215 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 502012009444 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 6 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2623940 Country of ref document: ES Kind code of ref document: T3 Effective date: 20170712 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20170201 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: 20170601 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: 20170502 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: 20170501 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: 20170201 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: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20170201 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: 20170201 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: 20170601 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170531 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: 20170201 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: 20170201 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: 20170201 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: 20170501 |
|
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: 20170201 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: 20170201 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: 20170201 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: 20170201 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502012009444 Country of ref document: DE |
|
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: 20170201 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: 20170201 |
|
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 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
26N | No opposition filed |
Effective date: 20171103 |
|
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: 20170201 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170531 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: 20170201 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170531 |
|
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: 20170523 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20170531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170523 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 7 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 866120 Country of ref document: AT Kind code of ref document: T Effective date: 20170523 |
|
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: 20170531 Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170523 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT 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: 20170201 |
|
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: 20120523 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK 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: 20170201 |
|
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: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL 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: 20170201 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20230531 Year of fee payment: 12 Ref country code: FR Payment date: 20230517 Year of fee payment: 12 Ref country code: ES Payment date: 20230621 Year of fee payment: 12 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20230522 Year of fee payment: 12 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230726 Year of fee payment: 12 |