Communication error diagnosis device for vehicles, system and method having the device

Abstract

A communication error diagnosis device for a vehicle, a system including the communication error diagnosis device, and a method thereof are disclosed. The communication error diagnosis device includes: a processor configured to: send a request message including diagnostic identifiers of a plurality of controllers performing vehicle functions and sequence identifiers of the controllers according to a sequence of received response messages, and configured to analyze vehicle communication errors based on response messages received from the controllers; and a memory configured to store data and algorithms driven by the processor.

Description

Technical Field

[0001] The present invention relates to a communication error diagnosis device for vehicles, a system including the device and a method thereof, and more particularly, to a technique for diagnosing errors in low voltage differential signaling (LVDS) communication in vehicles. Background Technology

[0002] As vehicle technology advances, more diverse and sophisticated measurement and sensing functions are being provided to recently released vehicles. These sensing functions are controlled by the vehicle's electronic controller, or Electronic Control Unit (ECU).

[0003] Therefore, multiple controllers are installed in the vehicle to transmit and receive data between them, and diagnostics are required to verify the data quality.

[0004] However, traditionally, fault diagnosis is based on the ISO 14229-1 UDS integrated diagnostic service, and the LVDS fault diagnosis method is about to be implemented as a general function (0x22, 0x23) in addition to the safety target diagnostic service. This corresponds to the risk function (0x2E, 0x3D), where only certified diagnostic devices are allowed. In the general function, ReadDataByIndentifier (0x22) obtains the expected data (result value) from the controller through the diagnostic identifier (DID), and this ReadDataByIndentifier (0x22) is suitable for reading information related to a single controller. However, due to the limitation of I2C communication between controllers, it is impossible to ensure the security of LVDS image diagnostic data, and therefore there are limitations to LVDS fault diagnosis that requires image quality checks.

[0005] The information disclosed in the background section of this invention is intended only to enhance the understanding of the general background of the invention and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0006] Various aspects of the present invention aim to provide a communication error diagnostic apparatus for vehicles, a system including the apparatus, and a method thereof, configured to analyze vehicle-level error causes by diagnosing low-voltage differential signaling (LVDS) communication errors between multiple controllers in a vehicle, and to minimize the time required for error cause analysis.

[0007] The technical objectives of this invention are not limited to those described above, and those skilled in the art can clearly understand other unmentioned technical objectives through the description of the claims.

[0008] Various aspects of the present invention aim to provide a communication error diagnostic apparatus comprising: a processor configured to send a request message, including diagnostic identifiers of a plurality of controllers performing vehicle functions and sequence identifiers of the controllers, to the controllers according to a sequence of received response messages, and configured to analyze vehicle communication errors based on response messages received from the controllers; and a memory configured to store data and algorithms driven by the processor.

[0009] In various exemplary embodiments of the present invention, the request message may include a diagnostic identifier (DID), a sequence identifier (SID), and input variables for the SID.

[0010] In various exemplary embodiments of the present invention, DID may include at least one of the following: device connection information, line fault diagnosis service for diagnosing short circuits or disconnections in transmission lines, lockout identifier diagnosis service for diagnosing whether there is a connection between controllers in a vehicle system, ERRB identifier FWD channel diagnosis service for diagnosing whether bit errors occur in signals received from the receiver, ERRB identifier REV channel diagnosis service for diagnosing the occurrence of bit errors in signals received from the transmitter, and eye-opening monitor diagnosis service.

[0011] In various exemplary embodiments of the present invention, DID may include diagnostic start, diagnostic steps, and diagnostic end.

[0012] In various exemplary embodiments of the present invention, the response message may include DID, SID, and response result.

[0013] Various aspects of the present invention aim to provide a communication error diagnosis system comprising: a first controller configured to perform a first function of a vehicle; a second controller configured to perform a second function of the vehicle; and a communication error diagnosis apparatus configured to send a request message including a DID and SID for diagnosing the first controller to the first controller to receive a response message from the first controller, send a request message including a DID and SID for diagnosing the second controller to the second controller to receive a response message from the second controller, and analyze vehicle communication errors between the first controller and the second controller based on the response messages of the first controller and the second controller.

[0014] In various exemplary embodiments of the present invention, a first controller and a second controller may be included in a vehicle system, and a communication error diagnosis device outside the vehicle system may communicate with the first controller and the second controller.

[0015] In various exemplary embodiments of the present invention, the system may also include an on-board diagnostic (OBD) port configured to connect a communication error diagnosis device and a vehicle system.

[0016] In various exemplary embodiments of the present invention, the system may further include a gateway configured to communicate with a communication error diagnosis device in a first communication method and with a first controller and a second controller in a second communication method.

[0017] In various exemplary embodiments of the present invention, the first communication method may be D-HSCAN, and the second communication method may be Ethernet.

[0018] In various exemplary embodiments of the present invention, the communication error diagnosis device can send a request message including DID, SID and master role assignment for diagnosing the first controller to the first controller, and can receive a response message to the request message from the first controller.

[0019] In various exemplary embodiments of the present invention, the communication error diagnosis device can receive a response message from the first controller, and can then send a request message including DID, SID and role assignment for diagnosing the second controller to the second controller, and can receive a response message to the request message from the second controller.

[0020] In various exemplary embodiments of the present invention, the communication error diagnosis device may send a request message to the first controller to check the setting of a first parameter for diagnostic preparation of the first controller, and

[0021] You can receive response messages to request messages from the first controller.

[0022] In various exemplary embodiments of the present invention, the communication error diagnosis device may receive a response message from the first controller, and may then send a request message to the second controller to check the setting of a second parameter for diagnostic preparation of the second controller, and may receive a response message to the request message from the second controller.

[0023] In various exemplary embodiments of the present invention, when the communication error diagnosis device checks the settings of the first parameter of the first controller and the second parameter of the second controller, it may send a request message to the second controller, which is a slave device, requesting the setting of the third parameter of the second controller to perform diagnosis, and may receive a response message to the request message from the second controller.

[0024] In various exemplary embodiments of the present invention, the second controller may include a value in the response message that can distinguish between normal and fault states, and may send the message to the communication error diagnosis device.

