> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-lx1/safety-and-specifications/technical-specifications.md).

# Technical Specifications

Compatible with supported iOS and Android devices

### Measurement Technology

* Motion-based inertial measurement (primary)
* Integrated Class 2 laser module (supports widths, openings, and ceiling heights)

### Laser

* Class 2 visible-red
* Wavelength: **610–690 nm**
* Maximum output power: **< 1 mW**

### Power & Battery

* Battery life: approximately **10 hours** of typical use
* Charging port: **USB-C**
* Recommended input: **5 V USB (standard charging)**
* Avoid high-voltage fast chargers

### Environmental

* Operating temperature: **0°C to 40°C**
* Short-term storage temperature: **–20°C to 45°C**
* Long-term storage temperature: **–20°C to +35°C**
* Humidity: **≤ 80% (non-condensing)**
* Maximum altitude: **2000 m**
* Designed primarily for indoor use. When measuring an external building footprint, keep Moasure LX1 protected from the weather. Do not expose it to rain or snow, or submerge it in water.

### Connectivity

* Bluetooth Low Energy (BLE)
* Requires Moasure mobile application
* Compatible with supported iOS and Android devices

### Physical

* Dimensions: 178 × 75 × 37 mm (**7.0 × 3.0 × 1.5 in**)
* Weight: 230 g (**8.1 oz**)
* Material: Impact-resistant composite housing

Specifications will be updated as final engineering data becomes available.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.moasure.com/en/moasure-lx1/safety-and-specifications/technical-specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.