Drones with Thermal Cameras: OEM Integration, 640 LWIR Payloads & Selection Guide
Drones with Thermal Cameras: OEM Integration, 640 LWIR Payloads & Selection Guide
Thermal imaging is used in commercial UAVs, search-and-rescue systems and robotic inspection platforms. Equipping drones with thermal cameras complements visible imaging by detecting emitted infrared radiation without visible illumination. Useful contrast still depends on the target and background, optics, atmosphere and line of sight: dense fog, some plumes and intervening foliage can attenuate or block the thermal view.
Building an OEM payload means balancing Size, Weight, Power, and Cost (SWaP-C) against field of view and spatial resolution. Instantaneous Field of View (IFOV) describes angular sampling; Noise Equivalent Temperature Difference (NETD) describes thermal sensitivity under stated conditions. Choose onboard, ground-based or combined processing according to the control-loop latency budget, link reliability and operator workflow.
Onboard inference can reduce dependence on a video downlink, but processing capacity alone does not establish supported algorithms, sensor fusion, gimbal control or behavior during a link outage. Confirm those functions for the selected hardware and firmware, then validate the complete system.

This technical integration guide helps drone design engineers, systems integrators and payload specialists plan visible/thermal imaging, 640×512 LWIR configurations and onboard processing for civilian inspection and observation. Product specifications, integration requirements and application-level performance must be evaluated separately.
Table of Contents
- 👉 1. Detector Physics: Uncooled VOx LWIR Microbolometers in UAV Payloads
- 👉 2. Dual-Spectrum Optical Architecture & Sensor Fusion
- 👉 3. Onboard Edge-AI Acceleration & Low-Latency Tracking Pipelines
- 👉 4. Flight Controller Integration, SWaP-C & Protocol Architectures
- 👉 5. OEM Dual-Spectrum Module Specifications & Direct Comparison
- 👉 6. Engineering Selection Framework: Radiometric Payloads vs. Edge Tracking Modules
- 👉 7. Frequently Asked Questions (Deep-Dive Technical FAQ)
1. Detector Physics: Uncooled VOx LWIR Microbolometers in UAV Payloads
Infrared cameras operate in different spectral bands. SWIR imaging commonly uses reflected illumination, while many high-performance MWIR systems use cooled detectors; neither statement is a universal rule for every camera design. Uncooled LWIR imaging, commonly specified over 8–14 µm, is useful for compact UAV payloads because objects near ambient temperature emit strongly in this band. For ideal blackbodies from -40°C to +80°C, Wien’s displacement law places peak emission at approximately 12.4 to 8.2 µm; usable image contrast still depends on the scene and optical path.
Microbolometer Operating Principles
At the center of an aerial thermal core sits an uncooled microbolometer focal plane array (FPA). Think of it as a microscopic 2D grid of tiny thermal absorption membranes suspended over a silicon Readout Integrated Circuit (ROIC) by ultra-fine structural bridges. When incoming LWIR photons strike those membranes, their physical temperature climbs. That temperature bump alters the material’s electrical resistance. The ROIC sweeps the array, picks up those tiny resistance shifts, and converts them into raw digital voltage counts via high-resolution analog-to-digital converters (ADCs).
Vanadium Oxide (VOx) vs. Amorphous Silicon (α-Si)
Vanadium oxide (VOx) and amorphous silicon (α-Si) are both used in resistive microbolometers. Material choice alone does not rank complete camera performance: compare detector design, optics, readout electronics, frame conditions and image processing using matched specifications.
| Detector Parameter | Vanadium Oxide (VOx) | Amorphous Silicon (α-Si) |
|---|---|---|
| NETD (Thermal Sensitivity) | Compare a specified detector at matched temperature, f-number and frame conditions | Compare a specified detector at the same conditions |
| Temperature Coefficient of Resistance (TCR) | Material and process dependent; TCR alone does not determine system NETD | Material and process dependent; TCR alone does not determine system NETD |
| 1/f Electronic Noise | Evaluate detector and readout noise for the actual design | Evaluate detector and readout noise for the actual design |
| Thermal Time Constant (τ) | Use the detector-specific response specification | Use the detector-specific response specification |
| Motion Performance | Validate optics, response time, exposure, processing and stabilization | Validate optics, response time, exposure, processing and stabilization |
NETD should be compared at the same scene temperature, lens f-number and measurement conditions. A lower specified NETD can help distinguish small temperature differences, but does not establish detection range, calibrated temperature accuracy or visibility through foliage. The current VisionCube listing does not publish a detector-material or NETD specification to transfer into this comparison.
Pixel Pitch Scaling and Optomechanical Weight Reduction
For a fixed array size, smaller pixels reduce the active detector dimensions. A 640×512 array with 17 µm pitch has a 10.88×8.704 mm active area and a diagonal of approximately 13.93 mm. At 12 µm pitch, the active area is 7.68×6.144 mm and the diagonal is approximately 9.84 mm. These are calculated active-array dimensions, not package dimensions.
In the small-angle approximation, IFOV is pixel pitch divided by focal length. At the same IFOV, changing pitch from 17 to 12 µm permits focal length to scale by 12/17, or about 0.706. If the f-number also stays constant, the entrance-pupil diameter scales by the same factor. Actual lens mass, modulation transfer, housing and gimbal load depend on the optical design; this geometry does not establish a fixed percentage reduction in lens or payload mass.
Use the thermal imaging calculator for preliminary field-of-view, scene-coverage and pixel-sampling estimates at the intended working distance. Validate those estimates with the selected optics and representative scenes; geometry alone does not establish detection range, tracking performance or temperature accuracy.
If the project requires native 1280×1024 sampling, retain that requirement when evaluating a high-resolution core. This array has four times the pixel count of 640×512, but coverage and ground sampling also depend on pixel pitch, lens and altitude. A 640×512 module is a separate lower-resolution design choice, not an equivalent replacement for a native 1280×1024 requirement.
2. Dual-Spectrum Optical Architecture & Sensor Fusion
Thermal imaging provides information from temperature-related infrared contrast, but does not reproduce visible color or reliably resolve every painted marking. Contrast can fall when target and background radiance become similar. Visible cameras provide complementary color and detail when illumination and visibility permit; performance in low light, shadows and obscurants depends on the specific camera and scene.
A dual-spectrum payload combines visible and thermal channels. Mechanical alignment, calibration, timing and display software determine how those views can be compared; a shared product family does not by itself establish pixel-registered fusion or a fully integrated gimbal payload.
Optomechanical Alignment and Parallax Compensation
Spatially separated visible and thermal cameras have different viewpoints. Parallax depends on camera separation and scene depth, so there is no universal 30 m cutoff. If the application needs aligned overlays, characterize distortion and relative camera geometry across the intended working distances, and validate the registration on scenes with depth variation.
- ⚙️ Calibration: Obtain the selected assembly’s intrinsic and relative-camera calibration, or plan a calibration procedure. A single planar transform does not guarantee alignment for objects at different depths.
- ⚙️ Depth-Dependent Registration: If the application uses depth or range information to improve alignment, confirm the range source, coordinate frames and software support. The current VisionCube listing does not establish an included laser rangefinder or real-time depth-warping pipeline.
| Optical Channel Feature | AI VisionCube ST Pro | AI VisionCube DT Pro |
|---|---|---|
| Visible (EO) Resolution & Rate | 1920 × 1080 at 30 Hz | 1920 × 1080 at 30 Hz |
| Visible Optical Format & Focal Length | 1/2.8-inch brochure entry; single 4 mm lens | Conflicting 1/2.8-inch and 1/2.6-inch brochure entries: confirm BOM; 3.9 mm wide + 12 mm telephoto |
| Visible Field of View (H / V) | 69° / 42° | Wide: 72° / 45°; telephoto: 26° / 15° |
| Visible Sensitivity (as supplied) | 7341 mV/lux·s; not a minimum-illumination lux rating | 9650 mV/lux·s; not a minimum-illumination lux rating |
| Thermal Core Resolution & Rate | 640 × 512 at 50 Hz | 640 × 512 at 50 Hz |
| Thermal Pixel Pitch & Spectral Band | 12 µm, 8–14 µm LWIR | 12 µm, 8–14 µm LWIR |
| Thermal Focal Length & FOV | 9.1 mm; 45.9° H × 36.9° V | 9.1 mm; 45.9° H × 36.9° V |
Dual-Light Image Fusion and PIP Presentation
The VisionCube brochure lists picture-in-picture (PIP) support. Treat display composition and geometrically registered sensor fusion as separate functions:
- ✅ Picture-in-Picture (PIP): Displays one camera view within another. Confirm the selectable channels, placement and controls for the ordered configuration; PIP alone does not prove pixel-level registration.
- ✅ Dual-Light Image Fusion: If registered visible/thermal overlays are required, request confirmation of that function and its calibration limits. The current VisionCube source does not establish a particular edge-extraction algorithm, palette set or guaranteed fusion output.
A complete handheld ground-observation instrument serves a different role from an airborne OEM module. Keep its optics, display, power, enclosure and operator workflow explicit when planning ground verification. Do not assume automatic data sharing or coordinated target tracking with VisionCube. The thermal imager selection guide explains the distinction between OEM-core integration and a finished handheld instrument.
3. Onboard Edge-AI Acceleration & Low-Latency Tracking Pipelines
Ground-based vision processing depends on the video link. Evaluate the following factors when deciding which functions should run onboard:
- ⚠️ Downlink Latency: Measure capture, buffering, encoding, transport and decoding delays under the intended operating conditions. Do not assume a fixed transport delay across different links.
- ⚠️ Signal Dropouts: Define behavior for stale frames, packet loss and link interruption. A tracker may predict through a short gap, but recovery and safe behavior depend on its implementation and validation.
- ⚠️ Compression: Test the chosen codec, bitrate and image settings against representative inspection scenes. Compression can affect small features and downstream inference; its effect depends on the configuration.
Onboard AI Processing and Integration Requirements
The current AI VisionCube ST Pro combines one visible camera, 640×512 thermal imaging and 1 TOPS of advertised AI processing. AI VisionCube DT Pro combines wide-angle and telephoto visible cameras, the same Pro thermal resolution and 6 TOPS. Both list 1920×1080 visible output at 30 Hz and 640×512 thermal imaging at 50 Hz. TOPS describes advertised compute capacity, not a guaranteed application frame rate or tracking result.
Before designing a host application, request the interface and software documentation that matches the selected VisionCube variant and firmware. The thermal-camera table lists USB, but does not establish the complete host API, raw-frame path, neural-network format or deterministic processing latency. Use the following as an integration checklist:
- ⚙️ Frame Timing: Verify timestamps, buffering and synchronization between the advertised 30 Hz visible and 50 Hz Pro thermal streams. Different nominal rates do not establish hardware synchronization or eliminate temporal skew.
- ⚙️ Inference Validation: Establish which models and object classes are supported, then test representative scenes and minimum usable object size. The current source does not publish a minimum detection threshold.
- ⚙️ Tracking Validation: Request the supported tracking behavior and test identification continuity through motion and occlusion. Do not infer an algorithm or a maximum number of simultaneous tracks from the TOPS rating.
- ⚙️ Gimbal Integration: Confirm whether usable tracking outputs and a supported gimbal-control path are supplied. Measure the full camera-to-actuator loop; onboard processing does not establish direct motor drive or a particular response time.
Tracking Requirements and Validation
If an application needs assisted tracking, define the required behavior with the supplier and test it on the selected configuration:
- ✅ Target Selection: Confirm whether the supplied software provides manual selection, automatic selection or a host control interface, and how selection is cleared or overridden.
- ✅ Occlusion and Recovery: Test how the system reports loss of sight and whether it can reacquire the same object. Prediction is not evidence of visibility through tunnels, foliage or buildings.
- ✅ Relative Motion: Validate the chosen camera, exposure, scene and processing configuration over the expected motion envelope. Supplier demonstration annotations do not establish a guaranteed target-speed limit for ST Pro or DT Pro.
Validate throughput, dropped frames and recovery using the actual host interface and application load. Use the supported interface definition and measured test results when assessing compatibility and flight reliability.
4. Flight Controller Integration, SWaP-C & Protocol Architectures
Integrating dual-spectrum thermal payloads into an airframe demands careful attention to electrical power conditioning, mechanical weight distribution, thermal dissipation paths, and autopilot communication protocols.
Electrical Power Conditioning & Ground Loops
The VisionCube brochure gives a 9–16 V input range for the processing-board reference. Size the payload supply for the full battery voltage range, transients and measured startup and steady loads. Battery cell count alone does not establish compatibility; a nominally suitable pack can exceed the board’s input limit when fully charged.
Select regulation, filtering, protection and grounding for the actual board, harness and noise environment. Confirm supply-current requirements, signal reference levels and connector pin assignments before wiring. Do not assume a shutter-current profile or separate signal grounds without the matching interface documentation.
Mechanical SWaP-C & Thermal Dissipation Management
The current common processing-board reference is 38×38×29 mm, with 25.5×25.5 mm mounting and 43.8 g board weight. The Pro thermal-camera reference is 26×26×21.1 mm and ≤23 g, excluding lens and connectors. These component figures are not total payload dimensions or mass: include cameras, optics, cables, mounts, enclosure, cooling and any gimbal in the aircraft budget.
Plan and test a heat path for the processing board under sustained application load, while limiting avoidable heating and gradients near the thermal camera. TOPS alone does not determine power or heat output. Verify temperature limits, image stability and any correction interruptions for the delivered assembly; do not assume a particular shutter or NUC schedule.
Autopilot Protocols: CRSF and MAVLink Architecture
Open-source flight-control integration is a system engineering task. Confirm the exact VisionCube interface, electrical levels, messages and firmware support before planning a connection to ArduPilot, Betaflight or PX4; the current listing does not verify plug-and-play compatibility with those stacks.
- ⚙️ CRSF: If CRSF is required by the host design, obtain an explicit supported implementation and message mapping for the selected configuration. A UART connector or a TOPS rating does not establish CRSF support or a tracking-output update rate.
- ⚙️ MAVLink: If MAVLink is required, confirm the supported messages, coordinate frames, time bases and controller-side behavior. An image-space tracking result does not by itself provide a target GPS position or authorize an autonomous aircraft maneuver.
For core selection and mechanical trade-offs, consult the Infrared Camera Module OEM Buying Guide. Request a matched VisionCube mechanical drawing, connector definition and software/interface package before finalizing the host design. VisionCube DT Pro has a dedicated AI interface, so use the documentation for the exact DT Pro assembly rather than an ST pin definition or another product family’s SDK. Confirm that each document matches the selected hardware and firmware revision.
5. OEM Dual-Spectrum Module Specifications & Direct Comparison
The following matrix compares the current AI VisionCube ST Pro and DT Pro configurations. Published component specifications are separated from functions that still need configuration-specific confirmation; neither column is a complete aircraft-integration guarantee.
| Specification Dimension | AI VisionCube ST Pro | AI VisionCube DT Pro |
|---|---|---|
| Advertised AI Processing | 1 TOPS | 6 TOPS |
| CPU System Architecture | Not specified in the current listing; request the matched hardware documentation | Not specified in the current listing; do not inherit a different model’s CPU specification |
| EO Visible Camera Sensor | Single visible camera; 1/2.8-inch brochure entry | Dual visible cameras; conflicting 1/2.8-inch / 1/2.6-inch brochure entries require BOM confirmation |
| EO Visible Resolution & Frame Rate | 1920 × 1080 at 30 Hz | 1920 × 1080 at 30 Hz |
| EO Visible Lens Optics & FOV | 4 mm; 69° H × 42° V | 3.9 mm wide: 72° H × 45° V; 12 mm telephoto: 26° H × 15° V |
| Thermal Spectral Band & Detector Material | 8–14 µm LWIR; detector material not specified | 8–14 µm LWIR; detector material not specified |
| Thermal Pixel Pitch & Array Size | 12 µm; 640 × 512 at 50 Hz | 12 µm; 640 × 512 at 50 Hz |
| Thermal Lens Focal Length & FOV | 9.1 mm; 45.9° H × 36.9° V | 9.1 mm; 45.9° H × 36.9° V |
| Detection Range References | No guaranteed application detection range established by current source | No guaranteed application detection range established by current source |
| Minimum Target Resolution | Not specified; validate with selected software and scene | Not specified; validate with selected software and scene |
| Processing Latency | No guaranteed end-to-end latency established by current source | No guaranteed end-to-end latency established by current source |
| Dynamic Tracking Speed Limit | No guaranteed target-speed limit established by current source | No guaranteed target-speed limit established by current source |
| Maximum Identified Target Tracks | Not specified in the current source | Not specified in the current source |
| Tracking & Display Functions | PIP is listed; confirm required tracking and fusion functions | PIP is listed; confirm required tracking and fusion functions |
| Autopilot Control Protocol | CRSF/MAVLink support not established; request matched interface documentation | CRSF/MAVLink support not established; request DT Pro-specific interface documentation |
| Flight Controller Compatibility | No verified plug-and-play ArduPilot, Betaflight or PX4 integration | No verified plug-and-play ArduPilot, Betaflight or PX4 integration |
| Processing-Board Input | 9–16 V; verify supply and transient requirements | 9–16 V common board reference; verify the delivered assembly |
| Processing-Board Reference | 38 × 38 × 29 mm; 25.5 × 25.5 mm mounting; 43.8 g board only | 38 × 38 × 29 mm; 25.5 × 25.5 mm mounting; 43.8 g common board reference only |
| Camera Component Dimensions | Visible: 19 × 19 × 30 mm; Pro thermal: 26 × 26 × 21.1 mm, ≤23 g excluding lens/connectors | Visible: 40.8 × 25 × 26 mm; Pro thermal: 26 × 26 × 21.1 mm, ≤23 g excluding lens/connectors |
Detailed Product Overviews
AI VisionCube ST Pro: Single Visible Camera + 640×512 Thermal Imaging
The AI VisionCube ST Pro pairs a single 4 mm visible camera (69° H × 42° V) with a 640×512, 50 Hz Pro thermal camera using 12 µm pixels and 9.1 mm optics (45.9° H × 36.9° V). Visible output is 1920×1080 at 30 Hz, and advertised AI processing is 1 TOPS.
The current sample SKU is CC-VC-STPRO; the listing offers online orders for 1–99 units and requests a quotation for 100+ units. Confirm the included assembly, software, interface documents and dispatch schedule for the selected order. The component dimensions above do not establish aircraft fit, center of gravity or complete payload weight.
AI VisionCube ST Pro official product illustration; request a revision-matched drawing for mechanical integration.
View AI VisionCube ST Pro Configuration ➔
AI VisionCube DT Pro: Wide and Telephoto Visible Cameras + 640×512 Thermal Imaging
The AI VisionCube DT Pro combines 3.9 mm wide-angle visible optics (72° H × 45° V), 12 mm telephoto visible optics (26° H × 15° V) and 640×512 thermal imaging at 50 Hz. Its Pro thermal optics are 9.1 mm with 45.9° H × 36.9° V field of view; visible output is 1920×1080 at 30 Hz and advertised AI processing is 6 TOPS.
Confirm the final camera bill of materials because the supplied brochure contains conflicting D-family CMOS-format entries. Use the matching DT Pro interface documentation and validate the required software functions. The current sample SKU is CC-VC-DTPRO; the listing offers online orders for 1–99 units and requests a quotation for 100+ units. Confirm the included assembly and dispatch schedule.
AI VisionCube DT Pro official product illustration; request a revision-matched drawing for mechanical integration.
View AI VisionCube DT Pro Configuration ➔
6. Engineering Selection Framework: Radiometric Payloads vs. Edge Tracking Modules
Separate calibrated temperature measurement from imaging and AI processing when specifying a payload. A system can combine those capabilities, but neither thermal resolution nor TOPS establishes radiometric accuracy.
| Architectural Attribute | Calibrated Radiometric Payload | Visible/Thermal Imaging with AI Processing |
|---|---|---|
| Primary Mission Objective | Temperature measurement within specified range, accuracy and conditions | Imaging and any validated detection/tracking application |
| Calibration Requirements | Model-specific radiometric calibration plus scene and measurement corrections | Image calibration and any required geometric/timing alignment; NUC alone does not establish radiometry |
| Output Data Stream | Model-specific image/temperature data and conversion; confirm the host receiver | Confirm video formats, host API and any application outputs; PIP is listed for VisionCube |
| Onboard Compute Focus | Temperature conversion may run on the core, host or both, depending on the product | VisionCube ST Pro: 1 TOPS; DT Pro: 6 TOPS; supported software must be confirmed |
| Primary Use Case Fit | Validated solar, electrical and building thermography | Civilian inspection, observation and application-specific vision validation |
When to Select a Calibrated Radiometric Core
Choose a radiometric core when the mission requires temperature measurements, and verify its specified range, accuracy conditions, calibration and host-data path. Radiometry does not automatically provide certified or exact surface temperatures in every scene: emissivity, reflected radiation, distance, atmosphere and target size matter. The current CAMCUDA SuperMini 640TUltra-light core is a separate 640×512, 30 Hz thermographic OEM option; its V1.0.0 manual documents the model-specific temperature-data interfaces and limits. It is neither a 1280×1024 replacement nor a complete handheld instrument. Example inspection needs include:
- ⚙️ Solar Farm Inspections: Investigating abnormal thermal patterns under controlled operating and environmental conditions; a single temperature difference does not identify a specific electrical fault.
- ⚙️ Utility Grid Inspections: Comparing component temperatures with load, environmental conditions and an appropriate reference, within the measurement system’s accuracy limits.
- ⚙️ Building Envelope Audits: Identifying thermal patterns that may justify follow-up inspection for insulation or moisture problems; thermal images alone do not prove moisture content.
When to Select a Dual-Spectrum AI Tracking Module
Choose AI VisionCube ST Pro or DT Pro when the project needs the listed visible/thermal imaging configuration and onboard processing capacity for civilian inspection or observation. The current source does not specify calibrated temperature-measurement range or accuracy, nor guaranteed detection classes, tracking counts or speed limits. Validate any required application-level behavior for uses such as:
- ✅ Search and Rescue: Evaluating visible and thermal views to support trained operators; test detection and visibility under the actual terrain, weather and viewing conditions.
- ✅ Site and Asset Observation: Reviewing people, vehicles or infrastructure in the camera view, with any detection outputs and host integration confirmed for the selected software.
- ✅ Mobile Inspection: Assessing image quality and any assisted-tracking functions during representative vehicle or aircraft motion, without assuming performance through occlusion.

7. Frequently Asked Questions (Deep-Dive Technical FAQ)
Can modular thermal camera payloads be integrated into custom or open-source (ArduPilot/BetaFlight) drones instead of costly proprietary enterprise platforms?
Yes, a modular payload can be evaluated for a custom or open-source aircraft, but compatibility must be established for the complete design. The current AI VisionCube ST Pro and DT Pro specifications list a 9–16 V processing-board input and a common 38×38×29 mm board reference with 25.5×25.5 mm mounting. ST Pro provides one visible camera and 1 TOPS; DT Pro provides wide and telephoto visible cameras and 6 TOPS. Both Pro configurations list 640×512 thermal imaging at 50 Hz.
Before integration, obtain the exact hardware revision, connector pinout, electrical levels, software interface and supported control messages. DT Pro documentation must match the DT Pro assembly. The current listing does not establish plug-and-play CRSF/MAVLink, ArduPilot, Betaflight or PX4 compatibility, direct gimbal drive, license terms or complete payload fit.
What is the practical difference between radiometric thermal cameras and AI-assisted thermal tracking payloads for UAV operations?
Radiometry provides temperature measurements within specified calibration, range and accuracy conditions; imaging and AI processing support a different set of application needs, and the capabilities can coexist in a system. Surface emissivity, reflected radiation, atmosphere, distance and target size affect the interpretation of thermal measurements.
The current AI VisionCube ST Pro and DT Pro sources specify 640×512 thermal imaging and 1 TOPS / 6 TOPS respectively, but do not publish calibrated temperature-measurement range or accuracy. They also do not establish guaranteed tracking speeds, target counts or processing latency. For a separate thermographic OEM design, the CAMCUDA SuperMini 640T offers model-specific temperature-data paths at 30 Hz; confirm its manual, optics, host parsing and measurement conditions. It is a 640×512 core rather than a complete radiometric aircraft payload or handheld instrument.
How do you solve video latency and communication protocol bottlenecks when streaming thermal feeds from a UAV?
Build a latency budget covering capture, buffering, inference, encoding, transport, decoding and any actuator or display response, then measure it on the intended hardware. Running selected functions onboard can reduce dependence on the video link, but does not guarantee deterministic timing or tracking through packet loss.
For AI VisionCube ST Pro or DT Pro, verify the supported host interface and software functions instead of assuming raw MIPI ingestion, CRSF/MAVLink outputs or direct gimbal drive. The advertised rates are 30 Hz visible and 50 Hz Pro thermal, while 1 TOPS / 6 TOPS are compute ratings rather than measured application latency. Test timestamps, dropped frames, link interruptions and recovery against the actual system requirements.
📚 References & Further Reading
- Current Imaging Configurations: Published ST Pro and DT Pro optics, resolution, board references and ordering options on the AI VisionCube product page.
- Thermographic OEM Reference: Model-specific power, video and temperature-data information in the CAMCUDA SuperMini 640/640T Product Manual V1.0.0; 640T temperature functions do not apply to VisionCube or imaging-only SuperMini 640.
- High-Resolution Requirement: Specify native 1280×1024 sampling when the mission requires it; a 640×512 core does not meet the same pixel-array requirement. Evaluate scene coverage and sampling with the selected optics and altitude.
- OEM Procurement Guide: In-depth selection criteria for uncooled cores and optics via the Infrared Camera Module OEM Buying Guide.
- Complete Ground Observation: Compare the complete-instrument requirements in the OEM core integration vs. handheld selection guide. A bare core still needs optics, display, power and enclosure integration.
Technical author: Daniel · Hardware Support
Sales contributors: Vivian, Lena and Sophie





























