> For the complete documentation index, see [llms.txt](https://erdilrf.gitbook.io/erdilrf-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://erdilrf.gitbook.io/erdilrf-docs/erdilrf-0.1.1-scope-and-source.md).

# ErdiLRF 0.1.1: Scope and source

Start with the published source, select the exact model, then run the generated-byte check.

This guide describes **ErdiLRF 0.1.1**, an Arduino C++ library for the ERDI 905 nm LR, LRF-A1, SPD1200, LRF-H and LRF-VB model definitions included in that release. It is a software reference, not a declaration that every model, board or interface has been tested.

**Manufacturer disclosure:** Prepared by the ERDILRF technical resource team at ERDI TECH LTD. The examples use generated bytes, with no sensor, target or physical UART connected.

## Use a versioned source

Install the published 0.1.1 package rather than assuming that a repository's current default branch or latest release is identical.

* [Official Arduino 0.1.1 source archive](https://downloads.arduino.cc/libraries/github.com/yu911517778-a11y/ErdiLRF-0.1.1.zip)
* [Upstream source repository](https://github.com/ErdiTech/ErdiLRF)
* [PlatformIO Registry entry](https://registry.platformio.org/libraries/erdi-tech/ErdiLRF)

The archive used to check this guide is 16,279 bytes with SHA-256:

```
55aa84905539e45f48832eac00a90f52abca9b615677045a88bd5bd40a5d554c
```

Its `library.properties` reports `name=ErdiLRF`, `version=0.1.1`, `license=MIT`. The examples on these pages use its unchanged `src/ErdiLRF.h` and `src/ErdiLRF.cpp`.

## Keep source states separate

The published archive, repository default branch, release tags and any local working copy are separate artifacts. A local fix, build or test is not evidence that the change has been pushed, tagged or distributed through a package registry. These pages do not rely on the separate local maintenance changes prepared after the public package.

## Read in this order

1. Install the library and select the exact model definition.
2. Run the generated-byte check on a computer.
3. Handle status codes and known source limits before attempting a real integration.

A successful software check does not establish physical range, accuracy, electrical compatibility, laser safety classification or live ROS 2, PX4 or ArduPilot operation.