Thingy:91 Pre-built hex and asset tracker program ?

[Nahan_Trogn]

Hi Nordic,

I just had Thingy:91 few days ago. I ran this KIT with thingy91_nbiot_2021-03-04_8e8c6089.hex  and asset_tracker example in ncs/nrf/applications. I found that the speed when the KIT recognized LTE and connect to network in pre-built hex is quicker than in asset_tracker example. Can you point out where I have to modify in asset_tracker example to get the connection faster?

Thanks in advance.

[Øyvind]

Hello, 

Can you please tell me what version of NCS you are using when building asset_tracker example in ncs/nrf/applications? Also, have you verified that the Asset Tracker is trying to connect to a NB-IoT network?

In prj.conf

CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=n

CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

Kind regards,
Øyvind

[Nahan_Trogn]

Hi,

I use NCS v0.1.5, on Ubuntu. My prj.conf has some differences from yours:

And my additional question: How to know which power mode does my thingy91 run? (PSM, eDRX or Demo mode)?
Thanks in advance.

[Øyvind]

Hi,

Nahan_Trogn said:

My prj.conf has some differences from yours:

No, this is the same as mine, but I have only included the needed configurations for LTE-M vs NB-IoT to show what you need to change. Your prj.conf is configured to connect to LTE-M, and this will leave it trying to connect to wrong network for a while, before it falls back to NB-IoT and successfully connects. This should be visible in your debug output e.g. LTE Link Monitor.

 

Nahan_Trogn said:

How to know which power mode does my thingy91 run? (PSM, eDRX or Demo mode)?

 This is also output in debug output. E.g. the AT command CEREG will provide network information

As you are new to the world of Thingy:91, I suggest reading through our NCS documentation, especially Working with Thingy:91, and also have a look at our nRF Connect SDK Tutorial.

Kind regards,
Øyvind

[Nahan_Trogn]

Thanks for your informative support. Many thanks.

[Øyvind]

You're welcome