Head-up display device

Abstract

To provide a head-up display device capable of sharing hardware among a plurality of types of vehicles by changing methods of installation on a vehicle, which reduces the possibility of misuse and contributes to achievement of the Sustainable Development Goal "3. Good Health and Well-Being to all the people".SOLUTION: A memory 17 stores: target control software 25 which is any one of a plurality of types of control software 25 corresponding to a plurality of types of vehicles, respectively; and software identification information 30 that identifies the type of target control software 25. When being activated, the head-up display device compares with one another, at least some of the software identification information 30, installation identification information 31 that indicates an installation method of the head-up display device on the vehicle, and vehicle type information that indicates the type of vehicle, and determines whether or not to transition to normal operation on the basis of the comparison result.SELECTED DRAWING: Figure 6A

Description

Technical Field

[0001] The present invention relates to a head-up display device.

Background Art

[0002] Patent Document 1 discloses a head-up display device that enables a plurality of types of members including a housing to be shared between a right-hand drive vehicle and a left-hand drive vehicle. Specifically, the head-up display device includes a display, a plane mirror that reflects light from the display, and a concave mirror that reflects light from the plane mirror to a windshield inside the housing, and the shape of the main optical path inside the housing is set to be plane-symmetric with respect to a reference plane.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As one of the structures of a head-up display device, a structure that enables hardware to be shared among a plurality of types of vehicles by changing the installation method on the vehicle, such as the installation direction, etc., can be considered. When using such a structure, it is possible to support a plurality of types of vehicles by changing the control software according to the type of vehicle. In the specification, the head-up display device is also referred to as a HUD device.

[0005] Such a HUD device, for example, is shipped as a HUD device for vehicle type A after control software for vehicle type A is implemented, and is installed in a vehicle of type A. In order for the HUD device to be used correctly, it is necessary that the HUD device for type A is properly installed in a vehicle of type A using the installation method for type A. However, especially when the HUD device is installed manually in the vehicle, there was a risk that the HUD device would be misused due to human error during installation.

[0006] This invention has been made in view of the above, and one of its objectives is to reduce the possibility of misuse in a head-up display device that can share hardware across multiple types of vehicles by changing the method of installation on the vehicle.

[0007] The aforementioned and other objectives and novel features of the present invention will become apparent from the description herein and the accompanying drawings. [Means for solving the problem]

[0008] A brief overview of some of the representative inventions disclosed in this application is as follows:

[0009] Typical head-up display devices are designed to share hardware across multiple types of vehicles and comprise a memory unit, a video display unit, and a video light projection unit. The memory unit stores the target control software, which is one of several types of control software corresponding to each of the multiple types of vehicles, and software identification information that identifies the type of the target control software. The video display unit displays an image and emits video light from the displayed image. The video light projection unit projects the video light emitted from the video display unit onto a display area, making the projected video light visible as a virtual image. To execute the target control software, at the time the head-up display device is started, at least a portion of the software identification information, installation identification information representing the method of installing the head-up display device on the vehicle, and vehicle type information representing the type of vehicle are compared with each other, and a decision is made based on the comparison result whether or not to proceed to normal operation. [Effects of the Invention]

[0010] To briefly explain the effects obtained by representative inventions disclosed in this application, by changing the method of installation on vehicles, it becomes possible to reduce the possibility of misuse in a head-up display device whose hardware can be shared across multiple types of vehicles. [Brief explanation of the drawing]

[0011] [Figure 1] This is a schematic diagram showing an example of the configuration of a vehicle equipped with a head-up display device according to Embodiment 1. [Figure 2A] Figure 1 is a block diagram showing an example of the configuration of the main components of the control system responsible for control in the HUD device. [Figure 2B] This block diagram shows an example of the main components of the control system in the HUD device shown in Figure 1, which differs from the configuration shown in Figure 2A. [Figure 3] Figures 2A and 2B are block diagrams showing examples of configurations related to the control unit. [Figure 4A]It is a schematic diagram showing an example of the structure of the main part of the HUD device in FIG. 1 and an example of the installation method on a vehicle. [Figure 4B] It is a schematic diagram showing an example of the structure of the main part of the HUD device in FIG. 1 and an example of the installation method on a vehicle different from that in FIG. 4A. [Figure 5A] In the HUD device shown in FIG. 4A, it is a diagram showing an example of the stored content in the memory. [Figure 5B] In the HUD device shown in FIG. 4B, it is a diagram showing an example of the stored content in the memory. [Figure 6A] It is a schematic diagram showing an example of the processing content of the control unit in FIG. 2A. [Figure 6B] It is a diagram showing specific examples of the installation identification information and the software identification information in FIG. 6A.​​​​​​​​​​​​​​​​​​​​​​​​​​​​​This is a supplementary diagram for explaining part of the processing content in FIG. 11B. [Figure 12B] This is a supplementary diagram for explaining part of the processing content in FIG. 11B. [Figure 13] This is a schematic diagram showing a configuration example of a system including a head-up display device according to Embodiment 3. [Figure 14] In FIG. 13, this is a diagram showing an example of a screen displayed on the display of an external device.

Embodiments for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described in detail based on the drawings. In all the drawings for explaining the embodiments, the same members are generally denoted by the same reference numerals, and repeated explanations thereof are omitted.

[0013] (Embodiment 1) <Overview of HUD Device> FIG. 1 is a schematic diagram showing a configuration example of a vehicle equipped with a head-up display device according to Embodiment 1. The head-up display (HUD) device 1 shown in FIG. 1 is mounted on a vehicle 2 which is one type of vehicle. The vehicle 2 is typically an automobile, but is not necessarily limited thereto, and may be a railway vehicle or the like. Also, the vehicle is not limited to a vehicle, and may be an aircraft or the like. The vehicle 2 is equipped with a control unit 21 called an ECU (Electronic Control Unit), for example.

[0014] The control unit 21 acquires vehicle information 4 from various sensors installed in each part of the vehicle 2 and, in addition, from a navigation device or the like. The various sensors detect various events occurring in the vehicle 2 and also detect various parameter values related to the driving situation. The HUD device 1 acquires the vehicle information 4 acquired by the control unit 21 using, for example, CAN (Controller Area Network) communication or the like. <UNK>

