Technical Documentation

MRP-LD1 Drone LiDAR Datasheet, Manual and SDK

Download the Purpleriver dToF product brochure and review verified MRP-LD1 specifications, the English user manual, SDK package and integration resources.

Browse documentation View LiDAR module

MRP-LD1 Drone LiDAR datasheet, user manual and SDK resources

Documentation overview

Start with the file that matches your evaluation stage.

Download the public Purpleriver dToF product brochure for an immediate product-fit review. Use the English user manual for hardware and protocol details, then request the SDK package when the team is ready for host-side evaluation. The manual and SDK remain request-based so the controlled package can be matched to the module, interface and project context.

Compare the three resources

8 gModule weight

1.2 WTypical power

60° × 45°Field of view

40 × 30 · 10 fpsDepth output

Technical file library

Download the brochure. Request deeper engineering files when needed.

The public PDF is available immediately without an inquiry. The user manual and SDK use separate request flows so each controlled package stays connected to the relevant host, interface and evaluation stage.

01Public product brochure

Purpleriver dToF Product Brochure

A two-page public PDF for the Purpleriver dToF area-array module, covering application paths, the documented operating envelope and a point-cloud visualization example.

PDF2 pages237 KBDirect download

Robot navigation, UAV obstacle avoidance, AR/VR and industrial inspection applications.
dToF and SPAD sensing with a 940 nm VCSEL and Class 1 laser designation.
Range, accuracy, field of view, resolution, frame rate and ambient-light specifications.
UART, UVC and UDP interfaces plus software, power, temperature and weight information.

Download product brochure Open PDF

PDF dToF Area Array Module Product applications Verified specifications Point-cloud visualization

2pages

Controlled engineering files

Continue with the manual or SDK.

Choose one resource at a time. After a successful inquiry, only the file connected to that card appears in its confirmation panel.

02User manual

MRP-LD1 User Manual EN

English product and protocol reference for engineers preparing MRP-LD1 setup, communication and host-side evaluation.

DOCXEnglishControlled access

Hardware interface definitions
Serial communication protocol
UDP and UVC data-format references
Configuration and integration guidance

Request user manual

03Development package

Mini dToF SDK Package

Evaluation package for application development, data review and embedded integration planning with the MRP-LD1 module.

ZIPEvaluationControlled access

SDK evaluation resources
Host-side development material
Interface-planning references
Windows, ARM, Linux and Android context

Request SDK package

Access process: the product brochure downloads immediately. For the user manual or SDK, choose one card, submit the technical inquiry, then use the download button shown in that resource's confirmation panel.

Documented interfaces

Choose UART, UVC or UDP around the host workflow.

The interface decision should follow the host, data path and validation task. Confirm the exact product variant, protocol and SDK package before electrical or software integration.

UART

Embedded serial path

Plan baud rate, message framing, units, update timing and error recovery with the selected host controller.

UVC

Depth-image workflow

Evaluate host enumeration and image-style transport for depth, point-cloud or combined data workflows.

UDP

Network data path

Review addressing, packet handling, timestamps, data loss and replay behavior for networked evaluation.

Evaluation workflow

Use documentation to reduce integration uncertainty.

The files support engineering evaluation; final system behavior still needs validation on the selected host, aircraft or embedded platform.

Define the sensing task

Share the platform, scene, target distance, mounting direction and expected depth or point-cloud output.

Select the host path

Identify the processor, operating system and preferred UART, UVC or UDP communication path.

Use the right file

Download the public product brochure immediately, or request the manual and SDK package when deeper engineering detail is needed.

Validate before design-in

Test range, ambient light, data handling and system behavior under representative operating conditions.

Application-specific support

Need a controlled file or interface review?

Send the module variant, host, operating system, preferred interface, application scene and project stage so the technical team can match the available documentation to the request.

Discuss documentation needs

Related evaluation paths

Connect documents to product facts and representative data.

SpecificationsReview the approved MRP-LD1 product facts and operating boundaries.View product Sample dataRequest depth and point-cloud material matched to the intended scene.Request data Technical supportShare the host, interface, system and project timeline before requesting controlled files.Contact Purpleriver

Documentation FAQ

FAQ

Choose a file by evaluation stage and include enough host context to match the appropriate package.

Ask a technical question

Which Purpleriver dToF document should I use first?

Download the public product brochure for the initial product-fit review. Request the English user manual for hardware and protocol details, then request the SDK package when preparing host-side development or data evaluation.

Can I download the product brochure without submitting an inquiry?

Yes. The Purpleriver dToF Product Brochure is a direct public PDF download. The English user manual and SDK package remain request-based engineering resources.

Which host information should I provide?

Share the processor or computer, operating system, preferred UART, UVC or UDP path, expected data output and the application workflow your team plans to validate.

Can I request both the user manual and SDK?

Yes. Submit each controlled-resource card separately. The confirmation panel unlocks only the resource associated with that request, keeping the manual and SDK access states independent.