Difference between revisions of "Team:BostonU HW/Demonstrate"
| Line 402: | Line 402: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-2">Step 1 |</div> | <div class="col-md-2">Step 1 |</div> | ||
| − | <div class="col-md-8" style=" | + | <div class="col-md-8" style="padding-left:0;">Create a Project!</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
| Line 409: | Line 409: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-2">Step 2 |</div> | <div class="col-md-2">Step 2 |</div> | ||
| − | <div class="col-md-8" style=" | + | <div class="col-md-8" style="padding-left:0;">Specify the microfluidic design in terms of liquid flow relations using a library of features provided.</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
| Line 416: | Line 416: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-2">Step 3 |</div> | <div class="col-md-2">Step 3 |</div> | ||
| − | <div class="col-md-8" style=" | + | <div class="col-md-8" style="padding-left:0;">Make any parametric edits to chip features if desired in the more detailed MINT description.</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
| Line 423: | Line 423: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-2">Step 4 |</div> | <div class="col-md-2">Step 4 |</div> | ||
| − | <div class="col-md-8" style=" | + | <div class="col-md-8" style="padding-left:0;">Build and Assemble the chip and control infrastructure.</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
| Line 430: | Line 430: | ||
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
<div class="col-md-2">Step 5 |</div> | <div class="col-md-2">Step 5 |</div> | ||
| − | <div class="col-md-8" style=" | + | <div class="col-md-8" style="padding-left:0;">Control and use the microfluidic system!</div> |
<div class="col-md-1"></div> | <div class="col-md-1"></div> | ||
</div> | </div> | ||
Revision as of 17:14, 18 October 2016
DEMONSTRATION
Come see all that Neptune has to offer at live demonstration at our booth.
TAKE A LOOK AT NEPTUNE IN ACTION
Below you can find a video of a step by step walkthrough of the Neptune toolchain. We take an example case, Dr. Ali, who wants to create a simple inducer chip, and show how he can specify, design, build, and control his microfluidic device through Neptune’s system:
Step 1 |
Create a Project!
Step 2 |
Specify the microfluidic design in terms of liquid flow relations using a library of features provided.
Step 3 |
Make any parametric edits to chip features if desired in the more detailed MINT description.
Step 4 |
Build and Assemble the chip and control infrastructure.
Step 5 |
Control and use the microfluidic system!
Considerations for Replication | Neptune is built to be modular, accessible, parametric, and expandable.
OPEN SOURCE
All of our materials are Open Source. This includes our software tool Neptune, our parametric 3-D Print (STL) files for the microfluidic and hardware infrastructure, and our firmware used to control the valves and dispensers of our system. If an individual wishes to use, modify, or reinvent our software, firmware, or hardware, all of the material to do so is readily available to them to download at their convenience from our public GitHub repository. Also, any of our supporting software tools (including Cura and OpenScad), are free. Users can download any of these resources using the links below.
INSTRUCTIONAL RESOURCES
[Priya: Build & Assembly pages]
PARAMETRIC DESIGNS
All of our STL files used for 3-D printing hardware infrastructure are parametric. If the user decides to use a different servo than that which Neptune recommends, he or she may simply enter a few measurements into the parameters listed at the top of the provided files and the designs will update automatically to reflect those changes.
Our software is designed to convert a mL amount to be dispensed into a PWM command to be sent to the arduino such that an even dispense rate is achieved for fluid movement through the microfluidic device. This conversion, however, is dependent on the specific servo/syringe combination the user has implemented. If the user decides to use a different servo/syringe setup than what is recommended by our system, he or she may still use our dispense conversion algorithm to control their system as it is also completely parametric.
Our software is designed to convert a mL amount to be dispensed into a PWM command to be sent to the arduino such that an even dispense rate is achieved for fluid movement through the microfluidic device. This conversion, however, is dependent on the specific servo/syringe combination the user has implemented. If the user decides to use a different servo/syringe setup than what is recommended by our system, he or she may still use our dispense conversion algorithm to control their system as it is also completely parametric.
LARGE FUNCTIONAL RANGE OF HARDWARE
Our Hardware system is highly adaptable for both small and large system requirements. Neptune is capable of running up to 200 servo/syringe combinations at once, fulfilling the need for the most demanding microfluidic system. This number is calculated by finding the bottleneck in data transfer from the computer to Arduino, and the transfer rate from Arduino to motor controller shield. Processing time in both the computer and Arduino are comparatively negligible.
Transfer to Arduino: 115,200 bits/second, 14,400 bytes/second Transfer to motor controller: standard mode of I2C: 100,000 bits/second, 12,500 bytes/second Bytes required for one command: 12
Therefore the maximum theoretical number of commands that can be sent at once is 12,500/12 = 1040. Including a safety margin of over 5x to ensure that all servo/syringe combinations can move 5x per second to ensure smooth motion all at once, Neptune’s set maximum is 200 servo/syringe combinations.
Neptune transforms the build area of a desktop CNC mill into that of an entire machine shop, and beyond. By milling square, modular components with pre-drilled holes for easy mounting Neptune can span a build area of one 4.2”x 4.2” square to hundreds of feet in any direction. This modularity, in addition to enabling huge build areas, allows for custom baseboard configurations to fix each project’s individual needs. The pre-drilled holes ensure proper component alignment and spacing, further adding to Neptune’s ease-of-use.
Transfer to Arduino: 115,200 bits/second, 14,400 bytes/second Transfer to motor controller: standard mode of I2C: 100,000 bits/second, 12,500 bytes/second Bytes required for one command: 12
Therefore the maximum theoretical number of commands that can be sent at once is 12,500/12 = 1040. Including a safety margin of over 5x to ensure that all servo/syringe combinations can move 5x per second to ensure smooth motion all at once, Neptune’s set maximum is 200 servo/syringe combinations.
Neptune transforms the build area of a desktop CNC mill into that of an entire machine shop, and beyond. By milling square, modular components with pre-drilled holes for easy mounting Neptune can span a build area of one 4.2”x 4.2” square to hundreds of feet in any direction. This modularity, in addition to enabling huge build areas, allows for custom baseboard configurations to fix each project’s individual needs. The pre-drilled holes ensure proper component alignment and spacing, further adding to Neptune’s ease-of-use.