[0015] Vehicle information 4 includes, for example, vehicle 2's speed information, gear information, steering angle information, lamp illumination information, ambient light information, distance information, infrared information, engine ON / OFF information, camera images inside and outside the vehicle, accelerometer / gyro information, GPS (Global Positioning System) information, navigation information, vehicle-to-vehicle communication information, and vehicle-to-infrastructure communication information. GPS information also includes information such as the current time. Vehicle information 4 also includes various warning information. Based on this vehicle information 4, the HUD device 1 projects image light onto a display area such as the windshield 3. In this way, the HUD device 1 allows the driver or other user to perceive the projected image light onto the display area as a virtual image, more specifically as a virtual image superimposed on the scenery in front of the vehicle 2.

[0016] Figure 2A is a block diagram showing an example of the main components of the HUD device shown in Figure 1. The HUD device 1 shown in Figure 2A comprises a mirror drive unit 14, a display drive unit 15, a communication unit 16, a storage unit 17, and a control unit 20, all connected to each other by a bus 13. The display drive unit 15 drives the video display unit 11, and the mirror drive unit 14 drives the mirror M1. The video display unit 11 is, for example, a liquid crystal display comprising a light source and a display panel. The display panel displays images by modulating the backlight irradiated from the light source pixel by pixel based on video data. In this case, the display drive unit 15 can be implemented by an LCD driver circuit or the like. Hereinafter, the storage unit 17 will be described as memory.

[0017] Mirror M1 functions as an image projection unit that projects image light emitted from the image display unit 11 onto a display area on the windshield 3, thereby allowing the user to perceive the projected image light as a virtual image. The communication unit 16 is implemented by a communication interface circuit or the like. The communication unit 16 receives or transmits various information to and from the control unit 21 using CAN communication or the like. In other words, communication between the control unit 21 and the communication unit 16 is bidirectional. As one of its functions, the communication unit 16 functions as an information acquisition unit that acquires or receives information related to the vehicle, i.e., vehicle information 4, from the control unit 21. The communication unit 16 transmits the acquired vehicle information 4 to the control unit 20 or memory 17 via the bus 13.

[0018] Memory 17 consists of a combination of volatile and non-volatile memory. Memory 17 stores, for example, control programs used by the control unit 20, in other words, control software, and data. The control unit 20 is implemented by a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The control unit 20 controls the entire HUD device 1, including the content displayed on the video display unit 11, by executing the control software stored in memory 17.

[0019] As part of this control, the control unit 20 controls the mirror drive unit 14 and the display drive unit 15 via the bus 13. The mirror drive unit 14 adjusts the installation angle of the mirror M1 in response to signals or commands from the control unit 20. The mirror drive unit 14 can be implemented by a motor for adjusting the installation angle of the mirror M1, or by a motor driver circuit that drives the motor. The control unit 20 also generates video data based on acquired vehicle information 4, etc., and stores the video data in the memory 17. The display drive unit 15 reads the video data stored in the memory 17 via the bus 13 and drives the video display unit 11 based on the video data.

[0020] The communication unit 16, memory 17, and control unit 20 shown in Figure 2A can be mounted on, for example, a microcontroller. However, the implementation form of the HUD device 1 is not limited to such a microcontroller-based configuration; it may also be a configuration that appropriately combines FPGAs (Field Programmable Gate Arrays), ASICs (Application Specific Integrated Circuits), etc.

[0021] Figure 2B is a block diagram showing an example of a different main component configuration in the HUD device shown in Figure 1, but different from that shown in Figure 2A. Unlike the configuration example shown in Figure 2A, the HUD device 1 shown in Figure 2B does not have a control unit 20, but instead has a communication processing unit 16a. In this case, for example, the control unit 21 creates video data instead of the control unit 20 shown in Figure 2A, and stores the created video data in the memory 17 via the communication processing unit 16a.

[0022] In the configuration example shown in Figure 2B, the communication processing unit 16a may perform the functions of the control unit 20 described in Figure 2A, such as the control function of the mirror drive unit 14. Alternatively, the functions of the control unit 20 described in Figure 2A may be appropriately divided between the control unit 21 and the communication processing unit 16a. Unlike the communication unit 16 shown in Figure 2A, the communication processing unit 16a receives information about the vehicle from the control unit 21 using CAN communication or the like, processes the received information, and notifies the mirror drive unit 14 and the display drive unit 15 of the processing results. Communication between the communication processing unit 16a and the control unit 21 in Figure 2B is bidirectional.

[0023] Figure 3 is a block diagram showing an example configuration of the control unit in Figures 2A and 2B. The control unit 21 primarily acquires vehicle information 4, as described in Figure 1. The vehicle information 4 is generated by various information acquisition devices, such as sensors, connected to the control unit 21, as shown in Figure 3. An example of such information acquisition device is shown in Figure 3.

[0024] In Figure 3, for example, the vehicle speed sensor 101 detects the speed of vehicle 2 in Figure 1 and generates speed information as the detection result. The shift position sensor 102 detects the current gear and generates gear information as the detection result. The steering angle sensor 103 detects the current steering angle and generates steering angle information as the detection result. The headlight sensor 104 detects whether the headlights are ON or OFF and generates lamp illumination information as the detection result. The illuminance sensor 105 and the chromaticity sensor 106 detect ambient light and generate ambient light information as the detection result.

[0025] The distance measuring sensor 107 detects the distance between the vehicle 2 and an external object and generates distance information as the detection result. The infrared sensor 108 detects the presence and distance of an object in close proximity to the vehicle 2 and generates infrared information as the detection result. The engine start sensor 109 detects whether the engine is ON or OFF and generates ON / OFF information as the detection result. The acceleration sensor 110 and the gyro sensor 111 detect the acceleration and angular velocity of the vehicle 2, respectively, and generate acceleration gyro information representing the attitude and behavior of the vehicle 2 as the detection result. The temperature sensor 112 detects the temperature inside and outside the vehicle and generates temperature information as the detection result.

