New modules not connecting: different QMBNCFG and firmware revision

Hi,

We have received a new batch of modules which cannot register to a cell tower. They have newer firmware and MBN config (AT+QMBNCFG=“List”). Can we get a firmware package to downgrade the new module to see if that will allow it to register to cell tower? Below I have pasted commands from one of the new modules we received which doesn’t register to cell tower (Module #1) and a working module which can register to a cell tower (Module #2).

The differences between the working and not working modules I have found so far is:

  1. they have different firmware revisions (see below)
  2. they have different MBN Files (AT+QMBNCFG=“List”) (see below)
  3. Serving cell: module #1 LIMSRV, module #2 NOCONN
  4. Registration: module #1 Searching, module #2 RegisteredHome

below is the result of running the following commands on both modules:

  1. AT+QMBNCFG=“List”
  2. AT+QENG=“servingcell”
  3. AT+CGREG?

Module #1: Not working, cannot register to cell tower:


AT+QMBNCFG="List"

+QMBNCFG: "List",0,0,0,"ROW_Generic_3GPP",0x05010820,201905141
+QMBNCFG: "List",1,1,1,"VoLTE-ATT",0x0501033C,202004261
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,202004091
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,202004211
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,202003251
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,202004151

DONE


EG25GGBR07A08M2G_01.002.01.002
OK

AT+QENG="servingcell"
+QENG: "servingcell","LIMSRV","LTE","FDD",310,410,AD0FF03,269,2600,5,3,3,331C,-85,-9,-58,18,45
OK

AT+CGREG?
+CGREG: 0,2
OK

Module #2: Working module, can register to cell tower:


AT+QMBNCFG="List"

+QMBNCFG: "List",0,0,0,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,1,1,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201

DONE


EG25GGBR07A08M2G_01.001.01.001
OK


AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","LTE","FDD",310,410,AD0FF03,269,2600,5,3,3,331C,-87,-11,-55,20,-
OK

AT+CGREG?
+CGREG: 0,1
OK

We are using Linux so would need a QFirehose package I think.

The problem was you need to set the APN before the AT&T SIM card will connect with the Quectel EG25-G now. We tried a different vendors SIM and it worked straight away. For AT&T, you must set the APN in order to register to the cell tower.