Control system and control method

Abstract

To provide a control system and a control method that can more reliably suppress the execution of recording processing of an event file unrelated to an accident.SOLUTION: A control system 10 for controlling a recording device that executes event recording processing associated with impact detection of a vehicle, includes a calculation unit 11 and a control unit 12. The calculation unit 11 calculates, based on an image including an impact object that applies an impact to a vehicle, an impact object passing time which indicates a time from the present time until the vehicle passes through the impact object. The control unit 12 controls the event recording processing so that before the vehicle passes the impact object, the recording device does not execute the event recording processing based on the impact object passing time.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a control system and a control method.

Background Art

[0002] Patent Document 1 discloses an impact detection malfunction prevention device that can suppress the execution of event file recording processing when an impact not caused by an accident is detected. In the impact detection malfunction prevention device disclosed in Patent Document 1, a location where impact detection has been performed a predetermined number of times or more is registered as an impact detection malfunction location regardless of whether it is related to an accident, and at the impact detection malfunction location, the execution of event file recording processing is suppressed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the impact detection malfunction prevention device disclosed in Patent Document 1 described above, if it is not registered in advance as an impact detection malfunction location, it is impossible to suppress the execution of event file recording processing that has nothing to do with an accident.

[0005] The present disclosure has been made in view of such circumstances, and an object thereof is to provide a control system and a control method that can more reliably suppress the execution of event file recording processing that has nothing to do with an accident.

Means for Solving the Problems

[0006] The control system according to the present disclosure is a control system that controls a recording device that executes event recording processing associated with impact detection of a vehicle, A calculation unit that calculates an impact object passing time indicating the time from the current point until the vehicle passes the impact object based on an image including the impact object that imparts an impact to the vehicle; A control unit that controls the event recording process so that, before the vehicle passes the impact object, it becomes a non-recording period during which the recording device does not execute the event recording process based on the impact object passing time; It is provided with.

[0007] The control system according to the present disclosure calculates the impact object passing time from an image, and controls the event recording process so as to be a non-recording period during which the event recording process is not executed based on the impact object passing time. With such a configuration, it is possible to more reliably prevent the recording process of event files unrelated to an accident from being executed.

[0008] The control method according to the present disclosure is A control method for controlling a recording device that executes an event recording process associated with impact detection of a vehicle, Based on an image including an impact object that imparts an impact to the vehicle, calculate an impact object passing time indicating the time until the vehicle passes the impact object, Before the vehicle passes the impact object, based on the impact object passing time, control the event recording process so that it becomes a non-recording period during which the recording device does not execute the event recording process, The computer executes the process.

[0009] In the control method according to the present disclosure, the impact object passing time is calculated from an image, and the event recording process is controlled based on the impact object passing time so as to be a non-recording period during which the event recording process is not executed. With such a configuration, it is possible to more reliably prevent the recording process of event files unrelated to an accident from being executed.

Effect of the Invention

[0010] According to the present disclosure, it is possible to provide a control system and a control method that can more reliably prevent the recording process of event files unrelated to an accident from being executed.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Modes for Carrying Out the Invention

[0012] Hereinafter, the present disclosure will be described through embodiments of the invention, but the invention according to the claims is not limited to the following embodiments. Also, not all of the configurations described in the embodiments are necessarily essential as means for solving the problems. For the sake of clarity of explanation, the following description and drawings have been appropriately omitted and simplified. In each drawing, the same elements are denoted by the same reference numerals, and redundant explanations are omitted as necessary.

[0013] (Embodiment 1) <Control System> The control system according to Embodiment 1 will be described. FIG. 1 is a block diagram illustrating the control system according to Embodiment 1. As shown in FIG. 1, the control system 10 includes a calculation unit 11 and a control unit 12.

[0014] The control system 10 is a control system that controls event recording processing associated with impact detection of a vehicle. The event recording processing is a process of recording, when the vehicle detects an impact while traveling, the camera video file and sensor values at the time of impact detection as short-time event files separately from normal recording when the impact value exceeds a set sensor threshold value. The recording destination is a storage unit (not shown) inside and outside the control system 10. The event file is stored, for example, in the event folder of the storage unit. The control system 10 calculates the passing time of the impact object from the image, and controls the event recording processing so that it becomes a non-recording period during which the event recording processing is not executed based on the passing time of the impact object.

