We haven't come across that "freezing" error before, but it seems that
there is something suspicious going on. If it happens again, please
let us know (with a log dump if possible). Glad it worked for you
When you say "turn on the small DropBot power supply", are you
referring to the micro ATX power supply? None of the micro ATX PSU
models we have come with a switch, so I'm surprised that it would
cause a problem to have switched yours on prior to plugging in the
USB, since ours are essentially always "on". Either way, I see no
problem with the startup ordering you have proposed.
The startup-related requirements that I am aware of are:
1. all USB connections must be established before launching Microdrop
(you should be able to see the USB devices in the Windows "Device
Manager", otherwise Microdrop will be unable to connect)
2. you should turn on the HV amplifier only after Microdrop has
established a serial connection
Note that ATX power supply will not turn on until the control board
pulls the PWR_ON pin high. By default, this pin is pulled to ground by
a resistor, so if the control board is disconnected from the computer,
the power supply shuts down. The PWR_ON pin is only pulled high once a
serial connection is established (e.g., by launching Microdrop).
Under "File/Options" there is a setting called "Auto Atx Power Off".
If this is enabled, the control board requires a periodic heartbeat
signal to keep the power supply on. When you disconnect the serial
connection (e.g., by shutting down Microdrop), the computer stops
sending this signal and the power supply will automatically shut down
after couple of minutes.
Each of our systems has a dedicated computer, so we usually just leave
all USB cables plugged in. As I mentioned, we have no power switches
on our DropBot power supplies, so we generally use the "Auto Atx Power
Off" feature. The only thing we are careful about is to turn on the
amplifier after launching Microdrop and establishing a connection.
Even this is not really a problem as long as you turn everything on
prior to loading any liquids onto your DMF device.
On Fri, Mar 20, 2015 at 7:40 PM, Mindy Simon <simon...@gmail.com> wrote:
Hmm, I did not check the log window. It froze just before the "Record
measurements" screen. It may have been our error, as it worked fine today.
As an aside, we've noticed that it seems to be very important to maintain a
certain order of switching things on. We do:
Plug in Mega USB to computer --> Plug in FTDI cable USB to computer --> Run
uDrop v1 --> Turn on the DropBot small power supply --> Turn on amplifier
We had errors when doing it out of order (e.g. Turning on DropBot power
supply before plugging in USBs). Not sure why, but it appears to be working
fine now. However, it may save someone else time to follow this order, as we
spent a bit of time the other day playing around with the order until things
worked. Now to figure out the system calibration issues and we'll be on to
On Friday, March 20, 2015 at 1:37:29 PM UTC-7, Ryan Fobel wrote:
I seem to remember Michael having a similar problem. Do you see any
message in the log window when this freeze happens? At what point
exactly does it freeze?
On Wed, Mar 18, 2015 at 7:24 PM, Mindy Simon <simo...@gmail.com> wrote:
> Thanks Ryan! We are now running 1.0 and were able to complete all of the
> calibration steps except for the chip/device load. We opened the wizard
> this calibration step but it froze, so we'll continue troubleshooting
> The other wizard worked just fine so it's probably something we're not
> On Wednesday, March 18, 2015 at 1:08:15 PM UTC-7, Ryan Fobel wrote:
>> Hi Mindy,
>> I would recommend upgrading to v1.0rc0 which I mentioned in a recent
>> post on this list:
>> I have updated the blog entry you mentioned to point to this version
>> This release candidate is considered stable for routine use. We've
>> been using it for over a month without any major problems to report.
>> The only thing preventing us from officially calling it v1.0 is that
>> we still want to add a Windows installer (currently it is a portable
>> application that is not integrated into the Windows start menu, etc.).
>> Once that happens, previously installed versions will automatically
>> upgrade if they are configured to do so.
>> My best guess for when the 1.0 installer might be ready is the end of
>> On Wed, Mar 18, 2015 at 12:39 PM, Mindy Simon <simo...@gmail.com> >> >> wrote:
>> > Hi Ryan,
>> > Is there an estimated date for when the 1.0 software version will be
>> > released?
>> > Others,
>> > Have you been using the 1.0 preview software version that Ryan posted
>> > to
>> > the
>> > blog in December?
>> > We're running our calibrations now but couldn't find options for
>> > calibrating
>> > both the HV ref. load and the chip/device load with our current
>> > software
>> > version.
>> > Thanks,
>> > Mindy
>> > --
>> > 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...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
> You received this message because you are subscribed to the Google
> "dropbot-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> email to dropbot...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
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.