Communication system

Abstract

To provide a technique for reducing a communication time required for fault diagnosis communication without using a dedicated bus for a fault diagnosis communication.SOLUTION: A communication system 2 includes a plurality of communication nodes 30, 40, 50, 60, 70, 80, 90, 100, 110 that relay fault diagnosis communication of a diagnosis request and a diagnosis result between a request source and a request destination of the fault diagnosis. In a case in which a communication determination unit determines that a fault diagnosis communication is being sent either when a diagnosis request is sent or when a diagnosis result is sent, a communication setting unit of the communication node packs a first communication frame of a first communication protocol specified for use in a communication standard for fault diagnosis into a second communication frame of a second communication protocol having a communication speed faster than that of the first communication protocol, and transmits the second communication frame.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to techniques for performing fault diagnosis communication. [Background technology]

[0002] A technique for performing fault diagnosis communication via a communication node such as a central gateway is known. For example, Patent Document 1 listed below proposes a technology for conducting fault diagnosis communication between the source of the fault diagnosis request, such as a diagnostic tool connected to a DLC or a center that communicates wirelessly with a DCM, and the destination of the fault diagnosis request, via a communication node such as a central gateway.

[0003] It should be noted that DLC is an abbreviation for Diagnostics Link Connector, and DCM is an abbreviation for Data Communication Module. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2014-078800 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, after detailed consideration by the inventors, it was found that as the number of communication nodes relaying communication on the communication path between the source of the fault diagnosis request and the destination of the fault diagnosis request increases, the communication time required for the fault diagnosis communication increases.

[0006] In order to reduce the communication time required for fault diagnosis communication, it is possible to perform the fault diagnosis communication on a dedicated bus rather than a common bus with other communications. However, providing a dedicated bus for fault diagnosis communication poses the problem of an increase in communication channels and buses.

[0007] One aspect of the present disclosure is to provide a technique for reducing communication time required for fault diagnosis communication without using a dedicated bus for the fault diagnosis communication. [Means for solving the problem]

[0008] A communication system according to one embodiment of the present disclosure includes a plurality of communication nodes (30, 40, 42, 44, 46, 50, 60, 70, 80, 90, 100, 110) that relays diagnostic communication of diagnosis requests and diagnostic results between a source of a request for diagnostics and a destination of the request for the diagnostics. Any of the communication nodes includes a communication determination unit (32, 72, 92, S402, S406, S422) and a communication setting unit (34, 74, 94, S408, S410, S426, S428).

[0009] The communication determination unit determines whether the current communication is a fault diagnosis communication. When the communication determination unit determines that the current communication is a fault diagnosis communication either when a diagnosis request is transmitted from a request source of the fault diagnosis to a request destination or when a diagnosis result is transmitted from the request destination of the fault diagnosis to the request source, the communication setting unit packs a first communication frame of a first communication protocol, the use of which is specified by a communication standard for the fault diagnosis, into a second communication frame of a second communication protocol, the communication speed of which is faster than that of the first communication protocol.

[0010] According to this configuration, since the first communication frame is packed into the second communication frame, the time required to generate the second communication frame can be reduced compared to normal protocol conversion in which the data of the first communication frame is analyzed to generate the second communication frame. Furthermore, the communication speed of the second communication protocol using the second communication frame is faster than the communication speed of the first communication protocol using the first communication frame.

[0011] In this way, the first communication frame is packed into the second communication frame of the second communication protocol, which has a faster communication speed than the first communication protocol, so that the communication time required for fault diagnosis communication can be reduced without installing a dedicated communication bus for fault diagnosis. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing a configuration of a communication system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing the configuration of an ECU. [Diagram 3] A block diagram showing a VM generated by a processor core. [Figure 4] Block diagram showing the functions of the ECU. [Diagram 5] 2 is a schematic diagram showing packing and unpacking of communication frames; [Figure 6] 4 is a flowchart showing a fault diagnosis communication process. [Figure 7] 4 is a flowchart showing a fault diagnosis communication process. [Figure 8] FIG. 11 is a block diagram showing the configuration of a communication system according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. [1. First embodiment] [1-1. Configuration] The communication system 2 shown in Fig. 1 is mounted on a vehicle and includes a DLC 10, a DCM 20, and ECUs 30, 70, and 90. ECU stands for electronic control unit. The vehicle includes, as a drive source, either an internal combustion engine or an electric motor that receives power from a rechargeable battery. The internal combustion engine may be used for generating power to supply power to the rechargeable battery.

[0014] An external tool (not shown) is connected to the DLC 10. In this embodiment, it is assumed that the CAN protocol is used as a communication standard for fault diagnosis. Therefore, the DLC 10 and the ECU 30 communicate with each other via a bus 300 using the CAN protocol. CAN is an abbreviation for Controller Area Network and is a registered trademark.

[0015] The DCM 20 communicates with a server (not shown) and the like via a network. DCM is an abbreviation for Data Communication Module. The DCM 20 and the ECUs 30 and 70 communicate with each other via a bus 310 using the Ethernet protocol. Ethernet is a registered trademark.

[0016] The ECUs 30, 70, and 90 are connected to each other via a partial network-compatible bus 320. The bus 320 is used for normal vehicle control. Furthermore, ECU 30 and ECU 70 are connected by a bus 330, and ECU 30 and ECU 90 are connected by a bus 332. Communication is performed on the buses 330 and 332 using the CAN FD protocol. CAN FD stands for CAN with Flexible Data Rate. The buses 330 and 332 are not used in normal vehicle control, but are used, for example, for data checks and fault diagnosis when the ECUs 30, 70, and 90 communicate with each other.

[0017] In this embodiment, a diagnosis request from an external tool or server that is the source of the failure diagnosis request is transmitted to a destination of the failure diagnosis request, such as the ECU 30 , 70 , 90 or a device 200 connected to the ECU 30 , 70 , 90 .

[0018] In this embodiment, since the DLC 10 is connected to the ECU 30, the transmission of a diagnosis request from an external tool via the DLC 10 and the transmission of a diagnosis result to the external tool via the DLC 10 are performed via the ECU 30.

[0019] In addition, the transmission of a diagnosis request from the server via the DCM 20 and the transmission of a diagnosis result to the server via the DCM 20 are performed via the ECU 30. For example, when the ECU 70 receives a diagnosis request for the ECU 90 from the server via the DCM 20, the ECU 70 transmits the diagnosis request to the ECU 30 instead of to the ECU 90. Then, the diagnosis request is transmitted from the ECU 30 to the ECU 90.

[0020] Even when the ECU 90 transmits the diagnostic result to the server, the ECU 90 transmits the diagnostic result to the ECU 30, not to the ECU . The diagnostic result is then transmitted from the ECU 30 to the ECU .

[0021] The transmission of a diagnosis request from the server to the ECU 70 via the DCM 20 and the transmission of a diagnosis result from the ECU 70 to the server via the DCM 20 are also performed from the ECU 70 via the ECU 30.

[0022] In this embodiment, the transmission of diagnostic requests and diagnostic results via DLC 10 and DCM 20 is performed via ECU 30 because only ECU 30 has the function of checking whether the diagnostic request or diagnostic result is appropriate.

[0023] Each of the ECUs 30, 70, 90 includes one or more microcomputers including a processor core, a RAM, a ROM, etc. Also, each of the ECUs 30, 70, 90 is a gateway ECU, such as a domain ECU that manages each group classified by function, or a zone ECU that manages each group classified by vehicle position.

[0024] Various devices 200 such as a control ECU and an actuator are connected to each of the ECUs 30, 70, and 90. Each of the ECUs 30, 70, and 90 communicates with the devices 200 using, for example, the CAN protocol.

[0025] The ECU 30 has three processor cores 40, 50, and 60, the ECU 70 has one processor core 80, and the ECU 90 has two processor cores 100 and 110. The numbers of processor cores included in the ECUs 30, 70, and 90 are merely examples and are not limited to the numbers described above.

[0026] 2, the ECU 30 includes a plurality of processor cores 40, 50, 60, as well as a shared memory 62 and a communication unit 64. The communication unit 64 includes a communication controller and a communication switch compatible with a communication protocol by which the ECU 30 communicates with the DLC 10, the ECUs 70, 90, and the device 200 of its own ECU.

[0027] Although the ECUs 70 and 90 differ in the number of processor cores, they have the same configuration as the ECU 30 shown in FIG. 3, the processor core 40 generates multiple VMs 42, 44, and 46. VM is an abbreviation for Virtual Machine. The other processor cores 50 and 60 and the processor cores of the other ECUs 70 and 90 may also generate multiple VMs.

[0028] Communication between the processor cores 40, 50, and 60 is performed via a shared memory 62 or a communication unit 64. Communication between the VMs 42, 44, and 46 is performed via a virtual CAN bus, a virtual CAN FD bus, a virtual Ethernet bus, and the like.

[0029] 4, the ECUs 30, 70, 90 function as communication determination units 32, 72, 92 and communication setting units 34, 74, 94, respectively. The functions of the communication determination units 32, 72, 92 and the communication setting units 34, 74, 94 will be described in the following [1-2. Fault diagnosis process].

[0030] [1-2. Fault diagnosis processing] The fault diagnosis process described below is executed by the ECUs 30, 70, and 90. Which processor core of each ECU executes the fault diagnosis process, and further which VM the fault diagnosis process is executed by when any of the processor cores generates a VM, is preset or appropriately determined according to the processing conditions.

[0031] (1) Packing process (1-1) When a diagnosis request is made from DLC10 When the ECU 30 receives communication from the DLC 10 via the bus 300, the communication determination unit 32 determines in S400 of FIG. 6 whether the current communication is addressed to an ECU other than the ECU itself.

[0032] In the case of communication from the DLC 10 via the bus 300, the communication determination unit 32 determines, based on the ID of the received CAN frame, whether or not the current communication is addressed to an ECU other than its own ECU.

[0033] If the determination in S400 is No, that is, if the current communication is not destined for any ECU other than the own ECU, the process proceeds to S412. If the determination in S400 is Yes, in S402, the communication determination unit 32 determines whether or not the current communication is a fault diagnosis communication based on, for example, a data value at a predetermined position in the data field of the received CAN frame. In this case, the communication determination unit 32 functions as a first communication determination unit.

[0034] If the determination in S402 is No, that is, if the current communication is not a fault diagnosis communication, the process proceeds to S412. If the determination in S402 is Yes, that is, if the current communication is a fault diagnosis communication, in S404, the communication determination unit 32 determines whether or not the current communication requires conversion of the communication protocol. If the determination in S404 is No, that is, if the current communication does not require conversion of the communication protocol, the process proceeds to S412.

[0035] When the ECU 30 receives a diagnosis request from the DLC 10 and the destination is an ECU 70, 90 other than the ECU 30, the communication protocol is converted to transmit the CAN frame received from the DLC 10 to the buses 330, 332. Therefore, the determination in S404 is Yes.

[0036] If the determination in S404 is Yes, that is, if conversion of the communication protocol is required in the current communication, the communication determination unit 32 determines in S406 whether or not predetermined conditions for executing the packing process are satisfied. The predetermined conditions (a) to (e) are as follows.

[0037] (a) An external diagnostic tool is connected to the DLC10.

[0038] (b) Either the manual parking gear or handbrake or the electric parking brake is in a position to stop the vehicle. (c) If the vehicle is equipped with an electric motor as a drive source, the rechargeable battery that supplies power to the electric motor is being charged.

[0039] (d) The vehicle is equipped with an internal combustion engine and is being refueled. (e) In the bus currently being used, the amount of communication other than the fault diagnosis communication is equal to or less than a predetermined amount, and the fault diagnosis communication does not interfere with other communications.

[0040] If the determination in S406 is No, that is, if none of the predetermined conditions (a) to (e) for executing the packing process is satisfied, the process proceeds to S412. When any one of the predetermined conditions (a) to (e) for executing the packing process is satisfied, the determination in S404 becomes Yes.

[0041] In this case, in S408, the communication setting unit 34 packs the received CAN frame into a data field of a CAN FD frame of the CAN FD protocol, which has a faster communication speed than the CAN protocol, as shown in Fig. 5. In this case, the communication setting unit 34 functions as a first communication setting unit.

[0042] When the ECU 30 receives a diagnosis request from the DLC 10 in a CAN frame, the ID of the CAN frame is 0x7XX. The communication setting unit 34 packs the CAN frame received from the DLC 10 in a CAN FD frame without changing the ID of the CAN frame from 0x7XX. At this time, the communication setting unit 34 changes the CAN FD ID from 0x7XX set in the ID of the CAN frame to 0x0XX to increase the priority of the communication.

[0043] Then, in S410, the communication setting unit 34 transmits the CAN FD frame in which the CAN frame is packed to the bus 330 or the bus 332 to be used this time. In S412, the communication setting unit 34 performs protocol conversion if normal protocol conversion is necessary for the received communication frame, or performs normal communication to transmit a communication frame of the corresponding communication protocol without protocol conversion if not necessary, and then terminates this processing.

[0044] In the process of S412, normal protocol conversion refers to analyzing the contents of the received communication frame and rearranging the contents into a communication frame configuration compatible with the communication protocol to be transmitted.

[0045] (1-2) When a diagnosis request is made from DCM20 When the ECU 70 receives data from the DCM 20 via the bus 310, in S400 of FIG. 6, the communication determination unit 72 determines whether or not the current communication is destined for an ECU other than the ECU itself, based on the destination MAC address of the Ethernet frame.

[0046] If the determination in S400 is No, that is, if the current communication is not destined for any ECU other than the own ECU, the communication determination unit 72 shifts the process to S412. If the determination in S400 is Yes, in S402, the communication determination unit 72 determines whether or not the current communication is a fault diagnosis communication based on, for example, a data value at a predetermined position in the data field of the received Ethernet frame. In this case, the communication determination unit 72 functions as a first communication determination unit.

[0047] If the determination in S402 is No, that is, if the current communication is not a fault diagnosis communication, the process proceeds to S412. If the determination in S402 is Yes, that is, if the current communication is a fault diagnosis communication, in S404, the communication determination unit 72 determines whether or not the current communication requires conversion of the communication protocol. If the determination in S404 is No, that is, if the current communication does not require conversion of the communication protocol, the process proceeds to S412.

[0048] For example, when a diagnosis request from the DCM 20 is transmitted from the ECU 70 to the ECU 90 via the ECU 30, or when a diagnosis request is transmitted from the ECU 70 to the ECU 90 via the ECU 30, the communication protocol remains CAN FD without being converted in the ECU 30. In this case, the determination in S404 is No.

[0049] If the determination in S404 is Yes, that is, if conversion of the communication protocol is necessary for the current communication, the communication determination unit 72 determines in S406 whether or not the above-mentioned predetermined condition for executing the packing process is satisfied. Note that, in the above-mentioned predetermined condition (e), it is the bus 330 connecting the ECU 30 and the ECU 70 that the communication determination unit 72 determines whether or not the amount of communication other than the fault diagnosis communication is equal to or less than a predetermined amount.

[0050] If the determination in S406 is No, that is, if the predetermined condition for executing the packing process is not met, the process proceeds to S412. If the determination in S406 is Yes, that is, if the predetermined condition for executing the packing process is satisfied, in S408, the communication setting unit 74 packs the CAN frame used in the diagnosis request into the data field of the CAN FD frame, as shown in Fig. 5. In this case, the communication setting unit 74 functions as a first communication setting unit.

[0051] Since the ECU 70 has not received the CAN frame used in the diagnosis request from the DCM 20, the communication setting unit 74 generates a CAN frame with 0x7XX set as the ID and packs it into the data field of the CAN FD frame. At this time, the communication setting unit 74 changes the CAN FD ID from 0x7XX set as the ID of the CAN frame to 0x0XX to increase the priority of the communication.

[0052] In S410, the communication setting unit 74 transmits the CAN FD frame in which the CAN frame is packed to the bus 330 to be used currently. In S412, the communication setup unit 74 executes the normal communication described above, and ends this process.

[0053] (1-3) When a diagnosis result is transmitted from the ECU itself or the device 200 of the ECU itself When transmitting a diagnostic result received from a device 200 connected to the ECU 30 or a diagnostic result by the ECU itself, in S400 of FIG. 6, the communication determination unit 32 determines whether the current communication is addressed to an ECU other than the ECU itself.

[0054] When the diagnosis result by the own ECU is transmitted, the communication determination unit 32 determines whether or not the destination is an ECU other than the own ECU. On the other hand, in the case of communication from the device 200 connected to the own ECU, the communication determination unit 32 determines, based on the ID of the CAN frame received from the device 200, whether or not the current communication is addressed to an ECU other than the own ECU.

[0055] In the case of the ECU 30, when the ECU itself or the device 200 connected to the ECU itself transmits a diagnosis result in response to a diagnosis request from the DLC 10, the destination is the DLC 10, and not another ECU. In this case, the determination in S400 is No.

[0056] On the other hand, in response to the diagnosis request from the DCM 20, the destination to which the ECU 30 transmits the diagnosis result from the own ECU or the device 200 connected to the own ECU is the other ECU, that is, the ECU 70. In this case, the determination in S400 is Yes.

[0057] In the case of the ECUs 70 and 90, when the ECU itself or the device 200 connected to the ECU itself transmits a diagnosis result in response to a diagnosis request from the DLC 10 or the DCM 20, in this embodiment, the diagnosis result is once sent via the ECU 30. Therefore, since the ECU 30 is the destination as another ECU, the determination in S400 is Yes.

[0058] If the determination in S400 is No, that is, if the destination of the current communication is not an ECU other than the own ECU, the process proceeds to S412. If the determination in S400 is Yes, that is, if the destination of the current communication is another ECU other than the ECU itself, in S402 the communication determination unit 32, 72, 92 determines whether the current communication is a fault diagnosis communication. In this case, the communication determination unit 32, 72, 92 functions as a second communication determination unit. If the determination in S402 is No, that is, if the current communication is not a fault diagnosis communication, the process proceeds to S412.

[0059] If the determination in S402 is Yes, that is, if the current communication is a fault diagnosis communication, in S404, the communication determination unit 32, 72, 92 determines whether or not the current communication requires conversion of the communication protocol. If the determination in S404 is No, that is, if the current communication does not require conversion of the communication protocol, the process proceeds to S412.

[0060] When the diagnostic result is transmitted from the own ECU or the device 200 of the own ECU to another ECU, the communication protocol is converted in order to transmit the CAN frame in which the diagnostic result is set to the buses 330, 332 using the CAN FD protocol. In this case, the determination in S404 is Yes.

[0061] If the determination in S404 is Yes, that is, if the communication protocol needs to be converted in the current communication, the communication determination unit 32, 72, 92 determines in S406 whether the above-mentioned predetermined condition for executing the packing process is satisfied. If the determination in S406 is No, that is, if the predetermined condition for executing the packing process is not satisfied, the process proceeds to S412.

[0062] If the determination in S406 is Yes, that is, if the predetermined condition for executing the packing process is satisfied, the communication setting unit 34, 74, 94 executes the packing process in S408. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0063] When transmitting the diagnosis result of its own ECU, the communication setting unit 34, 74, 94 generates a CAN frame and packs the generated CAN frame into a CAN FD frame. When the device 200 connected to the own ECU transmits a diagnosis result, the communication setting unit 34, 74, 94 packs the CAN frame received from the device 200 into a CAN FD frame. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0064] In both cases of packing a CAN frame into a CAN FD frame, the ID of the CAN frame is 0x7XX, while the ID of the CAN FD is set to 0x0XX to give the communication a higher priority.

[0065] The following steps S410 and S412 are substantially the same as the steps S410 and S412 when a diagnosis request is transmitted from the DLC 10 (1-1) described above, and therefore a description thereof will be omitted. (2) Unpacking process The following process is executed by any of the ECUs 30, 70, and 90 and is basically the same process, so it will be explained using the ECU 30 as an example.

[0066] In S420 of FIG. 7, the communication determination unit 32 determines whether the current communication is a communication from another ECU. If the determination in S420 is No, that is, if the current communication is not a communication from another ECU, the process proceeds to S430.

[0067] If the determination in S420 is Yes, that is, if the current communication is a communication from another ECU, in S422, the communication determination unit 32 determines whether the current communication is a fault diagnosis communication. In this case, the communication determination unit 32 functions as a second communication determination unit.

[0068] The determination in S422 is Yes in any one of the following cases (a) to (c), for example. (a) The ECU 70, 90 receives a CAN FD frame indicating a diagnosis request for the ECU itself or the device 200 connected to the ECU from the DLC 10 or the DCM 20 via the ECU 30.

