MicroDrop v2.0 release


#1

Hi all,

We’ve just released MicroDrop v2.0. You can get it here.

We’ve been using this version internally for a few months now, and we think you’re going to love it! It has a lot of new features, including:

  • droplet path routing
  • improved video registration
  • a new profile manager which enables switching between multiple MicroDrop profile directories (e.g., plugins, devices, etc.) on the same computer
  • an improved system for installing plugin dependencies and auto-updating
    We’ve created a YouTube playlist showing some of the new droplet routing features.

There’s still a bit of work to do updating the documentation, but instructions for installation and migration from v1.0 are complete.

Please note that there are some important caveats for upgrading from v1.0, but we have posted a method for installing both versions side-by-side to help with the transition.

If you run into any problems with installation, please post them to the dev list and we’ll try to resolve them as quickly as possible. We will also be available for a Google Hangout on Nov. 30th from 12-1pm ET to sort out any remaining issues.

Thanks,

The MicroDrop dev team

Christian Fobel chri...@fobel.net
Ryan Fobel ry...@fobel.net


#2

Hi Christian, Ryan,

I had to change the host PC of Dropbot and tried to install MicroDrop v2.0 into new host PC.

However, it doesn’t working well. I’d like to have your advise.

Situation;

  1. Run MicroDrop-2.4-Windows-x86.exe

  2. Plugins were download/install from Plugin Manager. So far, 4 plugins are installed

wheelerlab.dropbot_dx 2.2.7

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.1.19

wheelerlab.droplet_planning_plugin 2.1.0

  1. Re-run MicroDrop

  2. Serial connection failed like screenshot (shot1, shot2)

  3. Go on ignoring warning window, user interface window appears but control board is Not connected (shot3)

  4. I suppose COM port is correctly assigned.(shot0)

profile manager log of above steps 1-5 is Log.txt

  • Arduino Mega driver was installed using Arduino LLC driver in advance. Corresponding port is COM4.

It is working well with Arduino_IDE.

I will truly appreciate your advise.

Best regards,

Aki@U-Tokyo

log.txt (23.9 KB)

···


#3

Sorry to hear about your troubles. I will investigate and get back to you later today.

Thanks,

Christian

···

On Mon, Nov 21, 2016, 3:54 AM ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Hi Christian, Ryan,

I had to change the host PC of Dropbot and tried to install MicroDrop v2.0 into new host PC.

However, it doesn’t working well. I’d like to have your advise.

Situation;

  1. Run MicroDrop-2.4-Windows-x86.exe
  1. Plugins were download/install from Plugin Manager. So far, 4 plugins are installed

wheelerlab.dropbot_dx 2.2.7

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.1.19

wheelerlab.droplet_planning_plugin 2.1.0

  1. Re-run MicroDrop
  1. Serial connection failed like screenshot (shot1, shot2)
  1. Go on ignoring warning window, user interface window appears but control board is Not connected (shot3)
  1. I suppose COM port is correctly assigned.(shot0)

profile manager log of above steps 1-5 is Log.txt

  • Arduino Mega driver was installed using Arduino LLC driver in advance. Corresponding port is COM4.

It is working well with Arduino_IDE.

I will truly appreciate your advise.

Best regards,

Aki@U-Tokyo

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.


#4

Please try uninstalling the dropbot-dx plugin. This is used for a different instrument and may be interfering.

-Ryan

···

On Nov 21, 2016 8:18 AM, “Christian Fobel” chri...@fobel.net wrote:

Sorry to hear about your troubles. I will investigate and get back to you later today.

Thanks,

Christian

On Mon, Nov 21, 2016, 3:54 AM ytoyoshima@nojilab.t.u-tokyo.ac.jp wrote:

Hi Christian, Ryan,

I had to change the host PC of Dropbot and tried to install MicroDrop v2.0 into new host PC.

However, it doesn’t working well. I’d like to have your advise.

Situation;

  1. Run MicroDrop-2.4-Windows-x86.exe
  1. Plugins were download/install from Plugin Manager. So far, 4 plugins are installed

wheelerlab.dropbot_dx 2.2.7

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.1.19