[0015] The control system 10 is configured to be able to communicate with the recording device 13. The recording device 13 executes event recording processing. The recording device 13 is, for example, a drive recorder, and the control system 10 controls the event recording processing of the drive recorder. However, as shown in the block diagram of FIG. 1, the control system 10 and the recording device 13 are not limited to a configuration in which they can communicate with each other, and a configuration in which the calculation unit 11 and the control unit 12 of the control system 10 are included in the recording device 13 may also be used.

[0016] Also, a configuration in which a part of the control system 10 (one of the calculation unit 11 and the control unit 12) is included in the recording device 13 and a part of the control system 10 (the other of the calculation unit 11 and the control unit 12) is included in a server (not shown) to execute distributed processing may be used. Hereinafter, the details of the calculation unit 11 and the control unit 12 shown in FIG. 1 will be described. Note that the control system 10 will be described as controlling the event recording processing of the drive recorder.

[0017] <Calculation of the Passing Time of the Impact Object> First, the calculation unit 11 will be described. The calculation unit 11 calculates the impact object passing time indicating the time from the current point until the vehicle passes the impact object based on an image including the impact object that gives an impact to the vehicle. The impact object is typically the road surface including unevenness, but is not limited thereto, and includes objects that can give an impact when the vehicle passes, for example, speed bumps, stones, and a road surface with steps.

[0018] With reference to FIG. 2, the method for calculating the impact object passing time will be described. FIG. 2 is a diagram showing the state when the vehicle passes a step. As shown in FIG. 2, the vehicle C1 is about to pass the step IP1 located ahead. The step IP1 is an example of an impact object. The calculation unit 11 calculates the distance from point S1 to point S2 and the distance from point S2 to point S3 by analyzing the image including the step IP1. Point S1 indicates the current position of the vehicle C1, point S2 indicates the position of the step closest to point S1, and point S3 indicates the position of the step farthest from point S2. Note that the current point of the vehicle C1 indicates the point where the vehicle C1 is located when starting the process of calculating the impact object passing time.

[0019] Here, the vehicle C1 can obtain information regarding the vehicle speed from position information such as GPS. Then, the calculation unit 11 (control system 10) obtains information regarding the vehicle speed from the vehicle C1. The calculation unit 11 can calculate the passing time of the distance by dividing the distance by the vehicle speed. In the example shown in FIG. 2, the calculation unit 11 divides the distance from point S1 to point S2 by the vehicle speed and calculates it as 3 seconds. Also, in the example shown in FIG. 2, the calculation unit 11 divides the distance from point S2 to point S3 by the vehicle speed and calculates it as 1 second. In the above manner, the calculation unit 11 can calculate the impact object passing time indicating the time until the vehicle C1 passes the step IP1 as 4 seconds.

[0020] Note that the calculation unit 11 may improve the accuracy of distance calculation by comparing the distance from point S1 to point S2 and the distance from point S2 to point S3 obtained from the image with the values obtained from the distance sensor mounted on the vehicle C1.

[0021] <Control of Event Recording Process> Next, the control unit 12 will be described. Before the vehicle passes through an impact object, the control unit 12 controls the event recording process so that it becomes a non-recording period during which the event recording process is not executed, based on the impact object passing time. During the non-recording period, the event recording process is not executed, but impact detection can be performed. Note that event recording is a so-called write-protected recording.

[0022] That is, the non-recording period is a period during which, when the vehicle is impacted by an impact object, impact detection is performed but the event recording process is not executed. Also, during the non-recording period, the event recording process is not executed, but normal recording (so-called always-recordable overwrite recording) is being performed. Therefore, even if an accident occurs during the non-recording period, the user can view the moving images recorded normally.

[0023] A method of controlling the event recording process will be described. In FIG. 2, the control unit 12 controls, for example, so that it becomes a non-recording period during which the event process of the drive recorder is not executed for 4 seconds of the impact object passing time. Thereby, it is possible to suppress the execution of the recording process of an event file not related to an accident.

