> 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/raw-data/determining-why-a-tracker-stopped-transmitting.md).

# Determining why a tracker stopped transmitting

Export 30 days of raw data to review battery voltage and signal strength trends in the period before a device stopped transmitting

## Question

How can I determine why my GPS tracker stopped transmitting data?

## Answer

Exporting raw data helps diagnose why a device has lost connection. To troubleshoot:

1. Export raw data for the last 30 days.
2. Check parameters related to **signal strength, power levels, and device status**.
3. Pay attention to:
   * Latest **battery level** readings (both internal and external batteries, if available).
   * **Signal strength** data (GSM, GPS).
   * Any disconnection events recorded.

If the last recorded messages before disconnection show low battery or poor signal strength, this may be the cause of the issue.


---

# 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/raw-data/determining-why-a-tracker-stopped-transmitting.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.