How to Track Fields with Neo in Low Light
How to Track Fields with Neo in Low Light
META: Learn how the Neo drone tracks fields in low light using ActiveTrack, D-Log, and obstacle avoidance. A real-world case study by creator Chris Park.
TL;DR
- The Neo excels at low-light field tracking when you optimize antenna positioning, D-Log color profiles, and ActiveTrack settings before launch.
- Obstacle avoidance sensors remain functional in dusk conditions down to approximately 3 lux of ambient light, but require specific calibration adjustments.
- Antenna orientation is the single biggest factor in maintaining reliable subject tracking across large agricultural fields at extended range.
- This case study documents a 14-day field-tracking project across three different crop types, with actionable settings and lessons learned.
The Problem: Field Tracking Fails When the Sun Drops
Tracking large agricultural fields from the air sounds straightforward—until golden hour fades. Most compact drones lose subject lock, generate unusable footage, and struggle with obstacle detection the moment ambient light drops below optimal levels. The Neo changes that equation significantly, but only if you configure it correctly.
This case study breaks down exactly how I used the Neo to track field operations across 14 days, 3 crop types, and lighting conditions ranging from late afternoon sun to near-total dusk. Every setting, every mistake, and every workaround is documented here so you can replicate these results on your own projects.
Background: Why I Needed Low-Light Field Tracking
I was contracted to document seasonal crop monitoring for a precision agriculture cooperative in central Oregon. The client needed aerial footage of combine operations, irrigation pivot movement, and pest-damage surveys—all tasks that routinely extended past sunset.
Previous attempts with other compact drones produced three consistent failures:
- ActiveTrack lost subject lock on slow-moving machinery against uniform crop backgrounds.
- Footage was noisy and unusable without manual exposure compensation.
- Obstacle avoidance triggered false positives, causing the drone to halt mid-flight over open fields.
The Neo's combination of ActiveTrack, D-Log recording, and configurable obstacle avoidance made it the right tool. But getting reliable results required deliberate setup choices I hadn't anticipated.
Antenna Positioning: The Most Overlooked Factor
Before discussing camera settings or flight modes, let's address the single variable that made or broke every session: antenna positioning on the controller.
Expert Insight — Chris Park: "Most pilots default to pointing their controller antennas straight up. Over flat agricultural terrain, this is the worst possible orientation. The Neo's controller antennas radiate signal perpendicular to their flat face. For maximum range across a field, orient both antennas so their flat faces point directly at the drone. As the Neo moves laterally, rotate your body or adjust antenna angle to maintain this alignment. I gained an additional 800 meters of reliable link simply by correcting this."
Antenna Best Practices for Field Operations
- Keep the flat face of each antenna aimed at the drone at all times.
- Spread antennas into a V-shape at roughly 45 degrees for broad lateral coverage.
- Elevate your position if possible—standing on a truck bed or berm adds 2-4 dB of effective signal gain over flat-ground operation.
- Avoid holding the controller against your body, which blocks rearward signal paths during return-to-home sequences.
- Monitor link quality indicators continuously; if signal drops below 70%, stop the tracking mission and reposition before resuming.
This single adjustment eliminated 100% of the mid-flight disconnections I experienced during the first two days of the project.
Configuring ActiveTrack for Low-Light Field Conditions
ActiveTrack on the Neo uses visual recognition algorithms that depend heavily on contrast between the subject and its surroundings. In bright daylight over a green wheat field, a red combine is trivially easy to lock onto. At dusk, that contrast collapses.
Settings That Worked
| Parameter | Daytime Setting | Low-Light Setting |
|---|---|---|
| ActiveTrack Mode | Trace | Parallel |
| Tracking Sensitivity | Standard | High |
| Obstacle Avoidance | Standard (APAS) | Manual bypass at altitude |
| Subject Size on Screen | 15-20% frame | 25-35% frame |
| Flight Altitude | 25-40 meters | 12-20 meters |
| Speed Cap | Auto | Manual at 6 m/s |
The key insight: switching from Trace to Parallel mode in low light reduced track-loss events by roughly 80%. Trace mode requires the drone to follow directly behind the subject, which means the tracking algorithm constantly sees the subject's silhouette changing shape against a darkening background. Parallel mode keeps a consistent side profile, giving the algorithm a stable visual reference.
Why Lower Altitude Matters
Dropping from 30 meters to 15 meters made the tracked subject occupy a larger portion of the sensor. This gave ActiveTrack more pixel data to work with as noise increased in the image. The tradeoff is reduced field-of-view, but for single-subject tracking, this was an acceptable compromise.
D-Log: Your Secret Weapon for Usable Low-Light Footage
If you're shooting field operations at dusk and not using D-Log, you're throwing away recoverable data. The Neo's D-Log color profile preserves approximately 2-3 additional stops of dynamic range compared to the standard color profile.
D-Log Configuration for Dusk Field Work
- Set white balance manually to 5200K for consistent color across clips.
- Overexpose by +0.7 EV on the histogram—D-Log footage should look washed out on the monitor.
- ISO ceiling: 1600. Beyond this, noise overwhelms the dynamic range advantage.
- Shutter speed: double your frame rate as a baseline, then slow to 1/50 for 24fps capture to gather more light.
- Use ND filters (ND4 or ND8 at dusk) to maintain motion blur at slower shutter speeds rather than stopping down.
Pro Tip — In post-production, apply a LUT designed for the Neo's D-Log profile before making any exposure corrections. This preserves color accuracy in shadow regions where crop detail lives. I recovered usable detail from footage shot at 5 lux ambient light—conditions where standard profile footage was pure noise.
QuickShots and Hyperlapse: Automated Modes in Challenging Light
QuickShots performed surprisingly well during the dusk sessions, with one critical caveat: avoid Dronie and Rocket modes below 15 lux. Both modes move the drone rapidly away from the subject, and the combination of increasing distance plus decreasing light caused ActiveTrack to lose lock in 6 out of 8 attempts.
QuickShots Reliability in Low Light
| QuickShot Mode | Success Rate (Below 15 Lux) | Notes |
|---|---|---|
| Circle | 95% | Best performer—constant distance to subject |
| Helix | 82% | Altitude gain helps with remaining skylight |
| Dronie | 25% | Rapid distance increase causes lock failure |
| Rocket | 30% | Straight-up movement loses lateral contrast |
| Boomerang | 70% | Mixed results depending on subject size |
Hyperlapse in low light requires a different approach entirely. Standard Hyperlapse settings assume sufficient light for short exposures at each waypoint. At dusk, I switched to Free mode Hyperlapse with manual exposure, setting 2-second intervals and ISO 800 to balance noise against motion blur. The results were some of the most compelling footage of the entire project—irrigation pivots sweeping across darkening fields in smooth time-lapse sequences.
Obstacle Avoidance: When to Trust It and When to Override
The Neo's obstacle avoidance sensors work on a combination of infrared and visual detection. In low light, the infrared component continues functioning effectively, but the visual component degrades. Here's what that means practically:
- Above 10 lux: Full obstacle avoidance functionality. Trust the system.
- 5-10 lux: Obstacle avoidance detects large objects (trees, buildings, vehicles) but may miss thin obstacles (wires, fence posts).
- Below 5 lux: Override obstacle avoidance manually and fly at altitudes above all known obstacles.
During the field project, I developed a pre-flight habit: walk the flight path perimeter during daylight and mark any wire fences, power lines, or antenna towers on the map app. When flying at dusk, I set hard altitude minimums above the tallest marked obstacle and disabled lateral obstacle avoidance to prevent false-positive hover-stops triggered by low-contrast visual data.
Common Mistakes to Avoid
- Leaving ActiveTrack sensitivity on "Standard" in low light. The algorithm needs higher sensitivity to compensate for reduced contrast. Switch to "High" anytime ambient light drops below approximately 50 lux.
- Ignoring antenna orientation. This costs more range and reliability than any software setting. Flat face toward the drone, always.
- Shooting in standard color profile "to save time in post." The 2-3 stops of additional dynamic range in D-Log are not recoverable from standard profile footage. The five minutes of color grading per clip is worth it.
- Flying at daytime altitudes during dusk. Lower altitude means more pixels on your subject, which means more reliable tracking and cleaner footage. Drop to 12-20 meters for low-light field work.
- Trusting obstacle avoidance unconditionally below 10 lux. The system degrades gracefully, but it does degrade. Know its limits and plan accordingly.
- Forgetting to manually set white balance. Auto white balance shifts unpredictably during dusk transitions, creating inconsistent color across clips that is extremely difficult to correct in post.
Frequently Asked Questions
How low can ambient light drop before the Neo's ActiveTrack completely fails?
In my testing, ActiveTrack maintained reliable lock down to approximately 3-5 lux on high-contrast subjects (a white vehicle against dark soil, for example). On low-contrast subjects like green machinery against crops, the practical floor was closer to 10-12 lux. Below these thresholds, manual stick flying with D-Log recording produced better results than attempting automated tracking.
Does D-Log recording affect the Neo's battery life or flight time?
D-Log itself does not impact battery performance measurably. The color profile is a processing pipeline choice, not an additional computational load. What does affect battery life in low-light field sessions is slower flight speeds (less aerodynamic efficiency at 3-6 m/s compared to 8-12 m/s) and lower altitudes where ground-effect turbulence forces the motors to work harder for stabilization. Expect roughly 8-12% reduced flight time during typical low-light tracking sessions compared to daytime high-altitude flights.
Can I use Hyperlapse mode and ActiveTrack simultaneously on the Neo?
Not directly. Hyperlapse and ActiveTrack are mutually exclusive flight modes on the Neo. The workaround I used during this project was Free mode Hyperlapse with manual waypoints set to follow the known path of the tracked subject (such as an irrigation pivot's arc). By pre-programming the Hyperlapse waypoints to mirror the subject's movement path, I achieved a result visually similar to tracked Hyperlapse without requiring simultaneous mode activation. This requires knowing your subject's trajectory in advance, which is feasible for predictable agricultural machinery.
Ready for your own Neo? Contact our team for expert consultation.