> 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/id/guide/devices-and-settings/device-specific-controls/other/virtual-ignition.md).

# Pengapian virtual

Gunakan tegangan di perangkat atau gerakan sebagai sumber pengapian ketika perangkat GPS tidak memiliki kabel pengapian. Atur ambang tegangan atau pengaturan waktu gerakan di Navixy.

Memungkinkan perangkat menentukan status pengapian berdasarkan tegangan onboard atau gerakan saat kabel pengapian tidak tersambung.

## Pengaturan

* **Mode**: menentukan status pengapian berdasarkan tegangan onboard atau sensor gerak.
* **Tegangan saat pengapian aktif**: tegangan di atas nilai ini pengapian dihitung sebagai aktif, dalam mode tegangan.
* **Durasi diam hingga mati**: berapa lama tanpa gerakan sebelum pengapian dihitung sebagai mati, dalam mode gerakan.
* **Durasi gerak hingga aktif**: berapa lama gerakan harus berlangsung sebelum pengapian dihitung sebagai aktif, dalam mode gerakan.

## Ketersediaan

Muncul pada model perangkat yang mendukung Pengapian virtual.

## Lihat juga

* [Sumber pengapian](/docs/user/id/guide/devices-and-settings/location-and-movement/ignition-source.md): blok utama untuk memilih mode deteksi pengapian.


---

# 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/id/guide/devices-and-settings/device-specific-controls/other/virtual-ignition.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.