> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/accessories/gport/troubleshooting.md).
# Troubleshooting
### Status LED Indicator
STATE
LED STATUS
DESCRIPTION
01
Red Blink
Video Transmission Error
02
Red Solid
System Error (Camera, Gimbal, SOM)
03
White Blink
Camera Not Found
04
White Solid
05
Yellow Blink
06
Green Blink
System Ready
07
Green Solid
08
Purple Blink
09
Purple Solid
10
Pink Blink
Gimbal Not Found
11
Pink Solid
### Display Real-time Data
| **STATE** | **SYSTEM STATUS** | **DESCRIPTION** |
| --------- | ----------------- | ---------------------------------- |
| 01 | READY | Ready to flight |
| 02 | ERROR | System Error (Camera, Gimbal, SOM) |
| 03 | CAM ERROR | Camera Not Found |
| 04 | GMB ERROR | Gimbal Not Found |
| 05 | SOM ERROR | Video Transmission Error |
| **PROBLEM** | **POSSIBLE CAUSES** | **SOLUTION** |
| ------------------------ | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| System Error | Camera, Gimbal, gPort are damaged | Check each component. |
| Camera Not Found | Connection is loose |
Check the connection.
Check MAVLINK setting for FLIR is set.
|
| Gimbal Not Found | Gimbal Error | Open gTune to check the operation of the gimbal. |
| Video Transmission error | Connection is loose or gPort is damaged. |
Reboot GPORT system by using DJI PILOT APP.
Waiting for the video stream (Approx: 50 seconds)
|
### No Video Stream
**->Reboot system**: After checking the setting and connection, please reboot the system and wait a second.
---
# 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.gremsy.com/accessories/gport/troubleshooting.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.
