Failing to connect Boron LTE over cellular

Hi community,
I had a Boron LTE set up about a year ago with a 3rd party sim card. Now I'm attempting to get this old Boron LTE setup with the internal sim card and I am failing. I am located in the U.S so I know the LTE works here (had it working before). Currently I have it plugged in to a USB 3.0 port on my computer (hoping that's got the 2 amps needed for the cellular transmission with no battery). So far I have taken these steps to resolve the problem

  1. Disconnected my boron from my particle account

  2. ran a program to reset to the internal sim:

//Boron LTE SIM, Credendtial, and Network settings.

#include "Particle.h"

SYSTEM_MODE(SEMI_AUTOMATIC);

void setup()

{

//For external Hologram (or other) SIM, uncomment the following and use the appropriate APN credentials:

//Cellular.setActiveSim(EXTERNAL_SIM);

//Cellular.setCredentials("hologram");

//For internal (Particle) SIM, uncomment the following:

Cellular.setActiveSim(INTERNAL_SIM);

Cellular.clearCredentials();

//    Mobile Network Operator (MNO) configuration:

//* 0 (default value): SW default

//* 1: SIM ICCID select

//* 2: ATT

//* 3: Verizon

//* 4: Telstra

//* 5: TMO

//* 6: CT

int mnoProf = 0;

Cellular.on();

Cellular.command("AT+COPS=2\r\n");               // De-register from network.

Cellular.command("AT+UMNOPROF=%d\r\n", mnoProf); // Explicitly call MNO profile from list above.

Cellular.command("AT+CFUN=15\r\n");              // Reset the modem.

// This is just so you know the operation is complete (turns on onboard blue LED).

pinMode(D7, OUTPUT);

digitalWrite(D7, HIGH);

}

void loop()

{

}

  1. ran particle update on the device
  2. manually updated to the 1.5.2 firmware on the GitHub
  3. left it on all night in hopes it would connect
  4. Ran the connectivity debugger with this output:
starting tests... turning cellular on... 0000015002 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN 0000020169 [hal] INFO: Using internal SIM card 0000020234 [gsm0710muxer] INFO: Starting GSM07.10 muxer 0000020235 [gsm0710muxer] INFO: Openning mux channel 0 0000020236 [gsm0710muxer] INFO: GSM07.10 muxer thread started deviceID=e00fce6883f61533d69a49a4 0000020288 [gsm0710muxer] INFO: Resuming channel 0 0000020288 [gsm0710muxer] INFO: Openning mux channel 1 0000020389 [gsm0710muxer] INFO: Resuming channel 1 0000020389 [gsm0710muxer] INFO: Resuming channel 1 manufacturer=u-blox model=SARA-R410M-02B firmware version=L0.0.00.00.05.06 [Feb 03 2018 13:00:41] ordering code=SARA-R410M-02B IMEI=352753091085421 IMSI=u-blox ICCID=89014103271226500807 0000020791 [app] INFO: enabling trace logging 0000020792 [ncp.at] TRACE: > AT+CGDCONT? 0000020841 [ncp.at] TRACE: < +CGDCONT: 1,"IP","10569.mcs","0.0.0.0",0,0,0,0 0000020841 [ncp.at] TRACE: < OK 0000020842 [ncp.at] TRACE: > AT+CSQ 0000020891 [ncp.at] TRACE: < +CSQ: 99,99 0000020891 [ncp.at] TRACE: < OK attempting to connect to the cellular network... 0000020894 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP 0000020894 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP 0000020895 [hal] TRACE: PPP netif -> 8 0000020896 [net.ifapi] INFO: Netif pp3 state UP 0000020896 [net.ifapi] INFO: Netif pp3 state UP 0000020898 [hal] TRACE: PPP thread event LOWER_DOWN 0000020899 [hal] TRACE: PPP thread event ADM_DOWN 0000020900 [hal] TRACE: PPP thread event ADM_UP 0000020901 [hal] TRACE: State NONE -> READY 0000020903 [ncp.at] TRACE: > AT+CIMI 0000020905 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP 0000020905 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP 0000020941 [ncp.at] TRACE: < 310410122650080 0000020941 [ncp.at] TRACE: < OK 0000020942 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","10569.mcs" 0000020991 [ncp.at] TRACE: < OK 0000020991 [ncp.at] TRACE: > AT+CEREG=2 0000021041 [ncp.at] TRACE: < OK 0000021041 [hal] TRACE: NCP connection state changed: 1 0000021042 [net.pppncp] TRACE: NCP event 2 0000021042 [net.pppncp] TRACE: State changed event: 1 0000021043 [hal] TRACE: PPP thread event LOWER_DOWN 0000021044 [ncp.at] TRACE: > AT+COPS=0,2 0000021091 [ncp.at] TRACE: < OK 0000021091 [ncp.at] TRACE: > AT+CEREG? 0000021092 [ncp.at] TRACE: < +CEREG: 2 0000021141 [ncp.at] TRACE: < +CEREG: 2,2 0000021141 [ncp.at] TRACE: < OK 0000021941 [ncp.at] TRACE: < +CEREG: 3 0000036242 [ncp.at] TRACE: > AT+CEREG? 0000036291 [ncp.at] TRACE: < +CEREG: 2,3 0000036291 [ncp.at] TRACE: < OK 0000051392 [ncp.at] TRACE: > AT+CEREG? 0000051441 [ncp.at] TRACE: < +CEREG: 2,3 0000051441 [ncp.at] TRACE: < OK 0000060537 [sys.power] TRACE: re-enabling charging 0000060579 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED 0000061677 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED 0000066443 [ncp.at] TRACE: > AT+CEREG? 0000066494 [ncp.at] TRACE: < +CEREG: 2,3 0000066494 [ncp.at] TRACE: < OK 0000081494 [ncp.at] TRACE: > AT+CEREG? 0000081544 [ncp.at] TRACE: < +CEREG: 2,3 0000081544 [ncp.at] TRACE: < OK 0000096545 [ncp.at] TRACE: > AT+CEREG? 0000096594 [ncp.at] TRACE: < +CEREG: 2,3 0000096594 [ncp.at] TRACE: < OK 0000111595 [ncp.at] TRACE: > AT+CEREG? 0000111644 [ncp.at] TRACE: < +CEREG: 2,3 0000111644 [ncp.at] TRACE: < OK 0000121677 [sys.power] TRACE: re-enabling charging 0000121712 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED 0000122794 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED

I'm pretty new to particle, but not new to micro-controllers. I've been stuck on this for two days please help.

@NotoriousBiaggi, welcome to the Community! I suggest you log a support ticket for this issue so the Particle folks can look at what’s happening in the back end to help you resolve the problem.

Which carrier are did you previously connect to? The Boron is only certified on AT&T’s network, so if it’s trying to connect to Verizon or presumably other carriers they could be blocking your IMEI. That happened to me with Verizon in the US. It worked during initial testing, but after several days in the field (550 miles away!) they stopped connecting to Verizon, and I could only connect to AT&T using a Hologram SIM. The internal SIM of course is locked to AT&T.

I would definitely log a support ticket, as I have complained about the lack of support for Verizon (and lack of external SIM on the B2 SOM) but if more people ask for this it may help the case.

P.S. If you’re trying to connect to AT&T disregard all of the above and just like a ticket like @peekay123 suggested. :slight_smile:

I just noticed in your debug trace the first thing it states is that it’s using the internal SIM card. Have you set it to use the external SIM?

In your code, I could not see any line to connect to the cloud?

e…g Particle.connect()
https://docs.particle.io/reference/device-os/firmware/boron/#particle-connect-

This would connect to both cloud and cellular network.

Or, if you just want to connect to cellular network do
Cellular.connect()
https://docs.particle.io/reference/device-os/firmware/boron/#connect--2

Or do I miss anything on your intentions?

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.