System and program, or the like

Abstract

To provide a system with high convenience and a program, or the like.SOLUTION: A drive recorder 1 comprises: a time laps mode that performs intermittent imaging and storage as a recording function for storing a video image imaged in a vehicle 100 in a recording processing program of a controller 30; and a dynamic body detection mode that performs imaging and storage in accordance with the detection of a mobile body.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to, for example, a system and a program. [Background technology]

[0002] For example, in-vehicle recording devices, so-called drive recorders, which are mounted on vehicles to capture images of the area around the vehicle and record the surrounding images and vehicle speed when the vehicle is subjected to an impact due to an event such as sudden braking, sudden steering, or a collision, are now widely used (see, for example, Patent Document 1).

[0003] The drive recorder (vehicle storage device) described in Patent Document 1 constantly records video and detects events while the vehicle is not parked but operating. Furthermore, when the drive recorder is powered by the vehicle's battery while the vehicle is parked, it constantly records video and detects events, and when it operates on a battery dedicated to the drive recorder, it detects events and captures video when an event is detected (see paragraph 0043 of Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6696558 Summary of the Invention [Problem to be solved by the invention]

[0005] There is a demand for highly convenient drive recorders and other systems. For example, in recent years, there has been a demand for drive recorders that can monitor for longer periods of time, not just while the vehicle is moving, such as continuing to record even when the vehicle is parked, as in Patent Document 1. For example, it would be desirable to be able to capture and store video more efficiently and to improve usability.

[0006] In view of the above-mentioned problems, one object of the present invention is to provide a highly convenient system, program, etc.

[0007] The object of the present invention is not limited to this, and the applicant intends to obtain rights for configurations that aim to achieve the effects achieved by parts of the configuration disclosed in the specification and drawings, etc., through divisional applications, amendments, etc. For example, this specification discloses problems in which the phrases "can" and "is possible" are read as "the problem is." Each problem is described as an independent problem, and the applicant intends to obtain rights for configurations that solve each problem separately through divisional applications, amendments, etc. Even if the problem is implicitly understood from the description in the specification, the applicant intends to claim part of the configuration described in this specification through amendments or divisional applications. Furthermore, the applicant has disclosed configurations that solve problems that combine these independent problems, and the applicant intends to obtain rights for them. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems, the present invention provides (1) a system having a recording function for storing images captured in a vehicle, characterized in that the recording function has a first recording mode for capturing images intermittently and storing the images, and a second recording mode for capturing images and storing the images in response to the detection of a moving object.

[0009] The first recording mode, which captures and stores images intermittently, captures images less frequently than the normal recording mode, reducing the amount of video data stored. The second recording mode, which captures and stores images in response to the detection of a moving object, can also avoid capturing and storing images if no moving object is detected. These two recording modes also reduce the number of captures compared to the normal recording mode, reducing the amount of video data stored. Providing the first and second recording modes as recording functions for storing images captured in a vehicle allows the user to select the recording mode appropriate for the situation, enabling efficient image capture and storage, and further enhancing user convenience.

[0010] The present invention is also characterized in that (2) a system having a recording function for storing images captured in a vehicle, the recording function having a first recording mode for capturing and storing images at a first frame rate, and a second recording mode for capturing and storing images at a second frame rate higher than the first frame rate and performing moving object detection.

[0011] The first recording mode, which captures and stores images at a first frame rate lower than the second frame rate, reduces the number of captures and the amount of video data to be stored. The second recording mode, which captures and stores images at a second frame rate higher than the first frame rate in response to the detection of a moving object, can also reduce the number of captures and the amount of video data to be stored because it is possible not to capture and store images if no moving object is detected. Providing these first and second recording modes as recording functions for storing captured images in a vehicle allows the user to select the recording mode appropriate for the situation, enabling efficient image capture and storage, and further enhancing user convenience.

[0012] (3) The recording function may be configured to allow selection of either the first recording mode or the second recording mode.

[0013] By making it possible to selectively (also called exclusively) select either the first or second recording mode in this way, it is possible to prevent the first and second recording modes from being executed in parallel, which reduces the processing load and reduces costs by eliminating the need for a high-performance encoder, etc.

[0014] (4) The recording function may be a parking memory function that records while the vehicle is parked. This makes it possible to provide a system with a parking memory function that is more convenient for users. For example, when recording the state of a vehicle while parked for a long period of time, the parking memory function may capture and record images intermittently to detect the presence of a third party attempting to tamper with or steal the vehicle or its contents, or other moving objects associated with an abnormality. The contents of each of the first and second recording modes are determined so that recording can be performed in an appropriate manner, taking into account the circumstances of the vehicle being parked.

[0015] (5) In the first recording mode, the captured video may be stored as a time-compressed moving image. Video captured intermittently or at the first frame rate results in long periods of still images. Therefore, by compressing the video into a time-compressed moving image, the amount of video data stored can be reduced. Furthermore, the video data can be viewed in a shorter time.

[0016] (6) The recording function may be configured to automatically switch to either the first recording mode or the second recording mode when a predetermined condition is met. This reduces the need for a user to switch between the first recording mode and the second recording mode. For example, the parking memory function is highly convenient because it eliminates the need for a user to manually set the recording mode or check the currently set mode, even when the user wants to get out of the vehicle immediately after parking.

[0017] (7) The recording function may automatically switch to either a preselected first recording mode or a preselected second recording mode when the vehicle is at a pre-registered location or time. This allows the recording function to switch to the preselected first recording mode or the preselected second recording mode depending on the situation at a pre-registered location or time, thereby more appropriately reducing the user's effort. For example, the parking memory function may select the first recording mode when the parking location is an easily visible location such as a home or workplace, a location with a lot of pedestrians and vehicles, or a time zone with a lot of pedestrians and vehicles. Alternatively, the parking memory function may select the second recording mode when the parking location is an unvisible location such as a travel destination or an unfamiliar location, a location with little pedestrians and vehicles, or a time zone with little pedestrians and vehicles. This allows the parking information to be memorized in an appropriate mode depending on the location and time, without the user having to explicitly specify it.

[0018] (8) The recording function may automatically switch to the first recording mode when a predetermined condition is met while the second recording mode is selected. By switching to the first recording mode when a predetermined condition is met, even if the second recording mode is selected, the motion detection process can be reduced, further reducing the processing load, consumption of storage resources, and power consumption. For example, in the parking memory function, recording may be triggered by the detection of a motion inside or outside the vehicle, and recording may be stopped and the system may switch to time-lapse mode when a predetermined condition is met, such as when a predetermined time has elapsed since the start of recording or when no motion is detected. This increases the recording time, reducing consumption of storage resources and power consumption.

[0019] (9) The recording function may automatically switch to the first recording mode when a state in which no moving object is detected in the second recording mode continues for a predetermined time or more. This reduces the load on the moving object detection process, the consumption of storage resources, and the consumption of power. For example, in the parking storage function, recording may be triggered by the detection of a moving object inside or outside the vehicle, and when a predetermined time has passed since the start of recording or when no moving object is detected, the recording may be terminated and the mode may be switched to time lapse mode.

[0020] (10) The recording function preferably stores first video data captured in response to a specific event in a first storage area, second video data different from the first video data in a second storage area, and video data captured in the first and second recording modes in the second storage area. This allows for a clear distinction between relatively important event video data and other video data, improving the efficiency of video data review. For example, while vandalism, intrusion by a third party into the vehicle, or theft may occur while the vehicle is parked, such incidents do not occur frequently. Therefore, the frequency with which video recorded using the parking memory function is actually played back and viewed is low. In contrast, the first video data is video recorded when a specific event occurs, such as when an accident is imminent or has occurred, so it is desirable to be able to quickly find and view the desired video when needed. The video data in the second storage area is second video data other than the first video data, such as video recorded continuously, and therefore is not frequently viewed. Therefore, if the video data recorded using the parking storage function is stored in the second storage area, the video recorded using the parking storage function can be managed without interfering with the viewing of the event recording data.

[0021] (11) It is preferable that the vehicle has imaging units installed at multiple locations to capture images for the recording function. This allows events relating to the vehicle to be captured from various positions or angles, and each imaging unit can be switched between the first and second recording modes, enabling more reliable and efficient monitoring and capturing images in an appropriate recording mode for each imaging unit. The recording modes of each imaging unit may be the same, or some imaging units may have recording modes different from the other recording modes.

[0022] (12) It is preferable that one of the imaging units is for the rear of the vehicle and is capable of capturing images with higher sensitivity than the other imaging units. In this way, monitoring of the rear of the vehicle can also be performed with high accuracy. Furthermore, since the rear window of the vehicle is often smoked and there is less light emitted from the vehicle's lights than in the front of the vehicle, by making the imaging unit for the rear of the vehicle capable of capturing images with higher sensitivity than the other imaging units, it is possible to perform appropriate monitoring while suppressing cost increases compared to making all imaging units highly sensitive.

[0023] (13) One of the imaging units is for the front of the vehicle, and the other is for the rear of the vehicle. The recording function preferably stores video data captured by the imaging unit for the front of the vehicle using one of recording codecs including at least a first codec and a second codec with higher compression than the first codec, and stores video data captured by the imaging unit for the rear of the vehicle using a recording codec with lower compression than the second codec.

[0024] In this way, multiple codecs including a highly compressed recording codec can be selected for the imaging unit for the front of the vehicle, which is more likely to be monitored, and imaging for the imaging unit for the rear of the vehicle, which is less likely to be monitored than the front of the vehicle, is performed using a recording codec lower than the second codec. By dividing the selectable recording codecs between the imaging units for the front and rear of the vehicle in this way, it is possible to capture and store video data more efficiently according to the imaging location.

[0025] (14) Preferably, the first codec is H.264 and the second codec is H.265. By using H.264 as the first codec, it is possible to capture and store general-purpose video data that can be played back on many commercially available PCs, for example, and by using H.265 as the second codec, it is possible to store high-quality video data with a small amount of data.

[0026] (15) The recording function preferably stores the video so that the recording time does not change between the video data in the first codec and the video data in the second codec. The recording time is the recording time of the video data. This provides high convenience because the recording time does not change even if the compression rate of the stored video data is different. For example, it is less likely that a situation will occur where the recording time is shorter than the user expected as a result of setting a high image quality, and the user is unable to capture the video they wanted.

[0027] (16) It is preferable that the recording function sets the first codec as the standard recording codec for the video data captured by the imaging unit in front of the vehicle. While a recording codec with a high compression rate may limit the number of devices that can play the video, by setting a recording codec with a relatively low compression rate as the standard setting, it is possible to capture and store highly versatile video data that can be played on many playback devices unless the user changes the setting, thereby preventing situations where the video data cannot be played.

[0028] (17) One of the imaging units is for the front of the vehicle, and the other is for the rear of the vehicle, and the recording function preferably stores video data captured by the imaging unit for the front of the vehicle at a resolution including at least a first resolution and a second resolution higher than the first resolution, and stores video data captured by the imaging unit for the rear of the vehicle at a resolution lower than the second resolution.

[0029] In this way, for the imaging unit for the front of the vehicle, which has a high need for monitoring, multiple resolutions including a first resolution and a second resolution higher than the first resolution can be selected, and for the imaging unit for the rear of the vehicle, which has a lower need for monitoring than the front of the vehicle, imaging is performed at a resolution lower than the second resolution. By dividing the selectable resolutions between the imaging units for the front and rear of the vehicle in this way, it is possible to capture and store video data more efficiently according to the imaging location.

[0030] (18) The video device may have a playback function for playing back the video data stored by the recording function, and the playback function may be capable of simultaneously playing back the video data captured by the imaging unit in front of the vehicle and the video data captured by the imaging unit in rear of the vehicle. By simultaneously playing back the video data from the imaging units in front and behind the vehicle, the situations in front of and behind the vehicle at the same time can be displayed simultaneously, thereby improving the efficiency of checking the video data.

[0031] (19) It is preferable to have a function for detecting the write capacity for writing the captured video to a storage medium and a function for issuing a warning when the write capacity is equal to or lower than a predetermined write capacity. In this way, a warning can be issued when the write capacity is equal to or lower than the predetermined write capacity. When a user receives the warning, the user knows that he or she needs to prepare a storage medium with sufficient write capacity and can take appropriate action.

[0032] (20) Preferably, the detection function measures the writing speed of the captured video onto the storage medium as the writing capacity, and the notification function issues a warning if the writing speed is below a predetermined speed. In this way, the writing capacity of the storage medium can be measured simultaneously with writing of the video data, and the user can be made aware that the writing speed of the storage medium is insufficient.

[0033] (21) Preferably, the detection function measures the write capacity of the storage medium by measuring the lifespan during which writing can be performed on the storage medium, and the notification function notifies the user of the lifespan. This allows the user to easily determine the appropriate time to replace the storage medium, and prevents a situation in which video data cannot be stored due to, for example, a failure of the storage medium due to its lifespan.

[0034] (22) The recording function may be capable of writing the captured video to the storage medium even when the notification function issues a warning. In this way, by detecting the write capacity of the storage medium and issuing a warning if the write capacity is below a predetermined level, while allowing storage (writing) to the storage medium to continue, it is possible to prevent a situation in which video data cannot be stored and to ensure a period of time for the user to replace the storage medium while continuing to use the storage medium. Specifically, the user can be made aware that the storage medium's write capacity is insufficient, and recording using the storage medium can continue, thereby preventing situations in which recording is not possible due to insufficient write capacity. When a user receives a warning, they know that they need to prepare a storage medium with sufficient write capacity and can take appropriate action.

[0035] (23) The warning may include at least one of a warning that the write capacity is below a predetermined write capacity and a warning that there is a risk of failure in recording the captured video onto the storage medium. In this way, a user who receives the warning will know that he or she must prepare a storage medium with sufficient write capacity and can take appropriate measures.

[0036] (24) The notification function may issue a warning to the user urging the user to replace the storage medium according to the writing capacity, and the recording function may be capable of recording the captured video onto the storage medium even when the warning to the user urging the user to replace the storage medium is issued. In this way, the user can be urged to replace the storage medium before video recording onto the storage medium becomes impossible due to a malfunction, end of life, etc., and the user can take appropriate measures, such as replacing the storage medium.

[0037] (25) Preferably, the notification function can provide three or more different notifications regarding the status of the storage medium depending on the write capacity. This allows notification of various information regarding the status of the storage medium as determined from the write capacity. For example, in addition to notifying that the storage medium is normal or that the storage medium is abnormal, such as broken or deteriorated, it can also notify the user that the storage medium is capable of recording video, but urges the user to replace the storage medium.

[0038] (26) It is preferable that the notification function performs the notification at least at startup or when recording by the recording function starts. In this way, it is expected that the user will be more likely to notice the warning notification.

[0039] (27) The detection function may detect the write capability based on information specifying the write capability that is pre-stored in the storage medium. In this way, the write capability can be detected simply by referring to the information pre-stored in the storage medium.

[0040] (28) The detection function may detect the amount of busy signals that occur when writing to the storage medium as the write capability, thereby making it possible to detect the actual write capability without referring to information previously stored in the storage medium.

[0041] (29) The detection function may detect the write capacity based on the usage status of a buffer used for writing to the storage medium. In this way, the actual write capacity can be detected without referring to information previously stored in the storage medium.

[0042] (30) The detection function may detect the write capability by performing a write test on the storage medium. This reduces the processing load compared to when the write test is performed during recording by the recording function.

[0043] (31) The detection function detects a write error on the storage medium as the write capability, and the recording function issues a first warning when the write error is detected and the write capability is equal to or lower than a predetermined value, and issues a second warning when the write error is detected a predetermined number of times, indicating that the write error has occurred. In this way, it is possible to issue a warning with appropriate content according to the number of times a write error on the storage medium is detected.

[0044] (32) The detection function may detect a write error to the storage medium as the write capability, and the recording function may stop recording when the write error is detected, unmount and mount the storage medium, and resume recording. In this way, even if a write error to the storage medium is detected, unmounting and mounting the storage medium may make it possible to write to the storage medium, so that recording can be resumed after mounting.

[0045] (33) The recording function may terminate the recording when the write error is detected a predetermined number of times. In this way, recording can be continued even with temporary recording stops until the number of write errors detected on the storage medium reaches the predetermined number, and when the number of errors reaches the predetermined number, it is determined that stable video recording is no longer possible and the recording can be terminated.

[0046] (34) The recording function may record the history of the write errors in an error history file. In this way, by referring to the information recorded in the error history file, it is possible to check the tendency of write errors.

[0047] (35) The recording function may be configured to store the captured video in an external information terminal if a problem occurs with writing the captured video to the storage medium. In this way, even if a problem occurs with writing the video to the storage medium, the video is stored in the external information terminal, thereby preventing a situation in which the video is lost.

[0048] (36) It is preferable that the recording function restarts the device having the recording function when the storage medium is switched. In this way, the switching of the storage medium can be performed stably.

