Transmission describes the useful signal that should pass; attenuation describes reduction. Both should be tied to wavelength range and instrument context.
Prepare Transmission Attenuation fields for optical filter review with wavelength, bandwidth, blocking, geometry, product-family path, and RFQ checklist guidance.
Transmission Attenuation belongs in the first technical description because it shapes how an optical filter request is reviewed. Use the field to describe the intended spectral position, width, blocking need, geometry, or transmission context before asking for a drawing review or quotation.
Add the field to the technical RFQ package before sending drawings or spectra.
A clear value helps separate a general component search from a request that can be checked against filter family, wavelength band, coating context, substrate, and size constraints. When the value is uncertain, state the acceptable range or the measurement condition instead of forcing a single number.
Prepare known values, acceptable ranges, and measurement conditions.
Useful request notes include the target band or wavelength, bandwidth or blocking target, AOI, substrate, outside dimensions, quantity, application context, and any drawings or spectra that explain the optical path. Keep commercial timing separate from the technical fields so the first review can focus on feasibility.
List target values and attach supporting spectra when available.
Review the product family that matches the optical function first: bandpass filters for passband selection, longpass or shortpass filters for edge behavior, dichroic optics for beam splitting, neutral density filters for attenuation, and coated optics when the geometry or substrate is the main constraint.
Open the relevant product family, then return to the RFQ package.
Write the field as a technical note rather than a sales summary. Include what is fixed, what can be adjusted, what documents are attached, and which application context matters most. This keeps the inquiry useful without asking the buyer to make unsupported performance assumptions.
Send the checklist with application context, target values, and document needs.
A buyer can ask for product sheets, coating review notes, drawing review, or spectrum-related documents when those materials are needed for evaluation. The request should describe the project context and the exact document type needed so Lumalyx can route the response for technical review.
Ask for the document type needed and include the related field values.
Use these fields to turn the page topic into a reviewable Lumalyx request.
A transmission target tells the reviewer what useful wavelength range should remain in the optical path.
Neutral density and blocking discussions use attenuation language, but the wavelength range and uniformity need to be clear.
Consumer filter names can be useful clues, but industrial requests need wavelength, OD, transmission, size and material fields.
Transmission targets are most useful when tied to a pass band or working range. A request should explain whether the value is a minimum target, a reference value from an existing part, or an open requirement to be reviewed.
Send transmission together with CWL, pass band or cutoff context.
Neutral density requests often focus on controlled attenuation of a useful beam. Blocking requests focus on reducing unwanted wavelength content. The review is clearer when the request states which behavior is needed and over which wavelength range.
Use OD, transmission and wavelength range fields together.
Include the target wavelength range, transmission or attenuation value if known, OD target when relevant, source intensity context, detector or sensor context, AOI, substrate, size and quantity. If the request comes from a camera or photography term, translate it into optical fields before review.
Start an RFQ when the target range is known but the exact value is open.
Neutral density filters are the usual path for controlled attenuation. Spectral filters use transmission alongside pass band and blocking fields. Coated components may need transmission or reflection context when the request involves beamsplitters, windows or lenses.
Browse neutral density filters or send the working range through RFQ.
These fields make the request easier to evaluate and show which values are confirmed, approximate or still open.
Send the values you know, mark uncertain fields clearly and include spectra, drawings or existing references when they help explain the signal path.
Start technical RFQTransmission and attenuation are easier to review when the request says which wavelengths should pass, which should be reduced and how the component is used.
| Field | Send when | Review note |
|---|---|---|
| Transmission target | Wanted signal should pass through a range. | Name the range and target when known. |
| Attenuation target | Light should be reduced rather than selected by a pass band. | Useful for neutral density and balancing tasks. |
| Working range | The component is used across a broad spectrum. | Send the full range, not only one wavelength. |
Transmission and attenuation values should not be mixed without stating the working wavelength range.
English should remain the default for broad transmission and attenuation education until regional evidence shows a stronger localized buyer task.
Send wanted range, reduced range, target value, size, substrate and quantity together.
These answers keep the request focused on reviewable engineering fields.
Transmission describes how much useful light should pass through a defined wavelength range. It should be paired with the range and the instrument context.
Send the target attenuation or OD if known, the working wavelength range, beam or source context, size and any mechanical constraints.
They can be clues, but the request should be translated into wavelength range, transmission or attenuation target, OD, size, substrate and use context.
