> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/accelerometer.md).

# Acelerómetro

Configure los umbrales de fuerza de impacto en el dispositivo para que detecte y reporte colisiones a Navixy. Algunos modelos admiten niveles de impacto débil y fuerte por separado.

Reportes de un impacto cuando el dispositivo detecta una fuerza por encima de un umbral configurado durante una duración configurada.

## Configuración

Algunos modelos exponen un solo umbral; otros proporcionan separados **Impacto débil** y **Impacto fuerte** umbrales.

* **Fuerza** (débil / fuerte): la fuerza mínima de impacto necesaria para registrar un evento. En los modelos con dos niveles, el umbral débil activa un evento de baja prioridad y el umbral fuerte activa un evento de alta prioridad.
* **Duración**: cuánto tiempo debe mantenerse la fuerza para registrar un impacto. Los golpes aislados más cortos que este valor se ignoran.

{% hint style="info" %}
Ambos valores son mínimos para la detección. Un valor más bajo vuelve al sensor más sensible.
{% endhint %}

## Disponibilidad

Aparece en modelos de dispositivos con un Acelerómetro de impacto configurable.


---

# 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://navixy.com/docs/user/es/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/accelerometer.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.