JP7733054B2 - Vehicle control device - Google Patents

Description

The present invention relates to a vehicle control device that changes a turn lamp indicator to an indicator state (e.g., blinks) corresponding to a change in the turn lamp state (e.g., in response to turning on or off) of the turn lamp.

Conventionally, blinking devices have been provided with a blinking indicator, a monitor that displays graphics and images, 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 monitor control circuit. They also have 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, start blinking the monitor by a delay equal to one reference pulse period minus the processing time required for that predetermined process (see, for example, Patent Document 1).

JP 2013-114207 A

However, in order to synchronize the indicator with the monitor, the start of blinking on the monitor was delayed, which may cause discomfort to the user.

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. However, in order to reduce costs by eliminating this, the automotive industry is now moving to a system where 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 other devices, an increasing number of vehicles are displaying turn lamp indicators, which previously used LEDs, on their displays.

As such, when using CAN to display turn lamp indicators on a display, the CAN transmission cycle and the drawing process for drawing the turn lamp indicators on the display can cause a delay in the blinking of the turn lamp indicators relative to the turning on and off of the turn lamps, which can be a problem and can cause discomfort to the user.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a vehicle control device that can minimize 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 that predetermined turn lamp state (e.g., the timing at which it flashes).

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 states include 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 related to drawing the first indicator state and a second indicator signal related to drawing the second indicator state, and the drawing processing unit The control unit calculates 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 a current control of changing the turn lamp to the first turn lamp state and a completion timing at which the drawing processing unit completes a current drawing process of drawing the turn lamp indicator in the first indicator state, and performs a next predetermined process including a next drawing process of drawing the turn lamp indicator in 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 performs 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 .

According to this configuration, the rendering 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 rendering processing, and performs the next predetermined processing, including the next rendering processing for rendering the turn lamp indicator in the first indicator state corresponding to the next control of the turn lamp to the first turn lamp state, by predicting the start timing of the next predetermined processing, including the next rendering processing, based on the time difference. This makes it 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. Furthermore, 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.

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 performs the next predetermined processing, including the next drawing processing to draw the turn lamp indicator in the first indicator state corresponding to the next control of the turn lamp to the first turn lamp state, by predicting the start timing of the next predetermined processing, including the next drawing processing, based on the time difference. This makes it 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 sense of 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.

1 is a diagram illustrating the configuration of a vehicle control device according to an embodiment of the present invention. 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 . This is a processing sequence subsequent to the processing sequence of FIG. 2. This is a processing sequence subsequent to the processing sequence of FIG. 3.

One embodiment of the present invention will be described in detail below with reference to the accompanying drawings.

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

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. Also, as shown in FIG. 1, the meter 30 includes an MCU (Micro Controller Unit) 31, a SoC (System-on-a-chip) 32, and a display 33, which displays a turn lamp indicator 33a that flashes to indicate whether the turn lamps 20 are on or off. The body ECU 10 and MCU 31 are each connected to a CAN 40. The CAN 40 corresponds to the "network" in this invention.

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 left turn lamp indicator and the control of the right turn lamp and right turn lamp indicator are the same in terms of the features in this embodiment, in this embodiment, for the sake of simplicity, they will be collectively referred to as turn lamp 20 and turn lamp indicator 33a.

