FPV Thermal Imaging Module RFQ Checklist and Deliverables

This buyer-first guide helps OEM/ODM teams issue an RFQ for an FPV Thermal Imaging Module that vendors can quote apples-to-apples. You’ll get a copy-ready checklist, spec definitions, acceptance tests, and the exact deliverables to request—so prototypes scale into reliable fleets and channel-ready products.

---

Executive Summary

• Standardize what you ask: optics/FOV, resolution, NETD, frame rate, power/peak current, interfaces, timestamps, and acceptance tests. Vendors then compete on engineering, not ambiguity.
• Tie performance to method: require target reflectivity/scene types, environment notes, and event-time timestamps so flight results match bench claims.
• Plan compliance early: thermal modules may be dual-use; EU Regulation (EU) 2021/821 and US BIS (e.g., ECCN 6A003 for many >9 Hz cameras) affect quoting and logistics.
• Choose deliverables that de-risk scale: per-serial calibration artifacts (aligned to ISO/IEC 17025), SDK docs, overlay scripts, and a short video acceptance clip.

Need hardware and SDK samples? Start with our Thermal camera module portfolio. If you plan to overlay distance later, see Laser Rangefinder Module.

Use Cases & Buyer Scenarios

FPV inspection platforms (utilities, rooftops, solar)

Wide-to-medium FOV, ≤50 mK NETD, 25–30 fps overlays, and clean power rails. Pair with Thermal Binoculars for ground confirmation.

Public safety night FPV

Stable overlays with event timestamps, simple HUD, and documented training SOPs (many programs reference NFPA 2400 competencies for sUAS).

Outdoor optics and demo fleets

Lightweight kits with repeatable HUD behavior across airframes; optional upsell paths into Thermal Rifle Scopes and Thermal Monoculars for cross-channel bundles.

---

Spec & Selection Guide (the heart)

Below are the parameters that belong in your RFQ—with plain-English definitions and trade-offs.

• Resolution & Optics/FOV
  256×192 or 384×288 are common for FPV overlays. Pair focal length to standoff distance and scene size.

• NETD (mK)
  Noise-Equivalent Temperature Difference—the smallest temperature delta the camera can resolve over noise. Lower is better; ≤50 mK is a practical target for night overlays.

• Frame Rate
  25–50 fps feels smooth in FPV goggles. Note: many >9 Hz thermal cameras fall under export controls (e.g., US BIS Category 6).

• Power & Peak Current
  Request steady-state power and peak/inrush profiles (cold start, AGC ramps).

• Interfaces & Time
  USB/MIPI/UART/CAN; require event-time timestamps in the SDK for stable HUD overlays.

• Mass & Mounting
  Ask for mass by sub-assembly (core, lens, mount) and datum drawings for repeatable boresight.

Quick comparison table—specs to collect

Decision rules 

If mission = wide-area search → wide FOV + ≤50 mK NETD + 25–30 fps.
If mission = confirmation/inspection → medium focal + ≤40–50 mK NETD + higher fps.
If export risk high → consider ≤9 Hz variant or plan licenses early (EU 2021/821, US BIS).
Always require event-time timestamps (SDK field) for HUD stability.

Integration & Engineering Notes

Electrical & Interfaces 

• Rails: Isolate VTX and compute rails; low-noise buck + LC filters to avoid banding.

• Headroom: Size DC-DC at ~2× steady-state to survive cold-start and AGC peaks.

• SDK fields: t_event_ns, temperature_px, palette_id, fps, supply_mv, status. Provide a minimal overlay sample.

Optics & Mechanics (mounting, alignment, vibration)

• Datums: Request V-groove/dowel pin drawings so boresight repeats after service.

• Isolation: Use elastomer standoffs tuned for the frame’s vibration spectrum.

• Windows: If enclosed, specify AR + anti-fog coatings and torque specs for consistent tilt.

Firmware/ISP/Tuning (AGC, palettes, HUD)

• AGC presets: Linear / histogram / target-lock; ship default LUTs so teams share a “thermal language.”

• HUD set: Keep to 3 primitives—temperature cursor, palette tag, and confidence bar—for low latency.

• Logging: Per-frame CSV or binary with event-time for audits and training.

Testing & Validation (bench → field, acceptance criteria)

• Bench: Verify overlay latency with a blinking heat source and a photodiode on the display.

• Field: Dusk panorama + rooftop/treeline scenes; save a 10–20 s clip per serial with power/FPS notes.

• Standards context: Many public-safety programs map procedures to NFPA 2400 (competency/operations) for repeatable training and reviews.

---

Compliance, Export & Certifications

• Dual-use/export
  The EU’s Regulation (EU) 2021/821 governs dual-use exports and is updated via delegated acts; classify before quoting. In the US, many higher-frame-rate thermal cameras are controlled under ECCN 6A003; ≤9 Hz models may fall under different entries (e.g., 6A993/NLR depending on destination).

• Calibration credibility
  Ask for calibration artifacts or references aligned to ISO/IEC 17025—this underpins traceable acceptance and audits.

• EMC/materials pack
  Vendors should provide CE/FCC/UKCA test reports and RoHS/REACH declarations alongside manuals and labels to accelerate distributor onboarding.

Planning to add a laser for range overlays? The LRF payload will also require IEC 60825-1 laser safety files. See our Laser Rangefinder Module page.

---

Business Model, MOQ & Lead Time 

• Samples: 2–4 weeks (standard lenses/SDK), 4–6 weeks (custom FOV/housings/HUD skins).

• MOQ: 50–200 pcs baseline; ≥300 pcs for custom enclosures/windows.

• Deliverables bundle (recommend): module + harness + low-noise buck + mounts, SDK docs, overlay script, calibration/acceptance data, and a 10–20 s acceptance clip per S/N.

• Attach strategy: For channel partners, bundle FPV payloads with Thermal Clip-On Sight or Thermal Pistol Sights as demo/loaner kits.

Mini ROI table—why a tight RFQ saves money

---

Pitfalls, Benchmarks & QA

Seven common mistakes (and fixes)

1. No method with performance claims. Require scene types and environment notes.

2. Using publish time instead of event time. Overlay “swim” and mis-sync ensue.

3. Ignoring peak current. Brownouts mid-flight; request inrush/cold-start data.

4. Over-spec resolution. Heavier optics and heat for marginal benefit.

5. No boresight datums. Post-service drift kills confidence.

6. Unclear export class. Shipments stall; pre-classify under EU 2021/821 and BIS.

7. Undefined acceptance. Debates replace data; demand per-serial clip + pass/fail sheet.

Benchmark recipe—detection vs recognition vs identification

• Detection: hotspot appears and persists ≥N frames at confidence ≥C.

• Recognition: operator can classify (human vs vehicle) at given FOV/distance.

• Identification: specific features visible under stable exposure.
  Use the same three scenes across lots; save clip + CSV per serial for traceability.

---

FAQs

1) What NETD should we ask for in the RFQ?
≤50 mK at 30 °C is a pragmatic target for FPV overlays; lower values improve small-signal detail, especially at dusk.

2) Why insist on event-time timestamps?
They keep HUD overlays aligned through the SDK → OSD → goggles chain—especially during fast yaw/roll.

3) Do we need >9 Hz for FPV?
25–30 fps looks best, but >9 Hz often triggers export controls (e.g., 6A003). Decide early to avoid quoting/shipping delays.

4) How “formal” should calibration be?
Request artifacts or references aligned to ISO/IEC 17025 so site acceptance and audits aren’t disputed.

5) Can we add range later without redoing the RFQ?
Yes. Reserve a UART/CAN and specify timestamps now. When ready, integrate our Laser Rangefinder Module for range/confidence overlays.

Email us your filled checklist and target airframe. We’ll return a side-by-side quote—two optics/NETD tiers, power options, and SDK deliverables—plus a sample and acceptance plan built on our Thermal camera module family.