Boron Cloud Disconnect Logs - ERROR: Event loop error 3

Troubleshooting
1

Hi,

I finally got round to running @rickkas7 Cloud debugging code with Particle.keepAlive(60) as Im using an 3rd party sim. I’m trying to identify why my Boron is dropping all the time. Here is a sample of the Serial output.

Device LTE BORON
Code: Rickkas7 Cloud debugging code

Any ideas why it is dropping,ERROR: Event loop error 3?? what is causing it?
I have looked through the forums and there are several that report this error but nothing that really says what is causing it?

Cheers

Serial monitor opened successfully:
clouddebug: press letter corresponding to the command
a - enter APN for 3rd-party SIM card
k - set keep-alive value
c - show carriers at this location
t - run normal tests (occurs automatically after 10 seconds)
or tap the MODE button once to show carriers
starting tests...
turning cellular on...
deviceID=xxxxxxxxxx
manufacturer=u-blox
model=SARA-R410M-02B
firmware version=L0.0.00.00.05.08 [Apr 17 2019 19:34:02]
ordering code=SARA-R410M-02B
IMEI=xxxxxxxxx
IMSI=u-blox
ICCID=xxxxxxxxxxx
0000021746 [app] INFO: enabling trace logging
attempting to connect to the cellular network...
connected to the cellular network in 293245 milliseconds
connected to cellular network!
operator name=
rssi=-53, qual=99
0000315200 [app] INFO: service rat=GSM mcc=65535, mnc=255, lac=0 ci=0 band=GSM 900 rssi=-121 bsic=0 arfcn=0 rxlev=0
0000315200 [app] INFO: service rat=GSM mcc=65535, mnc=255, lac=0 ci=0 band=GSM 900 rssi=-121 bsic=0 arfcn=0 rxlev=0
ping addr 8.8.8.8=0
device.spark.io=34.201.1.99
connecting to cloud
0000315854 [system] ERROR: Failed to load session data from persistent storage
0000315854 [system] ERROR: Failed to load session data from persistent storage
connected to the cloud!
0003612029 [comm.protocol] ERROR: Event loop error 3
0003612029 [comm.protocol] ERROR: Event loop error 3
0003612030 [system] WARN: Communication loop error, closing cloud socket
0003612030 [system] WARN: Communication loop error, closing cloud socket
0003904215 [system] ERROR: Failed to load session data from persistent storage
0003904215 [system] ERROR: Failed to load session data from persistent storage
0004551130 [comm.protocol] ERROR: Event loop error 3
0004551130 [comm.protocol] ERROR: Event loop error 3
0004551131 [system] WARN: Communication loop error, closing cloud socket
0004551131 [system] WARN: Communication loop error, closing cloud socket
0004703353 [system] ERROR: Failed to load session data from persistent storage
0004703353 [system] ERROR: Failed to load session data from persistent storage
0004717257 [comm.dtls] ERROR: handshake failed -6800
0004717257 [comm.dtls] ERROR: handshake failed -6800
0004717259 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004717259 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004717262 [system] WARN: Cloud handshake failed, code=17
0004717262 [system] WARN: Cloud handshake failed, code=17
0004718263 [system] ERROR: Failed to load session data from persistent storage
0004718263 [system] ERROR: Failed to load session data from persistent storage
0004734657 [comm.dtls] ERROR: handshake failed -6800
0004734657 [comm.dtls] ERROR: handshake failed -6800
0004734659 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004734659 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004734662 [system] WARN: Cloud handshake failed, code=17
0004734662 [system] WARN: Cloud handshake failed, code=17
0004735663 [system] ERROR: Failed to load session data from persistent storage
0004735663 [system] ERROR: Failed to load session data from persistent storage
0004743656 [comm.dtls] ERROR: handshake failed -1
0004743656 [comm.dtls] ERROR: handshake failed -1
0004743659 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004743659 [comm.protocol.handshake] ERROR: handshake failed with code 17
0004743662 [system] WARN: Cloud handshake failed, code=17
0004743662 [system] WARN: Cloud handshake failed, code=17
0004791107 [system] ERROR: Failed to load session data from persistent storage
0004791107 [system] ERROR: Failed to load session data from persistent storage
0004806357 [system] ERROR: Failed to determine server address
0004806357 [system] ERROR: Failed to determine server address
0004806359 [system] WARN: Cloud socket connection failed: -230
0004806359 [system] WARN: Cloud socket connection failed: -230
0004806361 [system] WARN: Internet available, Cloud not reachable!
0004806361 [system] WARN: Internet available, Cloud not reachable!
0004806363 [system] WARN: Handling cloud error: 3
0004806363 [system] WARN: Handling cloud error: 3
0004844059 [system] ERROR: Failed to load session data from persistent storage
0004844059 [system] ERROR: Failed to load session data from persistent storage
2

Hi @ric_hard!

Event loop errors occur when there’s a problem managing CoAP communication, with Error Code 3 throwing a rather generic INVALID_STATE. Would you mind opening a support ticket for this device, supplemented with your Device ID and OS version?

3

No I don’t mind. I have 40 Boron’s and have set up 5 of them and all suffer from the same thing. Plus I have another mate in a different state (Aus) and is also suffering from the same using 3rd party sims.

1 Like
5

I know I’m digging up and old thread, but LTE/cloud disconnects are causing me issues as well. Any resolution @ric_hard?

6

I put my Boron projects on hold last year due to issues like this. I’m reviving them today in hopes of seeing some improvement but after updating to the latest FW, I’m immediately seeing issues similar to those described here.

If this is a common problem, is it being addressed? If it is uncommon, are there any leads on what user-code might be causing it?

7

Negative. No solution what’s so ever. :frowning:

1 Like
8

@ric_hard, did you open a support ticket? I have had some success with other issues going that route. I have not tried for this issue yet.

1 Like
9

I’ve been in contact in the past day with Particle about this, and just sent them the connectivity community discussions I’ve been a part of over the past few months. I’ll update you on what I can find.

10

@aklein24 @trpropst only been fault finding for about a year now or when the first came out. Fault finding included access to Telstra and Ublox engineers. Even a loan EVA kit from ublox did the same. I believe its not a particle issue but more a modem / Telstra cat-M1 issue. It is not going to be resolved anytime soon. Just make sure your software can reconnect automatically and that’s the best option. sorry to be the bearer of the bad news.