The body ECU 10 is connected to the CAN 40 and is capable of 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 a vehicle equipped with the vehicle control device 1, it controls the turn lamp 20 so that the turn lamp 20 is repeatedly turned on and off by repeatedly energizing and de-energizing the LEDs 21 (described below) provided in the turn lamp 20. In this embodiment, when the body ECU 10 controls the turn lamps 20 to be turned on, it uses the CAN 40 to send an indicator signal (hereinafter sometimes referred to as an "indicator on drawing signal") related to drawing the turn lamp indicator 33a in an on state (hereinafter sometimes referred to as the "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 send an indicator signal (hereinafter sometimes referred to as an "indicator off drawing signal") related to drawing the turn lamp indicator 33a in an off state (hereinafter sometimes referred to as the "indicator off state") to the MCU 31 of the meter 30. The body ECU 10 corresponds to the "controller" 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 "second indicator signal" of the present invention, and the indicator off signal corresponds to the "second indicator signal" or "first indicator signal" of the present invention.

The turn signal lamp 20 is configured to include an LED 21. When power is applied to the LED 21, the LED 21 emits light, turning the turn signal lamp 20 on. When power is not applied to the LED 21 (when the LED 21 is not energized), the LED 21 does not emit light (does not emit light), turning the turn signal lamp 20 off. The body ECU 10 controls the application and de-energization of the LED 21. When the turn signal lamp switch 15 is on, the LED 21 is repeatedly energized and de-energized (e.g., energized time 340 ms, de-energized time 340 ms, energized time 340 ms, de-energized time 340 ms, energized time 340 ms, de-energized time 340 ms, energized time 340 ms, de-energized time 340 ms, energized time 340 ms, de-energized time 340 ms, etc.), causing the LED 21 to repeatedly emit and de-energize, turning the turn signal lamp 20 on and off. Furthermore, when the turn lamp switch 15 is off, the LED 21 remains de-energized, does not emit light, and the turn lamp 20 remains off. Note that 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.

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

SoC32 is capable of SPI communication with MCU31. SoC32 is also capable of LVDS communication with display 33, which is a low-voltage differential signaling (LVDS) communication method.

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

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 lamp 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. The time difference TB (see FIG. 2) is the delay 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 indicator 33a on the display 33 with the indicator light on (the display timing at which the turn lamp indicator 33a is displayed on the display 33 with the indicator light on). This time difference TB is a predetermined constant in this embodiment because it cannot be determined by the SoC 32. The time difference TA+TB between the display timing of the turn lamp indicator 33a in the indicator-on state and the start timing of the reception of the indicator-on drawing signal by the MCU 31 is calculated. The timing at which the body ECU 10 displays the turn lamp indicator 33a in the indicator-on state on the display 33 next time, corresponding to the next control to turn the turn lamp 20 on, is predicted and the next predetermined process (including the received data notification process, the shared memory storage process, and the drawing process) including the next drawing process related to the indicator-on state is started so that the time from when the turn lamp indicator 33a is currently in the indicator-on state until the next time the indicator is in the indicator-on 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. However, depending on the value of TA+TB (positive, zero, negative), the time at which the turn lamp indicator 33a is displayed in the indicator-off state may be shorter, the same as, or longer than the turn lamp 20 off time TP. Details of this process will be described with reference to FIGS. 2 to 4.

Based on the value of the SPI msg count (MCU) at the start of receiving 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 lamp 20, the time difference Ta (see Figure 3) is calculated by subtracting the start of receiving the indicator-off drawing signal by the MCU 31 from the completion of the drawing process by the SoC 32. The time difference Tb (see Figure 3), which is the delay between the completion of the vertical synchronization (V-Sync) display process for displaying the turn lamp indicator 33a on the display 33 with the indicator off (the display timing at which the turn lamp indicator 33a is displayed with the indicator off) and the completion of the drawing process by the SoC 32, is a predetermined constant in this embodiment because it cannot be determined by the SoC 32. The time difference Ta+Tb between the display timing of the turn lamp indicator 33a in the indicator-off state and the start timing of receiving the indicator-off drawing signal from the MCU 31 is calculated. The start timing of the next predetermined process (including the received data notification process, the shared memory storage process, and the drawing process) including the next drawing process related to the indicator-off state is predicted and the predetermined process is started so that the timing when the next turn lamp indicator 33a is displayed on the display 33 in the indicator-off state corresponding to the next control by the body ECU 10 to turn the turn lamp 20 off 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. However, depending on the value of Ta+Tb (positive, 0, negative), the time when 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 period TP. Details of this process will be explained with reference to Figures 2 to 4.

Note that MCU31 and SoC32 correspond to the "drawing processing unit" of the present invention.

Display 33 is, for example, a TFT liquid crystal display (Thin Film Transistor liquid crystal display). Display 33 is capable of LVDS communication with SoC 32.

The display 33 displays a turn lamp indicator 33a. The indicator states of the turn lamp indicator 33a include a state in which the turn lamp indicator 33a is displayed (lit) (indicator on state), corresponding to the lighting of the turn lamp 20, and a state in which the turn lamp indicator 33a is not displayed (off), corresponding to the lighting of the turn lamp 20 (indicator off state). When the turn lamp switch 15 is on, the turn lamp indicator 33a alternates between the indicator on state and the indicator off state, corresponding to the repeated lighting and off of the turn lamp 20. Furthermore, when the turn lamp switch 15 is off, the turn lamp indicator 33a remains in the indicator off state, corresponding to the continued extinction of the turn lamp 20. Note that the turn lamp indicator 33a corresponds to the "turn lamp indicator" of the present invention. Furthermore, 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.

Next, the processing sequence for turning on and off the turn lamps 20 and flashing the turn lamp indicators 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.

When the turn lamp switch 15 is changed from off to on by user operation, the body ECU 10 controls the turn lamp 20 to repeatedly turn on and off. As shown in FIG. 2, the body ECU 10 first energizes the LED 21 to cause it to emit light, thereby turning on the turn lamp 20 (step S1).

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 related 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).