[0024] When the recording process of an event file not related to an accident is executed, it compresses the capacity of the event folder in the storage unit (not shown in FIG. 1). Generally, since the event folder is not overwritten, when there is no free capacity, the user needs to organize the files. However, in the control system 10 according to Embodiment 1, since an event file not related to an accident is not stored in the event folder, it does not compress the capacity. Furthermore, the user can easily find the necessary event files, for example, the event files related to an accident.

[0025] In addition, since the control unit 12 controls so as not to execute the event recording process of the drive recorder using the impact object passing time calculated by the calculation unit 11 in real time, history information recording the execution status of past event recordings as in the prior art is unnecessary. Therefore, the control system 10 can more reliably prevent the recording process of event files unrelated to accidents from being executed.

[0026] Here, an example has been described in which the control unit 12 controls so that the event process of the drive recorder is not executed during a non-recording period of 4 seconds of the impact object passing time. However, it is not limited to this, and the control unit 12 may control so that the non-recording period during which the event process of the drive recorder is not executed is a time obtained by extending or shortening the impact object passing time. As a result, when the calculation unit 11 calculates the impact object passing time, the current location S1 of the calculation start point, the location S2 of the impact object including the step IP1 in front of the vehicle, and the location S3 after passing are specified based on the image. However, due to a decrease in the sharpness of the image or the like and the reception of vehicle speed information of the vehicle C1 from the GPS position information, it is possible to cope with a situation where accurate time calculation is difficult due to a decrease in the reception status.

[0027] In this way, as long as the control unit 12 is configured to control the event recording process of the drive recorder so as to be in a non-recording period during the impact object passing time or the time obtained by extending or shortening the impact object passing time before the vehicle passes the impact object. A method for the control unit 12 to control so that the event recording process of the drive recorder is executed again will be described later using a flowchart.

[0028] Note that when the control system 10 acquires information on the surrounding environment where accident-prone situations such as signals, crosswalks, and intersections are close from the vehicle's environment sensor, it does not necessarily need to control so that the event recording process of the drive recorder is not executed during a non-recording period. With such a configuration, the control system 10 can record an event file when there is a risk of an accident.

[0029] <Control method> Next, the control method according to Embodiment 1 will be described. FIG. 3 is a flowchart illustrating the driving support method according to Embodiment 1.

[0030] First, the control system 10 determines whether an impact object is included in the image of the drive recorder (step ST1). When an impact object is included in the image of the drive recorder (step ST1: YES), the control system 10 (calculation unit 11) calculates an impact object passing time indicating the time until the vehicle passes the impact object based on the image including the impact object that gives an impact to the vehicle (step ST2). On the other hand, when an impact object is not included in the image of the drive recorder (step ST1: NO), the process of step ST1 is repeatedly executed.

[0031] Subsequent to step ST2, the control unit 12 controls the event recording process of the drive recorder so that a non-recording period in which the event recording process is not executed is set based on the impact object passing time before the vehicle passes the impact object (step ST3).

[0032] Next, the control unit 12 determines whether the vehicle has detected an impact (step ST4). When the vehicle has detected an impact (step ST4: YES), the control unit 12 controls the event recording process of the drive recorder so that the event recording process of the drive recorder is executed again (step ST6).

[0033] On the other hand, when the vehicle has not detected an impact (step ST4: NO), the control unit 12 determines whether the impact object passing time has elapsed (step ST5). When the impact object passing time has elapsed (step ST5: YES), the control unit 12 executes the process of step ST6. In step ST5: YES, although no impact has been detected, since the impact object passing time has elapsed, the control unit 12 determines that the impact object included in the image is a misrecognition and executes the process of step ST6.

[0034] On the other hand, when the impact object passing time has not elapsed (step ST5: NO), the control unit 12 repeatedly executes the process from step ST4.

[0035] Thus, in the control method according to Embodiment 1, after controlling the event recording process so as to be in a non-recording period in step ST3, until controlling to execute the event recording process in step ST6, the recording process of the event file is not executed. And during this period, the vehicle is passing through an impact object. Therefore, the control method according to Embodiment 1 can more reliably prevent the recording process of an event file not related to an accident from being executed.

