I am sorry to hear about the difficulty with your system. It sounds like either a) the firmware on the control board has been overwritten, but the Teensy microcontroller is still ok; or b) the Teensy microcontroller has failed.
I would be happy to set up a Google Hangout, Skype, or phone chat with you to help troubleshoot the issue. First, we could check for scenario (a) by downloading the latest control board firmware and trying to manually flash the firmware while manually pressing the programming button on the Teensy at the right time. Failing that, we would be happy to promptly ship you a replacement control board (we have more ready in stock).
Please let me know if you are available for a call either today until 5PM EDT or any day next week 9AM-5PM EDT.
Thanks for your patience as we work through this issue!
Christian Fobel, PhD, CTD
Sci-Bots Inc. | https://sci-bots.com
On Thursday, May 10, 2018 at 8:41:45 PM UTC-4, meli…@sjsu.edu wrote:
Thanks for your quick response earlier! Erika & co. were able to complete the diagnostics and generate a self-test report (attached), but resumed testing later in the day and encountered difficulty. Specifically, the computer that’s communicating with DropBot is no longer detecting anything when we plug the DropBot into a USB port. We are running on a Windows machine, so opened up Device Manager to watch what would happen when we plugged in. DM refreshes when the “Prog” button is pressed on the DropBot (suggesting some signs of life), but the COM port does not show up in DM. Is there any way to check the connectivity to the Arduino or make sure it’s not fried somehow?
On Thursday, May 10, 2018 at 11:52:05 AM UTC-7, Ryan Fobel wrote:
It sounds like there may be a firmware version mismatch. Can you try going through the steps listed here:
You can start at step 9 and if that doesn’t work, repeat the process starting from step 1.
Ryan Fobel, PhD, CEO
Sci-Bots Inc. | http://sci-bots.com
On Thu, May 10, 2018 at 2:41 PM, erik...@sjsu.edu wrote:
Hi Dr. Fobel!
I’m a graduate student working with Professor Simon at San Jose State University. We’re having a bit of a problem with our DropBot.
We were able to install and launch Microdrop and a status line says “Not Connected”. Under the tools menu, there are no options.
Windows device manager recognized that a device was connected to the COM port but it won’t recognize the Arduino.
We tried the software on Windows 7 and Windows 10 as an administrator.
You received this message because you are subscribed to the Google Groups “dropbot-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropbot-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.