MCU31 counts the SPI synchronization clock (which has a period of 10 ms in this embodiment) (SPI msg count (MCU)), and SoC32 counts the SPI synchronization clock (SPI msg count (SoC)). In this embodiment, the value of SPI msg count (MCU) and the value of SPI msg count (SoC) are the same at the same timing.

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 begins is retained (hereinafter, this may be referred to as the "MCU count value at the start of reception of the indicator light drawing signal"). 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 the payload data (e.g., 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).

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

The functional unit that performs communication processing on SoC32 performs received data notification processing, notifying the functional unit that performs control processing on 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 the indicator lighting related received data notification processing") is retained. In this processing sequence, the SoC count value at the start of the indicator lighting related received data notification processing is 14. The functional unit that performs control processing on SoC32 stores the notified received data in shared memory (step S8).

The functional unit that performs control processing on 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 retained. In this processing sequence, the SoC count value at the completion of the indicator lit drawing processing is 21.

SoC32 performs LVDS polling to make display 33 the partner of LVDS communication (step S10). LVDS communication signals are sent and received between SoC32 and display 33 (LVDS sending and receiving processing) (step S11). In step S11, SoC32 sends a video signal including drawing data to display 33, and display 33 receives the video signal from SoC32.

Based on the drawing data contained in the video signal, the display 33 displays the turn lamp indicator 33a on the display screen of the display 33 using vertical synchronization (V-Sync) with the indicator lit (step S12).

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 one turn lamp 20 on time TP and one turn lamp 20 off time TP) is set to 680 ms, the turn lamp 20 on time TP for one turn lamp 20 is set to 340 ms, and the turn lamp 20 off time TP for one turn lamp 20 is set to 340 ms.

When the turn lamp 20 lighting time TP = 340 ms 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 Figure 3 (step S13).

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).

The MCU 31 receives the indicator-off drawing signal from the body ECU 10 via CAN communication (step S15). In step S15, the SPI msg count (MCU) value at the start of reception of the indicator-off drawing signal is retained (hereinafter, sometimes referred to as the "MCU count value at the start of reception of the indicator-off drawing signal"). 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 the payload data (e.g., 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).

Signals are sent and received between MCU31 and SoC32 via SPI communication (SPI sending and receiving processing) (step S18). In step S18, MCU31 sends to SoC32 a signal (hereinafter sometimes referred to as the "indicator off drawing/MCU count value signal") that includes 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 that was held in step S15 (hereinafter sometimes referred to as the "MCU count value data at the start of receiving the indicator off drawing signal"). The functional unit that performs communication processing in SoC32 receives the indicator off drawing/MCU count value signal from MCU31. The MCU count value at the start of receiving the indicator turn-off drawing signal sent in the indicator turn-off drawing MCU count value signal (the value of the SPI msg count (MCU) when MCU 31 starts receiving the indicator turn-off drawing signal in step S15) is retained and used in the turn-off timing prediction process (step S38). Note that the maximum number of retries for the SPI transmission/reception process is 3.

The functional unit that performs communication processing on SoC32 performs received data notification processing, notifying the functional unit that performs control processing on SoC32 of the received data (data sent via the received indicator extinguishing 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 extinguishing related received data notification processing") is retained. In this processing sequence, the SoC count value at the start of the indicator extinguishing related received data notification processing is 48. The functional unit that performs control processing on SoC32 stores the notified received data in shared memory (step S20).

The functional unit that performs control processing on 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 retained. In this processing sequence, the SoC count value at the completion of the indicator turned off drawing processing is 55.

SoC32 performs LVDS polling to make display 33 the partner of LVDS communication (step S22). LVDS communication signals are sent and received between SoC32 and display 33 (LVDS sending and receiving processing) (step S23). In step S23, SoC32 sends a video signal including drawing data to display 33, and display 33 receives the video signal from SoC32.

Based on the drawing data contained in the video signal, the display 33 displays the turn lamp indicator 33a on the display screen of the display 33 using vertical synchronization (V-Sync) with the indicator turned off (step S24).

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

The turn lamp 20 illumination time TP (the time from when the turn lamp 20 is illuminated in step S1 to when it is extinguished in step S13) is calculated. In this processing sequence, the MCU count value at the start of receiving the indicator illumination signal sent from the MCU 31 in step S6 is 1, the MCU count value at the start of receiving the indicator extinguishing signal sent from the MCU 31 in step S18 is 35, and the time length of one cycle of the synchronization clock is 10 ms. In this embodiment, the turn lamp 20 illumination time TP = the turn lamp 20 extinguishing time TP, so the turn lamp 20 extinguishing time TP = 340 ms is calculated from the turn lamp 20 illumination time TP = 340 ms.

Note that if multiple on/off cycles for the turn lamp 20 are provided, a process for calculating the on time TP and off time TP is performed. On the other hand, if only one on/off cycle for the turn lamp 20 is provided, the process for calculating the on time TP and off time TP may be omitted, and the on time TP and off time TP may be set in the SoC 32 in advance and the set on time TP and off time may be used, or the on time TP and off time TP may be calculated.

In step S9, the time difference TA is calculated by subtracting the start time when MCU31 started receiving the indicator light drawing signal in step S3 from the completion time when SoC32 completed the drawing process. Using the MCU count value at the start of reception of the indicator light signal sent from MCU31 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 synchronization clock = 10 ms, the time difference TA = (21 - 1 + 1) x 10 = 210 ms is calculated.

Calculate the time difference TB between 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) and 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).

