A shared front-lamp light guide can produce a strong on-axis daytime running light and still perform poorly in its turn signal state. Extraction features may favor one LED location, a curved tinted component may change the transmitted spectrum, or an unintended reflection may illuminate a neighboring region. These are plausible design risks, not a reported customer case. A single central candela value cannot describe them.
A useful daytime running light design workflow evaluates both functions in the same optical assembly, with each source state defined explicitly. TracePro®, Lambda Research Corporation’s optical design and analysis software, supports Monte Carlo ray tracing, CAD-based geometry, and customizable optical properties for this work. The model helps compare designs before tooling and plan prototype tests; it does not itself confer lamp or vehicle approval. [1]
Start with the Applicable Requirements and Operating States
Separate lamp performance from vehicle installation. UN Regulation No. 148 addresses light-signalling devices, including daytime running lamps and direction indicators. UN Regulation No. 48 addresses installation on vehicles. A project referencing legacy UN R87 material should confirm which approval route, amendment series, transition provisions, lamp category, and target-market requirements actually apply. Do not reuse an old numerical grid as a universal specification. [2, 3]
Define the operating-state matrix before tracing. Shared optics do not automatically mean that the white DRL and amber signal are energized together. For example, the cited R48 publication requires the DRL to remain off throughout indicator activation when the two functions are reciprocally incorporated. A common outer lens alone does not settle that classification. A separately approved position-lamp state also should not be treated as merely a dimmed DRL without checking its requirements. [3]
Model DRL-only, indicator-on, and indicator-off conditions, plus any other permitted companion-function states. Deliberately simultaneous white and amber operation can be a useful diagnostic or fault case, but label it as such when it is outside the intended control strategy. A static optical trace does not validate flashing frequency, transition timing, or electrical control logic.
Define White and Amber Sources from Measured Data
Keep the white and amber LEDs in separate source sets, with the production positions, orientations, spatial extent, and spectra. A measured ray file can preserve position-direction relationships that a far-field angular table cannot. When only angular photometry is available, document the assumed emitting area and check whether the approximation is adequate for coupling into the guide. Lambda Research documents rayfile creation and IES/LDT source-data workflows. [4]
Use source power and spectral data appropriate to drive current, LED bin, and temperature. White and amber devices can behave differently, but the correction must come from the selected part’s data or measurements. Do not assume a universal thermal ranking or scale every LED with one factor. Record whether the input is radiant power or luminous flux and avoid applying spectral photopic weighting twice.
An optical model needs thermal and electrical conditions as inputs unless they have been established through a separate coupled workflow. Include the operating corners that matter to minimum intensity, maximum intensity, and color. More source power may help a low point while consuming headroom at a high point.
Build the Complete Light Guide and Housing
Import the guide, LED package interfaces, lens, bezel, and nearby mechanical features that can intercept or redirect light. Check CAD units, reference axes, overlaps, and contact assumptions. Small air gaps, draft angles, and misalignment at the entrance face can change coupling into a total-internal-reflection guide.
Assign wavelength-dependent refractive index and absorption where needed, along with realistic reflection and scatter properties. For a tinted material, distinguish bulk absorption from interface losses and from a coating’s transmission. A measured transmission curve for one sample thickness cannot simply be applied as the same loss at every surface and every optical path length. TracePro supports material and surface properties and custom spectral data. [1]
Model extraction features as resolved geometry or a validated effective property, according to their scale and purpose. Changing pitch, depth, density, or orientation can redistribute extraction along the guide. There is no universally correct ramp: the result depends on how both source sets populate the guide. Evaluate both functions after each change. Compare a shared extraction pattern with separated optical paths if the requirements cannot be met together.
Evaluate Candela in the Correct Angular Coordinates
TracePro’s candela plots report luminous intensity as a function of angle. Set the source normalization, collection convention, reference axis, and horizontal/vertical angle convention deliberately. Confirm that the angular bins and integration method represent the intended measurement; a smoothed plot is not automatically a point measurement at the required direction. [5]
Extract all specified test directions for each relevant state and inspect the surrounding distribution for peaks or troughs that a sparse grid might miss. If using a finite-distance receiver to infer intensity from illuminance, confirm the far-field approximation and account for receiver orientation. Do not treat an arbitrary plane as equivalent to a goniophotometric measurement.
Keep a comparison table with direction, limit type, requirement, predicted intensity, margin, source state, and model revision. For a minimum requirement, a useful signed margin is 100 × (predicted − minimum) / minimum. For a maximum, use 100 × (maximum − predicted) / maximum. Both conventions make a positive margin desirable.
There is no general rule that ten percent nominal margin absorbs production variation. Set the required reserve from source spread, dimensional variation, material uncertainty, simulation uncertainty, and measurement uncertainty. Use the table to identify which change improves a weak direction and whether it worsens another.
Establish Ray Trace Convergence Before Ranking Designs
A high total ray count does not ensure that a weak angular bin or leakage path is well sampled. Increase ray count and, where appropriate, repeat independent runs while observing the quantities used for decisions. Check that the limiting intensity, color result, and low-level leakage remain stable relative to the available design margin.
Document bin size, smoothing, tracing thresholds, and collection settings. A low-energy termination threshold can remove paths that matter to leakage, while heavy smoothing can conceal a local peak. If a result remains dominated by Monte Carlo variation, report that uncertainty rather than assigning precise pass/fail meaning to the nominal value. Lambda Research provides technical resources on statistical noise in TracePro. [6]
Separate Apparent Surface from Styling Uniformity
Apparent surface is a defined regulatory geometric quantity. In the cited R48 text, its construction involves the orthogonal projection of a declared illuminating-surface boundary or light-emitting surface in the observation direction. It should not be invented by thresholding a luminance image at a convenient fraction of its maximum. Use the applicable definitions and declared boundaries for the project’s area and visibility checks. [3]
Luminance remains valuable for appearance assessment. TracePro provides luminance/radiance maps and rendering tools. Use a consistent viewing geometry, exposure, and sampling method when comparing guide revisions. A visually attractive rendering does not establish regulatory apparent area or photometric acceptance. [5]
For a styling metric, divide the visible guide into repeatable regions and compare representative luminance values, such as regional means or stated percentiles. Define treatment of edges, masks, and dark gaps so the metric is reproducible. Evaluate the intended viewing directions and both functions. A metric based on one extreme pixel is especially sensitive to resolution and statistical noise.
Calculate Amber Color through the Actual Optical Path
The emitted color depends on source spectra and the wavelength-dependent transmission of the complete assembly. In absorbing material, differing path lengths can alter the transmitted spectrum. Incidence angle can also change coating behavior. The size and direction of the color shift must be calculated for the actual materials, rather than assumed to be worst at every lens edge.
TracePro supports spectral source modeling and CIE chromaticity analysis. Match the analysis aperture and angular acceptance to the quantity being assessed: a local near-field color map and a directionally integrated far-field color measurement answer different questions. Use sufficient wavelength sampling across both LED emission and filter features. [7]
Evaluate the appropriate chromaticity coordinates against the specified boundary. Combine spectral or tristimulus contributions before calculating the mixed color; do not average x and y coordinates by an arbitrary power fraction. Track both color and intensity, since a change that improves one can reduce margin in the other.
Where a permitted companion function or a defined fault introduces white light, model its actual source and path. A controlled diagnostic sweep of that contribution can reveal color sensitivity. If the white source is correctly off in the relevant state, do not invent a continuously powered white leakage source and present it as normal operation.
Trace Unwanted Light to Its Origin
Switch sources independently and identify where light appears outside the intended emitting region. TracePro ray histories and Path Sorting Tables can isolate the surface sequences contributing to an unwanted destination. Rank those paths by delivered flux before proposing a fix. [5]
Candidate mechanisms include end-face reflections, escape around the LED coupling region, scatter from a molded surface, and reflections from the shared lens. They are hypotheses to test, not a guaranteed ordering. Compare local light traps, surface-finish changes, barriers, or geometry revisions against useful throughput as well as leakage. An absorptive feature can suppress one route while clipping intended rays.
Do not call illumination of the common emitting guide “leakage” merely because that guide also serves the other function. In a shared-aperture design, the same area may intentionally emit white in one state and amber in another. Define unwanted regions and acceptance metrics from the actual optical and control architecture.
Use Tolerances to Set the Prototype Test Plan
Vary LED placement, guide and lens position, extraction dimensions, source output, and optical properties across justified ranges. Include combinations where the effects can reinforce one another; one-at-a-time sensitivity checks alone do not establish a worst credible assembly.
TracePro’s macro language can automate repeated model and analysis tasks. Save each configuration with its assumptions and output table so a CAD change can be assessed against the same cases. [1]
Report the limiting conditions, remaining margin, and unresolved input uncertainties. Correlate the model with prototype angular photometry, color measurements, and appearance assessments. Validate switching behavior and any required environmental or approval tests through the appropriate test program. Simulation gives engineering a basis for deciding what to change and what to measure next.
Make Shared Optic Decisions Before Tooling
A multifunction front lamp needs more than a strong reference-axis result. Measured source states, complete geometry, angular intensity data, correctly defined apparent surfaces, spectral color checks, and path-based leakage analysis reveal the tradeoffs hidden by isolated nominal checks.
Use those results to choose the extraction pattern, source arrangement, and local light-control features, then verify the critical predictions on hardware. Request a TracePro demo to explore candela, apparent-surface support, color, and optical leakage analysis for a shared DRL and turn signal design before tooling.