None of my Boron LTE's will connect to cloud

I have (3) Boron LTE’s using internal Particle SIM that I haven’t used since late January.
System firmware version is 0.8.0-rc.27

Seeing the 0.9.0 firmware release yesterday, it’s time to resume testing.
Problem is that none of the (3) Borons will establish a cellular connection… blinking green, before making any changes to previously working Borons.
All (3) Still blink green when booting into safe mode.

I updated my IOS Particle app and tried the Device Setup again for each of the 3.
They get stuck at “Connecting to the internet via cellular”.

I have not tried to Deactivate or Unclaim any of the Boron LTEs.
All (3) SIMS are shown as ACTIVE in the Particle Console.

I also updated one Boron LTE (named Boron02) to 0.9.0 via:
• download the 0.9.0 system, Tinker, and bootloader .bin files from the repo
• DFU Mode
• particle flash --usb system-part1-0.9.0-boron.bin
• particle flash --usb tinker-0.9.0-boron.bin
• Listening mode
• particle flash --serial bootloader-0.9.0-boron.bin

Boron02 still wont establish a Cellular Connection in Safe Mode, or IOS App.

Serial Output for Boron02 after 0.9.0 HERE

C:\CLI>particle identify
Your device id is e00fce684f0f2f6b82f40312
Your IMEI is 352753090217819
Your ICCID is 89014103271226456372
Your system firmware version is 0.9.0

C:\CLI>particle serial inspect
Platform: 13
Modules
Bootloader module #0 - version 300, main location, 49152 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 403, main location, 671744 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
Bootloader module #0 - version 101
undefined module #0 - version 0
User module #1 - version 5, main location, 131072 bytes max size
UUID: 493ABD05C2F1B20405140EBFD39C5412C7ACE88F4A14C20B3A7E7D5184FBE3FD
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 403
undefined module #0 - version 0
empty - factory location, 131072 bytes max size

My next thought was something got crosswired during the last Billing Cycle, so I opened up a brand new Boron LTE. Same symptoms, it times-out at “Connecting to the internet via cellular” in the IOS App, after successfully activating the Particle SIM.

I’m starting to wonder if my location has lost LTE service somehow since late January.

I found the Boron Cloud Debug, Here, but it’s built on 0.8.0-rc.25
Also, the 0.9.0 release has a couple of options that looks like they could be useful in my situation, but I’m not sure which direction to take now.
image

Any advice or recommendations are greatly appreciated.

2 Likes

hey Ryan!
you may want to check this out:

Thanks @gusgonnet,
I’ve let them cook for hours.

2 Likes

same here. Patience is wearing out with the mesh network

2 Likes

I just took a Boron for a ride in my truck. It connected in Safe Mode a few miles away from my office.
It stayed connected when I returned to my office.
I reset the Boron, and it is back to blinking green at my office.

My problems may be that the LTE network has changed on me at my office.

Side Note: This Boron has previously performed over 10,000 Cellular Connections in a Trial that averaged 12 seconds per Cellular & Cloud connection. None on the 10,000 previously took longer that 42 seconds at my office during that trial.
Now I’m dead in the water.

1 Like

When you reset the Boron at the office, did you put it into Safe mode?

Yes, also tried a sweep with a 11 dBi Yagi. Nothing but Blinking Green.
I’ll take a few more Borons for a ride tomorrow and leave them connected when I bring them back to the office for more debugging.

it is my opinion that at&t doesn’t take kindly to spamming connection attempts. the thing i do not know is if they block at the network level or the tower level. but the 10,000 connection thing is just very questionable IMO. sorry to say it kinda reflects poorly on the IoT community in general. YMMV.

1 Like

Good Point @dkryder,
Although that trial was 3 months ago, and I wouldn’t think that 1 connection per minute would cause any stress to a tower or infrastructure.
But you bring up a good point indeed, this could be self inflicted.
Hmmm…

With a Boron LTE at my office, boron-CloudDebug seems to keep repeating:

 [ncp.at] TRACE: > AT+CEREG?
 [ncp.at] TRACE: < +CEREG: 2,2

Does anything in the Log below point towards the local Cell Tower “banning” my devices from registering on the network?

Full Debug Log
starting tests...
turning cellular on...
0000015001 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000021171 [hal] INFO: Using internal SIM card
0000021225 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000021226 [gsm0710muxer] INFO: Openning mux channel 0
0000021226 [gsm0710muxer] INFO: GSM07.10 muxer thread started
deviceID=e00fce68341c7d06e82f3c09
0000021276 [gsm0710muxer] INFO: Resuming channel 0
0000021277 [gsm0710muxer] INFO: Openning mux channel 1
0000021377 [gsm0710muxer] INFO: Resuming channel 1
0000021378 [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=352753091102150
IMSI=u-blox
ICCID=89014103259631200022
0000021779 [app] INFO: enabling trace logging
attempting to connect to the cellular network...
0000021781 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000021781 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000021782 [hal] TRACE: PPP netif -> 8
0000021783 [net.ifapi] INFO: Netif pp3 state UP
0000021783 [net.ifapi] INFO: Netif pp3 state UP
0000021784 [hal] TRACE: PPP thread event LOWER_DOWN
0000021784 [hal] TRACE: PPP thread event ADM_DOWN
0000021785 [hal] TRACE: PPP thread event ADM_UP
0000021785 [hal] TRACE: State NONE -> READY
0000021787 [ncp.at] TRACE: > AT+CIMI
0000021789 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000021789 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000021828 [ncp.at] TRACE: < 310410963120002
0000021829 [ncp.at] TRACE: < OK
0000021830 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","10569.mcs"
0000021878 [ncp.at] TRACE: < OK
0000021879 [ncp.at] TRACE: > AT+CEREG=2
0000021928 [ncp.at] TRACE: < OK
0000021929 [hal] TRACE: NCP connection state changed: 1
0000021929 [net.pppncp] TRACE: NCP event 2
0000021929 [net.pppncp] TRACE: State changed event: 1
0000021930 [ncp.at] TRACE: > AT+COPS=0
0000021930 [hal] TRACE: PPP thread event LOWER_DOWN
0000021978 [ncp.at] TRACE: < OK
0000021979 [ncp.at] TRACE: > AT+CEREG?
0000022028 [ncp.at] TRACE: < +CEREG: 2,0
0000022029 [ncp.at] TRACE: < OK
0000022728 [ncp.at] TRACE: < +CEREG: 2
0000037128 [ncp.at] TRACE: > AT+CEREG?
0000037179 [ncp.at] TRACE: < +CEREG: 2,2
0000037180 [ncp.at] TRACE: < OK
0000052279 [ncp.at] TRACE: > AT+CEREG?
0000052330 [ncp.at] TRACE: < +CEREG: 2,2
0000052331 [ncp.at] TRACE: < OK
0000060969 [sys.power] TRACE: re-enabling charging
0000061972 [sys.power] TRACE: re-enabling charging
0000062975 [sys.power] TRACE: re-enabling charging
0000063978 [sys.power] TRACE: re-enabling charging
0000064981 [sys.power] TRACE: re-enabling charging
0000065984 [sys.power] TRACE: re-enabling charging
0000066567 [sys.power] TRACE: Battery state DISCONNECTED -> CHARGED
0000067331 [ncp.at] TRACE: > AT+CEREG?
0000067388 [ncp.at] TRACE: < +CEREG: 2,2
0000067389 [ncp.at] TRACE: < OK
0000082488 [ncp.at] TRACE: > AT+CEREG?
0000082539 [ncp.at] TRACE: < +CEREG: 2,2
0000082540 [ncp.at] TRACE: < OK
0000097540 [ncp.at] TRACE: > AT+CEREG?
0000097589 [ncp.at] TRACE: < +CEREG: 2,2
0000097590 [ncp.at] TRACE: < OK
0000112590 [ncp.at] TRACE: > AT+CEREG?
0000112639 [ncp.at] TRACE: < +CEREG: 2,2
0000112640 [ncp.at] TRACE: < OK
0000127739 [ncp.at] TRACE: > AT+CEREG?
0000127790 [ncp.at] TRACE: < +CEREG: 2,2
0000127791 [ncp.at] TRACE: < OK
0000142890 [ncp.at] TRACE: > AT+CEREG?
0000142941 [ncp.at] TRACE: < +CEREG: 2,2
0000142942 [ncp.at] TRACE: < OK
0000158041 [ncp.at] TRACE: > AT+CEREG?
0000158092 [ncp.at] TRACE: < +CEREG: 2,2
0000158093 [ncp.at] TRACE: < OK
0000173192 [ncp.at] TRACE: > AT+CEREG?
0000173243 [ncp.at] TRACE: < +CEREG: 2,2
0000173244 [ncp.at] TRACE: < OK
0000188343 [ncp.at] TRACE: > AT+CEREG?
0000188394 [ncp.at] TRACE: < +CEREG: 2,2
0000188395 [ncp.at] TRACE: < OK
0000203494 [ncp.at] TRACE: > AT+CEREG?
0000203545 [ncp.at] TRACE: < +CEREG: 2,2
0000203546 [ncp.at] TRACE: < OK
0000218645 [ncp.at] TRACE: > AT+CEREG?
0000218696 [ncp.at] TRACE: < +CEREG: 2,2
0000218697 [ncp.at] TRACE: < OK
0000233697 [ncp.at] TRACE: > AT+CEREG?
0000233746 [ncp.at] TRACE: < +CEREG: 2,2
0000233747 [ncp.at] TRACE: < OK
0000248747 [ncp.at] TRACE: > AT+CEREG?
0000248796 [ncp.at] TRACE: < +CEREG: 2,2
0000248797 [ncp.at] TRACE: < OK
0000263797 [ncp.at] TRACE: > AT+CEREG?
0000263896 [ncp.at] TRACE: < +CEREG: 2,2
0000263897 [ncp.at] TRACE: < OK
0000278996 [ncp.at] TRACE: > AT+CEREG?
0000279047 [ncp.at] TRACE: < +CEREG: 2,2
0000279048 [ncp.at] TRACE: < OK
0000294147 [ncp.at] TRACE: > AT+CEREG?
0000294198 [ncp.at] TRACE: < +CEREG: 2,2
0000294199 [ncp.at] TRACE: < OK
0000309298 [ncp.at] TRACE: > AT+CEREG?
0000309349 [ncp.at] TRACE: < +CEREG: 2,2
0000309350 [ncp.at] TRACE: < OK
0000324449 [ncp.at] TRACE: > AT+CEREG?
0000324500 [ncp.at] TRACE: < +CEREG: 2,2
0000324501 [ncp.at] TRACE: < OK
0000324501 [hal] WARN: Resetting the modem due to the network registration timeout
0000324501 [hal] WARN: Resetting the modem due to the network registration timeout
0000324502 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000324502 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000324503 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000324503 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000324504 [gsm0710muxer] INFO: Closing all muxed channels
0000324504 [gsm0710muxer] INFO: Closing all muxed channels
0000324504 [gsm0710muxer] INFO: Closing mux channel 1
0000324504 [gsm0710muxer] INFO: Closing mux channel 1
0000324505 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000324505 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000324506 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000324506 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000324507 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000324507 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000324607 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000324607 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000324658 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000324658 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000324659 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000324659 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000324660 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000324660 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000324661 [hal] TRACE: Hard resetting the modem
0000335660 [hal] TRACE: Powering modem on
0000335810 [hal] TRACE: Modem powered on
0000335810 [hal] TRACE: Setting UART voltage translator state 0
0000335811 [hal] TRACE: Powering modem off
0000335811 [hal] TRACE: Setting UART voltage translator state 0
0000347411 [hal] ERROR: Failed to power off modem
0000347411 [hal] ERROR: Failed to power off modem
0000347412 [hal] TRACE: NCP state changed: 0
0000347412 [net.pppncp] TRACE: NCP event 1
0000347512 [hal] TRACE: Modem already on
0000347513 [hal] TRACE: Setting UART voltage translator state 1
0000348513 [ncp.at] TRACE: > AT
0000348518 [ncp.at] TRACE: < OK
0000349519 [hal] TRACE: NCP ready to accept AT commands
0000349519 [ncp.at] TRACE: > AT+UGPIOC?
0000349524 [ncp.at] TRACE: < +UGPIOC:
0000349525 [ncp.at] TRACE: < 16,255
0000349526 [ncp.at] TRACE: < 19,255
0000349526 [ncp.at] TRACE: < 23,0
0000349527 [ncp.at] TRACE: < 24,255
0000349528 [ncp.at] TRACE: < 25,255
0000349528 [ncp.at] TRACE: < 42,255
0000349529 [ncp.at] TRACE: < OK
0000349529 [ncp.at] TRACE: > AT+UGPIOR=23
0000349535 [ncp.at] TRACE: < +UGPIOR: 23,1
0000349536 [ncp.at] TRACE: < OK
0000349536 [hal] INFO: Using internal SIM card
0000349536 [hal] INFO: Using internal SIM card
0000349536 [ncp.at] TRACE: > AT+CPIN?
0000349541 [ncp.at] TRACE: < +CPIN: READY
0000349542 [ncp.at] TRACE: < OK
0000349542 [ncp.at] TRACE: > AT+CCID
0000349548 [ncp.at] TRACE: < +CCID: 89014103259631200022
0000349549 [ncp.at] TRACE: < OK
0000349549 [ncp.at] TRACE: > AT+COPS=2
0000349562 [ncp.at] TRACE: < OK
0000349562 [ncp.at] TRACE: > AT+CEDRXS=0
0000349567 [ncp.at] TRACE: < OK
0000349567 [ncp.at] TRACE: > AT+CPSMS=0
0000349572 [ncp.at] TRACE: < OK
0000349572 [ncp.at] TRACE: > AT+CEDRXS?
0000349578 [ncp.at] TRACE: < +CEDRXS: 2,"1001"
0000349580 [ncp.at] TRACE: < +CEDRXS: 5,"1001"
0000349580 [ncp.at] TRACE: < OK
0000349581 [ncp.at] TRACE: > AT+CPSMS?
0000349588 [ncp.at] TRACE: < +CPSMS:0,,,"01100000","00000000"
0000349588 [ncp.at] TRACE: < OK
0000349589 [ncp.at] TRACE: > AT+CMUX=0,0,,1509,,,,,
0000349595 [ncp.at] TRACE: < OK
0000349596 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000349596 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000349597 [gsm0710muxer] INFO: Openning mux channel 0
0000349597 [gsm0710muxer] INFO: Openning mux channel 0
0000349597 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000349597 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000349648 [gsm0710muxer] INFO: Resuming channel 0
0000349648 [gsm0710muxer] INFO: Resuming channel 0
0000349649 [gsm0710muxer] INFO: Openning mux channel 1
0000349649 [gsm0710muxer] INFO: Openning mux channel 1
0000357299 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000357299 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000357300 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000357300 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000357300 [gsm0710muxer] INFO: Closing all muxed channels
0000357300 [gsm0710muxer] INFO: Closing all muxed channels
0000357302 [gsm0710muxer] INFO: Muxed channel 1 already closed
0000357302 [gsm0710muxer] INFO: Muxed channel 1 already closed
0000357302 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000357302 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000357303 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000357303 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000357304 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000357304 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000357305 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000357305 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000364956 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000364956 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000365007 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000365007 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000365008 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000365008 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000365008 [net.pppncp] TRACE: Failed to initialize ublox NCP client: -100
0000365009 [hal] TRACE: Setting UART voltage translator state 0
0000365010 [hal] TRACE: Powering modem off
0000365010 [hal] TRACE: Setting UART voltage translator state 0
0000366710 [hal] TRACE: Modem powered off
0000366810 [hal] TRACE: Powering modem on
0000366960 [hal] TRACE: Modem powered on
0000366961 [hal] TRACE: Setting UART voltage translator state 1
0000367961 [ncp.at] TRACE: > AT
0000368961 [ncp.at] TRACE: > AT
0000369961 [ncp.at] TRACE: > AT
0000370961 [ncp.at] TRACE: > AT
0000371961 [ncp.at] TRACE: > AT
0000371965 [ncp.at] TRACE: < OK
0000372965 [hal] TRACE: NCP ready to accept AT commands
0000372965 [ncp.at] TRACE: > AT+UGPIOC?
0000372970 [ncp.at] TRACE: < +UGPIOC:
0000372970 [ncp.at] TRACE: < 16,255
0000372971 [ncp.at] TRACE: < 19,255
0000372972 [ncp.at] TRACE: < 23,0
0000372972 [ncp.at] TRACE: < 24,255
0000372973 [ncp.at] TRACE: < 25,255
0000372974 [ncp.at] TRACE: < 42,255
0000372974 [ncp.at] TRACE: < OK
0000372975 [ncp.at] TRACE: > AT+UGPIOR=23
0000372980 [ncp.at] TRACE: < +UGPIOR: 23,1
0000372981 [ncp.at] TRACE: < OK
0000372981 [hal] INFO: Using internal SIM card
0000372981 [hal] INFO: Using internal SIM card
0000372982 [ncp.at] TRACE: > AT+CPIN?
0000372987 [ncp.at] TRACE: < +CPIN: READY
0000372987 [ncp.at] TRACE: < OK
0000372988 [ncp.at] TRACE: > AT+CCID
0000372993 [ncp.at] TRACE: < +CCID: 89014103259631200022
0000372994 [ncp.at] TRACE: < OK
0000372994 [ncp.at] TRACE: > AT+COPS=2
0000373003 [ncp.at] TRACE: < OK
0000373004 [ncp.at] TRACE: > AT+CEDRXS=0
0000373010 [ncp.at] TRACE: < OK
0000373010 [ncp.at] TRACE: > AT+CPSMS=0
0000373015 [ncp.at] TRACE: < OK
0000373016 [ncp.at] TRACE: > AT+CEDRXS?
0000373021 [ncp.at] TRACE: < +CEDRXS: 2,"1001"
0000373022 [ncp.at] TRACE: < +CEDRXS: 5,"1001"
0000373023 [ncp.at] TRACE: < OK
0000373023 [ncp.at] TRACE: > AT+CPSMS?
0000373030 [ncp.at] TRACE: < +CPSMS:0,,,"01100000","00000000"
0000373031 [ncp.at] TRACE: < OK
0000373031 [ncp.at] TRACE: > AT+CMUX=0,0,,1509,,,,,
0000373038 [ncp.at] TRACE: < OK
0000373038 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000373038 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000373039 [gsm0710muxer] INFO: Openning mux channel 0
0000373039 [gsm0710muxer] INFO: Openning mux channel 0
0000373040 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000373040 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000373090 [gsm0710muxer] INFO: Resuming channel 0
0000373090 [gsm0710muxer] INFO: Resuming channel 0
0000373091 [gsm0710muxer] INFO: Openning mux channel 1
0000373091 [gsm0710muxer] INFO: Openning mux channel 1
0000373141 [gsm0710muxer] INFO: Resuming channel 1
0000373141 [gsm0710muxer] INFO: Resuming channel 1
0000373142 [gsm0710muxer] INFO: Resuming channel 1
0000373142 [gsm0710muxer] INFO: Resuming channel 1
0000373143 [ncp.at] TRACE: > AT
0000373193 [ncp.at] TRACE: < OK
0000373194 [hal] TRACE: NCP state changed: 1
0000373194 [net.pppncp] TRACE: NCP event 1
0000373194 [hal] TRACE: Muxer AT channel live
0000373195 [hal] TRACE: PPP thread event LOWER_DOWN
0000373195 [hal] TRACE: PPP thread event ADM_DOWN
0000373196 [hal] TRACE: State READY -> NONE
0000373196 [hal] TRACE: PPP thread event ADM_UP
0000373197 [hal] TRACE: State NONE -> READY
0000373199 [ncp.at] TRACE: > AT+CIMI
0000373243 [ncp.at] TRACE: < 310410963120002
0000373244 [ncp.at] TRACE: < OK
0000373244 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","10569.mcs"
0000373293 [ncp.at] TRACE: < OK
0000373294 [ncp.at] TRACE: > AT+CEREG=2
0000373343 [ncp.at] TRACE: < OK
0000373344 [hal] TRACE: NCP connection state changed: 1
0000373344 [net.pppncp] TRACE: NCP event 2
0000373344 [net.pppncp] TRACE: State changed event: 1
0000373345 [ncp.at] TRACE: > AT+COPS=0
0000373345 [hal] TRACE: PPP thread event LOWER_DOWN
0000373393 [ncp.at] TRACE: < OK
0000373394 [ncp.at] TRACE: > AT+CEREG?
0000373443 [ncp.at] TRACE: < +CEREG: 2,0
0000373444 [ncp.at] TRACE: < OK
0000374044 [ncp.at] TRACE: < +CEREG: 2
0000388444 [ncp.at] TRACE: > AT+CEREG?
0000388493 [ncp.at] TRACE: < +CEREG: 2,2
0000388494 [ncp.at] TRACE: < OK
0000403494 [ncp.at] TRACE: > AT+CEREG?
0000403543 [ncp.at] TRACE: < +CEREG: 2,2
0000403544 [ncp.at] TRACE: < OK
0000418643 [ncp.at] TRACE: > AT+CEREG?
0000418694 [ncp.at] TRACE: < +CEREG: 2,2
0000418695 [ncp.at] TRACE: < OK
0000433794 [ncp.at] TRACE: > AT+CEREG?
0000433845 [ncp.at] TRACE: < +CEREG: 2,2
0000433846 [ncp.at] TRACE: < OK
0000448846 [ncp.at] TRACE: > AT+CEREG?
0000448895 [ncp.at] TRACE: < +CEREG: 2,2
0000448896 [ncp.at] TRACE: < OK
0000463995 [ncp.at] TRACE: > AT+CEREG?
0000464046 [ncp.at] TRACE: < +CEREG: 2,2
0000464047 [ncp.at] TRACE: < OK


Thanks in advance for the troubleshooting help…

i’m not sure if this is a clue or not,

0000324501 [hal] WARN: Resetting the modem due to the network registration timeout
0000324501 [hal] WARN: Resetting the modem due to the network registration timeout

1 Like

I have confirmed the issue is Local.
My Boron LTE’s have no problem connecting to other Cell Towers when I drive them around.
Either the Cell Tower serving my Office is having Cat M1 problems, or this specific Tower has banned me (seems likely :disappointed:)

It appears that I’ll be testing Boron LTE’s with 3’rd party SIMS at my Office in the near future, but more carefully of course.

1 Like

if you know someone with a boron ask them over to your office. if they get in that might help explain what is happening. if they don’t then it is an issue with Cat M1 at your tower. unless you were the only Cat M1 at the tower and they figured the disconnects were their problem and are waiting for new equipment or other service .

Yea but didn’t he say he setup a brand new Boron and it had the same issue?

yup. he did say that. i missed it before. an indication that the local tower Cat M1 is down.