Boron LTE 3rd party SIM connection troubleshooting

Slimfetz · March 16, 2020, 11:11pm

I am having trouble using 3rd party SIMs that I previously had working on other Borons in the filed. I can not get my new Boron to connect to my Hologram SIM or my verizon SIM. Here is the code I used to set up the Boron for Verizon:

#include "Particle.h"

#include "dct.h"

SYSTEM_MODE(SEMI_AUTOMATIC);



void setup() {
    Cellular.on();
    Cellular.setActiveSim(EXTERNAL_SIM);
    //Cellular.setCredentials("hologram");
    Cellular.setCredentials("vzwinternet");
    int mnoProf = 3;
    Cellular.command("AT+COPS=2\r\n");
   // Cellular.command("AT+COPS=2,2,\"31170\"\r\n");
    Cellular.command("AT+UMNOPROF=%d\r\n", mnoProf);
    Cellular.command("AT+CFUN=15\r\n");
    Cellular.connect();
}

void loop() {
    
    if (Particle.connected() == false && Cellular.ready() == true){
        Particle.connect();
    }
}

After flashing the above code, I used @rickkas7 cloud debug found here:

github.com

rickkas7/boron-clouddebug/blob/master/README.md



# Boron Cloud Debug

*Special code for debugging cloud connection issues with the Particle Boron*

## What is this?

This is a tool to debug cloud connection issues. It:

- Prints out cellular parameters (ICCID, etc.)
- Prints out your cellular carrier and frequency band information
- Pings your IP gateway
- Pings the Google DNS (8.8.8.8)
- Does a DNS server lookup of the device server (device.spark.io)
- Makes an actual cloud connection
- Acts like Tinker after connecting 
- Can print out information about nearby cellular towers

It uses a special debug version of the system firmware, so there's additional debugging information generated as well.

This file has been truncated. show original

This is the Serial output:

starting tests...
turning cellular on...
0000015003 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000020171 [hal] INFO: Using external Nano SIM card
0000020234 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000020235 [gsm0710muxer] INFO: Openning mux channel 0
0000020235 [gsm0710muxer] INFO: GSM07.10 muxer thread started
deviceID=e00fce680df17bc4f0b091cd
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=356726103514378
IMSI=u-blox
ICCID=89148000004740191385
0000020792 [app] INFO: enabling trace logging
0000020793 [ncp.at] TRACE: > AT+CGDCONT?
0000020842 [ncp.at] TRACE: < +CGDCONT: 1,"IP","vzwinternet","0.0.0.0",0,0,0,0
0000020843 [ncp.at] TRACE: < +CGDCONT: 2,"IPV4V6","VZWADMIN","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000020846 [ncp.at] TRACE: < +CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000020847 [ncp.at] TRACE: < +CGDCONT: 6,"IPV4V6","VZWCLASS6","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000020850 [ncp.at] TRACE: < OK
0000020852 [ncp.at] TRACE: > AT+CSQ
0000020892 [ncp.at] TRACE: < +CSQ: 99,99
0000020892 [ncp.at] TRACE: < OK
attempting to connect to the cellular network...
0000020896 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000020896 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000020899 [hal] TRACE: PPP netif -> 8
0000020900 [net.ifapi] INFO: Netif pp3 state UP
0000020900 [net.ifapi] INFO: Netif pp3 state UP
0000020901 [hal] TRACE: PPP thread event LOWER_DOWN
0000020902 [hal] TRACE: PPP thread event ADM_DOWN
0000020904 [hal] TRACE: PPP thread event ADM_UP
0000020906 [hal] TRACE: State NONE -> READY
0000020906 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","vzwinternet"
0000020910 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000020910 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000020942 [ncp.at] TRACE: < OK
0000020942 [ncp.at] TRACE: > AT+CEREG=2
0000020992 [ncp.at] TRACE: < OK
0000020992 [hal] TRACE: NCP connection state changed: 1
0000020994 [net.pppncp] TRACE: NCP event 2
0000020995 [net.pppncp] TRACE: State changed event: 1
0000020996 [hal] TRACE: PPP thread event LOWER_DOWN
0000020998 [ncp.at] TRACE: > AT+COPS=0,2
0000021042 [ncp.at] TRACE: < OK
0000021042 [ncp.at] TRACE: > AT+CEREG?
0000021043 [ncp.at] TRACE: < +CEREG: 2
0000021092 [ncp.at] TRACE: < +CEREG: 2,2
0000021092 [ncp.at] TRACE: < OK
0000021992 [ncp.at] TRACE: < +CEREG: 3
0000036093 [ncp.at] TRACE: > AT+CEREG?
0000036142 [ncp.at] TRACE: < +CEREG: 2,3
0000036142 [ncp.at] TRACE: < OK
0000051243 [ncp.at] TRACE: > AT+CEREG?
0000051292 [ncp.at] TRACE: < +CEREG: 2,3
0000051292 [ncp.at] TRACE: < OK
0000061743 [sys.power] TRACE: re-enabling charging
0000061778 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000062890 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000066393 [ncp.at] TRACE: > AT+CEREG?
0000066442 [ncp.at] TRACE: < +CEREG: 2,3
0000066442 [ncp.at] TRACE: < OK
0000081543 [ncp.at] TRACE: > AT+CEREG?
0000081592 [ncp.at] TRACE: < +CEREG: 2,3
0000081592 [ncp.at] TRACE: < OK
0000096693 [ncp.at] TRACE: > AT+CEREG?
0000096742 [ncp.at] TRACE: < +CEREG: 2,3
0000096742 [ncp.at] TRACE: < OK
0000111843 [ncp.at] TRACE: > AT+CEREG?
0000111892 [ncp.at] TRACE: < +CEREG: 2,3
0000111892 [ncp.at] TRACE: < OK
0000123751 [sys.power] TRACE: re-enabling charging
0000123789 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000124900 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000126993 [ncp.at] TRACE: > AT+CEREG?
0000127042 [ncp.at] TRACE: < +CEREG: 2,3
0000127042 [ncp.at] TRACE: < OK
0000142143 [ncp.at] TRACE: > AT+CEREG?
0000142192 [ncp.at] TRACE: < +CEREG: 2,3
0000142193 [ncp.at] TRACE: < OK
0000157293 [ncp.at] TRACE: > AT+CEREG?
0000157342 [ncp.at] TRACE: < +CEREG: 2,3
0000157342 [ncp.at] TRACE: < OK
0000172443 [ncp.at] TRACE: > AT+CEREG?
0000172492 [ncp.at] TRACE: < +CEREG: 2,3
0000172492 [ncp.at] TRACE: < OK
0000184901 [sys.power] TRACE: re-enabling charging
0000184930 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000186042 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000187593 [ncp.at] TRACE: > AT+CEREG?
0000187644 [ncp.at] TRACE: < +CEREG: 2,3
0000187644 [ncp.at] TRACE: < OK
0000202745 [ncp.at] TRACE: > AT+CEREG?
0000202794 [ncp.at] TRACE: < +CEREG: 2,3
0000202794 [ncp.at] TRACE: < OK
0000217795 [ncp.at] TRACE: > AT+CEREG?
0000217844 [ncp.at] TRACE: < +CEREG: 2,3
0000217844 [ncp.at] TRACE: < OK
0000232945 [ncp.at] TRACE: > AT+CEREG?
0000232994 [ncp.at] TRACE: < +CEREG: 2,3
0000232994 [ncp.at] TRACE: < OK
0000246042 [sys.power] TRACE: re-enabling charging
0000246074 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000247186 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000248095 [ncp.at] TRACE: > AT+CEREG?
0000248148 [ncp.at] TRACE: < +CEREG: 2,3
0000248148 [ncp.at] TRACE: < OK
0000263149 [ncp.at] TRACE: > AT+CEREG?
0000263198 [ncp.at] TRACE: < +CEREG: 2,3
0000263198 [ncp.at] TRACE: < OK
0000278199 [ncp.at] TRACE: > AT+CEREG?
0000278248 [ncp.at] TRACE: < +CEREG: 2,3
0000278249 [ncp.at] TRACE: < OK
0000293350 [ncp.at] TRACE: > AT+CEREG?
0000293398 [ncp.at] TRACE: < +CEREG: 2,3
0000293399 [ncp.at] TRACE: < OK
0000307187 [sys.power] TRACE: re-enabling charging
0000307216 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000308328 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000308402 [ncp.at] TRACE: > AT+CEREG?
0000308448 [ncp.at] TRACE: < +CEREG: 2,3
0000308448 [ncp.at] TRACE: < OK
0000323549 [ncp.at] TRACE: > AT+CEREG?
0000323598 [ncp.at] TRACE: < +CEREG: 2,3
0000323599 [ncp.at] TRACE: < OK
0000323600 [hal] WARN: Resetting the modem due to the network registration timeout
0000323600 [hal] WARN: Resetting the modem due to the network registration timeout
0000323603 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000323603 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000323605 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000323605 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000323608 [gsm0710muxer] INFO: Closing all muxed channels
0000323608 [gsm0710muxer] INFO: Closing all muxed channels
0000323610 [gsm0710muxer] INFO: Closing mux channel 1
0000323610 [gsm0710muxer] INFO: Closing mux channel 1
0000323612 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000323612 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000323614 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000323614 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000323618 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000323618 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000323720 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000323720 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000323772 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000323772 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000323774 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000323774 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000323777 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000323777 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000323779 [hal] TRACE: Hard resetting the modem
0000334780 [hal] TRACE: Powering on the modem after the hard reset
0000334781 [hal] TRACE: Powering modem on
0000334932 [hal] TRACE: Modem powered on
0000334933 [hal] TRACE: Setting UART voltage translator state 0
0000334934 [hal] TRACE: Powering modem off
0000334935 [hal] TRACE: Setting UART voltage translator state 0
0000346536 [hal] ERROR: Failed to power off modem
0000346536 [hal] ERROR: Failed to power off modem
0000346537 [hal] TRACE: NCP state changed: 0
0000346538 [net.pppncp] TRACE: NCP event 1
0000346637 [hal] TRACE: Modem already on
0000346638 [hal] TRACE: Setting UART voltage translator state 1
0000347639 [ncp.at] TRACE: > AT
0000347645 [ncp.at] TRACE: < OK
0000348645 [hal] TRACE: NCP ready to accept AT commands
0000348645 [ncp.at] TRACE: > AT+UGPIOC?
0000348652 [ncp.at] TRACE: < +UGPIOC:
0000348653 [ncp.at] TRACE: < 16,255
0000348654 [ncp.at] TRACE: < 19,255
0000348655 [ncp.at] TRACE: < 23,0
0000348656 [ncp.at] TRACE: < 24,255
0000348657 [ncp.at] TRACE: < 25,255
0000348657 [ncp.at] TRACE: < 42,255
0000348658 [ncp.at] TRACE: < OK
0000348658 [ncp.at] TRACE: > AT+UGPIOR=23
0000348667 [ncp.at] TRACE: < +UGPIOR: 23,0
0000348667 [ncp.at] TRACE: < OK
0000348668 [hal] INFO: Using external Nano SIM card
0000348668 [hal] INFO: Using external Nano SIM card
0000348671 [ncp.at] TRACE: > AT+CPIN?
0000348678 [ncp.at] TRACE: < +CPIN: READY
0000348679 [ncp.at] TRACE: < OK
0000348679 [ncp.at] TRACE: > AT+CCID
0000348688 [ncp.at] TRACE: < +CCID: 89148000004740191385
0000348689 [ncp.at] TRACE: < OK
0000348691 [ncp.at] TRACE: > AT+COPS=2,2
0000348707 [ncp.at] TRACE: < OK
0000348707 [ncp.at] TRACE: > AT+COPS=3,2
0000348712 [ncp.at] TRACE: < OK
0000348712 [ncp.at] TRACE: > ATI9
0000348717 [ncp.at] TRACE: < L0.0.00.00.05.06,A.02.01
0000348718 [ncp.at] TRACE: < OK
0000348719 [ncp.at] TRACE: > AT+UMNOPROF?
0000348726 [ncp.at] TRACE: < +UMNOPROF: 3
0000348727 [ncp.at] TRACE: < OK
0000348728 [ncp.at] TRACE: > AT+URAT?
0000348733 [ncp.at] TRACE: < +URAT: 7
0000348734 [ncp.at] TRACE: < OK
0000348735 [ncp.at] TRACE: > AT+CEDRXS?
0000348740 [ncp.at] TRACE: < +CEDRXS:
0000348741 [ncp.at] TRACE: < OK
0000348742 [ncp.at] TRACE: > AT+CPSMS=0
0000348758 [ncp.at] TRACE: < OK
0000348758 [ncp.at] TRACE: > AT+CMUX=0,0,,1509,,,,,
0000348765 [ncp.at] TRACE: < OK
0000348765 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000348765 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000348768 [gsm0710muxer] INFO: Openning mux channel 0
0000348768 [gsm0710muxer] INFO: Openning mux channel 0
0000348768 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000348768 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000348821 [gsm0710muxer] INFO: Resuming channel 0
0000348821 [gsm0710muxer] INFO: Resuming channel 0
0000348822 [gsm0710muxer] INFO: Openning mux channel 1
0000348822 [gsm0710muxer] INFO: Openning mux channel 1
0000348924 [gsm0710muxer] INFO: Resuming channel 1
0000348924 [gsm0710muxer] INFO: Resuming channel 1
0000348925 [gsm0710muxer] INFO: Resuming channel 1
0000348925 [gsm0710muxer] INFO: Resuming channel 1
0000348927 [ncp.at] TRACE: > AT
0000348978 [ncp.at] TRACE: < OK
0000348978 [hal] TRACE: NCP state changed: 1
0000348979 [net.pppncp] TRACE: NCP event 1
0000348980 [hal] TRACE: Muxer AT channel live
0000348982 [hal] TRACE: PPP thread event LOWER_DOWN
0000348983 [hal] TRACE: PPP thread event ADM_DOWN
0000348983 [hal] TRACE: State READY -> NONE
0000348985 [hal] TRACE: PPP thread event ADM_UP
0000348986 [hal] TRACE: State NONE -> READY
0000348986 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","vzwinternet"
0000349028 [ncp.at] TRACE: < OK
0000349028 [ncp.at] TRACE: > AT+CEREG=2
0000349078 [ncp.at] TRACE: < OK
0000349078 [hal] TRACE: NCP connection state changed: 1
0000349080 [net.pppncp] TRACE: NCP event 2
0000349081 [net.pppncp] TRACE: State changed event: 1
0000349082 [ncp.at] TRACE: > AT+COPS=0,2
0000349082 [hal] TRACE: PPP thread event LOWER_DOWN
0000349128 [ncp.at] TRACE: < OK
0000349128 [ncp.at] TRACE: > AT+CEREG?
0000349178 [ncp.at] TRACE: < +CEREG: 2,3
0000349178 [ncp.at] TRACE: < OK
0000364279 [ncp.at] TRACE: > AT+CEREG?
0000364328 [ncp.at] TRACE: < +CEREG: 2,3
0000364329 [ncp.at] TRACE: < OK
0000368328 [sys.power] TRACE: re-enabling charging
0000368369 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000369480 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000379334 [ncp.at] TRACE: > AT+CEREG?
0000379381 [ncp.at] TRACE: < +CEREG: 2,3
0000379381 [ncp.at] TRACE: < OK
0000394482 [ncp.at] TRACE: > AT+CEREG?
0000394531 [ncp.at] TRACE: < +CEREG: 2,3
0000394531 [ncp.at] TRACE: < OK
0000409532 [ncp.at] TRACE: > AT+CEREG?
0000409581 [ncp.at] TRACE: < +CEREG: 2,3
0000409582 [ncp.at] TRACE: < OK
0000424583 [ncp.at] TRACE: > AT+CEREG?
0000424631 [ncp.at] TRACE: < +CEREG: 2,3
0000424631 [ncp.at] TRACE: < OK
0000430479 [sys.power] TRACE: re-enabling charging
0000430508 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000431619 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000439732 [ncp.at] TRACE: > AT+CEREG?
0000439786 [ncp.at] TRACE: < +CEREG: 2,3
0000439786 [ncp.at] TRACE: < OK
0000454887 [ncp.at] TRACE: > AT+CEREG?
0000454936 [ncp.at] TRACE: < +CEREG: 2,3
0000454936 [ncp.at] TRACE: < OK
0000470037 [ncp.at] TRACE: > AT+CEREG?
0000470086 [ncp.at] TRACE: < +CEREG: 2,3
0000470086 [ncp.at] TRACE: < OK
0000485087 [ncp.at] TRACE: > AT+CEREG?
0000485136 [ncp.at] TRACE: < +CEREG: 2,3
0000485136 [ncp.at] TRACE: < OK
0000491619 [sys.power] TRACE: re-enabling charging
0000491662 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000492773 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED

Slimfetz · March 17, 2020, 12:17am

Here is the output when using the hologram SIM and changing the APN to hologram

starting tests...
turning cellular on...
0000015001 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000021170 [hal] INFO: Using external Nano SIM card
0000021234 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000021235 [gsm0710muxer] INFO: Openning mux channel 0
0000021235 [gsm0710muxer] INFO: GSM07.10 muxer thread started
deviceID=e00fce680df17bc4f0b091cd
0000021286 [gsm0710muxer] INFO: Resuming channel 0
0000021287 [gsm0710muxer] INFO: Openning mux channel 1
0000021338 [gsm0710muxer] INFO: Resuming channel 1
0000021339 [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=356726103514378
IMSI=u-blox
ICCID=8944502802190652191
0000021741 [app] INFO: enabling trace logging
0000021742 [ncp.at] TRACE: > AT+CGDCONT?
0000021790 [ncp.at] TRACE: < +CGDCONT: 1,"IP","hologram","0.0.0.0",0,0,0,0
0000021791 [ncp.at] TRACE: < +CGDCONT: 2,"IPV4V6","VZWADMIN","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000021793 [ncp.at] TRACE: < +CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000021795 [ncp.at] TRACE: < +CGDCONT: 6,"IPV4V6","VZWCLASS6","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
0000021798 [ncp.at] TRACE: < OK
0000021799 [ncp.at] TRACE: > AT+CSQ
0000021840 [ncp.at] TRACE: < +CSQ: 99,99
0000021841 [ncp.at] TRACE: < OK
attempting to connect to the cellular network...
0000021843 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000021843 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000021846 [hal] TRACE: PPP netif -> 8
0000021848 [net.ifapi] INFO: Netif pp3 state UP
0000021848 [net.ifapi] INFO: Netif pp3 state UP
0000021852 [hal] TRACE: PPP thread event LOWER_DOWN
0000021853 [hal] TRACE: PPP thread event ADM_DOWN
0000021854 [hal] TRACE: PPP thread event ADM_UP
0000021854 [hal] TRACE: State NONE -> READY
0000021855 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","hologram"
0000021857 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000021857 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000021890 [ncp.at] TRACE: < OK
0000021891 [ncp.at] TRACE: > AT+CEREG=2
0000021940 [ncp.at] TRACE: < OK
0000021940 [hal] TRACE: NCP connection state changed: 1
0000021941 [net.pppncp] TRACE: NCP event 2
0000021941 [net.pppncp] TRACE: State changed event: 1
0000021942 [ncp.at] TRACE: > AT+COPS=0,2
0000021943 [hal] TRACE: PPP thread event LOWER_DOWN
0000021990 [ncp.at] TRACE: < OK
0000021991 [ncp.at] TRACE: > AT+CEREG?
0000021991 [ncp.at] TRACE: < +CEREG: 2
0000022040 [ncp.at] TRACE: < +CEREG: 2,2
0000022041 [ncp.at] TRACE: < OK
0000037041 [ncp.at] TRACE: > AT+CEREG?
0000037090 [ncp.at] TRACE: < +CEREG: 2,2
0000037091 [ncp.at] TRACE: < OK
0000052091 [ncp.at] TRACE: > AT+CEREG?
0000052140 [ncp.at] TRACE: < +CEREG: 2,2
0000052141 [ncp.at] TRACE: < OK
0000060742 [sys.power] TRACE: re-enabling charging
0000060771 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000061882 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000067142 [ncp.at] TRACE: > AT+CEREG?
0000067193 [ncp.at] TRACE: < +CEREG: 2,2
0000067194 [ncp.at] TRACE: < OK
0000082194 [ncp.at] TRACE: > AT+CEREG?
0000082243 [ncp.at] TRACE: < +CEREG: 2,2
0000082244 [ncp.at] TRACE: < OK
0000097244 [ncp.at] TRACE: > AT+CEREG?
0000097293 [ncp.at] TRACE: < +CEREG: 2,2
0000097294 [ncp.at] TRACE: < OK

rickkas7 · March 17, 2020, 3:27pm

In all likelihood you’ll fail to connect to Verizon with either a Verizon SIM or a Hologram SIM configured for Verizon. Even if you get it to work, it will eventually stop working.

The reason is that some LTE Cat M1 carriers (including AT&T and Verizon) will only allow connections from devices that have been certified with their network. Particle LTE devices have been certified by AT&T but not Verizon. Thus Verizon will eventually block the device by IMEI since the IMEI has not been registered with Verizon.

We do not currently have a plan to certify with Verizon, as the Particle SIM does not currently support it.

Slimfetz · March 17, 2020, 4:40pm

The only reason for using verizon, is I have never been able to get AT&T sim cards to work with the Borons. I worked on it for over a month and I was finally able to use Hologram sims on the very first try. Now I was trying to use a Hologram sim for a new setup and I am unable to connect using verizon or AT&T. I tried my original AT&T sims just to see if maybe the newest firmware on the Borons has made a difference and They still will not connect either. At this point I am beginning to feel like there aren’t really many compatible 3rd party sims that will work

Slimfetz · March 17, 2020, 4:48pm

Here is the setup I used for my AT&T sims


#include "Particle.h"

#include "dct.h"

SYSTEM_MODE(SEMI_AUTOMATIC);

void setup() {
    Cellular.setActiveSim(EXTERNAL_SIM);
   // Cellular.setCredentials("vzwinternet");
    //Cellular.setCredentials("hologram");
    Cellular.setCredentials("m2m.com.attz");

    // This clears the setup done flag on brand new devices so it won't stay in listening mode
    const uint8_t val = 0x01;
    dct_write_app_data(&val, DCT_SETUP_DONE_OFFSET, 1);

    // This is just so you know the operation is complete
    pinMode(D7, OUTPUT);
    digitalWrite(D7, HIGH);

	Cellular.on();
	
	/*
	* 0 (default value): SW default
    * 1: SIM ICCID select
    * 2: ATT
    * 3: Verizon
    * 4: Telstra
    * 5: TMO
    * 6: CT
	*/
    int mnoProf = 2;
    
    Cellular.command("AT+URAT=7\r\n"); //LTE M1
    Cellular.command("AT+COPS=2\r\n");
    Cellular.command("AT+UMNOPROF=%d\r\n", mnoProf);
    Cellular.command("AT+CFUN=15\r\n");
    Cellular.connect();
    Particle.connect();
}

void loop() {
    Particle.connect();
}

and here is the debug output

starting tests...
turning cellular on...
0000015003 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000020170 [hal] INFO: Using external Nano SIM card
0000020238 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000020239 [gsm0710muxer] INFO: Openning mux channel 0
0000020239 [gsm0710muxer] INFO: GSM07.10 muxer thread started
deviceID=e00fce680df17bc4f0b091cd
0000020290 [gsm0710muxer] INFO: Resuming channel 0
0000020290 [gsm0710muxer] INFO: Openning mux channel 1
0000020391 [gsm0710muxer] INFO: Resuming channel 1
0000020391 [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=356726103514378
IMSI=u-blox
ICCID=89011703278213679148
0000020794 [app] INFO: enabling trace logging
0000020795 [ncp.at] TRACE: > AT+CGDCONT?
0000020843 [ncp.at] TRACE: < +CGDCONT: 1,"IP","m2m.com.attz","0.0.0.0",0,0,0,0
0000020844 [ncp.at] TRACE: < OK
0000020845 [ncp.at] TRACE: > AT+CSQ
0000020893 [ncp.at] TRACE: < +CSQ: 99,99
0000020893 [ncp.at] TRACE: < OK
attempting to connect to the cellular network...
0000020896 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000020896 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000020897 [hal] TRACE: PPP netif -> 8
0000020898 [net.ifapi] INFO: Netif pp3 state UP
0000020898 [net.ifapi] INFO: Netif pp3 state UP
0000020899 [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+CGDCONT=1,"IP","m2m.com.attz"
0000020904 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000020904 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000020943 [ncp.at] TRACE: < OK
0000020944 [ncp.at] TRACE: > AT+CEREG=2
0000020993 [ncp.at] TRACE: < OK
0000020993 [hal] TRACE: NCP connection state changed: 1
0000020994 [net.pppncp] TRACE: NCP event 2
0000020994 [net.pppncp] TRACE: State changed event: 1
0000020995 [ncp.at] TRACE: > AT+COPS=0,2
0000020996 [hal] TRACE: PPP thread event LOWER_DOWN
0000021043 [ncp.at] TRACE: < OK
0000021044 [ncp.at] TRACE: > AT+CEREG?
0000021044 [ncp.at] TRACE: < +CEREG: 2
0000021093 [ncp.at] TRACE: < +CEREG: 2,2
0000021093 [ncp.at] TRACE: < OK
0000036094 [ncp.at] TRACE: > AT+CEREG?
0000036143 [ncp.at] TRACE: < +CEREG: 2,2
0000036144 [ncp.at] TRACE: < OK
0000051144 [ncp.at] TRACE: > AT+CEREG?
0000051193 [ncp.at] TRACE: < +CEREG: 2,2
0000051194 [ncp.at] TRACE: < OK
0000060745 [sys.power] TRACE: re-enabling charging
0000060784 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000061896 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000066196 [ncp.at] TRACE: > AT+CEREG?
0000066246 [ncp.at] TRACE: < +CEREG: 2,2
0000066247 [ncp.at] TRACE: < OK
0000076147 [ncp.at] TRACE: < +CEREG: 3
0000078047 [ncp.at] TRACE: < +CEREG: 2
0000081247 [ncp.at] TRACE: > AT+CEREG?
0000081296 [ncp.at] TRACE: < +CEREG: 2,2
0000081296 [ncp.at] TRACE: < OK
0000096297 [ncp.at] TRACE: > AT+CEREG?
0000096346 [ncp.at] TRACE: < +CEREG: 2,2
0000096347 [ncp.at] TRACE: < OK
0000111347 [ncp.at] TRACE: > AT+CEREG?
0000111396 [ncp.at] TRACE: < +CEREG: 2,2
0000111397 [ncp.at] TRACE: < OK
0000121896 [sys.power] TRACE: re-enabling charging
0000121928 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000123040 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000126401 [ncp.at] TRACE: > AT+CEREG?
0000126453 [ncp.at] TRACE: < +CEREG: 2,2
0000126454 [ncp.at] TRACE: < OK
0000141454 [ncp.at] TRACE: > AT+CEREG?
0000141503 [ncp.at] TRACE: < +CEREG: 2,2
0000141503 [ncp.at] TRACE: < OK

AT&T is certified for the Boron but I have never been able to connect a 3rd party AT&T sim

AlbertZeroK · March 17, 2020, 8:36pm

This works with at&t Cat M1 One Rate SIM

#include "Particle.h"

#include "dct.h"

SYSTEM_MODE(SEMI_AUTOMATIC);

void setup() {
    Cellular.setActiveSim(EXTERNAL_SIM);
    Cellular.setCredentials("m2m.com.attz");

    // This clears the setup done flag on brand new devices so it won't stay in listening mode
    const uint8_t val = 0x01;
    dct_write_app_data(&val, DCT_SETUP_DONE_OFFSET, 1);

    // This is just so you know the operation is complete
    pinMode(D7, OUTPUT);
    digitalWrite(D7, HIGH);
}

void loop() {
}

AlbertZeroK · March 17, 2020, 8:37pm

Here are the other APN’s, note you can’t use a normal LTE sim with the boron, it has to be a CAT M1

What APN or how can I find the APN that I need to use for my device?

Unlike a consumer device, IoT devices do not automatically configure themselves for connectivity to the network and instead will need to be properly configured.

Your device may have come pre-configured with a consumer APN that will not work with these SIMs. In order to establish a successful data connection when you test your device with the SIM in the kit, please be certain to set your devices APN name to

m2m.com.attz . No user name or password is typically required.

For OneRate SIMs, use m2m64.com.attz .

For NB-IoT OneRate, use APN m2mNB16.com.attz .

This setting can typically be found in your devices connection software or network details. If you are unable to set the APN on your device please contact the device manufacturer for details on how to set an APN on the device.

AlbertZeroK · March 17, 2020, 8:38pm

I don’t need any AT Commands to get mine to work either.

Slimfetz · March 17, 2020, 9:10pm

Wow you are my hero!!! This would have prevented so many problems months ago!!! I couldn’t find any info that the APN was different for my data plan. I was able to navigate to it through their website, but only because I knew what I was looking for. It was not easy to find thank you!

system · September 16, 2020, 9:11am

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

Topic		Replies	Views
Boron - Hologram SIM - Verizon Network Issues Troubleshooting boron	15	3465	January 10, 2020
Failing to connect Boron LTE over cellular Connectivity boron	5	573	January 7, 2021
Boron LTE 3rd Party SIM Issues Troubleshooting	6	2113	February 11, 2019
Trouble Using Hologram SIM to Connect to Verizon Connectivity boron	2	1365	April 5, 2020
Boron 2G/3G Never connects to cloud Troubleshooting boron	1	513	April 14, 2019

Boron LTE 3rd party SIM connection troubleshooting

What APN or how can I find the APN that I need to use for my device?

Related topics