Rain and Light Sensors: How a Cab Wipes and Lights Itself

Updated July 2026

Automatic wipers that start themselves when rain hits the glass, and headlamps that come on as the light fades into a tunnel or dusk, both come from the same small part behind the windscreen: a rain and light sensor. The driver never thinks about it, which is the point. It reads how much light is reaching the cab and whether there is water on the glass, hands those two readings to the vehicle, and lets the wiper and lighting logic do the rest. It is a small sensor with an outsized effect on how finished a cab feels to drive.

This guide is the version of the rain-and-light conversation we have with commercial-vehicle OEM buyers during project scoping. It covers what the sensor is responsible for, how the light and rain readings travel to the wiper and lighting controller, the real choice between a windscreen light-and-rain sensor and a dash-top sun-load sensor, why the windscreen glass is part of the specification, and what to put in a request for quotation so a supplier can price it without a round of clarification emails.

1. What a rain and light sensor actually does

On a basic cab the driver flicks the wipers and the lights by hand and no sensor is needed. The moment a programme wants those functions to happen on their own, something has to measure the weather and the daylight, and that is the sensor's job. It does a few distinct things, and the split matters when you come to specify one.

• Measuring ambient light. How much daylight is reaching the cab, used for the automatic headlamp strategy: switching to low beam at dusk, in a tunnel or under heavy overcast, and back off when the light returns.
• Measuring rain on the glass. An optical reading of water sitting on the outer surface in front of the sensor, used to start the wipers when rain begins, raise the sweep rate as it intensifies, and stop when the glass clears.
• Reading sun load for the climate system. On the sun-load variant, the strength and direction of sunlight plus temperature, so the air-conditioning can compensate for a cab heating up behind glass.
• Reporting, not deciding. The sensor is an input. It reports its readings to a wiper and lighting controller, which owns the wiper-speed and headlamp decisions. The sensor does not drive the wiper motor or the lamps itself.
• Surviving the windscreen environment. A part bonded to the glass cold-soaks overnight and bakes in summer sun, so it is specified for a wide temperature band and for stable optical performance across it.

The common mistake is to treat “rain-light sensor” as one fixed thing. In practice the first question is which of those jobs the cab actually automates, because that decides whether you need a windscreen light-and-rain part or a simpler dash-top sun-load part. For where this sensor sits among the cab inputs and the rest of the switching layer, the Switches and Sensors technical guide covers the full picture.

2. The two channels: light and rain

A windscreen sensor carries two readings in one housing, and they feed two different vehicle functions. Following that path from the glass to the wiper motor is what turns “we want automatic wipers” into a specification a supplier can build.

The pieces work like this:

• The sensor reads light and rain. The CGQ-024A light-and-rain sensor bonds to the inner face of the windscreen and reads both channels through the glass: daylight level for the lighting logic, and water on the outer surface for the wiper logic.
• The readings travel on LIN or a short hard-wire run. Rain and light are slow-changing signals, so they do not need a fast bus. A LIN segment or a direct wire to the controller carries them with margin to spare.
• The controller owns the decisions. A wiper and lighting controller such as the EBX-961 takes the rain reading and sets the wiper state (single sweep, intermittent rate, continuous), and takes the light reading and sets the headlamp state. Where a platform splits these across modules, the rain-light sensor still reports to the controller that carries the sensor interface, while a dedicated wiper module such as the EBX-2162 handles the wiper drive.
• The supply comes from the controller. A controller with a rain-light-sensor interface provides a regulated sensor supply rail, so the sensor plugs in without needing its own power source, which keeps the harness simple.

3. Windscreen light-and-rain versus dash-top sun-load

This is the choice that actually decides the part number, and it comes down to one question: does the cab automate the wipers, or only the lighting and climate? Youlai builds two related sensors for the two answers, and picking the wrong one is the most common way a rain-light line item goes wrong.

The honest way to choose is by the automation, not the sensor. Specify the CGQ-024A light-and-rain sensor when the programme wants automatic wipers, because the rain channel is what a dash-top part cannot provide; it bonds to the windscreen and runs from a 12 V supply. Specify the CGQ-012A sun-load sensor when the cab only needs automatic lighting and climate solar-compensation, because it is the simpler part: it reads sunlight and temperature from a dash-top position on a 24 V system without any of the windscreen-bonding constraints. One case is worth calling out for fleets: if you run a mix of 12 and 24 V vehicles and want to standardise on a single rain-light part, the 024A-LUX wide-input variant covers 9 to 32 V, so the same part number carries across the fleet. A related image-only 024B variant exists for legacy programmes; ask if you have a drawing that calls it out.

4. Mounting, and why the glass is part of the spec

For a dash-top sun-load sensor, mounting is straightforward: it sits on the dash top facing up and reads the sky. For a windscreen light-and-rain sensor, mounting is part of the specification rather than an afterthought, because rain sensing only works when the sensor is optically coupled to the glass. Three things decide whether it tracks the weather or misbehaves.

• Adhesive position. The CGQ-024A bonds to the inner face of the windscreen with 3M adhesive at a defined position shown on the assembly drawing. Before shipment the pads are applied to the fixed positions and each unit is fit-checked against that drawing, so the coupling geometry is correct on arrival.
• Glass at the sensing patch. The glass across the sensing area should be 3 to 7 mm thick and kept clear of anything that blocks light transmission there. A static-shielding film, a solar-reflective coating or a shade band will scatter or absorb the light and distort the reading, so the sensing patch has to be left out of those treatments.
• Aperture masking. An opaque mask around the sensing aperture stops refracted stray light entering from the side, reaching the optics and biasing the result. Without it the sensor can chatter in bright side light or miss a light shower.

None of this is exotic, but it is the detail that early RFQ conversations skip and then rediscover during integration. If the windscreen team specifies a solar film across the whole screen, or the glass at the sensing area is outside the 3 to 7 mm band, the rain sensor will not behave, and that is a glass-and-mounting problem, not a sensor fault. Agreeing the sensing-patch spec with the glass supplier up front is the cheapest way to avoid it.

5. How to write a rain-light sensor specification

A requirement a supplier can quote against, rather than guess at, covers five things. Leaving any of them implicit is what turns a quotation into a round of clarification emails.

1. Which functions you automate. Automatic wipers, automatic headlamps, climate solar-compensation, or a combination. This is the first fork: rain-sensing wipers need a windscreen light-and-rain part, while auto-lighting and HVAC alone can use a dash-top sun-load part.
2. System voltage. 12 V or 24 V, and whether the fleet mixes both. This decides the part and its supply-range variant, as set out in the comparison above; a fleet running both voltages on one rain-light part standardises on the wide-input 024A-LUX.
3. Windscreen glass at the sensing area. For a windscreen part, the glass thickness and a sensing patch left clear of any solar film, static-shielding layer or shade band (the mounting section above gives the target). This is a line item to agree with the glass supplier, not just the sensor supplier.
4. Controller interface. How the controller reads the sensor: LIN or a short hard-wire run, whether the controller provides the sensor supply rail, and which module owns the wiper and lighting logic. If a controller such as the EBX-961 owns it, name the interface up front.
5. Mounting and environment. Windscreen-bonded versus dash-top, the adhesive position drawing for a windscreen part, and the working temperature and ingress target the position demands.

From a sourcing perspective, the function list is the line buyers leave implicit and regret. “A rain-light sensor” is ambiguous until you say whether the wipers are automatic; the moment that is clear, the windscreen-versus-dash-top choice and the rest of the spec fall out of it. Provide the function list early and the sensor matches your vehicle plan instead of stalling in clarification.

6. What to look for in a supplier

A sensor bonded to the windscreen for the life of the vehicle, feeding a function the driver notices every time it rains, is not the place to chase headline price. The supplier questions that matter are about capability and support.

• Quality system in hand. Ask for the IATF 16949 certificate and what the PPAP package contains. Youlai manufactures under IATF 16949 with a PPAP package on programme handoff. Treat any verbal “automotive grade” claim without a certificate number as marketing.
• Both parts on one family. The most useful suppliers offer the windscreen light-and-rain part and the dash-top sun-load part as one family, so a range of cabs is covered without changing supplier. Confirm the two share the same quoting and validation workflow before committing.
• Glass and mounting support. Because the windscreen part depends on the glass at the sensing patch, a supplier that can give you the adhesive-position drawing and the sensing-patch glass requirement up front saves an integration cycle. Confirm they provide it, rather than leaving the glass spec to you.
• Optical stability across temperature. A windscreen part cold-soaks and bakes. Ask for the working range (−40 to +85 °C on the CGQ-024A) and confirm the optical performance is validated across it, not just at room temperature.
• Documentation on a project basis. EMC, IMDS and market-specific documentation are available upon project requirement rather than blanket-claimed across the catalogue. An honest supplier separates what it holds in hand from what it runs on a project basis.

Youlai validates in an in-house environmental laboratory with EMC pre-compliance equipment, and the contact page reaches the project team directly for a sourcing conversation.

Questions you will be asked at RFQ stage

• MOQ and samples. A standard CGQ-024A or CGQ-012A can usually move to samples quickly; a custom adhesive position, connector or output scaling follows the programme timeline. Sample quantities are agreed per programme.
• Lead time. Driven mostly by how much is configuration versus custom development, and by any bespoke mounting or connector tooling.
• PPAP timeline. The IATF 16949 PPAP package (drawings, BOM, control plan, FMEA, dimensional and test reports) is prepared on programme handoff.
• Customisation scope. Adhesive position, connector type, supply-range variant (024A-SYN versus 024A-LUX) and output scaling are routine configuration items, not exceptions.

7. Suggested next step

If you are scoping automatic wipers or automatic lighting for a commercial-vehicle programme, the most useful things to bring to a first conversation are which functions you automate, the cab system voltage, the windscreen glass spec at the sensing area if you want rain sensing, and how the controller reads the sensor. That lets us match the CGQ-024A light-and-rain sensor or the CGQ-012A sun-load sensor to your vehicle, alongside a controller such as the EBX-961, or tell you honestly where a custom configuration is needed. For how this sensor fits with the TPMS, the CAN switch panels and the rest of the cabin input layer, the Switches and Sensors technical guide covers the full stack.

For an adhesive-position drawing, the sensing-patch glass requirement, or a sensor-to-controller interface schedule against your vehicle programme, please use the contact page or message +86 134 6767 4786 on WhatsApp. Typical reply within 24 hours during China business hours (UTC+8).