[0069] (b) The ECU 30 receives, from the ECU 70, a CAN FD frame indicating a diagnosis request from the DCM 20 to the ECU itself or to the device 200 connected to the ECU itself. (c) The ECU 30 receives, from the ECUs 70 and 90, a CAN FD frame indicating a diagnosis result in response to a diagnosis request from the DLC 10.

[0070] If the determination in S422 is No, that is, if the CAN FD frame received from another ECU is not for fault diagnosis communication, the communication determination unit 32 transitions the process to S430. If the determination in S422 is Yes, that is, if the CAN FD frame received from another ECU is for fault diagnosis communication, in S424, the communication determination unit 32 determines whether or not conversion of the communication protocol is required for this communication. If the determination in S424 is No, that is, if conversion of the communication protocol is not required for this communication, the process proceeds to S430.

[0071] For example, in the case of transmitting a diagnosis result from ECU 70 or ECU 90 to ECU 70 via ECU 30, the communication protocol in ECU 30 remains CAN FD without being converted, and the determination in S424 is No.

[0072] If the determination in S424 is Yes, that is, if conversion of the communication protocol is necessary for the current communication, in S426, the communication setting unit 34 unpacks the CAN frame from the received CAN FD frame, as shown in Fig. 5. In this case, the communication setting unit 34 functions as a second communication setting unit. The ID of the unpacked CAN frame is set to 0x7XX, which is the ID of the CAN frame packed in the CAN FD frame.

[0073] In S428, the communication setting unit 34 performs a fault diagnosis on the ECU based on the unpacked CAN frame, transmits the CAN frame to the device 20 connected to the ECU, or transmits the CAN frame to the DLC 10, and then ends this process.

[0074] In S430, the communication setup unit 34 executes the normal communication described above, and ends this process. In the first embodiment described above, the CAN protocol corresponds to the first communication protocol, the CAN frame corresponds to the first communication frame, the CAN FD protocol corresponds to the second communication protocol, and the CAN FD frame corresponds to the second communication frame.

[0075] In addition, the 0x7 portion of the ID in the CAN frame, which indicates the priority, and the 0x0 portion of the ID in the CAN FD frame, which indicates the priority, correspond to the priority parameter. Furthermore, the ECUs 30, 70, and 90, the processor cores 40, 50, 60, 80, 100, and 1106, and the VMs 42, 44, and 46 correspond to a communication node, a first communication node, and a second communication node.

[0076] Moreover, S402, S406, and S422 correspond to the processing of the communication determination unit, and S408, S410, S426, and S428 correspond to the processing of the communication setting unit. [1-3. Effects] According to the first embodiment described above, the following effects can be obtained.

[0077] (1a) CAN frames of the CAN protocol, which is specified in the communication standard for fault diagnosis, are packed and transmitted in CAN FD frames of the CAN FD protocol, which has a faster communication speed than the CAN protocol. This makes it possible to reduce the communication time required for fault diagnosis without using a dedicated communication bus for fault diagnosis.

[0078] (1b) Instead of the usual protocol conversion, CAN frames are packed into CAN FD frames, which shortens the time it takes to generate a CAN FD frame from a CAN frame.

[0079] (1c) When packing a CAN frame into a CAN FD frame, the priority of communication by the CAN FD frame is increased above the priority of communication by the CAN frame, thereby suppressing delays in fault diagnosis communication, thereby further reducing the communication time required for fault diagnosis.

[0080] [2. Second embodiment] [2-1. Differences from the first embodiment] The second embodiment has a basic configuration similar to that of the first embodiment, and therefore differences will be described below. Note that the same reference numerals as those in the first embodiment indicate the same configuration, and the preceding description will be referred to.

[0081] In the first embodiment described above, the ECUs 30, 70, and 90 are provided with buses 330 and 332 that communicate using the CAN FD protocol. In contrast, in the second embodiment shown in Fig. 8, the ECUs 30, 70, and 90 are connected to each other using buses 312 and 314 that communicate using the Ethernet protocol instead of the buses 330 and 332, which is different from the first embodiment.

[0082] In addition to data checking when the ECUs 30, 70, 90 communicate with each other, the buses 312, 314 may also be used for part of normal vehicle control. [2-2. Fault diagnosis processing] (1) Packing process (1-1) When a diagnosis request is sent from DLC10 The following process is substantially the same as S400 to S406 and S412 in FIG. 6 described in <(1-1) When a diagnosis request is transmitted from the DLC 10> in the first embodiment, and therefore a description of the corresponding process will be omitted.

[0083] In S408 of Fig. 6, the communication setting unit 34 packs the received CAN frame into a data field of an Ethernet frame of the Ethernet protocol, which has a faster communication speed than the CAN protocol, as shown in Fig. 5. In this case, the communication setting unit 34 functions as a first communication setting unit.

[0084] Then, in S410, the communication setup unit 34 transmits the Ethernet frame in which the CAN frame is packed to the buses 312, 314 that connect to the destination ECU. At this time, the communication setting unit 34 sets a priority corresponding to the priority represented by 0x0XX that was set to increase the priority of CAN FD in the first embodiment, in the PCP of the tag field of the Ethernet frame, thereby increasing the priority of the communication.

