EG912U on PH-7 registering, but unable to access network

Evaluating EG912U-GL on PH-7 core board in the USA

Module was rebooting every few minutes until I reflashed it with BETA0002 firmware from the QuecDevZone website.
Now,
With Verizon and 1nce sims, it is assigned a valid network address, reports it is activated and registered, but dhcp to the module via ECM or RNDIS fails. In the case of 1nce, I know the IP address I should be assigned. So, I know the modem is getting this from the network provider.

I’ve tried under Windows 10 and 3 different flavors of Linux.
The SIMs I’m testing work in other modems.

What is most likely wrong?

Is there something like a PING command I can run as an AT command to verify I have connectivity from the modem, even if it will not properly respond to DHCP?

Well, part of my problem was the need for the Quectel specific
AT+QNETDEVCTL
command. [I’ve never before seen an ECM or RNDIS modem that required a special command to enable its DHCP server or to “Connect th network adapter”. Why does this command exist? If the PDP context is enabled and attached, what more has to happen? ]

So, I’ve got the the DHCP server giving out what clearly are unroutable (192.168.x.y) addresses although NAT is not enabled.

Not surprisingly, there’s no network connectivity from the private address. So,
I tried enabling NAT for cid 1, but, still, no network connectivity.

Still open to ideas…

Update:
The module is connecting for a few seconds, then it fails.

It’s USB powered on a PH-7 QuecPython board.
Likely a power supply and/or module hardware failure.

Hi brentr,

Based on your description, the module is able to successfully register on the network; however, data services cannot be accessed. This indicates that the RF registration procedure is completed normally, while the issue is likely occurring during the PDP context activation or data session establishment stage.

From my experience, this type of behavior is commonly related to operator-specific network policies rather than a module hardware defect. We kindly recommend checking the following points:

  1. APN Configuration
    Please confirm that the APN configured in

AT+CGDCONT

is correct and supported by the operator. Also verify the required PDP type (IP / IPV4V6 / IPV6), as some operators only allow specific PDP types.

  1. RAT and Network Mode
    We suggest temporarily forcing LTE-only mode to exclude RAT selection issues:

AT+QCFG=“nwscanmode”,3

After configuration, please reboot the module and retest.

  1. EPS Attach Type
    Some operators require a specific EPS attach type. You may try:

AT+QCFG=“epsattach”,1

Then restart the module and reattempt PDP activation.

Thank you for the tips.
I will keep them in mind in future.

However, in this case, the problem was due to a defective module.
I purchased another two EG-912u modules, one on an M.2 board and other on a PH7 board. Both worked fine.

Hi brentr,

Thank you for the update. Good to hear that your issue has been resolved. Feel free to reach out when you can any questions in the future.

Thank you and have a nice day