ZTE MF823 - help getting started

Hello,
I need help to get my older reach module (fw ver 27.1) connected via a ZTE MF823 to the internet. On my Linux laptop the MF823 reports to the system by default in storage mode 0x1225, but can be switched to ethernet/rndis mode 0x1403 with usb_modeswitch, which gives me direct lte/internet connectivity.
When I connect the MF823 to the reach module the stick powers up and indicates LTE connection with its green led, the module goes automatically in mode 0x1403, but is not recognized as usb ethernet device as on my Linux laptop (checked with ifconfig).

How can I get this running?

best regards, Tobias

Hi Tobias,

Welcome to the community forum! I can see that we’ve been in touch over the email. Let me quickly repeat my questions for you.

For us to help you, it’s quite important to understand the overall setup. What are you trying to accomplish? Do you have the Internet connection on your Reach device? Are there any issues with the connection to the unit?

Hello Polina,
I want to receive correction data from an NTRIP service over lte. Using WiFi it is working flawless, but I want to have the reach module independent from WiFi. Therefore I want to use LTE connection to the internet.
My setup:
[REACH MODULE] —usb otg— [LTE STICK] --)))))))-- internet --)))))))-- NTRIP SERVICE

I can login into the reach module by ssh. There I can see with “lsusb” that the lte stick is in RNDIS mode (1403), but with “ifconfig” I can’t see it as an usb-network-device like on my linux laptop.

Hi Tobias,

Right. Just to double-check, is your Reach in a hotspot mode when you try this?

Hello,

yes, the module is in hotspot mode

Hi Tobias,

That’s a bit weird. I’m no pro at the different modems configurations. Still, I don’t think I’ve seen this type of issue before.

While I’m checking up with the devs about it, is it possible for you to check any other modems?

Hi Polina,

since the MF823 is one of the two reported working models here in the forum and these two models are quite old I only have this one. The other model I wasn’t able to purchase anymore.

Tobias,

Right, I get you! We’re now checking this with our devs. We’ll be sure to give you an update soon!

Hi,

here is a log from /var/log/messages:

Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.163351] usb 1-1: new high-speed USB device number 2 using xhci-hcd
Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.316591] usb 1-1: New USB device found, idVendor=19d2, idProduct=1225, bcdDevice=f0.f1
Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.316609] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.316622] usb 1-1: Product: ZTE WCDMA Technologies MSM
Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.316633] usb 1-1: Manufacturer: ZTE,Incorporated
Nov 1 12:16:21 mrover-lte user.info kernel: [ 84.316644] usb 1-1: SerialNumber: MF8230ZTED010000CP26171XXXXXXXXXXXXXXXXX_ABCD&&&&&&&&&&&&&&&&&&&0
Nov 1 12:16:22 mrover-lte user.info kernel: [ 84.506175] usb-storage 1-1:1.0: USB Mass Storage device detected
Nov 1 12:16:22 mrover-lte user.info kernel: [ 84.517849] usb-storage 1-1:1.0: Quirks match for vid 19d2 pid 1225: 1
Nov 1 12:16:22 mrover-lte user.info kernel: [ 84.522440] scsi host0: usb-storage 1-1:1.0
Nov 1 12:16:22 mrover-lte user.info kernel: [ 84.523733] usbcore: registered new interface driver usb-storage
Nov 1 12:16:22 mrover-lte syslog.notice usb_modeswitch: switch device 19d2:1225 on 001/002
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.347618] usb 1-1: USB disconnect, device number 2
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.755333] usb 1-1: new high-speed USB device number 3 using xhci-hcd
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.902181] usb 1-1: New USB device found, idVendor=19d2, idProduct=1403, bcdDevice=f0.f1
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.902199] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.902211] usb 1-1: Product: ZTE WCDMA Technologies MSM
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.902223] usb 1-1: Manufacturer: ZTE,Incorporated
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.902234] usb 1-1: SerialNumber: MF8230ZTED010000CP26171XXXXXXXXXXXXXXXXX_ABCD&&&&&&&&&&&&&&&&&&&0
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.966212] usb-storage 1-1:1.2: USB Mass Storage device detected
Nov 1 12:16:28 mrover-lte user.info kernel: [ 90.966933] scsi host0: usb-storage 1-1:1.2
Nov 1 12:16:29 mrover-lte syslog.notice root: usb_modeswitch: switched to 19d2:1403 on 001/003
Nov 1 12:16:29 mrover-lte user.notice kernel: [ 92.026641] scsi 0:0:0:0: CD-ROM CWID USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
Nov 1 12:16:29 mrover-lte user.info kernel: [ 92.031874] sr 0:0:0:0: [sr0] scsi-1 drive
Nov 1 12:16:29 mrover-lte user.info kernel: [ 92.031886] cdrom: Uniform CD-ROM driver Revision: 3.20
Nov 1 12:16:29 mrover-lte user.debug kernel: [ 92.036329] sr 0:0:0:0: Attached scsi CD-ROM sr0
Nov 1 12:16:29 mrover-lte user.notice kernel: [ 92.038939] sr 0:0:0:0: Attached scsi generic sg0 type 5
Nov 1 12:16:29 mrover-lte user.notice kernel: [ 92.046979] scsi 0:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Nov 1 12:16:29 mrover-lte user.notice kernel: [ 92.049566] sd 0:0:0:1: Attached scsi generic sg1 type 0
Nov 1 12:16:29 mrover-lte user.warn kernel: [ 92.050006] sd 0:0:0:1: Power-on or device reset occurred
Nov 1 12:16:29 mrover-lte user.notice kernel: [ 92.053632] sd 0:0:0:1: [sda] Attached SCSI removable disk