[0085] (1-2) When a diagnosis request is sent from DCM20 The following processing is substantially the same as S400 to S406 and S412 in FIG. 6 described in <(1-2) When a diagnosis request is transmitted from the DCM 20> in the first embodiment, and therefore a description of the corresponding processing will be omitted.

[0086] In S408 of Fig. 6, the communication setting unit 74 packs the CAN frame used in the diagnosis request in the data field of the Ethernet frame as shown in Fig. 5. In this case, the communication setting unit 74 functions as a first communication setting unit. At this time, the communication setting unit 74 sets a priority corresponding to the priority represented by 0x0XX set in order to increase the priority of CAN FD in the first embodiment, in the PCP of the tag field of the Ethernet frame, thereby increasing the priority of communication.

[0087] Then, in S410, the communication setup unit 74 transmits the ETHANMET frame in which the CAN frame is packed, to the bus 312 in either case where the fault diagnosis request destination is the ECU 30 or where the fault diagnosis request destination is the ECU 70, 90.

[0088] This is because, as described above, only the ECU 30 has the function of checking whether the diagnosis request or the diagnosis result is appropriate, and therefore the ECU 30 checks the appropriateness of the failure diagnosis.

[0089] (1-3) When a diagnosis result is transmitted from the ECU itself or from the device 200 connected to the ECU itself The following processing is essentially the same as S400 to S406 and S412 in Figure 6 described in <(1-3) When a diagnosis result is transmitted from the ECU itself or the device 200 connected to the ECU> in the first embodiment, so the description of the corresponding processing is omitted.

[0090] In S408, the communication setting unit 34, 74, 94 executes the packing process. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit. When the diagnosis result of the own ECU is to be transmitted, in S408 the communication setup unit 34, 74, 94 generates a CAN frame and packs the generated CAN frame into an Ethernet frame.

[0091] When the device 200 connected to the own ECU transmits a diagnosis result, in S408 the communication setup unit 34, 74, 94 packs the CAN frame received from the device 200 into an Ethernet frame.

[0092] The ID of the CAN frame used in the fault diagnosis is 0x7XX as described above. The communication setting unit 34 does not change the ID of the CAN frame from 0x7XX, and packs it into an Ethernet frame.

[0093] At this time, the communication setting units 34, 74, 94 increase the priority of communication by setting a priority corresponding to the priority represented by 0x0XX that was set to increase the priority of CAN FD in the first embodiment in the PCP of the tag field of the Ethernet frame.

[0094] Then, in S410, the communication setup unit 34, 74, 94 transmits the Ethernet frame in which the CAN frame is packed to the bus 312 or the bus 314 to which the destination ECU is connected.

[0095] (2) Unpacking process Since this is substantially the same as the process in <(2) Unpacking process> described in the first embodiment, but with CAN FD replaced by Ethernet, a description thereof will be omitted.

[0096] In the second embodiment described above, the CAN corresponds to the first communication protocol, the CAN frame corresponds to the first communication frame, the Ethernet protocol corresponds to the second communication protocol, and the Ethernet frame corresponds to the second communication frame. Moreover, the PCP in the tag field of the Ethernet frame corresponds to the priority parameter.

[0097] [2-3. Effects] According to the second embodiment described above, it is possible to obtain substantially the same effects as those described in the effects (1a) to (1c) of the first embodiment described above, except that CAN FD is replaced by Ethernet.

[0098] 3. Other embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0099] (3a) In the above-described embodiment, the CAN FD protocol or the Ethernet protocol is used as a communication protocol having a faster communication speed than the CAN protocol, but the present invention is not limited to this. For example, the CAN XL protocol may be used.

[0100] (3b) In the above-described embodiment, when a CAN frame is packed into a communication frame of a communication protocol having a higher communication speed than the CAN protocol, the priority of the priority parameter representing the communication priority is increased. In contrast, the priority of the priority parameter representing the communication priority may remain the same.

[0101] (3c) In the above-described embodiment, the first communication frame is packed into the second communication frame in both the fault diagnosis communication from the request source to the request destination and from the request destination to the request source, but the present invention is not limited to this. The first communication frame may be packed into the second communication frame only in one or the other of the communication paths from the request source to the request destination or from the request destination to the request source.

[0102] (3d) If the first communication frame can be packed into the second communication frame, any communication node on the communication path from the request source of the fault diagnosis to the request destination, and from the request destination of the fault diagnosis to the request source may perform the packing process.

[0103] (3e) In the above embodiment, only the ECU 30 connected to the DLC 10 has the function of checking whether the diagnostic request or diagnostic result is appropriate. However, this is not limited to this.

[0104] By providing the ECU 70 connected to the DCM 20 with a function for checking whether or not a diagnostic request or a diagnostic result is appropriate, the ECU 70 can transmit a diagnostic request and a diagnostic result to the ECU 70 without going through the ECU 30. In this case, in the above-described embodiment, the ECU 70 needs to be connected to each of the ECUs 30 and 90 via a bus conforming to the CAN FD protocol or the Ethernet protocol.

[0105] (3f) In the above-described embodiment, the CAN protocol is used as the first communication protocol specified by the communication standard for fault diagnosis, but the present invention is not limited to this. If the communication standard for fault diagnosis is changed, the first communication protocol may be, for example, CAN FD or Ethernet. In this case, a second communication protocol having a communication speed faster than the CAN FD protocol or the Ethernet protocol is used.