[0036] In the control method shown in FIG. 3, in step ST4, the control unit 12 determines whether the vehicle detects an impact. However, in the control method according to Embodiment 1, step ST4 may be omitted. That is, the control unit 12 may control the event recording process of the drive recorder so as to execute the process of step ST6 according to whether the step difference passing time has elapsed (step ST5).

[0037] Here, with reference to FIG. 4, the effect of executing step ST4 will be described. FIG. 4 is a diagram showing the state when the vehicle passes through a step. In FIG. 4, for the step IP1 and the points S1 to S3, the configuration is the same as that shown in FIG. 2. The lower part of FIG. 4 shows the state in which the vehicle C1 has passed through the step IP1 after changing to twice the vehicle speed compared to the upper part of FIG. 4.

[0038] In the upper part of FIG. 4, the vehicle C1 has passed through the step IP1 4 seconds after leaving the point S1. And the control unit 12 controls the event recording process of the drive recorder so that the event process of the drive recorder is executed again 4 seconds after leaving the point S1.

[0039] In the lower part of FIG. 4, since the vehicle speed of the vehicle C1 is twice that of the upper part of FIG. 4, the vehicle C1 has passed through the step IP1 2 seconds after leaving the point S1. And in the lower part of FIG. 4, 2 seconds after leaving the point S3 (4 seconds after leaving the point S1), the vehicle C1 is located at a place away from the step IP1.

[0040] In the case of the lower part of FIG. 4, similar to the upper part of FIG. 4, when controlling the event recording process of the drive recorder so that the event process of the drive recorder is executed again 4 seconds after point S1 (2 seconds after point S3), the event data for 2 seconds from point S3 is not recorded. That is, in the lower part of FIG. 4, 2 seconds after passing point S1, since the vehicle is passing the step IP1, it is preferable that the control unit 12 controls the event recording process of the drive recorder so that the event process of the drive recorder is executed again.

[0041] Vehicle C1 is given an impact by passing the step IP1 2 seconds after point S1. From this, the control unit 12 can control the event recording process of the drive recorder so that the event process of the drive recorder is executed again at a more appropriate timing by determining whether the vehicle has detected an impact.

[0042] (Embodiment 2) <Height of the impact object> The control system according to Embodiment 2 will be described. FIG. 5 is a block diagram illustrating the control system according to Embodiment 2. As shown in FIG. 5, the control system 20 includes an analysis unit 14, a calculation unit 11, and a control unit 12. The control system 20 is configured to be able to communicate with the recording device 13 in the same manner as the control system 10 according to Embodiment 1. Since the calculation unit 11 and the recording device 13 are the same as those in Embodiment 1, the description thereof will be omitted. Here, the analysis unit 14 and the control unit 12 will be described. Also in Embodiment 2, similar to Embodiment 1, the description will be made assuming that the recording device 13 is a drive recorder.

[0043] The analysis unit 14 analyzes information regarding the height of the impact object from the image. Then, the control unit 12 controls the event recording process of the drive recorder so that there is a non-recording period when the height of the impact object by the analysis unit 14 is less than a predetermined value and greater than or equal to a predetermined value. Here, the height of the impact object being less than the predetermined value may use, for example, the minimum ground clearance of the vehicle (also referred to as the road clearance).

[0044] <Control of Event Recording Process Based on Height of Impact Object> With reference to FIG. 6, an example of the control unit 12 controlling the event recording process based on the height information of the impact object will be described. FIG. 6 is a schematic diagram showing the presence or absence of impact detection according to the vehicle speed and the height of the impact object. Generally, the higher the vehicle speed, the more likely an impact will be applied to the vehicle even if the height of the impact object is low. In FIG. 6, when the point plotting the vehicle speed and the height of the impact object is included in region R1, the drive recorder does not detect an impact even if the vehicle is impacted by the impact object. On the other hand, when the point plotting the vehicle speed and the impact object is included in region R2, the drive recorder detects an impact when the vehicle is impacted by the impact object.

[0045] That is, when the point plotting the vehicle speed and the impact object is included in region R1, since the drive recorder does not detect an impact, the control unit 12 does not control the event recording process of the drive recorder so as to be a non-recording period. On the other hand, when the point plotting the vehicle speed and the impact object is included in region R2, since the drive recorder detects an impact, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period.