[0049] (37) It is preferable that the recording function stores the video data in separate files, and assigns an eight-digit serial file number to the file name of each file. This makes it easier to manage video data files and prevents overflow. This is based on the knowledge that, taking into account the capacity and actual usage of storage media, an eight-digit serial number can prevent overflow.

[0050] (38) The recording function may capture and store images at a frame rate of less than 25 frames per second in at least one of the second and third recording modes. This allows an imaging device such as a drive recorder to capture and store images using a light emitting diode (LED). When capturing images of flashing LED traffic lights, LED signs, and other flashing objects, this prevents the image data volume from increasing while preventing the image from continuing to be captured when the lights are off. Furthermore, even when the image captured by the image capture device is later checked or when the number of frames is thinned before transmission, the image captured when the lights were on is preserved.

[0051] (39) The recording function may capture and store images at a frame rate of 23 frames / second to 24 frames / second in at least one of the second and third recording modes. This reduces the impact of flashing and the increase in the amount of video data when capturing images of LED traffic lights, LED signs, and other flashing objects with an imaging device such as a drive recorder. Furthermore, even when the image captured by the imaging device is later reviewed or the number of frames is thinned before transmission, the image captured at the time the lights were turned on is preserved.

[0052] (40) The imaging element used for the imaging may include, for each pixel, a first light receiving unit and a second light receiving unit having different light receiving periods, and the recording function may store an image captured based on a signal corresponding to the light received by the first light receiving unit and the light received by the second light receiving unit. In this way, when an imaging device such as a drive recorder captures an image of an LED traffic light, an LED sign, or other flashing installation, it is possible to prevent the image from continuing to be captured when the light is turned off.

[0053] (41) The first light receiving unit may be larger than the second light receiving unit, and the second light receiving unit may have a longer light receiving period per unit period than the first light receiving unit. In this way, when an imaging device such as a drive recorder captures an image of an LED traffic light, an LED sign, or other flashing object, it is possible to prevent the image from continuing to be captured when the light is turned off.

[0054] (42) The recording function may record using an internal storage area and a removable storage medium, and may record using the internal storage area at least when an impact of a predetermined magnitude or greater occurs. In this way, even when an impact of a predetermined magnitude or greater occurs, the possibility of recording failure can be reduced compared to when recording using a removable storage medium.

[0055] (43) When the supply of power from the vehicle is stopped, the data recorded by the recording function is backed up to an external storage device based on the power supplied from the battery. In this way, even if the supply of power from the vehicle is stopped, the recorded data can be protected by backing up the data to the external storage device.

[0056] (44) It is preferable to have a drive recorder having the recording function and a supercapacitor externally attached to the drive recorder for supplying power to the drive recorder. In this way, if the supercapacitor deteriorates, the user can easily replace it.

[0057] (45) It is preferable to make a program for causing a computer to realize the functions of any one of the above systems, thereby making it possible to make the computer execute the functions of (1) to (44) above.

[0058] The inventions described in (1) to (45) above can be combined arbitrarily. For example, a configuration may be created by adding at least a portion of the configuration of at least one of the inventions described in (2) and subsequent items to all or a portion of the configuration of the invention described in (1). In particular, an invention may be created by adding at least a portion of the configuration of at least one of the inventions described in (2) and subsequent items to the invention described in (1). Furthermore, any configuration may be extracted from the inventions described in (1) to (45) and combined. The applicant of this application intends to obtain rights to inventions including these configurations. Furthermore, even if a description is made of "in the case of..." or "when...," it is not intended to describe a configuration limited to that case or time. These are merely examples of better configurations, and the applicant intends to obtain rights to configurations other than these cases or times. Furthermore, any descriptions that specify an order are not limited to this order. Configurations in which some parts are deleted or the order is changed are also disclosed, and the applicant intends to obtain rights to such configurations. [Effects of the Invention]

[0059] According to the present invention, convenience can be improved.

[0060] The effects of the present invention are not limited to these, and effects achieved by the configuration disclosed in the present specification and drawings, etc. are also disclosed, and the applicant intends to obtain rights to the configuration achieving such effects through divisional applications, amendments, etc. For example, in this specification, phrases such as "can" and "is possible" are descriptions that clearly indicate the effects achieved, and there are also parts that demonstrate effects even without the phrases "can" and "is possible." Furthermore, there are effects that can be understood from the configuration even without such phrases. [Brief explanation of the drawings]

[0061] [Figure 1] FIG. 1A is a perspective view of a front camera of a drive recorder according to a first embodiment, FIG. 1B is a view showing the front of a vehicle where the front camera is installed, and FIG. 1C is a view showing the rear of the vehicle where a rear camera is installed. [Figure 2] 1 is a block diagram showing a schematic system configuration of a drive recorder according to a first embodiment. [Figure 3] 10 is an example of a setting screen for a recording mode for parking storage. [Figure 4] 10(a) to 10(c) are transition diagrams of manual switching operations to time lapse mode. [Figure 5] 10A to 10C are transition diagrams of manual switching operations to the moving object detection mode. [Figure 6] FIG. 10 is a diagram illustrating the operation in a time lapse mode. [Figure 7] FIG. 10 is a diagram illustrating the operation in a moving object detection mode. [Figure 8] 10 is a flowchart showing a recording mode execution control routine for parking storage. [Figure 9] 10 is a graph showing the results of simulating the lighting state of an LED traffic light at each imaging timing according to the second embodiment. [Figure 10]10 is a graph showing the results of simulating the lighting state of an LED traffic light at each imaging timing according to the second embodiment. [Figure 11] 10 is a graph showing the results of simulating the lighting state of an LED traffic light at each imaging timing according to the second embodiment. [Figure 12] 10 is a graph showing the results of simulating the lighting state of an LED traffic light at each imaging timing according to the second embodiment. [Figure 13] 10 is an example of a data waveform during data writing to an SD card. [Figure 14] 10 is a flowchart showing a write test routine. [Figure 15] This is an example of a method for dealing with an error received from a memory card. [Figure 16] (a)(b) are specific examples of warning signs. [Figure 17] FIG. 10 is a block diagram showing a schematic system configuration of a drive recorder according to a fifth embodiment. [Figure 18] FIG. 13 is a block diagram showing a schematic system configuration of an external battery according to a sixth embodiment. [Figure 19] FIG. 13 is a block diagram showing a schematic system configuration of an external battery according to a seventh embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0062] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment shown below is one embodiment of the present invention, and the content of the present invention should not be interpreted as being limited based on the following description.

[0063] [First embodiment] [System Configuration] An example of the system configuration will be described with reference to Figures 1 and 2. The "system" may be one in which part or all of the system is attached to a mobile body. In addition, when part of the "system" is attached to a mobile body, it is particularly preferable that an imaging unit such as a camera can be attached to the mobile body, and the control unit may be provided in a location separate from the mobile body to which the imaging unit is attached. In addition, the "system" may have the functions of a drive recorder or other imaging device.

[0064] Furthermore, the moving body to which part or all of the system is attached may not only be a vehicle such as an automobile or an electric vehicle, but may also be a system mounted on an object other than a vehicle. Examples of objects other than vehicles include systems mounted on transportation vehicles such as trains, linear motor cars, and monorails, as well as on moving bodies other than vehicles such as ships and airplanes. A system mounted on a vehicle is particularly preferable. The vehicle is not limited to a four-wheeled automobile, but may also be a two-wheeled automobile such as a motorcycle or a large transport vehicle with four or more wheels, particularly a four-wheeled automobile capable of observing the outside of the vehicle from inside the vehicle. Examples of vehicles include not only transportation vehicles (e.g., trucks, forklifts, etc.), commercial vehicles (e.g., taxis, buses, etc.), and general vehicles, but also vehicles with more diverse uses. In this embodiment, a drive recorder, which is an example of an imaging device that can be mounted on a vehicle, will be described.

[0065] Furthermore, when the "imaging unit" is a camera, the cameras may be provided at multiple locations on the vehicle. For example, a camera separate from the camera for the front of the vehicle may be provided for the rear of the vehicle, and images of other moving objects may be captured by the two cameras, the camera for the front of the vehicle (hereinafter referred to as the "front camera") and the camera for the rear of the vehicle (hereinafter referred to as the "rear camera").

[0066] The system according to this embodiment is a drive recorder 1 having a recording function for storing images captured in a vehicle 100, and has two imaging units: a front camera 10 provided in front of the vehicle and a rear camera 20 provided at the rear of the vehicle. The front camera 10 and the rear camera 20 capture images of multiple color components, for example, red (R), green (G), and blue (B), but the types and number of color components can be modified in various ways.

[0067] Fig. 1(a) is a perspective view of a drive recorder equipped with a front camera. As shown in Fig. 1(a), a memory card insertion slot 11 is provided on one side of the housing of the front camera 10. A display 12 and an operation unit 13 (in the example shown in Fig. 1(a) , a plurality of operation buttons 13a to 13d) are provided on the back of the housing. For example, in this embodiment, operation button 13a is a display button for switching images, operation button 13b is a mode button for displaying the playback mode, operation button 13c is a REC / STOP button for starting / stopping recording, operation button 13d is a menu button for displaying a setting menu, and operation button 13e is a memory button for manually starting event recording, which will be described later.

[0068] In addition, a joint rail 14 is provided on the top surface of the housing. Although not shown in Fig. 1(a), a lens for a front camera 10, which is an example of an imaging unit, is provided on the front surface of the housing. A DC jack is provided on the side not shown in Fig. 1(a), and a speaker and an HD output terminal are provided on the bottom surface.

[0069] A front camera 10 (an example of an imaging unit) having a lens captures, for example, an image in front of the vehicle. The DC jack is a jack for connecting to a DC power source via a power cable. The memory card insertion slot 11 is an insertion slot for inserting a memory card. The speaker outputs sound such as voice. The HD output terminal is a terminal for connecting to other information devices via a cable. The joint rail 14 is for attaching a joint member for mounting the front camera 10 on the vehicle. The display 12 displays various images. The operation unit 13 is for inputting various commands to the drive recorder 1 by a user's operation.

[0070] In this embodiment, the user may be, for example, the driver of the vehicle in which the drive recorder 1 is installed, or may be someone other than the driver, for example, a passenger.

[0071] FIG. 1(b) is a perspective view of the front camera of the drive recorder 1 of this embodiment. In the example shown in FIG. 1(b), the front camera 10 of the drive recorder 1 is disposed on the passenger side of the vehicle 100, adjacent to the rearview mirror 102, near the center in the left-right direction, above the windshield 101 of the vehicle 100. The front camera 10 is attached and fixed to the windshield 101 with a mounting member such as double-sided tape. A DC jack of the front camera 10 is connected to a cigarette lighter socket 103 via a power cable 15. When an accessory power supply of the vehicle 100 is turned on, for example, power is supplied to the drive recorder 1 from the cigarette lighter socket 103. On the other hand, when the accessory power supply of the vehicle 100 is turned off, power supply from the cigarette lighter socket 103 to the drive recorder 1 is stopped.

[0072] In this embodiment, although not shown, an external battery is connected to the front camera 10 of the drive recorder 1. The external battery is a power supply source when the accessory power of the vehicle 100 is turned off, and when the accessory power of the vehicle 100 is turned off, power is supplied to the drive recorder 1 from the external battery. The external battery may have an off-timer function that automatically stops power supply when a predetermined off-timer time has elapsed since the start of power supply from the external battery.

[0073] The drive recorder 1 may include a power supply unit that can receive power supply from the cigarette lighter socket 103 to the drive recorder 1 even when the accessory power supply of the vehicle 100 is turned off (engine off state). The power supply unit preferably has a function of monitoring the voltage of the vehicle battery. The voltage monitoring function is a function that stops the power supply to the drive recorder 1 when the voltage of the vehicle battery drops below a predetermined voltage. In this way, it is possible to prevent the vehicle battery from running out.

[0074] Fig. 1(c) is a diagram showing the rear of a vehicle in which a rear camera is installed. In the example shown in Fig. 1(c), the rear camera 20 is attached and fixed to the rear window 104 of the vehicle by a mounting member at an upper portion of the rear window 104 near the center in the left-right direction. The rear camera 20 shown in Fig. 1(c) also has a display function, but this is not essential. It is preferable to provide a display on the dashboard 105 that displays images captured by the rear camera 20 so that the images captured by the rear camera 20 can be viewed from the front.

[0075] The drive recorder 1 may capture images using two separate cameras, a front camera 10 and a rear camera 20, with various functions provided only on the front camera 10 side and the rear camera 20 connected to the front camera 10. The drive recorder 1 may also have a function for performing various settings on the front camera 10 side, and the front camera 10 and the rear camera 20 may operate according to the settings performed on the front camera 10 side. However, this is not essential, and systems capable of performing various functions and settings may be installed at the front and rear of the vehicle.

[0076] As shown in Fig. 1(a), some components of the drive recorder 1 may be provided at a position other than the windshield 101 depending on the purpose of the component. For example, an operation button 13f, which is one of the operation units 13, may be provided on a dashboard 105 as shown in Fig. 1(b). The controller 30 may transmit video data captured by a camera to the outside, for example, and record the video data externally.

