Hey Ryan,
I found 0.9.4 here: http://downloads.konekt.io/dash/system_firmware/dash_system_module_firmware_0.9.4.bin from this thread: Dash Modem Times Out and Won't Send Data After 1 Hour - #24 by HologramPat.
Is that the correct binary? If so, it does not work either. However the problem is now the reverse. We can send SMS to the cloud but we cannot send from the cloud (or API) to the device. Below is the output from the device. I used the M2 switch and verified the version only the device hung and would not complete booting (I waited 15 minutes). After I disconnected/reconnected and the device came up I could send to the cloud but not the reverse.
Output after using M2 switch:
$ cat < /dev/ttyACM0
+EVENT:LOG,37,5,DEBUG,26,Konekt Dash system init…
+EVENT:LOG,15,5,DEBUG,5,0.9.4
+EVENT:LOG,47,5,DEBUG,36,Beginning modem bootstrap process…
+EVENT:LOG,81,5,DEBUG,70,Bootstrapping (1/14): Init modem (can sometimes take several minutes).
+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
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+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
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,22,5,DEBUG,11,AT+CFUN=16
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,76,4,INFO,66,Data connection deactivated by network, possibly due to inactivity�+EVENT:LOG,37,5,DEBUG,26,Konekt Dash system init…
+EVENT:LOG,15,5,DEBUG,5,0.9.4
+EVENT:LOG,47,5,DEBUG,36,Beginning modem bootstrap process…
+EVENT:LOG,81,5,DEBUG,70,Bootstrapping (1/14): Init modem (can sometimes take several minutes).
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,36,5,DEBUG,25,Modem self-tests complete
+EVENT:LOG,46,5,DEBUG,35,Bootstrapping (2/14): Config modem.
+EVENT:LOG,47,5,DEBUG,36,Bootstrapping (3/14): Init SIM card.
+EVENT:LOG,33,5,DEBUG,22,Modem event: SIM ready
+EVENT:LOG,23,5,DEBUG,12,IMSI loaded.
+EVENT:LOG,24,5,DEBUG,13,ICCID loaded:
+EVENT:LOG,30,5,DEBUG,19,8944501006151414358
+EVENT:LOG,23,5,DEBUG,12,IMEI loaded:
+EVENT:LOG,26,5,DEBUG,15,353162070596656
+EVENT:LOG,53,5,DEBUG,42,Bootstrapping (4/14): Init event handling.
+EVENT:LOG,57,5,DEBUG,46,Bootstrapping (5/14): Wait for carrier signal.
+EVENT:LOG,36,5,DEBUG,25,Modem event: signal found
+EVENT:LOG,57,5,DEBUG,46,Bootstrapping (6/14): Establish operator link.
+EVENT:LOG,40,5,DEBUG,29,Caller-listening modem event:
+EVENT:LOG,38,5,DEBUG,27,+COPS: 0,0,“AT&T”,2
OK
+EVENT:LOG,48,5,DEBUG,37,Bootstrapping (7/14): Config network.
+EVENT:LOG,40,5,DEBUG,29,Modem event: Other (ignored):
+EVENT:LOG,32,5,DEBUG,21,+UPSND: 0,8,0
OK
+EVENT:LOG,44,5,DEBUG,33,Bootstrapping (8/14): Config APN.
+EVENT:LOG,51,5,DEBUG,40,Bootstrapping (9/14): Config IP address.
+EVENT:LOG,51,5,DEBUG,40,Bootstrapping (10/14): Link up (1 of 2).
+EVENT:LOG,51,5,DEBUG,40,Bootstrapping (11/14): Link up (2 of 2).
+EVENT:LOG,102,4,CRIT,92,Modem instruction aborted mid-instruction. This most likely is a bug and should be reported.
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,41,5,DEBUG,30,Modem event: PSD context event
+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
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,20s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,10s
+EVENT:LOG,81,5,DEBUG,70,Bootstrapping (1/14): Init modem (can sometimes take several minutes).
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,98,4,CRIT,88,Insufficient buffer while processing modem events, oldest event(s) dropped to make space
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,11,5,DEBUG,1,
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,46,5,DEBUG,35,Bootstrapping (2/14): Config modem.
+EVENT:LOG,47,5,DEBUG,36,Bootstrapping (3/14): Init SIM card.
+EVENT:LOG,23,5,DEBUG,12,IMSI loaded.
+EVENT:LOG,24,5,DEBUG,13,ICCID loaded:
+EVENT:LOG,30,5,DEBUG,19,8944501006151414358
+EVENT:LOG,23,5,DEBUG,12,IMEI loaded:
+EVENT:LOG,26,5,DEBUG,15,353162070596656
+EVENT:LOG,53,5,DEBUG,42,Bootstrapping (4/14): Init event handling.
+EVENT:LOG,57,5,DEBUG,46,Bootstrapping (5/14): Wait for carrier signal.
+EVENT:LOG,57,5,DEBUG,46,Bootstrapping (6/14): Establish operator link.
+EVENT:LOG,40,5,DEBUG,29,Caller-listening modem event:
+EVENT:LOG,22,5,DEBUG,11,+COPS: 0,0,
+EVENT:LOG,40,5,DEBUG,29,Caller-listening modem event:
+EVENT:LOG,38,5,DEBUG,27,+COPS: 0,0,“AT&T”,2
OK
+EVENT:LOG,48,5,DEBUG,37,Bootstrapping (7/14): Config network.
+EVENT:LOG,40,5,DEBUG,29,Modem event: Other (ignored):
+EVENT:LOG,32,5,DEBUG,21,+UPSND: 0,8,1
OK
+EVENT:LOG,44,5,DEBUG,33,Bootstrapping (8/14): Config APN.
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,39,5,DEBUG,28,AT+UPSD=0,1,“apn.konekt.io”
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,39,5,DEBUG,28,AT+UPSD=0,1,“apn.konekt.io”
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,39,5,DEBUG,28,AT+UPSD=0,1,“apn.konekt.io”
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,39,5,DEBUG,28,AT+UPSD=0,1,“apn.konekt.io”
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,39,5,DEBUG,28,AT+UPSD=0,1,“apn.konekt.io”
+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,60s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,50s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,40s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,30s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,20s
+EVENT:LOG,65,5,DEBUG,54,Delaying to prevent carrier frustration, please wait:
+EVENT:LOG,13,5,DEBUG,3,10s
+EVENT:LOG,81,5,DEBUG,70,Bootstrapping (1/14): Init modem (can sometimes take several minutes).
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
+EVENT:LOG,98,4,CRIT,88,Insufficient buffer while processing modem events, oldest event(s) dropped to make space
+EVENT:LOG,25,5,DEBUG,14,Modem command:
+EVENT:LOG,16,5,DEBUG,6,AT&K4
+EVENT:LOG,31,4,WARN,21,Modem command timeout
+EVENT:LOG,60,4,INFO,50,An error occurred while processing a modem command
The devices are not currently usable.
What I need to know: are your developers activity working on this and what is the ETA for a fix. Are there older versions of firmware available and if so where are they? Maybe we can find one that works.