• State Not Answered
  • Replies 13 replies
  • Subscribers 74 subscribers
  • Views 2849 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 284799
Options

Asset_tracker_v2 problem: Failed to set legacy PCO mode

Varinia Cabrera

Hello,

I am very new at this. I have just started to work with the nrf9160DK board, I am using modem firmware 1.3.1, and nRF Connect SDK 1.8.0. I am trying to test asset_tracker_v2 application to connect the board to nrfcloud. Some changes are needed because I am in Uruguay (South America) so I must use NB-IoT, with Legacy PCO (ePCO is not supported).

I used menuconfig in order to modify .config (and I attached a .config file). Some modification are: CONFIG_LTE_MODE_PREFERENCE_NBIOT, CONFIG_LTE_NETWORK_MODE_NBIOT_GPS (for NB-IoT and GNSS), CONFIG_PDN_LEGACY_PCO (for legacy PCO), CONFIG_PDN_DEFAULT_FAM_IPV6 (PDN uses IPv6), CONFIG_LTE_LOCK_BANDS, CONFIG_LTE_LOCK_BAND_MASK  (using certain bands), CONFIG_LTE_LOCK_PLMN, CONFIG_LTE_LOCK_PLMN_STRING (selecting Uruguayan network). Also, based on another ticket from Nordic, CONFIG_MODEM_JWT was modified  and CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID was selected.

LTE connection is achieved, however, nrfcloud connection fails. After booting the DK board, the following warning appears: pdn: Failed to set legacy PCO mode, err 65536 and then cloud connection is not possible. So I tried AT%XEPCO? and the answer is 1 but I had expected a 0 (Legacy PCO), it is like CONFIG_PDN_LEGACY_PCO=y is not working. If I turn off the modem and send AT%XEPCO=0, when cloud connection is attempted the following error appears: nrf_cloud_transport: MQTT input error: -128.  

First question is how to correctly set the legacy PCO mode. And secondly, how could I fix the MQTT connection.
Thanks a lot, 
I apologize if I was not clear or if any information is missing.
Varinia Cabrera
Parents
  • 0

    Hello,

    I'm not sure what the reason for this is, but if you give me some time I can try to reproduce it.

  • 0 in reply to Hakon

    Hello, I would be grateful If you could find out what kind of issue it is.

    It is relevant to mention that with serial_lte_modem and AT command I achieved a successful MQTT connection.

    However, I have tried other samples and application examples (serial_lte_modem, mqtt_simple) with similar modifications as the asset_tracker_v2 in their .config in order to achieve an automatic MQTT connection (instead of using AT commands). Same warning appears and nothing works.

    After that, I realized it might be a problem with PDN (packet domain network) so I started working with the pdn sample and the same warning appeared.

    Feel free to ask any other information needed.

    Thanks in advance,

    Varinia Cabrera

Reply
  • 0 in reply to Hakon

    Hello, I would be grateful If you could find out what kind of issue it is.

    It is relevant to mention that with serial_lte_modem and AT command I achieved a successful MQTT connection.

    However, I have tried other samples and application examples (serial_lte_modem, mqtt_simple) with similar modifications as the asset_tracker_v2 in their .config in order to achieve an automatic MQTT connection (instead of using AT commands). Same warning appears and nothing works.

    After that, I realized it might be a problem with PDN (packet domain network) so I started working with the pdn sample and the same warning appeared.

    Feel free to ask any other information needed.

    Thanks in advance,

    Varinia Cabrera

Children
Related
Terms of service