I have tried to do speed tests multiple times per day since my last post 10 days ago. I have attached a spreadsheet that contains the results. However, for the most part the router has been pretty stable and the speeds have been fast enough to stream. There were a couple of times it slowed down but I intentionally did not reboot to see what would happen. So it has not been rebooted in over 10 days.
Thank you for mentioning Disconnect. It’s been more or less stable for a little, but I finally lost Internet and had a chance to try it. Unfortunately, while much quicker, it doesn’t help at all. I have tried different delay intervals before re-connecting, and it always seems to reconnect at the seem speed and condition as before - whether barely providing Internet, or down to 0.0 both ways. Only a reboot restores full speed. By the way, the signal numbers are always ‘Excellent’, when the Internet is good and when it’s poor or non-existent.
Also, I was wrong in a couple of my observations - it can happen any day, not just weekdays, and it can happen with or without wireless usage.
I’ve checked the System Overview page when Internet service was down, and memory usage looks fine, and CPU usage is minimal - so not running out of memory or trapped in a loop.
1 Like
I really wish there was a way to edit posts. Invariably, even after triple checking I still find wrong words or awkward phrasing.
‘seem’ should be ‘same’
I’ve had this issue as well - Keeping the GL-X3000 running for more than 24 hours continuously causes random “stalls” and “pauses” in HTTP(S) requests. Pings work. But the whole network gets “paused” for up to one minute every hour for me.
I have a partner SIM card which is loaded on my phone, and it never runs into these stalling issues, so the cell tower or the network provider are definitely not the culprits here.
I tested and debugged this for 2 weeks to no avail. Finally just setup auto-restart once every day on the router to fix this problem. This is quite frustrating and should not be happening for a router this capable.
@RobJ Can we collect some modem log for better analysis?
Please share device to support via Goodcloud as per the above tutorial. If you have a USB drive, please insert it to the router. Thanks
Well, I was relatively trouble free for quite a while and a couple of days ago the data slowed to a trickle that was quickly fixed with a reboot. However, I did change locations by over one hundred miles. Is that why I had this latest issue? It has been solid since the reboot. Since we do move around quite a bit, should I reboot once we reach our next location?
Hi @Vettenuts sorry for the late response.
After your move, does the device need to be powered on again to connect to the network? If the device powers off and restarts, it will have the same effect as a manual reboot, so no additional manual restart is necessary.
To ensure the device operates normally, we recommend placing it in a well-ventilated area and adjusting the fan threshold to 70 ℃ in the system settings (SYSTEM ->Overview ->CPU Avarage Load) to try again.
Sorry Cathy, I probably should have explained better. The Spitz is installed in a motorhome. We made a major move of a few hundred miles and the reboot fixed it. Just went through it again last night as the result of another move in location. Reboot seems to have cleared it right up. I’m going to keep track of this phenomenon as we wil be make several moved over the next few weeks.
In the ongoing diagnostics of my XE3000, Cathy has apparently noted high temps, associated with the issues above. From her instructions and my observations:
- Adjust fan threshold down to 70
- Ensure all vent openings are clear, with good airflow
- Ensure no direct sun exposure
Mine was sitting on its front, blocking front vents, with a little sun exposure possible in the morning. I’ve adjusted its positioning so all vents have airflow, and placed a sheet of cardboard behind it, to block the sun. We’re now waiting to see if this resolves the issues. Unfortunately, my router often goes about 1 to 2 weeks between episodes, making this a slow process.
Our cellular modems and cellular routers have a potential issue normal routers do not, in that normal routers are placed well within buildings. Cellular routers are often placed in or near windows for optimal signal reception, possibly exposing them to the sun, or surfaces heated by the sun.
I suspect that, if necessary, a small fan on it might further improve its temps.
I found this post on Quectel forums claiming this (or a similar issue) happens if your modem has an R03 firmware. I was also on R03, as is the OP. Just flashed RM520NGLAAR01A08M4G_01.206.01.206 from here, and it’s working at the moment - I’ll see how it holds up.
github(dot)com/4IceG/RM520N-GL
I’ve been using RM520NGLAAR01A08M4G_01.206.01.206 for a couple weeks now and can confirm this fixed the problem for me. But I also see there’s a new version of R03 firmware that just came out (RM520NGLAAR03A03M4G_A0.304.A0.304). I might give that a try and revert if it’s still bugged.
304 still crapping out after a while, going back to 206. @Cathy - could you guys bring this up with Quectel? They might actually listen to you.
Thanks for the feedback. The version jump from R01 to R03 is significant, and Upgrading might lead to configuration incompatibility issues and cause network disconnection. For this reason, it's not recommended to upgrade from R01 to R03 previously.
We will report this to Quectel once more. I will send you a file via message—could you please assist in collecting the relevant information on R03 for analysis?