Headlamp driver architecture system without MCU (Microprogrammed Control Unit) and implementation method thereof

Abstract

The invention discloses a headlight driver architecture system without an MCU, and the system comprises a Filter module which serves as a filtering protection circuit, achieves the anti-reverse connection protection, and provides an EMC countermeasure; the SPI BOOST module is used for boosting the input KL15 voltage to 55V and supplying power to chips of the UartBuck 1 module, the SPI Buck module and the UartBuck 2 module; the UartBuck 1 module and the UartBuck 2 module are provided with IO ports for input and output detection, and are used for realizing constant-current Buck driving, external output SPI communication and external output 5V voltage; the CAN Transceiver module is used for transmitting a vehicle body Uart CAN signal to the Uart Buck 1 module and the Uart Buck 2 module through the transceiver, and completing information interaction with a chip of the Uart Buck 1 module and a chip of the Uart Buck 2 module; the SPIBuck module outputs two paths of constant current drive; the invention further discloses an implementation method of the headlamp driver architecture system without the MCU. According to the invention, BIN current management, NTC temperature management, LED driving and protocol conversion are realized through the UartBuck module, and transformation from a distributed ECU to centralized "central calculation + regional control" can be realized without using an MCU chip.

Description

Technical Field

[0001] This invention belongs to the field of automotive headlight lighting technology, specifically relating to a headlight driver architecture system without an MCU and its implementation method. Background Technology

[0002] With the continuous development of electronic technology, the current automotive architecture is undergoing a transformation from distributed ECUs to centralized "central computing + regional control". This trend has already begun to emerge in major OEMs. For automotive lighting drive systems, how to deal with this trend has become a top priority.

[0003] In current automotive lighting systems, the MCU, as the brain of the lighting ECU, carries the functions of computation and control. On this basis, the peripheral control modules have relatively simple functions, mainly serving as execution modules to complete the driving work. However, in the trend of centralized architecture, with the computing power moving up to the ZCU, how to reduce or even eliminate the lighting ECU algorithm on the basis of the current architecture, while taking cost into consideration, has become a problem that the market has to face.

[0004] Current driver DC-DC modules mainly support on-board communication bus methods such as SPI, while the main communication method of the vehicle body is CAN / CANFD. Furthermore, after the CAN transceiver receives CAN / CANFD signals, these DC-DC modules cannot use them directly.

[0005] While some modules on the market can currently receive TXD / RXD signals, two problems exist:

[0006] 1. The current solution is in its early stages and the product price is relatively high. For drivers with a large number of channels, if each chip is replaced with this solution, the product cost will exceed expectations, which deviates from the original intention of OEMs to reduce costs through centralized development.

[0007] 2. There are many types of vehicle headlight drive modules, including constant current drive, constant voltage drive, motor drive and high-side drive. If each module is replaced in this way, corresponding solutions need to be provided for all scenarios, which may take a long time and cannot support this trend. Summary of the Invention

[0008] The purpose of this invention is to provide a headlight driver architecture system without an MCU to solve the problems mentioned in the background art. The headlight driver architecture system without an MCU provided by this invention has the following characteristics.

[0009] Another objective of this invention is to provide a method for implementing a headlight driver architecture system without an MCU.

[0010] To achieve the above objectives, the present invention provides the following technical solution: a headlight driver architecture system without an MCU, comprising:

[0011] The filter module, as a filtering and protection circuit, provides reverse connection protection and EMC countermeasures;

[0012] The SPI BOOST module boosts the input KL15 voltage to 55V (adjustable according to the actual project) to power the chips of the Uart_Buck1, SPI_Buck and Uart_Buck2 modules.

[0013] The Uart_Buck1 and Uart_Buck2 modules have I / O ports for input / output detection, enabling constant current Buck driving, external SPI communication, and external 5V voltage output.

[0014] The CAN Transceiver module transmits the vehicle's Uart CAN signals to the Uart_Buck1 and Uart_Buck2 modules via a transceiver, and completes information exchange with the chips of the Uart_Buck1 and Uart_Buck2 modules.

[0015] The SPI_Buck module outputs two constant current drives. This module is commonly used in the market, and common chips include TPS929520, BD18398, NCV78825, and iND78520, etc. Those in the automotive lighting industry are familiar with these chips, so they will not be discussed in detail here.

[0016] In this invention, the Uart_Buck1 module is further used to implement:

[0017] BIN current management identifies the data of the BIN pin and returns the data to the ZCU via the CAN transceiver. The ZCU determines the current of the output channel under normal conditions based on this signal.

[0018] NTC temperature management identifies the data of the NTC pins and returns the data to the ZCU via a CAN transceiver. The ZCU determines the current of the output channel based on the signal and performs derating management to adjust the temperature of the driver system and LED board.

[0019] Based on the signal sent by the ZCU, the current setting of the output channel is completed, and the corresponding current is output to drive the LED;

[0020] Protocol conversion: The received Uart CAN signal is converted into full-duplex SPI data format, and control commands are transmitted to the SPI_Buck module chip through the SPI pin.

[0021] Furthermore, in this invention, the Uart_Buck2 module has the same function as the Uart_Buck1 module. The Uart_Buck2 module converts the received Uart CAN signal into a full-duplex SPI data format and transmits control commands to the stepper motor chip through the SPI pin.

[0022] Furthermore, in this invention, the SPI_Buck module completes the current output of CH3 and CH4 according to the instructions received from SPI1, and provides channel status feedback through SPI1. This invention describes only one SPI_Buck module; in practical applications, the number of SPI_Buck modules can be increased according to the load channels, sharing the SPI output control of Uart_CAN1. The more SPI_Buck modules there are, the greater the cost advantage compared to traditional buck-boost solutions.

[0023] Furthermore, in this invention, after KL15 is powered on, after an interval of 50ms (this value can be adjusted according to the different power-on times of each module), an initialization command is sent via Uart CAN to the Uart_Buck1 module, Uart_Buck2 module, SPI_Buck module, and stepper motor driver.

[0024] In this invention, the initialization operation, in addition to the conventional settings, also includes the open-circuit and short-circuit detection thresholds, registers for controlling the output current value, Buck switching frequency, duty cycle, and chip operating mode of the Uart_Buck1 module, Uart_Buck2 module, and SPI_Buck module chips; and the microstepping number, drive current, holding current, current frequency, motor rotation direction, drive mode, and stall detection of the stepper motor driver chip.

[0025] Furthermore, in this invention, the implementation method of the headlight driver architecture system without an MCU includes the following steps:

[0026] S1. Receive vehicle body commands via Uart_CAN. The commands are divided into Class A chip select command set and Class B chip select command set. Class A chip select command set is DC-DC control command set, and Class B chip select command set is stepper motor control command set.

[0027] S2, Uart_Buck1 module chip select Class A instruction set, performs chip initialization and normal control of Uart_Buck1 module, and converts the received Uart_CAN instruction into full-duplex format and sends it to SPI_Boost module and SPI_Buck module through SPI_1;

[0028] S3, Uart_Buck2 module chip select B-class instruction set, performs chip initialization and normal control of Uart_Buck2 module, and converts received Uart_CAN instructions into full-duplex format and sends them to stepper motor driver via SPI_2;

[0029] The S4, Uart_Buck1, and Uart_Buck2 modules detect the corresponding port values ​​through the ADC port to determine the current BIN level, NTC current derating level, and left / right identification, and send them to the vehicle body domain controller ZCU via Uart_CAN. The ZCU controls the corresponding functions based on the received signals.

[0030] In this invention, further, in S1, the Class A chip select instruction set and the Class B chip select instruction set are both virtual distinctions. When the chip select is performed through the Uart_Buck1 module, it is the Class A chip select instruction set, and when the chip select is performed through the Uart_Buck2 module, it is the Class B chip select instruction set. In addition to the data required by the Uart_Buck1 module and the Uart_Buck2 module themselves, the definitions of the data sent out in the Class A and Class B chip select instruction sets are inconsistent. The Class A chip select instruction set is for the data format required by DC-DC converters, and the Class B chip select instruction set is for the data format required by stepper motors.

[0031] In this invention, in step S2, the Class A chip select instruction set is converted into a data format that meets the requirements of the SPI_Boost module and the SPI_Buck module through the Uart_Buck1 module.

[0032] In this invention, in step S3, the B-type chip select instruction set is converted into a data format that meets the requirements of the stepper motor through the Uart_Buck2 module.

[0033] Further in this invention, in S4, multiple ADC port numbers of the Uart_Buck1 and Uart_Buck2 modules form a one-to-one mapping relationship with the BIN or NTC or left / right corresponding to high beam, low beam, daytime running light, position, and turn signals, and are pre-stored in the ZCU (the one-to-one mapping relationship is shown in the embodiment). When the ZCU controls the lights according to the signals, the A-type chip select instruction set and the B-type chip select instruction set will no longer contain light control instructions. The control instructions and logic judgments are all implemented by the software logic of the vehicle body ZCU. Its software logic directly outputs control instructions for Boost, Buck, and stepper motors in real time, which are issued through Uart_CAN for the A-type instruction set and the B-type instruction set. Similarly, the Boost, Buck, stepper motor, and other ICs in this driver only receive real-time feedback of the corresponding register values ​​and I / O port values ​​through Uart_CAN via the A-type instruction set and the B-type instruction set, respectively. The output load function and status are determined by the matching function definition in the vehicle body ZCU software.

[0034] Compared with the prior art, the beneficial effects of the present invention are:

[0035] 1. This invention implements BIN current management through the Uart_Buck module. By identifying the data of the BIN pin, the data is returned to the ZCU via the CAN transceiver. The ZCU determines the current of the output channel under normal conditions based on the signal.

[0036] 2. This invention implements NTC temperature management through the Uart_Buck module. By identifying the data of the NTC pins and returning the data to the ZCU via the CAN transceiver, the ZCU determines the current of the output channel for derating management based on the signal, thereby adjusting the temperature of the driver system and LED board.

[0037] 3. This invention uses the Uart_Buck module to set the current of the output channel according to the signal sent by the ZCU, and outputs the corresponding current to drive the LED.

[0038] 4. This invention uses the Uart_Buck module to perform protocol conversion, converting the received Uart CAN signal into a full-duplex SPI data format, and transmitting control commands to the SPI_Buck module chip and the stepper motor chip through the SPI pin.

[0039] 5. This invention realizes BIN current management, NTC temperature management, LED driving and protocol conversion through the Uart_Buck module, and can realize the transformation of distributed ECU to centralized "central computing + regional control" without the need for MCU chip. Attached Figure Description

[0040] Figure 1 This is a system architecture diagram of the present invention.

[0041] Figure 2 This is a system architecture diagram of Embodiment 1 of the present invention.

[0042] Figure 3 This is a control flowchart of Embodiment 1 of the present invention.

[0043] Figure 4 This is a system architecture diagram of Embodiment 2 of the present invention.

[0044] Figure 5 This is a control flowchart of Embodiment 2 of the present invention. Detailed Implementation

[0045] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] In the description of this invention, unless otherwise explicitly specified and limited, the terms "connected," "linked," and "fixed" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0047] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of the second feature includes the first feature directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature includes the first feature directly below or diagonally below the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature.

[0048] In the description of this invention, the terms "upper," "lower," "right," and "left," etc., refer to the orientation or positional relationship shown in the accompanying drawings. They are used only for ease of description and simplification of operation, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention. Furthermore, the terms "first" and "second" are used merely for distinction in description and have no special meaning.

[0049] Example 1

[0050] Please see Figures 1-3 In ZCU software, for Figure 2The functions of each pin are configured. CH1 is the constant current channel for low beam (LB), and CH2 is the constant current channel for high beam (HB), supplying power to the low beam and high beam headlights respectively; L / R is the left / right identification pin, identifying whether the system is installed on the left or right side of the vehicle; HSD1-EN is the fan enable pin; LB NTC pin collects low beam headlight temperature data; HB NTC pin collects high beam headlight temperature data; LB BIN collects low beam headlight BIN resistance data; HB BIN collects high beam headlight BIN resistance data; HSD1 FAN is the fan power supply switch, and HSD1 EN is the fan power supply enable pin.

