[NRF9160, NCS2.5.0 MFW1.3.5] AT%XPCO doesn't return any notification

[plotkin1996]

Hello,

I'm trying to access active PCO from nrf9160 applicaton to be able to diagnose problems like missing DNS, wrong access point etc. I tried using %XPCO command, AT%XPCO=1 returns ok, yet there is no notifications via AT monitor when the device attaches to a network. Tried it both on SLM and on our application. What am I doing wrong:

//Initialization
nrf_modem_at_printf("AT%%XPCO=1");

//Monitor

AT_MONITOR(sleet_pco, "%XPCO: ", pco_handler);
static void pco_handler(const char *notif) {
    LOG_ERR("PCO: %s\n", notif);
}

Otherwise, is there any other way to access PCO (and preferably rest of ESM message) short of full modem trace?

[Charlie]

Hi,

Thanks for checking with us.

To be honest, I have not found any use case or issue reports related to %XPCO command in DevZone by far. No sure if this will help on what you want to achieve.

Let me check with our modem developer to see how this %XPCO command should be used, I will return to you later.

Best regards,

Charlie

[Charlie]

Hi,

According to our development team, AT%XPCO command is implemented as part of Verizon requirements.

Based on code study, the only PCO container that is sent out as AT notifications is ESM_PCO_IE_VZW_ID 0xFF00. No more PCOs are supported from AT notification, so only PCAP generated from modem log has complete ESM messages.

Feel free to contact use if you need help to debug missing DNS, wrong access point etc issues.

Best regards,

Charlie

[plotkin1996]

Thank yoou, that makes sense. The problem is that we have sometimes had problems with devices in the field and there is no physical access nor enough flash to save traces the, so having a programmatic access to to PCO would have been nice…