Method for diagnosing components using a diagnostic system and diagnostic system

Abstract

A microcontroller of a diagnostic system sends CAN (controller area network) messages to a component to be tested S3 and receives the message relayed back to the microcontroller by the component S4. A display device outputs CAN signals for monitoring S5. A diagnostic module initiates a query Q1 to determine if there are any faulty CAN signal readings. If the response is NO, it is determined that no issues exist with the component S6. If the response is YES, it is determined that a capture device is required to check for potential faults on the components. A database stores data about the query and the components for future reference, and a report generator creates reports based on the collected data. An interface may transmit the data to a third entity S8. The capture device may be an optical device such as a camera to visually inspect the component Z1.

Description

FIELD OF THE INVENTION

[0001] The present invention relates to the field of automobiles. More specifically, the present invention relates to a method for diagnosing components using a diagnostic system, wherein the components are used in the field of automobiles, according to claim 1. Furthermore, the present invention relates to a corresponding diagnostic system, a computer program product, and a corresponding non-transitory computer-readable storage medium. BACKGROUND INFORMATION

[0002] The patent document CN 213934045 U discloses a utility model relating to the field of unmanned driving vehicle test racks. This utility model presents an unmanned vehicle test rack system comprising a test bench and unmanned vehicle hardware. The unmanned vehicle hardware is installed on the test bench using a fixing device. The test bench is equipped with a detection unit and the unmanned vehicle hardware includes automatic driving hardware. The detection unit is equipped with a detection hardware interface and / or a detection wire harness to which the automatic driving hardware is connected. The primary purpose of the detection unit is to assess the functions of the automatic driving hardware. This embodiment allows for the detection of relevant components of the autopilot system of unmanned vehicles, thereby enhancing the overall product quality of unmanned vehicles and reducing the defect rate of the components.

[0003] Therefore, detection systems as diagnostic systems are known in the state of the art. SUMMARY OF THE INVENTION

[0004] It is an object of the invention to further develop a method in such a way that it enables a more efficient and better diagnosis with high quality for components of vehicles.

[0005] One aspect of the invention relates to a method for diagnosing components using a diagnostic system, comprising different steps. Therefore, the described method provides a systematic and technically precise approach for diagnosing components using the diagnostic system described below. It comprises a series of steps and features that ensure an efficient and accurate component assessment. The first step in this method involves the connection of a microcontroller of the diagnostic system to the component under the examination. The microcontroller serves as the central control unit responsible for communication. It sends controller area network CAN messages to the component, facilitating data exchange between the diagnostic system and the component. Upon receiving the CAN messages, the component relaying these messages back to the microcontroller. This bidirectional communication ensures interaction between the diagnostic system and the component, wherein the system outputs the CAN signals for the purpose of diagnosis. Following the data transmission and reception, a query is initiated. This query serves to ascertain whether any faulty readings exist within the CAN signals. It is a pivotal check point in the diagnostic process, where precision is of high importance. If the response to this query is NO, indicating the absence of faulty CAN signal readings, it is determined that no issues with the component under the examination. However, if the response is YES, indicating the presence of potential issues or problems, the system proceeds to the next phase, where further assessment is necessary.

[0006] In the event of a YES response, indicating potential issues, a capture device is activated. This capture device may take the form of either an optical capture device or a camera. Its primary function is to conduct a visual inspection of the components, focusing on aspects such as failed pins and solder points. Simultaneously, data regarding the query and the component is stored in an existing database. This data storage ensures that detailed records are maintained for future reference, adding an essential layer of traceability to the diagnostic process.

[0007] Following visual inspection, a secondary query is initiated to determine if a fault exists within the component itself. If the response to the secondary query is YES, indicating an internal fault within the component, a warning signal is promptly dispatched. This signal serves as an alert for manual intervention. A technician is then tasked with the responsibility of manually evaluating and investigating the identified faulty areas or problems, collecting data on the nature and extent of the issue or problem. If the response is NO, indicating the absence of an internal false, the diagnostic system proceeds with the diagnosis, knowing that the component itself is not the source of the problem.

[0008] Throughout these steps, collected data and information and relevant reports may be transmitted to a third entity, for example stakeholders, enhancing collaboration and decision-making processes. Additionally, CAN signals and corresponding information are systematically displayed on the system’s display for reference. This feature allows for real monitoring and analysis of the problems of the components.

[0009] In conclusion, this method is a precise and systematic approach to component diagnosis, enabling technical accuracy and data-driven decision-making. Its well-defined steps, query-based assessments, data storage and optional involvement of a capture device ensure a comprehensive and traceable evaluation process contributing to an efficient troubleshooting and enhanced component quality.

[0010] Another aspect of the invention relates to a diagnostic system for component testing, comprising a microcontroller for connecting and communicating with the component to be tested via CAN messages, and a component capable of receiving and relaying messages from the microcontroller. The diagnostic system also comprises a display device for outputting CAN signals for examination as a diagnostic module that initiates a query to determine if there are faulty CAN signal readings, wherein, if the response is NO, it records that there are no issues or problems with the components, and wherein, if the response is YES, it records that a capture device is required to check for potential faults in the components. This capture device may be an optical capture device or a camera. Furthermore, the diagnostic system comprises a database for storing collected data for future reference, wherein the database may be a part of the diagnostic system or may be connected to or be a database of an external server or cloud for example. The diagnostic system also comprises a report generator or module to create reports based on the collected data and an interface for transmitting the data to a third entity or stakeholders, wherein the diagnostic system may comprise an electronic computing device capable of reading the signals and prepare or create all data packages, information, and reports for further steps of any method worked out by the diagnostic system.

