Boron LTE- support


#21

It appears that in order to use the the Hologram SIM with LTE Cat M1, you need to explicitly select the carrier.

You need to send AT+UMNOPROF=xx command where xx is the profile number below.

Mobile Network Operator (MNO) configuration:
* 0 (default value): SW default
* 1: SIM ICCID select
* 2: ATT
* 3: Verizon
* 4: Telstra
* 5: TMO
* 6: CT

You should send these three commands from the Cellular.on() state (but not connected):

int mnoProf = 3;
Cellular.command("AT+COPS=2\r\n");
Cellular.command("AT+UMNOPROF=%d\r\n", mnoProf);
Cellular.command("AT+CFUN=15\r\n");

The setting is saved in the NVRAM in the modem so you only need to do it once.

I was unable to use AT&T (2) with the Hologram SIM, though AT&T works great with the built-in Particle SIM.

Verizon (3), however did work for me (in the United States) with the Hologram SIM and a Boron LTE.

verizon


Boron + 3rd Party Sim (SORACOM)
Having an impossible time setting up LTE Borons with 3rd party sims
Boron - Hologram SIM - Verizon Network Issues
#22

Thanks, Rikkas,

I think this puts me on the right track (thanks for including Cellular.command() in latest FW, too!)

Sadly, my general mucking around with modem commands has kinda sorta borked my modem, it seems (hangs head in shame).

I could not get online last night (3rd party SIM) despite the excellent guidance, and starting fresh this morning, I can’t get back online with the internal SIM, either. Tried both the AT&T and Verizon configs, then started futzing around with the radio.

Gave up after the Oscars, and tried to reset all this AM.

I’ve tried all the usual things that have worked for me in the past:

SIM selection reset:

 Cellular.setActiveSim(INTERNAL_SIM);
 Cellular.clearCredentials();

Modem reset and /or radio selection: (each below tried independently, and in reverse order)

Cellular.command("AT&F\r\n");
Cellular.command("AT+URAT=7,8\r\n");

Reclaiming device (worked up to the “Connecting tip Internet via Cellular” stage, eternal green blinking)
Reloaded hybrid FW 0.9.0
Reloaded boron tinker.

Are there any AT commands / configs that are stored in the Boron by Particle that are wiped out by the factory (AT&F)modem config?

Got any ideas? My list of ideas has reached the end.

Thanks in advance!

And yes, I am the reason why people cannot have nice things, it seems…

UPDATE: loaded and ran boron-clouddebug.bin. Summary of output: Many +CEREG: 2,2, then changes to +CEREG: 2,3, then resets modem. Then repeats the cycle.


#23

Would you happen to have any insight for us on this, @BDub?


#24

UPDATE: My cloud debug output was similar to another user here who ended up with issues on his local cell tower. I took my Boron for a ride last night, certainly far enough to expose it to 4 or 5 new towers. No joy.


#25

If you are using a 3rd party SIM, you should be using the EXTERNAL_SIM option here, and you may also need to explicitly set the 3rd party SIM credentials.

You might also try forcing Cat-M1 mode since there is known issue with the R410 that was fixed in Gen 2, but might not be fixed yet in Gen 3. If we detect URAT=7,8, we force it to URAT=7. So you can run Cellular.command("AT+URAT=7\r\n"); and power cycle your Boron to get the same effect


#26

Thanks, Bdub!

I concur I saw the same behavior on my Arduino MKR NB 1500 – it REALLY works better / smoother / connects faster when set for Cat-M1.

I had used the external SIM setting, and saw in the serial debug it was definitely looking at the external SIM.

Are the MNO profiles also available when using the internal Particle SIM (outside of the “0” as default)?

To allow myself future A-B comparisons, and rule out such things as cell tower issues, I’ve ordered 2 more Boron LTE’s.

Will give it a try today after the day job. :slight_smile:

Thanks for the rapid response!


#27

Currently we use the u-blox factory default of 0 for +UMNOPROF, but do intend on switching this to AT&T (2) for Particle internal SIMs on devices that use the SARA-R410M-02B modem. You can make this change if you wish at any time via Cellular.command() as Rick mentioned above, but I don’t know of any differences you’ll see currently when using the Particle SIM.


#28

A bit of good news: my Boron is back to working perfectly on the internal SIM!

