> 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/cinterion-r-els61-wireless-module/general-at-commands.md).

# General AT Commands for the Cinterion® ELS61 Wireless Module

AT commands, or the Hayes command set, are instructions for controlling modules. The commands consist of a series of short text strings for a range of uses, including:

* Configuring a module
* Establishing the module's network connection
* Discovering module and connection status information, to ensure they are working correctly
* Managing the module
* Encrypting and transporting data to and from the module
* Directly accessing the cloud

You can find a full set of the Cinterion® ELS61 Wireless Module AT commands here:

[Cinterion® ELS61-E2 AT Command Set PDF](https://developer.gemalto.com/sites/default/files/els61-e2_atc_01000.pdf)

{% hint style="info" %}
Your software will need to send test, read and write AT commands to the Cinterion® ELS61 Wireless Module.
{% endhint %}

### Before you begin

Before you use any AT commands on the modem, ensure that it is ready to receive them.

To test that the modem is ready to receive AT commands:

1. Using a terminal emulator that is connected to your modem, type:

   `at`\<return>

   The terminal emulator will return any of the following:

   `OK` – the modem and port are connected and ready to communicate

   `ERROR` – the modem and port cannot communicate. Contact the modem supplier.

   Nothing – ensure you have set the correct baud rate in your code. For more information, see [Connecting to the LTE Cat.1-xx click](https://docs.eseye.com/modules/cinterion-r-els61-wireless-module/connecting-to-the-lte-cat-1-xx-click.md).

## AT Command syntax

Use the following syntax:

```
AT+<COMMAND><CR>
```

where:

* `AT` is in upper or lowercase
* `<COMMAND>` is a test, read or write command in upper or lower case
* `<CR>` is the end-of-line character marking the end of a command line (alias \r – carriage return)

  The modem will execute the command line after receiving the end-of-line character.
* `<LF>` is the line feed, which will move the cursor to the next line

{% hint style="info" %}
This document displays commands only. `<CR><LF>` after a command is intentionally omitted.
{% endhint %}

AT commands are usually followed by a response that includes:

```
<CR><LF><RESPONSE><CR><LF>
```

where `<RESPONSE>` is the command response

{% hint style="info" %}
This document displays responses only. `<CR><LF>` is intentionally omitted.
{% endhint %}

The response may include:

* `OK` – indicates the command executed with no errors
* `ERROR` – indicates an invalid command, or that the command line was too long

## Types of AT Commands and responses

| Command type | Command syntax                                                     | Description                                                                                                                                                                                                                                                                         |
| ------------ | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test**     | `AT+<COMMAND>=?`                                                   | Returns a list of parameters and value ranges set by the corresponding Write command or internal processes.                                                                                                                                                                         |
| **Read**     | `AT+<COMMAND>?`                                                    | Returns the currently set value of each parameter.                                                                                                                                                                                                                                  |
| **Write**    | <p><code>AT+\<COMMAND>=</code></p><p><code>\<parameter></code></p> | Sets the user-defined parameter values.                                                                                                                                                                                                                                             |
| **Execute**  | `AT+<COMMAND>`                                                     | Reads non-variable parameters affected by internal processes in the Eseye-enabled modem. For example, see [CCID – request unique SIM number (ICCID)](https://docs.eseye.com/modules/cinterion-r-els61-wireless-module/general-at-commands/ccid-request-unique-sim-number-iccid.md). |

{% hint style="info" %}
Thales supply a large set of AT commands that work with the Cinterion® ELS61 Wireless Module. You may find `AT+CCID`, `AT+CREG`, `AT+CEREG`, `AT+CGREG` and `AT+CSQ` useful. For more information, see the Thales AT command set documentation.
{% endhint %}


---

# 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.eseye.com/modules/cinterion-r-els61-wireless-module/general-at-commands.md?ask=<question>&goal=<user_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.
