Vehicle control device

Abstract

To reduce a time difference between a timing when a turn lamp becomes a predetermined turn lamp state and a timing when a turn lamp indicator becomes a predetermined indicator state corresponded to the predetermined turn lamp state.SOLUTION: A time difference TA obtained by subtracting an indicator lighting drawing signal reception start timing by a drawing processing completion by a SoC32 in regard to an indicator lighting state of an initial turn lamp indicator 33a is calculated by MCU 31. The turn lamp indicator 33a predicts a timing when the turn lamp indicator 33a at the second time becomes the indicator lighting state so that a time displayed in an indicator lights-out time becomes shorter than a lights-out time of the turn lamp 20 by a time obtained by combining the time difference TA and a time difference TB until a display timing when the turn lamp indicator 33a from a drawing processing completion timing to a timing when it is displayed in the indicator lighting stat.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a vehicle control device that changes a turn lamp indicator to an indicator state corresponding to a turn lamp state (for example, blinks) in response to a change in the turn lamp state of a turn lamp (for example, in response to turning on or off). [Background technology]

[0002] Conventionally, there has been a blinking device that includes a blinking indicator, a monitor that displays graphics, images, etc., a monitor control circuit that controls the monitor, and a reference circuit that generates a reference pulse that serves as a reference period for blinking and inputs it to the indicator and the monitor control circuit, and further includes synchronization means that, after the reference pulse is input from the reference circuit to the monitor control circuit and the monitor control circuit performs a predetermined process to control the monitor, delays the time obtained by subtracting the processing time required for the predetermined process from one period of the reference pulse and starts blinking the monitor (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-114207 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in order to synchronize the indicator with the monitor, the start of blinking on the monitor is delayed, which may cause a sense of discomfort to the user.

[0005] In vehicles equipped with turn lamps and LED-based turn lamp indicators that indicate the on / off state of the turn lamps (on / off), the ECU (Electronic Control Unit) that controls the on / off of the turn lamps previously directly controls the driving of the LEDs, but in order to reduce costs by eliminating the need for manual operation, the automotive industry is now moving to a system in which the ECU uses a Controller Area Network (CAN) to transmit indicator signals related to the blinking of the turn lamp indicators. Furthermore, with the spread of full LCD meters and the like, an increasing number of vehicles are displaying turn lamp indicators on displays, instead of the LEDs that previously used LEDs.

[0006] In this way, when using a CAN to display a turn lamp indicator on a display, there is a problem in that the blinking of the turn lamp indicator is delayed relative to the turning on and off of the turn lamp due to the CAN transmission cycle and the drawing process for drawing the turn lamp indicator on the display, which may cause discomfort to the user.

[0007] Therefore, the present invention has been made in consideration of the above-mentioned problems, and aims to provide a vehicle control device that can reduce the time difference between the timing at which a turn lamp enters a predetermined turn lamp state (e.g., the timing at which it turns on and off) and the timing at which a turn lamp indicator enters a predetermined indicator state corresponding to the predetermined turn lamp state (e.g., the timing at which it flashes). [Means for solving the problem]

[0008] In order to achieve the above object, a vehicle control device according to the present invention is a vehicle control device comprising: a display device having a turn lamp, a display, and a drawing processing unit that draws a turn lamp indicator on the display that indicates the turn lamp state of the turn lamp by an indicator state; and a control unit that receives a user's operation, controls the turn lamp state of the turn lamp, and transmits an indicator signal related to the indicator state of the turn lamp indicator to the display device via a network, wherein the turn lamp state includes a first turn lamp state and a second turn lamp state, and the indicator state includes a first indicator state corresponding to the first turn lamp state and a second indicator state corresponding to the second turn lamp state, and the indicator signal includes a first indicator signal related to drawing the first indicator state and a second indicator signal related to drawing the second indicator state, and the drawing processing unit calculates a time difference between a reception start timing at which the control unit starts receiving the first indicator signal transmitted in response to a current control of the turn lamp to the first turn lamp state from the control unit and a completion timing at which the drawing processing unit completes a current drawing process of drawing the turn lamp indicator to the first indicator state, and performs a next predetermined process including a next drawing process of drawing the turn lamp indicator to the first indicator state corresponding to a next control of the turn lamp to the first turn lamp state by predicting a start timing of the next predetermined process including the next drawing process based on the time difference. and performing the next predetermined process including the next drawing process based on the time difference so that a period of the second indicator state following the first indicator state drawn in the current predetermined process including the current drawing process is shorter than a period of one second turn lamp state of the turn lamp. It is characterized by the following.

[0009] According to this configuration, the drawing processing unit calculates the time difference between the start timing of reception of the current first indicator signal corresponding to the current control of the turn lamp to the first turn lamp state and the completion timing of the current drawing processing, and predicts the start timing of the next predetermined processing including the next drawing processing for drawing the turn lamp indicator in the first indicator state corresponding to the next control of the turn lamp to the first turn lamp state based on the time difference. Therefore, the time difference between the timing when the next turn lamp changes to the first turn lamp state and the timing when the next turn lamp indicator changes to the first indicator state corresponding to the first turn lamp state can be kept small. As a result, the discomfort felt by the user due to the time lag between the state change of the turn lamp and the state change of the turn lamp indicator can be reduced. Furthermore, the time difference between when the next turn lamp changes to the first turn lamp state and when the next turn lamp indicator changes to the first indicator state corresponding to the first turn lamp state can be kept small. As a result, it is possible to reduce the discomfort felt by the user due to the time difference between the state change of the turn lamp and the state change of the turn lamp indicator. [Effects of the Invention]

[0012] According to the present invention, the drawing processing unit calculates the time difference between the start timing of reception of the current first indicator signal corresponding to the current control of the turn lamp to the first turn lamp state and the completion timing of the current drawing processing, and predicts the start timing of the next predetermined processing including the next drawing processing for drawing the turn lamp indicator in the first indicator state corresponding to the next control of the turn lamp to the first turn lamp state based on the time difference. Therefore, it is possible to minimize the time difference between the timing when the next turn lamp changes to the first turn lamp state and the timing when the next turn lamp indicator changes to the first indicator state corresponding to the first turn lamp state. As a result, it is possible to reduce the discomfort felt by the user due to the time lag between the state change of the turn lamp and the state change of the turn lamp indicator. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating the configuration of a vehicle control device according to an embodiment of the present invention. [Figure 2] 2 is a processing sequence for turning on and off turn lamps and blinking turn lamp indicators by the vehicle control device of FIG. 1. [Figure 3] This is a processing sequence that follows the processing sequence of FIG. [Figure 4] This is a processing sequence subsequent to the processing sequence of FIG. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

[0015] First, the configuration of a vehicle control device 1 according to one embodiment of the present invention will be described with reference to Fig. 1. The vehicle control device 1 is mounted on a vehicle and causes a turn lamp indicator 33a to flash in response to turning on and off of a turn lamp 20.

[0016] As shown in Fig. 1, the vehicle control device 1 includes a body ECU 10, turn lamps 20, a meter 30, a turn lamp switch 15, and a CAN (Controller Area Network) 40. As shown in Fig. 1, the meter 30 includes an MCU (Micro Controller Unit) 31, an SoC (System-on-a-chip) 32, and a display 33, and the display 33 displays a turn lamp indicator 33a that indicates whether the turn lamps 20 are on or off by flashing. The body ECU 10 and the MCU 31 are each connected to a CAN 40. The CAN 40 corresponds to the "network" of the present invention.

[0017] The vehicle control device 1 has a left turn lamp corresponding to a left turn and a right turn lamp corresponding to a right turn, as well as a left turn lamp indicator corresponding to the left turn lamp and a right turn lamp indicator corresponding to the right turn lamp. However, since the control of the left turn lamp and the left turn lamp indicator and the control of the right turn lamp and the right turn lamp indicator are the same in terms of the characteristics in this embodiment, in this embodiment, to simplify the description, they will be collectively referred to as the turn lamp 20 and the turn lamp indicator 33a.

[0018] The body ECU 10 is connected to the CAN 40 and is capable of performing CAN communication with devices such as the MCU 31 of the meter 30 that are connected to the CAN 40. In this embodiment, when the body ECU 10 receives an operation to turn on the turn lamp switch 15 from a user (such as a driver) of the vehicle equipped with the vehicle control device 1, the body ECU 10 controls the turn lamp 20 so that the turn lamp 20 is repeatedly turned on and off by repeatedly energizing and de-energizing an LED 21 (described later) that the turn lamp 20 is equipped with. In this embodiment, when the body ECU 10 controls the turn lamps 20 to be turned on, it uses the CAN 40 to transmit an indicator signal (hereinafter also referred to as an "indicator on drawing signal") related to drawing the turn lamp indicators 33a in an on state (hereinafter also referred to as an "indicator on state") to the MCU 31 of the meter 30. When the body ECU 10 controls the turn lamps 20 to be turned off, it uses the CAN 40 to transmit an indicator signal (hereinafter also referred to as an "indicator off drawing signal") related to drawing the turn lamp indicators 33a in an off state (hereinafter also referred to as an "indicator off state") to the MCU 31 of the meter 30. The body ECU 10 corresponds to the "control unit" of the present invention. The indicator signal corresponds to the "indicator signal" of the present invention, the indicator on signal corresponds to the "first indicator signal" or the "second indicator signal" of the present invention, and the indicator off signal corresponds to the "second indicator signal" or the "first indicator signal" of the present invention.

[0019] The turn lamp 20 is configured to include an LED 21. When the LED 21 is energized, the LED 21 emits light, and the turn lamp 20 is turned on. When the LED 21 is not energized (when the LED 21 is not energized), the LED 21 does not emit light (does not emit light), and the turn lamp 20 is turned off. The body ECU 10 controls energization and de-energization of the LED 21. When the turn lamp switch 15 is on, energization and de-energization are repeated (for example, energization time 340 ms, de-energization time 340 ms, energization time 340 ms, de-energization time 340 ms, energization time 340 ms, de-energization time 340 ms, energization time 340 ms, de-energization time 340 ms, energization time 340 ms, de-energization time 340 ms, energization time 340 ms, de-energization time 340 ms, ...), and the LED 21 repeatedly emits and does not emit light, thereby repeatedly turning on and off the turn lamp 20. When the turn lamp switch 15 is off, the LED 21 remains de-energized, the LED 21 does not emit light, and the turn lamp 20 remains off. In addition, the turn lamp 20 corresponds to the "turn lamp" of the present invention, the lighting of the turn lamp 20 corresponds to the "first turn lamp state" or "second turn lamp state" of the present invention, and the turning off of the turn lamp 20 corresponds to the "second turn lamp state" or "first turn lamp state" of the present invention.

[0020] The MCU 31 is, for example, an in-vehicle RH850 MCU. The MCU 31 is connected to a CAN 40 and is capable of CAN communication with devices such as the body ECU 10 connected to the CAN 40. The MCU 31 is also capable of communication with the SoC 32 via SPI (Serial Peripheral Interface), which is a type of clock-synchronous serial interface (SPI communication).

[0021] The SoC32 is capable of performing SPI communication with the MCU 31. The SoC32 is also capable of performing communication (LVDS communication) with the display 33 using LVDS (Low Voltage Differential Signaling), which is one of the low-voltage differential transmission methods.

[0022] In this embodiment, with regard to SPI communication, the MCU 31 is on the master side and the SoC is on the slave side. The MCU 31 counts the SPI synchronous clock (Serial Clock: SCLK) (this count may also be referred to as "SPI msg count (MCU)"). The SoC 32 counts the SPI synchronous clock (this count may also be referred to as "SPI msg count (SoC)"). In this embodiment, the value of the SPI msg count (MCU) and the value of the SPI msg count (SoC) are the same at the same timing. In this embodiment, the clock period of the SCLK is 10 ms, but this is just an example and other clock periods may be used.

[0023] The following processing is performed by the MCU 31 and the SoC 32. Based on the value of the SPI msg count (MCU) at the start of reception of the indicator light drawing signal by the MCU 31 and the value of the SPI msg count (SoC) at the completion of the drawing process by the SoC 32, which corresponds to the current control by the body ECU 10 to turn on the turn lamps 20, the body ECU 10 calculates a time difference TA (see FIG. 2) between the completion timing of the drawing process by the SoC 32 and the start timing of reception of the indicator light drawing signal by the MCU 31. Because the SoC 32 cannot grasp the time difference TB (see FIG. 2) between the completion timing of the drawing process by the SoC 32 and the completion timing of the vertical synchronization (V-Sync) display process for displaying the turn lamp indicators 33a on the display 33 with the indicators turned on (the display timing at which the turn lamp indicators 33a are displayed on the display 33 with the indicators turned on), the body ECU 10 calculates a time difference TA+TB between the display timing at which the turn lamp indicators 33a are displayed with the indicators turned on and the start timing of reception of the indicator light drawing signal by the MCU 31. The body ECU 10 predicts the start timing of the next predetermined process (including received data notification process, shared memory storage process, and drawing process) including the next drawing process related to the indicator lighting state, so that the timing at which the next turn lamp indicator 33a corresponding to the next control to turn on the turn lamp 20 is displayed on the display 33 with the indicator lighting state is shorter by a time difference TA+TB than the time length TP×2 for one cycle of turning on and off the turn lamp 20. However, depending on the value of TA+TB (positive, 0, negative), the time during which the turn lamp indicator 33a is displayed with the indicator off may be shorter, the same as, or longer than the off time TP of the turn lamp 20. Details of this process will be described with reference to FIGS. 2 to 4.

[0024] Based on the value of the SPI msg count (MCU) at the start of reception of the indicator-off drawing signal by the MCU 31 and the value of the SPI msg count (SoC) at the completion of the drawing process by the SoC 32, which corresponds to the current control by the body ECU 10 to turn off the turn lamps 20, the body ECU 10 calculates a time difference Ta (see FIG. 3) between the completion timing of the drawing process by the SoC 32 and the start timing of reception of the indicator-off drawing signal by the MCU 31. Since the time difference Tb (see FIG. 3) between the completion timing of the drawing process by the SoC 32 and the completion timing of the vertical synchronization (V-Sync) display process for displaying the turn lamp indicators 33a on the display 33 in the indicator-off state (the display timing at which the turn lamp indicators 33a are displayed in the indicator-off state) is not known by the SoC 32, in this embodiment, it is set to a predetermined constant. The body ECU 10 calculates a time difference Ta+Tb between the display timing at which the turn lamp indicators 33a are displayed in the indicator-off state and the start timing of reception of the indicator-off drawing signal by the MCU 31. The body ECU 10 predicts the start timing of the next predetermined process (including received data notification process, shared memory storage process, and drawing process) including the next drawing process related to the indicator off state so that the timing of the next display of the turn lamp indicator 33a on the display 33 in the indicator off state corresponding to the next control to turn off the turn lamp 20 is shorter by a time difference Ta+Tb than the time length TP×2 for one cycle of turning on and off the turn lamp 20. However, depending on the value of Ta+Tb (positive, 0, negative), the time during which the turn lamp indicator 33a is displayed in the indicator on state may be shorter, the same as, or longer than the turn lamp 20 lighting time TP. Details of this process will be described with reference to FIGS. 2 to 4.

[0025] The MCU 31 and the SoC 32 correspond to the "drawing processing unit" of the present invention.

[0026] The display 33 is, for example, a TFT liquid crystal display (Thin Film Transistor liquid crystal display), etc. The display 33 is capable of performing LVDS communication with the SoC 32.

[0027] A turn lamp indicator 33a is displayed on the display 33. The indicator states of the turn lamp indicator 33a include a state (indicator on state) in which the turn lamp indicator 33a is displayed (lit) corresponding to the lighting of the turn lamp 20, and a state (indicator off state) in which the turn lamp indicator 33a is not displayed (off) corresponding to the lighting of the turn lamp 20. When the turn lamp switch 15 is on, the turn lamp indicator 33a alternates between the indicator on state and the indicator off state in response to the repeated lighting and off of the turn lamp 20. When the turn lamp switch 15 is off, the turn lamp indicator 33a remains in the indicator off state in response to the turn lamp 20 remaining off. The turn lamp indicator 33a corresponds to the "turn lamp indicator" of the present invention. The indicator state corresponds to the "indicator state" of the present invention, the indicator on state corresponds to the "first indicator state" or "second indicator state" of the present invention, and the indicator off state corresponds to the "second indicator state" or "first indicator state" of the present invention.

[0028] Next, a processing sequence for turning on and off the turn lamp 20 and blinking the turn lamp indicator 33a by the vehicle control device 1 will be described with reference to Figures 2 to 4. Note that the values ​​used in Figures 2 to 4 are merely examples and other values ​​may be used.

[0029] When the turn lamp switch 15 is changed from off to on by a user operation, the body ECU 10 controls the turn lamp 20 to be repeatedly turned on and off, and as shown in FIG. 2, first, the body ECU 10 turns on the turn lamp 20 by passing electricity through the LED 21 to cause the LED 21 to emit light (step S1).

[0030] In conjunction with turning on the turn lamp 20, the body ECU 10 transmits an indicator lighting drawing signal, the payload of which includes data relating to the indicator lighting state of the turn lamp indicator 33a (indicator lighting drawing data), to the MCU 31 of the meter 30 via CAN communication (step S2).

[0031] The MCU 31 counts the SPI synchronous clock (having a period of 10 ms in this embodiment) (SPI msg count(MCU)), and the SoC 32 counts the SPI synchronous clock (SPI msg count(SoC)). In this embodiment, the value of the SPI msg count(MCU) and the value of the SPI msg count(SoC) are the same at the same timing.

[0032] The MCU 31 receives the indicator light drawing signal from the body ECU 10 via CAN communication (step S3). In step S3, the value of the SPI msg count (MCU) when reception of the indicator light drawing signal starts (hereinafter, this may be referred to as the "MCU count value at the start of reception of the indicator light drawing signal") is held. In this processing sequence, the MCU count value at the start of reception of the indicator light drawing signal is 1. The MCU 31 extracts payload data (such as indicator light drawing data) of the indicator light drawing signal received in step S3 (step S4). The MCU 31 performs SPI polling to make the SoC 32 the partner of SPI communication (step S5).

[0033] Signals are transmitted and received between the MCU 31 and the SoC 32 via SPI communication (SPI transmission / reception processing) (step S6). In step S6, the MCU 31 transmits to the SoC 32 a signal (hereinafter also referred to as the "indicator light drawing·MCU count value signal") including data related to the indicator lighting state of the turn lamp indicator 33a (indicator light drawing data) and data indicating the MCU count value at the start of receiving the indicator light drawing signal held in step S3 (hereinafter also referred to as the "MCU count value data at the start of receiving the indicator light drawing signal"). A functional unit that performs communication processing in the SoC 32 receives the indicator light drawing·MCU count value signal from the MCU 31. The MCU count value at the start of receiving the indicator light drawing signal (the value of SPI msg count(MCU) when the MCU 31 started receiving the indicator light drawing signal in step S3) sent in the indicator light drawing·MCU count value signal is held and used in the lighting timing prediction processing (step S25). The maximum number of retries for the SPI transmission / reception processing is 3.

[0034] The functional unit that performs communication processing of SoC32 performs received data notification processing to notify the functional unit that performs control processing of SoC32 of the received data (data sent via the received indicator lighting drawing / MCU count value signal) (step S7). Also, in step S7, the value of the SPI msg count (SoC) at the start of the received data notification processing (hereinafter sometimes referred to as the "SoC count value at the start of indicator lighting related received data notification processing") is held. In this processing sequence, the SoC count value at the start of indicator lighting related received data notification processing is 14. The functional unit that performs control processing of SoC32 stores the notified received data in shared memory (step S8).

[0035] The functional unit that performs control processing of the SoC 32 performs drawing processing, such as generating drawing data for drawing the turn lamp indicator 33a on the display 33 with the indicator lit (step S9). Also, in step S9, the value of the SPI msg count (SoC) when the drawing processing is completed (hereinafter, sometimes referred to as the "SoC count value at the completion of the indicator lit drawing processing") is held. In this processing sequence, the SoC count value at the completion of the indicator lit drawing processing is 21.

[0036] SoC32 performs LVDS polling to make display 33 the other party of LVDS communication (step S10). Signals are transmitted and received between SoC32 and display 33 by LVDS communication (LVDS transmission and reception processing) (step S11). In step S11, SoC32 transmits a video signal including drawing data and the like to display 33, and display 33 receives the video signal from SoC32.

[0037] The display 33 displays the turn lamp indicator 33a on the display screen of the display 33 in a lit state in vertical synchronization (V-Sync) based on the drawing data included in the video signal (step S12).

[0038] In this processing sequence, the time length TP x 2 for one cycle of turning on and off the turn lamp 20 (the total time of the turning on time TP of one turn lamp 20 and the turning off time TP of one turn lamp 20) is set to 680 ms, the turning on time TP of one turn lamp 20 is set to 340 ms, and the turning off time TP of one turn lamp 20 is set to 340 ms.

[0039] When the lighting time TP=340 ms of the turn lamp 20 has elapsed since the turn lamp 20 was turned on, the body ECU 31 turns off the turn lamp 20 by stopping the supply of electricity to the LED 21 and preventing the LED 21 from emitting light, as shown in FIG. 3 (step S13).

[0040] In conjunction with turning off the turn lamp 20, the body ECU 10 transmits an indicator off drawing signal, the payload of which includes data relating to the indicator off state of the turn lamp indicator 33a (indicator off drawing data), to the MCU 31 of the meter 30 via CAN communication (step S14).

[0041] The MCU 31 receives the indicator-off drawing signal from the body ECU 10 via CAN communication (step S15). In step S15, the value of the SPI msg count (MCU) when reception of the indicator-off drawing signal starts (hereinafter, this may be referred to as the "MCU count value at the start of reception of the indicator-off drawing signal") is held. In this processing sequence, the MCU count value at the start of reception of the indicator-off drawing signal is 35. The MCU 31 extracts payload data (such as indicator-off drawing data) of the indicator-off drawing signal received in step S15 (step S16). The MCU 31 performs SPI polling to make the SoC 32 the partner of SPI communication (step S17).

[0042] Signals are transmitted and received between the MCU 31 and the SoC 32 via SPI communication (SPI transmission and reception processing) (step S18). In step S18, the MCU 31 transmits to the SoC 32 a signal (hereinafter also referred to as an "indicator-off drawing·MCU count value signal") including data related to the indicator-off state of the turn lamp indicator 33a (indicator-off drawing data) and data indicating the MCU count value at the start of receiving the indicator-off drawing signal held in step S15 (hereinafter also referred to as "MCU count value data at the start of receiving the indicator-off drawing signal"). A functional unit that performs communication processing in the SoC 32 receives the indicator-off drawing·MCU count value signal from the MCU 31. The MCU count value at the start of receiving the indicator-off drawing signal sent in the indicator-off drawing·MCU count value signal (the value of SPI msg count(MCU) when the MCU 31 started receiving the indicator-off drawing signal in step S15) is held and used in the light-off timing prediction processing (step S38). The maximum number of retries for SPI transmission / reception processing is 3.

[0043] The functional unit that performs communication processing of SoC32 performs received data notification processing to notify the functional unit that performs control processing of SoC32 of the received data (data sent via the received indicator-off drawing / MCU count value signal) (step S19). Also, in step S19, the value of the SPI msg count (SoC) at the start of the received data notification processing (hereinafter sometimes referred to as the "SoC count value at the start of the indicator-off related received data notification processing") is retained. In this processing sequence, the SoC count value at the start of the indicator-off related received data notification processing is 48. The functional unit that performs control processing of SoC32 stores the notified received data in shared memory (step S20).

[0044] The functional unit that performs control processing of the SoC 32 performs drawing processing, such as generating drawing data for drawing the turn lamp indicator 33a on the display 33 with the indicator turned off (step S21). Also, in step S21, the value of the SPI msg count (SoC) when the drawing processing is completed (hereinafter, sometimes referred to as the "SoC count value at the completion of the indicator turned off drawing processing") is held. In this processing sequence, the SoC count value at the completion of the indicator turned off drawing processing is 55.

[0045] SoC32 performs LVDS polling to make the display 33 the other party of LVDS communication (step S22). Signals are transmitted and received between SoC32 and display 33 by LVDS communication (LVDS transmission and reception processing) (step S23). In step S23, SoC32 transmits a video signal including drawing data and the like to display 33, and display 33 receives the video signal from SoC32.

[0046] The display 33 displays the turn lamp indicator 33a on the display screen of the display 33 in a state where the indicator is turned off in vertical synchronization (V-Sync) based on the drawing data included in the video signal (step S24).

[0047] The SoC 32 performs a lighting timing prediction process to calculate the timing when the next turn lamp indicator 33a is turned on (hereinafter, also referred to as "next turn lamp indicator lighting timing") (step S25). The lighting timing prediction process in step S25 is performed as follows.

[0048] The lighting time TP of the turn lamp 20 (the time from when the turn lamp 20 is turned on in step S1 to when it is turned off in step S13) is calculated. In this processing sequence, the lighting time TP of the turn lamp 20 is calculated as (35-1)×10=340 ms using the MCU count value at the start of receiving the indicator lighting signal sent from the MCU 31 in step S6=1, the MCU count value at the start of receiving the indicator turning-off signal sent from the MCU 31 in step S18=35, and the time length of one cycle of the synchronization clock=10 ms. In this embodiment, the lighting time TP of the turn lamp 20 is set to the lighting time TP of the turn lamp 20=the lighting time TP of the turn lamp 20, and therefore the lighting time TP of the turn lamp 20 is calculated as 340 ms from the lighting time TP of the turn lamp 20=340 ms.

[0049] It should be noted that a process for calculating the lighting time TP and the extinguishing time TP is performed when a plurality of cycles for turning on and off the turn lamp 20 are prepared. On the other hand, when only one cycle for turning on and off the turn lamp 20 is prepared, the lighting time TP and the extinguishing time TP may be set in advance in the SoC 32 and the set lighting time TP and extinguishing time TP may be used without performing the calculation process for calculating the lighting time TP and the extinguishing time TP, or the lighting time TP and the extinguishing time TP may be calculated.

[0050] In step S9, the time difference TA is calculated by subtracting the reception start timing at which the MCU 31 started receiving the indicator light drawing signal in step S3 from the completion timing at which the drawing process by the SoC 32 was completed. The time difference TA = (21 - 1 + 1) × 10 = 210 ms is calculated using the MCU count value at the start of reception of the indicator light signal sent from the MCU 31 in step S6 = 1, the SoC count value at the completion of the indicator light drawing process held in step S9 = 21, and the time length of one cycle of the synchronous clock = 10 ms.

[0051] A time difference TB is calculated by delaying the completion timing of the vertical synchronization (V-Sync) display process in step S12 (the display timing when the turn lamp indicator 33a is displayed on the display 33 with the indicator lit) from the completion timing of the drawing process by the SoC 32 in step S9. In this processing sequence, the time difference TB is calculated as 22 ms (constant) assuming that the time difference TB=22 ms.

[0052] The time difference TA+TB between the two is calculated by subtracting the reception start timing at which the MCU 31 started receiving the indicator lighting drawing signal in step S3 from the display timing at which the turn lamp indicator 33a is displayed on the display 33 with the indicator lighting state. In this processing sequence, the time difference TA=210 ms and the time difference TB=22 ms are used to calculate the time difference TA+TB=210+22=232 ms.

[0053] The timing for next turning on the turn lamp indicator 33a is predicted, and the start timing of predetermined processing related to the next indicator lighting state (the predetermined processing includes received data notification processing, shared memory storage processing, and drawing processing) is calculated and the predetermined processing is started so that the time from when the turn lamp indicator 33a is currently turned on until when it next turns on is shorter by the time difference TA+TB than the time length TP×2 for one cycle of turning on and off the turn lamp 20. In this processing sequence, the time TAB from when the turn lamp indicator 33a is currently turned on until when it next turns on is calculated as follows: time TAB = time length TP×2 for one cycle of turning on and off the turn lamp 20 - time difference (TA+TB) = 680 - 232 = 448 ms, using the time length TP×2 = 680 ms for one cycle of turning on and off the turn lamp 20 and the time difference TA+TB = 232 ms. In this processing sequence, the time TC during which the turn lamp indicator 33a is displayed in the indicator-off state (hereinafter sometimes referred to as "indicator-off time") is calculated as follows: indicator-off time TC = off time TP - time difference (TA + TB) = 340 - 232 = 108 ms, which is 232 ms shorter than the off time TP of the turn lamp 20. Note that depending on the value of the time difference TA + TB (positive, 0, negative), the indicator-off time TC of the turn lamp indicator 33a may be shorter, the same as, or longer than the off time TP of the turn lamp 20.

[0054] In this processing sequence, the SoC 32 starts the processing for setting the next turn lamp indicator 33a to the indicator lighting state from the received data notification processing (step S26), so the start of the received data notification processing (step S26) is delayed by a time TAB of 448 ms from the start of the received data notification processing (step S7). In this processing sequence, using the SoC count value at the start of the indicator lighting-related received data notification processing (held in step S7) of 14, the time length of one synchronous clock cycle of 10 ms, and the time TAB of 448 ms, it is determined that the received data notification processing (step S26) will be started at SPI msg count(SoC) of 58 or 59 at the 44th or 45th synchronous clock after the start of the received data notification processing in step S7. In this processing sequence, it is determined that the received data notification processing (step S26) will be started at SPI msg count(SoC) of 59 at the 45th synchronous clock.

[0055] As shown in FIG. 4, the functional unit that performs communication processing of SoC32 has not received the indicator lighting drawing·MCU count value signal that will be received in conjunction with the next lighting of the turn lamp 20 at the timing when the SPI msg count (SoC) value is 59. However, the functional unit that performs control processing of SoC32 performs received data notification processing to notify the functional unit that performs control processing of the indicator lighting drawing data and the like that will be received by the indicator lighting drawing·MCU count value signal as received data (step S26). Also, in step S26, the value of SPI msg count (SoC) at the start of the received data notification processing (SoC count value at the start of the indicator lighting related received data notification processing) is held. In this processing sequence, the SoC count value at the start of the indicator lighting related received data notification processing is 59. The functional unit that performs control processing of SoC32 stores the notified received data in the shared memory (step S27).

[0056] The functional unit that performs control processing of the SoC 32 performs drawing processing, such as generating image data for drawing the turn lamp indicator 33a on the display 33 with the indicator lit (step S28). Also, in step S28, the value of the SPI msg count(SoC) when the drawing processing is completed (the SoC count value at the completion of the indicator lit drawing processing) is held. In this processing sequence, the SoC count value at the completion of the indicator lit drawing processing is 66.

[0057] SoC32 performs LVDS polling to make display 33 the other party of LDVS communication (step S29). Signals are transmitted and received between SoC32 and display 33 by LDVS communication (LVDS transmission and reception processing) (step S30). In step S30, SoC32 transmits a video signal including drawing data and the like to display 33, and display 33 receives the video signal from SoC32.

[0058] The display 33 displays the turn lamp indicator 33a on the display screen of the display 33 in a lighting state in vertical synchronization (V-Sync) based on the drawing data included in the video signal (step S31).

[0059] When the turn lamp 20 extinguishing time TP=340 ms has elapsed since the body ECU 31 turned off the turn lamp 20, the body ECU 31 energizes the LED 21 to cause the LED 21 to emit light, thereby turning on the turn lamp 20 (step S32).

[0060] In conjunction with turning on the turn lamp 20, the body ECU 31 transmits an indicator lighting drawing signal, the payload of which includes data relating to the indicator lighting state of the turn lamp indicator 33a (indicator lighting drawing data), to the MCU 31 of the meter 30 via CAN 40 communication (step S33).

[0061] The MCU 31 receives the indicator light drawing signal from the body ECU 10 via CAN communication (step S34). In step S34, the value of the SPI msg count (MCU) when reception of the indicator light drawing signal starts (the MCU count value when reception of the indicator light drawing signal starts) is held. In this processing sequence, the MCU count value when reception of the indicator light drawing signal starts is 69. The MCU 31 extracts payload data (such as indicator light drawing data) of the indicator light drawing signal received in step S34 (step S35). The MCU 31 performs SPI polling to make the SoC 32 the partner of SPI communication (step S36).

[0062] Signals are transmitted and received between the MCU 31 and the SoC 32 via SPI communication (SPI transmission and reception processing) (step S37). In step S37, the MCU 31 transmits to the SoC 32 a signal (indicator light drawing·MCU count value signal) including data related to the indicator lighting state of the turn lamp indicator 33a (indicator light drawing data) and data indicating the MCU count value at the start of receiving the indicator light drawing signal (MCU count value data at the start of receiving the indicator light drawing signal) held in step S34. A functional unit that performs communication processing in the SoC 32 receives the indicator light drawing·MCU count value signal from the MCU 31. The MCU count value at the start of receiving the indicator light drawing signal (the value of SPI msg count(MCU) when the MCU 31 started receiving the indicator light drawing signal in step S34) sent in the indicator light drawing·MCU count value signal is held and used in lighting timing prediction processing that sets the turn lamp indicator 33a to the indicator lighting state in accordance with the lighting of the turn lamp 20 next to the lighting of the turn lamp 20 in step S32. The maximum number of retries for SPI transmission / reception processing is three.

[0063] The processes corresponding to the SPI transmission / reception process in step S37 from the received data notification process to the vertical synchronization (V-Sync) display process are the received data notification process in step S26 to the vertical synchronization (V-Sync) display process in step S31.

[0064] The SoC 32 performs a turn-off timing prediction process to calculate the timing when the next turn lamp indicator 33a is turned off (hereinafter, this may be referred to as "next turn lamp indicator turn-off timing") (step S38). The turn-off timing prediction process in step S38 is performed as follows.

[0065] The turn lamp 20 extinguishing time TP (the time from when the turn lamp 20 is turned off in step S13 to when it is turned on in step S32) is calculated. In this processing sequence, the turn lamp 20 extinguishing time TP = (69 - 35) × 10 = 340 ms is calculated using the MCU count value at the start of receiving the indicator turn-off signal sent from the MCU 31 in step S18 = 35, the MCU count value at the start of receiving the indicator turn-on signal sent from the MCU 31 in step S37 = 69, and the time length of one cycle of the synchronous clock = 10 ms. In this embodiment, the turn lamp 20 extinguishing time TP = the turn lamp 20 lighting time TP, and so the turn lamp 20 lighting time TP = 340 ms is calculated from the turn lamp 20 extinguishing time TP = 340 ms.

[0066] In step S21, the time difference Ta is calculated by subtracting the reception start timing at which the MCU 31 started receiving the indicator-turn-off drawing signal in step S15 from the completion timing at which the drawing process by the SoC 32 was completed. Using the MCU count value at the start of reception of the indicator-turn-off signal sent from the MCU 31 in step S18 = 35, the SoC count value at the completion of the indicator-turn-off drawing process held in step S21 = 55, and the time length of one cycle of the synchronous clock = 10 ms, the time difference Ta = (55 - 35 + 1) × 10 = 210 ms is calculated.

[0067] A time difference Tb is calculated between the completion timing of the vertical synchronization (V-Sync) display process in step S24 (the display timing when the turn lamp indicator 33a is displayed on the display 33 with the indicator turned off) and the completion timing of the drawing process by the SoC 32 in step S21. In this processing sequence, the time difference Tb is calculated as 22 ms (constant).

[0068] The time difference Ta+Tb between the display timing at which the turn lamp indicator 33a is displayed in the indicator-off state and the reception start timing at which the MCU 31 started receiving the indicator-off drawing signal in step S15 is calculated. In this processing sequence, the time difference Ta=210 ms and the time difference Tb=22 ms are used to calculate the time difference Ta+Tb=210+22=232 ms.

[0069] The timing for next turning the turn lamp indicator 33a into the indicator-off state is predicted, and the start timing of predetermined processing related to the next indicator-off state (the predetermined processing includes received data notification processing, shared memory storage processing, and drawing processing) is calculated and the predetermined processing is started so that the time from when the turn lamp indicator 33a is currently turned into the indicator-off state until when it next turns into the indicator-off state is shorter by the time difference Ta+Tb than the time length TP×2 for one cycle of turning on and off the turn lamp 20. In this processing sequence, the time Tab from when the turn lamp indicator 33a is currently turned into the indicator-off state until when it next turns into the indicator-off state is calculated as follows: time Tab = time length TP×2 for one cycle of turning on and off the turn lamp 20 - time difference (Ta+Tb) = 680 - 232 = 448 ms, using the time length TP×2 = 680 ms for one cycle of turning on and off the turn lamp 20 and the time difference Ta+Tb = 232 ms.

[0070] In this processing sequence, the SoC 32 starts the processing for turning the next turn lamp indicator 33a to the indicator-off state from the received data notification processing (herein referred to as the "next received data notification processing"), so that the start of the next received data notification processing is delayed by a time Tab = 448 ms from the start of the received data notification processing (step S19). In this processing sequence, using the SoC count value at the start of the indicator-turn-off related received data notification processing = 48, the time length of one synchronous clock cycle = 10 ms, and the time Tab = 448 ms held in step S19, it is determined that the next received data notification processing will be started at SPI msg count(SoC) = 92 or 93 at the 44th or 45th synchronous clock after the start of the received data notification processing in step S19. In this processing sequence, it is determined that the next received data notification processing will be started at SPI msg count(SoC) = 93 at the 45th synchronous clock.

[0071] Note that, for subsequent timing control of changing the turn lamp indicator 33a to the indicator-on state, a lighting timing prediction process similar to the lighting timing prediction process of step S25 is performed. For example, in the lighting timing prediction process of changing the turn lamp indicator 33a to the indicator-on state in accordance with the lighting of the turn lamp 20 next to the lighting of the turn lamp 20 in step S32, the lighting timing prediction process is performed using the MCU count value = 69 at the start of reception of the indicator lighting drawing signal received by the SoC 32 in step S37, the SoC count value = 66 at the completion of the indicator lighting drawing process held when the drawing process is completed in step S28, and the like. Furthermore, for subsequent timing control of changing the turn lamp indicator 33a to the indicator-off state, a lighting timing prediction process similar to the lighting timing prediction process of step S38 is performed.

[0072] According to the above-described embodiment, the blinking timing of the turn lamp indicator 33a corresponding to the turning on / off timing of the turn lamp 20 is controlled using the time differences TA, Ta from when the MCU 31 starts receiving the indicator on / off signal or the indicator off signal until the SoC 32 completes the drawing process, and the time differences TB, Tb from when the SoC 32 completes the drawing process until the indicator is displayed in the on state or the indicator off state on the display (when the vertical synchronization (V-Sync) display process is completed), thereby making it possible to minimize the time difference between the turning on / off timing of the turn lamp 20 and the blinking timing of the turn lamp indicator 33a. As a result, it is possible to reduce the discomfort felt by the user due to the time difference between the turning on / off timing of the turn lamp 20 and the blinking timing of the turn lamp indicator 33a.

[0073] In addition, various design modifications can be made to the above-described configuration within the scope of the claims.

[0074] For example, in the above embodiment, the time difference TA is calculated based on the value of SPI msg count(MCU) when the MCU 31 starts receiving the indicator lighting signal and the value of SPI msg count(SoC) when the SoC 32 completes the drawing process, but this is not limiting and, for example, the time difference TA may be a predetermined constant. Note that since the time difference TB is also a predetermined constant, the constants for the time difference TA and the time difference TB may be predetermined, or a constant may be predetermined as the sum of the time difference TA and the time difference TB, i.e., TA+TB.

[0075] Furthermore, in the above embodiment, the indicator state of the turn lamp indicator 33a is displayed (lit) when the turn lamp 20 is lit, and is not displayed (off) when the turn lamp 20 is off, but this is not limited to this, and for example, it may be displayed brightly (lit brightly) when the turn lamp 20 is lit, and displayed dimly (lit dimly) when the turn lamp 20 is lit.

[0076] Furthermore, the contents described in the above embodiment and the contents described in the above modified examples may be combined as appropriate.

[0077] The present invention is widely applicable to vehicle control devices that change a turn lamp indicator to an indicator state corresponding to a change in the turn lamp state of a turn lamp in response to the change in the turn lamp state of the turn lamp. [Explanation of symbols]

[0078] 1: Vehicle control device 10: Body ECU 15: Turn lamp switch 20: Turn lamp 21: LED 30: Meter 31:MCU 32:SoC 33: Display 33a: Turn lamp indicator 40:CAN

Claims

[Claim 1] Turn lamps and a display device having a display and a drawing processing unit that draws a turn lamp indicator on the display, the turn lamp indicator indicating the turn lamp state of the turn lamp by an indicator state; a control unit that receives a user's operation, controls the turn lamp state of the turn lamp, and transmits an indicator signal related to the indicator state of the turn lamp indicator to the display device via a network; A vehicle control device comprising: The turn lamp state includes a first turn lamp state and a second turn lamp state, the indicator states include a first indicator state corresponding to the first turn lamp state and a second indicator state corresponding to the second turn lamp state; the indicator signals include a first indicator signal associated with depicting the first indicator state and a second indicator signal associated with depicting the second indicator state; The drawing processing unit calculating a time difference between a reception start timing at which the control unit starts receiving the first indicator signal transmitted from the control unit in response to the current control of changing the turn lamp to the first turn lamp state, and a completion timing at which the drawing processing unit completes the current drawing process of drawing the turn lamp indicator to the first indicator state; performing a next predetermined process including a next drawing process for drawing the turn lamp indicator in the first indicator state, which corresponds to a next control of the turn lamp to the first turn lamp state, by predicting a start timing of the next predetermined process including the next drawing process based on the time difference; Based on the time difference, the next predetermined processing including the next drawing processing is performed so that the period of the second indicator state following the first indicator state drawn in the current predetermined processing including the current drawing processing is shorter than the period of one second turn lamp state of the turn lamp. A vehicle control device characterized by:

Images