Anyone who has worked with RM500U-CN?

Roney · February 13, 2023, 1:57pm

It says

+QCFG: "ethernet",1

jfrog · February 13, 2023, 2:37pm

this explains a lot )
Please try

AT+QCFG="ethernet",0
AT+QCFG="usbnet",1
AT+QCFG="nat",2
at+qnetdevctl=1,1,1
AT^RESET

Then check with AT+QNETDEVSTATUS and try DHCP (with the proper interface name).
Please do not use pictures to display textual information.

Roney · February 13, 2023, 3:50pm

OMG! Finally, it got a DHCP response. It still can’t ping anything on the internet tho.

pi@ubuntu:~$ ifconfig -a
enxaa1a7249342e: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether aa:1a:72:49:34:2e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether e4:5f:01:f4:ef:5f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 101  bytes 8154 (8.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 101  bytes 8154 (8.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.43.136  netmask 255.255.255.0  broadcast 192.168.43.255
        inet6 fe80::e65f:1ff:fef4:ef61  prefixlen 64  scopeid 0x20<link>
        ether e4:5f:01:f4:ef:61  txqueuelen 1000  (Ethernet)
        RX packets 151  bytes 19296 (19.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 167  bytes 26489 (26.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@ubuntu:~$ sudo dhclient -v enxaa1a7249342e
[sudo] password for pi:
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enxaa1a7249342e/aa:1a:72:49:34:2e
Sending on   LPF/enxaa1a7249342e/aa:1a:72:49:34:2e
Sending on   Socket/fallback
DHCPDISCOVER on enxaa1a7249342e to 255.255.255.255 port 67 interval 3 (xid=0x5d952477)
DHCPOFFER of 192.168.42.2 from 192.168.42.1
DHCPREQUEST for 192.168.42.2 on enxaa1a7249342e to 255.255.255.255 port 67 (xid=0x7724955d)
DHCPACK of 192.168.42.2 from 192.168.42.1 (xid=0x5d952477)
bound to 192.168.42.2 -- renewal in 33329 seconds.
pi@ubuntu:~$ sudo udhcp -i enxaa1a7249342e
sudo: udhcp: command not found
pi@ubuntu:~$ sudo udhcpc -i enxaa1a7249342e
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 192.168.42.2
udhcpc: lease of 192.168.42.2 obtained, lease time 86400
pi@ubuntu:~$ sudo route add -net 0.0.0.0 enxaa1a7249342e
sudo: unable to resolve host ubuntu: Temporary failure in name resolution
pi@ubuntu:~$ ping -I enxaa1a7249342e 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.42.2 enxaa1a7249342e: 56(84) bytes of data.
From 192.168.42.2 icmp_seq=1 Destination Host Unreachable
From 192.168.42.2 icmp_seq=2 Destination Host Unreachable
From 192.168.42.2 icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5122ms
pipe 3
pi@ubuntu:~$

The AT+CREG and AT+CGREG return 2,0 and the AT+C5GREG returns 0,0.
The AT+CSQ returns 8,99.

Also the interface name keeps changing after each restart anyway to fix that?

jfrog · February 13, 2023, 4:24pm

Please try with AT+QCFG="nat",0 (followed by reset or re-insert) instead.
Disable arp on the interface with ifconfig or ip utility.
Regarding the interface name problem please see this.

that looks pretty weak to me

Roney · February 13, 2023, 4:46pm

Doing this causes the same dhcp can’t get an IP issue.

Maybe this is happening because it’s looking for a 5G network and I am in a 4G coverage area? any way to change that?

jfrog · February 13, 2023, 4:56pm

Last 0 in each response tells us that the modem is not registered to the network.
Start from the basic troubleshooting - antennas, SIM, bands, etc.

Once you see there 0,1 as before, check with AT+QNETDEVSTATUS and try DHCP again.

Roney · February 13, 2023, 5:09pm

The registered status was always 0. I could never register it to a network.

jfrog · February 13, 2023, 5:13pm

I mean this answer of yours:

If there is no network registration, there is no point in proceeding to the next step(s).

Roney · February 13, 2023, 5:23pm

That’s CEREG not CREG or CGREG or C5GREG. Running that still returns 0,1

jfrog · February 13, 2023, 5:42pm

Well, I’m a bit confused with these AT responses - I’ve checked on my LTE modem (not Quectel though) and I see 0,1 with both +CEREG and +CREG
Do you still have an IP address and correct APN in AT+CGPADDR and AT+CGDCONT? ?

Roney · February 13, 2023, 5:44pm

Yes, The ip is different but the rest is same.

AT+CGPADDR
+CGPADDR: 1,"100.74.126.254"
+CGPADDR: 2,""
+CGPADDR: 4,""
+CGPADDR: 11,""

OK
AT+CGDCONT?
+CGDCONT: 1,"IP","UNINET","0.0.0.0",0,0,0,0,,,,,,0,,,0,,0,0,0,0
+CGDCONT: 2,"IPV4V6","","0.0.0.0",0,0,0,2,,,,,,0,,,0,,0,0,0,0

jfrog · February 13, 2023, 5:52pm

That looks good.
Could you please check if AT+QCFG="nat",1 (followed by reset) will make any difference.

Roney · February 13, 2023, 5:56pm

it still shows not registered but CGDCONT has new params,

AT+CGPADDR
+CGPADDR: 1,"100.74.78.226"
+CGPADDR: 2,""
+CGPADDR: 4,""
+CGPADDR: 11,""

OK
AT+CGDCONT?
+CGDCONT: 1,"IP","UNINET","0.0.0.0",0,0,0,0,,,,,,0,,,0,,0,0,0,0
+CGDCONT: 2,"IPV4V6","","0.0.0.0",0,0,0,2,,,,,,0,,,0,,0,0,0,0
+CGDCONT: 4,"IP","enxbe94d7918c78","0.0.0.0",0,0,0,0,,,,,,0,,,0,,0,0,0,0
+CGDCONT: 11,"IPV4V6","ims","0.0.0.0",0,0,0,0,,,,,,0,,,0,,0,0,0,0

Roney · February 13, 2023, 6:14pm

No it’s all the same outputs. Nothing changed.
Also the AT command AT+QNETDEVSTATUS returns error 4 on this modem.

jfrog · February 13, 2023, 6:54pm

Try checking with AT+QNETDEVSTATUS=1 instead.
Not sure that is important, but set the same APN that you have in +CGDCONT with AT+QICSGP=1,1,"UNINET"

Roney · February 14, 2023, 2:14am

It shows error 3 now.

Running AT+QICSGP=1,1,“UNINET” didn’t affect the registration status.

jfrog · February 25, 2023, 1:36pm

@Roney, Did you modify the usb_wwan.c driver for “zero packet”?

Roney · February 25, 2023, 1:50pm

No I did not. Can you please guide me through the process?

jfrog · February 25, 2023, 1:59pm

I thought you mentioned that you followed waveshare instructions

Under “Add VID and PID” they show how to change the driver(s).
In usb_wwan.c you will see a section added for Quectel’s IDs, search there for “zero packet”.

Translated from Chinese manual:

For the USB Bulk Out transmission mode, if the length of the sent data is an integer multiple of the length of the USB data packet, an additional data packet with a length of zero is used to notify the peer that data transmission is complete.

Roney · February 25, 2023, 2:14pm

I am sorry but I don’t see where it says I need to make changes to the file. Also, I tried to follow the windows 10 instructions and it gives me the same results i.e. low signal and no registration. So it might be that the issue is something else?