> 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/using-navixy/my-jimi-jc-tracker-is-configured-but-i-cant-see-video-playback.md). # My Jimi JC tracker is configured but I can't see video playback Send three SMS commands to the Jimi JC tracker to enable video uploads, retrieve the list of stored recordings, and trigger the upload ## Question Why can't I see video playback from my Jimi JC tracker? ## Answer If your JC-series tracker (like the JC261) is connected but you're not seeing any video playback, it's likely because the device hasn't been told to upload recorded videos yet. No worries — this is easy to fix. To make videos visible on the platform, just send these three commands to your tracker (in this exact order) via SMS or AirConsole: * `COREKITSW,0#` Enables video uploads to the platform. * `FILELIST,http://{server}:7514/filelist` Lets the device send a list of videos stored on the SD card. These show up in gray on the calendar and timeline. * `UPLOAD,http://{server}/upload` Tells the tracker to actually upload selected videos. These will appear in blue and stay available for 30 days. Replace {server} with the IP address of your platform: * US: 13.52.37.2 * EU: 52.57.1.136 Don't forget to add your device's IMEI number. **Example:** For a tracker with IMEI 88887777 connected to the US server, the commands would be: ``` COREKITSW,0# FILELIST,http://13.52.37.2:7514/filelist/88887777 UPLOAD,http://13.52.37.2/upload/88887777 ``` Make sure your tracker is online to receive these commands over GPRS. If it's offline, SMS will work too as long as the SIM supports it. ## Links * [Air Console](/docs/admin/devices/air-console.md) * [Jimi IoT dashcam configuration](/docs/expert-center/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-iot-dashcam-configuration.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 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/using-navixy/my-jimi-jc-tracker-is-configured-but-i-cant-see-video-playback.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.