[0046] The control system 20 acquires information regarding the vehicle speed from the vehicle. For example, when the vehicle speed is 60 km / h, the control unit 12 specifies that the height of the impact object for controlling the event recording process from FIG. 6 is 10 mm or more. Then, when the height of the impact object is 10 mm or more from the information regarding the height of the impact object of the analysis unit 14, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period because it is included in region R2.

[0047] Here, the control unit 12 may control the event recording process based on the information on the height of the impact object stored in the storage unit that stores whether the event recording process is to be executed. FIG. 7 is a block diagram illustrating the control system according to Embodiment 2. As shown in FIG. 7, the control system 21 includes a storage unit 15, an analysis unit 14, a calculation unit 11, and a control unit 12. The configurations other than the storage unit 15 and the control unit 12 shown in FIG. 7 are the same as those in FIG. 6, and thus the description thereof is omitted. Here, the storage unit 15 and the control unit 12 will be described in detail.

[0048] The storage unit 15 stores whether the event recording process is to be executed according to the height of the impact object. A more specific description will be given with reference to Table 1. Table 1 is an example of a list of information on the height of the impact object stored in the storage unit 15. It is for explaining whether to perform the event recording process according to the height and shape of the impact object, and the height and shape are not limited.

[0049]

Table 1

[0050] As shown in Table 1, the storage unit 15 stores whether the event recording process is to be executed according to the height of the impact object. Also, in the example shown in Table 1, the storage unit 15 stores the shape of the impact object in association with the height of the impact object. For example, in Table 1, when the height of the impact object is 5 mm and the shape of the impact object is flat, it indicates that the event recording process has been executed. Also, in Table 1, when the height of the impact object is 3 mm and the shape of the impact object is flat, it indicates that the event recording process has not been executed. Note that the minimum ground clearance of the vehicle, which is less than a predetermined value based on the height of the impact object, is also stored in the storage unit 15, but the minimum ground clearance of the vehicle may be stored in the analysis unit 14.

[0051] The control unit 12 controls the event recording process of the drive recorder as follows based on the height of the impact object by the analysis unit 14 and the information in Table 1 pre-stored in the storage unit 15. When the height of the impact object by the analysis unit 14 is less than a predetermined height at which the event recording process in the storage unit 15 is being executed and is greater than or equal to the height of the impact object, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period. For example, when the height of the impact object by the analysis unit 14 is 4 mm, since the event detection process of the impact object is being executed from Table 1, the control unit 12 controls the event recording process so as to be a non-recording period. Thereby, the control system 21 can prevent the recording process of an event file not related to an accident from being executed.

[0052] Also, when the storage unit 15 stores a plurality of heights of the impact object by the analysis unit 14, the control unit 12 may identify a shape identical or similar to the shape of the impact object included in the image from the storage unit and control the event recording process of the drive recorder. For example, when the height of the impact object by the analysis unit 14 is 3 mm, in the example shown in Table 1, two event recording processes with a height of 3 mm are stored in the storage unit. In this case, the control unit 12 acquires information regarding the shape of the impact object included in the image from the analysis unit 14. Then, the control unit 12 identifies whether the event recording process is being executed for an impact object having a shape identical or similar to the shape acquired from the analysis unit 14. For example, when the shape acquired from the analysis unit 14 is a concavo-convex shape, from Table 1, the event detection process is being executed for an impact object with a height of 3 mm and a concavo-convex shape. Therefore, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period.

[0053] Also, when the height of the impact object by the analysis unit 14 is not stored in the storage unit 15, the control unit 12 may control the event recording process of the drive recorder based on whether the event recording process corresponding to the height of the value closest to the height of the impact object by the analysis unit 14 is being executed.

[0054] Note that when the height of the impact object by the analysis unit 14 is equal to or lower than the height of the impact object for which the event recording process in the storage unit is not being executed, the control unit 12 does not control the event recording process so as to enter a non-recording period. This is because the event recording process is not executed even if the control unit 12 does not control the event recording process so as to enter a non-recording period.

[0055] As described above, the control systems 20 and 21 according to the second embodiment control the event recording process of the drive recorder so as to enter a non-recording period when the height of the impact object by the analysis unit 14 is less than a predetermined value and greater than or equal to a predetermined value.

