nrf9160 not able to connect to Bands other than 12

RE: nrf9160 not able to connect to Bands other than 12

Håkon Alseth — Fri, 29 Oct 2021 14:30:03 GMT

Hi,

Are you sure that LTE M (or NB1) is available on other bands in your area?

Do you get connected on other bands with a nRF9160-DK/thingy91 for instance?

If you lock the bands to the other band, then do a manual search using AT+COPS=? it should return any network it finds. If it does not find any, it's highly likely not available in your area.

Kind regards,

Håkon

RE: nrf9160 not able to connect to Bands other than 12

Stratosphere — Mon, 25 Oct 2021 23:52:19 GMT

Hi Haken,

After many tests I am still unable to connect to any band other than Band 12.

Band 12 connects right away but other bands just do not work.

I tried on Thingy91 with AT Client example and At LInk Monitor.

I have tried using BandLock command and it is working as I can see the Bands update on the GUI as well as when I send out AT%XBANDLOCK?

I have tried manually sending the MAGPIO command to set different different band settings as well but all without success.

At this point, I can safely say that the device just won't connect to any Bands other than 12.

Are you aware of any such behavior in Canada?

RE: nrf9160 not able to connect to Bands other than 12

helsing — Tue, 05 Oct 2021 13:32:50 GMT

Hi Noaman,

[quote user="Stratosphere"]after updating my code[/quote]

What changes did you make? Which sample are you building? And which board are you building for?

[quote user="Stratosphere"]Can let me know what line is that I need to add to configure the MAGPIO on thingy91?[/quote]

MAGPIO is set automatically when you are building for Thingy:91. If you want to use Band 4 at 850MHz, then the correct MAGPIO pins will be changed automatically whenever that frequency is in use. Here is how MAGPIO is configured automatically:

In the file board_nonsecure.c, located in v1.7.0/nrf/boards/arm/thingy91_nrf9160/, you will find the following.

#define AT_CMD_MAGPIO "AT%XMAGPIO=1,1,1,7,1,746,803,2,698,748," \

"2,1710,2200,3,824,894,4,880,960,5,791,849," \

"7,1565,1586"

The command is given to the modem at startup.

The setup corresponds more or less with Thingy:91 User Guide, section 5.3.1. Antenna tuning. The configuration is, as you say, set up with MAGPIO configuration %XMAGPIO and the MAGPIO set command.

Please let me know if you would like to make changes to the settings, and I will look up exactly how this is done. I think the way to do this is something like adding the below configs to prj.conf but I have not tested this myself:

CONFIG_NRF9160_GPS_SET_MAGPIO=y
CONFIG_NRF9160_GPS_MAGPIO_STRING="AT%XMAGPIO=1,1,1,7,1,746,803,2,698,748,2,1710,2200,3,824,894,4,880,960,5,791,849,7,1565,1586"

Best regards,

Håkon

RE: nrf9160 not able to connect to Bands other than 12

Stratosphere — Sun, 19 Sep 2021 21:17:01 GMT

Hi Hakan,

Thanks for your response.

1. I will check the log again and get back to you tomorrow about what I see after XBANDLOCK. When i try the band lock on Band 12, everything works well. Setting it to any other band is where LTE Connection is not established.

2. We have almost 20 devices in the field. They all submit band information and they all run band 12. I have on a couple of occassions seens devices connect to band 4 but that is 1 in a 100 occurance. This is without any bandlock.

3. Yes, I was trying band 13 in line 5 instead of band 12 just as one of the tests.

4. I will try the proj.conf settins as you suggested and get back to you tomorrow.

5. I have not tried it using at_client.

I just purchased a thingy91 and I was trying this XBAND code on their. The asset tracker example was working out of the box but after updating my code, it does not connect to any bands at all. I remember seeing somewhere about adding a MAGPIO config line in the code to properly configure the active tuner but I can't find that now. Can let me know what line is that I need to add to configure the MAGPIO on thingy91? This test should let me compare Antenna performance on various bands between thingy91 and our board and possibly indicate/elimiate any hardware issues

Regards

Noaman

RE: nrf9160 not able to connect to Bands other than 12

helsing — Thu, 16 Sep 2021 12:39:18 GMT

Thank you for your reply.

What do you currently see in the log after XBANDLOCK?

Could you please confirm that you are setting the band lock before activating modem with +CFUN? I assume, however, that you would have seen an error if you tried the opposite order.

How do you currently verify which band is working? Something to try is to activate the modem without using XBANDLOCK, and then use XCBAND to check the active bands(XCBAND works only after the modem is activated).

Looking at line 5 of the code you posted: Are you selecting band 13(and not band 12) on purpose? Is that in order to make band 12 unavailable?

An alternative to XBANDLOCK is to update your prj.conf with the following configs:

CONFIG_LTE_LOCK_BANDS and CONFIG_LTE_LOCK_BAND_MASK, for example like this:

CONFIG_LTE_LOCK_BANDS=y

CONFIG_LTE_LOCK_BAND_MASK="00000000000000000010"

Have you tried using XBANDLOCK with the at_client sample?

RE: nrf9160 not able to connect to Bands other than 12

Stratosphere — Mon, 13 Sep 2021 05:30:57 GMT

Hi Haken,

I have band 2 and 12 available for sure as confirmed by bell tech support.

I do not have a telus SIM. our current contract is with bell.

RE: nrf9160 not able to connect to Bands other than 12

helsing — Thu, 09 Sep 2021 11:14:22 GMT

Hi Noaman,

Your use of XBANDLOCK looks like it should be OK. After using the command, are you seeing 'OK' or some error in the log output?

Do you have any SIM card from Telus that you could try? Telus seems to have B4, B5 and B12 active in Canada. However, I do not know which bands are available in the Toronto area.

Best regards,

Håkon

RE: nrf9160 not able to connect to Bands other than 12

helsing — Wed, 08 Sep 2021 20:31:23 GMT

Hi Noaman,

Do you know which bands are available in your area?

I am checking with our team to see if we have any overview over how Toronto is covered.

Best regards,

Håkon