An eye that follows.
Use a suitable smart camera and vision-processing software to detect the test target and maintain its identity. A pan/tilt mount keeps it in view while recording the camera’s measured orientation.
Acquire. Launch. Approach. Pass.
A concept for a GPS-referenced smart camera, an orientable launchpad, and a DIY racing-style drone. Visualize camera acquisition, pad rotation, a stylized direct pad release, and a rapid, scripted approach and pass around a cooperative target. The animated flight remains non-contact.
Ready. Acquire phase. Fast approach and non-contact pass. Playback speed 2 times.
Build a controlled research demonstrator that connects visual tracking, a location estimate with explicit uncertainty, and an operator-approved launch sequence. The target is known and cooperative throughout the experiment.
Use a suitable smart camera and vision-processing software to detect the test target and maintain its identity. A pan/tilt mount keeps it in view while recording the camera’s measured orientation.
Combine the camera’s GNSS reference, calibrated viewing direction, and validated range evidence. Report a region of uncertainty and data age; retain bearing-only status when range is unknown.
Use the pad’s independent GNSS and measured orientation to register it in the same scene. Demonstrate pad rotation, then a scripted direct-release animation along a separate corridor. The inclined pad is a visual mockup.
Can the vision system maintain a trustworthy observation at the intended test distance? Reliable tracking and depth must be measured before any launch sequence is connected to hardware.
The camera and pad each need a position reference and a measured orientation. GNSS provides position; camera calibration, mount feedback, and pose sensing provide the viewing and pad directions.
Smart camera, detection model, persistent track ID, pan/tilt feedback, and an external GNSS reference. Confirm the chosen camera’s sensors and host requirements.
Associate the observations in one coordinate frame. Keep bearing-only and range-supported estimates distinct. Display uncertainty, track continuity, and stale-data warnings.
Register the pad independently. Show rotation toward an operator-selected, pre-cleared corridor on a bench mockup, followed by a scripted direct-release animation. Launcher engineering is outside this visual prototype.
A DIY racing-style airframe with GNSS and a flight stack suitable for stabilized navigation. Fly a separated test route under pilot supervision and record flight telemetry.
Shared foundation: time synchronization · calibration records · consistent position and height references · operator supervision · event logs
A target can appear at the same image location at many different distances. Camera GPS plus a pixel observation cannot uniquely determine the target’s 3D position.
Progress from recorded observations to a ground mockup, then to supervised flight. Each stage must produce reproducible evidence before the next begins.
Agree the cooperative target, observation conditions, flight boundaries, and reporting format. Review this animated sequence with the test team.
Capture representative footage. Evaluate target identity, pan/tilt tracking, pose records, and range availability against a known reference.
Display camera and pad references together. Use a non-flying pad mockup to demonstrate orientation, readiness feedback, and held-launch scenarios.
Demonstrate a separate observation flight with pilot supervision. Review the direct pad release as a separate animation study. Compare logs with reference data and produce a feasibility report.
The prototype should preserve the origin, time, and validity of each observation. These records support test review and uncertainty assessment; they are not aircraft navigation commands.
Image timestamp, persistent track identity, image observation, detection score, measured camera pose, and calibration reference.
Track continuity against labelled footage. Distinguish missed detections, occlusions, and identity switches.
Camera position reference, range provenance, reference timestamp, and an explicit indication of unavailable or invalid measurements.
Compare reported observations with an independent cooperative reference. Report range availability and uncertainty separately.
Pad position reference, measured orientation, parked / moving / aligned status, and the operator-selected corridor identifier.
Show requested and measured orientation as separate states. A visual alignment animation is not hardware position feedback.
Pilot approval event, flight state, telemetry timestamp, and the recorded observation-flight sequence and the separate pad-release storyboard.
Review the log and video together. Confirm the hold scenarios prevent departure and the flight remains in its cleared corridor.
Distinguish image detection, bearing-only tracking, a range-supported estimate, and an invalid or stale record. Never convert detection confidence into a claim of position accuracy.
Exercise absent range, track loss, delayed pose, stale timestamps, and missing operator approval before flight. Agree measurable acceptance criteria and test conditions in advance.
Record the evidence needed to assess perception and launch coordination. Set pass/fail criteria before testing, then assess track continuity, range availability, error against the cooperative reference, observation age, and correct hold-state behaviour.
Camera, processing software, and interface selection will be confirmed against prototype requirements.