Boron Not Connecting after AT&T Maintenance

I have a Boron running 1.5.2 that has been working flawlessly until the AT&T scheduled maintenance that recently occured. The device last connected successfully to Particle cloud on 9/1 at 4:10am. I have removed power from the device and tried resetting it. I also verified that my SIM card quota has not been reached. The device just produces a flashing green LED and never connects now. It is programmed to use SEMI-AUTOMATIC and NO threading. The connect code is below. Any ideas as to what may of happened during the scheduled maintenance?

The log does produce the following error now:
0000057764 [hal] ERROR: No response from NCP
0000111014 [hal] ERROR: No response from NCP
0000164264 [hal] ERROR: No response from NCP

  Log.info("Connecting to Particle Cloud...");
  Particle.connect(); //initiate connection to Particle cloud
  if (waitFor(Particle.connected, 2 * 60000)) {
    Log.info("Connected!");
    return 1;                           
  } else {
    Log.error("Unable to connect to Particle Cloud!");
    return 0;  
  }

If you consistently get “No response from NCP” you may have had a device failure, which was coincidentally at the same time as the maintenance, but not really related. You should contact support as you may be experiencing a known issue with the SARA-R410M-02-B in Boron LTE devices produced before October 2019.

Getting a cloud debug log may be helpful in diagnosing the issue.

Hey @rickkas7
I will contact support. I did run the Cloud debug and here is the output:

starting tests…
turning cellular on…
0000036004 [hal] ERROR: No response from NCP
0000036004 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
deviceID=************
manufacturer=
model=
firmware version=
ordering code=
IMEI=
IMSI=
ICCID=
0000117004 [app] INFO: enabling trace logging
0000117005 [ncp.at] TRACE: > AT+CGDCONT?
0000127005 [ncp.at] TRACE: > AT+CSQ
attempting to connect to the cellular network…
0000137007 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000137007 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000137009 [hal] TRACE: PPP netif -> 8
0000137009 [net.ifapi] INFO: Netif pp3 state UP
0000137009 [net.ifapi] INFO: Netif pp3 state UP
0000137011 [hal] TRACE: Powering modem on
0000137011 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000137011 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000137161 [hal] TRACE: Modem powered on
0000137162 [hal] TRACE: Setting UART voltage translator state 1
0000138163 [ncp.at] TRACE: > AT
0000139163 [ncp.at] TRACE: > AT
0000140163 [ncp.at] TRACE: > AT
0000141163 [ncp.at] TRACE: > AT
0000142163 [ncp.at] TRACE: > AT
0000143163 [ncp.at] TRACE: > AT
0000144163 [ncp.at] TRACE: > AT
0000145163 [ncp.at] TRACE: > AT
0000146163 [ncp.at] TRACE: > AT
0000147163 [ncp.at] TRACE: > AT
0000148163 [ncp.at] TRACE: > AT
0000149163 [ncp.at] TRACE: > AT
0000150163 [ncp.at] TRACE: > AT
0000151163 [ncp.at] TRACE: > AT
0000152163 [ncp.at] TRACE: > AT
0000153163 [ncp.at] TRACE: > AT
0000154163 [ncp.at] TRACE: > AT
0000155163 [ncp.at] TRACE: > AT
0000156163 [ncp.at] TRACE: > AT
0000157163 [ncp.at] TRACE: > AT
0000158163 [hal] ERROR: No response from NCP
0000158163 [hal] ERROR: No response from NCP
0000158164 [hal] TRACE: Setting UART voltage translator state 0
0000158165 [hal] TRACE: Hard resetting the modem
0000169165 [net.pppncp] TRACE: Failed to initialize ublox NCP client: -210
0000169166 [hal] TRACE: Setting UART voltage translator state 0
0000169166 [hal] TRACE: Modem already off
0000169267 [hal] TRACE: Powering modem on
0000169417 [hal] TRACE: Modem powered on
0000169418 [hal] TRACE: Setting UART voltage translator state 1
0000170419 [ncp.at] TRACE: > AT
0000171419 [ncp.at] TRACE: > AT
0000172419 [ncp.at] TRACE: > AT
0000173419 [ncp.at] TRACE: > AT
0000174419 [ncp.at] TRACE: > AT
0000175419 [ncp.at] TRACE: > AT
0000176419 [ncp.at] TRACE: > AT
0000177419 [ncp.at] TRACE: > AT
0000178419 [ncp.at] TRACE: > AT
0000179419 [ncp.at] TRACE: > AT
0000180419 [ncp.at] TRACE: > AT
0000181419 [ncp.at] TRACE: > AT
0000182419 [ncp.at] TRACE: > AT
0000183419 [ncp.at] TRACE: > AT
0000184419 [ncp.at] TRACE: > AT
0000185419 [ncp.at] TRACE: > AT
0000186419 [ncp.at] TRACE: > AT
0000187419 [ncp.at] TRACE: > AT
0000188419 [ncp.at] TRACE: > AT
0000189419 [ncp.at] TRACE: > AT
0000190419 [hal] ERROR: No response from NCP
0000190419 [hal] ERROR: No response from NCP
0000190420 [hal] TRACE: Setting UART voltage translator state 0
0000190421 [hal] TRACE: Hard resetting the modem
0000201421 [net.pppncp] TRACE: Failed to initialize ublox NCP client: -210

Yes, that looks like a failure of the cellular modem.

Support confirmed it was the modem issue as described in technical advisory (https://support.particle.io/hc/en-us/articles/360052556854). They are replacing it. Thanks for the help!

1 Like