[0025] In various exemplary embodiments of the present invention, the communication error diagnosis device may send a request message to the first controller, which is the master device, to request the setting of a fourth parameter for performing diagnosis, and the first controller may set the fourth parameter and de-set the fourth parameter after performing diagnosis.

[0026] In various exemplary embodiments of the present invention, the first controller may send the diagnostic results of the first controller to the communication error diagnostic device.

[0027] In various exemplary embodiments of the present invention, when receiving diagnostic results from the first controller and the second controller, the communication error diagnostic device may send a request message for requesting termination of the diagnosis of the second controller to the second controller. When receiving a response message to the request message from the second controller, the device may send a request message for requesting termination of the diagnosis of the first controller to the first device. And when receiving a response message to the request message from the first controller, the communication error diagnostic device may terminate the diagnostic process.

[0028] Various aspects of the present invention aim to provide a communication error diagnosis method, comprising: sending a request message including a DID and SID of a first controller for diagnosing a first function of a vehicle to a first controller; receiving a response message from the first controller; sending a request message including a DID and SID of a second controller for diagnosing a second function of a vehicle to a second controller; receiving a response message from the second controller; and analyzing vehicle communication errors between the first controller and the second controller based on the response messages of the first controller and the second controller.

[0029] According to this technology, vehicle-level error causes can be analyzed and error cause analysis can be minimized by diagnosing low-voltage differential signaling (LVDS) communication errors between multiple controllers in a vehicle.

[0030] In addition, it can provide various effects that can be directly or indirectly identified through this file.

[0031] The methods and apparatus of the present invention have other features and advantages, which will become apparent from the accompanying drawings and the following detailed description, or are set forth in more detail in the drawings, which together serve to explain certain principles of the invention. Attached Figure Description

[0032] Figure 1 A block diagram is shown illustrating the configuration of a diagnostic system including a communication error diagnostic device for a vehicle, according to various exemplary embodiments of the present invention.

[0033] Figure 2Detailed schematic diagrams of a communication error diagnosis device for a vehicle according to various exemplary embodiments of the present invention are shown.

[0034] Figure 3 Detailed diagrams illustrating the configuration of a diagnostic system including a communication error diagnostic device for a vehicle, according to various exemplary embodiments of the present invention.

[0035] Figure 4 Screen examples illustrating screen configurations for a communication error diagnosis device for a vehicle according to various exemplary embodiments of the present invention.

[0036] Figure 5 An example screen showing a diagnostic selection menu for a communication error diagnostic device for a vehicle according to various exemplary embodiments of the present invention is shown.

[0037] Figure 6 The diagnostic process for BIST of a serial link sequence is illustrated schematically according to various exemplary embodiments of the present invention.

[0038] Figure 7 A flowchart illustrating a communication error diagnosis method for a vehicle according to various exemplary embodiments of the present invention is shown.

[0039] Figure 8 The diagram schematically illustrates the diagnostic process for line faults according to various exemplary embodiments of the present invention.

[0040] Figure 9 The diagnostic process for a locking identifier according to various exemplary embodiments of the present invention is illustrated schematically.

[0041] Figure 10 The diagnostic process for the forward channel of the ERRB identifier is illustrated schematically according to various exemplary embodiments of the present invention.

[0042] Figure 11 The diagnostic process for the ERRB identifier REV channel is illustrated schematically according to various exemplary embodiments of the present invention.

[0043] Figure 12 The diagnostic process for link margin testing according to various exemplary embodiments of the present invention is illustrated schematically.

[0044] Figure 13 The diagnostic process of an eye-opening monitor according to various exemplary embodiments of the present invention is illustrated schematically.

[0045] Figure 14 The diagnostic process of error correction by retransmission counting is illustrated schematically according to various exemplary embodiments of the present invention.

[0046] Figure 15A computing system according to various exemplary embodiments of the present invention is shown.

[0047] It is understood that the accompanying drawings are not necessarily drawn to scale, and present slightly simplified representations of various features illustrating the basic principles of the invention. Specific design features of the invention disclosed herein (including, for example, specific dimensions, orientations, positions, and shapes) will be determined in part by the particular intended application and environment of use.

[0048] In the accompanying drawings, in several figures, reference numerals refer to parts that are the same as or equivalent to the present invention. Detailed Implementation

[0049] Reference will now be made in detail to one or more various embodiments of the invention, examples of which are illustrated in the accompanying drawings and described below. While one or more embodiments of the invention will be described in conjunction with exemplary embodiments thereof, it should be understood that this description is not intended to limit the one or more inventions to those exemplary embodiments. On the other hand, one or more inventions are intended to cover not only the exemplary embodiments thereof, but also various alternatives, modifications, equivalents and other embodiments that may be included within the spirit and scope of the invention as defined in the appended claims.

[0050] In the following, some exemplary embodiments of the present invention will be described in detail with reference to the exemplary accompanying drawings. It should be noted that when a reference numeral is attached to the constituent elements of each figure, even if the same constituent element is represented in different figures, the same reference numeral will be used as much as possible. Furthermore, when describing exemplary embodiments of the present invention, detailed descriptions of related well-known configurations or functions will be omitted if it is determined that such detailed descriptions interfere with the understanding of exemplary embodiments of the present invention.

[0051] In describing the constituent elements according to various exemplary embodiments of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are used only to distinguish a constituent element from other constituent elements, and the nature, sequence, or order of the constituent elements is not limited by these terms. Furthermore, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which the various exemplary embodiments of the present invention pertain. Unless expressly defined in the exemplary embodiments of the present invention, terms defined in commonly used dictionaries should be interpreted as having meanings that correspond to those meanings in the context of the relevant field and should not be interpreted as having idealized or overly formalized meanings.

[0052] In the following text, reference will be made to Figures 1 to 15 Various exemplary embodiments of the present invention will be described in detail below.

