> 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/qna/device-related-questions/jc261-p-d-input-mapping.md).
# JC261(P/D) Input Mapping
JC261 maps 3 logical inputs in Navixy: Input 1 is SOS button (event only), Input 2 is ignition, Input 3 is input voltage. Device has 2 physical inputs
**Question:** Why does the JC261(P/D) display 3 inputs in Navixy if the device physically only has 2 inputs?
**Answer:**\
The three inputs displayed in Navixy are related to how the camera internally interprets and reports its input signals. Although the device physically provides only two external inputs, the camera also treats the SOS button as an additional logical input.
As a result, the input mapping is represented as follows:
* **Input 1:** SOS button
* **Input 2:** Ignition
* **Input 3:** Input voltage
However, Input 1 will not display an “active” status when the SOS button is pressed. This is because the input is intended only for event detection purposes and not for monitoring a closed/open electrical circuit state.
Links: [Event Configuration on JC events](https://navixy.com/docs/expert-center/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series)
---
# 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/qna/device-related-questions/jc261-p-d-input-mapping.md?ask=&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.