Knowing what to ask before buying a thermal camera core can prevent expensive redesigns later. A thermal core is not only a detector board. It is an imaging chain that includes the focal plane array, optics, readout electronics, correction algorithms, video output, firmware controls, calibration data, mechanical mounting, and supplier support. If the buyer asks only about resolution and price, important integration risks stay hidden until sample testing or production.
The best questions connect the supplier’s specification to the real product. What target must the system detect? At what distance? Under which temperature and weather conditions? Which host processor, interface, enclosure, lens, and power budget will be used? The answers determine whether an uncooled LWIR core, cooled MWIR core, dual-band module, or integrated imaging system is the right starting point.
Questions About the Application
Start with the mission. Ask the supplier which applications the core has already supported and what test evidence is available for scenarios similar to yours. A core used for indoor inspection may not be suitable for long-range perimeter security. A core designed for compact robotics may not have the optical, mechanical, or environmental margin needed for a stabilized payload.
Provide the supplier with target size, required range, field of view, motion conditions, operating temperature, humidity, vibration, and whether the output will be used by a human operator, a measurement algorithm, or AI analytics. If the supplier cannot translate those conditions into detector format, pixel pitch, focal length, frame rate, and interface recommendations, the selection risk is high.
For example, a close-range inspection product may only need a compact LWIR module such as the SPECTRA L06 640x512 LWIR 12um. A long-range or high-detail product may need higher resolution like the SPECTRA L12 1280x1024 LWIR or a cooled MWIR platform such as the SPECTRA M12 1280x1024 Cooled MWIR.
Questions About Detector and Optics
Ask for detector format, pixel pitch, spectral band, NETD, frame rate, operability, bad pixel criteria, integration time behavior, and operating temperature range. These values should include test conditions. NETD without f-number, ambient temperature, frame rate, and processing mode is not enough for comparison.
Optics should be discussed at the same time as the detector. Ask which focal lengths are available, what horizontal and vertical FOV each lens provides, whether the lens is fixed focus or motorized focus, what the minimum focus distance is, and whether the lens is calibrated with the core. If the project needs long-range DRI performance, ask for pixels-on-target estimates under stated target size and distance assumptions.
For dual-channel or PTZ systems, also ask about boresight alignment, focus repeatability, lens heating, vibration behavior, and whether the thermal core can synchronize with a visible channel. These details often decide whether the module is easy to integrate into a real system.
Questions About Image Quality and Calibration
Image quality questions should go beyond sample photos. Ask how non-uniformity correction is performed, whether the core uses a shutter, how often NUC is needed, and what image interruption occurs during correction. Ask about temporal noise, fixed pattern noise, dead-pixel replacement, dynamic range, AGC behavior, polarity modes, and latency from sensor exposure to video output.
If the system needs radiometric temperature data, ask how the module is calibrated, what measurement range is supported, what accuracy conditions apply, how emissivity and reflected temperature are handled, and whether temperature metadata is aligned with the image stream. A camera core that looks good visually may still be unsuitable for measurement if radiometric behavior is not controlled.
It is also useful to ask for raw, corrected, and enhanced image options. OEM teams may want raw or lightly processed output for analytics, while operators may prefer enhanced video for visual interpretation. The supplier should explain which outputs are available and how processing settings affect repeatability.
Questions About Interfaces and Firmware Control
Interface questions should be specific. Ask whether the core supports MIPI, LVDS, Camera Link, USB, GigE, Ethernet, HDMI, SDI, analog video, or a custom output. Request electrical levels, connector models, timing diagrams, command protocol, SDK support, reference software, and firmware update procedures. Do not assume that a displayed image means the interface will be easy to integrate into your host system.
Firmware control is equally important. Ask which parameters can be changed by command: gain mode, integration time, NUC, AGC, palette, polarity, digital zoom, ROI, frame rate, metadata, temperature measurement, shutter behavior, and startup defaults. If a parameter requires custom firmware, ask about cost, schedule, version control, and future compatibility.
For networked cameras or security systems, ask about protocol support, cybersecurity expectations, metadata format, and whether the core can support the final product’s video pipeline. For embedded products, ask about boot time, power sequencing, heat dissipation, and how errors are reported to the host processor.
Questions About Mechanical, Environmental, and Production Fit
Ask for 2D drawings, 3D models, mounting hole tolerances, connector position, lens envelope, center of gravity, heat-sinking requirements, and recommended assembly process. A core that fits on a desk may still conflict with an enclosure, gimbal, drone payload, or vehicle mount.
Environmental questions should include operating temperature, storage temperature, humidity, vibration, shock, lens sealing, condensation risk, and warm-up behavior. For airborne, border security, and power inspection systems, platform environment can be as important as detector specification.
Production questions should cover serial-number traceability, calibration data storage, acceptance test criteria, firmware revision control, change notification, repair process, and expected product life. A good supplier can support not only the first sample but also repeatable production.
Questions About Commercial Terms and Compliance
Before placing an order, ask about sample price, MOQ, lead time, production capacity, payment terms, warranty, repair turnaround, spare parts, and customization fees. The article How to Buy Thermal Camera Modules from China covers the broader procurement workflow, but the key principle is simple: commercial terms must match engineering risk.
Ask what documents are available for export, customs, and product compliance. Requirements vary by product configuration and destination, so buyers should verify details with qualified logistics or compliance partners. The supplier should at least be able to identify part numbers, firmware versions, lens options, packing requirements, and serial-number records.
Finally, ask what happens after the first order. Will the same detector, lens, connector, and firmware remain available? How will product changes be announced? Is there a last-time-buy process? Long-term availability can be as important as image quality for OEM products.
FAQ
What is the first question to ask before buying a thermal camera core?
Ask whether the core matches the real application: target size, required range, field of view, environment, interface, power, and output type. If the application is unclear, the supplier cannot recommend the right detector, lens, or interface.
Is resolution the most important specification?
No. Resolution matters, but it must be evaluated with pixel pitch, lens focal length, field of view, NETD, frame rate, image processing, and interface bandwidth. A higher-resolution core can underperform if optics or integration are weak.
Should I ask for raw thermal data?
Ask for it if the product uses analytics, custom image processing, or radiometric measurement. Some applications only need enhanced video, but OEM teams should know what data levels are available before committing to a core.
What should be tested on samples?
Test image quality, focus, NUC, latency, power, interface timing, firmware commands, mechanical fit, environmental behavior, radiometric stability if needed, and consistency between units.
