Coverage gaps and difficult targets
Map the 60° × 45° sensing sector onto the airframe. Test narrow, dark, angled and reflective targets instead of assuming one favorable wall represents the mission.
Drone Obstacle Avoidance
Help Your Drone Avoid Obstacles with Compact dToF LiDAR
MRP-LD1 gives UAV teams compact 3D depth input for forward, downward or task-specific drone obstacle avoidance. At 8 g and 1.2 W typical power, it supports payload-limited prototypes while the host processor and flight controller remain responsible for decisions and motion.
8 gmodule weight
1.2 Wtypical power
60° × 45°field of view
0.2–8 moutdoor baseline
Real-flight constraints
Plan drone obstacle avoidance around the complete response chain.
A sensing module provides evidence about the scene. Reliable behavior still depends on coverage, target conditions, host interpretation and a flight-control response proven on the intended UAV.
Sunlight and scene variation
Use the documented 0.2–8 m outdoor range and 80 Klux ambient baseline as test inputs. Validate the real sunlight direction, background and target material.
Latency and response margin
Combine 10 fps sensor output with host, perception and flight-control delay. Vehicle speed must stay inside the response distance demonstrated by the complete system.
MRP-LD1 suppliesDepth images and 3D point-cloud data.The UAV stack suppliesDetection logic, planning, flight control and safe fallback behavior.
MRP-LD1 module fit
Compact depth input for payload-limited UAVs.
Evaluate MRP-LD1 as a compact UAV obstacle avoidance dToF module—not as a complete collision-avoidance system. Use the verified product facts to screen payload, coverage, data and host fit before mounted testing.
Indoor range0.5–25 m
Outdoor range0.2–8 m
FOV60° × 45°
Depth output40 × 30
Frame rate10 fps
Weight / power8 g / 1.2 W
InterfacesUART · UVC · UDP
SoftwareWin · ARM · Linux · Android
Application direction
Use a defined sensing sector for the mission.
MRP-LD1 can provide depth input for a selected direction. It does not turn one mounting position into automatic 360-degree drone collision avoidance.
Forward obstacle sensing
Place the sensing sector around the expected flight direction, then test closing speed, brake margin, thin targets and remaining blind areas.
Downward and landing support
Evaluate altitude and landing-zone input across concrete, vegetation, slopes and surface transitions. Airframe attitude and mounting angle remain part of the test.
Rear or multi-direction planning
Add separately oriented sensing only where the mission requires it. Document overlap, airframe occlusion and sectors that remain uncovered.
Evaluation path
Move from requirements to controlled flight evidence.
Keep the evaluation short and measurable. Each step should answer a decision before the team commits to the next build stage.
Define the task
Share the UAV, sensing direction, target set, distance, lighting, speed, payload and host constraints.
Review sample and data
Confirm the product facts, manual, SDK path and representative depth or point-cloud evidence.
Validate the mounted system
Measure alignment, occlusion, vibration, timing and invalid-data behavior on the intended airframe.
Run controlled flight tests
Start conservatively, record each handoff and widen the operating envelope only after repeatable evidence.
Engineering and supply support
Connect product evidence with the next project decision.
Founded in 2015, Purpleriver develops solid-state dToF technologies and supports B2B teams with product specifications, integration material, sample data and project-specific discussion.
SPAD + VCSELdToF platform4 environmentsWindows · ARM · Linux · AndroidEvaluation pathSample · SDK · data · quote
Focused engineering guides
Use the deeper guide only when the decision requires it.
The landing page stays focused on product fit and conversion. These guides carry the detailed information about system behavior, distance and outdoor testing.
How drones navigate and avoid obstacles
Understand the sensing, interpretation, planning and control layers behind an avoidance response.
Read engineering guide ›Distance and brake margin
Connect detection distance, aircraft speed and measured system latency before flight.
Read engineering guide ›Sunlight and target reflectivity
Build a repeatable outdoor test around light direction, material, angle and dropout.
Read engineering guide ›Product support
FAQ
Confirm the product boundary, coverage, timing and test conditions before requesting hardware.
Read the complete dToF LiDAR FAQCan MRP-LD1 make a drone avoid obstacles by itself?
No. MRP-LD1 supplies depth information. A host processor, perception logic, decision layer and flight controller must interpret that data and command the aircraft.
What range should an outdoor UAV test use?
Start from the documented 0.2–8 m outdoor baseline and validate the actual target reflectivity, sunlight, mounting and motion conditions. Do not combine it with the separate 0.5–25 m indoor range.
Does one module provide 360-degree obstacle avoidance?
No. The listed field of view is 60° horizontal by 45° vertical. Multi-direction coverage requires mounting and sensor-layout planning.
Is 10 fps enough for my drone?
That depends on speed, closing distance, host latency, control latency and braking dynamics. Calculate and test the complete system margin.
How should sunlight and difficult targets be tested?
Test the real target size, material, angle and background under representative light direction. Record missed or unstable frames and define the host response rather than assuming one universal result.
Which host interfaces are available?
The verified interfaces are UART, UVC and UDP, with software support listed for Windows, ARM, Linux and Android.
What should we send before requesting a sample?
Share the platform, sensing direction, target materials, operating environment, distance, speed, host, preferred interface, expected quantity and project timing.
Evaluation request
Share the UAV task before choosing a sample.
Send the platform, sensing direction, target distance, environment, host, quantity and project timing. These details help match the product, documentation, sample data and next technical discussion.
- Platform and payload limit
- Forward, downward or other sensing direction
- Target material, distance and lighting
- Host, interface, quantity and schedule
Request obstacle-sensing evaluation
Name, email and purchase quantity are required. Requirements are optional but help prepare a relevant response.