EP2676115B1 - Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule - Google Patents

Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule Download PDF

Info

Publication number
EP2676115B1
EP2676115B1 EP12701235.9A EP12701235A EP2676115B1 EP 2676115 B1 EP2676115 B1 EP 2676115B1 EP 12701235 A EP12701235 A EP 12701235A EP 2676115 B1 EP2676115 B1 EP 2676115B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
workshop
mobile communication
central
diagnostic server
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
Application number
EP12701235.9A
Other languages
German (de)
English (en)
Other versions
EP2676115A1 (fr
Inventor
Roger Malmsheimer
Ramon Amirpour
Guenter Nobis
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Robert Bosch GmbH
Original Assignee
Robert Bosch GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP2676115A1 publication Critical patent/EP2676115A1/fr
Application granted granted Critical
Publication of EP2676115B1 publication Critical patent/EP2676115B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808Diagnosing performance data
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Indexing scheme relating to group G07C5/00
    • G07C2205/02Indexing scheme relating to group G07C5/00 using a vehicle scan tool

Definitions

  • the invention relates to a system and a method for identifying, diagnosing, maintaining and repairing a vehicle, in particular in a motor vehicle workshop.
  • the pamphlet DE 44 46 512 A1 discloses a device for carrying out a vehicle test with a mobile radio component which transmits diagnostic data from a vehicle to a workshop.
  • the pamphlet DE 199 21 846 A1 discloses a diagnostic test apparatus with portable tester for motor vehicles.
  • a diagnostic device for vehicles is known in which a portable diagnostic unit (2) is connected to an electronic control unit ECU of a vehicle C via a cable (22).
  • the portable diagnostic device (2) is connected to a barcode reader (21) which reads a barcode to identify the vehicle.
  • the portable diagnostic device also determines the type of ECU. Diagnostic programs are made available wirelessly from a host computer (3) depending on the type of ECU. To simplify and accelerate the process, it is proposed that if a portable diagnostic device at another station on a diagnostic line has recognized an identical type of ECU in another vehicle, the diagnostic programs for this type of ECU are exchanged directly between the portable diagnostic devices to relieve the host computer.
  • the technical development of motor vehicle testing technology has led to a large number of specific external test devices for different test areas and motor vehicle components.
  • the vehicle testing devices used for this are highly specialized and adapted to the corresponding vehicle components.
  • Vehicle test devices are often used at special workplaces in a workshop or a test center, for example because the vehicle test devices are permanently installed in the workshop.
  • a vehicle that is in the workshop for fault diagnosis and / or repair is moved from workstation to workstation, depending on the test or repair to be carried out.
  • Diagnostic testers usually include an assembly that is responsible for communication with the vehicle. This assembly is usually referred to as a vehicle communication interface or, as is customary internationally, as a vehicle communication interface, abbreviated to VCI. VCIs of this type can also be arranged in their own housing and communicate with universal control and display devices such as laptops, PDAs or smartphones in a wired or wireless manner. The diagnostic functionality of universal diagnostic testers or operating and display devices is guaranteed by appropriate diagnostic software, which enables operation, display, diagnostic process control and communication with the electronic control devices via the VCI.
  • Fig. 6 shows a vehicle 61 in a workshop.
  • the vehicle 61 comprises one or more electronic control units 62 which are installed in the vehicle 61.
  • the vehicle 61 is brought to different workplaces 65a, 65b and 65c, which can be spatially separated from one another.
  • a specific vehicle test device 64a, 64b, 64c assigned to the respective workstation.
  • the specific vehicle test devices 64a, 64b, 64c can be connected to components of the vehicle 61, such as the exhaust, the engine, the air conditioning system or other components, for test purposes.
  • a universal diagnostic tester 63 assigned to the respective workstation 65a, 65b, 65c is available at each workstation, with which communication with the electronic control units 62 of the Vehicle 61 is produced via a standardized vehicle interface, not shown.
  • the workshop only has one universal diagnostic tester 63, which is then passed on from work station to work station if necessary.
  • the respective universal diagnostic tester 63 When the vehicle 61 runs through the workshop, it is necessary for the respective universal diagnostic tester 63 to be connected to the standardized vehicle interface (not shown) at each workstation 65a, 65b, 65c.
  • the diagnosis tester 63 and the respective vehicle test device 64a, 64b, 64c are operated separately. This can lead to manual input errors by the users of the devices.
  • a certain amount of additional time and effort is required.
  • Fig. 7 shows a different approach: A vehicle 71 with one or more built-in electronic control units 72 passes through workplaces 75a, 75b, 75c in a workshop.
  • a specific vehicle testing device 74a, 74b, 74c is located at each of the workstations 75a, 75b, 75c.
  • Each of the specific vehicle test devices 74a, 74b, 74c each includes an integrated VCI 73a, 73b, 73c, by means of which communication with the electronic control devices 72 in the vehicle 71 is established via a standardized vehicle interface (not shown). This eliminates the need to operate a separate universal diagnostic tester parallel to the vehicle tester as in Fig. 6 .
  • the invention is based on the idea of carrying out the identification of a vehicle, which is necessary for a large number of work steps in a workshop or test center, only once at the beginning of the workshop run or the test center run.
  • the identification data is saved in the VCI installed in the vehicle and carried with the vehicle from workstation to workstation in the workshop. In addition, that remains VCI until the end of the workshop cycle in the respective vehicle.
  • the multiple VCIs in a workshop can then be managed and controlled centrally from a central diagnostic server device via a workshop network.
  • vehicle test devices and / or universal operating and display devices present at the respective workplaces can initiate communication with the VCI and the control devices of the vehicle at the workplace via the central diagnostic server device, call up the vehicle's identification data and, for example, exchange diagnostic information with the vehicle control devices .
  • This saves the user of the vehicle tester and / or the universal operating and display device from installing and removing the VCI and the time required to identify the vehicle and to establish communication with the control units installed in the vehicle. In this way, on the one hand, the vehicle test and / or the fault diagnosis can be started more quickly and, on the other hand, errors in the manual vehicle detection can be avoided.
  • the method according to the invention for identifying, diagnosing, maintaining and repairing a vehicle in a workshop comprises the steps of connecting a mobile communication interface (VCI) and a first vehicle test device to the vehicle at a first workstation, establishing a communication link between the VCI and one on one central workshop server arranged central diagnostic server device as well as the first vehicle tester, the identification of the vehicle for diagnostic purposes, in particular for the control unit communication, the storage of identification data for the vehicle in the VCI, the simultaneous diagnosis, maintenance or repair of the vehicle with the first vehicle tester and the VCI via the central diagnostic server device, the disconnection of the first vehicle testing device from the vehicle, the connection of a second vehicle testing device to the vehicle at a second workstation, the readout ns of the identification data from the VCI into the second vehicle tester and the simultaneous diagnosis, maintenance or repair of the vehicle with the second vehicle tester and the VCI via the central diagnostic server device.
  • VCI mobile communication interface
  • the communication link between the VCI and the central diagnostic server device is advantageously a wireless communication link. This means that the VCI can be flexibly carried with the vehicle in the workshop.
  • the method according to the invention can furthermore include the steps of determining in the central diagnostic server device identification and / or diagnostic data from vehicles provided with VCI and located in the workshop, sending the determined identification and / or diagnostic data to the first or second vehicle testing device and displaying and processing the identified identification and / or diagnostic data at the first and the second workstation for the user of the respective first or second vehicle testing device.
  • the identification and / or diagnostic data can be displayed at the respective first or second workstation as a function of the proximity of the respective vehicle or the connected VCI to the workstation. This advantageously enables the VCI and thus the connected vehicle to be tracked as it passes through the workshop.
  • a system for identifying, diagnosing, maintaining and repairing and diagnosing a vehicle is provided in a workshop, with a central diagnostic server device, a plurality of VCI, each with a connection device which is designed to connect a VCI to a to connect standardized vehicle interface of a vehicle in a workshop, a storage device which is designed to additionally store identification data of the vehicle to be identified and connected, and a communication device which is designed to transmit identification and diagnostic data of the connected vehicle to the central diagnostic server device , and with a large number of vehicle test devices, each with different vehicle test modules, a communication device for establishing communication with the central diagnostic server device, an operating and A Display device of the vehicle test device for controlling the vehicle test modules and the VCI, which are designed to retrieve identification and, for example, diagnostic data of a vehicle from one of the large number of VCI via the central diagnostic server device and on the basis of the retrieved identification and diagnostic data and the diagnostic results of the specific vehicle test modules Carry out tester-specific vehicle tests on the vehicle.
  • the system according to the invention can preferably have a central diagnostic server device which is arranged on a central workshop server.
  • the system comprises a group of the plurality of vehicle test devices which comprise local diagnostic server devices which are designed to establish communication with the plurality of VCIs.
  • Vehicle testing devices within the meaning of this application are not restricted to special vehicle testing devices. They can include, for example, wheel alignment testers, engine testers, emission testers, brake testers, shock absorber testers, track testers, weighing devices, brake fluid testers, sound level meters, diesel smoke testers, chassis measuring devices, toe angle testers, steering angle testers, air conditioning testers and the like. These vehicle testers can be used in Workshops, in particular motor vehicle workshops, test centers or comparable facilities are used. In particular, the methods and devices according to the invention can be used equally in these devices.
  • VCI vehicle communication interface
  • these communication interfaces are mobile interfaces that can be carried with the vehicle from workstation to workstation in a workshop.
  • Fig. 8 shows a schematic representation of a vehicle test device structure in a workshop according to an embodiment of the invention.
  • a vehicle 10, in particular a motor vehicle, comprises one or more electronic control devices 10a.
  • the electronic control device (s) 10a can comprise specific control devices for specific vehicle components or universal electronic control devices 10a of the vehicle 10.
  • the electronic control devices 10a can hold diagnostic data, error data, actual values, operating state data or similar vehicle-relevant data for specific vehicle components via a standardized vehicle interface (not shown) and can be set to specific operating states or processes.
  • the electronic control device or devices 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 cycle, for example in the vehicle reception.
  • the VCI 1 can be designed to store unambiguous identification data of the vehicle 10, for example the vehicle owner, registration number, vehicle brand, vehicle make, chassis number or similar identification data.
  • the unique identification data can be re-entered in the vehicle reception of the workshop using a universal operating and display unit or taken from a central workshop database from a previous workshop visit.
  • the storage of the identification data in the VCI 1 can take place via a central workshop server 45.
  • the central workshop server 45 can include a central diagnostic server device 2, which is used to set up Communication connections with the VCI 1 is responsible.
  • the central diagnostic server device 2 can communicate with the VCI 1 via a wireless or wired communication connection, for example. In particular, it is possible via the central diagnostic server device 2 to manage and communicate with a large number of VCI 1, which are in use in the workshop and connected to various vehicles 10.
  • the VCI 1 is designed to be carried along with the vehicle 10 in the workshop when the vehicle 10 passes through the workplaces 42, 43, 44.
  • the specific vehicle test devices or universal operating and display units 3b, 3c, 3d are located at the workstations 42, 43, 44.
  • the specific vehicle test devices or universal operating and display units 3b, 3c, 3d can be connected to the respective vehicle components of the vehicle 10 at each workstation in order to carry out the diagnostic and / or repair work on the vehicle 10.
  • the central diagnostic server device 2 forms the communication point of contact for the specific vehicle test devices 3b, 3c, 3d, that is, the central diagnostic server device 2 can be designed to establish a communication link with the VCI 1 on the one hand and a communication link with each of the specific vehicle test devices 3b, 3c, 3d on the other build up. Via the central diagnostic server device 2, identification data of the vehicle 10 and, for example, diagnosis of the electronic control devices 10a can then be transferred from the VCI 1 to the specific vehicle test devices 3b, 3c, 3d.
  • the communication connection between the central diagnostic server device 2 and the specific vehicle test devices 3b, 3c, 3d can also be wireless or wired.
  • Fig. 1 shows a schematic representation of a VCI 1.
  • 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, and a communication device 16 for setting up a communication connection with a central diagnostic server device 2.
  • the microprocessor 12 is designed to evaluate control commands for the VCI 1 and to control the connection device 13, the memory device 15 and the communication device 16.
  • the microprocessor 12 can of course also comprise a microcontroller, an ASIC or a similar device.
  • connection device 13 can be designed to provide interfaces for diagnostic bus systems of the vehicle to be connected on a lower communication layer, in particular the bit transmission layer (“physical layer”).
  • the vehicle's electronic control units can be addressed via the diagnostic bus systems.
  • the memory device 15 can have a larger memory volume than conventional VCI in order to provide a correspondingly large amount of memory 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 storage device 15 comprises corresponding software 17 which is specific for the operation of the VCI 1.
  • the software 17 is described below under Fig. 2 described in more detail.
  • the communication device 16 is designed to establish a communication connection with a central diagnostic server device 2, for example in a central workshop server.
  • the communication device 16 can have 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 or display elements.
  • the operating and display elements can be provided, for example, via a universal operating and display device to be connected to the VCI 1 or a vehicle testing device.
  • a universal operating and display device to be connected to the VCI 1 or a vehicle testing device.
  • it can also be possible to equip the VCI 1 with its own operating and display elements.
  • Fig. 2 shows a schematic representation of the software architecture of two VCIs, in particular of the VCI 1 type, and a diagnostic server device 2 according to a further embodiment of the invention.
  • the software parts 17a and 17b shown can correspond to the software 17 that is stored in a storage device 15 of the VCI 1 Fig. 1
  • the software parts 17a and 17b each comprise a first communication layer 25a, 25b, a memory software 26a, 26b, a protocol software 27a, 27b and a second communication layer 28a and 28b.
  • the individual software components 25a / b, 26a / b, 27a / b and 28a / b can be combined in one software code. It is also possible that the software parts 17a and 17b each have further software components.
  • the first communication layer 25a, 25b is designed to set up communication with a communication layer 24 of a central diagnostic server device 2 and to control the VCI.
  • the communication layer 24 of the central diagnostic server device 2 can have two components 24a and 24b, each of which is provided for communication with one of the two mobile communication interfaces.
  • the storage software 26a, 26b is designed to receive, store and manage identification data for the vehicle 10. The identification data can preferably be kept for the duration of a workshop visit of the vehicle 10 and, if necessary, can be output via the central diagnostic server device 2 to specific vehicle testing devices or universal operating and display units.
  • the protocol software 27a, 27b is designed to provide necessary protocols for communication with the vehicle 10 and / or the central diagnostic server device 2.
  • the second communication layer 28a, 28b is designed to communicate via the connection device 13 in Fig. 1 to control communication links established with control units in the vehicle 10.
  • the central diagnostic server device 2 comprises, as software components, a communication layer 21, a software interface 22, diagnostic server software 23 and a second communication layer 24.
  • the diagnostic software 23, in conjunction with the software interface 22, can be designed to manage several mobile communication interfaces 1 in parallel and to access the same.
  • the second communication layer 24a, 24b can serve for communication with the first communication layer 25a, 25b of the software 17a or 17b of the VCI.
  • the second communication layer 24a, 24b of the central diagnostic server device 2 can also be designed to register which VCI 1 are within range of certain vehicle test devices. This information can change dynamically with the movement of a large number of vehicles provided with VCI 1 within a workshop.
  • the VCI 1 can be designed via communication devices 16 to indicate their presence via beacon signals to the central diagnostic server device 2 of a central workshop server in a workshop.
  • the first communication layer 21 of the central diagnostic server device 2 can be designed to provide an interface for specific vehicle test devices.
  • the first communication layer 21 can be designed to provide functions of the control device communication. This includes, for example, reading out errors, actual values, operating status data, deleting and overwriting values in control units, for example service intervals, error registers, actuator controls, performing complex test sequences such as a steering angle calibration, an ABS sensor test, a pump test, and a brake circuit vent and the same.
  • the first communication layer 21 is also designed to forward unique vehicle identifications from the electronic control devices of the vehicle 10 to be connected to the specific vehicle test devices and the VCI.
  • the first communication layer 21 can be matched to the specific vehicle test device, for example by means of a preconfigured test device parameter set which can be called up from the vehicle test device.
  • Fig. 3 shows a schematic representation of the structure of a workshop workstation.
  • a vehicle 10 to which a VCI 1 is shown is shown Fig. 1 connected.
  • the vehicle 10 is located on a workstation in a workshop or testing facility at which a corresponding vehicle testing device 3 is available.
  • the vehicle tester 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 tester 3 can be connected to the vehicle 10 or to vehicle components of the vehicle 10 such as the exhaust pipe via cables, sensors, hoses and similar suitable connecting means 37 , the engine, the air conditioning system, the braking system or the like.
  • the vehicle testing device 3 can be arranged in a housing 36.
  • the vehicle testing device 3 can for example be accommodated in a trolley or be permanently connected to the workshop floor at the workplace.
  • the test module 31 can have a specific vehicle test module which can carry out predefined tests or diagnostics with regard to certain vehicle components of the vehicle 10, for example engine tests, wheel alignment, air conditioning maintenance or the like.
  • the control computer 32 can be designed to control the corresponding specific functions of the test module 31 with the aid of the control software 33.
  • the control software 33 is in the remote box in FIG 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 sequences and results, a software layer 33b for controlling the test sequences, a first communication layer 33d, which establishes communication between the test sequence control through the software layer 33b and the test module 31, a second communication layer 33e, which establishes communication of the test sequence control through the software layer 33b and the diagnostic server device 2, and a diagnostic server device 2 according to FIG Fig. 2 .
  • the diagnostic server device 2 can be a local or decentralized diagnostic server device 2a, which in principle can be set up similar to the central diagnostic server device on a workshop server 45 and enables a direct communication link between a vehicle test device 3 and a VCI 1. For example, if a central diagnostic server device fails, the decentralized diagnostic server device 2a of a vehicle test device 3 in Fig. 3 Take over bridging communication tasks with the VCI 1. Communication then preferably takes place between the decentralized diagnostic server device 2a in FIG Fig. 3 and the VCI 1 wirelessly.
  • the software layers 33a and 33b for operation, display and test sequence control can also be integrated in a common software layer 33c.
  • Communication layer 33e can have a software component for communication with the user, a software component for establishing communication with the central or decentralized diagnostic server device 2a, a software component for communication between the test sequence control and the central or decentralized diagnostic server device 2a during a test sequence, and a test device parameter set.
  • the communication layer 33e can be designed to display a list of vehicles 10 to a user of the vehicle testing device 3 via the display unit 35, the VCI 1 of which is within range of the diagnostic server device 2 or the respective workstation. The user can thus select the correct vehicle from the list of vehicles 10 in question via the operating device 34.
  • the list can also be generated by the central diagnostic server device on a workshop server 45 and transmitted to the vehicle testing device.
  • the corresponding VCI 1 can be blocked for selection at other workplaces or with other vehicle testing devices. In this way, errors in a vehicle selection can advantageously be prevented.
  • a vehicle testing device for brake testing can access a VCI 1 of a vehicle 10 simultaneously with a universal operating and display device, for example a laptop, so that several testing and / or maintenance and / or repair steps can be carried out in parallel.
  • the communication layer 33e can receive already stored identification data from the VCI 1 of the vehicle 10 in preceding work steps of the workshop sequence and pass them on to the software layer 33b for test sequence control.
  • the test sequence can advantageously be automatically adapted to the vehicle 10.
  • the communication layer 33e can control functions in electronic control devices of the vehicle 10 via the central or decentralized diagnostic server device during the test run and dynamically forward diagnostic data from the electronic control devices of the vehicle 10 to the software layer 33b during the test run.
  • the communication layer 33e can furthermore advantageously receive preconfigured parameters of the specific test module 31 in order to activate or deactivate certain functions of the electronic control devices of the vehicle 10 in a targeted manner.
  • the usually large scope of functionality of the electronic control devices can advantageously be broken down into the functions required for the respective test run, in order to avoid errors when the user operates the vehicle test device 3.
  • Fig. 3a shows a schematic representation of the software architecture of the control software of two vehicle test devices and a central diagnostic server device 2 according to a further embodiment of the invention.
  • the respective control software 331 and 332 of the two vehicle testing devices can be integrated into the control software 33 of the vehicle testing device 3 in Fig. 3 correspond.
  • the components of the control software 331 and 332 each differ from the control software 33 of the vehicle testing device 3 in FIG Fig. 3 in that no decentralized or local diagnostic server devices 2a are provided.
  • the diagnosis server device 2 is shown in FIG Fig. 3a Arranged as a central diagnostic server device 2 on a central workshop server 45.
  • the central workshop server 45 can also have an acquisition software component 48.
  • the acquisition software component 48 can be designed to manage all of the VCI 1 currently used in the workshop or test center and their connected vehicles 10.
  • the acquisition software component 48 can be designed to acquire unique identification data of the vehicle, such as holder, license plate, chassis number and the like, and to store it in the VCI 1.
  • the vehicle test devices may also be possible to equip one or more of the vehicle test devices in a workshop, preferably a test device in the vehicle reception, with the detection software component 48. It may also be possible, instead of a vehicle testing device 3, to provide a universal operating and display unit such as a laptop, a PDA or a smartphone with the detection software component 48.
  • Fig. 4 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 is used in relation to the steps in Fig. 5
  • the schematic representation shown here of a method for identifying, diagnosing, maintaining and repairing a vehicle in a workshop via a VCI 1 is explained in more detail using an exemplary workshop process according to a further embodiment of the invention.
  • a first workstation 41 for example the vehicle acceptance department in a workshop, can use a first vehicle tester 3a via a central workshop server 45 be checked with a central diagnostic server device 2 and a detection software component 48 which of the total number of VCI 1 are ready for operation, which VCI 1 are available for installation in a vehicle 10, which VCI 1 is connected to which vehicle 10 and which of the vehicle test devices 3a , 3b, 3c, 3d with which VCI 1 or vehicle 10 is connected.
  • the first vehicle testing device 3 a can, for example, be a universal operating and display unit which, in cooperation with the VCI 1, can be used for a quick diagnosis of the vehicle 10.
  • the vehicle and / or customer data already stored in the workshop system for vehicle 10 can be read out or entered by the operator (step 51d) via a central workshop server 45 with a central diagnostic server device 2 and a detection software component 48
  • Unambiguous vehicle identification data can be determined (step 51e) and transmitted with the vehicle and / or customer data via the central diagnostic server device 2 to the VCI 1, preferably wirelessly, in which the vehicle identification data is stored at least for the duration of the workshop run (step 51f).
  • a quick diagnosis can be carried out with the VCI 1 by recording all fault memory entries in the electronic control units of the vehicle 10 (step 51g), after which a quick diagnosis Results protocol (step 51h) is printed.
  • the workshop order can then be coordinated with the customer (step 51i).
  • the vehicle 10 is then brought 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 work station 42 can be, for example, a work station for diagnosis and troubleshooting (step 52).
  • a second vehicle testing device 3b or a universal operating and display unit is located at the second workstation 42.
  • the second vehicle control device 3b establishes communication with the VCI 1 via the central diagnostic server device 2, and automatically reads the stored unique vehicle identification data from the VCI 1 via the central diagnostic server device 2.
  • step 52a it can be provided that, depending on the error symptoms specified by the customer (step 51b) or the results of the quick diagnosis (step 51g) at the second workstation 42 with the VCI 1 and the vehicle testing device 3b, further special vehicle testing devices or diagnostic steps for troubleshooting can be carried out on the vehicle 10. For example, a faulty steering angle sensor can be identified (step 52b), and a result log is again created after the troubleshooting (step 52c).
  • the vehicle 10, again together with the VCI 1, is then brought to a third workstation 43 with a third vehicle testing device or a universal operating and display unit 3c.
  • the third work station 43 can be a repair work station, for example.
  • a defective vehicle component for example a defective steering angle sensor
  • step 53b a defective steering angle sensor
  • step 53c a replacement part at the third workstation.
  • Communication with the VCI 1 and thus one or more electronic control units in the vehicle 10 can be established via the vehicle test device 3c with the help of the central diagnostic server device 2, so that, for example, the new steering angle sensor can be registered or learned in the corresponding electronic control device of the vehicle 10 ( Step 53d).
  • a result protocol is then again created (step 53e).
  • the vehicle 10 is brought to a fourth workstation 44, at which, for example, the vehicle geometry of the vehicle 10 can be measured (step 54a) and the chassis can be adjusted (step 54b).
  • a fourth vehicle test device 3d for example a test device, is closed at the fourth work station 44 Wheel alignment provided.
  • the newly installed steering angle sensor can be automatically calibrated by the vehicle testing device 3d after the chassis measurement and setting have been completed (step 54d), since the required identification data for the vehicle 10 is already in the VCI 1 are present.
  • the identification data of the vehicle 10 can also already be used for the preparation of the measurement and adjustment of the chassis.
  • the VCI 1 can be disconnected from the vehicle 10 again when the workshop cycle is ended (step 54e).
  • the workshop order can then be completed and the data and result logs of the workshop run can be stored in a central workshop system, for example the central workshop server 45, for reuse when the customer or vehicle 10 visits the workshop again.
  • Figure 4a shows a schematic representation of a method for identifying, diagnosing, maintaining and repairing a vehicle in a workshop via a VCI, a central workshop server with a central diagnostic server device and / or local diagnostic server devices according to a further embodiment of the invention.
  • the procedure after Figure 4a differs from the procedure according to Fig. 4 essentially only in the fact that a group of specific vehicle test devices, here for example only vehicle test device 3b, can be equipped with decentralized diagnostic server devices 2a.
  • the vehicle test devices of the group of specific vehicle test devices can thus establish direct communication with the VCI 1.
  • the central diagnostic server device 2 and / or the workshop server 45 fails, the VCI 1 can still be accessed via the decentralized diagnostic server devices 2a, here for example via the vehicle testing device 3b.
  • Any number of vehicle test devices can be equipped with such a decentralized diagnostic server device 2a.
  • the identification of the vehicle 10 required for the control device communication is carried out only once per workshop visit and is only expanded when required at individual workstations or with individual vehicle test devices. This leads to considerable time savings in the workshop cycle.
  • the vehicle identification data, once recorded, is available at every workstation, since it is carried along by the vehicle 10 via the VCI 1 from workstation to workstation and can be read out centrally via a workshop server 45 with a central diagnostic server device 2.
  • the control software of the vehicle testing device can only activate those functions in the communication with the electronic control devices of the vehicle that are actually required for the respective workstation. This enables simple and practical handling of the respective specific vehicle test devices or universal operating and display units at specific workplaces in the workshop. For the users of the vehicle test devices at the workstations, the necessary qualifications in dealing with control unit communication are reduced, since the communication between the electronic control units in the vehicle and the vehicle test devices can run largely automatically and in the background.

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 (10)

  1. Procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule (10) dans un atelier, comprenant les étapes consistant à :
    connecter un premier appareil de contrôle de véhicule (3a) au niveau d'un premier poste de travail (41) ;
    établir une liaison de communication avec un premier appareil de contrôle de véhicule (3a) et un dispositif serveur de diagnostic central (2) disposé sur un serveur d'atelier central (45) et un composant de logiciel de détection (48) ;
    connecter une interface de communication mobile (1) au véhicule (10) ;
    établir une liaison de communication au niveau du premier poste de travail (41) avec un premier appareil de contrôle de véhicule (3a) et l'interface de communication mobile (1) ;
    acquérir des données d'identification univoques pour le véhicule (10) avec le premier appareil de contrôle de véhicule (3a) et stocker des données d'identification pour le véhicule (10) dans l'interface de communication mobile (1) par l'intermédiaire du dispositif serveur de diagnostic central (2) disposé sur le serveur d'atelier central (45) ;
    effectuer des 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) ;
    déconnecter le premier appareil de contrôle de véhicule (3a) du véhicule (10) ;
    connecter un deuxième appareil de contrôle de véhicule (3b) au véhicule (10) et lire les données d'identification de l'interface de communication mobile (1) par l'intermédiaire du dispositif serveur de diagnostic central (2) dans le deuxième appareil de contrôle de véhicule (3b) à un deuxième poste de travail (42) ; et
    effectuer des 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) connectés au véhicule (10).
  2. Procédé selon la revendication 1, comprenant en outre les étapes consistant à :
    connecter un appareil de commande et d'affichage universel au véhicule (10) et lire les données d'identification à partir de l'interface de communication mobile (1) par l'intermédiaire du dispositif serveur de diagnostic central (2) dans l'appareil de commande et d'affichage universel ; et
    effectuer d'autres contrôles sur le véhicule (10) avec l'appareil de commande et d'affichage universel et l'interface de communication mobile (1) connectée au véhicule (10) à un troisième poste de travail (43).
  3. Procédé selon la revendication 1 ou 2, dans lequel la liaison de communication entre l'interface de communication mobile (1) et le dispositif serveur de diagnostic central (2) et/ou entre l'interface de communication mobile (1) et les appareils de contrôle de véhicule ou les appareils de commande et d'affichage universels est une liaison de communication sans fil.
  4. Procédé selon l'une quelconque des revendications précédentes, comprenant en outre les étapes consistant à :
    déterminer dans le dispositif serveur de diagnostic central (2) des données d'identification de véhicules (10) équipés d'interfaces de communication mobile (1) qui se trouvent à l'atelier ;
    envoyer les données d'identification déterminées au premier (3a) ou au deuxième appareil de contrôle de véhicule (3b) ; et
    afficher les données d'identification déterminées au premier (41) ou au deuxième poste de travail (42) pour l'utilisateur du premier (3a) ou du deuxième appareil de contrôle de véhicule (3b), respectivement.
  5. Procédé selon la revendication 4, dans lequel l'affichage des données d'identification au premier (41) ou au deuxième poste de travail (42) respectivement est effectué en fonction de la proximité du véhicule respectif (10) du poste de travail (41 ; 42) .
  6. Procédé selon l'une quelconque des revendications précédentes, comprenant en outre l'étape consistant à :
    établir une liaison de communication directe entre le premier (3a) et/ou le deuxième appareil de contrôle de véhicule (3b) et l'interface de communication mobile (1) .
  7. Système pour identifier, diagnostiquer, entretenir et réparer un véhicule (10) dans un atelier, comprenant :
    un dispositif serveur de diagnostic central (2) ;
    une pluralité d'interfaces de communication mobile (1), comprenant respectivement :
    un dispositif de liaison (13 ; 14) qui est conçu pour connecter l'interface de communication mobile (1) à un véhicule (10) dans un atelier ;
    un dispositif de mémoire (15) qui est conçu pour stocker des données d'identification du véhicule (10) à identifier et à connecter ; et
    un dispositif de communication (16) qui est conçu pour transmettre des données d'identification au dispositif serveur de diagnostic central (2) ; et
    une pluralité d'appareils de contrôle de véhicule (3 ; 3a ; 3b ; 3c ; 3d), comprenant respectivement :
    un dispositif de communication (331e ; 332e) pour établir une communication avec le dispositif serveur de diagnostic central (2) et le composant de logiciel de détection (48) ;
    un dispositif de commande et d'affichage (34 ; 35) pour commander l'appareil de contrôle de véhicule (3 ; 3a ; 3b ; 3c ; 3d) et l'interface de communication mobile (1) ; et
    différents modules de contrôle de véhicule (31) qui sont conçus pour sélectionner des interfaces de communication mobile (1) disponibles pour l'installation sur un véhicule (10) par l'intermédiaire du dispositif serveur de diagnostic central (2) et du composant de logiciel de détection (48), pour acquérir des données d'identification d'un véhicule (10) et pour les stocker dans l'interface de communication mobile (1) par l'intermédiaire du dispositif serveur de diagnostic central (2), pour récupérer des données d'identification d'un véhicule (10) à partir d'une de la pluralité d'interfaces de communication mobile (1) par l'intermédiaire du dispositif serveur de diagnostic central (2), et pour effectuer sur la base des données d'identification récupérées des contrôles de véhicule spécifiques à l'appareil de contrôle sur le véhicule (10).
  8. Système selon la revendication 7, dans lequel le dispositif serveur de diagnostic central (2) est disposé sur un serveur d'atelier central (45).
  9. Système selon la revendication 7 ou 8, dans lequel le composant de logiciel de détection (48) est disposé sur un serveur d'atelier central (45) et/ou l'un des modules de contrôle de véhicule (31).
  10. Système selon l'une quelconque des revendications 7 à 9, dans lequel un groupe de la pluralité d'appareils de contrôle de véhicule (3 ; 3a ; 3b ; 3c ; 3d) comprend un dispositif de serveur de diagnostic local (2a) qui est conçu pour établir une communication avec la pluralité d'interfaces de communication mobile (1) .
