> 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/expert-center/es/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide/test-framework-checklist-to-videocameras-in-navixy.md).

# Lista de verificación del marco de pruebas para videocámaras en Navixy

Lista de verificación de pruebas de dashcam para Navixy que cubre la calidad de video, la precisión del GPS, la estabilidad de la transmisión, la compresión y las tasas de reconocimiento de IA.

| Calidad de video                   | Resolución                                 | Píxeles (p. ej., 1920×1080) | ≥ 640x360 como mínimo para registrar un evento              |
| ---------------------------------- | ------------------------------------------ | --------------------------- | ----------------------------------------------------------- |
| <p><br></p>                        | Sensibilidad de video                      | Alto / Medio / Bajo         | Reducir o aumentar la frecuencia de los eventos.            |
| Frecuencia de cuadros              | Transición de video                        | FPS                         | ≥ 10 FPS                                                    |
| Rango dinámico                     | Transición de claridad con poca luz        | Segundos                    | Al menos 1 s.                                               |
| Rendimiento de GPS                 | Precisión de ubicación                     | Metros                      | ≤ 15 m (cielo despejado)                                    |
| <p><br></p>                        | Estabilidad de la transmisión              | Segundos                    | ≤30 segundos                                                |
| Red y transmisión                  | Uso de datos a 720p                        | MB/hora                     | ≤ 300 MB/h                                                  |
| Calidad de compresión              | Datos del protocolo                        | H264 o H265                 | Al menos H264                                               |
| Reconocimiento de calidad de video | Reconocimiento de placas                   | Metros                      | Legibilidad en un rango de 0-30–80 km/h.                    |
| <p><br></p>                        | Reconocimiento facial/reconocimiento de ID | Metros                      | Alertas por reconocimiento de ID o conductor no reconocido. |
| <p><br></p>                        | Prueba de esfuerzo                         | Frecuencia                  | Eventos erróneos/minuto                                     |
| Rango de temperatura               | Temperatura de operación                   | °C                          | –20°C a +60°C                                               |
| Mantenimiento                      | Firmware OTA                               | Aprobado/Reprobado          | Aprobado                                                    |


---

# 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/expert-center/es/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide/test-framework-checklist-to-videocameras-in-navixy.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.