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

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

plotkin1996 — Fri, 20 Sep 2024 07:39:08 GMT

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…

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

Charlie — Thu, 19 Sep 2024 11:14:18 GMT

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

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

Charlie — Thu, 19 Sep 2024 10:24:22 GMT

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