This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

AGPS startup via NB-IoT on nrf9160-DK

I took the APGS example and switched in to NB-IoT as I can't easily test with LTE/M at the moment

2021-03-15T16:25:39.226Z DEBUG modem << I: A-GPS sample has started
2021-03-15T16:25:39.246Z DEBUG modem << I: Connecting to LTE network. This may take minutes.
2021-03-15T16:25:39.249Z DEBUG modem << I: PSM mode requested
2021-03-15T16:25:42.194Z DEBUG modem << +CEREG: 2,"1BE8","00334D15",9,0,0,"11100000","11100000"
2021-03-15T16:25:42.900Z DEBUG modem << +CSCON: 1
2021-03-15T16:25:45.571Z DEBUG modem << +CEREG: 5,"1BE8","00334D15",9,,,"00000010","00011111"
2021-03-15T16:25:45.605Z DEBUG modem << I: Connected to LTE network
2021-03-15T16:25:45.606Z DEBUG modem << D: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1565,1586
2021-03-15T16:25:45.607Z DEBUG modem << D: COEX0 set: AT%XCOEX0=1,1,1565,1586
2021-03-15T16:25:45.610Z DEBUG modem << D: GPS socket created, fd: 1232491587
2021-03-15T16:25:45.611Z DEBUG modem << I: CLOUD_EVT_CONNECTING
2021-03-15T16:25:46.400Z DEBUG modem << I: CLOUD_EVT_CONNECTING

I tried this a few times and waiting several minutes in each case. No more output seen.
Are there other things I need to change? apart from:


#CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

Suggestions welcome. Thx.
Parents Reply
  • Hi Paul, 

    Yes, this may cause a connection issue as Legacy Protocol Configuration Options (PCO) is an older protocol compared to extended Protocol Configuration Options (ePCO), and intended for NB-IoT

    The Digital Matter blog https://www.digitalmatter.com/nb-iot-update-pco-support/ has a good explanation:

    Device manufacturers, module manufacturers, and networks all need to quickly adapt when deploying new networks. In the case of NB-IoT, not every network has got it right first try.

    The 3GPP standard (standard specification for mobile networks globally) specifies that NB-IoT networks support ePCO (extended protocol configuration options).

    Many networks globally instead offer PCO. When a device attempts to connect expecting ePCO, it will not be able to get online. The two messages are different, so the device and the network don’t understand each other properly.

    Did you try to remove this configuration?

    Kind regards,
    Øyvind

Children
Related