[0026] The vehicle-to-infrastructure wireless receiver 113 generates vehicle-to-infrastructure communication information through vehicle-to-infrastructure communication between vehicle 2 and roads, signs, traffic lights, etc. The vehicle-to-vehicle wireless receiver 114 generates vehicle-to-vehicle communication information through vehicle-to-vehicle communication between vehicle 2 and other surrounding vehicles. The in-vehicle camera 115 and the exterior camera 116 generate in-vehicle camera image information and exterior camera image information by capturing images of the inside and outside of the vehicle, respectively. The in-vehicle camera 115 is, for example, a camera for a Driver Monitoring System (DMS) that captures the posture, eye position, and movement of the user, i.e., the driver. In this case, by analyzing the captured images, the driver's fatigue level and gaze position can be determined.

[0027] On the one hand, the external camera 116 of the vehicle captures the surrounding situation, such as the front and rear of the vehicle 2. In this case, by analyzing the captured video, it becomes possible to grasp the presence or absence of obstacles such as other vehicles and people existing in the vicinity, the road surface conditions such as buildings, terrain, rain, snow accumulation, freezing, unevenness, etc., and road signs. Further, the external camera 116 may include, for example, a drive recorder that records the situation during driving in video.

[0028] The GPS receiver 117 generates GPS information obtained by receiving GPS signals. For example, the GPS receiver 117 can acquire the current time. The VICS (Vehicle Information and Communication System, registered trademark) receiver 118 generates VICS information obtained by receiving VICS signals. The GPS receiver 117 and the VICS receiver 118 may be provided as part of the navigation device.

[0029] Regarding the various information acquisition devices shown in FIG. 3, it is possible to appropriately delete them, add other types of devices, or replace them with other types of devices. Further, in addition to the vehicle information 4 from the various information acquisition devices shown in FIG. 3, the control unit 21 may be able to acquire information on the vehicle type of the vehicle 2, for example, information such as a truck, a passenger car, a one-box car, etc.

[0030] <Regarding the Structure and Installation Method of the HUD Device> The HUD device 1 according to the embodiment can share hardware among multiple types of vehicles 2 by changing the installation method or installation state on a vehicle, for example, the vehicle 2. FIG. 4A is a schematic diagram showing an example of the structure of the main part of the HUD device in FIG. 1 and an example of the installation method on the vehicle. In FIG. 4 and the like, for the driver of the vehicle 2, the horizontal direction is the left-right direction, the lateral direction of the vehicle, or the width direction of the vehicle, the vertical direction is the up-down direction of the vehicle, the longitudinal direction, and the horizontal direction orthogonal to the lateral direction of the vehicle is the front-rear direction or the traveling direction of the vehicle.

[0031] Figure 4B is a schematic diagram showing an example of the main structure of the HUD device in Figure 1, and an example of an installation method on a vehicle different from that shown in Figure 4A. Figure 4A shows an installation method for vehicle types where the inclination of the windshield 3 relative to the horizontal plane is large, such as trucks, vans, and some railway cars. On the other hand, Figure 4B shows an installation method for vehicle types where the inclination of the windshield 3 relative to the horizontal plane is smaller than that of the trucks in Figure 4A, such as passenger cars.

[0032] The HUD device 1 shown in Figures 4A and 4B both include a video display unit 11, a lens LS, a mirror M1, and a mirror drive unit 14, etc., housed within a housing 12. The video display unit 11 does not necessarily have to be entirely housed within the housing 12; only the display panel may be housed within it. The video display unit 11 is, for example, an LCD (Liquid Crystal Display), an organic EL display, or a projector, and displays an image based on input video data and emits the image light of the displayed image toward the mirror M1.

[0033] The lens LS, or optical element, is inserted in the optical path from the image display unit 11 to the mirror M1, and adjusts, for example, the spread of the image light. The lens LS is not necessarily required. As mentioned above, the mirror M1 functions as an image light projection unit. In this embodiment, the mirror M1, which is the image light projection unit, projects the image light emitted from the image display unit 11 and incident through the lens LS onto the display area 5 on the windshield 3 through the opening 7 provided in the housing 12 and the opening provided in the dashboard 10. As a result, the image light projection unit allows the user 6 to view the projected image light as a virtual image.

[0034] In detail, the mirror M1 is, for example, a concave mirror, i.e., a magnifying mirror, which reflects and magnifies the incident image light and projects it onto the display area 5 through the opening 7. The image light projected onto the display area 5 is reflected by the display area 5 and incident on the user's eyes 6. As a result, the user 6 sees the image light projected onto the display area 5 as a virtual image 9 existing beyond the transparent windshield 3, superimposed on the scenery outside the vehicle (roads, buildings, people, etc.). The information represented by the virtual image 9 includes, for example, road signs, the current speed of the vehicle, and various information added to objects in the scenery, i.e., AR (Augmented Reality) information, and various other things based on vehicle information 4.

[0035] The mirror M1 may be, for example, a free-form surface mirror or a mirror with an asymmetrical optical axis shape. A mirror drive unit 14 is installed on the mirror M1. The mirror drive unit 14 adjusts the installation angle of the mirror M1. Specifically, the mirror drive unit 14 includes, for example, a motor, and rotates the mirror M1 by the rotational operation of the motor. By adjusting the installation angle of the mirror M1, the position of the display area 5 on the windshield 3, that is, the vertical position of the virtual image viewed by the user 6, can be adjusted.

[0036] Furthermore, by variably adjusting the installation angle of the mirror M1, it becomes possible to protect the image display unit 11 from sunlight. Specifically, sunlight can travel in the reverse direction along the optical path of the image light and enter the image display unit 11. For example, if the control unit 20 shown in Figure 2A determines that there is a high possibility of damage to the image display unit 11 due to the incidence of sunlight, it can change the installation angle of the mirror M1 via the mirror drive unit 14 so that sunlight does not reach the image display unit 11.

[0037] In the case of a truck or similar vehicle shown in Figure 4A, the HUD device 1 is installed so that the direction of emission of the video light from the video display unit 11 is a first direction on the vehicle's coordinate axis, which in this example is the reverse direction. On the other hand, in the case of a passenger car or similar vehicle shown in Figure 4B, the HUD device 1 is installed so that the direction of emission of the video light from the video display unit 11 is a second direction on the vehicle's coordinate axis that is opposite to the first direction, which in this example is the forward direction. Thus, the HUD device 1 according to this embodiment can share hardware across multiple types of vehicles by changing the installation method on the vehicle, for example, the installation direction.

