> 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/safety-warnings-and-improper-use.md). # Safety Warnings & Improper Use To ensure safe operation and maintain device protection, always follow the guidance below: * If LX1 is used in a manner not specified by Moasure, protection may be impaired * Do not use LX1 if the device shows signs of damage, overheating, swelling, cracking, or unexpected behaviour * If LX1 is dropped or exposed to liquids, discontinue use and contact Moasure or your authorised distributor * Do not open, disassemble, modify, or attempt to repair the device * Only use accessories and charging cables approved or supplied by Moasure * Keep LX1 out of reach of children * Avoid exposing the device, battery, or laser components to extreme temperatures * Do not operate LX1 while running, climbing, or in unstable environments where loss of balance may occur * Ensure the device is placed on a stable, flat surface during use Failure to follow these instructions may result in device damage or reduced operator safety. --- # 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/safety-warnings-and-improper-use.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.