Cellular WILL NOT CONNECT

Connectivity Cellular
1

Device has been connected previously, up for about a month. Note this is using the internal sim. Using cloud-debug the log is as follows. The particle console SIM status shows me “updating - please check back later”

0000038548 [ncp.at] TRACE: > AT+COPS=3,2
0000040342 [app.help] INFO: Operator Selection (COPS) Set: mode=set format (3) format=numeric (2)
0000038552 [ncp.at] TRACE: < OK
0000038553 [ncp.at] TRACE: > ATI9
0000038558 [ncp.at] TRACE: < OK
0000038559 [hal] TRACE: App firmware: 200
0000038559 [ncp.at] TRACE: > AT+IPR=115200
0000038565 [ncp.at] TRACE: < OK
0000039566 [ncp.at] TRACE: > AT
0000039570 [ncp.at] TRACE: < OK
0000039570 [ncp.at] TRACE: > AT+IFC=2,2
0000039574 [ncp.at] TRACE: < OK
0000039575 [ncp.at] TRACE: > AT
0000039578 [ncp.at] TRACE: < OK
0000039578 [ncp.at] TRACE: > AT+UMNOPROF?
0000039587 [ncp.at] TRACE: < +UMNOPROF: 2
0000040359 [app.help] INFO: Mobile Network Operator Profile (UMNOPROF): AT&T (2)
0000039587 [ncp.at] TRACE: < OK
0000039588 [ncp.at] TRACE: > AT+URAT?
0000039593 [ncp.at] TRACE: < +URAT: 7
0000039593 [ncp.at] TRACE: < OK
0000039594 [ncp.at] TRACE: > AT+CEDRXS?
0000039599 [ncp.at] TRACE: < +CEDRXS:
0000039599 [ncp.at] TRACE: < OK
0000039600 [ncp.at] TRACE: > AT+CPSMS=0
0000039606 [ncp.at] TRACE: < OK
0000039607 [ncp.at] TRACE: > AT+CMUX=0,0,,1509,,,,,
0000039615 [ncp.at] TRACE: < OK
0000039716 [ncp.at] TRACE: > AT
0000039767 [ncp.at] TRACE: < OK
0000039767 [hal] TRACE: NCP state changed: 1
0000039767 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN
0000039768 [net.ppp.client] TRACE: PPP thread event ADM_DOWN
0000039768 [net.ppp.client] TRACE: PPP thread event ADM_UP
0000039769 [net.ppp.client] TRACE: State NONE -> READY
0000039771 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","broadband"
0000040385 [app.help] INFO: PDP context definition (CGDCONT): cid=1 pdpType=IP APN=broadband
0000039817 [ncp.at] TRACE: < OK
0000039817 [ncp.at] TRACE: > AT+CEREG=2
0000040392 [app.help] INFO: EPS network (CEREG) Set to location enabled (2)
0000039867 [ncp.at] TRACE: < OK
0000039867 [hal] TRACE: NCP connection state changed: 1
0000039867 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN
0000039868 [ncp.at] TRACE: > AT+COPS=0,2
0000040402 [app.help] INFO: Operator Selection (COPS) Set: mode=automatic (0) format=numeric (2)
0000039917 [ncp.at] TRACE: < OK
0000039917 [ncp.at] TRACE: > AT+CEREG?
0000039967 [ncp.at] TRACE: < +CEREG: 2,3
0000040409 [app.help] INFO: EPS network (CEREG) Status: registration denied (3)
0000039967 [ncp.at] TRACE: < OK
0000039968 [ncp.at] TRACE: > AT+CGMI
0000040017 [ncp.at] TRACE: < OK
0000040017 [app] INFO: manufacturer: u-blox
0000040067 [app] INFO: model: SARA-R410M-02B
0000040117 [app] INFO: firmware version: L0.0.00.00.05.06 [Feb 03 2018 13:00:41]
0000040167 [app] INFO: ordering code: SARA-R410M-02B
0000040217 [app] INFO: IMEI: 352753094130851
0000040267 [app] INFO: IMSI: u-blox
0000040317 [app] INFO: ICCID: 89014103271226567723
0000040318 [app] INFO: Still trying to connect to cellular 00:06
0000040318 [app] INFO: Power source: USB Host
0000040319 [app] INFO: Battery state: disconnected, SoC: -1.00
0000050318 [app] INFO: Still trying to connect to cellular 00:16
0000050318 [app] INFO: Power source: USB Host
0000050318 [app] INFO: Battery state: disconnected, SoC: -1.00
0000054968 [ncp.at] TRACE: > AT+CEREG?
0000055017 [ncp.at] TRACE: < +CEREG: 2,3
0000055019 [app.help] INFO: EPS network (CEREG) Status: registration denied (3)
2

maybe @marekparticle can help you here?

1 Like
3

Thanks for the tag @gusgonnet!

CEREG: 2,3 is the issue - the SIM is being rejected by the tower. There are three root causes of that condition in my experience:

a) the SIM is deactivated :slight_smile: - that’s not the case here, even though it is stuck in updating. We want to fix that for you anyways - that’s a relatively benign bug we are working to remove altogether.
b) the device is acting aggressively (tbd) and has been blacklisted by the tower
c) there is some issue (e.g. with propagation to the local tower) and it no longer recognizes friend from foe

@Impel - can you open up a support ticket (support.particle.io) with:

a) your Device ID (that’s missing here, I just see ICCID which is
b) GPS location of the device
c) ID + GPS location of nearby devices that are working if possible
d) I see this handshook yesterday, so I’m assuming this disconnection happened more recently - approximate timestamp of when you took these Cloud Debug logs would be useful

and we’ll get you sorted!

2 Likes
4

@marekparticle Thanks for the speedy reply! I left the device overnight connected to a power supply, when I came back this morning it had connected to the tower. I had opened a ticket yesterday, all information included except GPS location.

The logs were taken yesterday. The device had been retrieved from the field about a week ago as it was flashing green, and yesterday was the first time it had been powered since. Spent the day combing through documentation (all day flashing green & same CEREG 2,3 error) and finally logged the logs and submitted them here and a support ticket.

Located in Calgary, Alberta, Canada & approximate timestamp would be anywhere between 10:00 and 18:00 MST

5

Can you DM me the ticket ID?

6

According to the website, I am not allowed to haha - “Sorry, you cannot send a personal message to that user.”.

My ticket ID is 99287. Thanks again!

Tyler

7

Thanks! One of our engineers will be with you shortly. :slight_smile: