I have a QUECTEL EM160R-GL in a USB3 enclosure and would like to use it with ATX1800.
It runs in MBIM mode, all models of GL-iNet routers I tried (AR750S, MT1300, Flint) failed to detect the modem and I had to configure each router manually.
The way to make QUECTEL EM160R-GL in a USB3 enclosure to work with ATX1800:
Step 1: I installed mbim related packages;
Step2: I checked the logs, looks like something has been detected;
kernel log:
14.926465] usbcore: registered new interface driver qmi_wwan
[ 14.930307] usbcore: registered new interface driver rndis_host
[ 15.105400] cdc_mbim 2-1:1.4: cdc-wdm0: USB WDM device
[ 15.114883] cdc_mbim 2-1:1.4 wwan0: register ‘cdc_mbim’ at usb-xhci-hcd.0.auto-1, CDC MBIM, ee: xxxxxx:ca
[ 15.114985] usbcore: registered new interface driver cdc_mbim
[ 15.124984] usbcore: registered new interface driver option
[ 15.129598] usbserial: USB Serial support registered for GSM modem (1-port)
system log:
Thu Aug 11 18:43:47 2022 daemon.info [6072]: [cdc-wdm0/mbim] MBIM device is not QMI capable
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Read max control message size from descriptors file: 4096
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Opening device with flags ‘version-info, proxy, mbim, expect-indications’…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] created endpoint
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] creating MBIM device…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] MBIM device created
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] opening MBIM device…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: opening device…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Read max control message size from descriptors file: 4096
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] MBIM device open
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Checking version info (15 retries)…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] QMI Device supports 34 services:
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] ctl (1.5)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] wds (1.155)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] dms (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] nas (1.25)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] qos (1.14)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] wms (1.10)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] auth (1.13)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] at (1.4)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] voice (2.1)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] cat2 (2.24)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] uim (1.77)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] pbm (1.4)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] test (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] loc (2.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] sar (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] ims (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] ts (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] tmd (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] wda (1.20)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] csvt (1.1)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] imsa (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] coex (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] pdc (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] rfrpe (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] dsd (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x30] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x31] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x36] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x44] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x47] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x49] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x4a] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x4d] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] unknown [0x4e] (1.0)
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Enabling QMI indications via MBIM…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] enabled QMI indications via MBIM
Thu Aug 11 18:43:48 2022 daemon.info [6072]: [modem0/cdc-wdm0/mbim] MBIM device is QMI capable
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Allocating new client ID…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Registered ‘dms’ (version 1.0) client with ID ‘1’
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Allocating new client ID…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Registered ‘nas’ (version 1.25) client with ID ‘5’
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Allocating new client ID…
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Registered ‘loc’ (version 2.0) client with ID ‘1’
Thu Aug 11 18:43:48 2022 daemon.debug [6072]: [/dev/cdc-wdm0] Allocating new client ID…
So the modem has been detected but the GL-iNet GUI does not show it (instead it says something about repeater which is disabled)
Step 3: ok, if QUECTEL EM160R-GL in a USB3 enclosure is not detected by the GL-iNet GUI, we have to configure it manually using luci. I installed modemmanager and the luci frontend for it , configured WWAN interface by defining APN and the protocol type and got everything working:
That would be really cool if the GL-iNet GUI could properly work with this modem, detect it and let users to configure it - I am pretty much sure not everyone knows about luci and such.
That is the great news,thank you very much.
I would say that QUECTEL and Sierra Wireless share about 90% of the DIY market, plus 10% for Telit. I think if you properly support those 3 brands / cellular modems you will not hear any complains from your users for another 5 years.
Hey glad I found this! I’m in same boat, have an EM12 in usb 3 enclosure. GLi doesn’t see it at all, and it looks like advanced settings redirects me to Luci, but I’ve not used modemmanager before. In the Luci screens i don’t see usb device to add on WWAN. Any suggestions would be great!
First of all, you should make sure that the modem is detected by OpenWRT - you need to search in the log for the messages indicating that the modem has been found - the example of the log is given above.
If the modem has been detected then you have to install modemmanager and simply choose the correct device in its settings - please have a look at the screenshot in the first post. After that you should add APN name in the modemmanager (see the screenshot) and everything should start working. If you modem runs in MBIM mode then you will need to install missing mbim related packages.
My modem was in MBIM because I was using it in a different router running LEDE/OpenWRT Therefore I had to install the missing mbim* packages. And I noticed that QMI modules have been already present in the system (i.e. they are present by default).
It looks like the modem is being detected from what i can tell, and in QMI mode so that is good. How do I install modem manager on this modem? i’ve search and only found instructions using device specif firmware with modem manager in it.
Wed Aug 17 04:27:54 2022 kern.info kernel: [ 15.123378] NET: Registered protocol family 24
Wed Aug 17 04:27:54 2022 kern.info kernel: [ 15.127197] usbcore: registered new interface driver qmi_wwan
Wed Aug 17 04:27:54 2022 kern.info kernel: [ 15.131359] usbcore: registered new interface driver rndis_host
Wed Aug 17 04:27:54 2022 kern.info kernel: [ 15.294612] usbcore: registered new interface driver option
Wed Aug 17 04:27:54 2022 kern.info kernel: [ 15.294682] usbserial: USB Serial support registered for GSM modem (1-port)
Latest firmware 4.1.0 release 7, clean install, EM160R-GL is attached in the external USB3 enclosure.
Looking at the log in luci the modem has been detected:
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 14.862323] usbcore: registered new interface driver cdc_ether
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 14.866620] usbcore: registered new interface driver cdc_ncm
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 14.928528] usbcore: registered new interface driver huawei_cdc_ncm
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.072321] PPP generic driver version 2.4.2
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.073913] NET: Registered protocol family 24
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.106629] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.106657] qmi_wwan 2-1:1.4: QuectelEC25&EC21&EG91&EG95&EG06&EP06&EM06&BG96&AG35 work on RawIP mode
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.112074] qmi_wwan 2-1:1.4 wwan0: register ‘qmi_wwan’ at usb-xhci-hcd.0.auto-1, WWAN/QMI device, aa:c0:a5:87:c9:99
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.120190] usbcore: registered new interface driver qmi_wwan
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.132078] usbcore: registered new interface driver rndis_host
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.290951] usbcore: registered new interface driver option
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.291023] usbserial: USB Serial support registered for GSM modem (1-port)
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.295507] option 2-1:1.0: GSM modem (1-port) converter detected
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.302533] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.308859] option 2-1:1.1: GSM modem (1-port) converter detected
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.315612] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.321466] option 2-1:1.2: GSM modem (1-port) converter detected
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.328508] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.334318] option 2-1:1.3: GSM modem (1-port) converter detected
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 15.341297] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
Sun Dec 11 22:31:20 2022 kern.err kernel: [ 20.354430] ath11k c000000.wifi: Not multipd architecture
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 20.354849] ath11k c000000.wifi: ipq6018 hw1.0
Sun Dec 11 22:31:20 2022 kern.info kernel: [ 20.359101] remoteproc remoteproc0: powering up cd00000.qcom_q6v5_wcss
–
BUT neither the gl-inet GUI detects it nor a new interface has been created.
So, I guess it is still unsupported (without manual changes), please confirm.
Oh, this is very interesting. I am using a self powered USB 3 enclosure which works just fine with other routers.
Could you please do the following:
a) what is the version of AXT1800 firmware?
b) Can you press “Manual Setup” and show me a screenshot of the parameters defining protocol / port?
c) I assume you run the modem in QMI mode? Could you go to
http://YOU_MODEM_IP/#/modemmanage
run the following manual command: AT+QCFG="usbnet"
and show the screenshot with the command output?
d) can you please open luci and show the screenshot of the “Interface” page (want to see the name of WWAN interface, I have to create it manually).
e) can you please open the corresponding WWAN (LTE modem interface, whatever name it can have) and show me a screenshot with the general settings of the LTE interface (want to see protocol / device name)?
–
Last but not least - are you sure that you run your modem on the stock firmware and did not install any additional packages (I see that you work for GL.iNet and therefore your router could be used for tests, .i.e. some additional packages could be installed in the past)?
