EC25AF latest FW request and PPP debug help request

IoT Modules LTE Standard Module
1

Questions:

  1. May I have the latest firmware for EC25AFFA-MINIPCIE modems with version EC25AFFAR07A08M4G ?

  2. Any suggestions for next debug steps to troubleshoot the inconsistent PPP dial-up behavior described below ?

I have 5 EC25AFFA-MINIPCIE modems and all are running firmware version EC25AFFAR07A08M4G.

Only 1 of 5 EC25AF modems is making a proper PPP connection. I need to figure out why the other 4 modems will not make a proper connection. All 5 systems are prepared identically.

Observations:

All 5 modems are registered on their home network (Verizon Wireless) as shown by at+cereg? returning +CEREG: 0,1

I can confirm that the local IP addresses shown by at+cgpaddr=1 matches the IP addr shown on the VZW device info portal.

All 5 modems have identical PDP contexts for cid=1 with the proper APN string.

All 5 modems report similar PDP Context Read Dynamic Parameters as shown by at+cgcontrdp. As expected, the only difference is the IP address assignment assigned to each.

Only 1 of the 5 modems is receiving an IP address after the ATD*99# dial-up to establish the PPP connection as idicated by the lwip log as “I (169545) esp-netif_lwip-ppp: Connected”. The other 4 modems will not have this log entry and will not perform the ESP IDF “modem_console” ping or httpget funtions.

I can not find any difference in the configuration of the 5 modems and do not understand why I can reliably make a PPP connection on 1 modem but not the other 4 modems.

All 5 modems are connected to identical ESP32-S3 host controllers running identical ESP-IDF firmware utilizing lwip’s native PPP support.

Respectfully,
David.

2

Hi ，
Sent to your email,pls check.
PPP dialing failure issue, please try modifying the context ID

3

Hayes,

Thank you for sending the latest firmware. I have received the email.

Quectel Tech Support has reviewed my log files and verified that my PPP setup is OK. They are not sure what the root cause of the problem is and have given me instructions on how to “capture chipset Qlog for whole process.”

When I have a solution I will post the results of the helpdesk ticket here in the forum on this topic.

Respectfully,
David