Initiation problem on Vodafone with NB-IoT from nrf9160-DK

RE: Initiation problem on Vodafone with NB-IoT from nrf9160-DK

paul_tanner — Fri, 18 Dec 2020 17:30:11 GMT

We verified this by disabling the FOTA stuff. We're using the latest FW. I guess we could restore these changes if the Vodafone Eval Pack allows two endpoints. Not sure it does though.

RE: Initiation problem on Vodafone with NB-IoT from nrf9160-DK

paul_tanner — Wed, 16 Dec 2020 19:03:56 GMT

I guess this application has a lot of dependencies on the nrfCloud functionality which the Vodafone platform does not support. Reducing the use of those functions in the asset_tracker application might be one option?

RE: Initiation problem on Vodafone with NB-IoT from nrf9160-DK

Håkon Alseth — Mon, 14 Dec 2020 14:57:41 GMT

Hi,

In addition to Lukáš's response:

Which modem fw are you using?

Could you ensure that you have the latest (v1.2.2 at the time of writing this response) and see if this improves the scenario?

NB1 is a slower transport compared to LTE-M, which is the reason why TCP-based protocols on this transport might not always work (timeout's occur in the 3-way TCP sequence), but you can also try the mqtt_simple sample to see if this also behaves similarly.

Kind regards,

Håkon

RE: Initiation problem on Vodafone with NB-IoT from nrf9160-DK

Lukáš — Sat, 12 Dec 2020 09:45:14 GMT

If you are running Vodafone Evaluation Pack, then you have just a set of two particular IP adresses whitelisted. I guess you didn't whitelist the one for nRF Cloud.