[0011] Further advantages, features, and details of the invention derive from the following description of preferred embodiments as well as from the drawings. The features and feature combinations previously mentioned in the description as well as the features and feature combinations mentioned in the following description of the figures and / or shown in the figures alone can be employed not only in the respectively indicated combination but also in any other combination or taken alone without leaving the scope of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The novel features and characteristic of the disclosure are set forth in the appended claims. The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and / or methods in accordance with embodiments of the present subject matter are now described below, by way of example only, and with reference to the accompanying figures.

[0013] The drawing shows in:

[0014] Fig. 1 a visual diagram illustrating a possible architecture for the component diagnosis method. DETAILED DESCRIPTION

[0015] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0016] While the disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawing and will be described in detail below. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

[0017] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion so that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus preceded by “comprises” or “comprise” does not or do not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

[0018] In the following detailed description of the embodiment of the disclosure, reference is made to the accompanying drawing that forms part hereof, and in which is shown by way of illustration a specific embodiment in which the disclosure may be practiced. This embodiment is described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0019] Fig. 1 shows a visual diagram illustrating a possible architecture for the component diagnosis method. The method begins with an initiation as a first step S1. A microcontroller is connected to the system in a second step S2 and sends out CAN messages to a specific component in a third step S3. In a fourth step S4, the microcontroller receives responses from the component, which are displayed for monitoring purposes in a fifth step S5.

[0020] At this stage, a critical first query Q1 is made asking, if there are any faulty readings in the CAN signals. If the answer is NO, it is determined in a sixth step S6, that there are no issues with the device or components being diagnosed or tested. Data from this success test is stored in an existing database for future reference in a seventh step S7. Moreover, comprehensive reports are generated based on the collected data and sent to relevant stakeholders as third entities in an eighth step S8, marking??making?? the conclusion of the testing method in a ninth step S9.

[0021] However, if the response of the query Q1 is YES, indicating that there are faulty CAN signal readings, a capture device or an optical capture device or a camera or a camera system is activated to visually inspect the component in a first error detection step Z1, specifically checking for potential issues such as failed pins or solder points.

[0022] Consequently, a secondary query Q2 is made, asking, if there is a fault within the component itself. If the response remains NO, the system determines that there are no issues or problems with the device or components, similar to the first scenario in the seventh step S7. Again, data is locked in the database for future reference, and reports are generated and shared with the third entity or stakeholders until the end in the ninth step S9.

[0023] In the event of a YES response to the second query Q2 happens, indicating an internal fault within the component, a technician manually evaluates and investigates the identified faulty areas, collecting data about the nature and extent of the issue in a second error detection step Z2.

[0024] Following this manual evaluation, the gathered dated is stored in the existing database for future reference in the subsequent known sixth step S6. As before, comprehensive reports are generated based on this data and distributed to the relevant stakeholders and the entities in the eighth step S8. This concludes the testing or diagnostic method, ensuring that any faults or issues or problems with the device or component are addressed and documented. In summary, a telematics hardware failure analysis is shown by this invention.

[0025] In the end, the method should be executable through a Diagnostic System for component testing.

[0026] In summary, the invention describes a Telematics Hardware Failure Analysis. Reference Signs S1 first step S2 second step S3 third step S4 fourth step S5 fifth step S6 sixth step S7 seventh step S8 eighth step S9 ninth step Z1 first error detection step Z2 second error detection step Yes YES No NO Q1 Query 1 Q2 Query 2

Claims

1. A method for diagnosing components using a diagnostic system, comprising the following steps:- connecting a microcontroller of the diagnostic system and sending CAN messages from the microcontroller to the component;- receiving the message by the component and relaying it back to the microcontroller;- outputting the CAN signals for diagnosis;- initiation of a query, inquiring if there are any faulty CAN signal readings, wherein, if the response is NO, it is determined that no issues exist with the component, and wherein, if the response is YES, it is determined that a capture device checks for potential faults on the components;- storing data about the query and the components in an existing database for future reference; and- generating reports based on the collected data.

2. Method according to claim 1, characterized in thata further query is initiated, asking if there is a fault in the component, wherein, if YES, a warning signal is sent out for manual evaluation and wherein, if NO, the method proceeds with the diagnosis.

3. Method according to claim 1 or 2, characterized in thatcollected data and / or reports are sent to a third entity.

4. Method according to any one of the preceding claims, characterized in thatCAN signals and corresponding information are displayed for reference on a display of the system.

5. Method according to any one of the preceding claims, characterized in thatthe capture device is an optical capture device or a camera.

6. Diagnostic system for component testing, comprising:- a microcontroller for connecting and communicating with the component to be tested via CAN messages;- a component capable of receiving and relaying messages from the microcontroller;- a display device for outputting CAN signals for examination;- a diagnostic module that initiates a query to determine if there are faulty CAN signal readings, wherein, if the response is NO, it records that there are no issues with the component, and wherein, if the response is YES, it records that a capture device is required to check for potential faults in the components;- a database for storing collected data for future reference;- a report generator or module to create reports based on the collected data; and - an interface for transmitting the data to a third entity.

7. A computer program product comprising program code means for performing a method according to any one of claims 1 to 6.

8. A non-transitory computer-readable storage medium comprising at least the computer program product according to claim 7.

Images