[0051] The control system is divided into four parts: power supply, initialization, current setting and channel opening, and fault feedback.

[0052] Power supply: When KL15 is powered on, after passing through the Filter module, it powers the SPI BOOST module and HSD module. The SPI BOOST module powers the Uart Buck1 module and outputs 5V to the inner 5V pin to power the CAN Transceiver.

[0053] Initialization: The vehicle body communicates with this system via Uart CAN. After receiving the Uart CAN signal, this system transmits the signal to the Uart Buck1 module, communicates with the Uart Buck1 module, and initializes the chip of the Uart Buck1 module.

[0054] During initialization, the SPI class A instruction set is transmitted via SPI to set the SPI BOOST register and complete the basic parameter configuration.

[0055] Current setting and channel activation: When the ZCU determines that the fan activation conditions are met, it sends a control Uart Buck1_PIN4==1 to the Uart Buck1 module through the UartBuck1 module's Class A instruction set, and the fan is activated.

[0056] The activation of the headlights is implemented in the Class A instruction set. During initialization, the ZCU first reads the BIN resistor value via the UartBuck1 module and transmits the data to the ZCU. The ZCU sets the base current based on the resistance value. During normal headlight control, when the ZCU determines that the headlight activation conditions are met, it reads the NTC resistor value via the UartBuck1 module and sends it to the ZCU. The ZCU then determines the derating factor based on the resistance value and sends a current setting command `Current_set.UART BUCK` to the UartBuck1 module via the Class A instruction set to generate the control current to illuminate the headlights. This process enables the activation of both low beam and high beam headlights.

[0057] Fault Feedback: During the lighting process, the Uart Buck1 module monitors the load in real time. When a fault is detected, it sends a fault flag to the ZCU to achieve the purpose of fault feedback.

[0058] Example 2

[0059] Please see Figures 4-5 In ZCU software, for Figure 4 The functions of each pin are configured. CH1 is the constant current channel for low beam (LB), CH2 is the constant current channel for high beam (HB), CH3 / CH4 are the constant current channels for turn signals, and CH5 / CH6 / CH7 / CH8 are the constant current channels for daytime running lights; L / R are left / right recognition pins, identifying whether the system is installed on the left or right side of the vehicle; Motor control1 and Motor control2 are the motor control signals; LB NTC pin collects low beam headlight temperature data; HB NTC pin collects high beam headlight temperature data; DRL NTC pin collects daytime running light temperature data; TI NTC pin collects turn signal temperature data; LBBIN collects low beam headlight BIN resistance data; HB BIN collects high beam headlight BIN resistance data; DRL BIN collects daytime running light BIN resistance data; TI BIN collects turn signal BIN resistance data.

[0060] The control system is divided into four parts: power supply, initialization, current setting and channel opening, and fault feedback.

[0061] Power supply: When KL15 is powered on, after passing through the Filter module, it supplies power to the BOOST module and the Step Motor Driver module. The BOOST module supplies power to the Uart Buck1 module, Uart Buck2 module, SPI Buck2 module and SPI Buck2 module. After the Uart Buck2 module is powered on, it outputs 5V to the inner 5V pin to supply power to the CAN Transceiver module.

[0062] Initialization: The vehicle body communicates with this system via Uart CAN. After receiving the Uart CAN signal, this system transmits the signal to the Uart Buck1 module and sends the A-type instruction set. The Uart Buck1 module completes its own initialization by sending an initialization command to the SPI Buck via SPI1. The Uart Buck2 module sends the B-type instruction set and sends an initialization command to the StepMotor Driver module via SPI2 to complete the basic parameter configuration.

