EG916Q-GL detected as USB AT Port, but no response to AT commands

IoT Modules LTE Standard Module
1

Hello,

I am starting to work with a Quectel UMTS & LTE EVB kit equipped with an EG916Q-GL module, but I cannot communicate with the module through AT commands.

I have installed the latest official Windows driver available for this module:

Quectel_Windows_USB_Driver(Q)_RNDIS_V1.1_EN

Windows detects the module and creates the Quectel USB ports correctly. In Device Manager, the AT interface appears as:

  • Quectel USB AT Port (COM13)

  • Hardware ID: USB\VID_2C7C&PID_6007&MI_04

I will attach a screenshot showing how the Quectel USB AT Port is detected in Device Manager.

WhatsApp Image 2026-07-15 at 11.18.37
WhatsApp Image 2026-07-15 at 11.18.37607×362 51.3 KB

The EVB also appears to be correctly connected and powered:

  • The active SIM card is correctly inserted.

  • The LTE main antenna is connected.

  • D209 is ON.

  • D205 is ON.

  • D206 is blinking with the pattern corresponding to network registration/idle mode.

  • The module has been switched on using PWRKEY.

I will also attach a picture showing the EVB connections and LED status.

WhatsApp Image 2026-07-15 at 11.20.10
WhatsApp Image 2026-07-15 at 11.20.101152×2048 206 KB

I have tried communicating with the module using both QCOM and Tera Term. In QCOM, I select the Quectel USB AT Port and configure it at 115200 baud. The COM port opens correctly, but the module does not return any response when I send AT commands.

There is no OK, error message or any other response. The same issue occurs with Tera Term.

I will attach a screenshot of the QCOM configuration and the unsuccessful AT command attempts.

WhatsApp Image 2026-07-15 at 11.23.03
WhatsApp Image 2026-07-15 at 11.23.031170×1600 97.7 KB

I have also noticed that the D207 sleep-status LED does not appear to switch off when an AT command is sent.

Could you please help me confirm the following?

  1. Is Quectel_Windows_USB_Driver(Q)_RNDIS_V1.1_EN the correct driver for the EG916Q-GL with USB PID 6007? I have also tested previous driver versions, including the driver supplied with the EVB, but the module still does not respond.

  2. Is MI_04 the correct USB AT interface for this module?

  3. Could the module be remaining in sleep mode and therefore not responding through USB?

  4. Is any additional USB configuration or driver required?

  5. Should I use the MAIN UART interface to disable sleep or change the USB network configuration?

  6. Could this problem be related to the firmware version or the default USB composition?

Thank you in advance for your support.

2

Solved

I am posting the solution in case someone encounters the same issue in the future.

After installing the Quectel Windows USB drivers mentioned in my original post, I discovered that the USB COM ports were incorrectly named or assigned by the driver.

The Quectel documentation indicates that AT commands should be sent through the port named:

Quectel USB AT Port

However, in my case, this port did not respond to any AT commands. The port named:

Quectel USB NMEA Port

is actually the interface that responds correctly to AT commands.

After opening the Quectel USB NMEA Port in QCOM, I received normal responses to all AT commands and was able to configure the EG916Q-GL modem successfully.

Therefore, if the Quectel USB AT Port does not respond, try the Quectel USB NMEA Port, as the port names may be swapped or incorrectly assigned by the Windows driver.

No additional USB configuration or sleep-mode changes were required in my case.

Greetings from the past!

3

It might have been worth mentioning the operating mode - ECM or RNDIS - since the numbering appears to differ between these modes.