> 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/laser-classification-and-warnings.md).

# Laser Classification & Warnings

LX1 contains an integrated **Class 2 visible-red laser**, compliant with IEC 60825-1:2014.

### Laser Specifications

* Classification: **Class 2**
* Wavelength: **610–690 nm**
* Maximum output power: **< 1 mW**
* The laser beam is emitted only during specific measurement actions

### Warning

* Do not stare directly into the laser beam
* Do not aim the device at people or reflective surfaces
* Avoid operating LX1 in environments where unintended laser exposure could occur
* Use LX1 only as instructed to prevent accidental exposure

As required by IEC 60825-1:2014 clause 8.2(a):

{% hint style="info" %}
Users must not stare into the beam or operate in a manner where they or others’ eyes are exposed to the laser during operation of the product.
{% endhint %}

If the device shows any irregular laser behaviour, discontinue use and contact Moasure support.


---

# 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/laser-classification-and-warnings.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.