[0056] In addition, the control systems 20 and 21 provide a predetermined standard as shown in FIG. 6 or Table 1, and control the event recording process based on the height information of the impact object by the analysis unit 14. In the prior art, even if it is registered as an impact detection malfunction position, when the road surface shape changes due to construction or a disaster, there is a possibility that impact detection is performed and the event recording process is executed. However, once the control systems 20 and 21 provide a predetermined standard, they can control the event recording process. Therefore, the control systems 20 and 21 can more reliably prevent the recording process of event files that have nothing to do with accidents from being executed. In addition, the control systems 20 and 21 may acquire the magnitude of the impact when passing through the impact object, store information associating the height of the impact object with the magnitude of the impact, and set a non-recording period for the detected height of the impact object when the impact value is equal to or less than a predetermined impact value.

[0057] Note that the control system 21 may be configured to store the position information of the impact object, the shape and height of the impact object in the storage unit 15. By adopting such a configuration, the control system 21 can improve the accuracy of a predetermined standard. Further, the control system 21 may photograph the area before the impact object passes by using the front camera of the drive recorder, and photograph the area after the impact object passes by using the rear camera of the drive recorder. As a result, the control system 21 can more accurately recognize the height, shape, etc. of the impact object and store them in the storage unit 15, so that the accuracy of a predetermined standard can be further improved. Note that all or part of the control system 21 may be configured by a server (not shown).

[0058] <Control method> Subsequently, the control method according to Embodiment 2 will be described. FIG. 8 is a flowchart illustrating the driving support method according to Embodiment 2. In the flowchart shown in FIG. 8, compared with the flowchart shown in FIG. 3, steps ST11 and ST12 are executed differently. Since the other processes are the same as those in FIG. 3, the description thereof will be omitted.

[0059] Subsequent to step ST1, the control system 20(21) analyzes information regarding the height of the impact object from the image (step ST11). Here, the height of an impact object less than a predetermined height, for example, less than the lowest ground clearance of the vehicle, is the analysis target. Then, the control system 20(21) determines whether or not the analyzed height of the impact object is equal to or greater than a predetermined value (step ST12).

[0060] When it is determined that the height of the impact object analyzed by the control system 20(21) is equal to or greater than the predetermined value (step ST12 YES), the control system 20(21) executes the processes after step ST2. That is, the control system 20(21) controls the event recording process of the drive recorder so as to be in a non-recording period.

[0061] On the other hand, when the control system 20(21) does not determine that the height of the impact object analyzed is equal to or greater than a predetermined value (step ST12 NO), the control system 20(21) repeats the process from step ST1. That is, the control system 20(21) does not control the event recording process of the drive recorder so as to be a non-recording period.

[0062] (Embodiment 3) <Vehicle information> The control system according to Embodiment 3 will be described. FIG. 9 is a block diagram illustrating the control system according to Embodiment 3. As shown in FIG. 9, the control system 30 includes a vehicle information acquisition unit 16, a calculation unit 11, and a control unit 12. The control system 30 is configured to be able to communicate with the recording device 13 in the same manner as in Embodiment 1 and Embodiment 2. Since the calculation unit 11 and the recording device 13 are the same as those in Embodiment 1 and Embodiment 2, the description thereof is omitted. Here, the vehicle information acquisition unit 16 and the control unit 12 will be described. Also in Embodiment 3, as in Embodiment 1 and Embodiment 2, the recording device 13 is described as a drive recorder. Also, all or part of the control system 30 may be configured by a server (not shown). Thereby, information regarding the height of the impact object and the non-recording period stored in the storage unit 15 can be shared with other vehicles.

[0063] The vehicle information acquisition unit 16 acquires vehicle information regarding the vehicle. The vehicle information includes, for example, information regarding the vehicle type and the vehicle weight. The vehicle information is, for example, "a normal passenger car of 1500 kg" or "a dump truck of 13 tons". The control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period based on the vehicle information.