What did it: not sure, there may have been some issues with the network recently due to the massive winds we had on Sunday.

I have the sequence down to a science now: run my little credential setting / SIM setting / network setting program. Wait for the blue LED to blink at the end, so I know it’s done. Load and run boron-clouddebug.bin. Watch the serial output.

Network registration on the internal SIM is almost instantaneous. Much joy!

I’ve now tried the same sequence, switching to external Hologram SIM, APN “hologram”, AT&T modem preset, and also repeated for Verizon set up. No joy.

Switch back to internal SIM, clear the credentials, and the Boron works perfectly. I can now travel full circle. — just need to get that Hologram SIM to behave!

As always, thanks to the Particle team for the outstanding and rapid support!


#29

Here’s some debug output from boron cloud debug (0.9.0), Hologram SIM.

It never connects; endless flashing green.

I’ve tried both AT&T and Verizon presets; as you can see below, the external SIM is recognized, as is the Hologram APN.

The modem eventually recycles, and the whole thing repeats itself.

Ideas welcome!

20:43:41.795 -> starting tests...
20:43:41.795 -> turning cellular on...
20:43:41.795 -> 0000015004 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
20:43:47.964 -> 0000021174 [hal] INFO: Using external Nano SIM card
20:43:48.036 -> 0000021240 [gsm0710muxer] INFO: Starting GSM07.10 muxer
20:43:48.036 -> 0000021241 [gsm0710muxer] INFO: Openning mux channel 0
20:43:48.036 -> 0000021241 [gsm0710muxer] INFO: GSM07.10 muxer thread started
20:43:48.036 -> deviceID=e00fce680f32a31afe83fc37
20:43:48.071 -> 0000021294 [gsm0710muxer] INFO: Resuming channel 0
20:43:48.071 -> 0000021295 [gsm0710muxer] INFO: Openning mux channel 1
20:43:48.179 -> 0000021396 [gsm0710muxer] INFO: Resuming channel 1
20:43:48.179 -> 0000021397 [gsm0710muxer] INFO: Resuming channel 1
20:43:48.293 -> manufacturer=u-blox
20:43:48.328 -> model=SARA-R410M-02B
20:43:48.363 -> firmware version=L0.0.00.00.05.06 [Feb 03 2018 13:00:41]
20:43:48.431 -> ordering code=SARA-R410M-02B
20:43:48.466 -> IMEI=3527530XXXXXXX [redacted]
20:43:48.535 -> IMSI=u-blox
20:43:48.570 -> ICCID=8944500XXXXX. [redacted]
20:43:48.570 -> 0000021799 [app] INFO: enabling trace logging
20:43:48.570 -> attempting to connect to the cellular network...
20:43:48.570 -> 0000021803 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
20:43:48.570 -> 0000021803 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
20:43:48.570 -> 0000021805 [hal] TRACE: PPP netif -> 8
20:43:48.570 -> 0000021806 [net.ifapi] INFO: Netif pp3 state UP
20:43:48.570 -> 0000021806 [net.ifapi] INFO: Netif pp3 state UP
20:43:48.605 -> 0000021808 [hal] TRACE: PPP thread event LOWER_DOWN
20:43:48.605 -> 0000021809 [hal] TRACE: PPP thread event ADM_DOWN
20:43:48.605 -> 0000021811 [hal] TRACE: PPP thread event ADM_UP
20:43:48.605 -> 0000021813 [hal] TRACE: State NONE -> READY
20:43:48.605 -> 0000021813 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","hologram"
20:43:48.605 -> 0000021816 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
20:43:48.605 -> 0000021816 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
20:43:48.638 -> 0000021849 [ncp.at] TRACE: < OK
20:43:48.638 -> 0000021849 [ncp.at] TRACE: > AT+CEREG=2
20:43:48.674 -> 0000021899 [ncp.at] TRACE: < OK
20:43:48.674 -> 0000021899 [hal] TRACE: NCP connection state changed: 1
20:43:48.674 -> 0000021900 [net.pppncp] TRACE: NCP event 2
20:43:48.674 -> 0000021901 [net.pppncp] TRACE: State changed event: 1
20:43:48.674 -> 0000021902 [hal] TRACE: PPP thread event LOWER_DOWN
20:43:48.674 -> 0000021903 [ncp.at] TRACE: > AT+COPS=0
20:43:48.747 -> 0000021949 [ncp.at] TRACE: < OK
20:43:48.747 -> 0000021949 [ncp.at] TRACE: > AT+CEREG?
20:43:48.782 -> 0000021999 [ncp.at] TRACE: < +CEREG: 2,0
20:43:48.782 -> 0000021999 [ncp.at] TRACE: < OK
20:43:49.383 -> 0000022599 [ncp.at] TRACE: < +CEREG: 2
20:43:50.799 -> 0000023999 [ncp.at] TRACE: < +CEREG: 3
20:44:03.888 -> 0000037100 [ncp.at] TRACE: > AT+CEREG?
20:44:03.922 -> 0000037149 [ncp.at] TRACE: < +CEREG: 2,3
20:44:03.922 -> 0000037150 [ncp.at] TRACE: < OK
20:44:18.935 -> 0000052151 [ncp.at] TRACE: > AT+CEREG?
20:44:18.972 -> 0000052199 [ncp.at] TRACE: < +CEREG: 2,3
20:44:18.972 -> 0000052200 [ncp.at] TRACE: < OK
20:44:27.871 -> 0000061076 [sys.power] TRACE: re-enabling charging
20:44:27.905 -> 0000061122 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
20:44:28.821 -> 0000062037 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
20:44:34.119 -> 0000067300 [ncp.at] TRACE: > AT+CEREG?
20:44:34.157 -> 0000067349 [ncp.at] TRACE: < +CEREG: 2,3
20:44:34.157 -> 0000067349 [ncp.at] TRACE: < OK
20:44:49.273 -> 0000082450 [ncp.at] TRACE: > AT+CEREG?
20:44:49.311 -> 0000082499 [ncp.at] TRACE: < +CEREG: 2,3
20:44:49.311 -> 0000082500 [ncp.at] TRACE: < OK
20:45:04.327 -> 0000097501 [ncp.at] TRACE: > AT+CEREG?
20:45:04.364 -> 0000097549 [ncp.at] TRACE: < +CEREG: 2,3
20:45:04.364 -> 0000097549 [ncp.at] TRACE: < OK
20:45:19.476 -> 0000112650 [ncp.at] TRACE: > AT+CEREG?
20:45:19.511 -> 0000112699 [ncp.at] TRACE: < +CEREG: 2,3
20:45:19.511 -> 0000112699 [ncp.at] TRACE: < OK
20:45:28.864 -> 0000122037 [sys.power] TRACE: re-enabling charging
20:45:28.897 -> 0000122080 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
20:45:29.824 -> 0000122995 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
20:45:34.620 -> 0000127800 [ncp.at] TRACE: > AT+CEREG?
20:45:34.656 -> 0000127849 [ncp.at] TRACE: < +CEREG: 2,3
20:45:34.656 -> 0000127850 [ncp.at] TRACE: < OK
20:45:49.665 -> 0000142851 [ncp.at] TRACE: > AT+CEREG?
20:45:49.699 -> 0000142899 [ncp.at] TRACE: < +CEREG: 2,3
20:45:49.699 -> 0000142899 [ncp.at] TRACE: < OK
20:46:04.814 -> 0000158000 [ncp.at] TRACE: > AT+CEREG?
20:46:04.849 -> 0000158049 [ncp.at] TRACE: < +CEREG: 2,3
20:46:04.849 -> 0000158050 [ncp.at] TRACE: < OK
20:46:19.856 -> 0000173051 [ncp.at] TRACE: > AT+CEREG?
20:46:19.892 -> 0000173099 [ncp.at] TRACE: < +CEREG: 2,3
20:46:19.892 -> 0000173100 [ncp.at] TRACE: < OK
20:46:29.822 -> 0000182996 [sys.power] TRACE: re-enabling charging
20:46:29.858 -> 0000183037 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
20:46:30.789 -> 0000183970 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
20:46:35.004 -> 0000188201 [ncp.at] TRACE: > AT+CEREG?
20:46:35.072 -> 0000188252 [ncp.at] TRACE: < +CEREG: 2,3
20:46:35.072 -> 0000188253 [ncp.at] TRACE: < OK
20:46:50.164 -> 0000203353 [ncp.at] TRACE: > AT+CEREG?
20:46:50.202 -> 0000203402 [ncp.at] TRACE: < +CEREG: 2,3
20:46:50.202 -> 0000203403 [ncp.at] TRACE: < OK
20:47:05.319 -> 0000218503 [ncp.at] TRACE: > AT+CEREG?
20:47:05.356 -> 0000218552 [ncp.at] TRACE: < +CEREG: 2,3
20:47:05.356 -> 0000218553 [ncp.at] TRACE: < OK
20:47:20.473 -> 0000233653 [ncp.at] TRACE: > AT+CEREG?
20:47:20.510 -> 0000233702 [ncp.at] TRACE: < +CEREG: 2,3

