nRF9160 modem: AT+COPS=? does not work with SIM inserted

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Bjorn191023 — Fri, 25 Oct 2019 11:16:24 GMT

Thanks a lot Håkon, I will try to implement something like this

BR / Björn

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Håkon Alseth — Fri, 25 Oct 2019 11:03:04 GMT

Hi Björn,

[quote user="Bjorn191023"]What is meant by "an active radio connection"? [/quote]

If you start the search, then get an ATTACH to the network mid-COPS=?, that would be an active radio connection, or the application starts connecting to a mqtt broker for instance (ie: high throughput on IP). If you wait until the connection is attached (watch AT+CEREG? to see status, if application is connecting to a server, wait until that if finished as well), then issue COPS=?, you should be able to successfully discover other networks.

Kind regards,

Håkon

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Bjorn191023 — Thu, 24 Oct 2019 09:36:32 GMT

Hi Håkon,

Thanks for your response.

How can I find out when the network attachment is done and it is safe to scan for operators without being interrupted? The required state is not clear from the documentation.

Another question: the link you sent states the following: "The command fails if the device has an active radio connection. It returns ERROR or +CME ERROR: 516"

What is meant by "an active radio connection"?

BR / Björn

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Håkon Alseth — Thu, 24 Oct 2019 07:52:08 GMT

Its likely interrupted because you are, mid-process of COPS=?, attaching to your network, which will give an incomplete list back, as per the documentation:

https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cops_test.html?cp=2_1_6_0_2

As mentioned, I also got an error once while continuously resetting in between tests.

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Bjorn191023 — Wed, 23 Oct 2019 13:06:42 GMT

Hi,

Yes, it is consistent after cold start. The cold start (restart) of Thingy91 is important, otherwise the modem state is retained.

As I stated I can get it to work with SIM after a number of attempts (often three attempts) without cold start in between. Also selecting another operator manually (e.g. Tele2 instead of Telia) makes the command work. When it starts working it continues to work.

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Håkon Alseth — Wed, 23 Oct 2019 12:58:03 GMT

Hi,

I was able to successfully discover on both M1:

AT+COPS=?
+COPS: (2,"","","24201",7)
OK

And NB1:

AT+COPS=?
+COPS: (1,"","","24201",9),(3,"","","24202",9)
OK

I also locked the band to 20, and repeated with and without SIM card, and got the same responses.

I was able to get the "ERROR" response once (which can come if there's network disruptions), and running COPS=? again provided a list. You can try waiting till the link is up, and see if this has an impact. Is this behavior consistent on your side? ie: do you always get "ERROR" back?

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Bjorn191023 — Wed, 23 Oct 2019 12:05:11 GMT

Hi Håkon,

Thanks for your prompt response.

Yes, I have noticed that LTE Link Monitor times out very fast and that the command continues. It is not that timeout I am refering to. I get an actual "ERROR" response from the modem after ~ 1 minute.

We have narrowed scan to one band (20) to reduce the scan time. Without a SIM it takes around 5 seconds to get a proper response.

We are using LTE-M mode.

So I have already tested what you request.

RE: nRF9160 modem: AT+COPS=? does not work with SIM inserted

Håkon Alseth — Wed, 23 Oct 2019 11:59:46 GMT

Hi,

The AT+COPS=? command will take several minutes, especially on NB1, to return with the carriers in your area.

Even if the LTE Link Monitor times out, the command is executed and you'll have to wait for 2-to-10 minutes (depending on M1 or NB1), before it returns with the discovered list.

Could you try submitting the command only once, and wait for ~10 minutes to see if you get a response?

Kind regards,

Håkon