Modem issues with MR200 v5

I've got OpenWrt running fine so far, the only issue is the modem, which is a Qualcomm modem (same as in the v4). It's being detected as QMI device and AT commands work as well. I'm already using @mrhaav modified uqmi which made it possible to have at least some response from it. But it doesn't register with the network, I've only got it this far with various configurations:

Tue Sep  5 17:11:28 2023 daemon.notice netifd: 4G (3334): PINcode disabled
Tue Sep  5 17:11:28 2023 daemon.notice netifd: 4G (3334): Data format set to raw-ip
Tue Sep  5 17:11:28 2023 daemon.notice netifd: 4G (3334): Default profile: 1
Tue Sep  5 17:11:29 2023 daemon.notice netifd: 4G (3334): Initiate airplane mode
Tue Sep  5 17:11:30 2023 daemon.notice netifd: 4G (3334): Change default profile
Tue Sep  5 17:11:30 2023 daemon.notice netifd: 4G (3334):  apn: set to network default
Tue Sep  5 17:11:30 2023 daemon.notice netifd: 4G (3334):  authentication: pap to none
Tue Sep  5 17:11:30 2023 daemon.notice netifd: 4G (3334): Airplane mode off
Tue Sep  5 17:11:32 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:34 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:36 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:38 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:41 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:44 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:47 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:50 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:11:57 2023 daemon.notice netifd: 4G (3334):  searching on
Tue Sep  5 17:12:03 2023 daemon.notice netifd: 4G (3334):  searching on

Hi
Do you have your antennas connected and coverage from your service provider? :wink:
Did it worked with the TP-Link SW?

You can let the modem search for ever with:

uci set network.4G.abort_search=false
uci commit network

and restart our interface.

2 Likes

Hi,

yeah the antennas are connected. The modem did work on stock, I've also tested two sim cards from different providers, no real change. I've added the setting to keep it searching (also yes, I changed the interface name to wan), but it's unable to find anything (or register?).

Tue Sep  5 17:02:44 2023 daemon.notice netifd: wan (1789): Waiting for modem to initiate
Tue Sep  5 17:02:46 2023 daemon.notice netifd: wan (1789): PINcode disabled
Tue Sep  5 17:02:46 2023 daemon.notice netifd: wan (1789): Data format set to raw-ip
Tue Sep  5 17:02:46 2023 daemon.notice netifd: wan (1789): Default profile: 1
Tue Sep  5 17:02:47 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:02:49 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:02:51 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:02:53 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:02:56 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:02:59 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:02 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:06 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:12 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:18 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:25 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:32 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:43 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:03:54 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:04:06 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:04:20 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:04:38 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:04:57 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:05:17 2023 daemon.notice netifd: wan (1789):  not_registered on
Tue Sep  5 17:05:38 2023 daemon.notice netifd: wan (1789):  not_registered on

Install picocom (if not installed), connect with picocom /dev/ttyUSB1
and query your modem with AT+COPS=?

2 Likes

You could try to set the PLMN for your service provider:

uci set network.wan.plmn=<your service provider plmn>
uci commit network

Which service provider are you using?

1 Like

Hm, I can't actually do that, picocom hangs when I try to enter the command. When I re-open picocom it hangs for a few seconds then greets me with "+CME ERROR: operation not allowed". Some logs and information about the device:

cat /sys/kernel/debug/usb/devices:

(Had to add the device ID manually so I can use the ttys)

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=05c6 ProdID=9025 Rev= 3.18
S:  Manufacturer=Android
S:  Product=Android
S:  SerialNumber=58d3b311
C:* #Ifs= 9 Cfg#= 1 Atr=a0 MxPwr=500mA
A:  FirstIf#= 6 IfCount= 3 Cls=01(audio) Sub=00 Prot=00
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=option
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=84(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E:  Ad=86(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E:  Ad=88(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
I:* If#= 6 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=option
I:* If#= 7 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=option
I:  If#= 7 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=option
E:  Ad=8a(I) Atr=05(Isoc) MxPS=  16 Ivl=1ms
I:* If#= 8 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=option
I:  If#= 8 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=option

picocom /dev/ttyUSB2:

at+cops=?
Terminating...
Skipping tty reset...
Thanks for using picocom
root@OpenWrt:~# picocom /dev/ttyUSB2
picocom v3.1

port is        : /dev/ttyUSB2
flowcontrol    : none
baudrate is    : 9600
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        :
omap is        :
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

+CME ERROR: operation not allowed
ati
Manufacturer: QUALCOMM INCORPORATED
Model: 4108
Revision: MPSS.JO.2.0.2.c1.7-00034-9607_GENNS_PACK-1.280100.1  1  [Apr 20 2020 00:00:00]
SVN: 01
IMEI: - snip -
+GCAP: +CGSM

OK

netzclub right now to test, this didn't work either unfortunately.

option driver incorrectly bound to the ADB interface, hence the offset with tty numbers. But you figured that out.
Please try AT+COPS=?, you may need to wait for a response.

1 Like

Same result when waiting:

at+cops=?
+CME ERROR: operation not allowed

Was the device locked to a particular carrier?

1 Like

Can you paste syslog when you had your PLMN set?

1 Like

It shouldn't be, I bought it directly off TP-Links amazon store.

Tue Sep  5 17:20:29 2023 daemon.notice netifd: wan (1786): Waiting for modem to initiate
Tue Sep  5 17:20:31 2023 daemon.notice netifd: wan (1786): PINcode disabled
Tue Sep  5 17:20:31 2023 daemon.notice netifd: wan (1786): Data format set to raw-ip
Tue Sep  5 17:20:31 2023 daemon.notice netifd: wan (1786): Default profile: 1
Tue Sep  5 17:20:32 2023 daemon.notice netifd: wan (1786): PLMN set to mcc: 262 mnc: 07
Tue Sep  5 17:20:32 2023 daemon.notice netifd: wan (1786):  not_registered on
Tue Sep  5 17:20:34 2023 daemon.notice netifd: wan (1786):  not_registered on
Tue Sep  5 17:20:36 2023 daemon.notice netifd: wan (1786):  not_registered on
Tue Sep  5 17:20:38 2023 daemon.notice netifd: wan (1786):  not_registered on
Tue Sep  5 17:20:41 2023 daemon.notice netifd: wan (1786):  not_registered on
[...]

Just to be sure: AT+CLCK?

1 Like

Have you done a power reboot?

1 Like

AT+CLCK? just gives an error, AT+CLCK=? however:

at+clck=?
+CLCK: ("AB","AC","AG","AI","AO","IR","OI","OX","SC","FD","PN","PU","PP","PC","PF")

OK

Yep, same result.

It looks like every facility needs to be checked separately, so in this case
at+clck="PN",2

and also please at+cfun?

1 Like
at+clck="PN",2
+clck: 0

OK
at+cfun?
+CFUN: 1

OK

Can you try:

uqmi -d /dev/cdc-wdm0 --get-device-operating-mode
uqmi -d /dev/cdc-wdm0 --get-serving-system
uqmi -d /dev/cdc-wdm0 --get-signal-info
uqmi -d /dev/cdc-wdm0 --network-scan
2 Likes