I plugged the device back in my computer, and instead of saying DASH SERIAL unrecognized it’s now saying unrecognized USB device. I haven’t done nothing other than just plug it in.
Did you ever get a chance to try with a powered hub or y-cable?
Powered hub seems to have improved the situation … I am
getting messages from the Dash in the terminal.
However, messages from the terminal are not showing up in
the Konekt Dashboard. Terminal on PC message repeating over and over =
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem
bootstrapping:
+EVENT:LOG,16,5,DEBUG,6,240000
Note1: 240000 changes, counting up by 10000
Note2: I know that am on the hairy edge of cellular connectivity (probably should have been a Beta tester) … how can I tell if I am connected to a tower?
BR/Keith
I don’t have any Y-Cables, and when attached to my power USB hub it improves, but still can’t PUTTY into it.
Once there are Y-cables available I’ll definitely pick one up.
Hey Reuben, don’t Dash off, I need a some help here!
Haha
So if you’re able to get to the terminal then it sounds like you’ve resolved your driver/power issues.
Can you post the full log?
It does sound like you might just be having trouble getting a cell signal. Antenna connected?
Antenna is connected.
Log from System IC Reset:
+EVENT:LOG,37,5,DEBUG,26,Konekt Dash system init…
+EVENT:LOG,25,5,DEBUG,14,Version: 0.9.2
+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,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,60000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,50000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,40000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,30000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,20000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,15,5,DEBUG,5,10000
+EVENT:LOG,81,5,DEBUG,70,Bootstrapping (1/14): Init modem (can sometimes take several minutes).
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,16,5,DEBUG,6,120000
+EVENT:LOG,50,5,DEBUG,39,Retry delay before modem bootstrapping:
+EVENT:LOG,16,5,DEBUG,6,110000
…
Hmm, failures at step 1 are usually caused by the SIM being missing or not inserted properly or by power issues.
Can you try reseating the SIM just to rule that out?
I had a similar problem to this when i tried to use a different antenna, i guess it didn’t like the antenna impedance or something…
*Sigh!
I just received my Y cable, but still having the exact same problems (See photos above). If I plug into my USB 2 slot I get that the USB device isn’t recognized, and if I plug into my USB 3 I get that the DASH device isn’t recognized. And this is using the Y cable I ordered. So instead I decided to use my TTL serial to USB converter, but I’m not getting any information when I PUTTY into it. Maybe I’m using the wrong pinouts for the TX and RX connections but when I go to the instructions it shows for the DASH Pro and I have the DASH. I’m starting to believe that this device was sent to me not working. I hope not as I’m really excited to get programming and learn what this thing can do. Any other suggestions would appreciated or I’m just going to put this up on my shelf to collect dust disappointed.
Hmm, we do test USB serial on every board, but it’s possible that something broke during shipping. Can you contact us at support@konekt.io and we’ll see if we can swap it out for another one?
1 Like
And I’m sorry for the disappointment. We really want people to get these things and jump right into programming
OPA!!
I finally got the DASH to work. What it was, it was the driver. When I tried to install the driver it would come up as the driver wasn’t signed so Windows 10 wouldn’t allow me to install it. A friend came by and showed me how to install unsigned drivers and now I’m able to connect and start pushing data through.
I just want to publicly point out how helpful the Konekt staff was in assisting me, and also this community. Excited to start programming and sharing what I build. 
Oh, that’s great. Glad you’re up and running. We’re working to learn more about these driver issues. It’s weird that sometimes it installs automatically with no problem and sometimes you need a driver even though you might be on the same OS.
OK, my bad … let’s just say the SIM card had become dislodged.
Now I can receive SMS from my dashboard, but messages sent to
the dashboard are not showing up …
+EVENT:LOG,38,5,DEBUG,27,Opening connection to cloud
+EVENT:LOG,42,5,DEBUG,31,Data successfully sent to cloud
+EVENT:SMSRCVD,22,1/2 way to the cloud!?
Any help, greatly appreciated!
BR/Keith
I started a new topic for your issue
New topic = good idea, this thread became not being able to connect to cloud.
But, I can’t find the new topic.
Reuben, please put a link in this topic to the new one?
BR/Keith
I experienced both issues above, and wanted to share some tips:
When powering over USB, it is probably best to stick to a USB 3.0 port. Typically USB 3.0 can output 5V @ 900mA, while USB 2.0 is limited to 500mA. The datasheet for the Sara shows that peak current during a transmission (with a matched antenna) will be 1.5A @ 3.3V, which would be 990mA when converting back to 5V. So transmission should be much more reliable using USB 3.0.
Other things to think about include the amount of other USB devices that are drawing power from the PC. I would assume some of the USB ports share a common voltage regulator, so there is a higher likelihood of maxing out on current output if many other devices are connected to the PC.
This last tip may seem silly, but the quality of the USB micro cord being used to power and program the Dash by USB does make a huge difference. If its a cheap cable, it might not work.