Difference between revisions of "Team:Sherbrooke/Design"
Nicolas.noel (Talk | contribs) m |
|||
Line 26: | Line 26: | ||
<li><a href="#BB">BananaBoard</a></li> | <li><a href="#BB">BananaBoard</a></li> | ||
<li><a href="#Controller">Controller</a></li> | <li><a href="#Controller">Controller</a></li> | ||
+ | <li><a href="#Primers">Primers</a></li> | ||
</ul> | </ul> | ||
Line 958: | Line 959: | ||
<br/> | <br/> | ||
+ | <br/> | ||
+ | <hr/> | ||
+ | <span id="Primer"> </span> | ||
+ | <h2 class="subTitle">Primers</h2> | ||
+ | <head> | ||
+ | <style> | ||
+ | table { | ||
+ | width:100%; | ||
+ | } | ||
+ | table, th, td { | ||
+ | border: 1px solid black; | ||
+ | border-collapse: collapse; | ||
+ | } | ||
+ | th, td { | ||
+ | padding: 5px; | ||
+ | text-align: left; | ||
+ | } | ||
+ | table#t01 tr:nth-child(even) { | ||
+ | background-color: #fff; | ||
+ | } | ||
+ | table#t01 tr:nth-child(odd) { | ||
+ | background-color:#A6D785; | ||
+ | } | ||
+ | table#t01 th { | ||
+ | background-color: #009647; | ||
+ | color: black; | ||
+ | } | ||
+ | </style> | ||
+ | </head> | ||
+ | |||
+ | <table id="t01"> | ||
+ | <tr> | ||
+ | <th>Primer Name</th> | ||
+ | <th>Primer sequence</th> | ||
+ | <th>Annealing temperature</th> | ||
+ | <th>Anneal to</th> | ||
+ | <th>Goal</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-pBAD30-F</td> | ||
+ | <td>TCTCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGTGGGTCATCGAGACAA</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx028</td> | ||
+ | <td>Build pBAD30-vcrx028</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-pBAD30-R</td> | ||
+ | <td>ACTCTAGAGGATCCCCGGGTACCGAGCTCGTCACTCCTTCTTCAATTTATCCAAG</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx028</td> | ||
+ | <td>Build pBAD30-vcrx028</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>ccdB-pBAD30-F</td> | ||
+ | <td>TCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGCAGTTTAAGGTTTACACCT</td> | ||
+ | <td>50</td> | ||
+ | <td>ptac-ccdb-casette(gBlock)</td> | ||
+ | <td>Build pBAD30-ccdB</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>ccdB-pBAD30-R</td> | ||
+ | <td>ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTATATTCCCCAGAACATCAGGT</td> | ||
+ | <td>50</td> | ||
+ | <td>ptac-ccdb-casette(gBlock)</td> | ||
+ | <td>Build pBAD30-ccdB</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>mosT-pBAD30-F</td> | ||
+ | <td>CCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAGTGAACAACATAATGGATAAAGATAGCC</td> | ||
+ | <td>50</td> | ||
+ | <td>pSXT</td> | ||
+ | <td>Build pBAD30-mosT</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>mosT-pBAD30-R</td> | ||
+ | <td>ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTACTCGGCGTTTGCGTT</td> | ||
+ | <td>50</td> | ||
+ | <td>pSXT</td> | ||
+ | <td>Build pBAD30-mosT</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>mazF-pBAD30-F</td> | ||
+ | <td>TTCTCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGGTCTCACGCTATGTCC</td> | ||
+ | <td>50</td> | ||
+ | <td>gBlock-FG1</td> | ||
+ | <td>Build pBAD30-mazF</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>mazF-pBAD30-R</td> | ||
+ | <td>ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTAGCCGATCAGGACATTAATTTTAG</td> | ||
+ | <td>50</td> | ||
+ | <td>gBlock-FG1</td> | ||
+ | <td>Build pBAD30-mazF</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-KanR-del-F</td> | ||
+ | <td>TTCTGTTGCCAGCATTTGGTCAAGAGTTCTTGCCATAACGGTGTAGGCTGGAGCTGCTTC</td> | ||
+ | <td>55</td> | ||
+ | <td>pKD3</td> | ||
+ | <td>Remove vcrx028 from pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-KanR-del-R</td> | ||
+ | <td>TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATATGGGAATTAGCCATGGTCC</td> | ||
+ | <td>55</td> | ||
+ | <td>pKD3</td> | ||
+ | <td>Remove vcrx028 from pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-del-F</td> | ||
+ | <td>AGCAAGAGAAGTAATACGCCCCATAACGGGGCGTATCGAGATTGTCTGATTCGTTACCAA</td> | ||
+ | <td>50</td> | ||
+ | <td>pBAD30-vcrx028</td> | ||
+ | <td>Remove vcrx027 (anti-toxin) and previous KanR from pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-del-R</td> | ||
+ | <td>TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATTCGAGTAAACTTGGTCTGACAG</td> | ||
+ | <td>50</td> | ||
+ | <td>pBAD30-vcrx028</td> | ||
+ | <td>Remove vcrx027 (anti-toxin) and previous KanR from pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-clean-del-5'-F</td> | ||
+ | <td>TCACTGGGTTTGGTACTTTC </td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 upstream vcrx027</td> | ||
+ | <td>Clean deletion homology and cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-clean-del-5'-R</td> | ||
+ | <td>TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATCGATACGCCCCGTTATGGG</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 upstream vcrx027</td> | ||
+ | <td>Clean deletion homology and cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-clean-del-3'-F</td> | ||
+ | <td>GTATATGGGGCGACTGCACGTATGGGGGCCGAAATGTCAG</td> | ||
+ | <td>55</td> | ||
+ | <td>pVCR94 downstream vcrx028</td> | ||
+ | <td>Clean deletion homology and cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-clean-del-3'-R</td> | ||
+ | <td>CCTGTTGAATGCCAAGCGG</td> | ||
+ | <td>55</td> | ||
+ | <td>pVCR94 downstream vcrx028</td> | ||
+ | <td>Clean deletion homology and cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-del-verif-F</td> | ||
+ | <td>ACATTCCTGGGTTCAAAGC</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx027-28 region</td> | ||
+ | <td>Deletion verification primer</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx027-28-del-verif-R</td> | ||
+ | <td> | ||
+ | GATTATTTGCCCGCTCGTG | ||
+ | </td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx027-28 region</td> | ||
+ | <td>Deletion verification primer</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>pBAD30-vcrx028-igem-ship-F</td> | ||
+ | <td>CGCTAAGGATGATTTCTGGAATTCGCGGCCGCTTCTAGAGCAATTGTCTGATTCGTTACC</td> | ||
+ | <td>50</td> | ||
+ | <td>pBAD30-vcrx028</td> | ||
+ | <td>Build BBa_K1744000 + BBa_K1744002</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>pBAD30-vcrx028-igem-ship-R</td> | ||
+ | <td>CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTAGAGTAAACTTGGTCTGACAG</td> | ||
+ | <td>50</td> | ||
+ | <td>pBAD30-vcrx028</td> | ||
+ | <td>Build BBa_K1744000</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-igem-ship-F1</td> | ||
+ | <td>CGCTAAGGATGATTTCTGGAATTCGCGGCCGCTTCTAGAGTTAGAAAAACTCATCGAGCA</td> | ||
+ | <td>50</td> | ||
+ | <td>pOK12 for KanR</td> | ||
+ | <td>Build BBa_K1744001</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-igem-ship-R1</td> | ||
+ | <td>TGAAATTTCCATTGCACGCAAACCTGTGGTCGCCTAATAAATGAGCCATATTCAACGGGA</td> | ||
+ | <td>50</td> | ||
+ | <td>pOK12 for KanR</td> | ||
+ | <td>Build BBa_K1744001</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-igem-ship-F2</td> | ||
+ | <td>TTATTAGGCGACCACAGGTT</td> | ||
+ | <td>50</td> | ||
+ | <td>gBlock_IGEM_2015_2</td> | ||
+ | <td>Build BBa_K1744001</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-igem-ship-R2</td> | ||
+ | <td>CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTATTTACAGCTAGCTCAGTCCT</td> | ||
+ | <td>50</td> | ||
+ | <td>gBlock_IGEM_2015_2</td> | ||
+ | <td>Build BBa_K1744001</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-kan-amilCP-IGEM-ship-F1</td> | ||
+ | <td>TTTCAAAGCTAGCATAATACCTAGGACTGAGCTAGCTGTAAACTAGAGGATCCCCGGGTA</td> | ||
+ | <td>50</td> | ||
+ | <td>pBAD30-vcrx028</td> | ||
+ | <td>Build BBa_K1744002 plasmid + genomic cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-kan-amilCP-IGEM-ship-F2</td> | ||
+ | <td>TTTACAGCTAGCTCAGTCCTAG</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744001</td> | ||
+ | <td>Build BBa_K1744002 plasmid + genomic cassette assembly</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-kan-amilCP-IGEM-ship-R2</td> | ||
+ | <td>CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTATTAGAAAAACTCATCGAGCA</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744001</td> | ||
+ | <td>Build BBa_K1744002</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-lacZ-ins-F</td> | ||
+ | <td>TTATTTTTGACACCAGACCAACTGGTAATGGTAGCGACCGTTTACAGCTAGCTCAGTCCT</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744001</td> | ||
+ | <td>BBa_K1744001 insertion in lacZ</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>kanR-amilCP-lacZ-ins-R</td> | ||
+ | <td>GGATGGTGGCGCTGGATGGTAAGCCGCTGGCAAGCGGTGATTAGAAAAACTCATCGAGCA</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744001</td> | ||
+ | <td>BBa_K1744001 insertion in lacZ</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-kan-amilCP-lacZ-ins-F</td> | ||
+ | <td>TTATTTTTGACACCAGACCAACTGGTAATGGTAGCGACCGCAATTGTCTGATTCGTTACC</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744002</td> | ||
+ | <td>BBa_K1744002 insertion in lacZ</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>vcrx028-kan-amilCP-lacZ-ins-R</td> | ||
+ | <td>GGATGGTGGCGCTGGATGGTAAGCCGCTGGCAAGCGGTGATTAGAAAAACTCATCGAGCA</td> | ||
+ | <td>50</td> | ||
+ | <td>BBa_K1744002</td> | ||
+ | <td>BBa_K1744002 insertion in lacZ</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>lacZ-homology-ext-F</td> | ||
+ | <td>C*G*CGAAATACGGGCAGACATGGCCTGCCCGGTTATTATTATTTTTGACACCAGACCAACT</td> | ||
+ | <td>55</td> | ||
+ | <td>lacZ insertion cassette</td> | ||
+ | <td>Insertion in lacZ homology extension</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>lacZ-homology-ext-R</td> | ||
+ | <td>G*A*ATTCTCATGTTTGACAGCTTATCATCGGAGCTCCTGCACTGGATGGTGGCGCTGGATG</td> | ||
+ | <td>55</td> | ||
+ | <td>lacZ insertion cassette</td> | ||
+ | <td>Insertion in lacZ homology extension</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>5'_pVCR94_del_verif_F</td> | ||
+ | <td>ACATTCCTGGGTTCAAAGC</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx26 region</td> | ||
+ | <td>Verification of the insertion of BBa_K1744000 in pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>3'_pVCR94_del_verif_R</td> | ||
+ | <td>CATGACTACTTACTGACATTTCGGC</td> | ||
+ | <td>50</td> | ||
+ | <td>pVCR94 vcrx29 region</td> | ||
+ | <td>Verification of the insertion of BBa_K1744000 in pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>5'_pVCR94_del_verif_R</td> | ||
+ | <td>CGCCAGCAGTTAGGGATTAG</td> | ||
+ | <td>55</td> | ||
+ | <td>BBa_K1744000</td> | ||
+ | <td>Verification of the insertion of BBa_K1744000 in pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>3'_pVCR94_del_verif_F</td> | ||
+ | <td>GGCGGATAAAGTTGCAGGAC</td> | ||
+ | <td>55</td> | ||
+ | <td>BBa_K1744000</td> | ||
+ | <td>Verification of the insertion of BBa_K1744000 in pVCR94</td> | ||
+ | |||
+ | </tr> | ||
+ | |||
+ | |||
+ | </table> | ||
<br/> | <br/> | ||
<hr/> | <hr/> |
Revision as of 01:33, 15 September 2015
Design
Our robotic platform is composed of many modules, each with their own specifications, concept and functionalities. Each module is designed to be independent so they can be operated alone or jointly with other modules. The teamwork between every module is managed by the Main Administrator that communicates and controls them via a CAN communication bus and custom controller boards, named BananaBoard. In its entirety, the project has eight distinct modules: The platform, the tool holder, custom pipettes, the gripper, the centrifuge, the magneto caloric module for 96-well plate, the magneto caloric module for 1.5mL tube and the turbido agitator caloric module for glass tube. Additionally, most of these module are controlled by our custom controller board. The global architecture of the robotic platform is as follows:
![](https://static.igem.org/mediawiki/2015/5/55/Team_Sherbooke_Global_Architecture.png)
Biobot Project Global Architecture
In this page you will learn all there is to know about each module, whether it is for the electrical, mechanical or software design. Scroll down or choose one module in the following list to learn about it.
Modules
- Platform
- Tool Holder
- Pipettes
- Gripper
- Centrifuge
- Magneto Caloric 96 (MC96)
- Magneto Caloric 1.5 (MC1.5)
- Turbido Agitator Caloric (TAC)
- BananaBoard
- Controller
- Primers
Platform
Description
The physical platform consists of everything related to the structure on which the movements take place. It also acts as the reference surface area for the labware used during a protocol. It is equipped with motors and traction mechanisms for movement on the horizontal plane, as well as indicators to locate the home position of each axis. Atop the structure is a travelling bridge and a trolley with the tool holder attached to it. The movements and limits detection of the platform are supervised by a well known controller board: the SmoothieBoard. The robot does smooth and precise movements and gives feedback on its position on demand. We started with a small model as the first draft of our platform. Since the beginning of the project, we build a completely new platform, which is bigger and stronger. The redesigned platform was quadrupled in size, the motors was changed for a stronger and faster model, and the original work area with rails was changed for a pegboard for easier placement of the modules.
![](https://static.igem.org/mediawiki/2015/0/04/Team_Sherbrooke_Platform.jpg)
Biobot Project Physical Platform (La changer pour une récente avec les modifications)
The frame is made up of aluminium extrusions. This material was selected due to its lightness, rather low cost and simplicity to sterilize, which is a great advantage for a platform used in a biology lab. When designing the platform, we sometimes created a first version using a 3D printer to validate our concept. After validation, most of those parts were replaced by a machined aluminium version.
Movements of the different axes are ensured by stepper motors to perform translations of the travelling bridge and of the trolley. For movements relative to the horizotal plane, two NEMA 23 stepper motors, model 17HS3001-20B, were used. They offer fast speeds, while still being precise as to 200 microns, which is useful to move the tools to a precise position without slowing down the whole process. These motors are coupled with an endless screw which makes the assembly moves as it spins. The are also used because they are durable and reliable. Those two assets are significant since a lot of repetitive movements occur in the horizontal plane, which consequently deals more wear and tear.
Specifications
Mechanical
Specification | Value |
---|---|
Frame material | Aluminium extrusions |
Dimensions | 160 cm x 120 cm x 130 cm |
Motion mean | Stepper motors coupled with endless screws |
X axis movement precision | 0.25 mm |
X axis movement speed | 50 mm/s |
Y axis movement precision | 0.25 mm |
Y axis movement speed | 50 mm/s |
Electrical
Specification | Value |
---|---|
Motors' input voltage | 24V |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
Tool Holder
Description
One of the main scope of the platform is to perform pipetting operations using different type of pipettes, namely, single-channel and multi-channel pipette as needed by the lab protocol. To hold and use them, a custom tool holder was designed and built. The holder is fixed on the trolley which is fixed on the travelling bridge. The tool holder have three independent C-Beam by OpenBuilds to perform movement along the vertical axis. The two first C-Beams are used for pipettes. The third one is used for the gripper. Pipettes' C-Beam are equipped with a pipette holder, made of actuators to press the piston and the tip release push-button.
Specifications
Mechanical
Specification | Value |
---|---|
Frame material | Aluminium extrusions |
Dimensions | X cm x X cm x X cm |
Motion mean | Stepper motors coupled with endless screws |
Z axis movement precision | 0.25mm |
Z axis movement speed | 50mm/s |
Electrical
Specification | Value |
---|---|
Motors' input voltage | 24V |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
- 3x C-Beam Linear Rail, 500mm
- 3x NEMA 23 Stepper Motor, Model: Motech Motor, MT-2303Hs280AW-0B, 1.8°/Step
- 3x C shaped rails, 500mm
- 3x Endless screw, 500mm
- 2x XX Motor pour le pipettage
Assembly
...
Back to top
Pipettes
Description
Pipetting will be one of our platform major functionality. To do so, we designed custom pipette modules using syringes instead of using normal pipettes. This will give our pipette system more versatility. It will also ease the design of the mechanical interface between our pipettes and the tool-holder. We designed a single-channel pipette as well as a multi-channel one.
The system is somewhat simple. A custom support was designed and machined in aluminium pieces to hold the different parts of the whole pipette system. Starting at the bottom, a pipette tip is fixed on adapter. This adapter is needed because pipette tips are not design to fit on syringe and vice versa. Attached on top of the adapter is the syringe. The syringe piston is grabbed by a mechanical piece that is coupled on an endless screw, which is coupled on a stepper motor. As the motor spins, the piston moves in the syringe, and doing so, vacuuming the liquid in and out of the pipette tip. The amount of liquid in the pipette is known and controlled by the number of step the motor spins. The whole pipette assembly is then fixed on the tool-holder and is controlled by a BananaBoard.
The multi-channel pipette system has a minor difference, beside the number of syringe and tip of course. Because it was not possible to assemble the syringes close enough so they would fit the width of a standard 96-well plate, we had to add a tube between the syringe and the pipette tip adaptor. That way, tips are close enough, and there is enough space to attached the syringes side-by-side. Take a look at the assembly section of the pipette to have a better idea of the system.
Specifications
Mechanical
Specification | Value |
---|---|
Dimensions | 258 mm x 75 mm x 97 cm |
Vacuuming range | 0 to XXX μL |
Vacuuming precision | XX μL |
Vacuuming speed | XX μL/sec |
Electrical
Specification | Value |
---|---|
Stepper motor's input voltage | 12V |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
- Idex P-420 Super Flangeless Female Nut PEKK Natural for 1/16 (link)
- Idex P-259 Super Flangeless Ferrule w/SST Ring, Tefzel (ETFE), 1/4-28 Flat-Bottom, for 1/16" OD (link)
- Idex XP-286 Flangeless Fitting Headless, PEEK, Natural, 1/4-28 Flat-Bottom, for 1/16" OD (link)
Assembly
...
Back to top
Gripper
Description
The finger-like gripper is design to allow the handling of lab-ware around the work area. It can moves tubes, micro-plate and different type of boxes such as pipette tip box around as needed. The gripper is fixed to one of the three z-axis of the tool holder. It can therefore be used independently of the other tools on the holder. The gripper is first composed of a Dual Gripper Kit from Crust Crawler Robotics. This kit uses two Trossen Robotics' Dynamixel AX-12A servomotors for the finger-like motion. We then added a third AX-12A servo to give the gripper wrist-like capabilities, adding flexion and extension movement. Lastly, a MX-12W servo was also added so the gripper can rotate around a vertical axis on 360°.
This gripper kit was chosen because it uses Trossen Robotics' Dynamixel servomotors. Those servos are easy to control and their precision in movement allowed us to fall within the specification we needed for our gripper. They offer various options to monitor and use different operating values of the servo even during live operation, allowing us to use them at our will to control the gripping function of our platform. The most useful Dynamxiel's control function is the torque limit that we can set to a custom value corresponding to the object we desire to grip. Also, the MX-12W was chosen for the gripper rotation because the angle of the servo can be monitored over 360°, unlike AX-12A Dynamixel which can only be monitored from -150° to 150°. The servos assembly gives the gripper the ability to take narrow objects as well as wider ones, and it can grip them from top or from the side. It can also rotate on 360°. The gripper is controlled by a dedicated BananaBoard.
Specifications
Mechanical
Specification | Value |
---|---|
Dimensions | 258 mm x 75 mm x 97 cm |
Motors | Robotis' Dynamixel AX and MX servomotors |
Fingertip precision | 0.7 mm |
Fingertip speed | from 0 to 680 mm/s |
Fingertip torque | from 0 to 1.5 N*m |
Rotation precision | 0.088° |
Rotation speed | from 0 to 470 rpm |
Electrical
Specification | Value |
---|---|
Servos' input voltage | 12V |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
- 3x Dynamixel AX-12A by Robotis (link)
- 1x Dynamixel MX-12W by Robotis (link)
- 1x CrustCrawler AX Dual Robotic Gripper Hardware Kit (link)
- 2x Bioloid F2 Frame (from Dynamixel servo's kit)
- 3x Bioloid F3 Frame (from Dynamixel servo's kit)
- 3x 3-Pins Dynamixel Communication Cable (from Dynamixel servo's kit)
- Bolts and nuts (from Dynamixel servo's kit)
Assembly
...
Back to top
Centrifuge
Description
Centrifugation operations are often required for protocols in cellular biology lab. Our client therefore asked us to design an automated centrifuge that can be operated with the platform and the gripper.
The centrifuge is able to fit up to eight 1.5mL tubes and up to four 5mL tubes. The rotating plate, which hold the tubes, is fabricated with polyoxymethylene, a lightweight and strong thermoplastic. It is coupled on a Quanum MT series 2208 brush-less DC motor. Such motors offer high rotation speed and compact size, two characteristics profitable for the whole design. Tube slots allow tube to be vertical when resting, to ease manipulation with the gripper, and force tube to tilt to a 45° angle during centrifugation. To detect high vibrations, a warning of potential problems during run-time, an accelerometer is added to the module. The centrifuge is equipped with an automated lid which is secured by a lock mechanism during running time. Because the lid only opens over one tube slot, we need to rotate the plate from slot to slot when the centrifuge is being loaded by the gripper. To do so, a magnetic sensor is positioned on the axis of rotation so the absolute angular position is known. That way, it is possible to rotate the plate to place a tube slot under the opening in the lid so the gripper can load and unload tubes. And of course, the whole centrifuge case is built with a sturdy construction, using material such as X and Y to prevent any external damage should there be any internal problems. The centrifuge is controlled by a dedicated BananaBoard.
Specifications
Mechanical
Specification | Value |
---|---|
Dimensions (Length x Width x Heigth) | À valider Xmm x Ymm x Ymm |
Rotation Speed | X rpm |
G Force applied | 18000 G |
Tube capacity | 8x 1.5mL tubes and 4x 5mL tubes |
Electrical
Specification | Value |
---|---|
Servos' input voltage | 12V |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
Magneto Caloric 96 (MC96)
Description
![](https://static.igem.org/mediawiki/2015/b/b3/Sherbrooke_MC96_3D.png)
MC96 3D Plan
This module is called Magneto Caloric 96 (MC96) because it has to manage magnetism and temperature cycling (caloric) of a 96-well plate. The main use of the MC96 is to apply a specific temperature on different liquids (e.g. cell cultures) in the context of biological research.
The module has the possibility to concentrate particles in a solutions by applying an electromagnetic field that will bring particles on the wall of the well. This is explained by the magnetic attraction of microscopic magnetic beads to which particles are agglomerated. The beads are to be introduced into the well during the procedure and this can also be automated.
To apply the electromagnetic field, neodymium magnets are moved to the side of the wells. To do so, the magnets are assembled in a frame that is moved by a linear actuator. So, when the actuator raises the frame, the magnets are moved near the wells and the beads are brought on the well’s wall.
To implement thermal cycling, a Peltier element is used because it can heat or cool the 96-well plate depending on the current’s direction. A heat sink is stick to the other side of the Peltier element to eliminate the heat produced by it. The fan is used to create a forced convection, thus increasing the efficiency of the heat sink.Specifications
These characteristics are the specifications required by the client or part’s characteristics because no prototype has been built yet.
Thermal
Specification | Value |
---|---|
Range | 4 to 80°C |
Precision | ±1.5°C |
Heating speed | 0.5-1°C/s |
Cooling speed | 0.5-1°C/s |
Mechanical
Specification | Value |
---|---|
Material | 96-well mold : Aluminium Frames and Module base : Plastic |
Dimensions | Width x Length x Heigth cm |
Linear actuator speed | 12mm/s |
Linear actuator stroke | 2cm |
Electrical
Specification | Value |
---|---|
Input voltage | 24V |
Maximal power consumption | ≈800 Watts |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
Magneto Caloric 1.5 (MC1.5)
Description
![](https://static.igem.org/mediawiki/2015/f/fc/Sherbrooke_MC1.5_3D.png)
MC1.5 3D Plan
The other module that can control temperature and megnetic field is called Magneto Caloric 1.5 (MC1.5) and has the same functionalities as the MC96, but for tubes containing an amount of liquid as high as 1.5mL, which is more than the capacity of a MC96 well. The MC1.5 is composed of two independent sub-modules. So, each sub-module could have its own sequence.
Specifications
These characteristics are the specifications required by the client or parts’ characteristics because no prototype have not been completed yet.
Thermal
Specification | Value |
---|---|
Range | Achieved 4 to 80°C |
Precision | Achieved ±1.5°C |
Heating speed | Achieved 1°C/s |
Cooling speed | Achieved 0.5°C/s |
Mechanical
Specification | Value |
---|---|
Material | 1.5ml test tube mold : Aluminium Frames and Module base : Plastic |
Demensions | Width x Length x Heigth cm |
Linear actuator speed | 12mm/s |
Linear actuator stroke | 2cm |
Electrical
Specification | Value |
---|---|
Input voltage | 24V |
Maximal power consumption | ≈400 Watts |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
Turbido Agitator Caloric (TAC)
Description
![](https://static.igem.org/mediawiki/2015/archive/2/26/20150912145815!Sherbrooke_TAC_3D.png)
TAC 3D Plan
The main function of this module is to grow cell culture in a 25mm test tube. To do so, the module must regulate the tube temperature, be able to agitate the liquid and to measure the amount of cells in the culture. The TAC module enables the automation of repetitive steps that are performed on a daily basis in laboratories around the world. It can be reprogrammed to meet specifications of different protocols for molecular biology or microbiology experiments.
One possible application of the TAC module would be the insertion of DNA into a micro-organism. This manipulation requires the growth of the micro-organism at the optimal temperature until a specific optical density is reached. This is required for the observed colony to enter its stationary phase as we can observe in the following figure.
![](https://static.igem.org/mediawiki/2015/6/6c/Sherbrooke_Cell_Culture_Phase.png)
Cell density of a culture vs time
Once the optical density has been reached, the cells have to be washed a couple times to eliminate the residual growing media. Afterwards, the DNA is added to the mix and the cells are perforated to allow its transfer. This stressful operation kills most of them. Therefore, we have to replicate them quickly in a proper medium and at the right temperature.
To regulate the temperature between 0 and 37°C, a Peltier element is used because it can heat or cool the tube depending on the current’s direction. An heat sink is stick to the other side of the Peltier element to eliminate the heat produced by the Peltier element. The fan is used to create a forced convection, thus increasing the efficiency of the heat sink.
To agitate the liquid, the same principle as a magnetic stirrer is used. First, a magnetic stirrer bar must be inserted into the test tube. Then, a magnet stuck on a DC motor attracted the magnetic stirrer bar. So, when the DC motor rotates the magnetic stirrer bar inside the test tube rotates at the same speed and thus, agitating the liquid.
To measure the amount of cells in the culture, a system has previously been developed by the lab of professor Rodrigue. This system used the transmittance of the liquid to measure the amount of cells in a 25mm test tube. To measure it, a LED (light-emitting diode) is placed on one side of the test tube and a photodiode is placed on the other side. The LED blinks and this blink is received on the photodiode, generating a square signal as shown in the folowing Figure.
![](https://static.igem.org/mediawiki/2015/a/ae/Sherbrooke_TAC_Turbidity_Input_Signal.png)
Photodiode signal voltage vs time
The amplitude difference between the signal high and the signal low increase as the transmittance increased and decreased as the transmittance decreased. A calibration graph has been calculated and is shown in the folowing Figure.
![](https://static.igem.org/mediawiki/2015/4/47/Sherbrooke_Optical_density_vs_Amplitude_difference.png)
Optical density vs Amplitude difference
Specifications
Thermal
Specification | Value |
---|---|
Range | 0 to 37°C |
Precision | ±1.5°C |
Heating speed | Achieved 1.2°C/s |
Cooling speed | Achieved 0.3°C/s if tube temperature above room temperature Achieved 0.21°C/s if tube temperature below room temperature |
Mechanical
Specification | Value |
---|---|
Material | 25mm test tube mold : Aluminium Frames and Module base : Plastic |
Demensions | Width x Length x Heigth cm |
DC motor speed | 60 to 600 rpm |
Electrical
Specification | Value |
---|---|
Input voltage | 24V |
Maximal power consumption | ≈400 Watts |
Turbidity measurement precision | ±5% from a reference turbidimeter |
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
BananaBoard
Description
With so many different independent modules, it would have been a real struggle to design a Printed Circuit Board (PCB) for each of them. Yet, when you compare modules to each other, you can notice that there are similarities between them. We therefore decided to design a single PCB (that we named BananaBoard) that has all the electrical and software capabilities to supply every modules individually. Yet, the PCB is still functional even if some component are not soldered on it. For example, the BananaBoard has a 24V output connectors. The gripper doesn't need this electrical supply but the MC1.5 and the TAC need it. So the component for this output will not be soldered on the PCB for the gripper, but they will be for the MC1.5 and the TAC's PCB. This allowed us to save design time and reduce complexity during the PCB assembly and debugging.
Specifications
Mechanical
Specification | Value |
---|---|
Dimensions (with all component soldered) | 107.9 mm x 80.4 mm x 35.8 mm |
Electrical
Specification | Value |
---|---|
Input voltage | 24V |
Output voltages | 12-24V / 60A: Half H-Bridges and Stepper Motors 5V / 1A: Logic Circuit, LED, Sensors 3.3V / 100mA: Accelerometer |
Microcontroler | Cypress' PSoC5 CYC5868AXI-LP034 |
Other components |
|
Software
Specification | Value |
---|---|
Language | C++ |
Parts list
...
Assembly
...
Back to top
Controller
Description
...
Specifications
...
Parts list
...
Assembly
...
Back to top
Primers
Primer Name | Primer sequence | Annealing temperature | Anneal to | Goal |
---|---|---|---|---|
vcrx028-pBAD30-F | TCTCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGTGGGTCATCGAGACAA | 50 | pVCR94 vcrx028 | Build pBAD30-vcrx028 |
vcrx028-pBAD30-R | ACTCTAGAGGATCCCCGGGTACCGAGCTCGTCACTCCTTCTTCAATTTATCCAAG | 50 | pVCR94 vcrx028 | Build pBAD30-vcrx028 |
ccdB-pBAD30-F | TCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGCAGTTTAAGGTTTACACCT | 50 | ptac-ccdb-casette(gBlock) | Build pBAD30-ccdB |
ccdB-pBAD30-R | ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTATATTCCCCAGAACATCAGGT | 50 | ptac-ccdb-casette(gBlock) | Build pBAD30-ccdB |
mosT-pBAD30-F | CCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAGTGAACAACATAATGGATAAAGATAGCC | 50 | pSXT | Build pBAD30-mosT |
mosT-pBAD30-R | ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTACTCGGCGTTTGCGTT | 50 | pSXT | Build pBAD30-mosT |
mazF-pBAD30-F | TTCTCCATACCCGTTTTTTTGGGCTAGCGTAGGAGGCAAAAATGGTCTCACGCTATGTCC | 50 | gBlock-FG1 | Build pBAD30-mazF |
mazF-pBAD30-R | ACTCTAGAGGATCCCCGGGTACCGAGCTCGTTAGCCGATCAGGACATTAATTTTAG | 50 | gBlock-FG1 | Build pBAD30-mazF |
vcrx028-KanR-del-F | TTCTGTTGCCAGCATTTGGTCAAGAGTTCTTGCCATAACGGTGTAGGCTGGAGCTGCTTC | 55 | pKD3 | Remove vcrx028 from pVCR94 |
vcrx028-KanR-del-R | TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATATGGGAATTAGCCATGGTCC | 55 | pKD3 | Remove vcrx028 from pVCR94 |
vcrx027-del-F | AGCAAGAGAAGTAATACGCCCCATAACGGGGCGTATCGAGATTGTCTGATTCGTTACCAA | 50 | pBAD30-vcrx028 | Remove vcrx027 (anti-toxin) and previous KanR from pVCR94 |
vcrx027-del-R | TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATTCGAGTAAACTTGGTCTGACAG | 50 | pBAD30-vcrx028 | Remove vcrx027 (anti-toxin) and previous KanR from pVCR94 |
vcrx027-28-clean-del-5'-F | TCACTGGGTTTGGTACTTTC | 50 | pVCR94 upstream vcrx027 | Clean deletion homology and cassette assembly |
vcrx027-28-clean-del-5'-R | TTTTAGTCACATGACTACTTACTGACATTTCGGCCCCCATCGATACGCCCCGTTATGGG | 50 | pVCR94 upstream vcrx027 | Clean deletion homology and cassette assembly |
vcrx027-28-clean-del-3'-F | GTATATGGGGCGACTGCACGTATGGGGGCCGAAATGTCAG | 55 | pVCR94 downstream vcrx028 | Clean deletion homology and cassette assembly |
vcrx027-28-clean-del-3'-R | CCTGTTGAATGCCAAGCGG | 55 | pVCR94 downstream vcrx028 | Clean deletion homology and cassette assembly |
vcrx027-28-del-verif-F | ACATTCCTGGGTTCAAAGC | 50 | pVCR94 vcrx027-28 region | Deletion verification primer |
vcrx027-28-del-verif-R | GATTATTTGCCCGCTCGTG | 50 | pVCR94 vcrx027-28 region | Deletion verification primer |
pBAD30-vcrx028-igem-ship-F | CGCTAAGGATGATTTCTGGAATTCGCGGCCGCTTCTAGAGCAATTGTCTGATTCGTTACC | 50 | pBAD30-vcrx028 | Build BBa_K1744000 + BBa_K1744002 |
pBAD30-vcrx028-igem-ship-R | CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTAGAGTAAACTTGGTCTGACAG | 50 | pBAD30-vcrx028 | Build BBa_K1744000 |
kanR-amilCP-igem-ship-F1 | CGCTAAGGATGATTTCTGGAATTCGCGGCCGCTTCTAGAGTTAGAAAAACTCATCGAGCA | 50 | pOK12 for KanR | Build BBa_K1744001 |
kanR-amilCP-igem-ship-R1 | TGAAATTTCCATTGCACGCAAACCTGTGGTCGCCTAATAAATGAGCCATATTCAACGGGA | 50 | pOK12 for KanR | Build BBa_K1744001 |
kanR-amilCP-igem-ship-F2 | TTATTAGGCGACCACAGGTT | 50 | gBlock_IGEM_2015_2 | Build BBa_K1744001 |
kanR-amilCP-igem-ship-R2 | CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTATTTACAGCTAGCTCAGTCCT | 50 | gBlock_IGEM_2015_2 | Build BBa_K1744001 |
vcrx028-kan-amilCP-IGEM-ship-F1 | TTTCAAAGCTAGCATAATACCTAGGACTGAGCTAGCTGTAAACTAGAGGATCCCCGGGTA | 50 | pBAD30-vcrx028 | Build BBa_K1744002 plasmid + genomic cassette assembly |
vcrx028-kan-amilCP-IGEM-ship-F2 | TTTACAGCTAGCTCAGTCCTAG | 50 | BBa_K1744001 | Build BBa_K1744002 plasmid + genomic cassette assembly |
vcrx028-kan-amilCP-IGEM-ship-R2 | CTTGCCCTTTTTTGCCGGACTGCAGCGGCCGCTACTAGTATTAGAAAAACTCATCGAGCA | 50 | BBa_K1744001 | Build BBa_K1744002 |
kanR-amilCP-lacZ-ins-F | TTATTTTTGACACCAGACCAACTGGTAATGGTAGCGACCGTTTACAGCTAGCTCAGTCCT | 50 | BBa_K1744001 | BBa_K1744001 insertion in lacZ |
kanR-amilCP-lacZ-ins-R | GGATGGTGGCGCTGGATGGTAAGCCGCTGGCAAGCGGTGATTAGAAAAACTCATCGAGCA | 50 | BBa_K1744001 | BBa_K1744001 insertion in lacZ |
vcrx028-kan-amilCP-lacZ-ins-F | TTATTTTTGACACCAGACCAACTGGTAATGGTAGCGACCGCAATTGTCTGATTCGTTACC | 50 | BBa_K1744002 | BBa_K1744002 insertion in lacZ |
vcrx028-kan-amilCP-lacZ-ins-R | GGATGGTGGCGCTGGATGGTAAGCCGCTGGCAAGCGGTGATTAGAAAAACTCATCGAGCA | 50 | BBa_K1744002 | BBa_K1744002 insertion in lacZ |
lacZ-homology-ext-F | C*G*CGAAATACGGGCAGACATGGCCTGCCCGGTTATTATTATTTTTGACACCAGACCAACT | 55 | lacZ insertion cassette | Insertion in lacZ homology extension |
lacZ-homology-ext-R | G*A*ATTCTCATGTTTGACAGCTTATCATCGGAGCTCCTGCACTGGATGGTGGCGCTGGATG | 55 | lacZ insertion cassette | Insertion in lacZ homology extension |
5'_pVCR94_del_verif_F | ACATTCCTGGGTTCAAAGC | 50 | pVCR94 vcrx26 region | Verification of the insertion of BBa_K1744000 in pVCR94 |
3'_pVCR94_del_verif_R | CATGACTACTTACTGACATTTCGGC | 50 | pVCR94 vcrx29 region | Verification of the insertion of BBa_K1744000 in pVCR94 |
5'_pVCR94_del_verif_R | CGCCAGCAGTTAGGGATTAG | 55 | BBa_K1744000 | Verification of the insertion of BBa_K1744000 in pVCR94 |
3'_pVCR94_del_verif_F | GGCGGATAAAGTTGCAGGAC | 55 | BBa_K1744000 | Verification of the insertion of BBa_K1744000 in pVCR94 |