#30

How long have you waited for it to connect with the Hologram SIM? I’d leave it sitting over-night to be sure.


#31

Can’t hurt, right? I’ll leave it on overnight and see what happens.

I’ve let it run about 20 min each on AT&T and Verizon.


#32

It looks about 90 seconds to connect to Verizon with the Hologram SIM on the Boron LTE:

  • External SIM selected
  • Carrier (AT+UMNOPROF) explicitly set to 3
  • APN set to “hologram”

I’m pretty sure AT&T never works with the Hologram SIM with LTE Cat M1. That appears to be the case with other hardware as well, not just the Boron, from searching their forums. That’s how I determined that you need to set the carrier.

Also make sure you do a Cellular.on() before issuing the three AT commands listed above. You should do it without enabling the system thread, otherwise the commands will silently fail because the modem is not fully initialized yet.


#33

Hi, Rikkas7,

Thanks for the tips. Here’s the “all-in-one” app I wrote to select the SIM, credentials, and network profile. I run this on top of boron 0.9.0 part 1, then load cloud debug to watch the action. This same app gets me back to normal operation / internal SIM by commenting / de-commenting the appropriate lines, and changing the MNO to 0.

No luck thus far with Verizon. I’m in southeast Michigan – the gang’s all here, MNO-wise, but you never know. I’ll take my Verizon-intending Boron on a ride today and see what happens.

