> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/modules/quectel/connecting-to-the-quectel-module-using-a-terminal-emulator.md).

# Connecting to the Quectel module using a terminal emulator

If you are testing a single unit, we recommend that you use a terminal emulator to execute the AT commands, for example PuTTY or Tera Term.

### Serial port settings

Change the port settings using Device Manager, and ensure you also adjust the serial port settings in the terminal emulator.

| Serial port setting | Default value |
| ------------------- | ------------- |
| Baud rate           | 115200        |
| Data Bits           | 8             |
| Parity              | None          |
| Stop Bits           | 1             |
| Flow Control        | None          |


---

# 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.eseye.com/modules/quectel/connecting-to-the-quectel-module-using-a-terminal-emulator.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.