JP5217740B2 - Remote vehicle diagnostic method, remote vehicle diagnostic system, and in-vehicle diagnostic device - Google Patents

Description

  The present invention relates to a remote vehicle diagnostic system in which a vehicle executes various diagnostic processes in accordance with a diagnostic request transmitted from a center to the vehicle.

  Conventionally, as this type of remote vehicle diagnosis system, a remote failure diagnosis system that performs vehicle failure diagnosis by exchanging information between the vehicle and the center is known (for example, see Patent Document 1).

  In the remote failure diagnosis system disclosed in Patent Document 1, when an abnormality or failure (hereinafter referred to as “failure” or the like) is detected in the vehicle, the fact that the failure or the like has occurred from the vehicle to the center at the time of detection is indicated. Notice. In response to this notification, the center sets a diagnostic procedure necessary to identify the cause of the failure and sends it to the vehicle in a lump. The vehicle performs a plurality of diagnoses according to the diagnosis procedure transmitted from the center, and sends the diagnosis results to the center all at once.

Not only when a failure occurs in the vehicle, the center periodically requests the vehicle to make a diagnosis, causes the vehicle to execute the diagnosis, and the vehicle sends the diagnosis result to the center. Remote vehicle diagnostic systems that check status are also known. By performing such periodic diagnosis, it is possible to periodically monitor the presence or absence of a failure or the like without the user bringing the vehicle into a store or the like. When the occurrence of a failure or the like is detected, it is possible to promptly notify the user of the necessity for repair or the like.
JP 2006-64651 A

However, the conventional remote vehicle diagnostic system including the diagnostic system disclosed in Patent Document 1 has a problem in that no consideration is given to the location where the diagnosis is performed.
For example, it is possible to receive a diagnostic service while the vehicle is parked in the parking lot of the supermarket at the destination, but as a diagnostic menu in that case, for example, a diagnostic menu that locks and unlocks the door If it is assembled, the user cannot leave the vehicle in consideration of theft.

  In addition, not only at the location of the diagnosis, but also depending on the state of the vehicle such as whether the vehicle is running or the time zone, various concerns may arise if the diagnosis is performed unconditionally according to the diagnosis request from the center. There is.

  SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and an object of the present invention is to prevent concern on the user side when performing diagnosis on the vehicle side in accordance with a diagnosis request from the center. .

In order to solve the above-mentioned problem, the invention according to claim 1 is a remote vehicle diagnosis method in which a vehicle executes a diagnosis process in accordance with a diagnosis request transmitted by a center, and the permission condition under which the vehicle can execute the diagnosis process is provided. It is set in advance, and when the vehicle receives a diagnosis request from the center, the vehicle determines whether or not the state of the vehicle at the time of reception satisfies the permission condition. Execute the process. As a permission condition, at least the position of the vehicle that can execute the diagnostic process is set.

  According to the remote vehicle diagnosis method according to claim 1 configured as described above, the vehicle does not execute the diagnosis process unconditionally when a diagnosis request is issued from the center, but the preset permission condition is set. If the condition is satisfied, the diagnostic process is executed. Therefore, by appropriately setting the permission conditions, it is possible to prevent the user (for example, the driver of the vehicle) from being concerned about the execution of the diagnosis process.

In addition , when a diagnosis is requested from the center, a diagnosis process is executed when the vehicle is present at a position set as a permission condition, and the vehicle exists at a position different from the position set as a permission condition. In such a case, since the diagnosis process is not executed, it is possible to eliminate the user's concern due to the place where the diagnosis process is executed. Specifically, for example, by allowing the diagnosis to be executed only when the vehicle is at the user's home, the diagnosis process can be executed under the monitoring of the user.

Further, for example, as described in claim 2, when the vehicle is configured to be able to charge the battery included in the vehicle by the charging power supplied from the outside of the vehicle, at least as the permission condition, You may make it set that charging to the battery by the electric power for charging is performed.

  In this way, when a diagnosis request is made from the center, the diagnosis process is executed when the battery of the vehicle is being charged. Therefore, a diagnosis process with large power consumption is executed temporarily. Even if it is done, there is no risk of battery exhaustion. For this reason, it is possible to eliminate the user's concern (battery exhaustion) caused by the battery power consumption during the execution of the diagnostic process.

Next, the invention according to claim 3 is a remote vehicle diagnostic system in which the vehicle executes a diagnostic process according to a diagnostic request transmitted by the center, and the system sets in advance permission conditions that allow the vehicle to execute the diagnostic process. Provided permission condition setting means. In the permission condition setting means, at least a diagnosis executable position, which is a position of the vehicle that can execute the diagnosis process, is set as a permission condition. When the vehicle receives a diagnosis request from the center, the vehicle is permitted to determine whether the state of the vehicle at the time of reception satisfies the permission condition based on the permission condition set in the permission condition setting means. Condition determining means, and diagnosis executing means for executing diagnosis processing when the permission condition determining means determines that the permission condition is satisfied. The permission condition determination means, when receiving a diagnosis request from the center, at least the position of the vehicle at the time of reception acquired by the position acquisition means coincides with the diagnosis executable position set in the permission condition setting means as the determination Judge whether or not to do so.

According to the remote vehicle diagnosis system according to claim 3 configured as described above, the vehicle diagnosis execution means is configured such that when a preset permission condition is satisfied (the vehicle is present at the diagnosis executable position). In this case, the remote vehicle diagnosis method according to claim 1 can be realized, and the same effect as in claim 1 can be obtained.

The remote vehicle diagnosis system diagnostics executable position is set as the permission condition thus it is included the operation to unlock the door to which the vehicle is equipped with the diagnostic process vehicles runs, the diagnosis execution The means is configured to execute a diagnostic process including an operation of unlocking the door when it is determined by the permission condition determination means that the position of the vehicle matches the diagnosis executable position set in the permission condition setting means. It is more effective when

  If the diagnosis process including the operation of unlocking the door is unconditionally performed regardless of the position of the vehicle, there is a possibility that the user may be afraid of theft depending on the position of the vehicle. Therefore, if a diagnosis executable position is set as a permission condition for executing a diagnostic process including an operation of unlocking the door, the door unlocking is performed when the vehicle exists at the set position. Since the diagnostic process including the lock is executed, the user's concern associated with the door unlocking operation can be eliminated.

The invention according to claim 4 is the remote vehicle diagnosis system according to claim 3 , wherein the vehicle is for charging to input power for charging a battery included in the vehicle from outside the vehicle. Whether or not the battery is charged based on the power input means, the charge control means for controlling the charging of the charging power input to the charging power input means, and the charging power. Charging state detection means for directly or indirectly detecting the above. Further, the permission condition setting means is set as a permission condition that at least the battery is charged based on the charging power. The permission condition determining means detects, by the charge state detecting means, at least whether or not the battery is being charged based on the charging power when the diagnosis request is received from the center. Based on the results.

According to the remote vehicle diagnosis system of claim 4 configured as described above, the vehicle diagnosis execution means executes the diagnosis process when the vehicle battery is charged by the external charging power. You can achieve remote vehicle diagnostic method of claim 2, wherein, the same effect as claim 2 is obtained.

The remote vehicle diagnosis system that thus the battery charging based on the charging power as permission condition is a condition being performed is set, the engine of the vehicle in diagnostic processes vehicles runs An operation for consuming battery power in a stopped state is included, and when the diagnosis execution unit determines that the battery is charged based on the charging power by the permission condition determination unit, the engine This is more effective when the diagnosis process including the operation of consuming the battery power in the stopped state is executed.

  If a diagnosis process including an operation of consuming battery power is performed in a state where the engine is stopped, there is a risk of causing the user to run out of battery depending on the amount of power consumption. Therefore, if it is set as a permission condition for executing a diagnostic process including an operation of consuming battery power while the engine is stopped, the battery is charged based on the charging power. Since the diagnosis process is executed when the battery is being charged, it is possible to eliminate the concern about the battery running out.

With permission condition setting means is provided in the center, the center can further be a structure having a updating means for updating according to the update request permission condition set in the permission condition setting means.