[0106] (3g) In the above-described embodiment, fault diagnosis communication is performed not by bus 320 of the partial network used for vehicle control but by buses 330, 332 or buses 312, 314 which perform data checks when ECUs 30, 70, 90 communicate with each other. In contrast, fault diagnosis communication may be performed by bus 320 used for vehicle control without providing buses 330, 332, 312, 314. In this case, the communication protocol used by bus 320 has a communication speed at least faster than that of the CAN protocol.

[0107] (3h) In the above-described embodiment, the communication systems 2, 4 are described as having three ECUs 30, 70, 90. In this case, the number of ECUs that relay the fault diagnosis communication is a maximum of three as shown in the second embodiment. However, the number of ECUs may be four or more. And, the fault diagnosis communication may be relayed by four or more ECUs.

[0108] (3i) The communication systems 2, 4 and techniques described in this disclosure may be implemented by a special purpose computer provided by configuring a processor and memory programmed to perform one or more functions embodied in a computer program.

[0109] Alternatively, the communication systems 2, 4 and techniques described in this disclosure may be implemented in a special purpose computer provided by configuring a processor with one or more special purpose hardware logic circuits.

[0110] Alternatively, the communication systems 2, 4 and techniques described herein may be implemented using one or more special purpose computers configured using a combination of a processor and memory programmed to perform one or more functions and a processor configured with one or more hardware logic circuits.

[0111] The computer program may be stored in a computer-readable non-transitory recording medium as instructions executed by a computer. The method for realizing the functions of each unit included in the communication systems 2 and 4 does not necessarily need to include software, and all of the functions may be realized using one or more pieces of hardware.

[0112] (3j) Multiple functions possessed by one component in the above-mentioned embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above-mentioned embodiments may be omitted. Also, at least part of the configuration of the above-mentioned embodiments may be added to or substituted for the configuration of another of the above-mentioned embodiments.

[0113] (3k) In addition to the communication systems 2 and 4 described above, the present disclosure can also be realized in various forms, such as a program for causing a computer to function as the communication systems 2 and 4, a non-transient physical recording medium such as a semiconductor memory on which the program is recorded, and a communication method. [Technical idea disclosed in this specification]

[0114] [Item 1] A communication system including a plurality of communication nodes (30, 40, 42, 44, 46, 50, 60, 70, 80, 90, 100, 110) for relaying diagnostic communication of a diagnosis request and a diagnosis result between a request source of a fault diagnosis and a request destination of the fault diagnosis, Any of the communication nodes, a communication determination unit (32, 72, 92, S402, S406, S422) configured to determine whether or not the current communication is the fault diagnosis communication; a communication setting unit (34, 74, 94, S408, S410, S426, S428) configured to pack a first communication frame of a first communication protocol, the use of which is determined by a communication standard for the fault diagnosis, into a second communication frame of a second communication protocol, the second communication protocol having a communication speed faster than that of the first communication protocol, when the communication determination unit determines that the current communication is the fault diagnosis communication, either when a diagnosis request is transmitted from the request source to the request destination or when a diagnosis result is transmitted from the request destination to the request source; Equipped with Communication systems.

[0115] [Item 2] Item 1 is a communication system according to the present invention, Assuming that the communication node is a first communication node, the communication determination unit is a first communication determination unit, and the communication setting unit is a first communication setting unit, the first communication setting unit is configured to pack the first communication frame into the second communication frame when the first communication determining unit determines that the current communication is the fault diagnosis communication at either the time of transmitting the diagnosis request or the time of transmitting the diagnosis result; Among the plurality of communication nodes, a second communication node other than the first communication node is a second communication determination unit configured to determine whether the current communication is the fault diagnosis communication; a second communication setting unit configured to unpack the first communication frame from the second communication frame when the second communication determination unit determines that the current communication is the fault diagnosis communication at either the time of transmitting the diagnosis request or the time of transmitting the diagnosis result; Equipped with Communication systems.

[0116] [Item 3] Item 2. A communication system according to the present invention, the second communication setting unit is configured to pack the first communication frame into the second communication frame when the second communication determination unit determines that the current communication is the fault diagnosis communication at the other of the time of transmitting the diagnosis request or the time of transmitting the diagnosis result; the first communication setting unit is configured to unpack the first communication frame from the second communication frame when the first communication determination unit determines that the current communication is the fault diagnosis communication at the other of the time of transmitting the diagnosis request or the time of transmitting the diagnosis result. Communication systems.

[0117] [Item 4] A communication system according to any one of items 1 to 3, the communication setting unit is configured to increase the priority of a priority parameter representing a priority of communication in the second communication frame when packing the first communication frame into the second communication frame. Communication systems.

[0118] [Item 5] A communication system according to any one of items 1 to 4, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and that at least one of a manual parking gear, a side brake, and an electric parking brake is in a state to stop the vehicle. Communication systems.

[0119] [Item 6] 6. A communication system according to any one of claims 1 to 5, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and further that an external fault diagnosis tool is connected to the communication system as the request source of the fault diagnosis. Communication systems.