and here the output from lsusb:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 19d2:1403 ZTE WCDMA Technologies MSM
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and here from ip link show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether fc:db:b3:96:XX:XX brd ff:ff:ff:ff:ff:ff

Hi Tobias,

This looks like useful information, thanks for highlighting it!

Our devs team is already checking this case, so I’m waiting for the news from them so far to understand how I can help you here. By the way, can you share the whole Full system report with me? You can send it via support@emlid.com. It contains private information, so it’s better not to share it publicly.

Hi Tobias,

I’m back with good news: we’ve found why this happens on the device. Our devs are going to fix this in one of the future releases. It should resolve the issue you faced with Reach Module. We don’t have the exact dates of its release, but I’m sure to let you know when it’s out.

Hi Tobias,

We’ve just released Reach Firmware 28 that should fix the issue you faced. Let me know how it works for your Reach and modem.

Hello,
I just flashed v28.0 to the reach module.
Unfortunately there is no big change in behavior. Here is the system information:

Reach-lte:~$ tail -f /var/log/messages

Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.026888] usb 1-1: new high-speed USB device number 4 using xhci-hcd
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.181433] usb 1-1: New USB device found, idVendor=19d2, idProduct=1225, bcdDevice=f0.f1
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.181452] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.181465] usb 1-1: Product: ZTE WCDMA Technologies MSM
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.181477] usb 1-1: Manufacturer: ZTE,Incorporated
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.181488] usb 1-1: SerialNumber: MF8230ZTED010000CP261718U46EM0SHF3SVRVR7_9C63&&&&&&&&&&&&&&&&&&&0
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.200099] usb-storage 1-1:1.0: USB Mass Storage device detected
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.205397] usb-storage 1-1:1.0: Quirks match for vid 19d2 pid 1225: 1
Dec 21 06:57:10 Reach-lte user.info kernel: [ 355.205550] scsi host0: usb-storage 1-1:1.0
Dec 21 06:57:11 Reach-lte syslog.notice usb_modeswitch: switch device 19d2:1225 on 001/004
Dec 21 06:57:16 Reach-lte user.info kernel: [ 361.096317] usb 1-1: USB disconnect, device number 4
Dec 21 06:57:16 Reach-lte user.info kernel: [ 361.554875] usb 1-1: new high-speed USB device number 5 using xhci-hcd
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.713113] usb 1-1: New USB device found, idVendor=19d2, idProduct=1403, bcdDevice=f0.f1
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.713133] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.713145] usb 1-1: Product: ZTE WCDMA Technologies MSM
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.713156] usb 1-1: Manufacturer: ZTE,Incorporated
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.713167] usb 1-1: SerialNumber: MF8230ZTED010000CP261718U46EM0SHF3SVRVR7_9C63&&&&&&&&&&&&&&&&&&&0
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.791074] usb-storage 1-1:1.2: USB Mass Storage device detected
Dec 21 06:57:17 Reach-lte user.info kernel: [ 361.795023] scsi host0: usb-storage 1-1:1.2
Dec 21 06:57:17 Reach-lte syslog.notice root: usb_modeswitch: switched to 19d2:1403 on 001/005
Dec 21 06:57:18 Reach-lte user.notice kernel: [ 362.810031] scsi 0:0:0:0: CD-ROM CWID USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
Dec 21 06:57:18 Reach-lte user.info kernel: [ 362.815996] sr 0:0:0:0: [sr0] scsi-1 drive
Dec 21 06:57:18 Reach-lte user.debug kernel: [ 362.817375] sr 0:0:0:0: Attached scsi CD-ROM sr0
Dec 21 06:57:18 Reach-lte user.notice kernel: [ 362.818386] sr 0:0:0:0: Attached scsi generic sg0 type 5
Dec 21 06:57:18 Reach-lte user.notice kernel: [ 362.827525] scsi 0:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Dec 21 06:57:18 Reach-lte user.notice kernel: [ 362.829482] sd 0:0:0:1: Attached scsi generic sg1 type 0
Dec 21 06:57:18 Reach-lte user.warn kernel: [ 362.829626] sd 0:0:0:1: Power-on or device reset occurred
Dec 21 06:57:18 Reach-lte user.notice kernel: [ 362.836927] sd 0:0:0:1: [sda] Attached SCSI removable disk

Reach-lte:~$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether fc:db:b3:96:5a:cc brd ff:ff:ff:ff:ff:ff

Reach-lte:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 19d2:1403 ZTE WCDMA Technologies MSM
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What I see is that after flashing my linux laptop shows me a new USB Ethernet device “Emlid Ethernet”. The reach module is connected to the linux laptop over usb for flashing. Perhaps that is the normal case from beginning and I just never recognized.

Hi Tobias,

Well, that’s unexpected. Can you share the Full system report from Reach with me? Please, send it to support@emlid.com. I want to pass it to the devs to check what’s going on with your Reach.

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.