Thus, according to the remote vehicle diagnostic system comprising a updating means, it is possible to permit conditions are not fixed uniformly, appropriately setting change permission condition in accordance with the state of the user's request or a vehicle, usability A more user-friendly system is realized.

In this case, although the user specifically how to update the permission condition are various, For example, the center and provided with a communicable communication terminal via a communication line, the user so as to perform the update by using the communication terminal May be. Specifically, the communication terminal acquires a permission condition acquisition unit that acquires a permission condition set in the permission condition setting unit of the center, and a predetermined update for updating the permission condition acquired by the permission condition acquisition unit An update operation reception unit that receives an operation; and an update request transmission unit that transmits an update request corresponding to the update operation received by the update operation reception unit to the center. Then, when the update means provided in the center receives the update request from the communication terminal, the update means updates the permission condition set in the permission condition setting means based on the update request.

According to the thus constructed remote diagnostic system, the user since it is possible to update the permission condition set in the center by using the terminal device, and more user-friendly system for the user is achieved.

Moreover, you may comprise the remote vehicle diagnostic system of this invention as follows. That is, a plurality of types of permission conditions are set in the permission condition setting means, and a logical expression indicating a logical combination of the plurality of types of permission conditions is set. The permission condition determining means includes an individual determining means for determining each of a plurality of types of permission conditions, and a vehicle state based on a calculation result of a logical expression based on a determination result for each setting condition by the individual determining means. A final determination unit that finally determines whether or not the diagnosis process can be executed, and the diagnosis execution unit determines that the diagnosis process is executable by the final determination unit. The diagnostic process is executed.

  According to the remote vehicle diagnosis system according to claim 11 configured as described above, when two types (condition A and condition B) are set as permission conditions, for example, by appropriately setting a logical expression, for example, If the logical product of the condition A and the condition B is set, the diagnosis process can be executed only when both the condition A and the condition B are satisfied. Further, for example, if a logical sum of the conditions A and B is set, the diagnosis process can be executed as long as at least one of the conditions A and B is satisfied. Therefore, relative weighting can be set among a plurality of permission conditions, and permission conditions can be set in accordance with the user's intention.

The invention according to claim 5 is an in-vehicle diagnosis device that is mounted on a vehicle and executes diagnosis processing in accordance with a diagnosis request transmitted from the center, the position acquisition means for acquiring the position of the vehicle, and the diagnosis from the center. When receiving a request, based on preset permission conditions, permission condition determining means for determining whether or not diagnosis processing according to the diagnosis request can be executed, and the permission condition determining means Diagnostic execution means for executing a diagnosis process when it is determined that the permission condition is satisfied , and at least a diagnosis executable position, which is a position of the vehicle that can execute the diagnosis process, is set as the permission condition. The permission condition determining means, when receiving a diagnosis request from the center, determines at least the position of the vehicle at the time of reception acquired by the position acquiring means as the determination. It is characterized in that to perform the matching determination of whether a diagnosis execution can position set in.

According to the vehicle-mounted diagnosis device according to claim 5 configured as described above, the remote vehicle diagnosis system according to claim 3 can be configured.

Preferred embodiments of the present invention will be described below with reference to the drawings.
[First Embodiment]
FIG. 1 shows a schematic configuration of a remote vehicle diagnostic system according to an embodiment to which the present invention is applied.

  In the remote vehicle diagnosis system 1 of the present embodiment, the vehicle 3 executes a diagnosis in the vehicle 3 according to a diagnosis request from a remote diagnosis center (hereinafter referred to as “center”) 2 and notifies the center 2 of the diagnosis result. As shown in FIG. 1, an in-center system 10 is constructed on the center 2 side, and an in-vehicle system 9 is constructed in the vehicle 3.

  The center system 10 constructed in the center 2 includes a server 11 that provides a diagnostic service to each of a plurality of vehicles including the vehicle 3, and a vehicle number and a diagnostic scenario for each customer that provides the diagnostic service (see FIG. 3B). ), The diagnosis service information management database (DB) 12 in which the diagnosis permission condition table (see FIG. 3A) and the like are centrally managed, and the diagnosis result notified from the vehicle to be diagnosed are collated to determine whether the vehicle is normal. / A case database 13 in which standard case information is stored for deriving anomaly judgments, treatment methods, and the like, and these are connected to each other via a network 14 so as to be able to transmit and receive data.

  The diagnosis service execution timing (execution cycle) provided by the center 2, a diagnosis scenario in which a diagnosis procedure is specified for each diagnosis menu to be executed, and a diagnosis permission condition (diagnosis permission condition table described later) that is a condition for permitting execution are as follows: For each user (for each vehicle), an agreement is made in advance at the time of diagnosis service contract concluded between the user and the diagnosis service provider, and the contents are stored in the diagnosis service information management database 12 of the system 10 in the center. ing.

  The server 11 executes remote diagnosis for each user according to the contract contents. That is, at the time of remote diagnosis execution, a diagnosis request is transmitted to the vehicle 3 side via a communication network such as the Internet network 5 or the mobile phone network 4. At this time, a diagnosis scenario and a diagnosis permission condition table are also transmitted together with the diagnosis request.

  The in-vehicle system 9 constructed in the vehicle 3 includes a remote diagnosis master ECU (hereinafter abbreviated as “master ECU”) 20 and a plurality of ECUs (first ECU 40, second ECU 50, third ECU 60,...) That control each part in the vehicle 3. A navigation ECU 70), and these ECUs are connected to each other via the multiple communication line 30 so as to be able to transmit and receive data.

  The master ECU 20 plays a central role on the vehicle 3 side of the remote vehicle diagnosis system 1 of the present embodiment, in which various diagnoses are executed in accordance with a diagnosis request from the center 2 side. Data such as a diagnosis request transmitted from the center 2 side through the Internet network 5 and wirelessly transmitted through the mobile phone network 4 is received by the antenna 21 provided in the master ECU 20 in the in-vehicle system 9.

  The user also has a personal computer (PC) 7 at home 6, and the personal computer 7 is connected to the Internet network 5 through a communication line 8 such as an optical fiber or ADSL. Therefore, the user can access the in-center system 10 of the center 2 from the personal computer 7 of the home 6 via the Internet network 5, and as a result, the diagnosis in the diagnosis service information management database 12 is described later. The user can change the contents of the permission condition table using the personal computer 7.

  A more specific configuration of the in-vehicle system 9 will be described with reference to FIG. As shown in FIG. 2, the master ECU 20 includes an MCU 31 that executes various processes based on the program, a ROM 32 that stores various programs executed by the MCU 31, and a RAM 33 that serves as a work memory when the MCU 31 executes various processes. , For performing wireless communication between the communication controller 36 and the transceiver 24 for performing multiplex communication with the other ECUs 40, 50, 60, 70... The communication device 34 having the antenna 21, the GPS 35 having the antenna 22 for detecting the vehicle position (coordinates) of the vehicle 3 based on a signal from a GPS satellite (not shown), and each part in the master ECU 20 are operated. And a power supply circuit 23 for supplying power for operation. The GPS 35 also receives current time information indicating the current time together with the vehicle position information.

  The master ECU 20 is connected to each of the ECUs 40, 50, 60, 70,. When the master ECU 20 executes remote diagnosis in response to a diagnosis request from the center 2 side, the master ECU 20 acquires information necessary for determining whether or not a condition for executing diagnosis is satisfied from each ECU. Moreover, during diagnosis execution, various information required for diagnosis is acquired from each ECU.