wheelerlab.droplet_planning_plugin 2.1.0

  1. Re-run MicroDrop
  1. Serial connection failed like screenshot (shot1, shot2)
  1. Go on ignoring warning window, user interface window appears but control board is Not connected (shot3)
  1. I suppose COM port is correctly assigned.(shot0)

profile manager log of above steps 1-5 is Log.txt

  • Arduino Mega driver was installed using Arduino LLC driver in advance. Corresponding port is COM4.

It is working well with Arduino_IDE.

I will truly appreciate your advise.

Best regards,

Aki@U-Tokyo

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


#5

Hi Aki,

Are you able to connect after following Ryan’s suggestion of uninstalling the dropbot_dx_plugin?

-Christian

···

On Mon, Nov 21, 2016 at 8:21 AM, Ryan Fobel ry...@fobel.net wrote:

Please try uninstalling the dropbot-dx plugin. This is used for a different instrument and may be interfering.

-Ryan

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

On Nov 21, 2016 8:18 AM, “Christian Fobel” chri...@fobel.net wrote:

Sorry to hear about your troubles. I will investigate and get back to you later today.

Thanks,

Christian

On Mon, Nov 21, 2016, 3:54 AM ytoyoshima@nojilab.t.u-tokyo.ac.jp wrote:

Hi Christian, Ryan,

I had to change the host PC of Dropbot and tried to install MicroDrop v2.0 into new host PC.

However, it doesn’t working well. I’d like to have your advise.

Situation;

  1. Run MicroDrop-2.4-Windows-x86.exe
  1. Plugins were download/install from Plugin Manager. So far, 4 plugins are installed

wheelerlab.dropbot_dx 2.2.7

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.1.19

wheelerlab.droplet_planning_plugin 2.1.0

  1. Re-run MicroDrop
  1. Serial connection failed like screenshot (shot1, shot2)
  1. Go on ignoring warning window, user interface window appears but control board is Not connected (shot3)
  1. I suppose COM port is correctly assigned.(shot0)

profile manager log of above steps 1-5 is Log.txt

  • Arduino Mega driver was installed using Arduino LLC driver in advance. Corresponding port is COM4.

It is working well with Arduino_IDE.

I will truly appreciate your advise.

Best regards,

Aki@U-Tokyo

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


#6

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

log1.txt (19.7 KB)

···

#7

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

···

On Mon, Nov 21, 2016 at 11:07 PM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


#8

Hi Aki,

Please perform the following steps to list the COM port details with your Arduino Mega connected:

  1. Launch the following shortcut: Inline image 1
  2. Run the following command in the prompt that is launched:
python -m serial.tools.list_ports -v

  1. The output should be something like:
    COM5
desc: Arduino Mega 2560 (COM5)
hwid: USB VID:PID=2341:0010 SNR=8523533313535171B2A1
1 ports found

Please reply with the output from the command prompt above so we can try to debug what’s going on.

Thanks,
Christian

···

On Mon, Nov 21, 2016 at 11:07 PM, ytoyoshima@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


#9

Hi Ryan,

I find “Arduino Mega 2560 (COM4)” on the ”Port" of device manager like attached picture.

Sorry it include Japanese character.

-Aki

2016年11月24日木曜日 7時14分19秒 UTC+9 Ryan Fobel:

···

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

On Mon, Nov 21, 2016 at 11:07 PM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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.


#10

Christian,

Thanks your suggestion. Command results like attached env.txt.

I also tried command;
python.exe -m dmf_control_board_firmware.bin.upload -p COM4 mega2560 2.1
from windows command prompt as a troubleshooting firmware update.
Arduino-IDE serial monitor results attached control.txt .

However, still situation is the same. Microdrop can't find COM port.

Regards,
-Aki@U-Tokyo

2016年11月24日木曜日 7時29分05秒 UTC+9 Christian Fobel:

env.txt (462 Bytes)

control.txt (960 Bytes)

···

Hi Aki,

Please perform the following steps to list the COM port details with your Arduino Mega connected:

  1. Launch the following shortcut: Inline image 1
  2. Run the following command in the prompt that is launched:
python -m serial.tools.list_ports -v

  1. The output should be something like:
    COM5
desc: Arduino Mega 2560 (COM5)
hwid: USB VID:PID=2341:0010 SNR=8523533313535171B2A1
1 ports found

Please reply with the output from the command prompt above so we can try to debug what’s going on.

Thanks,
Christian

On Wed, Nov 23, 2016 at 5:13 PM, Ryan Fobel ry...@fobel.net wrote:

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

On Mon, Nov 21, 2016 at 11:07 PM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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.

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.


#11

Hi Aki,

Thanks very much for sending the environment information. I have published a new version (v2.2.2) of the dmf_control_board_plugin. See here for information about the changes.

Please try updating to this version of the plugin and try connecting again. If you still have difficulty, please copy/paste the serial port information using the command in my previous email.

Thanks,
Christian

···

On Thu, Nov 24, 2016 at 5:23 AM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Christian,

Thanks your suggestion. Command results like attached env.txt.

I also tried command;
python.exe -m dmf_control_board_firmware.bin.upload -p COM4 mega2560 2.1
from windows command prompt as a troubleshooting firmware update.
Arduino-IDE serial monitor results attached control.txt .


However, still situation is the same. Microdrop can't find COM port.


Regards,
-Aki@U-Tokyo

2016年11月24日木曜日 7時29分05秒 UTC+9 Christian Fobel:

Hi Aki,

Please perform the following steps to list the COM port details with your Arduino Mega connected:

  1. Launch the following shortcut: Inline image 1
  2. Run the following command in the prompt that is launched:
python -m serial.tools.list_ports -v

  1. The output should be something like:
    COM5
desc: Arduino Mega 2560 (COM5)
hwid: USB VID:PID=2341:0010 SNR=8523533313535171B2A1
1 ports found

Please reply with the output from the command prompt above so we can try to debug what’s going on.

Thanks,
Christian

On Wed, Nov 23, 2016 at 5:13 PM, Ryan Fobel ry...@fobel.net wrote:

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

On Mon, Nov 21, 2016 at 11:07 PM, ytoy...@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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.

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.

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


#12

Chritian,

Great! version (v2.2.2) successfully recognized COM port and microdrop came up with 90pin device data.

Thank you so much for your revision. I didn’t expect compatible Arduino (Genuino) might cause such affection.

Sorry lack of the information in the first question.

I’ve moved to the test & calibration.

Two calibration were successfully carried out.

-Calibrate the high-voltage reference load

-Calibrate the device load

However, Channels Test was hung up after 40 channel test like attached picture.

Profile manager log of this test is following.

···

Page 0 prepared.

712 300

Page 1 prepared.

712 300

Page 2 prepared.

712 300

Page 3 prepared.

C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmware\gui\ch

annels.py:60: RuntimeWarning: invalid value encountered in absolute

/ df[‘expected capacitance’])

