Constantly Loosing Cellular Connection on Spitz x3000

Technical Support for Routers
41

I actually use tower lock to lock to a particular N41 in my area. I have 3 N41 towers around me and 1 of them is consistently fast (even during peak times), so I just lock to that tower. It hasn’t dropped the tower connection yet.

If I enable all bands for 5G SA, then it will connect to 5G SA with 2CA, usually n71+n41 or n25+n41. The issue with this is that n41 under 2CA is always SCC for me (I prefer having n41 as PCC). When I tower lock to n41, then n41 will always be PCC.

I don’t use 5G NSA due to packet loss - my LTE signals are weaker than 5G, so I just stick with 5G SA.

The RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25) firmware works fine for me with a TMO phone SIM (Magenta, not TMHI), so I don’t need ROW_Generic_3GPP_PTCRB_GCF. My Wifi calling works fine too, so I’m not sure why you are having issues - maybe because you are on a business line?

42

What’s the AT command that forces 5G SA?

43

AT+QNWPREFCFG="nr5g_disable_mode,2

44

So (still havent done anything other than disable the speed boost thing as thats all i couldnt figure out how to do).
I should upgrade to ( RM520NGLAAR01A08M4G_01.202.01.202)
from what im currently on (RM520NGLAAR01 A07M4G_01.201.01.201)?

And i do not understand how to accomplish that with
(FILE=RM520NGLAAR01A08M4G_01.202.01.202
scp -O ~/Downloads/$FILE.zip root@192.168.8.1:/$FILE.zip)
Im on win 10… So not a mac. I dont understand where that command is supposed to be executed or how excatly.

Then run those commands whenever i figure out how to SSH properly into it? Am i running the commands in the window that SSH from Putty pops up? Or is that just to login and then i launch qfirehose which i cannot find a link for?

After doing all this do i do any thing else?

45

I found RM520NGLAAR01A08M4G_01.202.01.202 on the download page. To confirm its the first firmware choice from 2-1-24 correct?
I also notice the qfirehose program on there… But Its only for linux… I do not have linux

46

I think you need to read this document first

47

I have, and its confusing again… Now this is saying to downgrade or use some other firmware? And Again i dont have linux for qfirehose…
Everyone just hijacked my thread, and everything is mashed up and I cannot make sense of any of it. One gentleman said to do one thing, now your saying to do it another way with what appears to be the same firmware or older?
Im absolutly lost and confused.

48

AT+QNWPREFCFG=“mode_pref”,NR5G
AT+QNWPREFCFG=“nr5g_disable_mode”,2
I have actually added these two commands to my AT shortcuts dropdown. As well as many others.

49

When am i supposed to do that? Its not mentionted by either other guy who just replied… This is insane.

50

Can you use ssh to access the background of the router?

51

I haven’t done anything yet. Was trying to get a clear set of instructions and plan together so I know what I’m doing and was starting with what Aron Said but was confused. And with every post it’s escalated from there seemed simple enough to login with ssh and update to the newest firmware (waiting for confirmation I understood that right). But now seeing I have to download from that download repo qfirehouse but that’s for Linux which I’m not running. And then someone Said to read something else that says not to upgrade to that firmware but do something else. Then someone is saying to put in some modem AT command…

None of it makes sense as to what I’m supposed to do now… what should I do? What shouldn’t I do? What goes first? What goes last? How am I supposed to do this without running Linux? Why am I putting in ATT commands first or is that last!!!

52

Can we use anydesk? I’ll update your module firmware remotely

53

Does disconnection here refer to packet loss?

54

I have discovered that there is now a new R03A03_01.201.01.201 firmware out there that might be of interest. I still have not gotten a good answer as to what the difference is between R01A08 and R03A03 firmware. There has been a lot of work on my local towers as of late. I disabled the MBN ROW_Generic profile that I was using and switched back to the default Commercial-TMO profile. To my surprise, WiFi calling now works under that MBN profile! It never did before so whatever they did to the towers in my area has been an improvement. So, I will just continue to use the Commercial-TMO profile from now on. You must be closer to your tower than me. I get the best speeds when using n71 only. n71+n41 results in much slower speeds for some reason. I have tried band locking but I am so far from tower that band locking usually results in a total disconnect from the tower and zero cellular service. Then I need to reboot the router.
There are so many variations of SIM plans and tower locations for each user that it’s nearly impossible to have a one size fits all setting for this. I can see why people get frustrated with this router. Especially if they don’t have the technical skill to “tweak” their device.
Thank You for your input on this threads topic. It’s helpful to see what works and what doesn’t work for different users. Are you using a TTL of 65 in your cellular settings? If I don’t use TTL=65 I start using my HotSpot data. Just wondering if its the same for you on your SIM. I’ve set up 3 other x3000 devices for friends but they use the SIM from their TMHI device and that does not require the TTL=65 setting.

55

Httping would fail 10+ times which result in failover to my backup internet when I was on RM520NGLAAR01A08M4G_01.202.01.202 (2024-02-01). I no longer get the issue when I change firmware to RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25).

56

My TTL is 64 on x3000.

I checked the release notes for RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28) and nothing drew my attention, so I will stay on RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25) for now.

I have no disconnection issues with RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25). The router has been up and running for days now (no httping failures and no failovers to my backup internet as I have multiwan enabled).