[0120] [Item 7] A communication system according to any one of items 1 to 6, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication, that the vehicle includes an electric motor as a drive source, and that a rechargeable battery that supplies power to the electric motor is being charged. Communication systems.

[0121] [Item 8] A communication system according to any one of items 1 to 7, the communication setting unit is configured to pack the first communication frame into the second communication frame when the current communication is the fault diagnosis communication and the communication determination unit determines that the vehicle has an internal combustion engine and is undergoing refueling. Communication systems.

[0122] [Item 9] A communication system according to any one of items 1 to 8, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and that an amount of communication other than the fault diagnosis communication is equal to or less than a predetermined amount. Communication systems.

[0123] [Item 10] A communication system according to any one of items 1 to 9, The first communication protocol is a CAN protocol; Communication systems.

[0124] [Item 11] A communication system according to any one of items 1 to 10, At least one of the communication nodes is an electronic control device. Communication systems.

[0125] [Item 12] A communication system according to any one of claims 1 to 11, At least one of the communication nodes is a processor core. Communication systems.

[0126] [Item 13] A communication system according to any one of items 1 to 12, At least one of the communication nodes is a virtual machine. Communication systems. [Explanation of symbols]

[0127] 2, 4: communication system, 30, 70, 90: ECU (communication node), 32, 72, 92: communication determination unit, 34, 74, 94: communication setting unit, 40, 50, 60, 80, 100, 110: processor core (communication node), 42, 44, 46: VM (communication node)

Claims

1. A communication system including a plurality of communication nodes (30, 40, 42, 44, 46, 50, 60, 70, 80, 90, 100, 110) for relaying diagnostic communication of a diagnosis request and a diagnosis result between a request source of a fault diagnosis and a request destination of the fault diagnosis, Any of the communication nodes, a communication determination unit (32, 72, 92, S402, S406, S422) configured to determine whether or not the current communication is the fault diagnosis communication; a communication setting unit (34, 74, 94, S408, S410, S426, S428) configured to pack a first communication frame of a first communication protocol, the use of which is determined by a communication standard for the fault diagnosis, into a second communication frame of a second communication protocol, the second communication protocol having a communication speed faster than that of the first communication protocol, when the communication determination unit determines that the current communication is the fault diagnosis communication, either when a diagnosis request is transmitted from the request source to the request destination or when a diagnosis result is transmitted from the request destination to the request source; Equipped with Communication systems.

2. 2. The communication system according to claim 1, Assuming that the communication node is a first communication node, the communication determination unit is a first communication determination unit, and the communication setting unit is a first communication setting unit, the first communication setting unit is configured to pack the first communication frame into the second communication frame when the first communication determining unit determines that the current communication is the fault diagnosis communication at either the time of transmitting the diagnosis request or the time of transmitting the diagnosis result; Among the plurality of communication nodes, a second communication node other than the first communication node is a second communication determination unit configured to determine whether the current communication is the fault diagnosis communication; a second communication setting unit configured to unpack the first communication frame from the second communication frame when the second communication determination unit determines that the current communication is the fault diagnosis communication at either the time of transmitting the diagnosis request or the time of transmitting the diagnosis result; Equipped with Communication systems.

3. 3. The communication system according to claim 2, the second communication setting unit is configured to pack the first communication frame into the second communication frame when the second communication determination unit determines that the current communication is the fault diagnosis communication at the other of the time of transmitting the diagnosis request or the time of transmitting the diagnosis result, the first communication setting unit is configured to unpack the first communication frame from the second communication frame when the first communication determination unit determines that the current communication is the fault diagnosis communication at the other of the time of transmitting the diagnosis request or the time of transmitting the diagnosis result. Communication systems.

4. 2. The communication system according to claim 1, the communication setting unit is configured to increase the priority of a priority parameter representing a priority of communication in the second communication frame when packing the first communication frame into the second communication frame. Communication systems.

5. 2. The communication system according to claim 1, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and that at least one of a manual parking gear, a side brake, and an electric parking brake is in a state to stop the vehicle. Communication systems.

6. 2. The communication system according to claim 1, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and further that an external fault diagnosis tool is connected to the communication system as the request source of the fault diagnosis. Communication systems.

7. 2. The communication system according to claim 1, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication, that the vehicle includes an electric motor as a drive source, and that a rechargeable battery that supplies power to the electric motor is being charged. Communication systems.

8. 2. The communication system according to claim 1, the communication setting unit is configured to pack the first communication frame into the second communication frame when the current communication is the fault diagnosis communication and the communication determination unit determines that the vehicle is equipped with an internal combustion engine and is undergoing refueling. Communication systems.

9. 2. The communication system according to claim 1, the communication setting unit is configured to pack the first communication frame into the second communication frame when the communication determination unit determines that the current communication is the fault diagnosis communication and that an amount of communication other than the fault diagnosis communication is equal to or less than a predetermined amount. Communication systems.

10. 2. The communication system according to claim 1, The first communication protocol is a CAN protocol. Communication systems.

11. 2. The communication system according to claim 1, At least one of the communication nodes is an electronic control device. Communication systems.

12. 2. The communication system according to claim 1, At least one of the communication nodes is a processor core. Communication systems.

13. 2. The communication system according to claim 1, At least one of the communication nodes is a virtual machine. Communication systems.

Images