[0064] <Control of event recording process based on vehicle information> While referring to FIG. 10, an example of the control unit 12 controlling the event recording process based on vehicle information will be described. FIG. 10 is a schematic diagram showing the presence or absence of impact detection according to vehicle speed and vehicle weight. Generally, the faster the vehicle speed, the more likely an impact is applied to the vehicle even if the vehicle weight is light. In FIG. 10, when the point plotting the vehicle speed and vehicle weight is included in region R3, the drive recorder does not detect an impact even if the vehicle receives an impact from an impact object. On the other hand, when the point plotting the vehicle speed and vehicle weight is included in region R4, the drive recorder detects an impact when the vehicle receives an impact from an impact object.

[0065] That is, when the point plotting the vehicle speed and vehicle weight is included in region R3, since the drive recorder does not detect an impact, the control unit 12 does not control the event recording process of the drive recorder so as to be a non-recording period because it does not execute the event recording process either. On the other hand, when the point plotting the vehicle speed and vehicle weight is included in region R4, since the drive recorder detects an impact, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period.

[0066] The control system 30 acquires information regarding the vehicle speed from the vehicle. For example, in the case of a speed of 60 km / h, the control unit 12 specifies that the vehicle weight for controlling the event recording process is 1200 kg or more from FIG. 10. And when the information regarding the vehicle weight of the vehicle information acquisition unit 16 is 1500 kg, the control unit 12 controls the event recording process of the drive recorder so as to be a non-recording period because it is included in region R4.

[0067] Here, the control unit 12 may control the event recording process based on the information regarding the vehicle stored in the storage unit that stores whether the event recording process is executed or not. FIG. 11 is a block diagram illustrating the control system according to Embodiment 3. As shown in FIG. 11, the control system 31 includes a storage unit 17, a vehicle information acquisition unit 16, a calculation unit 11, and a control unit 12. Since the configurations other than the storage unit 17 and the control unit 12 shown in FIG. 7 are the same as those in FIG. 9, the description thereof is omitted. Here, the storage unit 17 and the control unit 12 will be described in detail.

[0068] The memory unit 17 stores whether to execute event recording processing corresponding to information about the vehicle. This will be described in more detail with reference to Table 2. Table 2 is an example of a list of information about the vehicle stored in the memory unit 17.

[0069]

Table 2

[0070] As shown in Table 2, the memory unit 17 stores whether to execute event recording processing according to the vehicle weight. Also, in the example shown in Table 2, the memory unit 17 stores the vehicle shape and vehicle speed associated with the vehicle weight. Further, the memory unit 17 may store including the minimum ground clearance. For example, in Table 2, when the vehicle weight is 13 tons, the vehicle shape is a dump truck, and the vehicle speed is 50 km / h, it indicates that the event recording processing has been executed.

[0071] The control unit 12 controls the event recording processing of the drive recorder based on the information about the vehicle weight acquired by the vehicle information acquisition unit 16 and the information about the vehicle speed acquired by the control system 31. For example, assume that the control unit 12 acquires information about the vehicle weight such as "13 tons" and information about the vehicle speed such as "50 km / h". In this case, since the event recording processing is being executed according to Table 2, the control unit 12 controls the event recording processing of the drive recorder so that it becomes a non-recording period. Thereby, the control system 31 can suppress the execution of the recording processing of the event file that has nothing to do with the accident.

[0072] Also, when the information about the vehicle weight acquired by the vehicle information acquisition unit 16 is not stored in the memory unit 17, the control unit 12 may control the event recording processing of the drive recorder based on whether to execute the event recording processing corresponding to the vehicle weight closest to the acquired vehicle weight.

[0073] Note that the control unit 12 does not control the event recording process so that it becomes a non-recording period when the information on the vehicle weight acquired by the vehicle information acquisition unit 16 and the information on the vehicle speed acquired by the control system 31 are the vehicle weight and vehicle speed for which the event recording process in the storage unit 17 is not being executed. This is because the event recording process is not executed even if the control unit 12 does not control the event recording process so that it becomes a non-recording period.

[0074] In this way, the control systems 30 and 31 according to the third embodiment control the event recording process of the drive recorder so that it becomes a non-recording period based on the vehicle information. Even for the same impact object, if the vehicle class, load, and speed are different, the impact applied to the vehicle is different. Therefore, the control systems 30 and 31 can more reliably prevent the recording process of the event file that has nothing to do with the accident from being executed.