(<type ‘exceptions.AttributeError’>, AttributeError("‘DMFControlBoard’ object ha

s no attribute ‘_i2c_devices’",), <traceback object at 0x11A32120>) {}

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 292, in read_measurements

on_update=on_update)

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 82, in sweep_channels

results[‘hv_switching_board’ % address] = proxy._i2c_devices[address]


It is big progress to me, although there is a miner issue.

Thanks,

Aki@U-Tokyo

2016年11月25日金曜日 0時44分19秒 UTC+9 Christian Fobel:

Hi Aki,

Thanks very much for sending the environment information. I have published a new version (v2.2.2) of the dmf_control_board_plugin. See here for information about the changes.

Please try updating to this version of the plugin and try connecting again. If you still have difficulty, please copy/paste the serial port information using the command in my previous email.

Thanks,
Christian

On Thu, Nov 24, 2016 at 5:23 AM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Christian,

Thanks your suggestion. Command results like attached env.txt.

I also tried command;
python.exe -m dmf_control_board_firmware.bin.upload -p COM4 mega2560 2.1
from windows command prompt as a troubleshooting firmware update.
Arduino-IDE serial monitor results attached control.txt .


However, still situation is the same. Microdrop can't find COM port.


Regards,
-Aki@U-Tokyo

2016年11月24日木曜日 7時29分05秒 UTC+9 Christian Fobel:

Hi Aki,

Please perform the following steps to list the COM port details with your Arduino Mega connected:

  1. Launch the following shortcut: Inline image 1
  2. Run the following command in the prompt that is launched:
python -m serial.tools.list_ports -v

  1. The output should be something like:
    COM5
desc: Arduino Mega 2560 (COM5)
hwid: USB VID:PID=2341:0010 SNR=8523533313535171B2A1
1 ports found

Please reply with the output from the command prompt above so we can try to debug what’s going on.

Thanks,
Christian

On Wed, Nov 23, 2016 at 5:13 PM, Ryan Fobel ry...@fobel.net wrote:

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

On Mon, Nov 21, 2016 at 11:07 PM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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.

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.

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.


#13

Hi Aki,

Please see my response inline below.

Chritian,

Great! version (v2.2.2) successfully recognized COM port and microdrop came up with 90pin device data.

Thank you so much for your revision. I didn’t expect compatible Arduino (Genuino) might cause such affection.

Sorry lack of the information in the first question.

No problem at all. We have just recently added in checks for USB vendor and product IDs to avoid interfering with devices connected to other serial ports while trying to find the port to which the control board is connected.

We are actually planning to change that behaviour, so that we try connecting to any serial port, but try recognized Mega2560 USB VID:PID ports first (see here for details).

I’ve moved to the test & calibration.

Two calibration were successfully carried out.

-Calibrate the high-voltage reference load

-Calibrate the device load

Great to hear!

However, Channels Test was hung up after 40 channel test like attached picture.

Profile manager log of this test is following.


Page 0 prepared.

712 300

Page 1 prepared.

712 300

Page 2 prepared.

712 300

Page 3 prepared.

C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmware\gui\ch

annels.py:60: RuntimeWarning: invalid value encountered in absolute

/ df[‘expected capacitance’])