EP12701235.9A 2011-02-16 2012-01-09 Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule Active EP2676115B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102011004205A DE102011004205A1 (de) 2011-02-16 2011-02-16 System und Verfahren zum Identifizieren, Diagnostizieren, Warten und Reparieren eines Fahrzeugs
PCT/EP2012/050232 WO2012110263A1 (fr) 2011-02-16 2012-01-09 Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule

Publications (2)

Publication Number Publication Date
EP2676115A1 EP2676115A1 (fr) 2013-12-25
EP2676115B1 true EP2676115B1 (fr) 2020-12-23

Family

ID=45531860

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12701235.9A Active EP2676115B1 (fr) 2011-02-16 2012-01-09 Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule

Country Status (5)

Country Link
US (1) US9087420B2 (fr)
EP (1) EP2676115B1 (fr)
CN (1) CN103348230B (fr)
DE (1) DE102011004205A1 (fr)
WO (1) WO2012110263A1 (fr)

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105336044B (zh) 2008-10-02 2018-04-10 埃科亚特姆公司 针对设备的二手市场和自动售货系统
US11010841B2 (en) 2008-10-02 2021-05-18 Ecoatm, Llc Kiosk for recycling electronic devices
US10853873B2 (en) 2008-10-02 2020-12-01 Ecoatm, Llc Kiosks for evaluating and purchasing used electronic devices and related technology
DE102010040549A1 (de) * 2010-09-10 2012-03-15 Robert Bosch Gmbh Kraftfahrzeug-Prüfgerät und Kraftfahrzeug-Prüfverfahren
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
CN103592936A (zh) * 2013-11-08 2014-02-19 深圳市道通科技有限公司 汽车诊断装置与vci设备之间的自动连接方法及装置
EP2998607A1 (fr) * 2014-09-16 2016-03-23 Meritor Heavy Vehicle Braking Systems (UK) Limited Procédé et système d'ajustement du jeu de la course d'un composant de freinage
US10401411B2 (en) 2014-09-29 2019-09-03 Ecoatm, Llc Maintaining sets of cable components used for wired analysis, charging, or other interaction with portable electronic devices
EP3201846A1 (fr) 2014-10-02 2017-08-09 Ecoatm Inc. Kiosque activé sans fil pour le recyclage de dispositifs de consommateurs
EP3201885B1 (fr) 2014-10-02 2021-03-10 ecoATM, LLC Application pour l'évaluation de dispositif et d'autres procédés associés au recyclage de dispositif
US10445708B2 (en) 2014-10-03 2019-10-15 Ecoatm, Llc System for electrically testing mobile devices at a consumer-operated kiosk, and associated devices and methods
WO2016069742A1 (fr) 2014-10-31 2016-05-06 ecoATM, Inc. Procédés et systèmes pour faciliter des processus associés à des services d'assurance et/ou d'autres services pour dispositifs électroniques
CA3056457A1 (fr) 2014-10-31 2016-05-06 Mark Vincent Bowles Systemes et procedes pour recycler des dispositifs electroniques grand public
EP3215988A1 (fr) 2014-11-06 2017-09-13 Ecoatm Inc. Procédés et systèmes permettant d'évaluer et de recycler des dispositifs électroniques
CN105578461B (zh) 2014-11-10 2019-08-02 阿里巴巴集团控股有限公司 在移动终端间建立通讯、通讯接入/呼出方法、装置及系统
US11080672B2 (en) * 2014-12-12 2021-08-03 Ecoatm, Llc Systems and methods for recycling consumer electronic devices
CN105809251B (zh) * 2016-03-01 2018-01-30 北京交通大学 一种多属性融合的动车组系统关键部件辨识方法
US10269110B2 (en) 2016-06-28 2019-04-23 Ecoatm, Llc Methods and systems for detecting cracks in illuminated electronic device screens
US10521977B2 (en) * 2017-03-27 2019-12-31 GM Global Technology Operations LLC Methods and systems for integrated vehicle sensor calibration and maintenance
DE102017218703A1 (de) * 2017-10-19 2019-04-25 Continental Teves Ag & Co. Ohg Verfahren zur Wertbestimmung von Parametern
CN108982118A (zh) * 2018-07-25 2018-12-11 安徽江淮汽车集团股份有限公司 汽车诊断装置与vci设备自动连接方法及系统
CN109698862A (zh) * 2018-12-17 2019-04-30 深圳市道通科技股份有限公司 车辆的诊断方法、管理服务器和诊断服务器
AU2019404076A1 (en) 2018-12-19 2021-07-15 Ecoatm, Llc Systems and methods for vending and/or purchasing mobile phones and other electronic devices
AU2020222971A1 (en) 2019-02-12 2021-09-23 Ecoatm, Llc Connector carrier for electronic device kiosk
WO2020167846A1 (fr) 2019-02-12 2020-08-20 Ecoatm, Llc Kiosque pour évaluer et acheter des dispositifs électroniques usagés
JP2021530793A (ja) 2019-02-18 2021-11-11 エコエーティーエム, エルエルシー 電子デバイスの物理的状態評価に基づくニューラルネットワーク、および関連付けられるシステムおよび方法
CN113597545A (zh) * 2019-03-15 2021-11-02 Tvs电机股份有限公司 用于车辆的便携式无线连接诊断系统
CN111983989A (zh) * 2019-05-22 2020-11-24 北京新能源汽车股份有限公司 一种下线检测方法及控制设备
US11721140B2 (en) 2019-07-01 2023-08-08 Hunter Engineering Company System and method for presentation of remote vehicle diagnostics and service guidance through a local vehicle service system
US11872965B2 (en) * 2020-05-11 2024-01-16 Hunter Engineering Company System and method for gyroscopic placement of vehicle ADAS targets
US11922467B2 (en) 2020-08-17 2024-03-05 ecoATM, Inc. Evaluating an electronic device using optical character recognition
CN113341933B (zh) * 2021-06-23 2022-08-19 中国第一汽车股份有限公司 车用中央控制器的诊断系统及方法
CN113900428A (zh) * 2021-10-25 2022-01-07 深圳市元征科技股份有限公司 车辆诊断方法、诊断节点、设备及存储介质
EP4250688A1 (fr) * 2022-03-25 2023-09-27 Volvo Truck Corporation Procédé et dispositif de gestion des connexions pour un véhicule dans un atelier

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060052919A1 (en) * 2002-12-06 2006-03-09 Seok-Woo Hong System for collecting vehicle data and diagnosticating the vehicle using USB hard drive
WO2008127247A1 (fr) * 2007-04-13 2008-10-23 Robert Bosch Gmbh Gestion d'accès à une interface de communication de véhicule
WO2008127243A1 (fr) * 2007-04-16 2008-10-23 Robert Bosch Gmbh Enregistrement chronologique de données diagnostiques mises en réseau par plusieurs sources
US20090265055A1 (en) * 2008-04-17 2009-10-22 Winston Lynn Gillies System and method for performing automotive diagnostics
US20140188331A1 (en) * 2011-06-08 2014-07-03 Ramon Amirpour Mobile communication interface, system having a mobile communication interface, and method for identifying, diagnosing, maintaining, and repairing a vehicle

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4602127A (en) * 1984-03-09 1986-07-22 Micro Processor Systems, Inc. Diagnostic data recorder
DE4446512A1 (de) 1994-12-24 1996-06-27 Sel Alcatel Ag Vorrichtung zur Durchführung eines Fahrzeugtests oder zur Auswertung von Fahrzeugfehlern
GB2323183B (en) * 1997-03-07 2001-04-18 Honda Motor Co Ltd A process for diagnosing a plurality of vehicles
JP3345827B2 (ja) * 1997-03-07 2002-11-18 本田技研工業株式会社 車両診断装置
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
US6694235B2 (en) * 2001-07-06 2004-02-17 Denso Corporation Vehicular relay device, in-vehicle communication system, failure diagnostic system, vehicle management device, server device and detection and diagnostic program
US9117319B2 (en) * 2005-06-30 2015-08-25 Innova Electronics, Inc. Handheld automotive diagnostic tool with VIN decoder and communication system
US20070050105A1 (en) * 2005-08-31 2007-03-01 Spx Corporation Remote diagnostic data collections for automotive scan tools
US7920944B2 (en) * 2005-10-21 2011-04-05 General Motors Llc Vehicle diagnostic test and reporting method
DE102006018831A1 (de) * 2006-04-22 2007-10-25 Daimlerchrysler Ag Kraftfahrzeugdiagnose und Fahrzeugannahme
US20100324376A1 (en) * 2006-06-30 2010-12-23 Spx Corporation Diagnostics Data Collection and Analysis Method and Apparatus
US8239094B2 (en) * 2008-04-23 2012-08-07 Spx Corporation Test requirement list for diagnostic tests
CN201247152Y (zh) * 2008-08-29 2009-05-27 东北林业大学 一种小型柴油机转速信号发生与测试装置
CN102158162B (zh) 2011-01-27 2013-02-27 沈阳黎明航空发动机(集团)有限责任公司 一种航空发动机地面试车用交流电机加载控制装置
US8930064B2 (en) * 2011-10-27 2015-01-06 Snap-On Incorporated Method and system for automated and manual data capture configuration
KR20140113776A (ko) * 2013-03-13 2014-09-25 삼성전자주식회사 데이터 처리 방법 및 그 전자 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060052919A1 (en) * 2002-12-06 2006-03-09 Seok-Woo Hong System for collecting vehicle data and diagnosticating the vehicle using USB hard drive
WO2008127247A1 (fr) * 2007-04-13 2008-10-23 Robert Bosch Gmbh Gestion d'accès à une interface de communication de véhicule
WO2008127243A1 (fr) * 2007-04-16 2008-10-23 Robert Bosch Gmbh Enregistrement chronologique de données diagnostiques mises en réseau par plusieurs sources
US20090265055A1 (en) * 2008-04-17 2009-10-22 Winston Lynn Gillies System and method for performing automotive diagnostics
US20140188331A1 (en) * 2011-06-08 2014-07-03 Ramon Amirpour Mobile communication interface, system having a mobile communication interface, and method for identifying, diagnosing, maintaining, and repairing a vehicle

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DON GILMAN: "Flexible Diagnoseplattform - Modulare Plattform für die Kommunikation mit dem Fahrzeug", INTERNET CITATION, 1 January 2006 (2006-01-01), XP002462024, Retrieved from the Internet <URL:http://www.gilmanconsultinggroup.com/articles/VCI_hanser_automotive.pdf> [retrieved on 10770101] *

Also Published As

Publication number Publication date
US20140052329A1 (en) 2014-02-20
DE102011004205A1 (de) 2012-08-16
WO2012110263A1 (fr) 2012-08-23
US9087420B2 (en) 2015-07-21
CN103348230A (zh) 2013-10-09
EP2676115A1 (fr) 2013-12-25
CN103348230B (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
EP2676115B1 (fr) Système et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule
EP2718908B1 (fr) Interface de communication mobile, système ayant une interface de communication mobile et procédé d&#39;identification, de diagnostic, d&#39;entretien et de réparation d&#39;un véhicule
EP2721586B1 (fr) Procédé et système d&#39;établissement automatique d&#39;une liaison de communication avec un véhicule
WO2012110262A1 (fr) Interface de communication mobile, système équipé d&#39;une interface de communication mobile et procédé pour identifier, diagnostiquer, entretenir et réparer un véhicule
WO2012031814A1 (fr) Dispositif de surveillance de véhicule à moteur et procédé de surveillance de véhicule à moteur
EP2013060A1 (fr) Systeme de diagnostic avec module de transmission wlan et test court de diagnostic mis en uvre
EP2629268A2 (fr) Procédé de diagnostic et dispositif de diagnostic pour un composant de véhicule
DE10313467A1 (de) Verfahren zur Fehlerdiagnose und dabei einsetzbarer Datenprotokollwandler
EP2010979A1 (fr) Diagnostic de véhicule automobile et acceptation de véhicule
WO2001043079A1 (fr) Procede de reconnaissance de defauts d&#39;un vehicule automobile
EP3616180B1 (fr) Procédé pour la collecte de données
EP4147210A1 (fr) Procédé et dispositif de diagnostic pour effectuer des diagnostics de véhicule
WO2021084065A1 (fr) Système de gestion d&#39;une flotte de véhicules
DE102012011538A1 (de) Verfahren und System zur Telediagnose von Fahrzeugen
EP1597117B1 (fr) Dispositif et procede de diagnostic embarque central pour vehicules automobiles
DE102015214987B4 (de) Bestimmung eines defekten Bauteils eines Fahrzeugs
EP3252719A1 (fr) Procédé permettant de diagnostiquer des défaillances dans un véhicule et système correspondant
EP2284631A1 (fr) Procédé de fonctionnement d&#39;un système de diagnostic de véhicule, programme de commande et système de diagnostic de véhicule
DE10307344A1 (de) Vorrichtung und Verfahren zur dezentralen On-Board-Diagnose für Kraftfahrzeuge
DE102017217873A1 (de) Fahrzeug mit integriertem Fahrzeugdiagnosesystem
DE102016223973A1 (de) Konzept zum Prüfen eines Sensorsystems zum Erfassen eines Belegungszustands eines Stellplatzes auf Fehler
DE60004589T2 (de) Hilfsvorrichtung zur Diagnose einer Kraftfahrzeugstörung
DE102006017644B4 (de) Erfassung und Diagnose von Fahrzeugdaten
DE102018212173A1 (de) Kraftfahrzeug mit einer Steuervorrichtung für ein zentrales Flottenmanagement sowie Verfahren zum Einflotten des Kraftfahrzeugs in eine Fahrzeugflotte

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: 20130916

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)
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: 20170329

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ROBERT BOSCH GMBH

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502012016548

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G01M0015020000

Ipc: G07C0005080000

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

RIC1 Information provided on ipc code assigned before grant

Ipc: G07C 5/08 20060101AFI20200910BHEP

INTG Intention to grant announced

Effective date: 20201007

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

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502012016548

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1348465

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

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: 20201223

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: 20201223

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: 20210323

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: 20210324

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20201223

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: 20201223

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: 20201223

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: 20210323

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

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: 20201223

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20201223

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: 20201223

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: 20201223

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: 20210423

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: 20201223

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: 20201223

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: 20201223

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: 20201223

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502012016548

Country of ref document: DE

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: 20210109

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: 20210423

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: 20201223

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210131

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: 20201223

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210131

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

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: 20201223

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210131

26N No opposition filed

Effective date: 20210924

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: 20210109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 1348465

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20210423

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: 20210131

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230123

Year of fee payment: 12

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: 20120109

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230131

Year of fee payment: 12

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: 20201223

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20240322

Year of fee payment: 13

Ref country code: GB

Payment date: 20240124

Year of fee payment: 13