Question on Quectel EG800G-EU TCP/IP & HTTP Stack Support and Pin-to-Pin Compatibility with EG800Q-EU

IoT Modules LTE Standard Module
,
1

Dear all,

I am currently evaluating the Quectel EG800G-EU module for an application that requires TCP/IP and HTTP functionality. During my tests, I observed that the AT+QPING command works correctly and returns expected results, confirming that basic IP connectivity is available.

However, when attempting to open a TCP connection using the AT+QIOPEN command, the module appears to hang and does not proceed to establish the connection. The same test sequence, executed under identical conditions on a Quectel EG800Q-EU module, works flawlessly — both TCP/IP and HTTP operations complete successfully.

Given these results, I would like to request clarification on the following points:

  1. Does the EG800G-EU fully support the TCP/IP stack and HTTP functionality in the same way as the EG800Q-EU?
  2. Are there any firmware or configuration differences that could explain the observed behavior with AT+QIOPEN?
  3. Can you confirm whether the EG800G-EU and EG800Q-EU are pin-to-pin compatible and can be interchanged on the same PCB without requiring hardware modifications?

Any insights, documentation references, or configuration recommendations would be greatly appreciated.

Thank you in advance for your support.

Best regards

2

hi

Please provide the configuration number information of ATI
Let me check internally.

Thanks

3

Thank you for the response.

Quectel EG800G-EU → AT+QGMR → EG800GEULDR01A13M04_01.001.01.001

I am currently referring to the AT Commands Manual Version 1.2 for the EC200U, EG800G, EG91xU, and EG915G series. However, I’ve noticed that certain commands—such as AT+QGMR—are not listed in the documentation, despite being functional on the modules.

Could you kindly confirm whether a more recent version of the manual is available that includes these missing commands?

4

hi，

Because this is an internal instruction and not for external use.
So it was not included in the document.

5

Thanks for the earlier clarification. I still have a couple of open questions:

  • Are the two modules pin-to-pin compatible?

  • Does the Quectel EG800G module support TCP/IP functionality?

6

the Quectel EG800G module support TCP/IP functionality。
@fuguiwang-Q Please help to look into the first question.

7

Thanks for confirming that the EG800G module supports TCP/IP functionality.

However, I’d like to understand why key socket-related AT commands such as AT+QIOPEN, AT+QISEND, etc. are not listed in the official AT command manual for EG800G. These are essential for TCP/IP communication, yet they seem to be missing from the documentation.

Moreover, I’ve tried issuing these commands directly to the module, but they return errors or no response, which makes me wonder whether they’re supported in the current firmware or require specific activation.

Could you please clarify:

  • Whether these commands are officially supported on EG800G?
  • If so, where can I find the correct and complete documentation?
  • Are there firmware versions or configurations that enable full socket functionality?

Thanks in advance for your help!

8

hi，

  1. Please execute: AT + QIOPEN =? ,AT+QISEND=? Check the return value of the module.
  2. I sent you a document privately. You can refer to it.
9

Thank you very much for sharing the document.
I tried executing the commands AT+QIOPEN=? and AT+QISEND=?, but unfortunately the module freezes right after. It does not return any error code and stops responding to further AT commands, remaining unresponsive until the power supply is turned off and restarted.

10

Could the AT commands be sent normally after the system restart?

11

Yes, after restarting the system all AT commands work normally, except for the TCP/IP related ones. The only exception is that AT+QIPING still works correctly.

12

Could you please provide the AT log?

13

AT
OK

AT+GMI
Quectel
OK

AT+QGMR
EG800GUR01A13M04_01.001.01.0
OK

AT+CGMR
EG800GUR01A13M04
OK

AT+CEREG=1
OK

AT+CGDCONT=1, “IP”, “TM”
OK

AT+CEREG?
+CEREG: 1,0
OK
+CEREG: 5

AT+CGATT?
+CGATT: 1
OK

AT+QIACT=1
OK

AT+QIACT?
+QIACT: 1,1,1,“IP”
OK

AT+QPING=1, “8.8.8.8”
OK
+QPING: 0,“8.8.8.8”,64,119,255
+QPING: 0,“8.8.8.8”,64,126,255
+QPING: 0,“8.8.8.8”,64,114,255
+QPING: 0,“8.8.8.8”,64,130,255
+QPING: 0,4,4,0,114,130,124

AT+QIOPEN=1,0,“TCP”,“<domain_name>”,80,0,1
No response in 150s, for 5 times with different <domain_name>

14

hi，

From the AT log, it seems that the module has not registered for the internet. To perform TCP operations, it is necessary to register for the network.

15

Hi,
Thanks for your observation. However, the module is actually registered to the network, as confirmed by the AT log:

AT+CEREG?
+CEREG: 0,5
OK

The value +CEREG: 0,5 indicates that the module is successfully registered to the LTE network and is capable of both SMS and data services. The initial mention of +CEREG: 1,0 was either from a different context or a misreading.

Additionally, the fact that the module can execute a successful AT+QPING=1,"8.8.8.8" confirms that it has active network connectivity, since ICMP ping requires a working data session.

That said, I believe the issue with AT+QIOPEN hanging without response is likely due to a firmware limitation or a bug in the Quectel EG800G module. If you have any suggestions for AT command sequences that are known to work reliably for opening TCP sockets I’d really appreciate it.

16

Thank you for your reply.

  1. Sorry, I only saw 0 and 1, so I concluded that the module was not registered on the network.
    AT+CEREG?
    +CEREG: 1,0
    OK
  2. Next, please follow the instructions below:
    AT + QIOPEN =?
    AT+QISEND=?
    AT+QENG=“servingcell”
    AT+QIDNSGIP=?
    AT+QIOPEN=1,0,“TCP”,“8.8.8.8”,80,0,1
17

Hi everyone,
First of all, thank you so much for your help — I really appreciate it!

After following the commands you suggested, I’m now able to successfully run AT+QIOPEN and all the other TCP/IP commands without any issues. Everything works as expected.

That said, I’m still a bit puzzled — I haven’t changed anything compared to the previous version where it wasn’t working. I simply executed the commands you recommended, and now it works. I’m not sure what was causing the problem before, but I’m glad it’s resolved!

Thanks again for the support!