[0038] Figure 5A shows an example of the memory contents in the HUD device shown in Figure 4A. Figure 5B shows an example of the memory contents in the HUD device shown in Figure 4B. The HUD device 1 shown in Figure 5A stores truck control software 25a in memory 17. On the other hand, the HUD device 1 shown in Figure 5B stores passenger car control software 25b in memory 17.

[0039] As described above, the HUD device 1 shown in Figures 4A and 4B can be adapted to multiple types of vehicles 2 by changing the installation method on the vehicle 2 and modifying the control software according to the vehicle type, while sharing hardware. This makes it possible to reduce the manufacturing cost of the HUD device 1, etc.

[0040] On the other hand, such a HUD device 1 is shipped with vehicle-specific control software 25a and 25b, as shown in Figures 5A and 5B, already installed, and is installed in the corresponding vehicle in the production process of the vehicle 2, for example, using the installation method shown in Figures 4A and 4B. However, when the HUD device 1 is manually installed in the vehicle 2, especially in the production process of the vehicle 2, human error in installation may occur. As a result, there was a risk that the HUD device 1 would be used incorrectly.

[0041] As a concrete example, the HUD device 1 may be installed on a truck as shown in Figure 4A, in the orientation shown in Figure 4B, i.e., an incorrect orientation. In this case, the HUD device 1 may have either passenger car control software 25a or truck control software 25b installed. In other words, a situation may arise where the installation method of the HUD device 1 is incorrect, and the control software is either correct or incorrect. Alternatively, the HUD device 1 equipped with truck control software 25a as shown in Figure 5A may be installed on a passenger car in the orientation shown in Figure 4B. In other words, a situation may arise where the installation method of the HUD device 1 is correct, but the control software is incorrect.

[0042] <Details of the control unit> Therefore, the control unit 20 performs the following processing as an example. Figure 6A is a schematic diagram showing an example of the processing content of the control unit in Figure 2A. Figure 6B is a diagram showing specific examples of installation identification information and software identification information in Figure 6A. First, as a premise, when the HUD device 1 is installed on the vehicle 2 during the production process of the vehicle 2, installation identification information 31 representing the installation method or installation state used, for example, the installation direction, is registered in advance. The installation identification information 31 may be built into the HUD device 1, or it may be registered separately manually by an operator or the like. The installation identification information 31 is in a state where it can be read from the control unit 20 or the vehicle's control unit 21. Furthermore, the specific processing is the same except that the control unit 20 in Figure 2A or the communication processing unit 16a in Figure 2B compares and makes a decision depending on the destination of the signal related to the identification information, or the vehicle's control unit 21 compares and makes a decision. The following explanation will use the installation identification information 31 that can be read from the control unit 20.

[0043] In the example shown in Figure 6A, the installation identification information 31 is stored in memory 17 or a register mapped to memory 17. However, the installation identification information 31 only needs to be registered in a state that can be read by the control unit 20, and does not necessarily need to be stored in memory 17. For example, a mechanical switch, specifically a DIP switch, for registering the installation identification information 31 could be provided in the HUD device 1, and the state of the mechanical switch could be read from the control unit 20 connected to the mechanical switch.

[0044] Furthermore, as mentioned above, memory 17 stores the control software 25. In this specification, software is also referred to as SW. The control software 25 includes SW identification information 30 that identifies its own type from among several types of control software 25, such as for trucks and for passenger cars. When the HUD device 1 is started up, the control unit 20 compares the SW identification information 30 stored in memory 17 with the installation identification information 31. If they match, it proceeds to normal operation; if they do not match, it outputs an error without proceeding to normal operation.

[0045] As shown in Figure 6B, the SW identification information 30 and the installation identification information 31 have a minimum size of 1 bit when there are two types of vehicle models. In this example, the SW identification information 30 is "0" if the control software 25 is for trucks and "1" if it is for passenger cars. In addition, the installation identification information 31 is registered as "0" when the HUD device 1 is installed in the orientation shown in Figure 4A and as "1" when it is installed in the orientation shown in Figure 4B.

[0046] In this example, to distinguish between two types of vehicle models, each identification piece of information is represented by 1 bit. However, to distinguish between three types, such as a state where the installation identification information 31 is not registered (i.e., the worker has forgotten to register the installation identification information 31), each identification piece of information may be represented by 2 bits or more.

[0047] Figure 7 is a flowchart showing an example of the processing content of the control unit in Figure 2A. Figures 8A, 8B, and 8C are diagrams showing specific examples of the processing content in steps S12 to S14 in Figure 7. In Figure 7, when the HUD device 1 is activated, the control unit 20 first establishes communication with the outside of the HUD device 1 via the communication unit 16, etc. (step S11). Next, the control unit 20 acquires various identification information (step S12). Then, the control unit 20 compares the acquired identification information (step S13) and performs an action according to the comparison result (step S14).

[0048] In the example shown in Figure 8A, the control unit 20 acquires SW identification information 30 and installation identification information 31 as various identification information, as shown in Figures 6A and 6B (step S12). If the SW identification information 30 and the installation identification information 31 match (step S13), the control unit 20 proceeds to normal operation without outputting an error (step S14, No. 1 in Figure 8A). If the SW identification information 30 and the installation identification information 31 match, it is highly likely that the HUD device 1 with the correct control software 25 has been installed in the correct manner. In this case, by proceeding to normal operation, for example, vehicle information 4 is displayed on the video display unit 11.

[0049] On the other hand, if the SW identification information 30 and the installation identification information 31 are inconsistent (step S13), the control unit 20 does not proceed to normal operation but outputs an error [1] indicating that the two pieces of identification information are inconsistent (step S14, No. 2 in Figure 8A). Specifically, the control unit 20 notifies an external party such as the control unit 21 via the communication unit 16 using a notification message or voice, or stores the error [1] in the memory 17 as an error log.