Release notes for RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28):

image
image1514×687 49 KB

image
image1254×1344 177 KB

1 Like
57

Can you share the device to goodcloud? Can you share the device to Goodcloud?
I want to grab a log remotely and send it to quectel for analysis

58

@Will12345

I disabled the AT command that I used to enable WiFi calling on R01A08 (2024-02-01) and WiFi calling still worked. So I thought that maybe I too would be able to try R03A03 release. However, when I woke the next morning, I could not make a phone call and WiFi calling was no longer enabled on my phone. So unfortunately, I will have to stick with using R01A08 and the “ROW_Generic_3GPP_PTCRB_GCF” MBN file over the “Commercial-TMO“ one.

I believe that n71 does not allow me to use WiFi calling but n41 does, so it just depends which band my router is on. n71 is the fastest band for me and n41 is extremely slow. The R01A08 firmware has worked extremely well for me and I have not had any reboots like I had previously. I’ll be moved in the RV in a months time and I’m certain that everything will need to be re-tweaked all over again once I connect to a different tower and new location. But for now, I’m happy to not have to reset the router multiple times a day.
In either case, I think we are in agreement that the default modem firmware needs to be upgraded right away for anyone wanting a more stable experience.

59

This is the version we want to upgrade in the future

60

I decided to try out RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28) to see if it contains ROW_Generic_3GPP_PTCRB_GCF since I use both TMO and VERIZON. I don’t need it now since both SIM cards seem to connect fine, but just in case.

On RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28), I ran AT+QMBNCFG=“list” and see ROW_Generic_3GPP_PTCRB_GCF was added there.

+QMBNCFG: "List",0,1,1,"Commercial-TMO",0x0A01050F,202402061
+QMBNCFG: "List",1,0,0,"CDMAless-Verizon",0x0A010126,202304251
+QMBNCFG: "List",2,0,0,"ROW_Generic_3GPP_PTCRB_GCF",0x0A01FF09,202203161
+QMBNCFG: "List",3,0,0,"TEF_Spain_Commercial",0x0A010C00,202302071
+QMBNCFG: "List",4,0,0,"FirstNet",0x0A015300,202206171
+QMBNCFG: "List",5,0,0,"Rogers_Canada",0x0A014800,202303141
+QMBNCFG: "List",6,0,0,"Bell_Canada",0x0A014700,202111051
+QMBNCFG: "List",7,0,0,"Telus_Jasper_Canada",0x0A01F900,202304281
+QMBNCFG: "List",8,0,0,"Telus_Consumer_Canada",0x0A01FA00,202304281
+QMBNCFG: "List",9,0,0,"Commercial-Sprint",0x0A010204,202111051
+QMBNCFG: "List",10,0,0,"VoLTE-ATT",0x0A010335,202206171
+QMBNCFG: "List",11,0,0,"CDMAless_Private-Verizon",0x0A01FD28,202304271
+QMBNCFG: "List",12,0,0,"Swiss-Comm",0x0A010411,202304261
+QMBNCFG: "List",13,0,0,"Telia_Sweden",0x0A012400,202111051
+QMBNCFG: "List",14,0,0,"TIM_Italy_Commercial",0x0A012B00,202111051
+QMBNCFG: "List",15,0,0,"France-Commercial-Orange",0x0A010B21,202401081
+QMBNCFG: "List",16,0,0,"Commercial-DT-VOLTE",0x0A011F1F,202212061
+QMBNCFG: "List",17,0,0,"Germany-VoLTE-Vodafone",0x0A010449,202401201
+QMBNCFG: "List",18,0,0,"UK-VoLTE-Vodafone",0x0A010426,202401201
+QMBNCFG: "List",19,0,0,"Commercial-EE",0x0A01220B,202111051
+QMBNCFG: "List",20,0,0,"Optus_Australia_Commercial",0x0A014400,202111051
+QMBNCFG: "List",21,0,0,"Telstra_Australia_Commercial",0x0A010F00,202311071
+QMBNCFG: "List",22,0,0,"Commercial-LGU",0x0A012608,202111051
+QMBNCFG: "List",23,0,0,"Commercial-KT",0x0A01280B,202308031
+QMBNCFG: "List",24,0,0,"Commercial-SKT",0x0A01270A,202111051
+QMBNCFG: "List",25,0,0,"Commercial-Reliance",0x0A011B0C,202210211
+QMBNCFG: "List",26,0,0,"Commercial-SBM",0x0A011C0B,202401231
+QMBNCFG: "List",27,0,0,"Commercial-KDDI",0x0A010709,202401191
+QMBNCFG: "List",28,0,0,"Commercial-DCM",0x0A010D0D,202312201
+QMBNCFG: "List",29,0,0,"VoLTE-CU",0x0A011561,202310181
+QMBNCFG: "List",30,0,0,"VoLTE_OPNMKT_CT",0x0A0113E0,202312141
+QMBNCFG: "List",31,0,0,"Volte_OpenMkt-Commercial-CMCC",0x0A012010,202209221
+QMBNCFG: "List",32,0,0,"ROW_Commercial",0x0A010809,202401151

So far RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28) seems as stable as RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25) with regards to tower connection on TMO US.