> 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/vehicle-sensors/discrete-sensors.md).

# Sensores discretos

Agregue sensores discretos a dispositivos GPS en Navixy: configure la etiqueta, el tipo y el número de entrada del dispositivo para el monitoreo del estado binario.

Los sensores digitales reportan estados de encendido/apagado (binarios) desde una entrada del dispositivo, como Ignición, puertas, Botón de pánico, motor, alarma, carga o manipulación/desconexión.

## Disponibilidad

Disponible cuando el modelo del dispositivo tiene entradas digitales.

## Agregar un sensor digital

Para agregar un sensor digital, haga clic en ![Discrete sensor](https://www.navixy.com/wp-content/uploads/2019/06/plus.jpg) y seleccione **Sensor digital** en el menú emergente:

Configure los parámetros requeridos del sensor:

* **Etiqueta del sensor:** Ingrese el nombre del sensor en el sistema. Puede elegir el nombre que desee.
* **Tipo de sensor**: Elija el tipo de sensor.
* **Entrada**: Ingrese el número de la entrada del terminal a la que está conectando el sensor.

Para confirmar los cambios, haga clic en **Guardar**.

Puede conectar sensores digitales y botones de los siguientes tipos:

1. Ignición
2. Botón de pánico
3. Alimentación externa
4. Estado del motor
5. Alarma del vehículo
6. Puertas
7. Personalizado


---

# 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/vehicle-sensors/discrete-sensors.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.