[0053] Figure 1 The diagram illustrates the configuration of a diagnostic system including a communication error diagnostic device for a vehicle, according to various exemplary embodiments of the present invention. Figure 2 Detailed schematic diagrams of a communication error diagnosis device for a vehicle according to various exemplary embodiments of the present invention are shown. Figure 3 Detailed diagrams illustrating the configuration of a diagnostic system including a communication error diagnostic device for a vehicle, according to various exemplary embodiments of the present invention.

[0054] refer to Figure 1 A communication error diagnosis system for a vehicle according to various exemplary embodiments of the present invention may include a communication error diagnosis device 100 for a vehicle and a vehicle system 200.

[0055] The communication error diagnosis device 100 according to various exemplary embodiments of the present invention can be implemented as a stand-alone device outside the vehicle, and can be implemented as shown in the figure. Figure 3 The on-board diagnostic (OBD) port 300 shown is connected to the vehicle system 200. In this example, the communication error diagnostic device 100 can be connected to the OBD port 300 via D-HSCAN.

[0056] The communication error diagnosis device 100, serving as an external diagnostic test (EDT), may include smartphones, tablet computers (PCs), mobile phones, video phones, e-book readers, netbooks, personal digital assistants (PDAs), portable multimedia players (PMPs), mobile communication terminals, e-notebooks, etc., and may be equipped with vehicle interactive applications that interact with the vehicle system 200. The interactive applications can be downloaded wirelessly or via the internet, and can be automatically installed after download.

[0057] The communication error diagnosis device 100 can sequentially acquire image diagnostic data from multiple controllers using ReadMemoryByAddress(23h) and display the diagnostic results on the screen. In this example, ReadMemoryByAddress(23h) is a diagnostic service that performs each diagnostic function, a diagnostic identifier (DID) identifies the diagnostic function, and a sequence identifier (SID) includes control over the diagnostic process.

[0058] The communication error diagnostic device 100 sends diagnostic commands to the controller in a predetermined sequence. According to the UDS diagnostic specification, the communication error diagnostic device 100 uses D-HSCAN to send diagnostic commands (controller ID, 0x23, DID, setting value) for diagnosing the target controller. The controller ID is a unique controller number in the vehicle. "0x23" represents the ReadMemoryBy Address in the UDS diagnostic service. The DID represents the diagnostic identifier, and the setting value represents the SID and diagnostic attribute value.

[0059] Vehicle system 200 may include gateway 210, multiple controllers 221 and 222, and cameras 231 and 232 connected to controllers 221 and 222. Communication error diagnosis device 100 in various exemplary embodiments of the present invention can perform diagnostics on data transmission and reception between controllers 221 and 222.

[0060] The communication error diagnosis device 100 is connected to the gateway 210 via the OBD port 300 and can be connected in D-HSCAN mode.

[0061] The gateway 210 for the vehicle may be equipped with a predetermined diagnostic communication interface module, and may communicate with an external communication error diagnostic device 100 for the vehicle via the diagnostic communication interface module. In this document, the diagnostic communication interface module may provide at least one of the following: Ethernet communication functionality, Bluetooth communication functionality, Wi-Fi communication functionality, Near Field Communication (NFC) communication functionality, Wideband Code Division Multiple Access (WCDMA) communication functionality, Long Term Evolution (LTE) communication functionality, or LTE-Advanced communication functionality.

[0062] That is, the gateway 210 can convert the diagnostic commands of the communication error diagnosis device 100 input via D-HSCAN into HSCAN, CANFD and Ethernet formats according to the communication method of the target controller, and the controller communication method may be different for each vehicle model.

[0063] Multiple controllers 221 and 222 may include controllers that respectively implement Remote Smart Parking Assist (RSPA), Advanced Driver Assistance Systems (ADAS), Forward Collision-Avoidance Assist (FCA), Lane Keeping Assist (LKA), Blind Spot Collision-Avoidance Assist (BCA), Smart Cruise Control (SCC), Surround View Monitor (SVM), Head-Up Display (HUD), etc. Currently, controllers 221 and 222 can be implemented in a combination of hardware and software, and may be, for example, an Electronic Control Unit (ECU), a Microcontroller Unit (MCU), a Central Processing Unit (CPU), or other sub-controllers installed in the vehicle. In various exemplary embodiments of the invention, for ease of description, the controller will be described as an ECU.

[0064] Furthermore, controllers 221 and 222 may include one or more application processors (APs), serializers (SERs), or deserializers (DESs). The application processor (AP), acting as a central processing unit, can implement the functions of the corresponding controller, and the SER can transmit signals, while the DES can receive signals from the SER. (See reference) Figure 3 Multiple controllers, ECU1, ECU2, ECU3, and ECU4, send and receive data to each other. In this example, because it was previously impossible to diagnose the data transmitted and received between controllers, this invention aims to diagnose the data transmitted and received between controllers.

[0065] When each of the multiple controllers 220, ECU1, ECU2, ECU3, and ECU4 is selected as a diagnostic target, the controller's diagnostic register value is set according to the function to be performed (DID). The controller with the set diagnostic register value then performs the diagnostic according to the function and records the results in the diagnostic register. Controller 220 can send the collected diagnostic results (controller ID, 0x63, DID, result value) to gateway 210, and gateway 210 can send its diagnostic results to communication error diagnostic device 100 via D-HSCAN.

[0066] for Figure 3 In the diagnostic process, the communication error diagnostic device 100 sends (①) a diagnostic command (controller ID, 0x23, DID, setting value) to the vehicle system 200, and (②) a diagnostic command to the selected controller via the gateway 210 of the vehicle system 200 (③). In this example, the controller ID represents information related to the selected controller, "0x23" represents ReadMemoryByAddress(23h) as a diagnostic service item, DID means diagnostic identifier, and the setting value represents the parameter value used to prepare for or perform the diagnostic. Request frame messages containing such information will be described in detail with reference to Table 1.

[0067] Therefore, the controller receiving the diagnostic command sets the parameters (④) for the diagnostic and performs the diagnostic (⑤). Then, the controller performing the diagnostic collects (⑥) the diagnostic results and sends (⑦) the diagnostic results to the communication error diagnostic device 100 outside the vehicle, and the communication error diagnostic device 100 displays (⑧) the diagnostic results (controller ID, 0x63, DID, result value). In this example, the diagnostic results will be described in detail later with reference to Table 2.

