Quick Answer
The three main camera trigger methods for drone mapping are hot shoe adapters, built-in intervalometers, and flight controller software triggers. Hot shoe triggering gives the highest positional accuracy by capturing the exact shutter moment. Intervalometers are the simplest to set up but less precise. Software triggers via ArduPilot or Pixhawk offer full mission integration at the cost of slightly lower timing precision.
Why Camera Triggering Matters for Drone Mapping
In aerial surveying and photogrammetry, every photograph needs a precise geographic coordinate. The accuracy of your final orthomosaic, 3D model, or point cloud depends directly on how well each image is geotagged. That means knowing exactly where the camera was and, just as importantly, exactly when the shutter fired.
RTK and PPK workflows use GNSS receivers like the Emlid Reach RS4 Pro to log position data at high update rates (up to 10 Hz on the Reach M2). When a photo is taken, the receiver records a time mark. During post-processing, these time marks are matched to the GNSS position log to assign centimetre-level coordinates to each image.
The problem is that "when the shutter fires" is not always straightforward. There is a small delay between the trigger signal and the actual exposure, and that delay varies depending on how you trigger the camera. For mapping-grade results, you need a trigger method that minimises this uncertainty. We covered the broader RTK vs PPK decision in our RTK vs PPK for Drone Mapping comparison. This guide focuses specifically on the triggering piece of the puzzle.
Trigger Method 1: Hot Shoe Adapter
The hot shoe adapter (HSA) is the gold standard for camera triggering in survey-grade drone mapping. It connects directly to the camera's hot shoe mount, the same fitting used for external flashes, and detects the electrical signal that fires the shutter. Because the HSA sits in the signal path between the camera body and the actual exposure event, it captures the precise moment of capture with virtually no lag.
How It Works
The HSA plugs into the camera's hot shoe and connects to the GNSS receiver via a JST-GH cable. On the Emlid Reach system, you plug the cable into the C1 port on the Reach M2 or M+. Every time the camera takes a photo, the hot shoe sends an electrical pulse to the receiver, which logs it as a time mark in the raw GNSS data.
This is the same principle that synchronises a flash gun with a camera. The electrical contact in the hot shoe closes at the instant the shutter opens, making it the most direct and reliable way to detect the exact exposure moment.
Accuracy
Hot shoe triggering is the most accurate option available, with timing uncertainty typically under 1 millisecond. At a drone flying speed of 10 m/s, a 1 ms error translates to just 1 cm of positional uncertainty. For most mapping applications, this is negligible.
Setup
- Mount the hot shoe adapter on the camera's hot shoe
- Connect the JST-GH cable from the HSA to the C1 port on the Reach M2/M+
- Configure the camera's trigger source (intervalometer, autopilot, or manual)
- Verify time marks are appearing in Emlid Flow before flight
Limitations
The main limitation is hardware compatibility. Your camera must have a standard hot shoe mount. Most interchangeable-lens cameras from Sony, Canon, and Nikon have one. Consumer drones like the DJI Mavic or Phantom series do not provide hot shoe access, ruling out this method entirely for those platforms.
Trigger Method 2: Intervalometer (Camera Timelapse)
An intervalometer triggers the camera at fixed time intervals, typically every 2 to 5 seconds. Many cameras have this feature built in, often called "timelapse" or "interval shooting" mode. It is by far the simplest trigger method to configure.
How It Works
You set the camera to take a photo at a regular interval (for example, every 3 seconds) using its own internal timer. The GNSS receiver independently logs position data. Since there is no electrical connection between the camera and the receiver, the two systems are synchronised by timestamp alone.
The receiver does not log time marks in this scenario. Instead, during post-processing, the software interpolates the camera's position based on the GNSS log and the known capture interval. This introduces a small amount of uncertainty because the exact shutter moment is estimated rather than measured.
Accuracy
Intervalometer timing is less precise than hot shoe triggering. Most cameras have a small but variable delay between the scheduled interval and the actual shutter release, typically 10 to 50 milliseconds. At 10 m/s flight speed, a 50 ms error equals 50 cm of positional uncertainty. For many mapping jobs this is acceptable, but it falls short of survey-grade requirements.
Setup
- Enable timelapse or interval shooting mode on the camera
- Set the desired interval based on flight speed and required overlap
- Start the intervalometer before take-off and stop it after landing
- No physical connection to the GNSS receiver is needed
Best For
Intervalometer triggering is a good fit for lower-accuracy mapping jobs, quick site surveys, or situations where you cannot physically connect a cable to the camera. It is also useful as a fallback when hot shoe hardware is unavailable. If you are using ground control points to anchor your map (as we explain in our Ground Control Points Guide), the lower trigger accuracy can be compensated by the GCP network.
Trigger Method 3: Flight Controller Software Trigger
Flight controllers running ArduPilot or PX4 can trigger the camera directly as part of the autopilot mission. This is the most integrated approach, allowing the camera to fire at specific waypoints, at fixed distance intervals, or on a timed schedule controlled by the flight plan.
How It Works
The flight controller sends a signal to the camera via a servo output or relay. In ArduPilot, this is configured using the DO_DIGITAL_SERVO or DO_SET_SERVO MAVLink commands within the mission plan. The signal travels from the flight controller's PWM output through a cable to the camera's trigger input (usually a USB, HDMI, or dedicated remote port depending on the camera model).
When the shutter fires, the hot shoe adapter (if fitted) can still send a time mark back to the GNSS receiver. This creates a two-stage system: the flight controller initiates the trigger, and the hot shoe confirms the exact moment of capture. For the best results, use both together.
Accuracy
Software trigger accuracy sits between the hot shoe and intervalometer methods. The main source of uncertainty is the shutter lag: the time between the flight controller sending the signal and the camera actually taking the photo. This lag varies by camera model and can range from 20 ms to over 200 ms on older cameras. Without a hot shoe adapter to confirm the actual capture moment, you are relying on an assumed lag value, which may not be consistent.
Setup
- Connect the flight controller's servo output to the camera trigger input
- In Mission Planner (or your ground station software), configure the camera trigger parameters
- Set
CAM_TRIGG_TYPEto 1 (servo) and adjust the servo PWM values for trigger on/off - Use
DO_DIGITAL_SERVOcommands in the mission to trigger at waypoints or distance intervals - If using a Reach M2/M+, connect the hot shoe adapter to the C1 port for time mark logging
Best For
Software triggering is the right choice when you need full mission integration. It ensures the camera fires at precisely planned positions, maintaining consistent front and side overlap across the survey area. This is the standard approach for professional mapping with platforms like the GPS navigation systems and flight controllers from our range.
Comparing the Three Methods
| Feature | Hot Shoe | Intervalometer | Software Trigger |
|---|---|---|---|
| Timing accuracy | Under 1 ms | 10 to 50 ms | 20 to 200 ms |
| Positional error at 10 m/s | Under 1 cm | 10 to 50 cm | 20 to 200 cm |
| Setup complexity | Medium | Low | High |
| Hardware required | Hot shoe adapter, cable | None (built-in) | Flight controller, trigger cable |
| GNSS time marks | Yes | No | Yes (with HSA) |
| Camera compatibility | Hot shoe required | Timelapse feature | Remote trigger port |
| Mission integration | Works alongside | Independent | Full |
Which Trigger Method Should You Use?
For Survey-Grade Mapping
Use the hot shoe adapter combined with a flight controller software trigger. The flight controller ensures the camera fires at planned positions for consistent overlap, while the hot shoe captures the exact shutter moment for centimetre-level geotagging. This combination gives you the best of both worlds: mission control and timing precision.
For General Mapping With GCPs
An intervalometer with a solid network of ground control points is often sufficient. The GCPs correct for positional errors during processing, compensating for the lower trigger timing accuracy. This is the simplest setup and works well for construction site monitoring, agricultural surveys, and other applications where absolute accuracy of 2 to 5 cm is acceptable.
For Integrated Autopilot Missions
If you are running automated survey flights with GPS modules and ArduPilot or PX4, the software trigger is your starting point. Add a hot shoe adapter for time marks if your camera supports it. The resulting data will work well in PPK processing tools like Emlid Studio, as we covered in our guide to using the Emlid Reach RS4 Pro for drone mapping.
Practical Tips for Reliable Triggering
- Test before you fly. Set up your trigger system on the bench and verify time marks appear in Emlid Flow or your receiver's interface. A missed connection on the ground is easy to fix. A missed connection at 100 metres altitude is not.
- Check overlap. Whatever trigger method you use, verify that front overlap is at least 60% and side overlap at least 30%. These are minimums for reliable photogrammetry. Increase to 75% / 50% for challenging terrain or when using lower-resolution cameras.
- Account for shutter lag. If you are using software trigger without a hot shoe, measure your camera's shutter lag by comparing the trigger command timestamp against the actual exposure. Some cameras publish this value; otherwise, test it empirically.
- Isolate the GNSS receiver. Keep the Reach M2/M+ away from radio transmitters, video transmitters, and high-current wiring. Electromagnetic interference can cause cycle slips that degrade position accuracy and may cause missed time marks.
- Log raw data on both base and rover. Even with perfect triggering, PPK processing needs raw observation files from both the base station and the rover. Double-check logging is enabled on both before take-off.
FAQ
Q: Can I use a hot shoe adapter with a DJI drone?
A: Most DJI consumer drones (Mavic, Phantom, Mini series) do not expose a hot shoe connection, so the HSA method is not an option. You would need to use GCPs for georeferencing or a DJI platform that supports PPK natively, such as the Matrice series with the right payload.
Q: Do I need a hot shoe adapter for PPK mapping?
A: It is not strictly required, but it is strongly recommended for survey-grade results. Without it, you are relying on interpolation or assumed timing, which introduces positional uncertainty. For the small extra cost and setup effort, the accuracy improvement is significant.
Q: What is the best trigger interval for drone mapping?
A: This depends on your flight speed, altitude, and required ground sample distance (GSD). A common starting point is 2 to 3 seconds between shots at a flight speed of 5 to 8 m/s, which typically produces 70% front overlap at 50 to 80 metres altitude. Adjust based on your specific camera and mission parameters.
Q: Can I combine multiple trigger methods?
A: Yes, and this is actually the recommended approach for professional mapping. Use the flight controller's software trigger to fire the camera at planned positions, and connect a hot shoe adapter to log the exact capture moment. The software trigger controls when to shoot, and the hot shoe records precisely when the shutter actually fired.
Q: What is the DO_DIGITAL_SERVO command in ArduPilot?
A: It is a MAVLink mission command that tells the flight controller to pulse a servo output to a specified PWM value. In mapping missions, this pulse is wired to the camera trigger input and fires the shutter. You can set it to trigger at waypoints or at distance intervals using the CAM_TRIGG_DIST parameter.