> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/controller/pilot-pro/operating-handbook/radio-modules/doodle-labs-radio-module/doodle-pro-tips.md).

# Doodle Pro Tips

## Pro Tips for Resolving Radio Connectivity Issues

**1. Too Close?**\
Ensure that your air and ground radios are at least 2 feet apart. Doodle radios are powerful, and if they are too close, they may create interference with each other.

**2. Too Soon?**\
Give it time. Each radio takes about 60 seconds from power-up to fully boot its system. Ensure both the air and ground radios have been powered on for at least 60 seconds before checking connectivity.

**3. Multiple Aircraft?**\
Be mindful of multiple Doodle radio pairs in the same environment. Doodle radios are not frequency hopping and are shipped with channel 3 selected by default. If multiple pairs are on the same channel, they will interfere with each other. Make sure to select [different channels](/ecosystem/controller/pilot-pro/operating-handbook/radio-modules/doodle-labs-radio-module/doodle-channel-selection.md) for each pair.

**4. Determine Which Path is Broken**\
Pilot Pro and the tablet have separate communication links. It’s possible for one to be connected while the other is not. If the Pilot Pro’s LED is blue, it indicates no connection. A green LED means it’s connected.

**5. Environmental Radio Interference**\
Doodle radios operate on the 2.4 GHz band, similar to typical Wi-Fi devices. We default to channel 3 to minimize interference with common Wi-Fi routers. However, you may need to perform a [channel scan ](/ecosystem/controller/pilot-pro/operating-handbook/radio-modules/doodle-labs-radio-module/doodle-channel-selection.md)to find a less congested channel.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.freeflysystems.com/ecosystem/controller/pilot-pro/operating-handbook/radio-modules/doodle-labs-radio-module/doodle-pro-tips.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.