> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book.md).
# Low Cost Tracker Full Device Guide Book
Introduction to the Low-Cost Tracker (LCT) User Guide
LCT introduction Device Book
This guide provides a comprehensive overview of the **Low-Cost Tracker (LCT)** device, detailing its functionalities, configurations, and diverse applications. It serves as a complete resource for understanding both the **platform-integrated features** and the **hardware specifications** of the LCT. The guide is structured into the following key areas:
* **Device Capabilities**: Covers geolocation, motion tracking, tamper detection, and other advanced features.
* **Configuration Settings**: Explains adaptive rules, alarm management, and measurement parameters for optimal device operation.
* **Shipping and Handling**: Provides specifications for safely shipping the LCT as a tracking device for logistics.
* **Platform Integration**: Guides you through seamless device setup and management within the IoT platform.
Whether used for **monitoring assets**, **optimizing operations**, or **ensuring security**, this guide equips you with the tools and knowledge to unlock the full potential of the LCT device.
---
# 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://docs.g-iot.io/low-cost-tracker-full-device-guide-book.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.