[0068] Therefore, the communication error diagnosis device 100 in various exemplary embodiments of the present invention can send and receive communication performance verification data between controllers through diagnostic communication, and can verify problems that occur in LVDS image communication.

[0069] refer to Figure 2 The communication error diagnosis device 100 may include a communication device 110, a memory 120, a display device 130, and a processor 140.

[0070] The communication device 110 can communicate wirelessly or wiredly with the vehicle system 200, and can perform, for example, D-HSCAN communication.

[0071] The memory 120 may store data and / or algorithms required for the processor 140 to run.

[0072] For example, memory 120 can store algorithms and data used for diagnostics. Furthermore, memory 120 can store information related to the on-board controller configured for diagnostics.

[0073] The memory 120 may include at least one type of storage medium, such as flash memory, hard disk, microprocessor, card (e.g., Security Digital (SD) card or Ultimate Digital (XD) card), random access memory (RAM), static RAM (SRAM), read-only memory (ROM), programmable ROM (PROM), electrically erasable PROM (EEPROM), magnetic RAM (MRAM), disk, or optical disk.

[0074] Display device 130 may include input tools for receiving control commands from a user and output tools for outputting the operating status and results of output device 100. Hereinafter, input tools may include buttons, and may include a mouse, joystick, rotary joystick, stylus, etc. Furthermore, input devices may include soft keys implemented on the display.

[0075] Output devices may include a display and may also include voice output tools such as speakers. In this example, when a touch sensor formed by a touch film, touchpad, or touch pad is provided on the display, the display can function as a touchscreen and can be implemented in a manner in which the input device and output device are integrated.

[0076] In this example, the display may include at least one of the following: a liquid crystal display (LCD), a thin-film transistor liquid crystal display (TFTLCD), an organic light-emitting diode display (OLED display), a flexible display, a field emission display (FED), or a 3D display. Specifically, in various exemplary embodiments of the present invention, the display device 130 may display a diagnostic request menu and diagnostic execution results.

[0077] Figure 4 Screen examples illustrating screen configurations of a vehicle communication error diagnosis device according to various exemplary embodiments of the present invention, and Figure 5The following is a screen example illustrating the screen configuration diagnostic selection menu of a vehicle communication error diagnostic device according to various exemplary embodiments of the present invention.

[0078] refer to Figure 4 When the communication error diagnosis device 100 performs its diagnostic algorithm, a diagnostic session control message is transmitted to the vehicle controller. The LVDS controller is checked using the response ID received from the vehicle controller, and the connection information associated with the corresponding controller (such as...) is also checked. Figure 4 As shown, the controller for the LVDS video communication application connection is displayed on the left side of the screen of the display device 130, and the topology is displayed on the right side, so that the connection relationship can be known.

[0079] refer to Figure 5 The display device 130 displays a screen for selecting diagnostic links and desired diagnostic functions, and when the user presses the corresponding function (e.g., test) menu, the communication error diagnostic device 100 sends a corresponding diagnostic message to perform the diagnosis. Furthermore, the display device 130 displays the received diagnostic results.

[0080] The processor 140 can be electrically connected to the communication device 110, the memory 120, the display device 130, etc., and can electrically control each component. It can also be a circuit that executes software commands, performs various data processing and calculations.

[0081] The processor 140 can process signals transmitted between components of the communication error diagnosis device 100 and can act as an overall controller, enabling each component to perform its function correctly.

[0082] The processor 140 may be implemented in hardware, software, or a combination of hardware and software, or it may be implemented as a microprocessor.

[0083] Based on the sequence of received response messages, the processor 140 can send a request message to the controller, including a diagnostic identifier for the controller performing vehicle functions and a sequence identifier for the controller, and can analyze communication errors based on the response messages received from the controller.

[0084] In this example, the request message may include DID, SID, and input variables for SID.

[0085] In addition, the response message may include DID, SID, and response result.

[0086] (Table 1)

[0087] Request Frame

[0088]

[0089] (Table 2)

[0090] Response Frame

[0091]

[0092] Table 1 is a list of diagnostic services used for LVDS diagnostics. Table 1 is an example of a request frame message sent by the communication error diagnostic device 100 for diagnostic purposes. Table 2 is an example of a response frame message sent from the controller to the communication error diagnostic device 100.

[0093] Referring to Table 1, as a request frame message structure for requesting information from the Communication Error Diagnostic Device (EDT) 100 to the controller (ECU), the request frame message may include fields such as UDS service, ALFID (addressAndLengthFormatIdentifier), memory address, and memory size. Specifically, the memory address includes VADD (virtual address), DID, SID, and a parameter. VADD represents the name of the LVDS test, DID represents the diagnostic list (see Table 3 below), SID represents the sequence identifier (see Table 4 below), and the parameter represents the SID input variable. Although DID_LBIST is described as a DID value in Table 1, one of the DID values ​​in Table 3 can be described as an example. Furthermore, the VADD (virtual address) of the memory address field is a virtual address indicating the LVDS diagnostic interface (LVDS_TEST) and is a predefined unique value (e.g., 0x2020). When the ALFID (addressAndLengthFormatIdentifier) ​​and DID values ​​are input as a message, the ECU recognizes the LVDS fault diagnosis request (e.g., 23X02020). In ALFID (addressAndLengthFormatIdentifier), the bottom 4 bits (memory address) are always 0, and the top 4 bits (memory size) are the memory size of the subsequent input value, and a maximum of 15 bytes are supported.

[0094] Table 2 shows the response format structure, and the response value (return value) varies according to the SID. In this example, when the response value is 0, the controller is in a normal state; any other value can be considered an error, and cases where specific values ​​(ErrorCount, etc.) are specified can be excluded.

[0095] In addition, DID may include at least one of the following: device connection information; line fault diagnosis service for diagnosing short circuits or disconnections in transmission lines; lockout identifier diagnosis service for diagnosing whether a connection has been established between controllers in a vehicle system; ERRB identifier forward channel diagnosis service for diagnosing whether bit errors have occurred in signals received from the receiver; ERRB indicator reverse channel diagnosis service for diagnosing whether bit errors have occurred in signals received from the transmitter; or eye-opening monitor diagnosis service.

