> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/payloads/flux-lidar/safety-and-legal.md).
# Safety and Legal
This section contains important information about safety and legal notices while using any of Flux sensor. Please read them carefully before operating any of the sensors. Contact Freefly in case of any doubts.
Flux H1 features a Hesai XT32M2X sensor that has been evaluated to be **Class 1 laser product** per **60825-1:2104 (Ed. 3)** and operates in the 905 nm band.
Flux O1 features an Ouster OS1 sensor that has been evaluated to be **Class 1 laser products** per **60825-1: 2014 (Ed. 3)** and operates in the 865nm band.
Flux L1 features a Livox Avia sensor that has been evaluated to be **Class 1 laser product** per **60825-1:2104 (Ed. 3)**and operates in the 905 nm band.
## Laser Radiation
Class 1 Laser Product
The XT32M2X, Ouster OS1, and Livox Avia sensors featured in Flux emit Class 1 invisible laser radiation.
The entire window is considered to be the laser aperture. While Class 1 lasers are considered "eye safe", avoid prolonged direct viewing of the laser and do not use optical instruments to view the laser.
This product does not have a power switch. It starts operating once connected to power. During operation, the entire cover lens can be regarded as the product's laser emitting window; looking at the cover lens can be regarded as looking into the transmitting laser.
{% hint style="danger" %}
Use of controls, or adjustments, or performance of procedures other than those specified herein may result in hazardous radiation exposure.
{% endhint %}
## Hot Surfaces
Hot Surfaces
{% hint style="danger" %}
Flux can get **very hot** - use caution when handling Flux or removing it from the payload connector
{% endhint %}
When operated in an ambient temperature > 40 °C, the metallic surfaces of the sensor may be hot enough to potentially cause skin burn. Avoid skin contact with the sensor’s base, lid and the heatsink when the sensor is operated under these conditions. The sensor should not be used in an ambient temperature above 50°C. The maximum safety certified ambient operating temperature is 50°C.
## Installation and Operation
Before powering on the product, make sure the electrical interfaces are dry and clean. Do **NOT** power on Flux with wet connectors on the Smart Dovetail or GNSS modules
{% hint style="danger" %}
Do not "hotswap" (remove or insert) Flux from the Smart Dovetail connector when the aircraft is powered on. Doing so may damage the aircraft and/or Flux
{% endhint %}
## LiDAR Cover Lens
Do not touch the plastic or glass covering over the LiDAR sensor. Fingerprints or other contaminates such as grease or dirt can cause issues with the point cloud collection on Flux. The LiDAR cover can be gently wiped down as needed with the included microfiber cloth. Avoid scratching the glass or plastic lens covering.
---
# 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.freeflysystems.com/ecosystem/payloads/flux-lidar/safety-and-legal.md?ask=&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.