[0075] Of course, the control systems 30 and 31 may further include the analysis unit 14 described above, and control the event recording process of the drive recorder so that it becomes a non-recording period based on the information on the height of the impact object and the vehicle information.

[0076] <Control Method> Subsequently, the control method according to the third embodiment will be described. FIG. 12 is a flowchart illustrating the driving support method according to the third embodiment. In the flowchart shown in FIG. 12, compared with the flowchart shown in FIG. 3, the difference is that steps ST111 and ST112 are executed. Since the other processes are the same as those in FIG. 3, the description thereof will be omitted.

[0077] Following step ST1, the control system 30 (31) acquires information on the vehicle weight (step ST111). Then, the control system 30 (31) determines whether the vehicle weight is equal to or greater than a predetermined value (step ST112).

[0078] When the control system 30(31) determines that the vehicle weight acquired is greater than or equal to a predetermined value (step ST112 YES), the control system 30(31) executes the processes after step ST2. That is, the control system 30(31) controls the event recording process of the drive recorder so as to be in a non-recording period.

[0079] On the other hand, when the control system 30(31) does not determine that the vehicle weight acquired is greater than or equal to a predetermined value (step ST112 NO), the control system 30(31) repeatedly executes the processes from step ST1. That is, the control system 30(31) does not control the event recording process of the drive recorder so as to be in a non-recording period.

[0080] Part or all of the processes in the control system and control method according to the above-described embodiments 1 to 3 can be realized as a computer program. Such a program can be stored using various types of non-transitory computer-readable media and supplied to a computer. Non-transitory computer-readable media include various types of tangible recording media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, semiconductor memories (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). Further, the program may be supplied to the computer by various types of transitory computer-readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer-readable media can supply the program to the computer via a wired communication path such as electric wires and optical fibers, or a wireless communication path.

[0081] As described above, the present disclosure has been described in accordance with the above embodiments. However, the present disclosure is not limited only to the configurations of the above embodiments, and of course includes various modifications, corrections, and combinations that can be made by those skilled in the art within the scope of the claims of the present patent application.

Explanation of Reference Numerals

[0082] 10, 20, 21, 30, 31 Control System 11 Calculation Unit 12 Control Unit 13 Recording Device 14 Analysis Unit 15, 17 Storage Unit 16 Vehicle Information Acquisition Unit C1 Vehicle IP1 Step R1, R2, R3, R4 Regions S1, S2, S3 Locations

Claims

1. A control system for controlling a recording device that executes event recording processing associated with impact detection of a vehicle, comprising: a calculation unit that calculates an impact object passing time indicating the time from the current time until the vehicle passes the impact object based on an image including the impact object that imparts an impact to the vehicle; a control unit that controls the event recording processing so that, before the vehicle passes the impact object, a non-recording period during which the recording device does not execute the event recording processing is set based on the impact object passing time; A control system comprising the above.

2. further comprising an analysis unit that analyzes information regarding the height of the impact object from the image, wherein the control unit controls the event recording processing so that the recording device enters the non-recording period when the height of the impact object by the analysis unit is less than a predetermined height of the vehicle and equal to or more than a predetermined value. The control system according to claim 1.

3. further comprising a storage unit that stores whether or not event recording processing corresponding to the height of the impact object is to be executed, wherein the control unit controls the event recording processing so that the recording device enters the non-recording period when the height of the impact object by the analysis unit is equal to or more than the height of the impact object for which event recording processing is executed in the storage unit. The control system according to claim 2.

4. further comprising a vehicle information acquisition unit that acquires vehicle information regarding the vehicle, wherein the storage unit stores whether or not event recording processing corresponding to the vehicle information is to be executed, wherein the control unit controls the event recording processing so that the recording device enters the non-recording period when the vehicle information acquired by the vehicle information acquisition unit is the vehicle information for which event recording processing is executed in the storage unit. The control system according to claim 3.

5. A control method for controlling a recording device that executes event recording processing associated with impact detection of a vehicle, comprising: calculating an impact object passing time indicating the time until the vehicle passes the impact object based on an image including the impact object that imparts an impact to the vehicle; controlling the event recording processing so that, before the vehicle passes the impact object, a non-recording period during which the recording device does not execute the event recording processing is set based on the impact object passing time; The computer executes the processing. A control method.

Images