EM160R-GL

[JoshKelly]

Is it possible to completely reset one of these modems?

I would like to upgrade to the latest firmware for the modem, then reset everything to factory and then make sure all the setting are changed for ATT.

If so can someone help me with resetting mine and then help me make sure all the settings are correct on it for an ATT post paid plan?

I have had nothing but problems with my EM160 and WG1608 (v1). I am leaning towards a problem with the modem just because I can flash different versions of GO and get drastically different results. Currently I get the best results with GO based on 18.0x. All the never versions cut my speeds in half. The problems I am having with my 18.0x version is about 2-3 times a week I have to do a reset because it disconnects lte.

Just wanted to try this before dropping money on a RP4 compute, TOFU carrier board and a POE hat.

[Didneywhorl]

Use the command

Code: Select all

AT+QPRTPARA=3

When your modem comes back, use the command:

Code: Select all

AT+QPRTPARA=1

Done. Factory reset modem.

Not real healthy to do to the modem very often, so be conservative. It's usually best to track the settings you made and undo them if needed.

[JoshKelly]

Use the command

Code: Select all

AT+QPRTPARA=3

When your modem comes back, use the command:

Code: Select all

AT+QPRTPARA=1

Done. Factory reset modem.

Not real healthy to do to the modem very often, so be conservative. It's usually best to track the settings you made and undo them if needed.

Thank you so much! I will do this once and see if problems are solved. Are there any settings I need to make sure to change specifically for At&t. I don't band lock but it definitely would be nice if I could set band priorities. For example, if I can get my modem to connect to band 66 and ca 14 & 2 I get much faster speeds than if it connects to band 14 and ca 2 (which is what it likes to do most of the time). On another note, the tower I connect to is supposed to be capable of 66-66-2-2 or 66-66-14. I think both of these would result in much greater speeds, I have just not been able to get it to connect this way.

Also is there a way to make the router auto-reconnect the modem if the LTE signal is lost? There are times when it will be connected to W??? I think and this results in less than 5mbs speeds. A reset of the modem normally fixes this.

Josh

[Didneywhorl]

Look into how to use the command AT+QNWLOCK

This will lock the modem to a specific radio (band) on a specific tower, but still allow CA with other bands on that tower. I've honestly never used it so I'm not the expert on the command. I just know of the command.

If you are using WiFiX firmware, try using the The Wireless Haven / Custom Ping test. I think its under Modem menu. Not the one in the Modem Connection Profiles page. This one has a web page load option (curl) instead of ping testing. Then you can choose to reboot the modem or the router or both.... I think.

[JoshKelly]

Look into how to use the command AT+QNWLOCK

This will lock the modem to a specific radio (band) on a specific tower, but still allow CA with other bands on that tower. I've honestly never used it so I'm not the expert on the command. I just know of the command.

If you are using WiFiX firmware, try using the The Wireless Haven / Custom Ping test. I think its under Modem menu. Not the one in the Modem Connection Profiles page. This one has a web page load option (curl) instead of ping testing. Then you can choose to reboot the modem or the router or both.... I think.

Thank you so much! Starting to mess with the AT+QNWLOCK today. I think my GO firmware might be too old for the ping test because I cannot find it in any of the menus

[JoshKelly]

So I have messed around with AT+QNWLOCK today with no luck.

When I issue:

AT+QNWLOCK=?
+QNWLOCK: "common/4g",<num of cells>,[[<freq>,<pci>],...]
+QNWLOCK: "common/lte"[,<action>[,<EARFCN>,<PCI>[,<status>]]]

AT+QENG="neighbourcell"
+QENG: "neighbourcell intra","LTE",67086,164,-9,-77,-49,0,-,-,-,-,-
+QENG: "neighbourcell intra","LTE",67086,456,-15,-83,-59,0,-,-,-,-,-
+QENG: "neighbourcell intra","LTE",67086,79,-19,-90,-59,0,-,-,-,-,-
+QENG: "neighbourcell inter","LTE",9840,164,-12,-91,-70,0,-,-,-,-
+QENG: "neighbourcell inter","LTE",5145,164,-11,-79,-58,0,-,-,-,-
+QENG: "neighbourcell inter","LTE",5145,456,-11,-78,-58,0,-,-,-,-
+QENG: "neighbourcell inter","LTE",5330,79,-8,-70,-53,0,-,-,-,-
+QENG: "neighbourcell inter","LTE",5330,456,-19,-83,-53,0,-,-,-,-

AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","LTE","FDD",310,410,70CDE17,164,67086,66,3,3,6201,-77,-11,-46,18,-

Looking at cell mapper there are three band 66 available on the tower, I don't think it maters which:
PCI 164 (looks like this is what I connect to regularly)
PCI 202
PCI 335


My problem is with the AT syntax, I just don't know how to put together the AT command.

I'd like to QNWLOCK to band 66 on this tower and let it CA with whatever it wants.

Also is there a way to make this stuck after a reboot?

[Didneywhorl]

Give us an example of a failed/errored AT command that you tried. Maybe a few.

[JoshKelly]

Give us an example of a failed/errored AT command that you tried. Maybe a few.

Here is what I tried, they all error out or time out:

AT+QNWLOCK="common/4g",1,410,310
AT+QNWLOCK="common/4g",1,310,410

AT+QNWLOCK="common/LTE",1,410,310
AT+QNWLOCK="common/LTE",1,310,410

[mtl26637]

Your frequency and pci are incorrect. For instance, take a look at your 'servingcell' output. The frequency would be '67086' and your pci is '164'. Also, if you lock to 1 band then no CA. you would need to lock to all that you 'may' use in CA. I've played with locking and things didn't go as well as letiing the tower do it own thing and ended up moving back to auto selection for best results. But can be fun to play with to see what the possibilities are. Also tower will only do certain combo's of CA so when you lock then you may be locking out certain CA combinations unless you know exactly what CA combo's the tower will allow.

[Didneywhorl]

Give us an example of a failed/errored AT command that you tried. Maybe a few.

Here is what I tried, they all error out or time out:

AT+QNWLOCK="common/4g",1,410,310
AT+QNWLOCK="common/4g",1,310,410

AT+QNWLOCK="common/LTE",1,410,310
AT+QNWLOCK="common/LTE",1,310,410

Did you try the recommendations from Josh?