[0050] If the SW identification information 30 and the installation identification information 31 do not match, there is a high possibility that the HUD device 1 has incorrect control software 25 installed or that the HUD device 1 is installed incorrectly. As a result, there is a high possibility that the HUD device 1 will be used incorrectly. Therefore, in this case, the transition to normal operation will not occur.

[0051] In the example shown in Figure 8B, the control unit 20 acquires various identification information, including vehicle type identification information representing the type of vehicle 2, such as a truck or a passenger car, and SW identification information 30 (step S12). If the vehicle type identification information and SW identification information 30 match (step S13), the control unit 20 proceeds to normal operation without outputting an error (step S14, No. 1 in Figure 8B).

[0052] Thus, the HUD device 1 may be able to acquire vehicle identification information through communication with an external source. Specifically, the HUD device 1 may be able to acquire vehicle identification information from the control unit 21 via the communication unit 16, or from an external mobile terminal, such as a smartphone, via a separately provided wired communication unit or wireless communication unit. The wired communication unit or wireless communication unit may be, for example, a USB interface, a wireless LAN interface, or a Bluetooth® interface. The communication unit 16, the wired communication unit, or the wireless communication unit functions as an information acquisition unit that acquires vehicle identification information.

[0053] In this way, the vehicle identification information obtained from outside the HUD device 1 can be considered correct. Therefore, if the vehicle identification information and the SW identification information 30 match, it can be determined that at least the combination of vehicle 2 and the HUD device 1 itself is correct. In this case, the system transitions to normal operation.

[0054] On the other hand, if the vehicle identification information and the SW identification information 30 do not match (step S13), the control unit 20 does not proceed to normal operation but outputs an error [2] indicating that the two pieces of identification information do not match (step S14, No. 2 in Figure 8B). If the vehicle identification information and the SW identification information 30 do not match, it can be determined that the combination of the vehicle 2 and the HUD device 1 itself is incorrect. Therefore, in this case, the system does not proceed to normal operation.

[0055] In the example shown in Figure 8C, the control unit 20 acquires vehicle type identification information, SW identification information 30, and installation identification information 31 as various identification information (step S12). If all three pieces of identification information match (step S13), the control unit 20 proceeds to normal operation without outputting an error (step S14, No. 1 in Figure 8C).

[0056] Furthermore, if the vehicle identification information and the SW identification information 30 match, but the vehicle identification information and the installation identification information 31 do not match (step S13), the control unit 20 will proceed to normal operation and output an error [3] indicating that only the installation identification information 31 did not match (step S14, No. 2 in Figure 8C). In other words, in this case, as described above, it can be determined that at least the combination of the vehicle 2 and the HUD device 1 itself is correct. However, there is a possibility that the installation method is incorrect, or that the operator made a mistake in registering the installation identification information 31. In this case, the control unit 20 will proceed to normal operation and output an error.

[0057] Furthermore, if the vehicle identification information and the SW identification information 30 do not match (step S13), the control unit 20 outputs an error without proceeding to normal operation, regardless of the installation identification information 31, as in the case of Figure 8B (step S14, No. 3 and No. 4 in Figure 8C). In this case, if the vehicle identification information and the installation identification information 31 match, the control unit 20 outputs an error [4] indicating that (No. 3 in Figure 8C), and if the vehicle identification information and the installation identification information 31 do not match, it outputs an error [5] indicating that (No. 4 in Figure 8C).

[0058] As shown in Figure 8C, in addition to comparing the vehicle identification information with the SW identification information 30, comparing the vehicle identification information with the installation identification information 31 allows for verification, unlike in Figure 8B, whether the HUD device 1 can be used correctly, including the installation method. As a result, in Figure 8C, if all three pieces of identification information match, the certainty that the HUD device 1 can be used correctly is higher compared to when two pieces of identification information match in Figure 8B.

[0059] <Main effects of Embodiment 1> As described above, in the method of Embodiment 1, assuming a HUD device 1 whose hardware can be shared across multiple types of vehicles by changing the installation method on the vehicle, the correctness of the control software 25 and / or installation method can be verified by comparing at least a portion of the SW identification information 30, installation identification information 31, and vehicle type identification information with each other. Then, if it is presumed that the control software 25 and / or installation method is correct based on the comparison results, the system will transition to normal operation. As a result, the possibility of the HUD device 1 being used incorrectly can be reduced.

[0060] (Embodiment 2) <Details of the control unit> Figure 9A is a schematic diagram showing an example of the processing content of the control unit in Figure 2A in the head-up display device according to Embodiment 2. Figure 9B is a diagram showing an example of the contents stored in the memory in Figure 9A. In the HUD device 1 shown in Figure 9A, unlike in Embodiment 1, the memory 17 stores multiple types of control software corresponding to multiple types of vehicles 2 as shared control software 25c.

[0061] The shared control software 25c comprises a vehicle-independent common section 35 and vehicle-specific sections, in this case a truck-specific section 36a and a passenger car-specific section 36b. The operation mode 37 selects which of the truck-specific section 36a and the passenger car-specific section 36b to execute. That is, the control unit 20 selects one of several types of control software based on the setting information of the operation mode 37 and controls the entire HUD device 1 by executing the selected control software. By using such shared control software 25c, the HUD device 1 can be shared among multiple vehicle types, including not only the hardware but also the software, further reducing product costs.

[0062] Furthermore, as shown in Figure 9B, memory 17 stores installation identification information 31 as described in Figures 6A and 6B, in addition to the shared control software 25c. Unlike in Figure 6A, the shared control software 25c does not include SW identification information 30. Here, the control unit 20 generally compares the vehicle type identification information and installation identification information 31 described in Figure 8B when the HUD device 1 is started, preferably at the first startup. If the two pieces of identification information match, the control unit 20 sets the operation mode 37 corresponding to the matched identification information and transitions to normal operation; if they do not match, it outputs an error without transitioning to normal operation.

[0063] Figure 10 is a flowchart showing an example of the processing content when the control unit in Figure 2A starts up in the head-up display device according to Embodiment 2. In Figure 10, when the HUD device 1 starts up, preferably at the first startup, the control unit 20 establishes communication with the outside of the HUD device 1 via the information acquisition unit, i.e., the communication unit 16, or the wired communication unit, wireless communication unit, etc., as described in Figure 8B (step S21).