[0096] (Table 3)

[0097] DID value

[0098]

[0099]

[0100] (Table 4)

[0101] Serial Identifier (SID)

[0102]

[0103] Table 3 is a table showing examples of DID values, and Table 4 is a table showing examples of SID values.

[0104] Referring to Table 3, the DID indicates the supported DIDs, such as DID_LIF, DID_LLF, ... and DID_LECR.

[0105] DID_LIF represents device connection information, and when represented by a HEX value, it becomes A001. DID_LLF indicates a line fault, DID_LLI indicates a lockout identifier, DID_LEIFC ERRB indicates the FWD channel identifier, DID_LEIRC indicates the REV channel identifier ERRB, DID_LBIST indicates the serial link BIST, DID_LEOM indicates the open-eye monitor, DID_LLMT indicates the link margin test, and DID_LECR indicates error correction via retransmission.

[0106] In this example, within the DID, DID_LIF, DID_LLI, DID_LEIFC, DID_LEIRC, DID_LEOM, and DID_LECR perform individual controller diagnostics, such as... Figures 8 to 14 As shown, for DID_LBIST and DID_LLMT, diagnostics are performed between multiple controllers. The DID_LBIST diagnostic service will be discussed later. Figure 4 Detailed description.

[0107] Table 4 shows the SIDs that depend on the DIDs in Table 3, and the SIDs include only SID_TSRT and SID_TF, or SID_STEP1, ..., and SID_STEP# can be added. Furthermore, parameters can be set based on the SID.

[0108] CH# information is sent as a parameter in the request frame, and CH# or result information is sent as a parameter in the response frame.

