> 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.md). # Device-related questions - [How to troubleshoot Jimi JC400 video streaming and playback](https://navixy.com/docs/qna/device-related-questions/how-to-troubleshoot-jimi-jc400-video-streaming-and-playback.md): Fix JC400 video streaming: verify IMEI, SIM connectivity, firmware version, APN settings, and server configuration. Includes manual command setup for EU and US - [Configuring sensors on Teltonika trackers](https://navixy.com/docs/qna/device-related-questions/configuring-sensors-on-teltonika-trackers.md): Add measurement sensors to Teltonika devices using the configurator tool, parameter settings, and AVL IO mapping. Covers FMB920 sensor setup in Navixy - [HVIDEO vs EVIDEO commands](https://navixy.com/docs/qna/device-related-questions/hvideo-vs-evideo-commands.md): Choose video retrieval source: HVIDEO pulls lower-quality sub-stream footage faster, while EVIDEO extracts higher-quality SD card video with more data usage - [Camera light indicators (JC261)](https://navixy.com/docs/qna/device-related-questions/camera-light-indicators-jc261.md): Diagnose JC261 LED status: red indicates power, green shows GPS lock, and blinking blue signals missing cellular connectivity. Verify APN configuration - [MC40-02 Howen event sensitivity](https://navixy.com/docs/qna/device-related-questions/mc40-02-howen-event-sensitivity.md): Adjust MC40-02 event sensitivity in Howen iTools (L/M/H), not Navixy. Configure DMS or ADAS events, trigger hold, interval, and buzzer settings - [Howen Device ID Configuration - Navixy Activation](https://navixy.com/docs/qna/device-related-questions/howen-device-id-configuration-navixy-activation.md): Configure Device ID in Howen iTools via System > Terminal, then verify it matches the activation ID requested in Navixy. Not related to IMEI or S/N - [GSENSOR calibration failure on JC261](https://navixy.com/docs/qna/device-related-questions/gsensor-calibration-failure-on-jc261.md): The GCALIBRAT command is unsupported on JC261. Firmware v1.8.1.3+ performs automatic sensor calibration on power-on to reduce false events - [No livestreaming video on the platform (JC261)](https://navixy.com/docs/qna/device-related-questions/no-livestreaming-video-on-the-platform-jc261.md): Verify RSERVICE is set to rtmp.x-gpsmail.com:1935/encoder and SIM has active data plan with stable connectivity. Check signal strength - [JC261(P/D) Input Mapping](https://navixy.com/docs/qna/device-related-questions/jc261-p-d-input-mapping.md): 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 - [FMC150 (QJIBO/QKIBO) Input and Output Capabilities](https://navixy.com/docs/qna/device-related-questions/fmc150-qjibo-qkibo-input-and-output-capabilities.md): Compare FMC150-QJIB0 (3 digital inputs, 2 outputs) and FMC150-QKIB0 (2 digital inputs, 3 outputs) specifications and select during device activation - [Slight difference between GPS CAN mileage and physical odometer](https://navixy.com/docs/qna/device-related-questions/slight-difference-between-gps-can-mileage-and-physical-odometer.md): Vehicle control modules report mileage asynchronously; CAN data is more precise than dashboard odometer readings. Small differences are normal and expected - [Coban Devices SMS and GPRS differences](https://navixy.com/docs/qna/device-related-questions/coban-devices-sms-and-gprs-differences.md) - [How to Control and Read Digital Inputs/Outputs on Starlink Devices](https://navixy.com/docs/qna/device-related-questions/how-to-control-and-read-digital-inputs-outputs-on-starlink-devices.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/qna/device-related-questions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.