365 nm requests often sit near UV excitation, fluorescence, shortpass and coated-window discussions. The useful first step is to separate the target band from the blocked range and mechanical context.
Prepare 365 nm Optical Filters fields for optical filter review with wavelength, bandwidth, blocking, geometry, product-family path, and RFQ checklist guidance.
365 nm is a starting point for a technical request, not a complete specification by itself. State whether the wavelength is used as an excitation band, emission band, blocking region, reference channel, sensing band, or alignment point so the filter family can be reviewed in context.
Use the wavelength together with bandwidth, blocking, AOI, and application context.
Prepare the target passband or cutoff behavior, FWHM or edge position when known, OD or blocking region, transmission context, and measurement condition. If the final band is still open, provide the working range and the optical path so the request can be discussed without overstating a fixed design.
Add bandwidth and blocking notes before requesting review.
Useful context includes fluorescence channel, machine vision illumination, sensing target, alignment use, imaging path, detector type, and any nearby wavelengths that must be separated. The page does not decide suitability; it helps the buyer prepare the fields needed for a technical conversation.
Describe the optical path and nearby bands that matter.
A wavelength request may point toward bandpass filters, edge filters, dichroic optics, neutral density filters, or coated elements depending on whether the task is selecting a band, removing a band, splitting a beam, reducing intensity, or fitting a mechanical geometry.
Choose the product family by optical function, then include the wavelength.
Include wavelength, acceptable tolerance or range, bandwidth, blocking region, AOI, substrate, dimensions, quantity, environment notes, and any spectrum file or drawing. Keep unconfirmed needs as open questions so the technical review can respond to the real uncertainty.
Prepare the technical note and attach spectra or drawings where relevant.
Ask for the product sheet, drawing review, coating discussion, or spectrum-related material that supports the evaluation. Document availability should be confirmed through the request path rather than assumed from the public page.
Send a document request with the wavelength and application context.
Use these fields to turn the page topic into a reviewable Lumalyx request.
Use 365 nm as the spectral anchor, then describe whether the request is UV pass, shortpass, fluorescence excitation, AR-coated window, or another optical path.
Prepare the target wavelength, FWHM or pass-band edges, OD or blocked range, UV source context, substrate, size, thickness and AOI. If UV exposure or material behavior matters, mark it as a review field rather than a finished requirement.
Start with spectral filters for bandpass or shortpass discussions, fluorescence bandpass filters for channel work, and coated optics when the request is about AR windows or component geometry.
Do not treat a 365 nm label as a complete specification. UV-adjacent requests need source, detector, substrate and blocking context before review.
Send known values, mark open values clearly, and include spectra or drawings when they explain the signal path.
A clearer wavelength request separates useful signal, unwanted light, geometry and commercial context.
Lumalyx can review the request more efficiently when 365 nm is paired with pass or blocked range, bandwidth, OD, transmission, source, detector and mechanical fields.
Start wavelength RFQA 365 nm request should say whether the wavelength is the wanted UV band, an excitation source, or part of a broader coated-window discussion.
| Field | Send when | Review note |
|---|---|---|
| 365 nm role | The UV band is the request anchor. | State whether it should pass, excite, or be blocked. |
| Blocked visible/NIR range | Detector or background light may matter. | Name unwanted wavelengths separately. |
| Substrate and size | UV path or window geometry is constrained. | Include drawing, AOI and clear aperture. |
Common RFQ contexts include UV excitation, fluorescence review, coated windows and compact analyzer paths.
A 365 nm label does not define the UV pass window or the visible/NIR blocking target.
Start with fluorescence bandpass or spectral filters when 365 nm is the wanted band; use coated components when the request is about a window or optical surface.
DACH, Japan and South Korea localization should wait for evidence of UV-specific engineering vocabulary or RFQ behavior.
Send 365 nm role, bandwidth, blocked ranges, OD target, substrate, size, AOI and spectra if available.
These answers keep the page focused on RFQ preparation and product-family navigation.
Send the 365 nm target, bandwidth or pass-band edges, blocked range, OD or transmission target, UV source context, substrate, size and AOI.
No. It should be paired with the role of the part, such as bandpass, shortpass, fluorescence excitation or coated-window review.
Yes. Mark substrate, thickness or exposure-related fields as open so the review can focus on missing information.