[0109] Set the target diagnostic controller as the master and the relative controller as the slave, and combine the master or slave configuration information with the channel information (CH#) of the target diagnostic controller. For master or slave configuration, the MSB is 0 for master and 1 for slave. Only use the DID that needs to be specified by the master or slave; no other special distinction is required.

[0110] For example,

[0111] [Slave]: CH#[7] bit, which is a slave device when MSB is 1.

[0112] [ChannelNo]: The channel number transmitted is diagnosed by the Ch#[6:0] bits.

[0113] (Table 5)

[0114] BIST for Serial Link Messages

[0115]

[0116]

[0117] Table 5 shows examples of request and response messages for BIST used in serial link messages in the DID of Table 3.

[0118] Referring to Table 5, MemorySize is 0 (unused), and MemoryAddress includes the virtual address, DID, SID, and parameters, which are LVDS_TEST, DID_LBIST, and SID_, respectively. LVDS_TEST can be a unique value specifying the LVDS diagnostic test (e.g., 0x2020), DID_LBIST can be the DID of the currently being diagnosed test, and SID_ can be the processing sequence during the current DID diagnosis. This parameter can also include the channel number, etc.

[0119] Figure 6 The diagnostic process for BIST of a serial link sequence is illustrated schematically according to various exemplary embodiments of the present invention.

[0120] refer to Figure 6The diagnostics begin with DID_LBIST and SID_TSRT (Test Start) and end with DID_LBIST and SID_TF (Test Complete). The SID_TSRT parameter sets the target controller as the master and the other controller as the slave.

[0121] The communication error diagnosis device (EDT) 100 can assign roles to controllers ECU1 and ECU2 (S601).

[0122] The communication error diagnosis device (EDT) 100 sends a request frame message including "23 60LVDS_TEST DID_LBIST SID_TSRT[Master=00:CH#]" to ECU1, and in response, ECU1 sends "63 04DID_LBISTSID_TSRT[Master:CH]#]" to the EDT. That is, the communication error diagnosis device (EDT) 100 designates ECU1 as the master device, and ECU1 responds by assuming the role of the master device. Before diagnosis, it is necessary to know the channel information of the corresponding controller and the configuration information of other controllers, and to specify the channel for both via SID_TSRT.

[0123] In this example, the communication error diagnostic device (EDT) 100 and the controllers ECU1 and ECU2 can transmit and receive data via the vehicle gateway 210.

[0124] Therefore, the communication error diagnosis device (EDT) 100 sends a request frame message including "23 60LVDS_TEST DID_LBIST SID_TSRT[Slave=80:CH#]" to ECU2, and in response, ECU2 sends "63 04DID_LBISTSID_TSRT[Slave:CH#]" to the EDT. That is, the communication error diagnosis device (EDT) 100 designates ECU2 as a slave device, and ECU2 responds by acting as a slave device.

[0125] The communication error diagnostic device (EDT) 100 sequentially sends and acknowledges diagnostic setting value confirmation request messages (S602) to multiple controllers ECU1 and ECU2 for performing diagnostics. In the following text, SID_STEP# refers to the step of setting the register for each controller based on the SID.

[0126] The communication error diagnostic device (EDT) 100 sends a request frame message including "23 50LVDS_TEST DID_LBIST SID_STEP1 (Check paraml)" to ECU1 to check the setting of paraml, where paraml is a parameter that can be set to perform diagnostics. In response, ECU1 sends "63 04DID_LBIST SID_STEP1 00" to the EDT. That is, since the communication error diagnostic device (EDT) 100 can request to check whether ECU1 has set param1, and ECU1 responds by sending "00" to the request to confirm that param1 has been set, the communication error diagnostic device 100 can check that the controller ECU1 is ready to perform diagnostics.

[0127] Therefore, the communication error diagnostic device (EDT) 100 sends a request frame message including "23 50LVDS_TEST DID_LBIST SID_STEP2 (checking param2)" to the ECU2 to check the setting of param2, which is a parameter that can be set to perform diagnostics. In response, the ECU2 sends "63 04DID_LBIST SID_STEP2 00" to the EDT. That is, since the communication error diagnostic device (EDT) 100 can request to check whether the ECU2 has set param2, and the ECU2 responds by sending "00" to the request to set param2, the communication error diagnostic device 100 can check that the controller EUC2 is ready to perform diagnostics.

[0128] The communication error diagnosis device (EDT) 100 sequentially sends a diagnosis start message to the controllers ECU1 and ECU2, and begins fault diagnosis (S603).

[0129] The communication error diagnostic device (EDT) 100 sends a request frame message including "23 50LVDS_TEST DID_LBIST SID_STEP3 (setting parameter 3)" to the ECU2 to check the setting of param3, which is a parameter that can be set to begin diagnostics. In response, the ECU2 sends "63 04DID_LBIST SID_STEP3 00" to the EDT. That is, since the communication error diagnostic device (EDT) 100 can request the ECU2 to set param3, and the ECU2 responds by setting param3 by sending "00" to the request, the communication error diagnostic device 100 can check that the diagnostics of the controller EUC2 have been performed.

[0130] Therefore, the Communication Error Diagnostic Device (EDT) 100 sends a request frame message including "23 50LVDS_TEST DID_LBIST SID_STEP4 (set param4)" to ECU2 to check the setting of param4. param4 is a parameter that can be set to perform diagnostics, and ECU2 sets param4 and removes it after the diagnostic is completed or after a predetermined time period. In this example, ECU1, as the master device, can be set to a preset value and automatically removed. Then, ECU1 transmits "63 04DID_LBISTSID_STEP4 ErrorCount" to the EDT. In this example, a result of "00" indicates normal operation, and a result of "ErrorCount" indicates a fault condition. Figure 6 When ECU1 responds with "ErrorCount" to the communication error diagnostic device (EDT) 100, the communication error diagnostic device (EDT) 100 can know that ECU1 is in a fault state.

[0131] At the same time, the communication error diagnostic device (EDT) 100 sends “23 50LVDS_TEST DID_LBIST SID_STEP5(releasing param3)” to the ECU2 that sets param3 to request the release of param3, and in response, the ECU2 releases the setting of param3 by transmitting “63 04 DID_LBIST SID_STEP5 00”.

[0132] The communication error diagnostic device (EDT) 100 can display and report the diagnostic results of controllers ECU1 and ECU2 on the screen (S604). When the diagnosis is complete and the result values ​​are checked, the communication error diagnostic device (EDT) 100 sends SID_TF to end the diagnosis and complete all diagnostics.

[0133] That is, the communication error diagnostic device (EDT) 100 sends “23 60LVDS_TEST DID_LBIST SID_TF[Slave=80:CH#]” to ECU2 to end the diagnostic, and in response, ECU2 sends “63 05DID_LBIST SID_TF[Slave:80:CH#]00” to the communication error diagnostic device (EDT) 100, thereby ending the diagnostic of ECU2.

[0134] In addition, the communication error diagnostic device (EDT) 100 sends “23 60LVDS_TEST DID_LBIST SID_TF[Master=00:CH#]” to ECU2 to end the diagnostic, and in response, ECU2 sends “63 05DID_LBIST SID_TF[Master:CH#]00” to the communication error diagnostic device (EDT) 100, thereby ending the diagnostic of ECU1.

[0135] Therefore, by sequentially controlling controllers ECU1 and ECU2, the communication error diagnosis device (EDT) 100 can determine whether there are any anomalies in the image data exchanged between controllers ECU1 and ECU2.

[0136] Therefore, according to various exemplary embodiments of the present invention, image quality can be rapidly diagnosed and responded to at the vehicle level, thereby increasing the reliability of the system.

[0137] In the following text, reference will be made to Figure 7 A method for diagnosing communication errors in vehicles according to various exemplary embodiments of the present invention is described in detail. Figure 7 A flowchart is shown, illustrating a method for diagnosing communication errors in a vehicle according to various exemplary embodiments of the present invention.

[0138] In the following text, it is assumed that... Figure 1 The communication error diagnosis device 100, gateway 210, and controllers ECU1 and ECU2 perform... Figure 7 The process. Furthermore, in Figure 7 In the description, the operation described as being performed by the communication error diagnosis device 100 can be understood as being controlled by the processor 140 of the communication error diagnosis device 100.

[0139] The communication error diagnostic device 100 sends a diagnostic command (S101). According to the UDS diagnostic specification, the communication error diagnostic device 100 sends a diagnostic command (controller ID, 0x23, DID, setting value) for diagnosing the target controller using D-HSCAN. The controller ID is a unique controller number in the vehicle. "0x23" represents the ReadMemoryBy Address in the UDS diagnostic service. The DID represents the diagnostic identifier, and the setting value represents the SID and diagnostic attribute value.

[0140] Gateway 210 converts the communication rules used for diagnostic commands (S102). That is, according to the communication method of the target controller, gateway 210 converts the diagnostic commands of the communication error diagnostic device 100 input via D-HSCAN into HSCAN, CANFD and Ethernet formats.

[0141] The communication error diagnosis device 100 selects the target controller for diagnosis (S103). In this example, the target controller is selected based on the controller ID according to the UDS diagnosis specification.

[0142] The diagnostic target controller that receives the diagnostic command performs diagnostic settings (S104). That is, based on the function to be executed (DID), the diagnostic target controller that receives the diagnostic command sets the diagnostic register value of the controller.

[0143] The controller with the diagnostic register value set performs a diagnostic (S105). That is, the controller with the diagnostic register value set performs a diagnostic based on the function and records the result in the diagnostic register.

[0144] The communication error diagnosis device 100 determines whether the response waiting time from the control target controller has been exceeded (S106), and resets the controller when it is exceeded (S110).

[0145] That is, if a predetermined response waiting time exceeds the time elapsed after sending a diagnostic command to the controller, the communication error diagnostic device 100 determines that a problem exists, sends an ECU reset request command (0x11) to the controller, and completes the diagnostic upon receiving a reset response result (0x51). Furthermore, when a diagnostic cannot be performed due to a problem in the controller, the communication error diagnostic device 100 can request a reset from the controller. For example, if there is no response during testing or when the diagnostic cannot be performed normally, the communication error diagnostic device 100 can request a reset. In this example, the controller can use a soft reset of the reset type.

[0146] Simultaneously, when the response waiting time from the target controller has not been exceeded, that is, when the response arrives within the response waiting time, the communication error diagnosis device 100 collects the diagnosis result from the controller 220 (S107). That is, the communication error diagnosis device 100 sends a diagnosis command to read the diagnosis result recorded in the diagnosis register, and thereby diagnoses the target controller to collect the result value.

[0147] The controller 220 sends the collected diagnostic results (controller ID, 0x63, DID, result value) to the gateway 210 (S108), and the gateway 210 sends its diagnostic results to the communication error diagnosis device 100 via D-HSCAN (S109).

[0148] Therefore, according to various exemplary embodiments of the present invention, in cases where it is difficult to obtain LVDS image diagnostic data due to limited I2C communication between controllers, the external vehicle data diagnostic device 100 can obtain image diagnostic data from multiple controllers by using ReadMemoryByAddress(23h).

[0149] Figure 8 The diagram schematically illustrates the diagnostic process for line faults according to various exemplary embodiments of the present invention.

[0150] The line fault diagnosis service functions as follows: it notifies whether there is a battery short circuit, ground (GND) short circuit, or disconnection on the transmission line between Ser and Des. When a line fault error occurs, the SER / DES error pin output goes low.

[0151] For line fault diagnosis, DID_LLF (see Table 4) is used for the DID in Table 3. SIDs can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be used as user-defined values.

[0152] Figure 9 The diagnostic process for a locking identifier according to various exemplary embodiments of the present invention is illustrated schematically.

[0153] The lock identifier is a function used to check whether the Ser and Des connection has been established. When a disconnection occurs between Ser and Des using the LOCK pin, the output goes low, and it returns high when the connection is restored.

[0154] DID_LLI (see Table 4) is the DID used as the lock identifier. The SID can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be set by the user.

[0155] Figure 10 The diagnostic process for the forward channel of the ERRB identifier is illustrated schematically according to various exemplary embodiments of the present invention.

[0156] Information related to the ERRB identifier FWD channel can be received through the diagnostic service of the ERRB identifier FWD channel. The ERRB identifier FWD channel functions as follows: when a signal received from the deserializer's receiver experiences a bit error and exceeds a value specified by accumulating and storing the corresponding value in a register, the ERRB pin is changed to 1.

[0157] DID_LEIFC (see Table 3) is the DID for the ERRB identifier FWD channel. The SID can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be set by the user.

[0158] Figure 11 The diagnostic process for the ERRB identifier REV channel is illustrated schematically according to various exemplary embodiments of the present invention.

[0159] Information related to the ERRB identifier REV channel can be received through the diagnostic service of the ERRB identifier REV channel. The ERRB identifier REV channel functions as follows: when a signal received from the transmitter of the serializer experiences a bit error and exceeds the value specified by accumulating and storing the corresponding value in the register, the ERRB pin is changed to 1.

[0160] DID_LEIRC (see Table 2) is the DID for the ERRB identifier REV channel. The SID can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be set by the user.

[0161] Figure 12 The diagnostic process for link margin testing according to various exemplary embodiments of the present invention is illustrated schematically.

[0162] The normal output voltage level range of the communication lines (signal lines, connectors, cables, etc. on the board) between the serializer and deserializer can be obtained through the link margin test diagnostic service.

[0163] DID_LLMT (see Table 3) is the DID used for link margin testing. The SID can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be set by the user.

[0164] Figure 13 The diagnostic process of an eye-opening monitor according to various exemplary embodiments of the present invention is illustrated schematically.

[0165] The horizontal and vertical eye-opening monitoring (EOM) values ​​can be checked via the diagnostic service of the eye-opening monitor at the Rx level of the serializer and deserializer. Diagnostic mode needs to be maintained until results are available.

[0166] DID_LEOM (see Table 3) is the DID used for the eye-opening monitor. The SID can begin with SID_TSRT and end with SID_TF, and the required parameters depending on the SID can be set by the user.

[0167] Figure 14 The diagnostic process of error correction by retransmission counting is illustrated schematically according to various exemplary embodiments of the present invention.

[0168] It can check whether the transmission of control channel signals (I2C, UART, SPI, GPIO, audio) between serializers or deserializers is performed normally, and whether the fault continues even after a failure through a retransmission count error correction service.

[0169] DID_LECR (see Table 3) is the DID used for error correction via retransmission count. A SID can begin with SID_TSRT and end with SID_TF, and the required parameters can be set by the user depending on the SID.

[0170] Figure 15 A computing system according to various exemplary embodiments of the present invention is shown.

[0171] refer to Figure 15 The computing system 1000 includes at least one processor 1100, memory 1300, user interface input device 1400, user interface output device 1500 and memory 1600, or network interface 1700, connected via a bus 1200.

[0172] Processor 1100 may be a central processing unit (CPU) or semiconductor device that executes processing on commands stored in memory 1300 and / or storage 1600. Memory 1300 and memory 1600 may include various types of volatile or non-volatile storage media. For example, memory 1300 may include read-only memory (ROM) 1310 and random access memory (RAM) 1320.

[0173] Therefore, the steps of the methods or algorithms described in conjunction with the exemplary embodiments included herein can be directly implemented by hardware, software modules, or a combination of both executed by processor 1100. The software modules can reside in storage media (i.e., memory 1300 and / or storage 1600), such as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable disks, and CD-ROMs.

[0174] An exemplary storage medium is coupled to processor 1100, which can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with processor 1100. The processor and storage medium can reside within an application-specific integrated circuit (ASIC). The ASIC can reside within a user terminal. Alternatively, the processor and storage medium can reside as separate components within the user terminal.

[0175] The above description is merely an illustration of the technical concept of the present invention, and those skilled in the art can make various modifications and changes without departing from the essential characteristics of the present invention, to which various exemplary embodiments of the present invention pertain.

[0176] For purposes of illustration and description, the foregoing description of specific exemplary embodiments of the invention has been presented. These descriptions are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and it will be apparent that many modifications and variations can be made in accordance with the foregoing teachings. The exemplary embodiments were chosen and described to explain certain principles of the invention and its practical application, enabling others skilled in the art to make and utilize various exemplary embodiments of the invention, as well as its various alternatives and modifications. The scope of the invention is intended to be defined by the appended claims and their equivalents.

Claims

1. A communication error diagnosis apparatus for a vehicle, the communication error diagnosis apparatus comprising: a processor configured to transmit a request message including a diagnosis identifier for diagnosing a plurality of controllers performing a function of the vehicle and a sequence identifier of the controller to the controller according to a sequence of receiving a response message, and configured to analyze a low-voltage differential signal (LVDS) communication error between the plurality of controllers based on the response message received from the controller; and a memory configured to store data and algorithms driven by the processor; wherein the processor is further configured to transmit a request message requesting a setting of a parameter for performing a diagnosis of a first controller to the first controller as a master apparatus, wherein the first controller among the plurality of controllers is used to perform a first function of the vehicle; and the first controller is configured to set the parameter and release the setting of the parameter after performing the diagnosis. The request message includes a diagnosis identifier (DID), a sequence identifier (SID), and an input variable for the SID.

2. The communication error diagnosing apparatus according to claim 1, wherein The diagnosis identifier includes at least one of device connection information, a line fault diagnosis service for diagnosing a short circuit or disconnection of a transmission line, a lock identifier diagnosis service for diagnosing whether connection is made between controllers in a vehicle system, an ERRB identifier FWD channel diagnosis service for diagnosing whether an error occurs in a signal received from a receiving end, an ERRB identifier REV channel diagnosis service for diagnosing occurrence of an error in a signal received from a transmitter, and an open eye monitor diagnosis service.

3. The communication error diagnosing apparatus according to claim 2, wherein 4.The communication error diagnosis apparatus of claim 2, wherein the SID includes a diagnosis start, a diagnosis step, and a diagnosis end. The response message includes the DID, the SID, and a response result.

5. The communication error diagnosing apparatus according to claim 1, wherein 6.A communication error diagnosis system for a vehicle, the communication error diagnosis system comprising: a first controller configured to perform a first function of the vehicle; a second controller configured to perform a second function of the vehicle; and a communication error diagnosis apparatus configured to transmit a request message including a DID and a SID for diagnosing the first controller to the first controller to receive a response message from the first controller, transmit a request message including the DID and the SID for diagnosing the second controller to the second controller to receive a response message from the second controller, and analyze a low-voltage differential signal (LVDS) communication error between the first controller and the second controller based on the response message of the first controller and the response message of the second controller; wherein the communication error diagnosis apparatus is configured to transmit a request message requesting a setting of a parameter for performing a diagnosis of the first controller to the first controller as a master apparatus, and wherein the first controller sets the parameter and releases the setting of the parameter after performing the diagnosis. The first controller and the second controller are included in a vehicle system, and the communication error diagnosis apparatus outside the vehicle system communicates with the first controller and the second controller. ​ 7. The communication error diagnostic system of claim 6, wherein, ​ 8. The communication error diagnosis system according to claim 6, further comprising: an on-board diagnostic (OBD) port for connecting the communication error diagnosis device and the on-board system.

9. The communication error diagnosis system according to claim 8, further comprising: a gateway configured to communicate with the communication error diagnosis device in a first communication method and to communicate with the first controller and the second controller in a second communication method.

10. The communication error diagnosis system according to claim 9, wherein, the first communication method is D-HSCAN, and wherein the second communication method is Ethernet.

11. The communication error diagnosis system according to claim 6, wherein the communication error diagnosis device is configured to transmit a request message including a DID, a SID, and a master role assignment for diagnosing the first controller to the first controller, and to receive a response message to the request message from the first controller.

12. The communication error diagnostic system of claim 6, wherein, the communication error diagnosis device receives the response message from the first controller, and then transmits a request message including a DID, a SID, and a slave role assignment for diagnosing the second controller to the second controller, and receives a response message to the request message from the second controller.

13. The communication error diagnostic system of claim 6, wherein, the communication error diagnosis device is configured to transmit a request message to check a setting of a first parameter for diagnosis preparation of the first controller to the first controller, and to receive a response message to the request message from the first controller.

14. The communication error diagnostic system of claim 13, wherein, the communication error diagnosis device receives the response message from the first controller, and then transmits a request message to check a setting of a second parameter for diagnosis preparation of the second controller to the second controller, and receives a response message to the request message from the second controller.

15. The communication error diagnostic system of claim 14, wherein, when checking the first parameter setting of the first controller and the second parameter setting of the second controller, the communication error diagnosis device is configured to transmit a request message to request a setting of a third parameter for performing diagnosis of the second controller to the second controller as a slave device, and to receive a response message to the request message from the second controller.

16. The communication error diagnostic system of claim 15, wherein, the second controller includes a value configured to distinguish a normal state and an error state in the response message, and the second controller transmits the value to the communication error diagnosis device.

17. The communication error diagnostic system of claim 15, wherein, the first controller transmits a diagnosis result of the first controller to the communication error diagnosis device.

18. The communication error diagnostic system of claim 17, wherein, the communication error diagnosis device, when receiving diagnosis results from the first controller and the second controller, when receiving a response message to the diagnosis result from the second controller, transmitting a request message to request termination of the diagnosis of the second controller to the second controller, transmitting a request message to request termination of the diagnosis of the first controller to the first controller, and when receiving a response message to the diagnosis result from the first controller, terminating a diagnosis process.

19. A communication error diagnosis method for a vehicle, the communication error diagnosis method comprising: sending a request message including a DID and a SID of a first controller for diagnosing execution of a first function of the vehicle to the first controller; receiving a response message from the first controller; sending a request message including a DID and a SID of a second controller for diagnosing execution of a second function of the vehicle to the second controller; receiving a response message from the second controller; and analyzing a vehicle communication error between the first controller and the second controller based on the response message of the first controller and the response message of the second controller; wherein the communication error diagnosis method further includes sending a request message requesting setting of a parameter for execution of diagnosis of the first controller to the first controller as a master device, and wherein the first controller sets the parameter and cancels the setting of the parameter after diagnosis is performed.

Images