> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/6x-series-sensors-user-guide/incident-light-sensor-and-gps/operation/how-to-use.md).
# How to Use
6X Series Sensors - Incident Light Sensor/External GPS How To Use Instructions
## Before Starting
### Reflectance Panel
If a reflectance panel is also being used see the page linked below:
{% content-ref url="/pages/jtCrdJGsEP4hMiAm6xNs" %}
[How To Use](/home/6x-series-sensors-user-guide/reflectance-panel/how-to-use.md)
{% endcontent-ref %}
***
## Install Light Sensor/GPS
1. Install the light sensor and gimbal onto the aircraft.
2. Connect the USB-C cable to the light sensor.
3. Secure the cable to the aircraft.
4. Connect the USB-C cable to the port on the gimbal.
For Gimballed Sensors
Connect the light sensor/GPS to the USB-C port on the gimbal
For Non-Gimballed Sensors
Connect the light sensor/GPS to the USB-C port on the 6X
## Power on Aircraft & Verify Status LEDs
1. Power on the aircraft. This will also power the gimbal, sensor, and light sensor on.
2. Verify the Status LEDs shown below have all turned solid green.
## Fly
The sensor and light sensor are now ready for flight.
---
# 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://support.senterasensors.com/home/6x-series-sensors-user-guide/incident-light-sensor-and-gps/operation/how-to-use.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.