I see from other Interweb users that Verizon is a good “go-to” network for Hologram users on a variety of platforms.

//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 = 3;    

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() {
}

#34

That code looks correct. You could also try capturing a Boron cloud debug log after running the code above.


#35

Fresh debug output – just re-compiled, re-ran. Had this running overnight, as well.

THANK YOU for cloud debug.bin. Very interesting and helpful to see the gears turning.

Here’s the debug from minutes ago, from board power-on to modem reset.

particle flash --usb system-part1-0.9.0-boron.bin
particle flash --usb firmware.bin  (my app in the post above).
particle flash --usb boron-clouddebug.bin

Is there such a thing as a “stale” SIM? I’ve tried two different Hologram SIM’s. Both are active w/ Hologram, both work on 3G (ATT & TMO), but neither have ever connected to Verizon. Each SIM roughly 2 years old.

10:14:55.857 -> clouddebug: press letter corresponding to the command
10:14:55.857 -> a - enter APN for 3rd-party SIM card
10:14:55.857 -> k - set keep-alive value
10:14:55.857 -> c - show carriers at this location
10:14:55.857 -> t - run normal tests (occurs automatically after 10 seconds)
10:14:55.857 -> or tap the MODE button once to show carriers
10:15:05.852 -> starting tests...
10:15:05.852 -> turning cellular on...
10:15:05.852 -> 0000015004 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
10:15:11.004 -> 0000020172 [hal] INFO: Using external Nano SIM card
10:15:11.074 -> 0000020221 [gsm0710muxer] INFO: Starting GSM07.10 muxer
10:15:11.074 -> 0000020222 [gsm0710muxer] INFO: Openning mux channel 0
10:15:11.074 -> 0000020223 [gsm0710muxer] INFO: GSM07.10 muxer thread started
10:15:11.074 -> deviceID=e00fce680f32a31afe83fc37
10:15:11.110 -> 0000020274 [gsm0710muxer] INFO: Resuming channel 0
10:15:11.110 -> 0000020275 [gsm0710muxer] INFO: Openning mux channel 1
10:15:11.220 -> 0000020376 [gsm0710muxer] INFO: Resuming channel 1
10:15:11.220 -> 0000020377 [gsm0710muxer] INFO: Resuming channel 1
10:15:11.331 -> manufacturer=u-blox
10:15:11.365 -> model=SARA-R410M-02B
10:15:11.439 -> firmware version=L0.0.00.00.05.06 [Feb 03 2018 13:00:41]
10:15:11.478 -> ordering code=SARA-R410M-02B
10:15:11.512 -> IMEI=3527530902XXXX... [redacted]
10:15:11.582 -> IMSI=u-blox
10:15:11.615 -> ICCID=894450180517XXXXX... [redacted]
10:15:11.615 -> 0000020780 [app] INFO: enabling trace logging
10:15:11.615 -> attempting to connect to the cellular network...
10:15:11.615 -> 0000020783 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
10:15:11.615 -> 0000020783 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
10:15:11.615 -> 0000020786 [hal] TRACE: PPP netif -> 8
10:15:11.615 -> 0000020786 [net.ifapi] INFO: Netif pp3 state UP
10:15:11.615 -> 0000020786 [net.ifapi] INFO: Netif pp3 state UP
10:15:11.615 -> 0000020789 [hal] TRACE: PPP thread event LOWER_DOWN
10:15:11.615 -> 0000020790 [hal] TRACE: PPP thread event ADM_DOWN
10:15:11.653 -> 0000020791 [hal] TRACE: PPP thread event ADM_UP
10:15:11.653 -> 0000020793 [hal] TRACE: State NONE -> READY
10:15:11.653 -> 0000020794 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","hologram"
10:15:11.653 -> 0000020796 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
10:15:11.653 -> 0000020796 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
10:15:11.691 -> 0000020829 [ncp.at] TRACE: < OK
10:15:11.691 -> 0000020830 [ncp.at] TRACE: > AT+CEREG=2
10:15:11.728 -> 0000020879 [ncp.at] TRACE: < OK
10:15:11.728 -> 0000020880 [hal] TRACE: NCP connection state changed: 1
10:15:11.728 -> 0000020881 [net.pppncp] TRACE: NCP event 2
10:15:11.728 -> 0000020882 [net.pppncp] TRACE: State changed event: 1
10:15:11.728 -> 0000020883 [hal] TRACE: PPP thread event LOWER_DOWN
10:15:11.728 -> 0000020884 [ncp.at] TRACE: > AT+COPS=0
10:15:11.762 -> 0000020929 [ncp.at] TRACE: < OK
10:15:11.762 -> 0000020930 [ncp.at] TRACE: > AT+CEREG?
10:15:11.762 -> 0000020931 [ncp.at] TRACE: < +CEREG: 2
10:15:11.833 -> 0000020979 [ncp.at] TRACE: < +CEREG: 2,2
10:15:11.833 -> 0000020980 [ncp.at] TRACE: < OK
10:15:26.843 -> 0000035981 [ncp.at] TRACE: > AT+CEREG?
10:15:26.881 -> 0000036029 [ncp.at] TRACE: < +CEREG: 2,2
10:15:26.881 -> 0000036030 [ncp.at] TRACE: < OK
10:15:41.876 -> 0000051030 [ncp.at] TRACE: > AT+CEREG?
10:15:41.909 -> 0000051079 [ncp.at] TRACE: < +CEREG: 2,2
10:15:41.909 -> 0000051080 [ncp.at] TRACE: < OK
10:15:51.766 -> 0000060906 [sys.power] TRACE: re-enabling charging
10:15:51.800 -> 0000060948 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
10:15:52.162 -> 0000061323 [sys.power] TRACE: Battery state CHARGED -> CHARGING
10:15:52.195 -> 0000061352 [sys.power] TRACE: Battery state CHARGING -> CHARGED
10:15:52.669 -> 0000061812 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
10:15:56.913 -> 0000066081 [ncp.at] TRACE: > AT+CEREG?
10:15:56.984 -> 0000066132 [ncp.at] TRACE: < +CEREG: 2,2
10:15:56.984 -> 0000066133 [ncp.at] TRACE: < OK
10:16:12.083 -> 0000081233 [ncp.at] TRACE: > AT+CEREG?
10:16:12.116 -> 0000081282 [ncp.at] TRACE: < +CEREG: 2,2
10:16:12.116 -> 0000081283 [ncp.at] TRACE: < OK
10:16:27.132 -> 0000096283 [ncp.at] TRACE: > AT+CEREG?
10:16:27.165 -> 0000096332 [ncp.at] TRACE: < +CEREG: 2,2
10:16:27.165 -> 0000096333 [ncp.at] TRACE: < OK
10:16:42.170 -> 0000111333 [ncp.at] TRACE: > AT+CEREG?
10:16:42.240 -> 0000111382 [ncp.at] TRACE: < +CEREG: 2,2
10:16:42.240 -> 0000111383 [ncp.at] TRACE: < OK
10:16:52.670 -> 0000121813 [sys.power] TRACE: re-enabling charging
10:16:52.708 -> 0000121854 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
10:16:53.640 -> 0000122786 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
10:16:57.227 -> 0000126387 [ncp.at] TRACE: > AT+CEREG?
10:16:57.263 -> 0000126432 [ncp.at] TRACE: < +CEREG: 2,2
10:16:57.263 -> 0000126433 [ncp.at] TRACE: < OK
10:17:12.387 -> 0000141533 [ncp.at] TRACE: > AT+CEREG?
10:17:12.421 -> 0000141582 [ncp.at] TRACE: < +CEREG: 2,2
10:17:12.421 -> 0000141583 [ncp.at] TRACE: < OK
10:17:27.529 -> 0000156683 [ncp.at] TRACE: > AT+CEREG?
10:17:27.566 -> 0000156732 [ncp.at] TRACE: < +CEREG: 2,2
10:17:27.566 -> 0000156733 [ncp.at] TRACE: < OK
10:17:42.561 -> 0000171734 [ncp.at] TRACE: > AT+CEREG?
10:17:42.631 -> 0000171782 [ncp.at] TRACE: < +CEREG: 2,2
10:17:42.631 -> 0000171783 [ncp.at] TRACE: < OK
10:17:53.632 -> 0000182787 [sys.power] TRACE: re-enabling charging
10:17:53.665 -> 0000182827 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
10:17:54.583 -> 0000183742 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
10:17:57.611 -> 0000186783 [ncp.at] TRACE: > AT+CEREG?
10:17:57.681 -> 0000186832 [ncp.at] TRACE: < +CEREG: 2,2
10:17:57.681 -> 0000186833 [ncp.at] TRACE: < OK
10:18:12.679 -> 0000201834 [ncp.at] TRACE: > AT+CEREG?
10:18:12.713 -> 0000201882 [ncp.at] TRACE: < +CEREG: 2,2
10:18:12.713 -> 0000201883 [ncp.at] TRACE: < OK
10:18:27.726 -> 0000216883 [ncp.at] TRACE: > AT+CEREG?
10:18:27.764 -> 0000216932 [ncp.at] TRACE: < +CEREG: 2,2
10:18:27.764 -> 0000216933 [ncp.at] TRACE: < OK
10:18:42.788 -> 0000231933 [ncp.at] TRACE: > AT+CEREG?
10:18:42.824 -> 0000231982 [ncp.at] TRACE: < +CEREG: 2,2
10:18:42.824 -> 0000231983 [ncp.at] TRACE: < OK
10:18:54.593 -> 0000243743 [sys.power] TRACE: re-enabling charging
10:18:54.630 -> 0000243782 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
10:18:55.565 -> 0000244715 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
10:18:57.836 -> 0000246984 [ncp.at] TRACE: > AT+CEREG?
10:18:57.874 -> 0000247033 [ncp.at] TRACE: < +CEREG: 2,2
10:18:57.874 -> 0000247034 [ncp.at] TRACE: < OK
10:19:12.864 -> 0000262035 [ncp.at] TRACE: > AT+CEREG?
10:19:12.936 -> 0000262083 [ncp.at] TRACE: < +CEREG: 2,2
10:19:12.936 -> 0000262084 [ncp.at] TRACE: < OK
10:19:27.928 -> 0000277085 [ncp.at] TRACE: > AT+CEREG?
10:19:28.031 -> 0000277183 [ncp.at] TRACE: < +CEREG: 2,2
10:19:28.031 -> 0000277184 [ncp.at] TRACE: < OK
10:19:43.011 -> 0000292184 [ncp.at] TRACE: > AT+CEREG?
10:19:43.085 -> 0000292233 [ncp.at] TRACE: < +CEREG: 2,2
10:19:43.085 -> 0000292234 [ncp.at] TRACE: < OK
10:19:55.544 -> 0000304716 [sys.power] TRACE: re-enabling charging
10:19:55.582 -> 0000304756 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
10:19:56.548 -> 0000305688 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
10:19:58.158 -> 0000307334 [ncp.at] TRACE: > AT+CEREG?
10:19:58.230 -> 0000307385 [ncp.at] TRACE: < +CEREG: 2,2
10:19:58.230 -> 0000307386 [ncp.at] TRACE: < OK
10:20:13.219 -> 0000322386 [ncp.at] TRACE: > AT+CEREG?
10:20:13.291 -> 0000322435 [ncp.at] TRACE: < +CEREG: 2,2
10:20:13.291 -> 0000322436 [ncp.at] TRACE: < OK
10:20:13.291 -> 0000322436 [hal] WARN: Resetting the modem due to the network registration timeout
10:20:13.291 -> 0000322436 [hal] WARN: Resetting the modem due to the network registration timeout
10:20:13.291 -> 0000322439 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
10:20:13.291 -> 0000322439 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
10:20:13.291 -> 0000322441 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
10:20:13.291 -> 0000322441 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
10:20:13.291 -> 0000322443 [gsm0710muxer] INFO: Closing all muxed channels
10:20:13.291 -> 0000322443 [gsm0710muxer] INFO: Closing all muxed channels
10:20:13.291 -> 0000322444 [gsm0710muxer] INFO: Closing mux channel 1
10:20:13.291 -> 0000322444 [gsm0710muxer] INFO: Closing mux channel 1
10:20:13.291 -> 0000322446 [gsm0710muxer] INFO: Muxed channel 2 already closed
10:20:13.291 -> 0000322446 [gsm0710muxer] INFO: Muxed channel 2 already closed
10:20:13.291 -> 0000322448 [gsm0710muxer] INFO: Muxed channel 3 already closed
10:20:13.291 -> 0000322448 [gsm0710muxer] INFO: Muxed channel 3 already closed
10:20:13.291 -> 0000322450 [gsm0710muxer] INFO: Muxed channel 4 already closed
10:20:13.291 -> 0000322450 [gsm0710muxer] INFO: Muxed channel 4 already closed
10:20:13.399 -> 0000322552 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
10:20:13.399 -> 0000322552 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
10:20:13.433 -> 0000322604 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
10:20:13.433 -> 0000322604 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
10:20:13.433 -> 0000322606 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
10:20:13.433 -> 0000322606 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
10:20:13.433 -> 0000322609 [gsm0710muxer] INFO: GSM07.10 muxer stopped
10:20:13.433 -> 0000322609 [gsm0710muxer] INFO: GSM07.10 muxer stopped
10:20:13.433 -> 0000322610 [hal] TRACE: Hard resetting the modem

#36

Sweet Success

I guess there really IS such a thing as a “stale” SIM.

Solution: A new Hologram SIM, and activated 15 minutes prior to putting into Boron LTE in the past hour.

Result: Verizon connected in 122 sec. (happy, breathing cyan).

I will do some more futzing around with various parameters and report back. So for now, call it good. More to follow tonight.


#37

You should do it without enabling the system thread, otherwise the commands will silently fail because the modem is not fully initialized yet.

Is there any way to check and see if the modem is fully initialized if System_Thread is required? If I were to use Semi-Automatic mode, but only attempt the modem commands after some period of time, would that be a workable workaround?


#38

Supporting what Wayne said; looking at Telstra’s coverage map it appears as though they have better coverage for Cat M1 than regular 3G/4G or at least this is the case in my area of rural Australia.

https://www.telstra.com.au/business-enterprise/solutions/internet-of-things/iot-coverage


#39

Gizzard, You are right. Cat M1 and NB1 will have better range due to the lower bandwidth, so therefore much larger coverage. Each tower will have a larger range profile with Cat M1/NB1.


#40

UPDATE on Hologram SIM in Boron LTE:

Now functioning on AT&T and Verizon.

Used my little “all-in-one” app above, and a fresh new SIM from Hologram.

Old SIM works great on 3G and Arduino MKR NB 1500 (Cat-M1), but not on Particle.