The time difference TA + TB between the display timing of the turn lamp indicator 33a on the display 33 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 indicator is turned on. 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.

The system predicts the next timing for the turn lamp indicator 33a to be turned on so that the time from when the indicator 33a is currently turned on until the next time it is turned on is shorter by the time difference TA + TB than the time length TP x 2 for one cycle of the turn lamp 20 turning on/off. The system calculates the start timing of the specified processing related to the next indicator lighting state (including received data notification processing, shared memory storage processing, and drawing processing) and starts the specified processing. In this processing sequence, the time TAB from when the turn lamp indicator 33a is currently turned on until the next time it is turned on is calculated as follows: Time TAB = Time length TP x 2 for one cycle of the turn lamp 20 turning on/off - Time difference (TA + TB) = 680 - 232 = 448 ms, using the time length TP x 2 = 680 ms for one cycle of the turn lamp 20 turning on/off 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 the "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 can be shorter, the same as, or longer than the off time TP of the turn lamp 20.

In this processing sequence, the SoC 32 starts the process for turning the next turn lamp indicator 33a on with the received data notification process (step S26), so the start of the received data notification process (step S26) is delayed by a time TAB of 448 ms from the start of the received data notification process (step S7). In this processing sequence, using the SoC count value at the start of the indicator illumination-related received data notification process (stored in step S7) of 14, the time length of one synchronous clock cycle of 10 ms, and the time TAB of 448 ms, it determines to start the received data notification process (step S26) when the SPI msg count (SoC) is 58 or 59 on the 44th or 45th synchronous clock after the start of the received data notification process in step S7. In this processing sequence, it determines to start the received data notification process (step S26) when the SPI msg count (SoC) is 59 on the 45th synchronous clock.

As shown in FIG. 4, the communication processing functional unit of SoC 32 does not receive the indicator lighting drawing/MCU count value signal that would be received in conjunction with the next illumination of the turn signal 20 at the timing when the SPI msg count (SoC) value is 59. However, it performs received data notification processing to notify the control processing functional unit of SoC 32 of the indicator lighting drawing data and other data that would be received via the indicator lighting drawing/MCU count value signal as received data (step S26). Also, in step S26, the SPI msg count (SoC) value at the start of the received data notification processing (the SoC count value at the start of the indicator lighting related received data notification processing) is retained. In this processing sequence, the SoC count value at the start of the indicator lighting related received data notification processing is 59. The control processing functional unit of SoC 32 stores the notified received data in shared memory (step S27).

The functional unit that performs control processing on 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 retained. In this processing sequence, the SoC count value at the completion of the indicator lit drawing processing is 66.

SoC32 performs LVDS polling to make display 33 the partner of LDVS communication (step S29). LDVS communication signals are sent and received between SoC32 and display 33 (LVDS sending and receiving processing) (step S30). In step S30, SoC32 sends a video signal including drawing data to display 33, and display 33 receives the video signal from SoC32.

Based on the drawing data contained in the video signal, the display 33 displays the turn lamp indicator 33a on the display screen of the display 33 using vertical synchronization (V-Sync) with the indicator lit (step S31).

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).

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).

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 begins is retained (the MCU count value when reception of the indicator light drawing signal begins). In this processing sequence, the MCU count value when reception of the indicator light drawing signal begins is 69. The MCU 31 extracts the payload data (e.g., 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).

Signals are sent and received between MCU31 and SoC32 via SPI communication (SPI sending and receiving processing) (step S37). In step S37, MCU31 sends to SoC32 a signal (indicator lighting drawing/MCU count value signal) that includes data related to the indicator lighting state of turn lamp indicator 33a (indicator lighting drawing data) and data indicating the MCU count value at the start of receiving the indicator lighting drawing signal (MCU count value data at the start of receiving the indicator lighting drawing signal) that was held in step S34. The functional unit that performs communication processing in SoC32 receives the indicator lighting drawing/MCU count value signal from MCU31. The MCU count value at the start of receiving the indicator light drawing signal sent in the indicator light drawing/MCU count value signal (the value of the SPI msg count (MCU) when the MCU 31 starts receiving the indicator light drawing signal in step S34) is retained and used in the lighting timing prediction process that sets the turn lamp indicator 33a to the indicator lighting state in time with the lighting of the turn lamp 20 following the lighting of the turn lamp 20 in step S32. Note that the maximum number of retries for the SPI sending and receiving process is three.

Note that 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.

The SoC 32 performs a turn-off timing prediction process to calculate the timing at which the next turn lamp indicator 33a will be turned off (hereinafter, sometimes referred to as the "next turn lamp indicator turn-off timing") (step S38). The turn-off timing prediction process in step S38 is performed as follows.

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 MCU count value at the start of receiving the indicator turn-off signal sent from MCU 31 in step S18 = 35, the MCU count value at the start of receiving the indicator turn-on signal sent from MCU 31 in step S37 = 69, and the time length of one cycle of the synchronization clock = 10 ms are used to calculate the turn lamp 20 extinguishing time TP = (69 - 35) x 10 = 340 ms. In this embodiment, the turn lamp 20 extinguishing time TP = the turn lamp 20 on time TP, so the turn lamp 20 on time TP = 340 ms is calculated from the turn lamp 20 extinguishing time TP = 340 ms.

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

The time difference Tb between the completion timing of the drawing process by the SoC 32 in step S21 and 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) is calculated. In this processing sequence, the time difference Tb is calculated as 22 ms (constant) assuming that the time difference Tb = 22 ms.

The time difference Ta + Tb is calculated by subtracting the reception start timing when the MCU 31 started receiving the indicator-off drawing signal in step S15 from the display timing when the turn lamp indicator 33a is displayed in the indicator-off 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.

The system predicts the next time the turn lamp indicator 33a will be turned off so that the time from when the indicator 33a is turned off until the next time is shorter than the time length TP x 2 for one cycle of the turn lamp 20 on/off by the time difference Ta + Tb. It then calculates the start timing of the specified processing related to the next indicator off state (including received data notification processing, shared memory storage processing, and drawing processing) and starts the specified processing. In this processing sequence, the time Tab from when the turn lamp indicator 33a is turned off until the next time is calculated as follows: Time length TP x 2 - Time difference (Ta + Tb) = 680 - 232 = 448 ms, using the time length TP x 2 = 680 ms for one cycle of the turn lamp 20 on/off and the time difference Ta + Tb = 232 ms.

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

Note that, for subsequent timing control of 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 for turning the turn lamp indicator 33a to the indicator-on state in time with the lighting of the turn lamp 20 following 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, and the SoC count value (=66) at the completion of the indicator lighting drawing process held when the drawing process is completed in step S28. Note that, for subsequent timing control of 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.

In the above-described embodiment, the blinking timing of the turn lamp indicator 33a, which corresponds to the timing of turning on and off the turn lamp 20, is controlled using the time difference TA, Ta between when the MCU 31 starts receiving the indicator on/off signal or indicator off signal and when the SoC 32 completes the drawing process, and the time difference TB, Tb between when the SoC 32 completes the drawing process and when the indicator is displayed on the display with the indicator on or off (when the vertical synchronization (V-Sync) display process is completed). This makes it possible to minimize the time difference between the timing of turning on and off the turn lamp 20 and the blinking timing of the turn lamp indicator 33a. As a result, it is possible to reduce the sense of discomfort felt by the user due to the time difference between the timing of turning on and off the turn lamp 20 and the blinking timing of the turn lamp indicator 33a.

In addition, various design modifications may be made to the above-described configuration within the scope of the claims.

For example, in the above embodiment, the time difference TA was calculated based on the value of SPI msg count (MCU) when MCU31 started receiving the indicator illumination signal and the value of SPI msg count (SoC) when SoC32 completed the drawing process. However, this is not limited to this, and the time difference TA may be a predetermined constant, for example. 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 that combines the time difference TA and the time difference TB, i.e., TA+TB.

In addition, 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. For example, the indicator 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.

In addition, the contents described in the above embodiment and the contents described in the above modified example may be combined as appropriate.

The present invention is widely applicable to vehicle control devices that change the turn lamp indicator to an indicator state corresponding to a change in the turn lamp state of the turn lamp.

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 (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,
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: