PAL vs UVC for Infrared Camera Modules

You pick a thermal sensor. 640×512, 12μm, 25mK NETD. Then checkout asks: PAL or UVC?

This one choice decides if your module plugs into a drone VTX with no lag — or into a laptop and just works. Pick wrong and you're buying frame grabbers, adapters, and a second module.

What They Are

PAL — Analog, zero latency

720×576 at 25 fps. Single composite video wire. No drivers. No OS. The sensor grabs a frame, the module pushes it out. That's the whole pipeline.

PAL runs the FPV ecosystem — analog goggles, 5.8 GHz VTX, DVR boards. It's old. That's the point. Simple = fast.

UVC — Digital, plug and play

USB Video Class. Plug into Windows, macOS, Linux, Android. The OS sees a webcam. No driver. Open any app, feed is there.

The cost: latency. USB polling, driver buffers, app queues — every step adds delay.

Side by Side

Latency Is the Deciding Factor

At 40 km/h you cover 11 meters per second. PAL's 15 ms = you move 16 cm between seeing and reacting. UVC's 150 ms = 1.65 meters. That's gate clearance vs a crash.

Where UVC latency comes from:

• USB polling — host doesn't read continuously. Polling interval: 1–8 ms per cycle.
• Driver buffers — kernel holds frames before user-space gets them. Adds 30–60 ms.
• App buffers — VLC, OpenCV queue frames for smooth playback. Another 20–60 ms.

PAL skips all three. Analog signal goes sensor → amplifier → display. No buffer. No polling.

Resolution: When It Matters

PAL caps at 720×576. For a 640×512 sensor, that's fine — you lose nothing. For 1280×1024, PAL is the bottleneck.

UVC outputs native sensor resolution. For radiometric work — where per-pixel temperature matters — this is real. For FPV flight, PAL's D1 is plenty.

Wiring

PAL: 3 pins — Video Out, GND, VIN (5V or 3.3V). Straight into a VTX on the drone, or FPV goggles on the ground. For PC: add a USB frame grabber. Works, but it's another device in the chain.

UVC: 4 pins — D+, D-, VBUS (5V), GND. Some have onboard USB-C. Plug into phone with OTG, open an app, feed is there. No capture hardware.

Which One for Your Setup

Hybrid Modules: Both Outputs

Some modules now ship with composite video pad (PAL) and USB-C (UVC) on the same board. Switchable by mode pin or firmware.

Best of both: PAL into the drone VTX for flight, UVC into a laptop for post-flight analysis. One module.

Common Mistakes

• Buying PAL for a phone project. You'll need a frame grabber. Native UVC saves the dongle and the headache.
• Buying UVC for FPV. 150 ms behind reality. You'll fly like the video is drunk.
• Assuming all Androids do UVC. Most modern phones support OTG UVC. Some budget devices and custom ROMs don't. Test with a cheap USB webcam first.
• Cheaping out on the frame grabber. A $5 EasyCap clone adds compression artifacts, frame drops, and 50–100 ms of its own latency. If you're bridging PAL → UVC, the capture device is part of your signal chain.

Quick Decision Table

PAL vs UVC isn't about one being better. It's about matching output to the rest of your signal chain. Check what your display device needs first, then pick the module output that feeds it with the fewest adapters.

FAQ