> 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/id/vehicle-telematics-technology/video-telematics/video-telematics-101.md).

# Dasar-dasar telematika video

Panduan teknis tentang perangkat keras dashcam, pemilihan codec, dan pembandingan kualitas video untuk mengevaluasi dan menerapkan sistem kamera armada.

Bagian ini membahas dasar teknis perangkat keras dashcam, mulai dari prosesor dan codec di dalam perangkat hingga metode terstruktur untuk membandingkan kualitas video pada kondisi armada nyata.

## Daftar isi

* [Di dalam dashcam: apa yang sebenarnya menggerakkan telematika video](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/video-telematics-101/inside-the-dashcam-what-really-powers-video-telematics.md): Bagaimana arsitektur SoC menentukan kemampuan AI, kompresi, dan dukungan fitur di berbagai chip kelas ekonomis dan premium.
* [H.264 vs H.265 dalam telematika armada: memecahkan teka-teki codec](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/video-telematics-101/h.264-vs-h.265-in-fleet-telematics-cracking-the-codec-puzzle.md): Membandingkan efisiensi kompresi, beban termal, dan biaya lisensi untuk memandu keputusan penerapan dashcam.
* [Apa yang membuat video dashcam andal untuk armada? Panduan benchmarking](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/video-telematics-101/what-makes-dash-cam-video-reliable-for-fleets-a-benchmarking-guide.md): Mengevaluasi sensitivitas pemantauan supir, kinerja HDR, dan penanganan cahaya redup dalam kondisi armada nyata.


---

# 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/id/vehicle-telematics-technology/video-telematics/video-telematics-101.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.