Dash Modem Times Out and Won't Send Data After 1 Hour

Hardware (and firmware) Dash
61

Our latest System Firmware should fix the issue (0.9.4 rc2) which is what the new Dash I was testing was running on. The Dash reconnected as expected with the new system firmware.

Still working on this to verify, but the quick answer is it should not have a reconnect issue. Any Hologram board running System Firmware 0.9.4 RC2 should work.

The first batch is about 4 weeks from being available in the store :tada:

Update on Dash Pro: We are still working to discover why it was not reconnecting. When I first reported my Pro was not connecting I was under the impression that board had the latest firmware, it did not. Now I’m running the tests for a second time with the latest System Firmware.

62

Thanks folks for sticking with us through our testing and verification of this bug. We have verified this bug exists with a handful of Dash Pro units stemming from issues encountered during manufacturing. If you think yours may be one of them direct message me to discuss replacements.

In addition we have started to phase out the Dash Pro since the new Dash v1.1 will be released soon. The Dash Pro will continue to be supported by our firmware updates for at least the next 6 months.

63

I have not been having ‘Modem command timeout’ problem for the last 3 hours (it was ok before that). The problem is very similar to what Frank described on Mar 23 above. But sometimes it can go pass Bootstrapping (14/14), then keeps having Modem command timeout.

+EVENT:LOG,67,5,DEBUG,56,Bootstrapping (14/14): Enter serial passthrough mode. OK
+EVENT:LOG,38,5,DEBUG,27,Opening connection to cloud
Humidity 1: 57.30 % Temperature 1: 29.80 *C
Humidity 2: 36.00 % Temperature 2: 28.00 *C
Humidity 3: 35.00 % Temperature 3: 30.00 *C
29.8,28.0,30.0
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,22,5,DEBUG,11,AT+USOCR=6

+EVENT:LOG,31,4,WARN,21,Modem command timeout
Humidity 1: 58.20 % Temperature 1: 29.80 *C
Humidity 2: 43.00 % Temperature 2: 28.00 *C
Humidity 3: 35.00 % Temperature 3: 30.00 *C
29.8,28.0,30.0
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,22,5,DEBUG,11,AT+USOCR=6

+EVENT:LOG,31,4,WARN,21,Modem command timeout

And the scary thing is that when I send something to the Cloud, it says Socket failure!
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,44,5,DEBUG,33,AT+USOCO=0,“23.253.146.203”,9999

+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,26,5,DEBUG,15,Socket failure!
+EVENT:LOG,43,4,WARN,33,Socket failure during socket openÿ+EVENT:+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&F0

+EVENT:LOG,31,4,WARN,21,Modem command timeout

Is my Dash dead after 2 weeks of playing? The reply to Frank’s question by @Reuben was that it’s dead and I have to contact support@konekt.io. Correct?

64

Also, just to add that besides the Modem command timeout, I also have a lot of:
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,10s

65

@juipin just to clarify, is this on a Dash or Dash Pro?

66

@benstr, It’s a Dash.

67

Good news! At least for now. I pulled out the USB power and let it sit for 30 minutes or so. I just tried, and it powered up beautifully. I managed to send a few messages to the Cloud.

But can you tell me how exactly to recover from the modem failure state? I am really afraid it will come back again, and I am a little anxious about using it on my battery charging monitoring station, as the modem can get stuck in some mode for a long time.

68

Bad news. I wanted to prove that it would work again. But this time, it went ‘dead’ after 11/14:
27.2,26.0,28.0
+EVENT:LOG,51,5,DEBUG,40,Bootstrapping (11/14): Link up (2 of 2).
Humidity 1: 54.60 % Temperature 1: 27.20 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.2,26.0,28.0
Humidity 1: 55.60 % Temperature 1: 27.20 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.2,26.0,28.0
Humidity 1: 55.50 % Temperature 1: 27.20 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.2,26.0,28.0
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,24,5,DEBUG,13,AT+UPSDA=0,3

+EVENT:LOG,31,4,WARN,21,Modem command timeout
Humidity 1: 55.50 % Temperature 1: 27.20 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.2,26.0,28.0
Humidity 1: 55.40 % Temperature 1: 27.30 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.3,26.0,28.0
Humidity 1: 54.80 % Temperature 1: 27.20 *C
Humidity 2: 40.00 % Temperature 2: 26.00 *C
Humidity 3: 35.00 % Temperature 3: 28.00 *C
27.2,26.0,28.0
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,24,5,DEBUG,13,AT+UPSDA=0,3

+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,30s

69

@juipin Sorry for not asking this before, what system firmware is your Dash running on?

70

@benstr The firmware is 0.9.4. I was prompted within Arduino IDE to do the upgrade 3 days ago. Actually another problem happens after the upgrade. The IDE can no longer upload data. I asked in another thread.

71

With the new update 0.9.1 on Arduino IDE, the upload is working again! Thanks.

72

My Dash Pro has the same timeout error over and over, Battery or USB power, with or with the GPS unit. It’s on the latest firmware. It just does not work. I am in Australia if that makes a difference. I am not sure how to send a PM but how do we go about getting replacement?

+EVENT:LOG,31,4,WARN,21,Modem command timeout

73

contacted through direct message

74

Hello all, I’m really enjoying getting this up and running. It’s my first electronics project in 30 years!

I have a Dash setup with the asset tracking demo using the Adafruit GPS module and all was working well then I started getting this same modem timeout message. I moved the USB to one designed to power electronics and it started and worked for a few minutes then went back to the modem timeout issue.

I have updated the firmware to the latest. tried system and user resets. Good news is the GPS has a fix and is working well and adding the button CR1220 battery made a big difference.

Is this still an issue, tips for resolution?

Thanks.

75

Quick update. I left the Dash disconnected and powered down for about three days and tried again and its been working mostly ever since. I still see these modem error quite regularly and I think it’s still an issue but in most cases it is able to reconnect or I do a system or user reset until I can get it to connect.