[0064] Next, the control unit 20 acquires vehicle type identification information from an external source (step S22), and then reads installation identification information 31 from the memory 17 or the like (step S23). Subsequently, the control unit 20 determines whether the vehicle type identification information and the installation identification information 31 match (step S24). If the two pieces of identification information match (step S24: Yes), the control unit 20 sets the operation mode 37 corresponding to the matched identification information in the memory area referenced by the shared control software 25c (step S25). After that, the control unit 20 transitions to the normal operation shown in Figures 11A and 11B.

[0065] On the other hand, if the vehicle identification information and the installation identification information 31 do not match (step S24: No), the control unit 20 stores information in its memory indicating that it did not set the operation mode 37 or was unable to set the operation mode 37, and outputs an error indicating that the installation identification information 31 is incorrect (step S26). In this case, the control unit 20 does not transition to normal operation.

[0066] In step S25, it is desirable for the control unit 20 to store the setting information for the operating mode 37 in a non-volatile memory area, for example, in the non-volatile memory included in memory 17. In this case, when the HUD device 1 is started for the second time or later, the control unit 20 does not need to execute the flow shown in Figure 10, but simply needs to have the shared control software 25c refer to the setting information for the operating mode 37 stored in the non-volatile memory area. In this way, when the HUD device 1 is started for the second time or later, the startup time of the HUD device 1 can be shortened by omitting the flow shown in Figure 10.

[0067] Furthermore, in the example shown in Figure 10, the control unit 20 sets the operation mode 37 when the vehicle type identification information and the installation identification information 31 match. However, the control unit 20 is not limited to this; for example, it can also set the operation mode 37 based solely on the vehicle type identification information. However, in this case, since the HUD device 1 is not necessarily installed correctly, it is more desirable to use the flow shown in Figure 10, which allows verification including the installation method.

[0068] Furthermore, the control unit 20 can also set the operating mode 37 based solely on the installation identification information 31. For example, this method may be used when vehicle type identification information cannot be obtained. However, the HUD device 1 is not always installed correctly, and the installation identification information 31 is not always registered correctly. Therefore, when vehicle type identification information can be obtained, it is more desirable to use the flow shown in Figure 10.

[0069] <Normal operation of the control unit> Figure 11A is a flowchart showing an example of the processing content during normal operation of the control unit in Figure 2A in the head-up display device according to Embodiment 2. Figure 11B is a flowchart showing an example of the processing content in the display processing (step S34) in Figure 11A. Figures 12A and 12B are supplementary diagrams to explain some of the processing content in Figure 11B.

[0070] In Figure 11A, the control unit 20 first obtains setting information for the operation mode 37 from a predetermined storage area, preferably a non-volatile storage area (step S31). Here, although not shown in the figure, if the control unit 20 is unable to obtain the setting information for the operation mode 37, as in step S26 in Figure 10, and consequently if the operation mode 37 is not set, the control unit 20 terminates the process. On the other hand, if the control unit 20 is able to obtain the setting information for the operation mode 37, it repeatedly executes the processes in steps S32 to S34 at predetermined processing cycles until a display termination request is input (step S35).

[0071] In this iterative process, the control unit 20 first acquires vehicle information 4 from the control unit 21 via the communication unit 16 (step S32). Next, the control unit 20 determines the display content to be displayed on the video display unit 11 based on the acquired vehicle information 4, and creates video data based on the determined display content (step S33). Then, the control unit 20 performs display processing using the created video data (step S34).

[0072] In the display processing (step S34), as shown in Figure 11B, the control unit 20 first determines the operation mode 37 acquired in step S341. If it is truck mode, it proceeds to step S342; if it is passenger car mode, it proceeds to step S346. If the operation mode 37 is truck mode, the control unit 20 determines whether the created video data is for trucks (step S342). If the video data is for trucks (step S342: Yes), the control unit 20 proceeds to step S343; if it is for passenger cars (step S342: No), it proceeds to step S343 via step S345.

[0073] In step S345, the control unit 20 performs a horizontal inversion of the displayed content, or in addition, a vertical inversion. Figure 12A shows an example of the relationship between the content displayed by the video display unit 11 and the content viewed by the user 6 in a HUD device 1 installed on a truck. Figure 12B shows an example of the relationship between the content displayed by the video display unit 11 and the content viewed by the user 6 in a HUD device 1 installed on a passenger car.

[0074] For example, in the installation configuration shown in Figure 12A, the display surface of the display panel of the video display unit 11 faces directly into the eyes of the user 6. In other words, the direction of emission of the video light emitted from the display surface of the display panel of the video display unit 11 is opposite to the forward direction of the vehicle 2. Therefore, the user 6 can view the image displayed on the display surface of the display panel of the video display unit 11 in its original orientation. On the other hand, in the installation configuration shown in Figure 12B, the back surface of the video display unit 11 faces directly into the eyes of the user 6. In other words, the direction of emission of the video light emitted from the display surface of the display panel of the video display unit 11 is the same as the forward direction of the vehicle 2. Therefore, the user 6 will view the image displayed on the display surface of the video display unit 11 in the opposite orientation. To address this, the control unit 20 pre-displays an image that has been reversed horizontally on the video display unit 11, as shown in Figure 12B.

[0075] Based on this relationship, the control unit 20 performs a left-right inversion process for the displayed content in step S345 in Figure 11B. Specifically, if a left-right inversion mechanism is provided in the display drive unit 15 or the video display unit 11, the control unit 20 uses it. If a left-right inversion mechanism is not provided, the control unit 20 processes the video data so that the left and right are inverted and then stores it in the memory 17.

[0076] Next, in step 343, the control unit 20 performs distortion correction processing for the truck. That is, distortion may occur in the image viewed by the user 6 depending on the shape of the truck's windshield 3, etc. The control unit 20 processes the image data in advance to correct for such distortion. After that, the control unit 20 uses the distortion-corrected image data to update the display content of the image display unit 11 (step S344).

[0077] On the other hand, when the operating mode 37 is passenger car mode, the control unit 20 determines whether the created video data is for a truck or not, similar to the case of truck mode (step S346). If the video data is for a truck (step S346: Yes), the control unit 20 performs a left-right inversion process of the display content (step S347) and then proceeds to step S348. If the video data is for a passenger car (step S346: No), it proceeds directly to step S348. Then, the control unit 20 performs distortion correction processing for passenger cars based on the shape of the passenger car's windshield 3, etc. (step S348) and then causes the video display unit 11 to update the display content (step S344).

[0078] Thus, the shared control software 25c differs for each type of vehicle 2 in at least the specifications for the orientation of the image displayed on the image display unit 11 and the processing details for distortion correction of the image. These differences are reflected in the truck-specific section 36a and passenger car-specific section 36b shown in Figure 9A. In the common section 35, for example, the processing details for creating image data based on vehicle information 4 are defined.

[0079] <Main effects of Embodiment 2> As described above, the same effects as those described in Embodiment 1 can be obtained by using the method of Embodiment 2. Furthermore, by using the shared control software 25c, it becomes possible to further reduce product costs and other factors.

[0080] (Embodiment 3) <About Engineer Mode> For example, as shown in Figures 8A, 8B, 8C, or 10, if an inconsistency occurs between the vehicle type identification information, SW identification information 30, and installation identification information 31, the control unit 20 basically does not transition to normal operation but outputs an error to the control unit 21, etc. On the other hand, in such cases, it is desirable to be able to perform error analysis, including cause investigation, and error countermeasures by some means. Therefore, here, an engineer mode is provided as an analytical operation mode executed by the control unit 20. In detail, the control unit 20 operates in engineer mode, for example, by executing a program for engineer mode stored in memory 17.

[0081] The control unit 20 may automatically switch to engineer mode when outputting an error, or it may simply prompt the user to switch to engineer mode. Alternatively, the control unit 20 may switch to engineer mode when a special operation input is made by the analyst via the operation keys of the vehicle 2. In this case, a limiting condition may be added, such as only being applied when a special operation input is made while a certain menu is displayed. Furthermore, the operation input is not limited to the operation keys of the vehicle 2, but may also be, for example, voice input or input from an external device separately connected to the HUD device 1.

[0082] When the control unit 20 transitions to engineer mode, it can perform actions such as the following: • Even if the conditions for transitioning to normal operation are not met, the system will forcibly perform normal operation. - The system displays predetermined content on the video display unit 11. Alternatively, with an external display connected to the HUD device 1, the system controls the system so that the predetermined content can be viewed on the external display. • When an external device such as a computer system is connected to the HUD device 1 via a USB cable or the like, the system controls the communication of information or commands between the external device and the HUD device 1. The external device includes, for example, a display and a user interface that accepts user input. • Controls the update / download / reinstallation of the control software.

[0083] As a specific example, the control unit 20 may, for instance, communicate with the external device mentioned above to output errors, including phenomena such as those described in Figures 8A, 8B, 8C, or 10, such as the error log stored in memory 17, to the external device. Alternatively, the control unit 20 may output errors not limited to those associated with such control software, but also errors occurring in various hardware components within the HUD device 1 to the external device.

[0084] Furthermore, the control unit 20 may provide external devices with a method for resolving the error that occurred, i.e., the content of the error countermeasure. Specifically, this could include forcibly restarting the HUD device 1, updating / downloading / reinstalling the control software, or replacing the hardware. The control unit 20 will terminate engineer mode, for example, when the analyst performs the operation to terminate engineer mode, when the HUD device 1 is restarted, or when the update / reinstallation of the control software is completed.

[0085] Figure 13 is a schematic diagram showing an example of a system configuration including a head-up display device according to Embodiment 3. Embodiment 3 describes how the head-up display device can be operated using one or more external devices 45. In other words, it describes an example in which one or more external devices 45 and the head-up display device cooperate via wired or wireless connections. The HUD device 1 shown in Figure 13 includes, for example, a wired communication interface 40 and / or a wireless communication interface 41 in addition to the configuration shown in Figure 2A, etc.

[0086] The wired communication interface 40 is, for example, a USB interface and is connected to the external device 45a via a USB cable. The wireless communication interface 41 is, for example, a wireless LAN interface or a Bluetooth interface and is connected to the external device 45b via a network 46 as needed. The external devices 45a and 45b are, for example, mobile devices such as smartphones and tablet terminals, and have a display and a user interface.

[0087] This section describes the control of the engineer mode of the head-up display device using external devices 45. The operator can use external devices 45a and 45b to acquire information from the control unit 20 and send signals / commands to the control unit 20. The operator can also switch the control unit 20 to engineer mode by inputting operations using the user interfaces of external devices 45a and 45b. The control unit 20 can also acquire the aforementioned vehicle identification information from external devices 45a and 45b.

[0088] Figure 14 shows an example of a screen displayed on the external device's display in Figure 13. In this example, the control unit 20, in engineer mode, provides the external devices 45a and 45b with a screen prompting them to restart the HUD device 1. In this example, the control unit 20 provides a screen to the external devices 45a and 45b, such as mobile devices, but the external device only needs to have a display. In addition, the control unit 20 can, in some cases, display such a screen as a virtual image 9 located beyond the windshield 3.

[0089] <Main effects of Embodiment 3> As described above, by using the method of Embodiment 3, it becomes possible to easily analyze the cause of situations in which the HUD device 1 cannot be used correctly. Furthermore, it becomes possible to take countermeasures or provide countermeasures depending on the cause. Operation becomes more convenient when the external device and the head-up display device are linked via wired or wireless connections.

[0090] Furthermore, by using the methods of each embodiment, the user 6 can view various information necessary for driving, such as destination and speed, as an image through the windshield 3 while the HUD device 1 is in a state where it can be used correctly. This makes it possible to provide a HUD device 1 that reduces the user 6's eye movement and contributes to supporting safe driving. As a result, it becomes possible to prevent traffic accidents. Moreover, it becomes possible to contribute to "3. Good Health and Well-being" of the United Nations' Sustainable Development Goals (SDGs).

[0091] The present invention has been described in detail above based on embodiments, but the present invention is not limited to the embodiments described above and can be modified in various ways without departing from its essence. For example, the embodiments described above are described in detail in order to explain the present invention in an easy-to-understand manner and are not necessarily limited to those having all the described configurations. Furthermore, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add a configuration from another embodiment to the configuration of one embodiment. In addition, it is possible to add, delete, or replace a part of the configuration of each embodiment with a configuration from another embodiment. [Explanation of Symbols]

[0092] 1…Head-Up Display (HUD) device, 2…Vehicle, 4…Vehicle information, 5…Display area, 11…Video display unit, 16…Communication unit (information acquisition unit), 17…Memory, 20…Control unit, 25…Control software, 30…SW identification information, 31…Installation identification information, 37…Operation mode, 45a, 45b…External devices, M1…Mirror (video light projection unit)

Claims

1. A head-up display device that can share hardware across multiple types of vehicles, A storage unit that stores a target control software which is one of several types of control software corresponding to each of the aforementioned several types of vehicles, and software identification information that identifies the type of the target control software. A video display unit that displays an image and emits video light from the displayed image, A video light projection unit projects the video light emitted from the video display unit onto a display area, thereby causing the projected video light to be perceived as a virtual image. Equipped with, When the head-up display device is installed in the vehicle, installation identification information representing the installation method used is registered in advance. When the head-up display device is started, the software identification information and the installation identification information are compared. If they match, the device proceeds to normal operation; if they do not match, the device does not proceed to normal operation and an error is output. Head-up display device.

2. In the head-up display device according to claim 1, The installation identification information is stored in the storage unit. Head-up display device.

3. In the head-up display device according to claim 1, Furthermore, it is equipped with a mechanical switch for registering the installation identification information. Head-up display device.

4. In the head-up display device according to claim 1, The head-up display device is installed such that, depending on the type of vehicle, the direction of emission of the image light from the image display unit is a first direction on the coordinate axes of the vehicle, or a second direction opposite to the first direction. Head-up display device.

5. In the head-up display device according to claim 1, The aforementioned multiple types of control software differ in at least the specifications for the orientation of the image to be displayed on the image display unit and the processing content for distortion correction of the image, for each type. Head-up display device.

6. In the head-up display device according to claim 1, further, A control unit that controls the display of the video display unit, A communication interface that can be connected to an external device having a display, Equipped with, The control unit outputs the error to the external device via the communication interface. Head-up display device.

7. A head-up display device that can share hardware across multiple types of vehicles, A storage unit that stores a target control software which is one of several types of control software corresponding to each of the aforementioned several types of vehicles, and software identification information that identifies the type of the target control software. A video display unit that displays an image and emits video light from the displayed image, A video light projection unit projects the video light emitted from the video display unit onto a display area, thereby causing the projected video light to be perceived as a virtual image. An information acquisition unit that acquires vehicle type identification information representing the type of vehicle through communication with an external source, Equipped with, When the head-up display device is started, the vehicle identification information acquired by the information acquisition unit is compared with the software identification information. If they match, the device proceeds to normal operation; if they do not match, the device does not proceed to normal operation and outputs an error. Head-up display device.

8. In the head-up display device according to claim 7, When the head-up display device is installed in the vehicle, installation identification information representing the installation method used is pre-registered in a readable state. If the vehicle identification information and the software identification information match, and the vehicle identification information and the installation identification information do not match, the system will proceed to normal operation and output an error. Head-up display device.

9. In the head-up display device according to claim 8, The installation identification information is stored in the storage unit. Head-up display device.

10. In the head-up display device according to claim 8, Furthermore, it is equipped with a mechanical switch for registering the installation identification information. Head-up display device.

11. In the head-up display device according to claim 7, The head-up display device is installed such that, depending on the type of vehicle, the direction of emission of the image light from the image display unit is a first direction on the coordinate axes of the vehicle, or a second direction opposite to the first direction. Head-up display device.

12. In the head-up display device according to claim 7, The aforementioned multiple types of control software differ in at least the specifications for the orientation of the image to be displayed on the image display unit and the processing content for distortion correction of the image, for each type. Head-up display device.

13. In the head-up display device according to claim 7, further, A control unit that controls the display of the video display unit, A communication interface that can be connected to an external device having a display, Equipped with, The control unit outputs the error to the external device via the communication interface. Head-up display device.

14. A head-up display device that can share hardware across multiple types of vehicles, A storage unit that stores multiple types of control software corresponding to each of the aforementioned multiple types of vehicles, A video display unit that displays an image and emits video light from the displayed image, A video light projection unit projects the video light emitted from the video display unit onto a display area, thereby causing the projected video light to be perceived as a virtual image. A control unit that selects one of the aforementioned multiple types of control software based on the setting information of the operating mode and executes the selected control software to control the entire head-up display device, including the video display unit, An information acquisition unit that acquires vehicle type identification information representing the type of vehicle through communication with an external source, Equipped with, When the head-up display device is installed in the vehicle, installation identification information representing the installation method used is registered in advance. The control unit compares the vehicle identification information and the installation identification information at least when the head-up display device is first started. If they match, it sets the operation mode corresponding to the matching identification information and transitions to normal operation. If they do not match, it outputs an error without transitioning to normal operation. Head-up display device.

15. In the head-up display device according to claim 14, The control unit stores the operating mode setting information in a non-volatile memory area, and when the head-up display device is started for the second time or later, it transitions to normal operation based on the operating mode setting information stored in the non-volatile memory area, without comparing the vehicle type identification information with the installation identification information. Head-up display device.

16. In the head-up display device according to claim 14, The installation identification information is stored in the storage unit. Head-up display device.

17. In the head-up display device according to claim 14, Furthermore, it is equipped with a mechanical switch for registering the installation identification information. Head-up display device.

18. In the head-up display device according to claim 14, The head-up display device is installed such that, depending on the type of vehicle, the direction of emission of the image light from the image display unit is a first direction on the coordinate axes of the vehicle, or a second direction opposite to the first direction. Head-up display device.

19. In the head-up display device according to claim 14, The aforementioned multiple types of control software differ in at least the specifications for the orientation of the image to be displayed on the image display unit and the processing content for distortion correction of the image, for each type. Head-up display device.

20. In the head-up display device according to claim 14, Furthermore, it is equipped with a communication interface that can be connected to an external device having a display, The control unit outputs the error to the external device via the communication interface. Head-up display device.

Images