[0063] Current setting and channel activation: For motor control, when the ZCU determines that the motor control conditions are met, it sends control commands to the Step Motor Driver module via the UART Buck2 module's Class B instruction set, and completes motor control through motorcontrol1 and motorcontrol2. By setting the value of motorcontrol1, the motor's direction of motion is set; by setting the value of motorcontrol2, the motor's pulse current frequency is set; and by transmitting the corresponding register data to SPI2, the motor steps and motor control current are determined.

[0064] The activation of the headlights is implemented in the Class A instruction set. During initialization, the ZCU first reads the BIN resistor value via the UartBuck1 module and transmits the data to the ZCU. The ZCU sets the base current based on the resistance value. During normal headlight control, when the ZCU determines that the headlight activation conditions are met, it reads the NTC resistor value via the UartBuck1 module and sends it to the ZCU. The ZCU determines the derating factor based on the resistance value and then sends the current setting instruction `Current_set` to the UartBuck1 module via the Class A instruction set. For loads controlled by the UartBuck1 module, the UartBuck1 module generates a control current to illuminate the headlights. For loads controlled by the SPI Buck module, the UartBuck1 module sends the setting parameters to the UartBuck1 module via SPI1, and the UartBuck1 module generates a control current to illuminate the headlights. Through this method, the low beam, high beam, turn signals, daytime running lights, and position lights are activated.

[0065] Fault Feedback: During the lighting and motor control process, the Uart Buck1 module and SPI Buck monitor the load in real time. When a fault is detected, the fault information is sent to the Uart Buck1 module and then a fault flag is sent to the ZCU to achieve the purpose of fault feedback.

[0066] In summary, this invention implements BIN current management through the Uart_Buck module. By identifying the data of the BIN pin and returning this data to the ZCU via a CAN transceiver, the ZCU determines the current of the output channel under normal conditions based on this signal. This invention also implements NTC temperature management through the Uart_Buck module. By identifying the data of the NTC pin and returning this data to the ZCU via a CAN transceiver, the ZCU determines the current of the output channel and performs derating management to adjust the temperature of the driver system and LED board based on this signal. Furthermore, this invention uses the Uart_Buck module to set the current of the output channel based on signals sent by the ZCU and outputs the corresponding current to drive the LEDs. Finally, this invention uses the Uart_Buck module for protocol conversion, converting the received Uart CAN signal into full-duplex SPI data format, and transmitting control commands to the SPI_Buck module chip and the stepper motor chip via the SPI pin. This invention achieves BIN current management, NTC temperature management, LED driving, and protocol conversion through the Uart_Buck module, enabling the transformation from a distributed ECU to a centralized "centralized computing + regional control" system without the need for an MCU chip.

[0067] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A headlight driver architecture system without an MCU, characterized in that, include: The filter module, as a filtering and protection circuit, provides reverse connection protection and EMC countermeasures; The SPI BOOST module boosts the input KL15 voltage to 55V to power the chips of the Uart_Buck1 module, SPI_Buck module and Uart_Buck2 module; The Uart_Buck1 and Uart_Buck2 modules have I / O ports for input / output detection, enabling constant current Buck driving, external SPI communication, and external 5V voltage output. The CAN Transceiver module transmits the vehicle's Uart CAN signals to the Uart_Buck1 and Uart_Buck2 modules via a transceiver, and completes information exchange with the chips of the Uart_Buck1 and Uart_Buck2 modules. The SPI_Buck module outputs two constant current drives.

2. The headlight driver architecture system without an MCU according to claim 1, characterized in that: The Uart_Buck1 module is used to implement: BIN current management identifies the data of the BIN pin and returns the data to the ZCU via the CAN transceiver. The ZCU determines the current of the output channel under normal conditions based on this signal. NTC temperature management identifies the data of the NTC pins and returns the data to the ZCU via a CAN transceiver. The ZCU determines the current of the output channel based on the signal and performs derating management to adjust the temperature of the driver system and LED board. Based on the signal sent by the ZCU, the current setting of the output channel is completed, and the corresponding current is output to drive the LED; Protocol conversion: The received Uart CAN signal is converted into full-duplex SPI data format, and control commands are transmitted to the SPI_Buck module chip through the SPI pin.