.. Except for the navigation ECU 70 are connected to actuator groups 41, 51, 61... Each composed of one or a plurality of actuators controlled by each ECU. In addition, each ECU 40, 50, 60... Has a sensor group 42, 52, 62... Composed of one or a plurality of sensors and switches (for example, a vehicle speed sensor, an O ₂ sensor, a temperature sensor, etc.). It is connected.

  In the present embodiment, a vehicle speed sensor 43 is included in the sensor group 42 connected to the first ECU 40, and a vehicle speed signal detected by the vehicle speed sensor 43 is input to the first ECU 40. Therefore, the master ECU 20 can know the vehicle speed by acquiring a vehicle speed signal from the first ECU 40 as necessary when performing a remote diagnosis.

  The first ECU 40 controls the engine of the vehicle 3. Therefore, the master ECU 20 can know the operating state of the engine by acquiring information related to the state of the engine from the first ECU 40.

  The actuator group 51 connected to the second ECU 50 includes a door lock mechanism 53 that controls the operation (lock / unlock) of each door lock mechanism of the vehicle 3 (not shown). The sensor group 52 connected to the second ECU 50 includes a lock position switch 54 that detects the locked / unlocked state of each door and outputs a lock position signal that is the detection result. Therefore, when performing the remote diagnosis, the master ECU 20 can know the locked / unlocked state of each door by acquiring a lock position signal from the second ECU 50 as necessary.

  The navigation ECU 70 is a well-known ECU for realizing a navigation system in the vehicle 3, acquires own vehicle position data (coordinate data) via the built-in GPS, detects the current position, and detects the detected current The position is superimposed on the map data and displayed on the display 71.

  The display 71 includes not only a function of displaying information but also a so-called touch panel that allows a user to make various inputs by touching the display surface with a finger or the like. In the present embodiment, as will be described later, the contents of the diagnosis permission condition table stored in the diagnosis service information management database 12 on the center 2 side can be changed by the user himself. This can be done by the user operating the touch panel of the display 71.

  In this embodiment, since the GPS 35 is built in the master ECU 20, the navigation ECU 70 does not necessarily have a built-in GPS, and the navigation ECU 70 acquires the vehicle position information from the GPS 35 in the master ECU 20. You may do it. Conversely, the master ECU 20 may not include the GPS 35, and the master ECU 20 may acquire the vehicle position information and the current time information from the navigation ECU 70.

  Here, of the information transmitted from the center system 10 on the center 2 side to the vehicle 3 to be diagnosed during the execution of the remote diagnosis, FIG. It explains using. FIG. 3A is a diagnosis permission condition table, and FIG. 3B is a diagnosis scenario. Both the diagnosis permission condition table and the diagnosis scenario are stored in the diagnosis service information management database 12 as described above.

  As shown in FIG. 3A, the diagnosis permission condition table includes a plurality of (N) records, and each record is based on a plurality of conditions (three conditions A, B, and C in this example). It is made up. Each record is managed with record numbers 1 to N.

Condition A is a vehicle speed, and a vehicle speed condition capable of performing remote diagnosis is set for each record.
Condition B is the vehicle position, and the condition of the vehicle position where remote diagnosis can be performed is set for each record. In this example, names such as “home”, “office”, and “home” are set as an example, but actual data stored in the diagnostic service information management database 12 includes coordinate values indicating these locations. It is. The coordinate value is set and stored according to the designated location when the user designates the location at the time of the contract of the remote diagnosis service. The contents of the condition B set at the time of contract can be changed later by the user as described above.

Condition C is a time zone, and a time zone condition in which remote diagnosis can be performed is set for each record.
In the present embodiment, when executing the remote diagnosis, the master ECU 20 determines whether all the conditions are satisfied for each record. If all the conditions set in any of the records are satisfied, it is determined that the permission condition is satisfied, that is, the condition that can execute the diagnosis is satisfied. Run diagnostics. On the other hand, if all the conditions A, B, and C are not satisfied for all records 1 to N, it is determined that the permission condition is not satisfied, and at least the remote diagnosis is not performed at that time.

  The determination of each condition by the master ECU 20 is performed as follows. The condition A (vehicle speed) is determined by obtaining a vehicle speed signal from the vehicle speed sensor 43 connected to the first ECU 40 from the first ECU 40. The condition B (own vehicle position) is determined based on own vehicle position information (coordinate values) acquired by the GPS 35 in the master ECU 20. The condition C (time zone) is determined based on the current time information acquired together with the vehicle position information by the GPS 35.

  If “No-care” is present in the diagnosis permission condition table, the condition is unquestioned. For example, in the case of the record N, the condition C is No-care. Therefore, when a diagnosis request is transmitted from the center 2 side, for example, if the current vehicle speed is 0 and the current position of the vehicle 3 is in the parents' home, the record N is permitted regardless of the time zone. It is determined that all the conditions are satisfied, and the remote diagnosis is executed.

  As shown in FIG. 3B, the diagnosis scenario transmitted from the center 2 together with the diagnosis permission condition table at the time of transmitting a diagnosis request shows the procedure for executing the diagnosis for each diagnosis menu to be executed. It is a thing. In the example of FIG. 3B, a plurality of diagnosis menus α, β,... Are set.

  Of these, the diagnostic menu α is accompanied by door locking / unlocking operations. As shown in the figure, it is confirmed that the engine is turned off (stopped) in step 1 and that each door is locked. Confirmation is performed. Confirmation of engine OFF is performed when the master ECU 20 acquires information indicating the engine state from the first ECU 40. The confirmation that the door is locked is performed by the master ECU 20 acquiring a lock position signal from the second ECU 50.

  In procedure 2, the unlocking operation of each door is performed, and the unlocking operation of each door at the time of the operation is confirmed. The unlock operation of each door is performed by the master ECU 20 sending an unlock command to the second ECU 50 and the second ECU 50 controlling the door lock mechanism 53 accordingly. Confirmation of the unlocking operation is performed based on various sensor signals including a lock position signal from the door position switch 54 when the second ECU 50 controls the door lock mechanism 53. In procedure 3, the operation of locking each door and the confirmation of the locking operation at that time are performed again.

  The diagnosis permission condition table shown in FIG. 3A may be prepared individually for each diagnosis menu, or one table may be used in common regardless of the diagnosis menu. The number of permission condition tables and the relationship with each diagnosis menu can be determined as appropriate.