[0077] Furthermore, the controller 30 may attach data relating to the vehicle or the user (for example, the vehicle inspection certificate number, the chassis number, the owner's name, etc.) to the video data. The controller 30 may, for example, superimpose subtitles relating to the data relating to the vehicle or the user on the video. The controller 30 may attach information indicating this to the video captured by the front camera 10, and information indicating this to the video captured by the rear camera 20.

[0078] 2 is a block diagram showing a schematic system configuration of the drive recorder of this embodiment. The drive recorder 1 includes the front camera 10 (an example of an imaging unit) and rear camera 20 (an example of an imaging unit), a display 12 (an example of a display unit), and an operation unit 13 including operation buttons 13a to 13f, as well as a controller 30 (an example of a control unit), a speaker 40, a GPS receiver 41, an acceleration sensor 42, a communication circuit 43, and a memory card reader 44. Note that the memory card reader 44 has a read / write function, and strictly speaking should be called a "memory card reader / writer," but in this specification it will simply be called a "memory card reader."

[0079] The display 12 and the speaker 40 function as a notification unit for informing the user of various information. The display 12 outputs various information as image displays under the control of the controller 30. The speaker 40 outputs warnings and various information as sounds under the control of the controller 30. The operation unit 13 functions as an input means by which the user gives various commands to the drive recorder 1 (more specifically, the controller 30).

[0080] In this embodiment, the front camera 10 has a lens directed forward of the vehicle 100 and functions as an imaging unit that captures images within a field of view (within the field of view) in front of the vehicle. Images captured by the front camera 10 are input to the controller 30 as video data. The front camera 10 is capable of capturing images at least in front of the vehicle. For example, the front camera 10 may be provided with a camera that captures images in front of the vehicle and a camera that captures images inside the vehicle, and each may capture images separately. It is even more preferable to use a camera with a 360-degree viewing angle so that it can capture images of both the front and the interior of the vehicle.

[0081] In this embodiment, the rear camera 20 has a lens directed toward the rear of the vehicle 100 and functions as an imaging unit that captures images within a field of view (within the field of view) behind the vehicle. The images captured by the rear camera 20 are input as image data into the controller 30. In this embodiment, the rear camera 20 is capable of capturing images with higher sensitivity than the front camera 10. Specifically, the front camera 10 uses a 4K color CMOS, while the rear camera 20 uses a 2-megapixel color CMOS. The CMOS sensor of the rear camera 20 has a higher sensitivity per pixel than the CMOS sensor of the front camera 10, making it not only resistant to dark environments but also able to maintain the discrimination ability of captured images even when the resolution is relatively lower than that of the front camera 10. Note that the rear camera 20 can capture images at least behind the vehicle, but it would be even better if it could capture images of the sides in addition to the rear. Furthermore, although the present embodiment uses two imaging units, the front camera 10 and the rear camera 20, the number of imaging units may be one or more.

[0082] The GPS receiver 41 detects the position information of the vehicle at the current time based on instructions from the controller 30. The position information detected includes the time, speed, longitude, latitude, altitude, etc. of the vehicle, which are determined based on signals from GPS satellites. The controller 30 performs processing to record the history of this position information.

[0083] The acceleration sensor 42 is a three-axis sensor that detects acceleration and tilt in each of three axes (x-axis, y-axis, and z-axis). Measurement values ​​by the acceleration sensor 42 are constantly input to the controller 30. The controller 30 acquires three-axis acceleration information, for example, every 10 ms.

[0084] The communication circuit 43 functions as a communication unit for wireless communication with external devices, such as servers (e.g., servers of public institutions such as police, servers of companies that operate publicly accessible internet sites, etc.), personal computers, smartphones, tablet terminals, etc. The controller 30 has a function of transmitting video data to external devices via the communication circuit 43 by executing a communication processing program. The communication circuit 43 may be a communication circuit that complies with a short-range wireless communication standard such as the Wi-Fi standard or Bluetooth (registered trademark), or a mobile communication system standard such as LTE (Long Term Evolution) or 4G. The mobile communication system standard can be applied, for example, to communication between an external device and a vehicle moving within a wider area.

[0085] The memory card reader 44 functions as a medium holder that holds a memory card 45. The memory card 45 is, specifically, an SD card, a miniSD card, a microSD card, or the like, and functions as a removable storage medium. A user can insert a memory card into the memory card reader 44 through the memory card insertion slot 11. The memory card reader 44 reads data from the memory card 45 held in the memory card reader 44 or stores data in the memory card 45 under control of the controller 30. The memory card reader 44 may have separate areas for recording data captured by the front camera 10 and data captured by the rear camera 20. While a single memory card may have separate recording areas, it is preferable to allow insertion of two or more memory cards, with data captured by the front camera 10 being recorded on a first memory card and data captured by the rear camera 20 being recorded on a second memory card.

[0086] The controller 30 includes a known arithmetic processing unit such as a CPU 31, memories such as a ROM 32 and a RAM 33, a timer 34, and other peripheral circuits. Various programs are stored in the ROM 32 of the controller 30. The controller 30 executes these programs to realize various functions. The various programs include an operating system (OS), a GPS information processing program, a communication processing program, a recording processing program, and the like. The GPS information processing program, the communication processing program, and the recording processing program do not need to be independent programs, and a program combining multiple of these functions may be used.

[0087] The controller 30 executes the GPS information processing program, thereby storing the GPS information received by the GPS receiver 41 in a memory card 45 held in the memory card reader 44 .

[0088] By executing the recording processing program, the controller 30 can record the images captured by the front camera 10 and the rear camera 20 in association with the time in a recording area of ​​the memory card 45. The controller 30 has a function of accessing the memory card 45 held in the memory card reader 44, and functions as a control unit having a recording function of recording the images captured by the front camera 10 and the rear camera 20 on the memory card held in the memory card reader 44. Specifically, the recording function of the controller 30 temporarily writes the image data captured by the front camera 10 and the rear camera 20 into the RAM 33, and then writes the data from the RAM 33 to the memory card 45 via the memory card reader 44, thereby storing the data.

[0089] The recording function of the controller 30 allows various settings, and the settings of the recording function will be described in detail below.

[0090] The controller 30 of this embodiment has the following recording modes: event recording mode, continuous recording mode, time lapse mode (an example of a first recording mode), and motion detection mode (an example of a second recording mode). Of these, one of the continuous recording mode, time lapse mode, and motion detection mode is selected and executed alternatively (also referred to as exclusively). The time lapse mode and motion detection mode are modes associated with a parking memory function that records while the vehicle is parked. The parking memory function is a function related to recording while the vehicle is parked. The parking memory function is sometimes called a parking monitoring function because it monitors the interior or surroundings of a parked vehicle. The parking memory function is executed by selecting one of the time lapse mode and motion detection mode alternatively. The event recording mode is executed as a multitasking process in parallel with one of the continuous recording mode, time lapse mode, and motion detection mode.

[0091] The event recording mode is a recording mode in which video data captured by the front camera 10 and the rear camera 20 is stored in response to the occurrence of a specific event (e.g., an event). A specific event may be, for example, a user's sudden steering or braking while the vehicle is in motion, or the vehicle's collision with another object. The controller 30 determines such a specific event based on, for example, a measurement value obtained by the acceleration sensor 42. Specifically, the controller 30 determines that a specific event has occurred when the measurement value obtained by the acceleration sensor 42 exceeds a predetermined threshold value or when the measurement value indicates a predetermined change over time. The conditions for determining a specific event are not limited to the above, and may include, for example, vehicle conditions such as vehicle speed and steering state. The controller 30 also determines that a specific event has occurred when a specific operation button on the operation unit 13 (e.g., the operation button 13e in FIG. 1(a)) is pressed. Note that capturing and storing video data in the event recording mode by pressing the operation button 13e is hereinafter also referred to as one-touch recording. Note that the operation that triggers the start of recording does not necessarily have to be a one-touch operation; any specific operation may be used. The recording in this case is called manual recording, and can be substituted for one-touch recording.

[0092] In the event recording mode, when a specific event described above occurs, the controller 30 stores video data captured for a certain period of time before and after the event. For example, the controller 30 stores video data for a total of 40 seconds, consisting of 20 seconds before the event and 20 seconds after the event, as one recording file on the memory card 45.

[0093] The continuous recording mode is a recording mode in which video data is continuously captured and stored by the front camera 10 and the rear camera 20. Specifically, in the continuous recording mode, the controller 30 stores video data captured at least from the start to the stop of the engine of the vehicle 100. The start of the engine is detected, for example, by the accessory power supply of the vehicle 100 being turned on, and the stop of the engine is detected by the accessory power supply being turned off.

[0094] The time lapse mode is a recording mode in which intermittent image capture is performed by the front camera 10 and the rear camera 20 and the captured images are stored. In this embodiment, intermittent image capture refers to capturing images at a frame rate that is lower than the reference frame rate. In this embodiment, when the time lapse mode is selected, the controller 30 sets the frame rate of the images captured by the front camera 10 and the rear camera 20 to a frame rate (an example of a first frame rate) that is lower than the reference frame rate, and captures and stores the images. The reference frame rate may be, for example, a frame rate used in at least one of the continuous recording mode, the event recording mode, the one-touch recording mode, and the motion detection mode. For example, while the frame rate of the other recording modes (an example of a second frame rate) is, for example, 20 to 30 frames per second (hereinafter, this may also be referred to as "frames per second"), the frame rate of the time lapse mode is, for example, 1 frame per second. For example, for the front camera 10, the controller 30 sets the frame rate to 23 frames per second when the resolution is set to 4K in the continuous recording, event recording, and one-touch recording modes, and 28 frames per second when the resolution is set to any other setting. On the other hand, for the rear camera 20, the controller 30 fixes the frame rate to 27.5 frames per second regardless of the resolution in the continuous recording, event recording, and one-touch recording modes, and sets it to 1 frame per second in the time-lapse mode. The reason for adopting 23 frames per second is that it is advantageous for reducing the flashing of LED traffic lights in captured images and reducing the video generation capacity. Details regarding this will be described in the second embodiment.

[0095] In this embodiment, the controller 30 stores video captured in time lapse mode as a time-compressed moving image. For example, video data captured at 1 frame per second is compressed to 30 frames per second, which is the same frame rate as in other recording modes, and then stored. Note that video data captured in time lapse mode may also be stored as a moving image at one frame per second.

[0096] The motion detection mode is a recording mode in which an image is captured and stored in response to the detection of a moving object. Specifically, when the motion detection mode is selected, the controller 30 detects a moving object from changes in the images captured by the front camera 10 and the rear camera 20, and stores the image data when there is movement (i.e., when a moving object is detected). The frame rate in the motion detection mode is higher than the frame rate in the time lapse mode, for example, 20 to 30 frames per second. The controller 30 performs motion detection based on the image data temporarily written to the RAM 33, and when a moving object is detected, the controller 30 performs recording by writing the image data to the memory card 45 based on the image data in the RAM 33.

[0097] The recording function of the controller 30 creates a new file each time a video is recorded for a predetermined period of time, for example, one minute in continuous recording mode, 30 minutes in time lapse mode, and 40 or 30 second intervals in event recording mode and one-touch recording.

[0098] The controller 30 has a parking memory function that stores information about the vehicle 100 while it is parked by using power supplied from an external battery when the engine is off. The controller 30 can set a time lapse mode or a moving object detection mode as a recording mode for parking memory. If parking memory is not set, the controller 30 continues in a constant memory mode, for example, as when the engine is on. Whether the vehicle is parked can be determined using a well-known method, and may be determined using one or more of the following: the accessory power is turned off; the engine is turned off; power supply from the external battery has started; and the vehicle speed is 0 km / h or a predetermined speed or less.

[0099] In this embodiment, the controller 30 can select either the time lapse mode or the moving object detection mode as the recording mode for parking storage. In other words, the controller 30 makes an exclusive selection between the time lapse mode and the moving object detection mode, i.e., when one mode is selected, the other mode is not executed.

[0100] The controller 30 may also have a function of automatically switching to either the time lapse mode or the moving object detection mode when a predetermined condition is met. This predetermined condition can be set based on various factors, such as location or time. Specifically, the controller 30 automatically switches to either the time lapse mode or the moving object detection mode, which has been pre-selected as a recording mode for recording parking information, when the vehicle 100 is parked at a pre-registered location based on location information detected by the GPS receiver 41, or when a predetermined time has arrived based on time information from the timer 34 or the like.

[0101] For example, the motion detection mode is preferably selected when parking in a location with few people or cars. This reduces the amount of video data stored by recording only when people or cars approach, which is rare. On the other hand, if the parking location is in front of a major road or other location where people or cars frequently approach the vehicle 100, selecting the motion detection mode results in almost constant recording, resulting in an increase in the amount of video data. Therefore, in parking locations facing major roads, the time lapse mode is preferable because it reduces the amount of video data stored. Furthermore, in terms of time, the time lapse mode is preferable when the parking location is in a time period where there are many people and cars passing by, and the motion detection mode is preferable when the parking location is in a time period where there are many people and cars passing by. In addition, the time lapse mode is preferable when the parking location is in a relatively safe location, such as a home or workplace, where it is easy to keep an eye on, or at night, while the motion detection mode is preferable when the parking location is in a difficult-to-see location, such as a travel destination or an unfamiliar place, where safety is difficult to ensure. For this reason, when certain conditions such as location and time are met, the controller 30 may automatically switch the recording mode for parking storage by selecting either the time lapse mode or the moving object detection mode, whichever is more suitable for the conditions.

[0102] Furthermore, when the motion detection mode is selected, the controller 30 automatically switches to a time-lapse mode, which is more power-efficient than the motion detection mode, if a predetermined condition is met. The predetermined condition can be set based on various factors. For example, the controller 30 switches to the time-lapse mode when a state in which no motion is detected continues for a predetermined period of time or longer, i.e., when no video data has been stored in the motion detection mode for a predetermined period of time or longer. Specifically, the controller 30 measures the time during which no motion is detected in the motion detection mode using the timer 34, and automatically switches to the time-lapse mode when this time exceeds a predetermined period of time. Note that the time-lapse mode and the motion detection mode may be executed simultaneously to enhance surveillance functionality when the vehicle is parked. In other words, the controller 30 may capture images intermittently, and when a moving object is detected, capture and store images at a normal frame rate.

[0103] The memory card 45, which is the storage destination for video data in the drive recorder 1, has at least two storage areas, a first storage area and a second storage area. The recording function realized by the recording processing program executed by the controller 30 records video data captured in the event recording mode, i.e., in response to the occurrence of a specific event, in the first storage area (an event recording folder in this embodiment). Also, the second storage area (a normal recording folder in this embodiment) stores video data captured in the continuous storage mode, time lapse mode, and motion detection mode.

[0104] The controller 30 performs a recording function by dividing video data captured over a certain period of time into separate files and storing them in a storage area on the memory card 45. Each file is assigned an eight-digit file number. The file numbers are assigned in ascending order based on the order in which the files were created. The file names may contain other text besides the file number, such as a numeric value indicating the date and time of capture. For example, the file name may be in the format "00000001_202004221234_N_F." "00000001" is the eight-digit file number. "202004221234" is the recording date and time (year, month, day, hour, minute), which in this example represents 12:34 PM on April 22, 2020. The character N indicates the file type. "N" indicates continuous recording mode, while "G" indicates event recording mode, "S" indicates one-touch recording, "L" indicates time-lapse mode, and "M" indicates motion detection mode. "F" indicates the type of camera. "F" indicates image data from the front camera 10, while "R" indicates that it is the rear camera 20.

[0105] Furthermore, the recording processing program executed by the controller 30 can separately set and store specifications such as recording codec and resolution of the video data captured by the front camera 10 and the rear camera 20.

[0106] For example, in this embodiment, the front camera 10 can select at least one of H.264 (an example of a first codec) and H.265 (an example of a second codec) which has a higher compression rate than H.264 as its recording codec. Meanwhile, the rear camera 20 is set to H.264, which has a lower compression rate than H.265. A recording processing program executed by the controller 30 stores video data captured by the front camera 10 using either the H.264 or H.265 recording codec on the memory card 45, and stores video data captured by the rear camera 20 using H.264 on the memory card 45. The controller 30 adjusts the video quality so that the recording time is the same for both the H.264 and H.265 video data. The controller 30 also sets the recording codec of the front camera 10 to H.264 as the default setting. The reason for this is that devices capable of hardware decoding (e.g., PCs) are not yet widespread, so the standard setting (default) is H.264. However, users can change from H.264 to H.265. Because H.265 has a higher compression rate than H.264, if the file size of video data recorded using each codec is the same, H.265 will provide higher image quality. Furthermore, the codec setting (H.265 / H.264) of the front camera 10 does not affect the maximum number of recordings. The maximum number of recordings refers to the combined number of event-recorded video files and one-touch recording video files, which are recorded when the user presses a specific operation button on the operation unit 13.

[0107] In this embodiment, the front camera 10 can select any one of the following resolutions: 1920×1080 (so-called 2K) (an example of a first resolution), 2560×1440, and 3840×2160 (so-called 4K) (an example of a second resolution). On the other hand, the rear camera 20 has a resolution set to 1920×1080 (so-called 2K) (an example of a first resolution). In the recording processing program executed by the controller 30, video data captured by the front camera 10 at any one of the resolutions of 1920×1080, 2560×1440, and 3840×2160 is stored in the memory card 45, and video data captured by the rear camera 20 at 1920×1080 is stored in the memory card 45.

[0108] Furthermore, the controller 30 has a function for detecting the write capability for writing captured video data related to the recording function to the memory card 45, and a notification function for issuing a warning (an example of a first warning) via the display 12 or the speaker 40 if the write capability is below a predetermined write capability. The controller 30 detects the write capability, for example, by measuring the write speed of the captured video data to the memory card 45. The write speed can be calculated, for example, from the amount of video data to the memory card 45 and the time required for writing. The controller 30 then issues a warning as a notification function if the measured write speed falls below a predetermined speed. The detection of the write capability in the controller 30, for example, evaluation (benchmarking), is preferably performed continuously during recording, but may also be performed, for example, when the drive recorder 1 is started up or at other times.

[0109] On the other hand, the recording function of the controller 30 allows the captured video data to be written to the memory card 45 even when a warning is issued by the notification function. In other words, the controller 30 does not prohibit writing even when a warning is issued by the notification function, and continues writing to the memory card 45. For example, the controller 30 continues recording while displaying a pop-up indicating the warning issued by the notification function. The controller 30 may display the pop-up superimposed on the video being captured and displayed on the display 12. If a predetermined operation button on the operation unit 13 is pressed while the pop-up is displayed, the controller 30 hides the pop-up (hides it) and continues recording. Instead of hiding the pop-up, it is also possible to increase its transparency and keep it dimmed, or to continue displaying it in a smaller size. If an error subsequently occurs, the controller 30 displays a warning indicating the error (an example of a second warning, for example, an error pop-up) and stops writing (recording). The error here indicates that writing of the video data to the memory card 45 failed. The warning indicating an error is a warning to notify the user that such an error has occurred, and may include a message such as "A write error has occurred," a specified icon indicating the occurrence of an error, or other display element.

[0110] In this way, the drive recorder 1 continues to operate as is if the memory card 45 has a sufficiently high write speed, but if the drive recorder detects that the write speed is clearly slow, it issues a warning indicating that recording may fail. This is because a 4K-compatible drive recorder 1 requires a memory card 45 with a faster write speed than a conventional drive recorder with a lower resolution. For example, if the memory card 45 is an SD card, it must be compatible with UHS-I U3 or higher.

[0111] FIG. 16 shows a specific example of a warning display (warning display) using the notification function described above. FIG. 16(a) shows a warning display when the write capacity is equal to or less than a predetermined write capacity. This warning is intended to inform the user that the write capacity of the memory card 45 is equal to or less than the predetermined write capacity (in other words, that the write capacity of the memory card 45 is insufficient), as described above. In this example, the warning includes information such as "SD Slow Speed," indicating that the write capacity of the memory card 45 is equal to or less than the predetermined write capacity. The warning also includes information such as "Possible Recording Failure," indicating that the video recording may fail. While the warning may include only one of these warnings, including both makes it easier for the user to understand the nature of the warning. FIG. 16(b) shows an example of a warning indicating the error described above, including information such as "SD Card Error." The information included in the warning is textual information here, but may also include icons (e.g., the icons shown in FIGS. 16(a) and 16(b)), animation, or other elements. The warning in Figure 16(a) is a warning when writing to memory card 45 will continue even though the writing capacity is insufficient, and the warning in Figure 16(a) is a warning when writing to memory card 45 will not or cannot continue because the writing capacity is insufficient.

[0112] Furthermore, the controller 30 may measure the lifespan of the memory card 45 as the write capability. This lifespan can be estimated, for example, from the number of busy signals (BUSY) generated when writing video data to the memory card 45. The controller 30 then notifies the user of the measured lifespan as a notification function. Specifically, the lifespan notification may indicate the remaining number of writable times, the remaining writable period, the remaining amount of writable data, or the recommended replacement time. Note that there is a correlation between the lifespan of the memory card 45 and the write speed of the memory card 45. If recording is performed over a long period of time, the write capability may decrease over the lifespan of the memory card 45, and for example, the write speed may decrease or writing may become impossible.

[0113] Furthermore, the controller 30 restarts the drive recorder 1, which has a recording function, when switching to the memory card 45. Specifically, when the memory card 45 is removed from the memory card reader 44 and the same or another memory card 45 is reinserted into the memory card reader 44, the controller 30 automatically restarts the drive recorder 1. More specifically, when the logic of the memory card 45 replacement detection (for example, the CARD_DET terminal, which is a terminal for detecting the memory card 45) changes, the controller 30 automatically restarts the drive recorder 1, and does not allow hot swapping.

[0114] The controller 30 has a playback function for playing back video data stored by the recording function. The playback function has a function for selectively playing back video data captured by the front camera 10 and video data captured by the rear camera 20. The user can switch which video to play back by, for example, operating a predetermined operation button on the operation unit 13.

[0115] The display 12 also functions as a notification unit that notifies the user of the role played by the memory card 45 accessed by the controller 30.

[0116] Furthermore, a viewer program having a function of simultaneously playing back video data captured by the front camera 10 and video data captured by the rear camera 20 may be provided. The display area of ​​the display 12 may be divided into two areas, with the video captured by the front camera 10 displayed in one area and the video captured by the rear camera 20 displayed in the other area. The simultaneous playback may be, for example, synchronous playback, in which videos captured by the front camera 10 and the rear camera 20 at the same time are played back simultaneously. In this way, the viewer program that plays back data recorded by the drive recorder 1 is configured to be able to simultaneously play back the videos from the front camera 10 and the rear camera 20, while the drive recorder 1 does not have a function of simultaneously playing back the videos from the front camera 10 and the rear camera 20, and is configured to be able to switch between playing back the videos from the front camera 10 and the rear camera 20. If the user wants to play back these videos simultaneously, he or she can play back the videos recorded on memory card 45 using a terminal on which a viewer program is installed, or if he or she only needs to play back one of them, he or she can immediately check the video while leaving memory card 45 inserted in drive recorder 1, which is convenient as it allows the user to use either method depending on the situation at hand. However, drive recorder 1 itself may have a function for simultaneous playback.

[0117] Furthermore, the display 12 may be provided on the dashboard 105 of the vehicle 100 as described above, or a display capable of playing back only the video captured by the rear camera 20 out of the video captured by the front camera 10 and the video captured by the rear camera 20 may be provided on the dashboard 105. Furthermore, the playback function may be implemented not only on the display 12 of the drive recorder 1, but also on the display of another information terminal such as a PC, smartphone, mobile phone, or tablet terminal. For example, a viewer program having the playback function may be installed in another information terminal to realize the playback function on the display of the information terminal. The viewer program may be provided from the drive recorder 1 to the information terminal via the communication circuit 43, stored in the memory card 45, or provided via a communication network such as the Internet.

[0118] [Effect] Next, we will explain an example of the operation of the recording mode for parking storage executed as a recording function of the controller 30 of the drive recorder 1. Here, Fig. 3 shows an example of a setting screen for the recording mode for parking storage, Figs. 4(a) to (c) show transition diagrams of an example of a manual switching operation to the time lapse mode, Fig. 5 shows an explanatory diagram of an example of operation in the time lapse mode, Figs. 6(a) to (c) show transition diagrams of an example of a manual switching operation to the moving object detection mode, and Fig. 7 shows an explanatory diagram of an example of operation in the moving object detection mode, and the following explanation will be based on these figures.

[0119] In the drive recorder 1 of this embodiment, the recording mode for parking storage can be set in advance. For example, when the operation button 13d, which is the menu button shown in FIG. 1A, is pressed, the controller 30 opens a setting menu. When "Parking Storage Method" is selected from "Parking Storage" in the setting menu, the setting screen shown in FIG. 3 is displayed on the display 12. As shown in FIG. 3, the setting screen for the recording mode for parking storage displays "Time Lapse" and "Motion Detection," and the set items are marked with square marks. In other words, the time lapse mode is selected in FIG. 3. For example, the time lapse mode is selected as the standard setting, and the user can switch modes by operating the operation button 13a, which also functions as the up movement operation, or the operation button 13b, which also functions as the down movement operation, shown in FIG. 1A. The controller 30 executes parking storage in the recording mode for recording storage set in this way.

[0120] Specifically, when starting the time lapse mode for parking storage, the user first turns off the engine of the vehicle 100, as shown in FIG. 4(a). From this point, recording for parking storage using an external battery as a power source starts, and the controller 30 plays a voice message saying "Recording will start" from the speaker 40. At the same time, the controller 30 turns on the power lamp next to the display 12 of the drive recorder 1 in red, flashes a red circle storage mark icon on the display 12, and displays the word "Recording" next to it. At this point, the controller 30 continues capturing and storing images in the continuous recording mode that was normally executed before the engine was turned off.

[0121] Next, as shown in FIG. 4(b), when the user presses the operation button 13c, which also serves as the OK operation, for three seconds or more, the controller 30 displays a pop-up message saying "Time Lapse" on the display 12 and plays a voice message saying "Starting time lapse mode" from the speaker 40. Then, while in time lapse mode, the controller 30 displays a time lapse icon at the top of the display. After this, the controller 30 captures and stores images in time lapse mode.

[0122] To end the time lapse mode, the user presses the operation button 13c, which also functions as the OK operation, while in time lapse mode, as shown in Figure 4(c). When this is done, the controller 30 plays a voice message from the speaker 40 saying "Time lapse mode is ending," followed by a voice message saying "Recording will begin." The controller 30 then switches the recording mode from time lapse mode to continuous recording mode, and captures and stores the images.

[0123] 5, when the time lapse mode is being executed, the controller 30 automatically turns off the display 12 one minute after the time lapse mode is started and continues capturing and storing images. If the user operates the operation unit 13 other than the operation button 13e, which is the storage button for starting event recording, the controller 30 turns on the display 12. On the other hand, when the user presses the operation button 13e, the controller 30 plays a "ding ding" sound from the speaker 40 and starts the event recording mode. Similarly, if an impact to the vehicle 100 is detected, the controller 30 also plays a "ding ding" sound from the speaker 40 and starts the event recording mode.

[0124] The operation for starting the motion detection mode is also similar to that for the time-lapse mode. With the motion detection mode already set as the recording mode for parking storage, the user turns off the engine of the vehicle 100, as shown in FIG. 6(a). Next, as shown in FIG. 6(b), for example, during recording in the continuous recording mode, the user presses and holds the operation button 13c for three seconds or more. This causes the controller 30 to display a pop-up message saying "MOTION DETECTION" on the display 12 and play a voice message saying "MOTION DETECTION MODE IS STARTING" from the speaker 40. During the motion detection mode, a motion detection icon is displayed on the display 12. From this point on, the controller 30 captures and stores images in the motion detection mode. The sensitivity of motion detection in the motion detection mode can be set from multiple levels. For example, the controller 30 sets the sensitivity when the user selects one of Low, Mid, or High.

[0125] To end the motion detection mode, the user presses the operation button 13c while the motion detection mode is active, as shown in Fig. 6(c). This causes the controller 30 to play a voice message from the speaker 40 saying "The motion detection mode is ending," followed by a voice message saying "Recording will begin." The controller 30 then switches the recording mode from the motion detection mode to the continuous recording mode, and captures and stores the image.

[0126] 5, when the motion detection mode is in progress, the controller 30 automatically turns off the display 12 one minute after the motion detection mode is started and continues capturing and storing images. If the user operates any operation unit 13 other than the operation button 13e, which is a storage button for starting event recording, the controller 30 turns on the display 12. On the other hand, if the user presses the operation button 13e, the controller 30 plays a "ding ding" sound from the speaker 40 and starts the event recording mode. Also, if an impact to the vehicle 100 is detected, the controller 30 plays a "ding ding" sound from the speaker 40 and starts the event recording mode. Furthermore, if a moving object is detected, the controller 30 plays a "ding ding" sound from the speaker 40 and captures and stores images in the motion detection mode.

[0127] 8 shows a flowchart illustrating an example of a parking storage recording mode execution control routine. The procedure for controlling the parking storage recording mode execution executed by the controller 30 will be described below with reference to this flowchart. This routine starts when the engine is detected to be turned off (corresponding to the time points in FIGS. 4(a) and 6(a) above), and is executed by the controller 30 based on power supplied from an external battery. The recording mode at the start is the continuous recording mode. Power may be supplied to the drive recorder 1 by a power supply unit that enables power supply from the vehicle battery when the engine is off.

[0128] First, in step S1, the controller 30 determines whether a manual operation to switch to the parking recording mode has been performed, as shown in Figures 4(b) and 6(b) above. The manual operation is, for example, a long press of the operation button 13c. If the determination result is false (No), that is, if the user has not performed an operation to switch to the parking recording mode, the process proceeds to step S2.

[0129] In step S2, the controller 30 determines whether the location where the vehicle 100 is parked is a predetermined location or whether the current time is a predetermined time. This predetermined location or time is an example of a predetermined condition for automatically switching to the parking storage recording mode. If the determination result is false (No), that is, if the predetermined condition is not met, the process proceeds to step S3.

[0130] In step S3, the controller 30 captures and stores images in the continuous recording mode, and then the process proceeds to step S8.

[0131] On the other hand, if the user switches to the parking recording mode in step S1 and the result of the judgment is true (Yes), or if the predetermined conditions are met in step S2 and the result of the judgment is true (Yes), the process proceeds to step S4.

[0132] In step S4, the controller 30 determines whether or not the predetermined recording mode for storing parking information is the time lapse mode. If the determination result is true (Yes), the process proceeds to step S5.

[0133] In step S5, the controller 30 performs imaging and storage in the time lapse mode (corresponding to FIG. 5 described above), and the process proceeds to step S8.

[0134] On the other hand, if the recording mode for parking storage is not the time lapse mode in step S4, that is, if the recording mode for parking storage is the moving object detection mode, the determination result becomes false (No), and the process proceeds to step S6.

[0135] In step S6, the controller 30 performs imaging and storage in the moving object detection mode (corresponding to FIG. 7 described above), and the process proceeds to step S7.

[0136] In step S7, the controller 30 determines whether a state in which no moving object has been detected has continued for a predetermined time or longer. If the determination result is true (Yes), the process proceeds to step S5 described above, where image capture and storage are performed in time lapse mode. That is, the recording mode for parking storage is automatically switched from moving object detection mode to time lapse mode. On the other hand, if the determination result in step S7 is false (No), the process proceeds to step S8.

[0137] In step S8, the controller 30 determines whether the time set by the off timer for the external battery has elapsed. If a power supply unit that allows power to be supplied from the vehicle battery while the engine is off is used and the power supply unit has a voltage monitoring function, the voltage monitoring function may be used to determine whether the voltage of the vehicle battery has dropped below a predetermined voltage. If the determination result in step S8 is false (No), that is, if power supply to the drive recorder 1 can be continued, the controller 30 returns from the routine to step S1.

[0138] On the other hand, if the judgment result of step S8 is false (No), that is, if the external battery's off timer is activated or the voltage monitoring function of the power supply unit is activated and power supply to the drive recorder 1 is stopped, processing proceeds to step S9.

[0139] In step S9, the controller 30 turns off the power of the drive recorder 1 and ends the routine.

[0140] [effect] As described above, the drive recorder 1 of this embodiment has, in the recording processing program of the controller 30, recording functions for storing images captured in the vehicle 100, including a time lapse mode (an example of a first recording mode) in which images are captured intermittently and stored, and a moving object detection mode (an example of a second recording mode) in which images are captured and stored in response to the detection of a moving object.

[0141] The time lapse mode, which captures and stores images intermittently, captures images less frequently than other recording modes, reducing the amount of video data stored. The motion detection mode, which captures and stores images in response to the detection of a moving object, can also prevent image capture and storage if no moving object is detected. Therefore, these two recording modes can capture images less frequently than the normal recording mode, reducing the amount of video data stored. Providing the time lapse mode and motion detection mode as recording functions for storing images captured in vehicle 100 allows the user to select the recording mode appropriate for the situation, enabling efficient image capture and storage, and enhancing user convenience.

[0142] In other words, the time lapse mode is a recording mode in which images are captured and stored at a frame rate (an example of a first frame rate) slower than other recording modes, and the motion detection mode is a recording mode in which images are captured and stored and motion detection is performed at a frame rate (an example of a second frame rate) higher than the time lapse mode.

[0143] In other words, the time lapse mode, which captures and stores images at a low frame rate, reduces the number of times images are captured and the amount of video data to be stored. Furthermore, the motion detection mode, which captures and stores images at a higher frame rate than the time lapse mode in response to the detection of a moving object, can also reduce the number of times images are captured and the amount of video data to be stored, since it is possible not to capture and store images if no moving object is detected. Providing the time lapse mode and motion detection mode as recording functions for storing captured images in vehicle 100 allows the selection of a recording mode appropriate for the situation, enabling efficient image capture and storage, and further enhancing user convenience.

[0144] Furthermore, the recording function of the controller 30 allows the user to select either the time lapse mode or the motion detection mode. By selectively selecting either the time lapse mode or the motion detection mode, it is possible to prevent the time lapse mode and the motion detection mode from being executed in parallel. This reduces the processing load on the controller 30 and reduces costs by eliminating the need for a high-performance encoder, etc.

[0145] Furthermore, the recording function of the controller 30 is a parking memory function that records while the vehicle 100 is parked. This makes it possible to provide a system with a parking memory function that is more convenient for the user. With the parking memory function, for example, if you want to record the state of the vehicle while it is parked for a long period of time, you may want to capture and record images intermittently, and detect the presence of a third party attempting to tamper with or steal the vehicle or its contents, or other moving objects associated with an abnormality. The contents of each of the time lapse mode and the moving object detection mode are determined so that recording can be performed in an appropriate manner, taking into account the circumstances of the vehicle being parked.

[0146] In addition, in the time lapse mode of this embodiment, captured video is stored as a time-compressed moving image. Video captured intermittently, i.e., at a low frame rate, results in long periods of still images. Therefore, by compressing the video into a time-compressed moving image, the amount of video data stored can be reduced. This also shortens the time required to view the video data.

[0147] Furthermore, when a predetermined condition is met, the recording function of the controller 30 automatically switches to either the time lapse mode or the moving object detection mode as the recording mode for parking storage. This reduces the need for the user to switch between the time lapse mode and the moving object detection mode. The parking storage function is particularly convenient because it eliminates the need for the user to manually set the recording mode or check the currently set mode, even when the user wants to get out of the vehicle 100 immediately after parking the vehicle 100.

[0148] Furthermore, the recording function of the controller 30 automatically switches to either a preselected time lapse mode or a motion detection mode when the vehicle 100 is at a pre-registered location or time. This allows the preselected time lapse mode or motion detection mode to be switched to depending on the situation at a pre-registered location or time, thereby more appropriately reducing the user's effort. For example, the parking memory function switches to the time lapse mode when the parking spot is in an easily visible location such as a home or workplace, a location with a lot of pedestrians and vehicles, or a time zone with a lot of pedestrians and vehicles. On the other hand, the parking spot is in an out-of-sight location such as a travel destination or an unfamiliar place, a location with little pedestrians and vehicles, or a time zone with little pedestrians and vehicles. This allows the parking spot to be memorized in an appropriate mode depending on the location and time, without the user having to explicitly specify it.

[0149] Furthermore, the recording function of the controller 30 automatically switches to time lapse mode when certain conditions are met when motion detection mode is selected. By switching to time lapse mode when certain conditions are met, even when motion detection mode is selected, the motion detection process can be reduced, further reducing processing load, storage resource consumption, and power consumption. For example, the parking storage function may start recording when a motion object is detected inside or outside the vehicle 100, and end recording and switch to time lapse mode when certain conditions are met, such as when a certain time has passed since recording started or when no motion object is detected. This increases the recording time, reducing storage resource consumption and power consumption.

[0150] Specifically, the recording function of the controller 30 in this embodiment automatically switches to time-lapse mode when no moving object is detected in the moving object detection mode for a predetermined period of time or more. For example, the parking memory function may be configured to record when a moving object is detected inside or outside the vehicle 100, and then terminate the recording and switch to time-lapse mode when a predetermined period of time has elapsed since the start of recording or when no moving object is detected. This prevents the continuation of processing to detect moving objects in situations where there are few moving objects around the vehicle, such as when the vehicle is parked in a location surrounded by obstacles. This reduces the processing load, storage resource consumption, and power consumption associated with moving object detection.

[0151] Furthermore, the recording function of the controller 30 stores event video data captured in response to the occurrence of a specific event in a first storage area, video data other than the event video data in a second storage area, and video data captured in time lapse mode and motion detection mode in the second storage area. This allows for a clear distinction between relatively important event video data and other video data, improving the efficiency of video data review. For example, with the parking memory function, while incidents such as vandalism, intrusion by a third party into the vehicle, and theft may occur while the vehicle is parked, these incidents do not occur frequently. Therefore, the frequency with which parking memory recordings are actually played back and viewed is low. In contrast, event video data is recorded when a specific event occurs, such as when an accident occurs or is nearing an accident. Therefore, it is desirable to be able to quickly find and view the desired video when needed. The video data in the second storage area is data other than event recording data, such as continuous recording video, and is therefore not frequently viewed. Therefore, if the video data of the parking storage recording is stored in the second storage area, the video of the parking storage recording can be managed without interfering with the viewing of the event recording data.

[0152] In this embodiment, the vehicle 100 has imaging units installed at multiple locations on the vehicle that capture images for the recording function. This allows events related to the vehicle to be captured from various positions or angles, and each imaging unit can be switched between time lapse mode and motion detection mode, enabling more reliable and efficient monitoring and capturing images in an appropriate recording mode for each imaging unit. The recording modes of each imaging unit may be the same, or some imaging units may have recording modes that are different from the other recording modes.

[0153] In particular, in this embodiment, the rear camera 20, which is one of the imaging units, is used for the rear of the vehicle and is capable of capturing images with higher sensitivity than the front camera 10. In this way, monitoring of the rear of the vehicle can also be performed with high accuracy. Because the rear window of the vehicle is smoked and there is less light emitted from the vehicle 100 than in the front of the vehicle, by making the rear camera 20 capable of capturing images with higher sensitivity than the front camera 10, it becomes possible to perform appropriate monitoring while suppressing cost increases compared to when all imaging units are made highly sensitive.

[0154] Furthermore, the recording function of the controller 30 of this embodiment stores video data captured by the front camera 10 in one of recording codecs including at least H.264 (an example of a first codec) and H.265 (an example of a second codec) which is more highly compressed than H.264, and stores video data captured by the rear camera 20 in H.264. To explain how to select the codec for the front camera 10, for example, the menu displayed on the display 12 by the controller 30 may include an item called "front codec," allowing the user to select either "H.264" or "H.265" using the operation unit 13. On the other hand, the codec for the rear camera 20 is fixed to H.264.

[0155] In this way, multiple codecs including a high-compression recording codec can be selected for the front camera 10 at the front of the vehicle, which is highly necessary for monitoring, and the rear camera 20 at the rear of the vehicle, which is less necessary for monitoring than the front of the vehicle, captures images using a recording codec lower than the second codec. By dividing the selectable recording codecs between the front and rear imaging units of the vehicle 100 in this way, it is possible to capture and store video data more efficiently according to the imaging location.

[0156] In particular, by using H.264 as the low-compression recording codec and H.265 as the high-compression recording codec, H.264 can capture and store general-purpose video data that can be played back on many commercially available PCs, while H.265 can store high-quality video data with a small amount of data.

[0157] The recording function preferably stores video so that the recording time is the same for video data in the first codec and video data in the second codec. The recording time is the recording time of the video data. This is highly convenient because the recording time does not change even if the compression rate of the stored video data is different. For example, it is less likely that a situation will occur where the recording time is shorter than the user expected as a result of setting the image quality to high, and the user is unable to capture the video they wanted.

[0158] Furthermore, in the recording function of the controller 30 of this embodiment, the recording codec for video data captured by the front camera 10 is set to H.264 as the default setting. While a recording codec with a high compression rate may limit the devices that can play the codec, by setting H.264, which has a relatively low compression rate as the default setting, it is possible to capture and store highly versatile video data that can be viewed on many playback devices unless the user changes the setting, thereby preventing situations in which the video data cannot be viewed.

[0159] In addition, the recording function of the controller 30 of this embodiment stores video data captured by the front camera 10 at any one of resolutions including at least 1920 x 1080 (so-called 2K) (an example of a first resolution) and 3840 x 2160 (so-called 4K) (an example of a second resolution), and the rear camera 20 stores video data captured at 1920 x 1080 (so-called 2K).

[0160] In this way, for the front camera 10, which requires more monitoring, multiple resolutions including 2K and 4K can be selected, and for the rear camera 20, which requires less monitoring than the area in front of the vehicle, video data captured at 2K is stored. By dividing the selectable resolutions between the front and rear imaging units of the vehicle 100 in this way, video data can be captured and stored more efficiently according to the imaging location.

[0161] In addition, in this embodiment, a viewer program is provided that can simultaneously play back the video data captured by the front camera 10 and the video data captured by the rear camera 20. In this way, by simultaneously playing back the video data from the imaging units in front and behind the vehicle, the situations in front and behind the vehicle at the same time can be simultaneously displayed, thereby improving the efficiency of checking the video data.

[0162] For example, there are low-spec devices that have low image processing capabilities and cannot display a highly compressed recording codec such as H.265. For the convenience of users of such devices, the rear camera 20 can be fixed to a low-compression recording codec such as H.264, and the front camera 10 can also be set to H.264 as the standard setting, thereby minimizing situations where stored video data cannot be played back.

[0163] In this embodiment, the controller 30 has a function for detecting the write capacity for writing captured video to a storage medium and a function for issuing a warning if the write capacity is below a predetermined level. Even if the notification function issues a warning, the recording function can still write captured video to the memory card 45. In this way, by detecting the write capacity of the memory card 45 and issuing a warning if the write capacity is below the predetermined level while allowing storage (writing) to the memory card 45 to continue, this prevents a situation in which video data cannot be stored and ensures a replacement period for the user while continuing to use the memory card 45. Specifically, the controller 30 can inform the user that the write capacity of the memory card 45 is insufficient (in other words, that the write capacity of the memory card 45 is below the predetermined level), and allows recording using the memory card 45 to continue. This prevents situations in which recording is not possible due to insufficient write capacity of the memory card 45. When the user receives the warning, they know that they need to prepare a memory card 45 with sufficient write capacity and can take appropriate action.

[0164] The detection function of controller 30 measures the writing speed of captured video to memory card 45 as the writing capacity, and the notification function issues a warning if the writing speed is below a predetermined speed. In this way, the writing capacity of memory card 45 can be measured at the same time as video data is written, making it possible to notify the user that the writing speed of memory card 45 is insufficient, and also allowing recording using memory card 45 to continue, thereby preventing situations in which recording is not possible due to insufficient writing speed of memory card 45.

[0165] The detection function of the controller 30 measures the lifespan of the memory card 45 as the writable capacity detected by the detection function, and the notification function can notify the user of the lifespan. This allows the user to easily determine the appropriate time to replace the memory card, and can prevent a situation in which video data cannot be stored due to, for example, a malfunction of the storage medium due to the end of its lifespan.

[0166] Furthermore, the recording function of the controller 30 of this embodiment restarts the device having the recording function when the memory card 45 is switched. In this way, the memory card 45 can be switched stably.

[0167] Furthermore, the recording function of the controller 30 in this embodiment stores video data in separate files, with each file being assigned an eight-digit serial file number. This facilitates file management of video data and prevents overflow. This is based on the knowledge that, taking into account the capacity and actual usage of the memory card 45, an eight-digit serial number will prevent overflow.

[0168] The recording processing program of this embodiment is a program for causing a computer to realize the recording function, playback function, detection function, notification function, etc. of the controller 30 described above, and can achieve the effects described above.

[0169] [Second embodiment] Next, a second embodiment of the present invention will be described. The configuration and functions of the drive recorder 1 of this embodiment, which are common to the first embodiment, will not be described. First, the background to the conception of this embodiment will be described. LED traffic lights display their respective colors by flashing LEDs using AC power at a commercial frequency of 60 Hz in western Japan and 50 Hz in eastern Japan. Meanwhile, drive recorders typically comply with the NTSC (National Television System Committee) or PAL (Phase Alternating Line) standards, capturing and recording video data at 30 or 25 frames per second. While this number varies by country, countries with a commercial frequency of 60 Hz typically handle PAL video at 25 frames per second, while countries with a commercial frequency of 50 Hz typically handle NTSC video at 30 frames per second. In Japan, LED traffic lights flash without an inverter, using both 60 Hz and 50 Hz. As a result, current drive recorder and autonomous driving footage suffer from the inconvenient flashing of the colors displayed by LED traffic lights. Furthermore, if the flashing of the LED traffic light is synchronized with the timing of the image capture, the image will only be captured when the LED traffic light is off, which may make it impossible to determine the color of the traffic light from the image. This means that if you want to verify the vehicle situation from the image later, such as the situation at the time of an accident, you will not be able to tell the color of the LED traffic light, which can hinder the verification or reduce the evidential value of the image in explaining the situation at the time of the accident.

[0170] To solve this problem, the recording function of the drive recorder 1 of this embodiment is configured to control the synchronization between the flashing of the LED traffic light and the image capture timing. To achieve this synchronization, the drive recorder 1 should capture images at a frame rate greater than 25 frames / second (for 50 Hz) and less than 30 frames / second (for 60 Hz). Figure 9 is a graph showing the results of simulating the illumination state of the LED traffic light at each image capture timing. In this graph, the horizontal axis corresponds to the image capture timing, and the vertical axis corresponds to the illumination state of the LED traffic light. On the vertical axis, "0" represents the LED traffic light being off, and "1" represents the LED traffic light being on. The graph in Figure 9(a) corresponds to 29.8 frames / second, the graph in Figure 9(b) corresponds to 27.5 frames / second, and the graph in Figure 9(c) corresponds to 29 frames / second. It can be seen that the illumination timing is present in images captured at all frame rates.

[0171] Figure 10 is a graph showing the results of a simulation of the lighting state of an LED traffic light at each imaging timing when frames are thinned out for communication purposes; the vertical and horizontal axes are the same as those in Figure 9. Figure 10(a) shows the case where video captured at 27.5 frames / second is thinned to 5.5 frames / second for communication purposes, Figure 10(b) shows the case where video captured at 27.5 frames / second is thinned to 1.375 frames / second for communication purposes, and Figure 10(c) shows the case where video captured at 27.5 frames / second is thinned to 1.309 frames / second for communication purposes. The more communication volume is thinned out, the fewer frames are captured when the traffic light is on, but it can be confirmed that the video is still captured so that the lighting timing exists.

[0172] Another method would be to capture images at a frame rate of 27 frames per second or more and 28 frames per second or less, corresponding to a frame rate between 25 Hz and 30 Hz, to avoid synchronization, but the LED traffic light would still be captured flashing. Therefore, the recording function of the drive recorder 1 is preferably configured to capture and store images at a frame rate of less than 25 frames per second. In particular, the inventors considered using a frame rate of 23 frames per second or more and 24 frames per second or less (e.g., 23 frames per second or 24 frames per second) to further reduce the impact of flashing LED traffic lights. In this case, the recording function of the drive recorder 1 is configured to capture and store images at a frame rate of 23 frames per second or more and 24 frames per second or less in at least one of the following modes: motion detection mode, continuous recording, event recording, and one-touch recording (continuous recording, event recording, and one-touch recording are examples of the third recording mode). This further reduces the number of frames per unit time compared to conventional modes. This reduces the amount of video data generated, ultimately saving storage and communication resources. This also increases the amount of time available for recording video on a storage medium. Furthermore, while increasing image quality (e.g., lowering the compression rate to record clearer video) only results in a few percent difference in video quality, these few percent differences can have a significant impact when increasing image quality. Furthermore, the inventors have confirmed that a frame rate of 23 frames per second or higher and 24 frames per second or lower does not hinder the ability to understand and verify vehicle conditions from video. Figure 11 is a graph showing the results of a simulation of the illumination status of an LED traffic light at each imaging timing, with the vertical and horizontal axes being the same as those in Figures 9 and 10. The graph in Figure 11(a) corresponds to 24 frames per second, and the graph in Figure 11(b) corresponds to 23 frames per second. It can be seen that imaging is possible at both frame rates when the traffic light is illuminated. Note that "24 frames per second or lower" may be interpreted as "less than 24 frames per second" where appropriate.

[0173] The frame rate may be even lower. For example, a frame rate of 15 frames / second or higher but lower than 23 frames / second (e.g., 22 frames / second or lower) reduces the flashing of LED traffic lights and is advantageous for grasping and verifying the vehicle status from the video. FIG. 12 is a graph showing the results of simulating the illumination state of LED traffic lights at each imaging timing, with the vertical and horizontal axes being the same as those in FIGS. 9 to 11. The graph in FIG. 12(a) corresponds to 22 frames / second, and the graph in FIG. 12(b) corresponds to 15 frames / second. Furthermore, a frame rate lower than 15 frames / second, for example, 10 frames / second or 5 frames / second, is even more advantageous in reducing the amount of video data generated. In this case, the vehicle status can still be grasped and verified from the video. The lower limit of the frame rate that can be adopted in the drive recorder 1 may be determined taking into consideration factors such as the purpose of the video and whether the vehicle status can be grasped and verified.

[0174] The above has been explained using the example of reducing the blinking of LED traffic lights, but even when capturing images of traffic signs that use LEDs (i.e., LED signs) or other blinking installations, the increase in the amount of video data can be suppressed while preventing continued capture when the lights are turned off. Furthermore, even when the video captured by the imaging device is checked later or when the number of frames is thinned and transmitted, the video captured when the lights were on can be secured.

[0175] [Third embodiment] Next, a third embodiment of the present invention will be described. The configuration and functions of the drive recorder 1 that are common to the first embodiment will not be described. One method for reducing the flashing of the illumination color of captured LED traffic lights, etc., is to use an imaging element with a function to suppress LED flicker that occurs during imaging. As an example, an imaging element with the following configuration is used in at least one of the front camera 10 and the rear camera 20 of this embodiment. A drive recorder having an imaging element such as a typical CMOS sensor typically has one sensor per pixel. Instead, the imaging element of this embodiment has a first sensor and a second sensor per pixel. In this imaging element, the first sensor corresponds to a first light-receiving element, which is a large light-receiving element. The second sensor corresponds to a second light-receiving element, which is smaller than the first light-receiving element. The imaging element captures images at a first cycle using the first light-receiving element and at a cycle longer than the first cycle using the second light-receiving element. This is because the second light receiving section has a smaller light receiving area (e.g., light receiving surface) than the first light receiving section, allowing it to capture more light. Therefore, the first light receiving section and the second light receiving section have different light receiving periods (also referred to as exposure periods). In the image sensor, the first light receiving section and the second light receiving section are configured, for example, so that the shutters are open during the light receiving period and closed during the non-light receiving period, but the mechanism for switching between receiving and not receiving light is not limited to this. The image sensor combines and outputs, for each pixel, a signal indicating the light receiving result of the first light receiving section and a signal indicating the light receiving result of the second light receiving section. Because this combined signal reflects the amount of light received by the first light receiving section and the second light receiving section, the controller 30 can generate and store an image with reduced influence from flashing LED traffic lights, etc. When such an image sensor is used, the second light receiving element receives light even during periods when the first light receiving element does not, so compared to a configuration in which a single light receiving element is provided for each pixel, it is possible to prevent flashing LED traffic lights and the like from being captured in an image. In addition, by using an image sensor with such a pixel structure and exposure method, it is expected that high-quality images with a wide dynamic range will be captured even in scenes with large differences in brightness, such as entrances and exits.

[0176] In a drive recorder 1 equipped with such an imaging element, the controller 30 may insert an I frame (i.e., a key frame) three times per second, as in the case of capturing images at 30 frames per second. This is advantageous in that a clear image can be obtained once every eight frames. In contrast, conventionally, one I frame is inserted once every ten frames.

[0177] Furthermore, when recording images from the front camera 10 and the rear camera 20 using the front camera, the controller 30 may set the front camera 10 to a frame rate of 24 frames / second or less with a relatively high resolution (for example, 4K), while setting the rear camera 20 to a frame rate of 27.5 frames / second with a relatively low resolution (full HD). In this way, good quality images can be obtained from the front camera 10, which is highly necessary for capturing images.

[0178] The above-mentioned imaging element is flicker-free, so there is no need to take into account things like blinking signals. However, by deliberately setting the frame rate outside of 30 frames / second and 25 frames / second and setting it to a lower frame rate (for example, the frame rate described in the second embodiment), it is possible to both suppress blinking and reduce the amount of data.

[0179] Furthermore, the keyword "electronic transmission" will become important in the future. When it comes to electronic transmission, it will be difficult to transmit at high frame rates such as 30 or 20 frames per second. Furthermore, when storing images on a server, there is a possibility that the same images will be saved unnecessarily, resulting in insufficient storage capacity. On the other hand, even when using a low frame rate, it is important to ensure that LED traffic lights and other similar devices are lit in each frame. When LEDs are used to create characters on road signs, such as speed signs, or other road features, scanning does not produce characters in the captured image (e.g., some lights are on, some are off), but using the image sensor described above solves this flickering problem.

[0180] [Fourth embodiment] Next, a fourth embodiment of the present invention will be described. Of the configuration and functions of the drive recorder 1, those that are common to the first embodiment will not be described.

[0181] There are memory cards (such as SD cards) on the market that are used in dash cams that have insufficient read and write speeds. Even such inappropriate SD cards may be advertised on the packaging as "UHS Speed ​​Class 3" or "for dash cams," but in reality they do not have sufficient performance, or there are cards that are fast when first purchased but quickly lose speed.

[0182] As described above, the controller 30 of the first embodiment has a function for detecting the write capability for writing captured video data related to the recording function to the memory card 45, and a notification function for issuing a warning via the display 12 or the speaker 40 if the write capability is below a predetermined write capability. In addition to the first embodiment described above, other embodiments of such detection and notification functions include the following. The following describes an example in which the memory card 45 is an SD-compliant memory card (e.g., a miniSD card, a microSD card, etc.). Specifically, the following five methods will be described. The controller 30 may be capable of executing all or some of the methods described in the first embodiment and the following five methods. Furthermore, the user may be able to select one of the methods by setting the method.

[0183] (First method: Reading write capability information from a register, etc.) In the first method, the controller 30 checks information (hereinafter referred to as "write capacity information") that identifies the write capacity of the memory card 45, stored in the CSD register (an example of an internal register), using a command for determining the contents of the CSD register (Card-Specific Data register), such as CMD9, of the memory card 45. The write capacity information may directly or indirectly indicate, for example, the amount of data that can be written (i.e., transferred) to the memory card 45 per unit time. The write capacity information may include a maximum data transfer rate value and card class information. If the write capacity information is true, the write capacity indicated by the write capacity information should match the actual write capacity of the memory card 45 and should also match the write capacity stated on the packaging (packaging) or instruction manual for the memory card 45.

[0184] In this way, the detection function of the first method detects the writability based on the writability information pre-stored in memory card 45. The higher the writability, the greater the amount of data that can be written to memory card 45 per unit time, and the lower the writability, the less the amount of data that can be written to memory card 45 per unit time.

[0185] The notification function of the controller 30 issues a warning to the effect that the write capability of the memory card 45 does not meet the write capability (specifications in this embodiment) required by the drive recorder 1 based on the write capability information. For example, the controller 30 issues a warning if the maximum data transfer rate specified by the write capability information is insufficient compared to the maximum data transfer rate required by the drive recorder 1. For example, the controller 30 issues a warning if the card class does not match the card class required by the drive recorder 1 (in other words, does not comply with the standard). The warning in the first method is, for example, the same as the warning display described in FIG. 16(a), but may be different. The timing of the warning notification may be, for example, when the memory card 45 is inserted into the drive recorder 1, when the drive recorder 1 is started, or when recording in the drive recorder 1 starts (for example, at least one of immediately before recording starts, at recording starts, and immediately after recording starts; the same applies below), which is expected to make the user more aware of the warning. The warning notification may be given at another time, such as during recording.

[0186] In this way, according to the first method, for example, a warning can be given when the user mistakenly inserts a memory card 45 such as a non-compatible SD card (for example, an SD card with a slow writing speed).

[0187] (Second method: Measuring the amount of busy times) The second method is a method that allows a warning to be issued if the actual write capacity of memory card 45 is below a predetermined write capacity, even if the SD card used as memory card 45 is defective (for example, if it is a counterfeit, or if a dishonest manufacturer has falsified the speed in the CSD register). For example, if the write capacity information is false, the write capacity indicated by the write capacity information will not match the actual write capacity of memory card 45, and will differ from the write capacity stated on the packaging (packaging) that packs memory card 45 or in the instruction manual, for example.

[0188] In the second method, the detection function of the controller 30 detects the amount of busy (BUSY) occurrences as the write capability, as described in the first embodiment above. Below, as a specific embodiment, a method will be described in which the controller 30 constantly measures (detects) busy time as an index of the amount of busy occurrences in the memory card 45. Here, "constant measurement" refers to measuring busy time at predetermined time intervals during the period from when the drive recorder 1 is powered on to when it is powered off, or during recording. Generally, in the case of a memory card 45 (SD card) with poor performance, the occurrence of busy time on the memory card 45 (SD card) side will result in a decrease in data transfer speed.

[0189] As shown in the example in Figure 13, when observing the bus waveform during data write, data normally flows continuously. However, if a certain amount of data is sent to the SD card, bus access stops at certain points toward the end of the write. The SD card has a buffer that temporarily stores the data to be written. As long as the buffer does not overflow, data is accepted from the host (e.g., drive recorder 1). However, if the NAND writing in the SD card is slow, the transfer from the buffer to the NAND cannot keep up. When the buffer becomes full, the SD card notifies the host (e.g., drive recorder 1) of a busy state and is unable to accept any more data. Therefore, an increase in busy states indicates a decrease in the SD card's write speed. For example, as the SD card deteriorates, damaged sectors in the NAND memory can cause writes to slow down, overflowing the buffer and causing a busy state. If data writing to the SD card slows down or is unable to be written, the busy time (the amount of busy state) increases. Note that even during the busy periods shown in Figure 13, the busy state may actually end momentarily. This is thought to be because some SD card standards are designed so that the busy state lasts for, for example, several tens of milliseconds or less. It is preferable that the controller 30 not determine that the busy state has been resolved when the busy state is resolved only momentarily. This allows the controller 30 to detect the write capability based on the actual busy time.

[0190] Also, due to differences in performance among memory cards 45, high-performance cards are less likely to enter a busy state even when transferring large amounts of data for a long period of time. Low-performance cards enter a busy state immediately. Some cards also take a long time to clear the busy state. Furthermore, if the card deteriorates after prolonged use, symptoms such as the time until the busy state occurs gradually becoming shorter, the busy state occurring immediately, or the busy state taking a long time to clear may appear.

[0191] The host (drive recorder 1, etc.) also has a buffer that temporarily stores data to be written to the memory card 45, and no problem occurs as long as the busy time is within a predetermined time. However, if the busy time exceeds the predetermined time and the amount of data to be written exceeds the capacity of the buffer, the recorded video cannot be written, so the controller 30 should display a warning (for example, a warning pop-up (for example, a warning about an error in the memory card 45)) and stop video recording. The warning in the second method is, for example, the same as the warning display described in Figure 16(a), but may be different. The timing of the warning notification should be, for example, during recording.

[0192] When transferring video (captured data) recorded on the host (drive recorder 1, etc.) side to memory card 45, controller 30 divides the data into certain fixed data segments and records the data while measuring how long it takes to write the data to the SD card. This allows controller 30 to estimate how busy the memory card 45 is and determine the performance and degree of deterioration of memory card 45. However, since it is necessary to make this determination while recording, it is advisable for CPU 31 of controller 30 to have the capability to do so.

[0193] The controller 30 may combine the first and second methods, and if there is a discrepancy between the results obtained by the first method and the results obtained by the second method, issue a warning indicating that the SD card being used is counterfeit. In particular, the controller 30 may issue a warning indicating the possibility of a counterfeit, such as a message stating, "This card may be counterfeit." For example, if the memory card 45 meets the specifications required by the drive recorder 1 used and does not meet the conditions for issuing a warning in the first method, but the second method meets the conditions for issuing a warning based on the number of busy periods, the controller 30 may issue a warning indicating that the write capability information stored in the memory card 45 may be counterfeit. Similar processing may also be performed by combining the first method with the third to sixth methods described below.

[0194] (Third method: Reading the buffer on the host side (drive recorder 1, etc.)) The third method is also a method that can issue a warning if the writing capacity of memory card 45 is below a predetermined writing capacity, even if the SD card used as memory card 45 is defective (for example, if it is a counterfeit, or if a dishonest manufacturer has falsified the speed in the CSD register). The third method is a method that detects the buffer usage status on the host (drive recorder 1, etc.) side as the writing capacity.

[0195] As described in the second method, the drive recorder 1 includes a buffer that temporarily stores data to be transferred to the memory card 45. In the third method, the detection function of the controller 30 monitors the usage status of the buffer in the controller 30's memory and issues a warning based on the buffer usage status. The buffer usage status may be measured by the extent to which the buffer is being used. If the buffer usage status is measured by the buffer usage rate, the controller 30 may issue a warning when the buffer usage rate exceeds a predetermined value (threshold value) or when the writing capacity of the memory card 45 is below the predetermined writing capacity. The warning may be issued by displaying the warning as described in FIG. 16(a), but may be issued in a different manner. For example, the controller 30 may issue a warning to the user that includes a message saying "The SD card is degraded" (for example, by displaying a warning pop-up). The warning may be issued, for example, during recording. Alternatively, the warning may be issued at another timing.

[0196] The controller 30 may also display the buffer usage status on the display 12. For example, the controller 30 may display the buffer usage rate as a percentage or a bar graph. For example, the controller 30 may display the buffer usage status together with the video captured by the drive recorder 1, superimposed on the video, on a single screen.

[0197] This third method can be implemented more easily than the second method because it is sufficient to monitor the buffer of the controller 30 itself.

[0198] (Fourth method: written test) The fourth method is a method of detecting the write capability by performing a speed test on the memory card 45 at startup or when recording starts (here, before recording starts (before recording)). Thus, detecting the write capability by the fourth method is an example of detecting the write capability performed at startup of the drive recorder 1 described above. In the second and third methods, some kind of determination must be made simultaneously while recording. Therefore, the controller 30 measures the data write speed as a speed test of the memory card 45 at startup.

[0199] Specifically, the controller 30 performs operations as shown in the flowchart in Fig. 14. The controller 30 starts the flowchart in Fig. 14, for example, when the drive recorder is powered on. If the drive recorder 1 is equipped with an electric double layer capacitor (sometimes called a supercapacitor), the controller 30 starts the flowchart in Fig. 14 after the electric double layer capacitor has completed charging. The electric double layer capacitor is an example of a power storage means of the drive recorder 1. By storing electricity in the electric double layer capacitor, for example, even if the power supply to the drive recorder 1 is unexpectedly cut off, the controller 30 can perform the minimum processing necessary to prevent operational problems such as file corruption.

[0200] 14, the controller 30 determines whether or not a write test result file, which will be described later, exists. In the case of a new memory card 45 or the like, the write test result file does not exist, the determination result is false (No), and the controller 30 proceeds to step S12.

[0201] In step S12, the controller 30 performs a write test (also referred to as an SD write test in this embodiment) on the memory card 45. The specific method of the write test is not particularly limited, but for example, the controller 30 writes approximately 100 MB of random data and measures the time required for this. During the write test, the controller 30 may display a message indicating that the SD write test is being performed, such as "SD card speed, write speed test in progress." In this way, the detection of the write capability in this embodiment is achieved by measuring the time required to write predetermined data to the memory card 45 through the write test.

[0202] In the next step S13, the controller 30 determines whether the write test performed in step S12 is successful. For example, if the time required for the write test is less than a predetermined time, the write test is successful, and the controller 30 proceeds to step S14.

[0203] In step S14, the controller 30 records the total recording file counter value, the recording file counter value from the previous writing test to the present, and the fact that the writing test result is a pass in the writing test result file, and proceeds to the next step S17. The total recording file counter value may indicate the total number of recording files recorded to the memory card 45 on which the writing test was performed. The writing test result file is a file in which the results of the writing test are written as data and is an example of writing test result information. The writing test result file is, for example, a text file. Note that the information written in the writing test result file is not limited to this, and other information may be written. The writing test result file is not limited to a text file and may be a .dat file. The writing test result file preferably contains data that is not easily viewable by users, data that cannot be tampered with, and data that is stored in an area that is not erased by a quick format.

[0204] On the other hand, if the time taken for the write test is equal to or longer than the predetermined time in step S13, the write test is deemed to have failed, and the controller 30 proceeds to step S15. Causes of the write test taking longer than the predetermined time include the occurrence of a busy state as described above, an increase in the buffer usage rate, etc.

[0205] In step S15, the total recorded file counter value, the counter value from the previous write test to the present, and the fact that the write test result is a failure are entered in the write test result file, and the process proceeds to the next step S16.

[0206] In step S16, since the result of the write test was a failure, the controller 30 may issue a warning to the effect that the write capability of the memory card 45 is below a predetermined write capability. The warning may be issued by displaying the warning as described in FIG. 16(a), but may be issued in a different manner. The controller 30 may issue a warning (for example, by displaying a warning pop-up) that "recording may fail due to a faulty card," and then proceed to step S17.

[0207] In step S17, the controller 30 starts recording in the drive recorder 1 as a normal operation (for example, recording in the continuous recording mode).

[0208] In the next step S18, when creating the next recording file, the controller 30 increments the value of the file counter (specifically, the total recording file counter and the counter from the previous SD writing test to the present) in the write test result file by 1, and then ends the routine. Recording files (for example, video data recorded continuously) are created at predetermined intervals, and the file counter value is incremented (by 1) each time a recording file is created.

[0209] In step S11, if the write test has already been performed in step S12 and a write test result file exists in the memory card 45, the determination result becomes true (Yes), and the controller 30 proceeds to step S19.

[0210] In step S19, the controller 30 determines whether the recording time since the previous write test is equal to or greater than a threshold value, for example, based on the value of the file counter in the write test result file. For example, it determines whether the value counted by the counter since the previous write test is equal to or greater than 6,000 (equivalent to 100 hours if one recording file is one minute long). If the determination result is true (Yes), that is, if the time since the previous write test is equal to or greater than the threshold value (a predetermined time), the controller 30 proceeds to step S12 and performs a new write test. On the other hand, if the determination result is false (No), that is, if the time since the previous write test is less than the threshold value (less than the predetermined time), the controller 30 proceeds to step S20. In other words, if not much time has passed since the previous write test, the controller 30 proceeds to step S20 without performing a write test.

[0211] In step S20, the controller 30 determines whether or not there is a problem with the contents of the write test result file. For example, if the result of the write test of the write test result file is a failure, the controller 30 determines that there is a problem with the contents of the write test result file, and proceeds to step S16 to issue a warning notice. In other words, while the result of the write test is a failure, a warning notice is displayed every time the drive recorder 1 is turned on and started up. On the other hand, if the result of the write test is a pass, the determination result becomes true (Yes), and the controller 30 proceeds to step S17 to start recording.

[0212] As described above, the controller 30 performs the write test when the drive recorder 1 is started or when recording in the drive recorder 1 is started, and issues a warning. This is expected to have the effect of making the user more aware of the warning. The timing of the warning notification may be different. For example, the controller 30 may perform the write test when the drive recorder 1 is powered on but not recording. When an instruction to turn off the power of the drive recorder 1 is received, the controller 30 may perform the write test and then turn off the power.

[0213] As described above, the fourth method reduces the processing load on the controller 30 and unnecessary CPU resource consumption during recording. When the memory card 45 is first used with the drive recorder 1 or when the drive recorder 1 is next powered on after a certain period of time (e.g., 100 hours) has elapsed since recording began, a write test of several seconds is required. However, the controller 30 does not perform a write test until the recording time since the previous write test in the write test result file has not exceeded the certain period of time. This reduces frequent write tests and the resource consumption of the CPU 31. Furthermore, since a write test is not performed every time recording using the recording function is started, inconveniences such as a long wait time between turning on the drive recorder 1 and starting recording can be avoided. Because the write capability of the memory card 45 may gradually decrease due to deterioration, there are few practical problems even if a write test is not performed every time recording using the recording function is started.

[0214] (5th method: Error history) A write error may occur in the memory card 45 while the controller 30 is continuing to write recording data to the memory card 45. In the case of such a write error in the memory card 45, it may become possible to write recording data again by removing and inserting (unmounting / mounting) the memory card 45.

[0215] Therefore, the fifth method is to unmount and then mount the memory card 45 when it is detected that a write error has occurred in the memory card 45. The following describes a case where the controller 30 detects a write error based on receiving (obtaining) error information from the memory card 45.

[0216] Specifically, as an example of a method for dealing with receiving error information from memory card 45 shown in Figure 15, when the controller 30 receives error information from memory card 45 for the first time while recording (e.g., in continuous recording mode) for a long period of time after powering on the drive recorder 1, the controller 30 executes a first error process.

[0217] As one of the first error processes, the controller 30 may issue a warning that the writing capacity of the memory card 45 is below a predetermined writing capacity. The warning in the first error process is an example of a first warning, and may be the same as the warning display described in FIG. 16(a), for example, but may be different. The controller 30 may, for example, display a slow pop-up on the display 12 to notify the user that the slow writing speed may cause problems in recording. The slow pop-up may, for example, display a message such as "Recording may fail due to slow SD card speed," as shown in the specific example of the warning display in FIG. 16(a).

[0218] As one of the first error processes, the controller 30 may emit an error sound from the speaker 40 to draw the user's attention.

[0219] As one of the first error handling methods, the controller 30 may temporarily suspend recording.

[0220] As one first error processing method, the controller 30 temporarily suspends recording, then unmounts the memory card 45 from the memory card reader 44 using, for example, an SD card reset command, and then mounts it (hereinafter referred to as the unmount / mount processing). In other words, the controller 30 performs a process of logically removing and inserting the SD card into the memory card reader 44, rather than physically. By mounting the memory card 45, the controller 30 recognizes the memory card 45 and makes it possible to resume recording using this memory card 45. The controller 30 may, for example, perform the unmount / mount processing while issuing a warning notification in the first error processing, and stop issuing the warning notification when the unmount / mount processing is completed. This makes it easier for the user to understand why recording was paused.

[0221] As one of the first error processes, the controller 30 creates an error history file on the SD card that lists the date and time when recording was paused. For example, the controller 30 creates the error history file as a text file such as "SD_Error.txt" at the top level of the storage area of ​​the memory card 45. The error history file records the date and time when recording pause started and the date and time when the pause was released (i.e., recording resumed), such as "REC NG: 2021 / 01 / 22 13:10:10 to 2021 / 01 / 22 13:10:13."

[0222] When the error in the memory card 45 is resolved by unmounting / mounting the memory card 45, the controller 30 resumes recording.

[0223] Then, when error information is received from the memory card 45 again after the recording is resumed, the first error process is executed for the second time.

[0224] The controller 30 may perform the second first error processing in the same manner as the first first error processing described above. When updating the error history file during the first error processing, the controller 30 adds the date and time when the pause was released (i.e., recording resumed) to the date and time when the second recording pause was started, for example, like this: "REC NG: 2021 / 01 / 22 14:10:10 to 2021 / 01 / 22 14:10:13".

[0225] When the error in the memory card 45 is resolved by unmounting / mounting the memory card 45, the controller 30 resumes recording.

[0226] When the controller 30 receives error information from the memory card 45 a predetermined number of times, it performs second error processing, which includes processing to end recording. It is preferable to perform processing similar to the first error processing each time error information is received from the memory card 45 until the predetermined number of times is reached. This predetermined number can be set arbitrarily, for example. In this embodiment, the predetermined number is set to five times, but it is preferable to set it to at least two times. The controller 30 performs second error processing only when it receives error information from the memory card 45 for the fifth time since the power was turned on or recording started.

[0227] As one of the second error handling procedures, the controller 30 ends (stops) the recording.

[0228] As one of the second error processes, the controller 30 issues a warning indicating a write error. The warning indicating an error is an example of a second warning, and may be issued by displaying the warning described in FIG. 16(b), but may be issued in a different manner. For example, the controller 30 displays a warning (e.g., an error pop-up) on the display 12 to notify the user that an error has occurred in the memory card 45. The error pop-up display may display a message such as "SD card error" as shown in FIG. 16(b), for example.

[0229] As one of the second error processes, the controller 30 emits an error sound from the speaker 40 to draw the user's attention.

[0230] As one of the second error processes, the controller 30 updates the error history file. For example, the error history file is updated by recording (adding) the date and time when recording ended, such as "REC NG: 2021 / 01 / 22 17:10:10" in the error history file.

[0231] In this way, in the fifth method, when the controller 30 detects a write error to the memory card 45, it does not immediately end the recording, but pauses it and performs an unmount / mount process on the memory card 45, thereby allowing the recording to continue.

[0232] Furthermore, by recording the date and time when recording was paused or stopped in the error history file, the user or service person can later check the error trends of the memory card 45. The information written in the error history file may be the number of times (counter) that recording was paused or stopped. The information written in the error history file is not limited to this, and other information may be written. The error history file is not limited to a text file, and may be a dat file. It is preferable that the error history file contains data that cannot be easily viewed by the user, data that cannot be tampered with, and data that is stored in an area that will not be erased by a quick format.

[0233] When the drive recorder 1 is started (restarted) or recording starts, if an error history file remains on the memory card 45, the controller 30 may display the contents of the error history file on the display 12. The controller 30 may display, for example, "This card has stopped due to a write error during previous writing," "The error occurred on x month x day at x hour x minute...," or "This card may not have been able to finish writing in time during previous writing," etc. By displaying such a message upon restart, the controller 30 can once again alert the user.

[0234] One possible cause of a write error to the memory card 45 is that, when data is continuously written to the memory card 45, the microcontroller (e.g., firmware control) in the memory card 45 does not have time to perform internal processing to properly use the memory (e.g., flash memory) in the memory card 45. Therefore, when turning off the power to the drive recorder 1, the controller 30 may unmount the memory card 45 and leave it for a predetermined period of time before turning off the power. This may be done using a battery dedicated to the drive recorder 1, regardless of whether or not the drive recorder 1 switches to the parking storage function (also called the parking monitoring function) described above.

[0235] (6th method: Number of pins on memory card 45) The detection function of the controller 30 is not limited to checking the write capability information stored in the memory card 45. It may also detect the actual write capability of the memory card 45 based on the pins possessed by the memory card 45. In this case, if a required pin is unavailable, the controller 30 may notify the user that the memory card 45 is an incompatible card and the required pin is unavailable. For example, if a UHS-I SD card with fewer pins is inserted into the drive recorder 1, even though the drive recorder 1 is UHS-II compatible, the controller 30 may issue a warning indicating a physical problem with the SD card, such as "Please use UHS-II," "Not compatible with UHS-I," or "SD card hardware is not compatible." The controller 30 may also display a warning message using an image of a specific standard, such as "SD cards with a *mark A cannot be used. Please use an SD card with a *mark B." It is preferable that a predetermined mark, such as an example of an image indicating an NG standard, be displayed in the position of "*mark A," and a predetermined mark, such as an example of an image indicating an OK standard, be displayed in the position of "*mark B." It should be noted that the notification of the warning may be configured in the same manner as described in the first method, for example.

[0236] (warning display) According to the first to sixth methods described above, when a malfunction or the like of the SD card is detected, the notification function of warning the user, such as a warning display or an error sound, is not limited to the above.

[0237] For example, the controller 30 may use a notification function in which the display (e.g., a warning display) or the audible alert (e.g., an error sound) is divided into three or more levels instead of just two levels, normal and abnormal. For example, if a four-level display or audible alert is used, the first level indicates a normal state with no problems. The second level indicates a display or audible alert that an abnormality will soon occur in the memory card 45 (SD card) (e.g., urging the user to prepare for a replacement SD card). The third level indicates a display or audible alert that the memory card 45 (SD card) should be replaced (e.g., it is not surprising that the card may break at any time, urging the user to replace the card). The fourth level indicates a display or audible alert that an abnormality has occurred in the memory card 45 (SD card) (no more recording is possible, replace the card immediately). The second and third level notifications are examples of warning notifications urging the user to replace the memory card 45. However, the recording function can still record video to the memory card 45 even when the second or third level notification is issued.

[0238] For example, the controller 30 may display an icon indicating that a memory card 45 is inserted in the drive recorder 1 in three or more color levels. For example, if the icon has four color levels, the first level is a blue icon indicating a normal state with no problems. The second level is a light blue icon indicating that an abnormality will soon occur in the memory card 45 (e.g., urging the user to prepare to replace the memory card 45). The third level is a yellow icon indicating that the memory card 45 should be replaced (it is not surprising that the card may break at any time, urging the user to replace it). The fourth level is a red icon indicating that an abnormality has occurred in the memory card 45 (no more recording is possible, replace it immediately). In this case, the second and third level notifications are also examples of warning notifications urging the user to replace the memory card 45. Furthermore, the recording function is still capable of recording video to the memory card 45 even when the second or third level notification is issued.

[0239] In this way, by displaying the warning notification in three or more stages, the controller 30 can notify the user of a variety of information according to the writing capacity, thereby informing the user of the status of the memory card 45 in more detail. Furthermore, in addition to, for example, notifying that the memory card 45 is normal or that the storage medium is malfunctioning or deteriorating, the controller 30 can also notify the user of information such as that the storage medium is capable of recording video but urging the user to replace the storage medium, as described above. Therefore, by knowing in advance that there is a problem with the memory card 45, the user can prepare in advance for replacing the SD card, thereby reducing the possibility of video recording failure and improving convenience.

[0240] The controller 30 may separately notify whether the installed memory card 45 is broken (faulty) or simply unusable (slow) for recording in the drive recorder 1 being used. The controller 30 may determine whether the memory card 45 is broken (fault determination) by writing and reading data at a low speed in compatibility mode. For example, the controller 30 may determine that the memory card 45 is not faulty if it can be written in compatibility mode. Alternatively, as another determination method, the controller 30 may determine that the memory card 45 is not faulty if it can be written at a speed slower than the speed at which video is recorded.

[0241] For example, the controller 30 may write and read data at a rate equal to or slightly higher than the maximum recording speed of the drive recorder 1 used in UHS mode, and make a judgment based on the read and write speed, or may make a judgment using the same method as the write test described above. Specifically, if the memory card 45 is broken, the controller 30 may display a message on the display 12 saying, "This SD card is broken." If the memory card 45 is not broken but cannot be used with the drive recorder 1 (for example, if the write speed is slow), the controller 30 may notify the user that the memory card 45 is not broken, that the drive recorder 1 uses high-quality recording, and that the memory card 45 cannot be used with the drive recorder 1, such as, "This card is not broken, but cannot be used with this drive recorder because this drive recorder records in high quality."

[0242] As described above, warning notifications regarding the memory card 45 include a warning notification indicating that the write capacity is within a predetermined range, notifications regarding writing to the memory card 45 such as when the memory card 45 is busy or the buffer is insufficient, notifications regarding malfunctions such as errors in the memory card 45, and notifications regarding hardware defects in the memory card 45. The notification function described above may also be configured to allow arbitrary setting of notification conditions, such as a combination of conditions under which a warning is issued. For example, a setting may be made such that warnings are permitted for the first and second methods but not for the third through sixth methods. The controller 30 may, for example, display each method and a checkbox next to each other on a setting screen, execute all checked methods, and not execute unchecked methods.

[0243] To solve the problem of the user forgetting to buy a new memory card even after being notified to do so, the controller 30 may notify (notify) the user to replace the memory card 45 when the user gets out of the car or is about to get out. Specifically, the notification may be given at least one of the following times: when the vehicle engine is turned off, when the drive recorder 1 enters a mode in which it operates with the parking storage function, or when the vehicle approaches a POI (such as an auto parts store) that sells memory cards 45.

[0244] (Automatic ordering when memory card 45 is abnormal) If the drive recorder 1 is capable of communicating with the outside, when an abnormality in the memory card 45 is found by the above-described method, the controller 30 may take action to have the memory card 45 replaced externally.

[0245] For example, if the memory card 45 experiences a third or fourth level abnormality, the controller 30 may use a communication means to transmit information about the abnormality in the memory card 45 to, for example, an external management center, and the management center may take action such as arranging for a replacement memory card 45 for the user. This management center may be, for example, a service provider that receives and stores data recorded in a drive recorder, and arranging for the memory card 45 may be part of the service. The notification of the abnormality in the SD card to the management center is easy to understand using the three or more levels described above, but may also be expressed as a quantitative number, for example. In this way, convenience can be improved.

[0246] (Smartphone connectivity) If the drive recorder 1 can be linked with an external information terminal such as a smartphone or a PC (personal computer), the controller 30 may perform an action linked with the external information terminal when a notification regarding the memory card 45 is required by the above-described method. Communication means for linking with an external information terminal include, for example, wireless LAN, a mobile phone line, Bluetooth (registered trademark), etc.

[0247] For example, if the memory card 45 experiences a third or fourth stage abnormality, the controller 30 displays a warning on the display of the linked information terminal, emits an alarm, or displays an icon, thereby improving convenience.

[0248] Furthermore, when the memory card 45 is about to break or has broken, the controller 30 may record on an external information terminal such as a smartphone, or may notify the user to set the external information terminal to record. Whether or not a malfunction of the memory card 45 has occurred, such as when the memory card 45 is about to break or has broken, may be determined based on, for example, whether the write capacity has fallen below a predetermined level, whether a write error has occurred, or whether a predetermined number of write errors have occurred, as described above. However, other methods may also be used. When a malfunction of the memory card 45 occurs, the controller 30 may transfer only the recorded data, for example, in the event recording mode, to an external information terminal (e.g., a smartphone). The external information terminal may later transfer information, such as the stored recorded data, to the drive recorder 1, which has switched to a normal memory card 45.

[0249] A storage area may be provided inside the drive recorder 1 in addition to the memory card 45, and when the SD card is about to break or has broken, data may be recorded in this storage area inside the drive recorder 1. In this case, continuous recording is not performed, and the controller 30 may perform event recording in event recording mode. When it detects that the memory card 45 has been replaced with a normal one, the controller 30 may inquire of the user as to whether to move the internally stored event-recorded video data to the memory card 45, or may automatically transfer the data to the memory card 45. A function for externally retrieving the internally recorded data via communication may also be provided.

[0250] The controller 30 may also have a function for displaying a speed graph of the memory card 45. In other words, it visualizes the speed of the memory card 45. The controller 30 may also be a drive recorder that displays, for example, the number of frames that could not be written within a unit time in a bar graph in chronological order.

[0251] A busy time detection circuit may also be provided in the drive recorder 1. A separate circuit may be provided to detect the busy time (one example of the amount of busy time) when writing to the memory card 45, and the controller 30 may issue an alert (notification) if the busy time exceeds a predetermined amount a predetermined number of times. Alternatively, the controller 30 may be a drive recorder that visualizes this state.

[0252] [Fifth embodiment] Next, a fifth embodiment of the present invention will be described. Of the configuration and functions of the drive recorder 1 of this embodiment, those that are common to the other embodiments will not be described.

[0253] In the above-described fourth embodiment, it has been described that the controller 30 records data in a storage area inside the drive recorder 1, for example, performs event recording in the event recording mode using the storage area inside the drive recorder 1. The drive recorder 1 of this embodiment has a recording function using this configuration to reduce the probability of recording failure triggered by an impact occurring to the vehicle 100.

[0254] In a drive recorder, when an impact is detected and an event is recorded, a problem may occur in which the event is not recorded at the time of the event (hereinafter referred to as an "impact event"). Possible causes of this problem include an SD card (an example of a memory card 45) that has not been formatted for a long time and is therefore unable to be written to, the power being disconnected, or the SD card contacts being momentarily disconnected, causing a write failure. However, the causes are sometimes unclear. Since the causes of such failures are sometimes unclear, the inventors felt that measures should be taken to reduce the probability of recording failure.

[0255] Therefore, as shown in FIG. 17, in addition to the configuration described in the first embodiment, the drive recorder 1 includes an eMMC 46 as an internal storage device that provides an internal storage area. When an impact event occurs with an impact of a predetermined magnitude or greater (e.g., a very large impact), the controller 30 (recording function) records data (such as video data) in the eMMC 46. The controller 30 may record data for all impact events in the eMMC 46. However, for example, for an impact event with an extremely large impact greater than a threshold, the controller 30 may record data in the eMMC 46, and for an impact event with a smaller impact, the controller 30 may record data in the memory card 45. In this way, the controller 30 may perform recording using the eMMC 46 at least when an impact of a predetermined magnitude or greater occurs. Furthermore, instead of storing a program in a NAND memory (e.g., SLC NAND), the program may be stored in the eMMC 46.

[0256] Although the controller 30 may write data to the eMMC 46 simultaneously with writing data to the memory card 45, this may be difficult. Therefore, when an impact event occurs, the controller 30 performs event recording, recording data to the eMMC 46. The controller 30 may then write data from the eMMC 46 to the memory card 45 at a predetermined timing after the event recording, such as the next time the drive recorder 1 is started, when the memory card 45 is inserted into the memory card reader 44. Note that, in this embodiment, the storage device providing the internal storage area of ​​the drive recorder 1 has been described as the eMMC 46, but other types of storage devices may also be used, for example, a flash memory such as an SSD, or other storage devices.

[0257] Furthermore, the controller 30 may back up the protected data to a predetermined backup storage (a storage device for backup), not shown. In this way, even if the drive recorder 1 main body is powered off and damaged, the data can be retrieved from the predetermined backup storage later. This is because some users of the drive recorder 1 consider this kind of peace of mind to be important, even if it increases costs.

[0258] According to this embodiment, the probability of a recording failure triggered by an impact occurring to the vehicle 100 can be reduced, and a highly convenient drive recorder 1 is provided.

[0259] [Sixth embodiment] Next, a sixth embodiment of the present invention will be described. Of the configuration and functions of the drive recorder 1 of this embodiment, those that are common to the other embodiments will not be described.

[0260] The drive recorder 1 may be provided with a function supporting a recording backup option (an example of a backup function). To achieve this, the drive recorder 1 and external battery of this embodiment may be the drive recorder 1 and external battery 50 shown in FIG. 18. In addition to the configuration described in the first embodiment, the drive recorder 1 has a terminal 47. The terminal 47 is a terminal for electrically connecting to an external device. The terminal 47 is a terminal for transmitting and receiving signals to and from the external device and for receiving power from the external device. The terminal 47 is connected to the external battery 50.

[0261] The external battery 50 is a battery device external to the drive recorder 1. The external battery 50 includes a converter 51, a battery unit 52, a first terminal 53, a second terminal 54, and a controller 55. The converter 51 is a DC / DC converter that converts 12V DC (direct current) power from an accessory power supply or the battery unit 52 into 5V DC. The battery unit 52 includes a battery (battery pack) that stores power internally. The battery unit 52 may be charged based on power supplied from the accessory power supply. The first terminal 53 is a terminal to which a cable for connecting to the drive recorder 1 is connected. The second terminal 54 is a terminal to which a cable for connecting to a storage 60, which is an external storage device of the drive recorder 1, is connected. The first terminal 53 and the second terminal 54 may each have pins for connecting to a signal line for signal transmission and a power line for power supply.

[0262] The standards of the terminal 47, the first terminal 53, and the second terminal 54 are not particularly limited, but may correspond to the 10-pin mini USB standard, for example. In this embodiment, the storage 60 is a USB-connected storage, such as a device connected via USB mass storage (for example, a large-capacity 2.5-inch SSD / HDD / SD card). The storage 60 may be stored in, for example, a glove box of the vehicle 100. The storage 60 needs to be able to connect a USB data line to the external battery 50 (I / F unit). Therefore, the second terminal 54 may be, for example, a USB Type A receptacle provided on the external battery 50, so that it can be connected to the storage 60.

[0263] The controller 55 has, for example, a microcomputer, and corresponds to a control unit that controls each part of the external battery 50. For example, the controller 55 controls the supply of power to the drive recorder 1 and the storage 60, and controls communication with the drive recorder 1 and the storage 60. As described in the first embodiment, the controller 55 supplies the drive recorder 1 with the power required to realize the parking storage function, and also controls the implementation of the backup function.

[0264] The controller 55 supplies power to the drive recorder 1 based on the accessory power supply while the accessory power supply is ON. The controller 55 does not supply power to the storage 60 while the accessory power supply is ON. When the accessory power supply is turned OFF, backup of data recorded by the drive recorder 1 begins. Specifically, when the accessory power supply is turned OFF and power supply from the vehicle 100 stops, the controller 55 uses power from the battery unit 52 to supply power to the drive recorder 1 via the first terminal 53 and to the storage 60 via the second terminal 54. The drive recorder 1 (controller 30) also functions as a USB host. When the USB host recognizes the storage 60 through power supply, it backs up data stored in the memory card 45 to the storage 60 (differential backup in this embodiment). The controller 55 receives data supplied from the drive recorder 1 via the terminal 47 and the first terminal 53. When data to be backed up is supplied, the data is supplied to the storage 60 via the second terminal 54 and stored therein. The controller 30 may copy only the event recording data, or may copy all the data, and various modifications are possible regarding the data to be backed up. For example, the controller 30 may copy all the data and then format the memory card 45 (i.e., erase the event recording data from the memory card 45), or may leave the data as is in a duplicated form on the memory card 45 and the storage 60 without formatting. The user may be able to set in the drive recorder 1 how the data to be backed up is to be backed up.

[0265] If you try to back up data while the accessory power is on (for example, while recording), it may be difficult due to the use of memory card 45 and the problem of vibration in storage 60. However, according to this embodiment, backups can be performed at least during the period when the accessory power is off, such as at night.

[0266] For example, it is conceivable that SD cards that can be used as memory card 45 will have larger capacities in the future. However, rather than relying on the widespread use of expensive, large-capacity MLC or 3D TLC cards, the configuration of this embodiment is likely to offer users greater price benefits per capacity. For example, a USB memory-type SSD / HDD / SD card (and a card reader) that can be used as storage 60 is easier for users to carry around. According to this embodiment, the user is less likely to remove memory card 45 from drive recorder 1, which is expected to reduce accidents such as memory card 45 flying out when trying to remove it from drive recorder 1, dropping it into an air conditioner duct, or going missing.

[0267] The controller 30 may execute the backup without any explicit instruction from the user (i.e., automatically), but may also stop recording in response to a user operation while the vehicle 100 is stopped, and execute the backup in response to the user operation (i.e., manually). When the accessory power of the vehicle 100 is turned off, the controller 30 may simultaneously start and execute the backup and recording using the parking memory function, but if simultaneous execution is difficult, the controller 30 may start recording using the parking memory function after the backup has finished.

[0268] The controller 30 may copy data from the memory card 45 to a storage device attached to the SD card reader when the second terminal 54 is connected (for example, via USB connection). In preparation for this case, the drive recorder 1 may have a function that allows the user to set not to copy unnecessary files or to set the data to be copied.

[0269] The controller 30 may vary the backup operation depending on the storage 60. For example, the controller 30 may perform a differential backup if the storage 60 is an SSD, and may perform a full backup if the storage 60 is an SD card. The controller 30 may vary the backup operation depending on the capacity of the storage 60.

[0270] For example, in the event of an accident, the user may not want to hand over the memory card 45 itself, but may be willing to hand over the backup data. To prepare for such a case, the controller 30 may have a function for playing back video data backed up in the storage 60. The controller 30 may display a playback menu on the display 12 and play back the backed up video data via the corresponding playback menu.

[0271] For example, if 32 GB of data is recorded during one drive and backed up at a speed of 20 MB / s, it would take 1638 seconds, or approximately 27 minutes. Therefore, to protect the data in the drive recorder 1, the controller 30 may have a function to interrupt the backup after a certain period of time (a predetermined period of time). The maximum period of time is determined by the operating time of the accessory power supply.

[0272] According to this embodiment, a backup can be performed to protect the data in the drive recorder 1, and a highly convenient drive recorder 1 and external battery 50 are provided.

[0273] [Seventh embodiment] Next, a seventh embodiment of the present invention will be described. Of the configuration and functions of the drive recorder 1 of this embodiment, those that are common to the other embodiments will not be described.

[0274] Some drive recorders include a supercapacitor (electric double layer capacitor) as a power storage means, as explained in the fourth embodiment above, but there is a problem that the supercapacitor becomes unusable due to temperature and aging degradation. Therefore, a configuration in which the supercapacitor is externally attached to the outside of the drive recorder 1 may be adopted. The supercapacitor may be externally attached instead of being internally attached to the drive recorder 1 (front camera main body), or may be externally attached in addition to being internally attached to the drive recorder 1.

[0275] The drive recorder 1 and the external battery 50 of this embodiment may have the configuration shown in FIG. 19 . The external battery 50 includes a supercapacitor 56 in addition to the configuration described in FIG. 18 . The use and function of the supercapacitor 56 may be the same as those of the supercapacitor described in the fourth embodiment. The supercapacitor 56 is connected to an accessory power supply. The controller 55 notifies the drive recorder 1 via the first terminal 53 (e.g., UART communication or a pin) that recording can be started when charging of the supercapacitor 56 is complete and that recording will stop when the accessory power supply is turned off. In the drive recorder 1, when the controller 30 receives a notification from the external battery 50 via the terminal 47, it starts or stops recording based on the notification. In addition, the controller 55 supplies power to the drive recorder 1 based on the power stored in the supercapacitor 56. When power supply from the accessory power supply to the drive recorder 1 is stopped, the drive recorder 1 performs limited predetermined processing, such as closing a file, based on the power from the supercapacitor 56. If the supercapacitor 56 completes charging at an abnormal rate after the accessory power is turned on, the controller 55 determines that the performance has deteriorated and notifies the drive recorder 1 that an abnormality has occurred in the supercapacitor 56. Based on this notification, the controller 30 in the drive recorder 1 may notify the user that the external battery 50 (supercapacitor) needs to be replaced and prompt the user to replace it. The notification to the user may be made by a method that can be perceived by humans, such as a display on the display 12, a sound, or an LED light. The notification to the user may also be made by a method other than via the drive recorder 1, such as via the smartphone described above.

[0276] Because the supercapacitor 56 is integrated with the external battery 50 along with the converter 51, the user does not need to disassemble the supercapacitor 56 to replace it. This allows the user to easily replace the supercapacitor 56 when it deteriorates. While it is conceivable to configure the supercapacitor 56 to be detachable (for example, as a cassette type), it is more advantageous to have the supercapacitor 56 built into and integrated with the external battery 50 in consideration of contact issues and safety. Furthermore, because the supercapacitor 56 is externally disposed from the main body of the drive recorder 1, the effect of slimming down the main body of the drive recorder 1 can also be expected. While the present embodiment describes a case in which the supercapacitor 56 is integrated with the external battery 50, the supercapacitor 56 may be integrated with another device connected to the drive recorder 1, or may be a dedicated device equivalent to the supercapacitor 56, as long as it is an external device to the drive recorder 1.

[0277] According to this embodiment, a highly convenient drive recorder 1 and external battery 50 are provided, in which the supercapacitor can be easily replaced.

[0278] [Eighth embodiment] Next, an eighth embodiment of the present invention will be described. Of the configuration and functions of the drive recorder 1 of this embodiment, those that are common to the other embodiments will not be described.

[0279] To prevent recording failures due to an impact event, the key issue is that the power cable must not easily come loose from the main unit. A drive recorder 1 should be equipped with a locking mechanism as a disconnection prevention function to prevent the power cable from coming loose due to the impact of an accident. Given the nature of drive recorders, a disconnection prevention function is advantageous in increasing the probability that the drive recorder 1 will be able to record and record the entire impact event. To achieve this, one option for a disconnection prevention function that can reduce the size of the drive recorder 1 housing is to have the cable extend directly from the drive recorder 1, i.e., the end of the cable on the drive recorder 1 side is located inside the drive recorder 1 housing and fixed to the drive recorder 1, making it non-detachable. Even so, a sturdy structure would be even better to prevent the wiring inside the drive recorder 1 from coming loose due to an impact.

[0280] The external battery 50 has a function as a converter 51 (5V control function), a role for recording by the parking memory function, and a role for storing the backup USB It is preferable to use an integrated I / F unit that oversees power control for the Type A receptacle. Even when not recording using the parking memory function, the external battery 50 may be configured to receive power from the constant power supply (+B) so that power is supplied to the external battery 50 even when the accessory power is turned off or the key is off. This has the advantage that the drive recorder 1 can start recording early without waiting for charging when the accessory power is turned on. Even if the accessory power is turned off due to an accident crash, where a super capacitor alone can only perform limited processing such as closing files, a configuration that receives power from the constant power supply (+B) has the advantage of increasing the possibility of recording the event to the end.

[0281] According to this embodiment, a highly convenient drive recorder 1 and external battery 50 are provided.

[0282] This concludes the description of the embodiments of the present invention, but the configurations of the first to eighth embodiments may be combined as appropriate. Furthermore, the aspects of the present invention are not limited to these embodiments. The configurations described in the second to eighth embodiments are also applicable to drive recorders and other imaging devices that do not have a parking storage function.

[0283] One file is a file in which video of a specified duration, such as 1 minute or 2 minutes, is recorded (however, the duration may be shortened when the power is turned off, etc.). Furthermore, as described in the first embodiment, serial numbers are added consecutively to the file names of such files. Therefore, the assigned serial numbers serve as an indicator of how much the memory card 45 has been used (e.g., how many times data has been recorded or how long video data has been recorded). Therefore, when the serial number reaches a predetermined number (e.g., a threshold value), the controller 30 may issue a notification urging the operator to format the memory card 45. This is because, when the serial number reaches a predetermined number, it can be estimated that the number of times data has been written to the memory card 45 is large. The notification may be given to the operator by displaying a message on the display 12, making a sound, illuminating an LED, or by other methods. Furthermore, the controller 30 may issue a notification urging the operator to format the memory card 45 when the difference between the serial number used the previous time the card was formatted and the current serial number reaches a predetermined value (e.g., a threshold value). Although the notification urges the user to format the memory card 45, the controller 30 may also notify the user that the memory card 45 has reached the end of its life in a similar manner.

[0284] In the above-described embodiment, the time lapse mode and the motion detection mode are exclusively selected, such that when one is selected, the other is not executed. However, this is not limited to this. For example, a drive recorder may include a first board (SoC) and a second board (SoC), with the first board operating in the time lapse mode and the second board operating in the motion detection mode. In this way, the situation while parking can be continuously recorded in the time lapse mode, and if a moving object is detected due to an abnormality in the motion detection mode, the situation at that time can be recorded at a higher frame rate. The functions of the first board and the second board may be realized on a single board.

[0285] In the above embodiment, the vehicle 100 is provided with two imaging units, the front camera 10 and the rear camera 20, but the number and locations of the imaging units are not limited to this. For example, an imaging unit that is oriented toward the side of the vehicle or an imaging unit that captures images of the interior of the vehicle may be provided.

[0286] In the above embodiment, the memory card 45 is described as an SD card, a miniSD card, a microSD card, or other storage medium, but it may be other storage media such as a USB memory, an SSD, a small hard disk, etc. The memory card reader 44 can also be changed to a writing / reading device suitable for the storage medium.

[0287] The time lapse mode and the motion detection mode may also be applied to monitoring functions other than the parking memory function. For example, they may be applied to a monitoring function that uses an imaging unit to monitor a work area such as a factory. In this case, motion detection would be detecting falling objects or overturned equipment. In this way, the system of the present invention can be applied to devices other than drive recorders and other vehicle imaging devices.

[0288] The scope of the present invention is not limited to the structures explicitly described in the specification, but also includes combinations of various aspects of the present invention disclosed herein. The structures of the present invention that are sought to be patented are specified in the appended claims, but it is the intention of the present inventors to claim structures disclosed in this specification in the future, even if they are not currently specified in the claims.

[0289] The present invention is not limited to the configurations described in the above-described embodiments. The components of each of the above-described embodiments and variations may be arbitrarily selected and combined. Furthermore, any component of each embodiment or variation may be arbitrarily combined with any component described in the Summary of the Invention or any component embodying any component described in the Summary of the Invention. The present invention also intends to obtain rights to these configurations through amendments or divisional applications of the present application. Even if a description is made of "in the case of..." or "when...," it is not intended to describe a configuration limited to that case or time. Configurations that are not limited to those cases or times are also disclosed, and the present invention intends to obtain rights to them. Furthermore, any descriptions that specify an order are not limited to this order. Configurations in which some parts are deleted or the order is changed are also disclosed, and the present invention intends to obtain rights to them.

[0290] Furthermore, we intend to obtain rights to the overall design or partial design by converting the application to a design registration. The drawings depict the entire device in solid lines, but they also include partial designs claimed for parts of the device. For example, a partial design can be a partial design for a part of the device, or a part of that part. A partial design can be a part of the device, or a part of that part. We intend to obtain rights not only for the overall design, but also for partial designs in which any part of the solid line portion of the drawing is drawn as a broken line. Furthermore, the modules, components, and parts inside the device's casing, all of which are shown in the drawings, are subject to independent commerce, and we intend to similarly obtain rights by converting the application to a design registration. [Explanation of symbols]

[0291] 1 Drive recorder (system) 10. Front camera 11 Memory card slot 12 Display 13 Control section 13a~13f Operation buttons 14 Joint Rail 15 Power cable 100 vehicles 101 Windshield 102 Rearview mirror 103 Cigarette lighter socket 104 Rear window 105 Dashboard

Claims

1. A system having a recording function for storing images captured in a vehicle, The recording function of the system has a function of stopping recording when a write error to a storage medium is detected, and resuming recording after unmounting and mounting the storage medium.

2. 2. The system according to claim 1, wherein when the storage medium is switched, the device having the recording function is restarted.

3. 3. A system according to claim 1, wherein recording is performed using an internal storage area and a removable storage medium, and recording is performed using the internal storage area when an impact of at least a predetermined magnitude occurs.

4. In a system according to any one of claims 1 to 3, the recording function has a detection function for detecting the write capability of the storage medium and a notification function for notifying a warning according to the write capability, and the system allows the recording of captured video even when a warning is notified.

5. 5. A system according to any one of claims 1 to 4, comprising a drive recorder having a recording function, which has a function of backing up recorded data to an external storage device based on power supplied from a battery when power supply from the vehicle is stopped, and a supercapacitor attached externally to the drive recorder for supplying power to the drive recorder.

6. A program for causing a computer to realize the functions of the system according to any one of claims 1 to 5.

Images