3. The headlight driver architecture system without an MCU according to claim 2, characterized in that: The Uart_Buck2 module has the same function as the Uart_Buck1 module. The Uart_Buck2 module converts the received UartCAN signal into a full-duplex SPI data format and transmits control commands to the stepper motor chip through the SPI pin.

4. The headlight driver architecture system without an MCU according to claim 1, characterized in that: The SPI_Buck module completes the current output of CH3 and CH4 according to the instructions received by SPI1, and provides feedback on the channel status through SPI1.

5. The headlight driver architecture system without an MCU according to claim 1, characterized in that: After the KL15 is powered on, after a 50ms interval, it sends an initialization command via Uart CAN to the Uart_Buck1 module, Uart_Buck2 module, SPI_Buck module, and stepper motor driver. In addition to the usual settings, the initialization operation also includes setting the open and short circuit detection thresholds, registers for controlling the output current value, Buck switching frequency, duty cycle, and chip operating mode for the Uart_Buck1, Uart_Buck2, and SPI_Buck module chips. The stepper motor driver chip includes parameters such as microstep count, drive current, holding current, current frequency, motor rotation direction, drive mode, and stall detection.

6. A method for implementing a headlight driver architecture system without an MCU according to any one of claims 1-5, characterized in that, Includes the following steps: S1. Receive vehicle body commands via Uart_CAN. The commands are divided into Class A chip select command set and Class B chip select command set. Class A chip select command set is DC-DC control command set, and Class B chip select command set is stepper motor control command set. S2, Uart_Buck1 module chip select Class A instruction set, performs chip initialization and normal control of Uart_Buck1 module, and converts the received Uart_CAN instruction into full-duplex format and sends it to SPI_Boost module and SPI_Buck module through SPI_1; S3, Uart_Buck2 module chip select B-class instruction set, performs chip initialization and normal control of Uart_Buck2 module, and converts received Uart_CAN instructions into full-duplex format and sends them to stepper motor driver via SPI_2; The S4, Uart_Buck1, and Uart_Buck2 modules detect the corresponding port values ​​through the ADC port to determine the current BIN level, NTC current derating level, and left / right identification, and send them to the vehicle body domain control ZCU via Uart_CAN. The ZCU controls the corresponding functions based on the received signals.

7. The implementation method of a headlight driver architecture system without an MCU according to claim 6, characterized in that: In S1, both the Type A and Type B chip select instruction sets are virtual distinctions. When the chip selector is selected through the Uart_Buck1 module, it is the Type A chip select instruction set, and when it is selected through the Uart_Buck2 module, it is the Type B chip select instruction set. Apart from the data required by the Uart_Buck1 and Uart_Buck2 modules themselves, the definitions of the data sent out by the Type A and Type B chip select instruction sets are inconsistent. The Type A chip select instruction set is for the data format required by DC-DC converters, while the Type B chip select instruction set is for the data format required by stepper motors.

8. The implementation method of a headlight driver architecture system without an MCU according to claim 6, characterized in that: In S2, the Class A chip select instruction set is converted into a data format that meets the requirements of the SPI_Boost module and the SPI_Buck module through the Uart_Buck1 module.

9. The implementation method of a headlight driver architecture system without an MCU according to claim 6, characterized in that: In S3, the B-type chip select instruction set is converted into a data format that meets the requirements of the stepper motor through the Uart_Buck2 module.

10. The implementation method of a headlight driver architecture system without an MCU according to claim 6, characterized in that: In S4, multiple ADC port numbers of the Uart_Buck1 and Uart_Buck2 modules form a one-to-one mapping relationship with the BIN or NTC or left / right corresponding to high beam, low beam, daytime running light, position, and turn signals, and are pre-stored in the ZCU. When the ZCU controls the lights according to the signals, the A-type chip select instruction set and the B-type chip select instruction set will no longer contain light control instructions. The control instructions and logic judgments are all implemented by the software logic of the vehicle body ZCU. Its software logic directly outputs control instructions for Boost, Buck, and stepper motors in real time, and issues them to the A-type instruction set and the B-type instruction set through Uart_CAN.

Images