Next, the remote diagnosis performed in the remote vehicle diagnosis system 1 of the present embodiment will be described more specifically based on FIGS.
First, the center side diagnosis process executed by the server 11 in the center system 10 of the center 2 will be described with reference to FIG. The server 11 executes the center side diagnosis process shown in FIG. 4 for each user.

  In this center-side diagnosis process, the server 11 first determines whether or not the diagnosis execution timing has arrived (S110). As described above, when the remote diagnosis is executed is preset by the user at the time of the contract. Specifically, for example, “diagnosis is executed on the first day of every month” and “diagnosis is executed every three months”. For this reason, the server 11 sequentially monitors the execution timing of the remote diagnosis based on the preset execution timing information.

  If it is determined that the diagnosis execution timing has arrived (S110: YES), the diagnosis target vehicle (vehicle 3 in this case) is diagnosed to the master ECU 20 in the vehicle 3 through the Internet network 5, the mobile phone network 4, or the like. A request is transmitted (S120). At this time, as described above, the diagnosis scenario and the diagnosis permission condition table stored in the diagnosis service information management database 12 are also transmitted together with the diagnosis request. After transmission of the diagnosis request or the like, a response from the vehicle 3 to the transmitted diagnosis request is awaited (S130).

  Receiving the diagnosis request, the master ECU 20 of the vehicle 3 executes the requested diagnosis according to the diagnosis scenario by executing a vehicle-side diagnosis process of FIG. 5 described later. However, the master ECU 20 of this embodiment does not always execute the requested diagnosis unconditionally when there is a diagnosis request from the center 2 side, but as described later, each of the master ECU 20 set in the diagnosis permission condition table The permission condition is searched for each record, and it is determined whether or not there is a record that satisfies all the permission conditions, that is, whether or not the diagnosis can be executed. In any one record, when all the permission conditions in the record are satisfied, the diagnosis is made as the permission condition is satisfied. When the diagnosis is permitted / executed on the vehicle 3 side, the diagnosis result is transmitted to the center 2 side after the diagnosis by the vehicle 3 is completed. On the other hand, if there is no record that satisfies all the permission conditions, a signal indicating that the condition is awaiting to be satisfied is transmitted as described below, as the permission condition is not satisfied.

  If any data is received after the transmission of the diagnosis request (S130: YES), the server 11 determines whether the received data is a diagnosis result from the vehicle 3 (S140). (S140: YES), determination based on the diagnosis result is performed (S150). Specifically, by comparing the diagnosis result with the case database 13, it is determined whether the vehicle 3 is normal or abnormal, whether it is necessary to enter a store or the like for repair, etc. I do.

  Then, the result of the determination is notified again (S160). The result notification in S160 may be notified by sending e-mail or the like to the user's mobile phone or the personal computer 7 at the user's home 6, or may be notified to the vehicle 3 again. Good. In that case, the master ECU 20 receives the result notification on the vehicle 3 side, and informs the user of the result through a display device connected to the multiplex communication line 30, for example, a meter (not shown), a display 71 connected to the navigation ECU 70, and the like. be able to.

  On the other hand, if the received data is not a diagnosis result (S140: NO), a diagnosis interruption determination is made as to whether or not the remote diagnosis should be interrupted (S170). Specifically, based on the elapsed time from the time when the diagnosis request is transmitted in S120, for example, when the time has not yet elapsed since the time of transmission, the situation should be seen for a while (remote diagnosis processing is performed). If it is determined that it should be continued, the process proceeds to S190.

  In S190, it is determined whether or not the received data is a signal indicating that the condition is awaited. If it is a signal indicating that the condition is awaited (S190: YES), that is, at least the vehicle 3 is not in a state where remote diagnosis can be executed at the present time, and the vehicle 3 is receiving an opportunity to execute remote diagnosis autonomously. It means that it is in a waiting process. Therefore, the process returns to S130 and waits for new data reception. On the other hand, if the signal is not a signal indicating that the condition is awaited (S190: NO), predetermined data processing corresponding to the received data is performed (S200), and the processing from S130 is performed again.

  On the other hand, in the diagnosis interruption process of S170, for example, when the vehicle 3 has been receiving a signal indicating that the condition has been waited for a long time since the diagnosis request was transmitted in S120, or the vehicle 3 has performed remote diagnosis. When it is predicted that the state that cannot be executed still continues for a while, it is determined that the remote diagnosis process should be interrupted once, and an interruption instruction is transmitted to the vehicle 3 (S180). By this interruption instruction, the diagnosis waiting state is canceled on the vehicle 3 side.

  Next, the vehicle-side diagnosis process executed by the master ECU 20 in the in-vehicle system 9 of the vehicle 3 will be described based on FIG. The ROM 32 of the master ECU 20 stores a vehicle-side diagnosis processing program. When a diagnosis request (S120 in FIG. 4) is received from the center 2 side, the MCU 31 stores the vehicle-side diagnosis processing program in the ROM 32. Follow the process.

  When this vehicle-side diagnosis process is started by receiving a diagnosis request from the center 2 side, the master ECU 20 first receives the diagnosis scenario and diagnosis permission condition table transmitted together with the diagnosis request and stores them in the RAM 33. Perform (S310). Then, the stored setting permission condition table is read (S320), a pointer for determining the record reading position in the diagnosis permission condition table is initialized, and preparations for reading the diagnosis permission condition table from the first record (record number = 1) are made ( S330).

Thereafter, a permission condition satisfaction determination process is performed to determine whether or not the diagnosis permission condition is satisfied (S340). Details of the permission condition establishment determination process are shown in FIG.
In the permission condition establishment determination process in S340, each condition (conditions A to C) set in the record designated by the pointer is compared with the current state of the vehicle 3 to check whether each condition is satisfied. As a result, as shown in FIG. 6, first, the vehicle speed set as the condition A is 3 is confirmed (S341). This vehicle speed is confirmed based on a vehicle speed signal from the first ECU 40.

  Then, the current value of the confirmed vehicle speed is compared with the contents set in the condition A in the record designated by the pointer, and it is determined whether or not they match (S342). For example, when the value of the pointer is 1 and the record number 1 is a determination target, it is determined whether or not the current value of the vehicle speed is 0 or less. When the setting content in the diagnosis permission condition table is “No-care”, it is treated as “match”.

  If it is determined in S342 that the current value of the vehicle speed does not match the setting contents of the condition A, the permission condition is not satisfied, that is, at least the record specified by the current pointer among the records does not satisfy the permission condition. Assuming that there is something, this permission condition establishment determination process is temporarily terminated without making a determination regarding the other conditions B and C in the record, and the process proceeds to S380 in FIG.

  In the determination of S342, if the current value of the vehicle speed matches the setting content of the condition A (including No-care), the vehicle of the vehicle 3 is set for the vehicle position set as the condition B in the subsequent S343. Check the current value of the position. This vehicle position is confirmed by acquiring the current position information from the GPS 35 built in the master ECU 20.

  Then, the current value of the confirmed vehicle position is compared with the contents set in the condition B in the record, and it is determined whether or not they match (S344). For example, when the value of the pointer is 1 and the record number 1 is a determination target, it is determined whether or not the vehicle 3 is located at home.

  In this determination of S344, if the current value of the vehicle position does not match the setting contents of the condition B, it is determined that the permission condition is satisfied without making a determination regarding the other condition C in the record, as the permission condition is not satisfied. The process is temporarily terminated and the process proceeds to S380 in FIG.

  If it is determined in S344 that the current value of the vehicle position matches the setting content of the condition B (including No-care), the current time is set for the time zone set as the condition C in the subsequent S345. Check. The confirmation of the current time is performed by acquiring current time information from the GPS 35 incorporated in the master ECU 20.

  Then, the confirmed current time is compared with the contents set in the condition C in the record, and it is determined whether or not they match (S346). For example, when the value of the pointer is 1 and the record number 1 is a determination target, it is determined whether or not the current time is between 3:00 and 5:00.

  If it is determined in S346 that the current time does not coincide with the setting contents of the condition C, it is determined that the permission condition is not satisfied, and the permission condition satisfaction determination process is temporarily terminated, and the process proceeds to S380 in FIG.

  If it is determined in S346 that the current time matches the setting contents of the condition C (including No-care), all the conditions A to C in the record are satisfied. The process proceeds to S350.

  Returning to FIG. 5, if it is determined that the permission condition is satisfied in the permission condition satisfaction determination process in S340, the vehicle 3 is processed in accordance with the diagnosis scenario (see FIG. 3B) transmitted from the center 2 stored in S310. The diagnosis is executed (S350).

  Note that the diagnosis scenario shown in FIG. 3B includes a plurality of diagnosis menus. That is, it includes a menu α for performing a series of diagnoses including a door lock / unlock operation and one or a plurality of diagnostic menus including a menu β. A diagnosis scenario is set for each diagnosis menu. When there are a plurality of menus to be diagnosed in this way, only one diagnostic menu (for example, only the menu α is first executed) is executed in the diagnostic processing of S350.

  When the diagnostic process is completed for the one diagnostic menu, it is determined whether the diagnosis is completed for all the diagnostic menus (S360). At this time, when the diagnosis is completed for all the diagnosis menus (S360: YES), the diagnosis results of each diagnosis menu are collectively transmitted to the center 2 (S370), and the vehicle-side diagnosis process is ended.

  If there is a diagnostic menu that has not yet been implemented (S360: NO), the process returns to S340, and one of the remaining diagnostic menus is subjected to a permission condition establishment determination process in S340, and the diagnostic menu is converted into a diagnostic scenario. The diagnostic processing along is performed (S350).

  On the other hand, if it is determined that the permission condition is not satisfied in the permission condition satisfaction determination process of S340, whether or not the current pointer value is smaller than the number at the end of the record number set in the diagnosis condition permission table, that is, It is determined whether or not there is a record that has not yet been subjected to permission condition establishment determination in S340 (S380). If the pointer value is smaller than the end of the record number (S380: YES), the pointer value is updated (incremented) (S390). Then, it is determined whether or not an interruption instruction has been received from the center 2 side (S400). If not received (S400: NO), the process returns to S340 again to perform permission condition establishment determination processing. The permission condition establishment determination process performed at this time is performed based on the setting contents of the record next to the record number at the previous time.

  Thus, until it is determined that the permission condition is satisfied for any one of the records, the permission condition satisfaction determination of S340 is sequentially executed for each record unless an interruption instruction is received from the center 2 side. If all the records (all records 1 to N in FIG. 3A) are determined not to satisfy the permission condition, a negative determination is made in S380, and the process proceeds to S410 to indicate that the condition is awaiting to be satisfied Is transmitted (notified) to the center 2. After that, the process returns to S330, and permission condition establishment determination is performed again from record 1.

  While the interruption instruction is not received from the center 2 side, the determination of whether or not the permission condition is satisfied is continued for each record (S340). However, when the interruption instruction is received from the center 2 side while the condition is not satisfied (S400). : YES), the vehicle-side diagnosis process is terminated as it is.

  Note that the vehicle-side diagnosis process may be terminated as it is after the notification of the condition establishment wait in S410, but in this embodiment, the establishment of the permission condition is monitored until an interruption instruction is issued from the center 2. I have to.

  By the way, in this embodiment, it is possible to update the contents of the diagnosis permission condition table set by the user at the time of the conclusion of the contract for the diagnosis service after the user's will. The update method is, for example, a method in which a user accesses the server 11 of the center system 10 from the personal computer 7 at home 6 and executes a predetermined table update process on the personal computer 7 or a navigation system in the vehicle 3. There is a method in which the master ECU 20 executes a predetermined table update process according to the operation content when the user performs a predetermined operation via the display 71 (touch panel).

  Thus, by using the navigation system of the personal computer 7 or the vehicle 3, the setting contents of the conditions A to B in the diagnosis permission condition table on the diagnosis service information management database 12 can be rewritten, new records can be added, deleted, etc. It can be carried out. Table update processing executed on the user side (the personal computer 7 or the master ECU 20 of the vehicle 3) and the center 2 side (the server 11) when updating the diagnosis permission condition table will be described with reference to FIG.

  In FIG. 7, the process on the left side is a table update process executed on the user side (the personal computer 7 or the master ECU 20), and the process on the right side is a table update process executed on the center 2 side (server 11).

  As shown in FIG. 7, when a user performs a predetermined operation and an update request is transmitted to the center 2 side (S510), the server 11 of the center 2 receives the update request from the user side ( In step S610, the current diagnosis permission condition table data stored in the diagnosis service information database 12 is transmitted to the transmission source user (S620).

  On the user side, the received data of the diagnosis permission condition table is received, and the contents of the current diagnosis permission condition table are displayed on the display device (if the personal computer 7 is displayed on the display or navigation system) based on the received data. If there is, it is displayed on the display 71) (S520). Then, a change operation of the table setting content by the user is accepted (S530), and when the change operation by the user is completed (S540: YES), the information after the change is transmitted to the center 2 side as update information (S550).

  For example, when the user wants to change the vehicle position of the condition B, the user registers a specific place with the memory point registration function of the navigation system (the navigation ECU 70) in the vehicle 3, and the name of the registered place is the coordinates of the place. This can be done by associating with the value and transmitting to the center 2 side.

  When the server 11 of the center 2 receives the update information transmitted from the user side (S630), it updates the contents of the current diagnosis permission condition table stored in the diagnosis service information database 12 based on the update information. (S640).

  As described above, in the present embodiment, the diagnosis permission condition table set by the user at the time of contract is not fixed as it is, but the user can change the contents as appropriate.

  In the remote vehicle diagnosis system 1 of the present embodiment described above, the condition for the vehicle 3 itself to determine whether or not the vehicle 3 may execute diagnosis in response to the diagnosis request from the center 2 is set as the permission condition. Stored in the center 2 as a table. When the timing for executing the remote diagnosis arrives, the center 2 transmits a diagnosis permission condition table and a diagnosis scenario to the vehicle 3 together with a diagnosis request. When the vehicle 3 receives the diagnosis request from the center 2, the vehicle 3 does not start the remote diagnosis unconditionally only by receiving the diagnosis request, but performs the diagnosis according to the diagnosis permission condition table received together with the diagnosis request. It is determined whether it is in a state that can be executed. The diagnosis is not executed unless the permission condition is satisfied, and the diagnosis is executed according to the diagnosis scenario when the permission condition is satisfied.

  Therefore, according to the remote vehicle diagnosis system 1 of the present embodiment, only when the conditions A to C set in the diagnosis permission condition table are all satisfied when the diagnosis request is transmitted from the center 2, the diagnosis scenario is set. Therefore, it is possible to prevent the user from being concerned about the execution of the diagnostic process.

  In particular, when the host vehicle position is set as the condition B and the vehicle 3 is present at the position set in the condition B, the diagnosis process is executed, which is different from the position set in the condition B. Since the diagnosis process is not executed when the position is present, it is possible to dispel the user's concerns (such as theft) from the place where the diagnosis process is performed.

  In particular, in the present embodiment, the door unlocking operation is included in the diagnosis scenario, and if such door unlocking operation is unconditionally performed regardless of the position of the vehicle, theft or the like There is a higher risk and user concerns are also increased. On the other hand, since the vehicle position is set as the condition B in the present embodiment, even if a diagnosis involving the unlocking operation of the door is executed, there is no concern for the user.

  In the remote vehicle diagnosis system 1 of the present embodiment, the diagnosis is permitted in the diagnosis service information management database 11 when the user accesses the server 11 of the center 2 using the home personal computer 7 or the navigation system of the vehicle 3. The setting contents of the condition table can be freely updated (changed, added, deleted, etc.). Therefore, a user-friendly system that is more user-friendly for the user is realized.

  Here, the correspondence between the components of the present embodiment and the components of the present invention will be clarified. In this embodiment, the conditions A, B, and C set in the diagnosis permission condition table all correspond to the permission conditions of the present invention, and the vehicle position set as the condition B among them is the diagnosis execution of the present invention. The diagnosis service information management database corresponds to the permission condition setting means of the present invention, the server 11 corresponds to the update means of the present invention, and the master ECU 20 corresponds to the permission condition determination means and diagnosis execution means of the present invention. The GPS 35 corresponds to the position acquisition means of the present invention, and the personal computer 7 and the navigation system (system consisting of the navigation ECU 70 and the display 71) correspond to the communication terminal of the present invention.

  In the table update process of FIG. 7, the process of S520 corresponds to the process executed by the permission condition acquisition unit of the present invention, the process of S530 corresponds to the process executed by the update operation reception unit of the present invention, and the process of S550 The process corresponds to the process executed by the update request transmission unit of the present invention, and the process of S640 corresponds to the process executed by the update unit of the present invention.

[Second Embodiment]
FIG. 8 shows a schematic configuration of an in-vehicle system constituting the remote vehicle diagnostic system of the present embodiment. The remote vehicle diagnosis system of the present embodiment is basically the same as the remote vehicle diagnosis system 1 of the first embodiment shown in FIG.

  The remote vehicle diagnosis system of the present embodiment is different from the remote vehicle diagnosis system 1 of the first embodiment mainly in that the vehicle 3 is a plug-in hybrid vehicle having a smart ignition function, and a diagnosis permission condition table. In addition to the conditions A to C, the condition D is further set, and the diagnosis menu α is different from the first embodiment. Therefore, in the following description, a configuration different from the first embodiment will be described in detail, and the same configuration as the first embodiment will be denoted by the same reference numeral as the first embodiment, and the detailed description thereof will be omitted.

  A plug-in hybrid vehicle is a vehicle configured to be able to charge a battery for driving an electric motor with an external commercial AC power supply to a known hybrid vehicle combining an internal combustion engine and an electric motor. is there.

  Therefore, as shown in FIG. 8, the in-vehicle system 80 of the present embodiment receives a power supply socket 91 for taking in a commercial AC power supply for charging (AC100V in this example) and the power supply socket 91. A charging control ECU 90 that controls charging of the motor driving battery 92 and the auxiliary battery 93 by the AC 100V power source is provided. The charging control ECU 90 is also connected to the multiplex communication line 30 and configured to be able to transmit and receive data to and from the master ECU 81.

  From the commercial AC power supply 101 in the user's home 6, AC 100V power is supplied to the vehicle side via a charging cable 102 having a charging power plug 100 connected to one end. That is, when the charging power plug 100 is connected to the power socket 91 of the vehicle, the AC 100V power from the commercial AC power supply 101 is supplied into the charging control ECU 90.

  The charge control ECU 90 executes control for charging the supplied AC 100V power to the batteries 92 and 93, detects the connection state of the charging power plug 100 to the vehicle-side power socket 91, and indicates the connection state. A plug connection state signal is transmitted to master ECU 81. That is, when the charging power plug 100 is connected to the power socket 91, a plug connection state signal indicating that it is connected is transmitted, and when the charging power plug 100 is not connected to the power socket 91, it is connected. Send a plug connection status signal to the effect.

In other words, the detection of the connection state can be said to be a detection of whether or not the batteries 92 and 93 are being charged by the AC 100 V power source supplied from the outside.
A method of detecting the connection state by the charging control ECU 90 is conceivable as appropriate. For example, it can be performed by determining whether or not AC 100 V power is supplied via the power socket 91. In addition, for example, a mechanism that mechanically turns on the switch when the charging power plug 100 is connected to the power socket 91 may be provided, and the connection state may be detected based on the state of the switch. .

  Moreover, the smart ignition function with which the vehicle of this embodiment is provided is that a user (driver) brings a regular portable device (smart key), that is, a portable device having an ID code that matches the ID code on the vehicle side into the vehicle interior. It is a function that only allows the engine to start.

  The user can start the engine by holding this regular portable device, sitting in the driver's seat, and pressing a push switch 98 provided near the handle. Further, by pushing the push switch 98, only an accessory switch can be turned on, or an ignition switch can be turned on together with the accessory switch, as in a general key system in which a key is inserted into a key cylinder and rotated. .

  Further, the in-vehicle system 80 of the present embodiment has a power supply control ECU 96 as an ECU connected to the multiple communication line 30. The power control ECU 96 has various functions for controlling power supply to each part in the vehicle, and one of them is when the push switch 98 is pressed while the user is carrying a regular portable device. According to the operation, the relay control box 97 is operated to turn on only the accessory switch, turn on the ignition switch, and further start the engine.

  Also in this embodiment, when the master ECU 81 receives a diagnosis request from the center 2 as in the first embodiment, the master ECU 81 performs remote diagnosis based on the diagnosis scenario and diagnosis permission condition table received together with the request for diagnosis. I do.

  The center-side diagnosis process executed by the server 11 of the center 2 at the time of this remote diagnosis is basically the same as that in FIG. 4 of the first embodiment. However, the diagnosis scenario and diagnosis permission condition table transmitted to the vehicle side in S120 in the center side diagnosis process are different from those in the first embodiment (FIG. 3).

  Further, the vehicle-side diagnosis process executed on the vehicle side during the remote diagnosis is basically the same as that in FIG. 5 of the first embodiment. However, the permission condition establishment determination process of S340 in the vehicle side diagnosis process of FIG. 5 is different from that of the first embodiment (FIG. 6). This is because the configuration of the diagnosis permission condition table transmitted from the center 2 side is different from that of the first embodiment. Therefore, in the following description, a diagnosis scenario, a diagnosis permission condition table, and a permission condition establishment determination process according to the present embodiment will be described.

  FIG. 9 shows an example of the diagnosis permission condition table and diagnosis scenario of the present embodiment. As shown in FIG. 9A, the diagnosis permission condition table of this embodiment also includes a plurality (N) of records. However, in this embodiment, each record is composed of four conditions including a condition D in addition to the conditions A, B, and C. In this respect, the diagnosis permission condition table of the first embodiment (FIG. 3 ( Different from a)).

  Condition D is a connection state of the charging power plug 100. That is, the connection state of the charging power plug 100 to the power socket 91 on the vehicle side is set for each record as the execution condition of the remote diagnosis.

  In this example, in the record 2, “plug connection” is set as the condition D. In the record 2, all other conditions A, B, and C are No-care. Therefore, when a diagnosis request is transmitted from the center 2 side, if the power plug for charging 100 is connected to the power socket 91, the record 2 is recorded regardless of other vehicle speed, own vehicle position, and time zone. Diagnosis is executed as the permission condition is satisfied. The determination of the condition D by the master ECU 20 is specifically made based on a plug connection state signal from the charge control ECU 90.

In the diagnosis scenario of this embodiment, as shown in FIG. 9B, the procedure at the time of executing the diagnosis is specifically shown for each of a plurality of diagnosis menus α, β,.
Of these, the diagnostic menu α is accompanied by an operation in which the accessory switch is turned on with the engine turned off (that is, battery power is consumed when the engine is stopped). It is confirmed that the engine is turned off (stopped). The confirmation of the engine OFF is the same as the procedure 1 in the diagnosis menu α in FIG.

  In procedure 2, an operation of turning on the accessory switch is performed. The accessory switch is turned on when the master ECU 81 transmits a switch operation command to the power supply control ECU 96 to turn on the accessory switch. When receiving the switch operation command from the master ECU 81, the power supply control ECU 96 controls the relay control box 97 to turn on the accessory switch. In step 3, an operation check of the navigation system (the navigation ECU 70 or the like) is performed.

  In the diagnosis permission condition table of the present embodiment, as a background of setting the connection state of the charging power plug 100 as the condition D, the battery running up during diagnosis is one of the concerns in executing remote diagnosis There is. As in the diagnosis menu α of the present embodiment, when the diagnosis is performed with the operation of turning on the accessory switch while the engine is turned off (stopped), the battery is not charged while the engine is turned off. If the on-state of the accessory switch is continued, the battery may go up.

  On the other hand, in the present embodiment, since the vehicle is a plug-in hybrid vehicle, even when the engine is OFF, the charging power source (AC 100V) is supplied via the power socket 91 and each of the batteries 92 and 93 is supplied. While the battery is being charged, there is no worry of running out of the battery. Accordingly, “plug connection”, that is, “when the charging power plug 100 is connected to the power socket 91” is set as a permission condition capable of executing remote diagnosis. In the record 2, regardless of the vehicle state corresponding to each of the other conditions A to C, the diagnosis is permitted if the condition D is satisfied (that is, if charging is being executed).

Next, the permission condition establishment determination process (the process of S340 in the vehicle side diagnosis process of FIG. 5) executed by the master ECU 81 of the present embodiment will be described with reference to FIG.
Of the permission condition establishment determination process of the present embodiment shown in FIG. 10, the processes of S710 to S760 are the same as the processes of S341 to S346 of the permission condition establishment determination process of the first embodiment shown in FIG. Exactly the same. Therefore, description of S710-S760 is abbreviate | omitted here.

  If it is determined in S760 that the current time matches the setting contents of the condition C (including No-care), the current connection state of the charging power plug 100 set as the condition D is determined in S770. Check the connection status. This connection state is confirmed based on a plug connection state signal transmitted from the charging control ECU 90 to the master ECU 81.

  Then, the confirmed connection state is compared with the contents set in the condition D in the record, and it is determined whether or not they match (S780). For example, when the pointer value is 2 and the record number 2 is a determination target, it is determined whether or not the charging power plug 100 is connected to the power socket 91.

  In the determination in S780, if the connection state does not match the setting contents of the condition D (in the case where the charging power plug 100 is not connected to the power socket 91 in the record 2), it is determined that the permission condition is not satisfied. The permission condition establishment determination process is once ended, and the process proceeds to S380 in FIG.

  On the other hand, if it is determined in S780 that the connection state matches the setting content of the condition D (in the case where the charging power plug 100 is connected to the power socket 91 in the record 2), the four conditions A to Since all D are satisfied, the process proceeds to S350 in FIG.

  According to the remote vehicle diagnosis system of the present embodiment described above, the diagnosis process is executed when the batteries 92 and 93 of the vehicle 3 are charged when a diagnosis request is received from the center 2. Therefore, even if a diagnosis with a large power consumption is executed, there is no risk of battery exhaustion. For this reason, it is possible to eliminate the user's concern (battery exhaustion) caused by the battery power consumption during the execution of the diagnostic process.

  In particular, the present embodiment includes a process for turning on the accessory switch (consuming battery power) while the engine is turned off as a diagnostic menu. If battery power consumption continues while the engine is turned off, the battery will run out. Although there is a concern, the diagnostic process is executed only while the battery is being charged.

  In this embodiment, the AC 100V power input from the charging power plug 100 via the power socket 91 corresponds to the charging power of the present invention, and the power socket 91 corresponds to the charging power input means of the present invention. The charge control ECU 90 corresponds to the charge control means and the charge state detection means of the present invention.

[Third Embodiment]
FIG. 11 shows a diagnosis permission condition table used in the remote vehicle diagnosis system of the present embodiment. FIG. 12 shows a permission condition establishment determination process (( 5 shows the processing of S340 in the vehicle-side diagnosis processing of Fig. 5. The remote vehicle diagnosis system of this embodiment is compared with the remote vehicle diagnosis system 1 of the first embodiment, and the diagnosis permission condition table (Fig. 11). In addition, the permission condition establishment determination process (FIG. 12) is different, and other configurations, functions, and the like are basically the same as those in the first embodiment.

  In the diagnosis permission condition table of this embodiment, as shown in FIG. 11, three types of permission conditions of conditions A to B are set for each record. In this respect, the table of the first embodiment (FIG. )). In this embodiment, not only conditions A to C are set, but a logical combination of these three conditions is set for each record as a “conditional expression”. The “conditional expression” is information that describes a logical combination of a plurality of permission conditions for each record using a logical expression. In this example, by setting “conditional expressions” for the conditions A to C, weighting of each condition is set for each record.

  For example, in the case of record 1, since the conditional expression is set to “condition A × condition B × condition C”, the permission condition of this record 1 is satisfied when all three conditions A to C are satisfied, If any one of them is not satisfied, the permission condition is not satisfied. That is, for the record 1, the weights of the conditions A, B, and C are the same level. Therefore, the record 1 is handled in the same manner as in the first embodiment and the second embodiment.

  On the other hand, for example, in the case of record 2, the conditional expression is set to “(condition A + condition B) × condition C”. Therefore, in order for the permission condition of this record 2 to be satisfied, at least condition C needs to be satisfied. However, the condition A and the condition B are not necessarily satisfied at the same time, and it is sufficient that at least one of the condition A or the condition B is satisfied. That is, for this record 2, the weight of condition C is set higher than the weight of condition A and condition B.

  Therefore, for example, even if the vehicle is stopped at the user's friend's house and does not satisfy the condition B, if both of the other two conditions A and C are satisfied, as a result, the permission condition of the record 2 Will be established. On the other hand, for example, even if the vehicle is stopped at the office and both the conditions A and B are satisfied, if the time zone is out of the condition C, the permission condition of the record 2 is not satisfied as a result. .

  In the record N, since the condition C is set to No-care, the conditional expression is set to “condition A × condition B”, and if both the condition A and the condition B are satisfied regardless of the time zone, the record N The permission condition is satisfied.

  Next, in the remote vehicle diagnosis system of the present embodiment in which the diagnosis permission condition table is set as shown in FIG. 11, the permission condition determination process (S340 process in FIG. 5) executed by the master ECU is based on FIG. explain.

When this process is started, the master ECU first reads the “conditional expression” set in the record indicated by the pointer (S810).
Then, as in S341 to S342 in FIG. 6, for the vehicle speed set as the condition A, the current value of the vehicle speed of the vehicle 3 is confirmed (S820), and the current value of the confirmed vehicle speed and the record specified by the pointer The contents set in condition A in the middle are compared to determine whether or not they match (S830).

  In the determination process of S830, if the current value of the vehicle speed does not coincide with the setting content of the condition A (S830: NO), “0” is set in the corresponding term in the conditional expression (here, the term of the condition A). Then, the process proceeds to S860. On the other hand, when the current value of the vehicle speed matches the setting content of condition A (including No-care), “1” is set to the corresponding term (condition A) in the conditional expression (S840), and S860 is entered. move on.

  In subsequent S860 to S870, as in S343 to S344 of FIG. 6, the current value of the vehicle position of the vehicle 3 is confirmed for the vehicle position set as the condition B (S860), and the vehicle position of the confirmed vehicle position is confirmed. The current value is compared with the contents set in the condition B in the record designated by the pointer, and it is determined whether or not they match (S870).

  In the determination process of S870, if the current value of the vehicle position does not match the setting contents of the condition B (S870: NO), “0” is set to the corresponding term in the conditional expression (here, the term of the condition B). Set and proceed to S900. On the other hand, if the current value of the vehicle position matches the setting contents of condition B (including No-care), “1” is set to the corresponding term (condition A) in the conditional expression (S880), Proceed to S900.

  In subsequent S900 to S910, as in S345 to S346 of FIG. 6, the current time (current value) is confirmed for the time zone set as the condition C (S900), and the confirmed current time and pointer are used. The contents set in the condition C in the designated record are compared, and it is determined whether or not they match (S910).

  In the determination process of S910, when the current time does not coincide with the setting content of the condition C (S910: NO), “0” is set in the corresponding term in the conditional expression (here, the term of the condition C), Proceed to S940. On the other hand, when the current time matches the setting contents of the condition C (including No-care), “1” is set in the corresponding term (condition C) in the conditional expression (S920), and the process proceeds to S94.

  In S940, the set value of “1” or “0” is applied to each conditional term (conditions A, B, C) in the conditional expression read in S810, and the calculation result of the entire conditional expression is obtained. obtain. Then, it is determined whether or not the calculation result is “1”.

  If the calculation result is “1” in this determination, it is determined that the permission condition of the record is satisfied, and the process proceeds to S350 in FIG. 5 and diagnosis according to the diagnosis scenario is executed. On the other hand, if the calculation result is “0”, it is determined that the permission condition is not satisfied for the record, and the process proceeds to S380 in FIG.

  Also in this embodiment, the user can update the setting contents of the diagnosis permission condition table via the personal computer 7 or the vehicle navigation system, and at that time, the contents of the conditions A, B, and C are updated. Of course, conditional expressions can be updated.

  According to the remote vehicle diagnosis system of the present embodiment described above, in the diagnosis permission condition table, in addition to the conditions A to C, a conditional expression indicating a logical combination of these is set. In order to determine whether or not the diagnosis may be executed based on the calculation result of the logical expression, by appropriately setting the logical expression, it is possible to set a relative weight among a plurality of permission conditions. Remote diagnosis can be performed in a state that is more appropriate to the intention.

  In the permission condition establishment determination process of FIG. 12, the process of S820 to S930 corresponds to the process executed by the individual determination unit of the present invention, and the process of S940 corresponds to the process executed by the final determination unit of the present invention.

[Modification]
Although the embodiments of the present invention have been described above, the embodiments of the present invention are not limited to the above-described embodiments, and can take various forms as long as they belong to the technical scope of the present invention. Needless to say.

  For example, in the above embodiment, a plurality of records are set in the diagnosis permission condition table, and remote diagnosis can be executed when the permission condition of any one of the records is satisfied. However, only one record is available. It may be. Also, regarding the number of conditions to be set, although three conditions A to C in the first embodiment and four conditions A to D in the second embodiment, this is just an example. Furthermore, as the contents of the conditions, in the above embodiment, the vehicle speed, the vehicle position, the time zone, and the connection state of the power plug for charging are set, but this is also an example only, the number of conditions and the contents thereof are When performing remote diagnosis, it can be determined as appropriate so as not to cause various concerns for the user.

  In the above embodiment, as shown in FIG. 3B and FIG. 9B, a plurality of menus α, β,... Are set for the diagnosis scenario, but this is also an example only. The number of menus may be one, and the contents of each procedure in the diagnosis scenario are only examples.

  In the first embodiment, the user communicates with the center 2 side using the personal computer 7 at home 6 or the navigation system in the vehicle 3, and is stored in the diagnostic service information management database 12 of the center 2. Although the description has been made assuming that the contents of the diagnosis permission condition table can be changed (updated), the method of updating the diagnosis permission condition table by the user is not limited to this. An update may be offered via a store or the like, or the user himself / herself may be able to update by accessing the server 11 of the center 2 from a mobile phone, and there are various specific methods of updating.

  In the above-described embodiment, the diagnosis permission condition table is described as being notified from the center 2 to the vehicle 3 together with the diagnosis request. However, the present invention is not limited to this. For example, the master ECU 20 previously holds the program information as program information on the vehicle 3 side. It can also be made to keep.

  However, the latest diagnosis permission condition table can be transmitted each time a diagnosis request is made by transmitting the information one by one from the center 2 each time remote diagnosis is executed as in the above embodiment.

  In the above embodiment, the remote diagnosis is performed, that is, the diagnosis request for the remote diagnosis from the center 2 to the vehicle 3 is executed in advance with the execution time information (for example, “monthly ○ day”, “3 months” However, this is merely an example, and there are various possible timings for the center 2 to transmit a diagnosis request to the vehicle 3 side.

  In addition, the vehicle 3 is not limited to executing a diagnosis only when there is a diagnosis request from the center 2, and when a failure or the like is detected in the vehicle 3, the fact is transmitted from the vehicle 3 to the center 2, Based on this, a diagnosis scenario necessary for the center 2 to identify the cause of the failure is set and sent to the vehicle 3 side together with the diagnosis permission condition table, and the vehicle 3 is diagnosed based on the sent diagnosis permission condition table. It is also possible to configure a remote vehicle diagnosis system that determines whether or not it is feasible, and executes diagnosis according to a diagnosis scenario when it is determined that diagnosis can be performed.

  In the second embodiment, the case where the vehicle is a plug-in hybrid vehicle has been described. However, the present invention is not limited to a plug-in hybrid vehicle, and is an electric vehicle including only an electric motor, for example, so that a battery can be charged from outside. The remote vehicle diagnosis system of the second embodiment can be configured as long as the vehicle is configured such that the battery in the vehicle can be externally charged.

  In the above-described embodiment, the communication between the center 2 and the vehicle 3 is described as being performed via the Internet network 5 and the mobile phone network 4, but the communication network between the center 2 and the vehicle 3 is particularly It is not limited.

It is explanatory drawing showing schematic structure of the remote vehicle diagnostic system of 1st Embodiment. It is a block diagram showing the schematic structure of the in-vehicle system which comprises the remote vehicle diagnostic system of 1st Embodiment. It is a figure showing the information which a remote diagnosis center transmits to a vehicle at the time of remote diagnosis execution of 1st Embodiment, (a) is a diagnosis permission condition table, (b) is a diagnosis scenario. It is a flowchart showing the center side diagnostic process performed with the server in a remote diagnostic center. It is a flowchart showing the vehicle side diagnostic process which master ECU in a vehicle of 1st Embodiment performs. It is a flowchart showing the detail of the permission condition establishment determination process of S340 in the vehicle side diagnosis process of 1st Embodiment. It is a flowchart showing the table update process each performed by the user side and the center side at the time of updating of a diagnosis permission condition table. It is a block diagram showing the schematic structure of the in-vehicle system which comprises the remote vehicle diagnostic system of 2nd Embodiment. It is a figure showing the information which a remote diagnosis center transmits to a vehicle at the time of remote diagnosis execution of 2nd Embodiment, (a) is a diagnosis permission condition table, (b) is a diagnosis scenario. It is a flowchart showing the detail of the permission condition establishment determination process of 2nd Embodiment. It is a figure showing the diagnosis permission condition table of 3rd Embodiment. It is a flowchart showing the detail of the permission condition establishment determination process of 3rd Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Remote vehicle diagnostic system, 2 ... Center, 3 ... Vehicle, 4 ... Mobile telephone network, 5 ... Internet network, 6 ... Home, 7 ... Personal computer, 8 ... Communication line, 9,80 ... In-vehicle system, 10 ... Center Internal system, 11 ... server, 12 ... diagnostic service information management database, 13 ... case database, 14 ... network, 20, 81 ... remote diagnostic master ECU, 21, 22 ... antenna, 23 ... power supply circuit, 24 ... transceiver, 30 ... Multiple communication lines, 31 ... MCU, 32 ... ROM, 33 ... RAM, 34 ... Communicator, 35 ... GPS, 36 ... Communication controller, 40 ... First ECU, 41, 51, 61 ... Actuator group, 42, 52, 62 ... Sensor group, 43 ... vehicle speed sensor, 50 ... second ECU, 53 ... door lock mechanism, 54 ... lock position switch, 60 ... third CU, 70 ... Navi ECU, 71 ... Display, 90 ... Charge control ECU, 91 ... Power socket, 92 ... Battery for motor drive, 93 ... Battery for auxiliary equipment, 96 ... Power control ECU, 97 ... Relay control box, 98 ... Push switch, 100 ... charging power plug, 101 ... commercial AC power supply, 102 ... charging cable

Claims (5)

A remote vehicle diagnostic method in which a vehicle executes a diagnostic process in accordance with a diagnostic request transmitted by a center,
Permit conditions under which the vehicle can execute the diagnostic process are set in advance,
When the vehicle receives the diagnosis request from the center, the vehicle determines whether or not the state of the vehicle at the time of reception satisfies the permission condition. When the vehicle satisfies the permission condition, the diagnosis processing is performed. the execution,
The remote vehicle diagnosis method according to claim 1 , wherein at least a position of the vehicle capable of executing the diagnosis process is set as the permission condition . The remote vehicle diagnosis method according to claim 1,
The vehicle is configured such that a battery provided in the vehicle can be charged by charging power supplied from the outside of the vehicle,
The remote vehicle diagnosis method, wherein at least the charging of the battery with the charging power is performed as the permission condition. A remote vehicle diagnostic system in which a vehicle executes a diagnostic process according to a diagnostic request transmitted by a center,
A permission condition setting means in which permission conditions under which the vehicle can execute the diagnosis process are set;
In the permission condition setting means, at least a diagnosis executable position that is a position of the vehicle capable of executing the diagnosis processing is set as the permission condition,
The vehicle is
Position acquisition means for acquiring the position of the vehicle;
A permission condition for determining whether or not the state of the vehicle at the time of reception satisfies the permission condition based on the permission condition set in the permission condition setting means when the diagnosis request is received from the center Judgment means,
Diagnosis execution means for executing the diagnosis process when the permission condition determination means determines that the permission condition is satisfied;
Equipped with a,
The permission condition determining means, when receiving the diagnosis request from the center, at least the position of the vehicle at the time of reception acquired by the position acquiring means is set in the permission condition setting means as the determination. Judgment is made as to whether or not it matches the diagnosis executable position
A remote vehicle diagnostic system characterized by that. The remote vehicle diagnostic system according to claim 3 ,
The vehicle is
Charging power input means for inputting the charging power of the battery included in the vehicle from the outside of the vehicle;
Charging control means for controlling charging of the battery with the charging power input to the charging power input means;
Charging state detection means for directly or indirectly detecting whether or not the battery is being charged based on the charging power;
With
In the permission condition setting means, as the permission condition, it is set that the battery is being charged based on at least the charging power,
The permission condition determining means, when receiving the diagnosis request from the center, determines whether or not the battery is being charged based on at least the charging power as the determination. A remote vehicle diagnosis system, which is performed based on a detection result by a state detection means. An in-vehicle diagnosis device that is mounted on a vehicle and executes diagnosis processing according to a diagnosis request transmitted from a center,
Position acquisition means for acquiring the position of the vehicle;
Permission condition determination means for determining whether or not the diagnosis process according to the diagnosis request is executable based on a preset permission condition when the diagnosis request is received from the center;
Diagnosis execution means for executing the diagnosis process when the permission condition determination means determines that the permission condition is satisfied;
Equipped with a,
As the permission condition, at least a diagnosis executable position that is a position of the vehicle capable of executing the diagnostic processing is set,
The permission condition determining means, when receiving the diagnosis request from the center, at least the position of the vehicle at the time of reception acquired by the position acquiring means is set in the permission condition setting means as the determination. Judgment is made as to whether or not it matches the diagnosis executable position
An in-vehicle diagnostic apparatus characterized by that.