(<type ‘exceptions.AttributeError’>, AttributeError("‘DMFControlBoard’ object ha

s no attribute ‘_i2c_devices’",), <traceback object at 0x11A32120>) {}

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 292, in read_measurements

on_update=on_update)

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 82, in sweep_channels

results[‘hv_switching_board’ % address] = proxy._i2c_devices[address]


Thanks for posting the error log. I’ve uploaded a new version of the `dmf_control

I have published a new version (v2.2.3) of the dmf_control_board_plugin. See here for information about the changes.

Please try updating to this version of the plugin, plug in the test board and try to run the channel test again.

Please let me know how things go.

Thanks,

Christian

It is big progress to me, although there is a miner issue.

Thanks,

Aki@U-Tokyo

2016年11月25日金曜日 0時44分19秒 UTC+9 Christian Fobel:

Hi Aki,

Thanks very much for sending the environment information. I have published a new version (v2.2.2) of the dmf_control_board_plugin. See here for information about the changes.

Please try updating to this version of the plugin and try connecting again. If you still have difficulty, please copy/paste the serial port information using the command in my previous email.

Thanks,
Christian

Christian,

Thanks your suggestion. Command results like attached env.txt.

I also tried command;
python.exe -m dmf_control_board_firmware.bin.upload -p COM4 mega2560 2.1
from windows command prompt as a troubleshooting firmware update.
Arduino-IDE serial monitor results attached control.txt .


However, still situation is the same. Microdrop can't find COM port.


Regards,
-Aki@U-Tokyo

2016年11月24日木曜日 7時29分05秒 UTC+9 Christian Fobel:

Hi Aki,

Please perform the following steps to list the COM port details with your Arduino Mega connected:

  1. Launch the following shortcut: Inline image 1
  2. Run the following command in the prompt that is launched:
python -m serial.tools.list_ports -v

  1. The output should be something like:
    COM5
desc: Arduino Mega 2560 (COM5)
hwid: USB VID:PID=2341:0010 SNR=8523533313535171B2A1
1 ports found

Please reply with the output from the command prompt above so we can try to debug what’s going on.

Thanks,
Christian

Hi Aki,

Does the COM port show up in the Windows device manager?

-Ryan

Chrstian, Ryan,

Thanks a lot for your quick reply.

I’ve tried both (a) Uninstalling dropbot_dx plugin and (b) Uninstall/Install of MicroDrop-2.4-Windows-x86.exe

Unfortunately, situation is the same. COM port is not appeared also in the window File->Option (shot4)

During the (b), some plugins are updated. Current version are;

wheelerlab.dmf_device_ui_plugin 2.0.31

wheelerlab.dmf_control_board_plugin 2.2.1

wheelerlab.droplet_planning_plugin 2.1.0

Latest profile manager log is Log1.txt

I’m going to try anything you recommend.

Thanks.

Aki@U-Tokyo

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 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 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.

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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

···

On Fri, Nov 25, 2016 at 4:45 AM, ytoyo...@nojilab.t.u-tokyo.ac.jp wrote:

On Thu, Nov 24, 2016 at 5:23 AM, ytoy...@nojilab.t.u-tokyo.ac.jp wrote:

On Wed, Nov 23, 2016 at 5:13 PM, Ryan Fobel ry...@fobel.net wrote:

On Mon, Nov 21, 2016 at 11:07 PM, ytoy...@nojilab.t.u-tokyo.ac.jp wrote:


#14

Hi Christian,

Thank you for quick update.

Plugin (v2.2.3) were successfully installed. However, Channels Test is hung up during page3 step.

Test was carried out several times and hung up steps were bit different like ch.16, 12, 13.

Log example is following and screen shot at hung up is attached.

···

Page 0 prepared.

712 300

Page 1 prepared.

712 300

Page 2 prepared.

712 300

Page 3 prepared.

(<type ‘exceptions.ValueError’>, ValueError('Length of values does not match len

gth of index’,), <traceback object at 0x11BA4328>) {}

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 332, in read_measurements

on_update=on_update)

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 102, in sweep_channels

result_frames.append(measure_load(channel, v))

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 74, in measure_load

df[‘measured impedance’] = results.Z_device()

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2419, in setitem

self._set_item(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2485, in _set_item

value = self._sanitize_column(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2656, in _sanitize_column

value = _sanitize_index(value, self.index, copy=False)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\series.py”, l

ine 2798, in _sanitize_index

raise ValueError('Length of values does not match length of ’ ‘index’)


Regards,


#15

Hi Aki,

Sorry, I’ve posted a new version of the dmf_control_board_plugin (v2.2.4) which should hopefully address the issue. Please try upgrading the plugin and let me know if it helps.

Thanks,
Christian

···

On Monday, November 28, 2016 at 1:25:52 AM UTC-5, ytoyo…@nojilab.t.u-tokyo.ac.jp wrote:

Hi Christian,

Thank you for quick update.

Plugin (v2.2.3) were successfully installed. However, Channels Test is hung up during page3 step.

Test was carried out several times and hung up steps were bit different like ch.16, 12, 13.

Log example is following and screen shot at hung up is attached.


Page 0 prepared.

712 300

Page 1 prepared.

712 300

Page 2 prepared.

712 300

Page 3 prepared.

(<type ‘exceptions.ValueError’>, ValueError('Length of values does not match len

gth of index’,), <traceback object at 0x11BA4328>) {}

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 332, in read_measurements

on_update=on_update)

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 102, in sweep_channels

result_frames.append(measure_load(channel, v))

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 74, in measure_load

df[‘measured impedance’] = results.Z_device()

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2419, in setitem

self._set_item(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2485, in _set_item

value = self._sanitize_column(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2656, in _sanitize_column

value = _sanitize_index(value, self.index, copy=False)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\series.py”, l

ine 2798, in _sanitize_index

raise ValueError('Length of values does not match length of ’ ‘index’)


Regards,


#16

Christian,

v2.2.4 solved the issue and channels test has been completed successfully!

Thank you for quick update! Now system installation has been completed.

Let me confirm just one point.

During reference load calibration, profile manager window indicates like “R=1, f=1898.2”.

At that time output waveform frequency is 3406 Hz.

I suppose profile manager is indicating completed measurement step. Is it right?

Thanks,

Aki@U-Tokyo

2016年11月28日月曜日 23時11分14秒 UTC+9 Christian Fobel:

···

Hi Aki,

Sorry, I’ve posted a new version of the dmf_control_board_plugin (v2.2.4) which should hopefully address the issue. Please try upgrading the plugin and let me know if it helps.

Thanks,
Christian

On Monday, November 28, 2016 at 1:25:52 AM UTC-5, ytoyo…@nojilab.t.u-tokyo.ac.jp wrote:

Hi Christian,

Thank you for quick update.

Plugin (v2.2.3) were successfully installed. However, Channels Test is hung up during page3 step.

Test was carried out several times and hung up steps were bit different like ch.16, 12, 13.

Log example is following and screen shot at hung up is attached.


Page 0 prepared.

712 300

Page 1 prepared.

712 300

Page 2 prepared.

712 300

Page 3 prepared.

(<type ‘exceptions.ValueError’>, ValueError('Length of values does not match len

gth of index’,), <traceback object at 0x11BA4328>) {}

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 332, in read_measurements

on_update=on_update)

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 102, in sweep_channels

result_frames.append(measure_load(channel, v))

File "C:\Users\toyoshima\MicroDrop\lib\site-packages\dmf_control_board_firmwar

e\gui\channels.py", line 74, in measure_load

df[‘measured impedance’] = results.Z_device()

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2419, in setitem

self._set_item(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2485, in _set_item

value = self._sanitize_column(key, value)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\frame.py”, li

ne 2656, in _sanitize_column

value = _sanitize_index(value, self.index, copy=False)

File “C:\Users\toyoshima\MicroDrop\lib\site-packages\pandas\core\series.py”, l

ine 2798, in _sanitize_index

raise ValueError('Length of values does not match length of ’ ‘index’)


Regards,


#17

Ryan,

I am trying to get multiple dropbot systems running under the new Microdrop 2.0 release on the same control computer. The first system is launching fine. However, when I attach the second system to the same computer and launch microdrop I get a “No Serial Ports Available” Error in Microdrop. For the initial system the Arduino Mega 2560 was assigned COM 3, for system 2 that generates the error it is assigned Com 5, and for a third system it is assigned Com 6. I have tried uninstalling/reinstalling the plugins and rebooting the cpu.

Do I need to create separate profiles for each of these Dropbot systems or how do I work around this com/serial port issue?

We had all three systems launching fine under v1.0 so there should not be any issues with the Dropbots.

What does the metadata plugin do?

The attached file contains the com port trace you suggested Aki run for two of the systems.

–Michael

No_Serial_Ports_Available_Error.rtf (2.72 MB)

···

On Friday, November 18, 2016 at 3:37:06 PM UTC-8, Ryan Fobel wrote:

Hi all,

We’ve just released MicroDrop v2.0. You can get it here.

We’ve been using this version internally for a few months now, and we think you’re going to love it! It has a lot of new features, including:

  • droplet path routing
  • improved video registration
  • a new profile manager which enables switching between multiple MicroDrop profile directories (e.g., plugins, devices, etc.) on the same computer
  • an improved system for installing plugin dependencies and auto-updating
    We’ve created a YouTube playlist showing some of the new droplet routing features.

There’s still a bit of work to do updating the documentation, but instructions for installation and migration from v1.0 are complete.

Please note that there are some important caveats for upgrading from v1.0, but we have posted a method for installing both versions side-by-side to help with the transition.

If you run into any problems with installation, please post them to the dev list and we’ll try to resolve them as quickly as possible. We will also be available for a Google Hangout on Nov. 30th from 12-1pm ET to sort out any remaining issues.

Thanks,

The MicroDrop dev team

Christian Fobel chr...@fobel.net
Ryan Fobel ry...@fobel.net


#18

Hi Michael,

Sorry to hear about the trouble. I’ve posted a new version of the dmf_control_board_plugin (v2.2.10) which should hopefully address the issue.

Please try upgrading the plugin and let me know if it helps.

Note that we also have a more long term solution planned.

Thanks,

Christian

PS - The metadata plugin is used internally to store per experiment metadata, such as sample ID, etc. However, we’re lacking a user-friendly interface to describe what metadata can be entered. If you are interested in the meantime and are comfortable hand-coding a jsonschema definition, let me know and I can put together some instructions.

···

On Tue, Nov 29, 2016, 5:49 PM Michael Connolly mdcon...@lbl.gov wrote:

Ryan,

I am trying to get multiple dropbot systems running under the new Microdrop 2.0 release on the same control computer. The first system is launching fine. However, when I attach the second system to the same computer and launch microdrop I get a “No Serial Ports Available” Error in Microdrop. For the initial system the Arduino Mega 2560 was assigned COM 3, for system 2 that generates the error it is assigned Com 5, and for a third system it is assigned Com 6. I have tried uninstalling/reinstalling the plugins and rebooting the cpu.

Do I need to create separate profiles for each of these Dropbot systems or how do I work around this com/serial port issue?

We had all three systems launching fine under v1.0 so there should not be any issues with the Dropbots.

What does the metadata plugin do?

The attached file contains the com port trace you suggested Aki run for two of the systems.

–Michael

On Friday, November 18, 2016 at 3:37:06 PM UTC-8, Ryan Fobel wrote:

Hi all,

We’ve just released MicroDrop v2.0. You can get it here.

We’ve been using this version internally for a few months now, and we think you’re going to love it! It has a lot of new features, including:

  • droplet path routing
  • improved video registration
  • a new profile manager which enables switching between multiple MicroDrop profile directories (e.g., plugins, devices, etc.) on the same computer
  • an improved system for installing plugin dependencies and auto-updating
    We’ve created a YouTube playlist showing some of the new droplet routing features.

There’s still a bit of work to do updating the documentation, but instructions for installation and migration from v1.0 are complete.

Please note that there are some important caveats for upgrading from v1.0, but we have posted a method for installing both versions side-by-side to help with the transition.

If you run into any problems with installation, please post them to the dev list and we’ll try to resolve them as quickly as possible. We will also be available for a Google Hangout on Nov. 30th from 12-1pm ET to sort out any remaining issues.

Thanks,

The MicroDrop dev team

Christian Fobel chr...@fobel.net
Ryan Fobel ry...@fobel.net

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.


#19

Christian,

Microdrop updated my dmf_control_board_plugin on launch to v2.2.5 and will not update further from the plugin manager to v2.2.10 saying that 2.2.5 is the current release. 2.2.5 does not resolve the serial port issue.

–Michael

···

On Tuesday, November 29, 2016 at 4:16:26 PM UTC-8, Christian Fobel wrote:

Hi Michael,

Sorry to hear about the trouble. I’ve posted a new version of the dmf_control_board_plugin (v2.2.10) which should hopefully address the issue.

Please try upgrading the plugin and let me know if it helps.

Note that we also have a more long term solution planned.

Thanks,

Christian

PS - The metadata plugin is used internally to store per experiment metadata, such as sample ID, etc. However, we’re lacking a user-friendly interface to describe what metadata can be entered. If you are interested in the meantime and are comfortable hand-coding a jsonschema definition, let me know and I can put together some instructions.

On Tue, Nov 29, 2016, 5:49 PM Michael Connolly mdco...@lbl.gov wrote:

Ryan,

I am trying to get multiple dropbot systems running under the new Microdrop 2.0 release on the same control computer. The first system is launching fine. However, when I attach the second system to the same computer and launch microdrop I get a “No Serial Ports Available” Error in Microdrop. For the initial system the Arduino Mega 2560 was assigned COM 3, for system 2 that generates the error it is assigned Com 5, and for a third system it is assigned Com 6. I have tried uninstalling/reinstalling the plugins and rebooting the cpu.

Do I need to create separate profiles for each of these Dropbot systems or how do I work around this com/serial port issue?

We had all three systems launching fine under v1.0 so there should not be any issues with the Dropbots.

What does the metadata plugin do?

The attached file contains the com port trace you suggested Aki run for two of the systems.

–Michael

On Friday, November 18, 2016 at 3:37:06 PM UTC-8, Ryan Fobel wrote:

Hi all,

We’ve just released MicroDrop v2.0. You can get it here.

We’ve been using this version internally for a few months now, and we think you’re going to love it! It has a lot of new features, including:

  • droplet path routing
  • improved video registration
  • a new profile manager which enables switching between multiple MicroDrop profile directories (e.g., plugins, devices, etc.) on the same computer
  • an improved system for installing plugin dependencies and auto-updating
    We’ve created a YouTube playlist showing some of the new droplet routing features.

There’s still a bit of work to do updating the documentation, but instructions for installation and migration from v1.0 are complete.

Please note that there are some important caveats for upgrading from v1.0, but we have posted a method for installing both versions side-by-side to help with the transition.

If you run into any problems with installation, please post them to the dev list and we’ll try to resolve them as quickly as possible. We will also be available for a Google Hangout on Nov. 30th from 12-1pm ET to sort out any remaining issues.

Thanks,

The MicroDrop dev team

Christian Fobel chr...@fobel.net
Ryan Fobel ry...@fobel.net

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.


#20

OK, I’m not at my computer now, will check why the updated plugin isn’t published soon.

-Christian

···

On Tue, Nov 29, 2016, 7:32 PM Michael Connolly mdcon...@lbl.gov wrote:

Christian,

Microdrop updated my dmf_control_board_plugin on launch to v2.2.5 and will not update further from the plugin manager to v2.2.10 saying that 2.2.5 is the current release. 2.2.5 does not resolve the serial port issue.

–Michael

On Tuesday, November 29, 2016 at 4:16:26 PM UTC-8, Christian Fobel wrote:

Hi Michael,

Sorry to hear about the trouble. I’ve posted a new version of the dmf_control_board_plugin (v2.2.10) which should hopefully address the issue.

Please try upgrading the plugin and let me know if it helps.

Note that we also have a more long term solution planned.

Thanks,

Christian

PS - The metadata plugin is used internally to store per experiment metadata, such as sample ID, etc. However, we’re lacking a user-friendly interface to describe what metadata can be entered. If you are interested in the meantime and are comfortable hand-coding a jsonschema definition, let me know and I can put together some instructions.

On Tue, Nov 29, 2016, 5:49 PM Michael Connolly mdco...@lbl.gov wrote:

Ryan,

I am trying to get multiple dropbot systems running under the new Microdrop 2.0 release on the same control computer. The first system is launching fine. However, when I attach the second system to the same computer and launch microdrop I get a “No Serial Ports Available” Error in Microdrop. For the initial system the Arduino Mega 2560 was assigned COM 3, for system 2 that generates the error it is assigned Com 5, and for a third system it is assigned Com 6. I have tried uninstalling/reinstalling the plugins and rebooting the cpu.

Do I need to create separate profiles for each of these Dropbot systems or how do I work around this com/serial port issue?

We had all three systems launching fine under v1.0 so there should not be any issues with the Dropbots.

What does the metadata plugin do?

The attached file contains the com port trace you suggested Aki run for two of the systems.

–Michael

On Friday, November 18, 2016 at 3:37:06 PM UTC-8, Ryan Fobel wrote:

Hi all,

We’ve just released MicroDrop v2.0. You can get it here.

We’ve been using this version internally for a few months now, and we think you’re going to love it! It has a lot of new features, including:

  • droplet path routing
  • improved video registration
  • a new profile manager which enables switching between multiple MicroDrop profile directories (e.g., plugins, devices, etc.) on the same computer
  • an improved system for installing plugin dependencies and auto-updating
    We’ve created a YouTube playlist showing some of the new droplet routing features.

There’s still a bit of work to do updating the documentation, but instructions for installation and migration from v1.0 are complete.

Please note that there are some important caveats for upgrading from v1.0, but we have posted a method for installing both versions side-by-side to help with the transition.

If you run into any problems with installation, please post them to the dev list and we’ll try to resolve them as quickly as possible. We will also be available for a Google Hangout on Nov. 30th from 12-1pm ET to sort out any remaining issues.

Thanks,

The MicroDrop dev team

Christian Fobel chr...@fobel.net
Ryan Fobel ry...@fobel.net

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 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.