sorry, I didn't pay attention to that post
Can you send me a more complete log?
Too few logs are not conducive to problem analysis
thank you
I will but I have to reflash 4.4.9 and wait till it happens again so it will take some days.
Anyway there's nothing else useful on logs sadly apart from this:
Thu Aug 29 12:19:00 2024 cron.err crond[4331]: USER root pid 15130 cmd . /lib/functions/modem.sh;check_ip
Thu Aug 29 12:19:00 2024 cron.err crond[4331]: USER root pid 15131 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Thu Aug 29 12:20:00 2024 cron.err crond[4331]: USER root pid 18247 cmd . /lib/functions/modem.sh;check_ip
Thu Aug 29 12:20:00 2024 cron.err crond[4331]: USER root pid 18248 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Thu Aug 29 12:20:00 2024 cron.err crond[4331]: USER root pid 18249 cmd . /lib/functions/modem.sh;modem_net_monitor
Thu Aug 29 12:21:00 2024 cron.err crond[4331]: USER root pid 21295 cmd . /lib/functions/modem.sh;check_ip
Thu Aug 29 12:21:00 2024 cron.err crond[4331]: USER root pid 21296 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:18:01:391] call_end_reason is 1
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:18:01:391] call_end_reason_type is 2
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:18:01:391] call_end_reason_verbose is 210
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:18:01:391] try to requestSetupDataCall 60 second later
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:19:01:459] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:19:01:459] call_end_reason is 1
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:19:01:459] call_end_reason_type is 2
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:19:01:459] call_end_reason_verbose is 210
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:19:01:459] try to requestSetupDataCall 60 second later
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:20:01:527] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:20:01:527] call_end_reason is 1
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:20:01:527] call_end_reason_type is 2
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:20:01:527] call_end_reason_verbose is 210
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:20:01:527] try to requestSetupDataCall 60 second later
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:21:01:579] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:21:01:579] call_end_reason is 1
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:21:01:579] call_end_reason_type is 2
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:21:01:579] call_end_reason_verbose is 210
Thu Aug 29 12:21:01 2024 daemon.notice netifd: modem_0001 (11964): [08-29_12:21:01:579] try to requestSetupDataCall 60 second later
Thu Aug 29 12:22:00 2024 cron.err crond[4331]: USER root pid 24551 cmd . /lib/functions/modem.sh;check_ip
Thu Aug 29 12:22:00 2024 cron.err crond[4331]: USER root pid 24552 cmd sleep 30;. /lib/functions/modem.sh;check_ip
Thu Aug 29 12:22:00 2024 cron.err crond[4331]: USER root pid 24553 cmd . /lib/functions/modem.sh;modem_net_monitor
Thu Aug 29 12:23:00 2024 cron.err crond[4331]: USER root pid 27551 cmd . /lib/functions/modem.sh;check_ip
Thu Aug 29 12:23:00 2024 cron.err crond[4331]: USER root pid 27552 cmd sleep 30;. /lib/functions/modem.sh;check_ip
If you can suggest me some AT commands to try when it disconnects, I will try them.
@Max3 it happens also with me on a vanilla openwrt. While when I was running GL firmware 4.4.8, it never disconnected.
It seems to be an intrinsic issue within Quectel module, however in firmware 4.4.8 it was corrected by running custom cron jobs.
That appears to be the same issue reported here, in June: Spitz AX Modem going offline
call_end_reason is 1
call_end_reason_type is 2
call_end_reason_verbose is 210
Reason 210 maps to PDN IPv6 call disallowed based on the error codes here: https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/blob/main/src/libqmi-glib/qmi-enums-wds.h
Well, I've just discovered that yes, it doesn't disconnect with 4.4.8 (with modem firmware RM520NGLAAR03A03M4G_01.201.01.201) but insted of disconnecting I lose carrier band aggregation after 2-3 days. Weird.
Now I am on 4.4.9 and I decided to try the new RM520NGLAAR03A04M4G_01.202.01.202 (https://github.com/4IceG/RM520N-GL).
I think that SpitzAX3000 is right, it's most probably a problem with the modem firmware since I had absolutely none of these problems before upgrading to RM520NGLAAR03A03M4G_01.201.01.201.
I did install this newest version last night and unfortunately my connection was disrupted today. Again I am running a vanilla OpebWrt. So it had nothing to do with GL firmware.
The problem is once you flash Quectel with version A07 you can’t go to older ones.
Yep I know sadly.
That's a shame. Anyway, since RM520NGLAAR03A03M4G_01.201.01.201. has become the suggested modem firmware, I think GL.iNet should look on this problem ASAP.
Man, I really love my Spitz AX but the amount of problems/bugs since the beta testing is really a nightmare with this unit...
hello
Have you upgraded to 4.4.9?
Can I see it remotely?
I am trying to solve this problem, but we can not reproduce it here
so,I need your help
Yes, I am on 4.4.9 now and so far it's working, I am waiting for the problem to arise again.
Anyway I've enabled GoodCloud, I will PM you so you can see it remotely, thanks.
Same issue here. The router randomly lose cellular connection.
I have the following version.
Modem: RM520NGLAAR03A03M4G
Current Firmware
Version: 4.0
Firmware Type: 0409release3
I disabled mulit-wan, and diasbled Internet Status Tracking, too. I attached relevant log messages.
The command worked for me.
I am on Digicel Network in Guyana.
Where I am located I only get 3G WCDMA signal.
I upgraded to the RM520NGLAAR03A03M4G firmware yesterday,
VERSION .201
