Difference between revisions of "Team:Aachen/Lab/Bioreactor"

Line 1: Line 1:
 
{{Team:Aachen/Header}}
 
{{Team:Aachen/Header}}
 +
 +
{{Team:Aachen/ReadMore|title=Download Library|link=/Team:Aachen/Lab/Bioreactor/Download_Library|picture=rmDownloadLibrary}}
 +
{{Team:Aachen/ReadMore|title=Hardware|link=/Team:Aachen/Lab/Bioreactor/Hardware|picture=rmHardware}}
 +
{{Team:Aachen/ReadMore|title=Control Software|link=/Team:Aachen/Software|picture=rmSoftware|url=/wiki/images/7/7a/Aachen_tile_Lab_Bioreactor_controlsoftware.JPG}}
 +
{{Team:Aachen/ReadMore|title=<html><span style="font-size:15px">Characterization of Bioreactor</span></html>|link=/Team:Aachen/Lab/Bioreactor/Characterization_of_Bioreactor|picture=rmDownloadLibrary|url=/wiki/images/2/20/Aachen_DownloadLibrary.jpg}}
  
 
As our cloning tools get more and more advanced, the next bottleneck starts to show up: strain characterization.
 
As our cloning tools get more and more advanced, the next bottleneck starts to show up: strain characterization.
Line 17: Line 22:
 
We focused on building a highly modular system. Requirements on lab equipment change from experiment to experiment. Therefore it is useless to create a closed system that can do only one task at all. It should not matter if you need six pumps or just three analysis units or three whole reactors. With our system that is all possible and even more: The open implementation of the MCP makes it possible to easily add new components and stay ready for future requirements.
 
We focused on building a highly modular system. Requirements on lab equipment change from experiment to experiment. Therefore it is useless to create a closed system that can do only one task at all. It should not matter if you need six pumps or just three analysis units or three whole reactors. With our system that is all possible and even more: The open implementation of the MCP makes it possible to easily add new components and stay ready for future requirements.
  
−
{{Team:Aachen/ReadMore|title=Download Library|link=/Team:Aachen/Lab/Bioreactor/Download_Library|picture=rmDownloadLibrary}}
 
−
{{Team:Aachen/ReadMore|title=Hardware|link=/Team:Aachen/Lab/Bioreactor/Hardware|picture=rmHardware}}
 
−
{{Team:Aachen/ReadMore|title=Control Software|link=/Team:Aachen/Software|picture=rmSoftware|url=/wiki/images/7/7a/Aachen_tile_Lab_Bioreactor_controlsoftware.JPG}}
 
−
{{Team:Aachen/ReadMore|title=<html><span style="font-size:14px">Characterization of Bioreactor</span></html>|link=/Team:Aachen/Lab/Bioreactor/Characterization_of_Bioreactor|picture=rmDownloadLibrary|url=/wiki/images/2/20/Aachen_DownloadLibrary.jpg}}
 
  
  

Revision as of 17:35, 18 September 2015

As our cloning tools get more and more advanced, the next bottleneck starts to show up: strain characterization.


For metabolic engineering the chemostat cultivation is one of the most important characterization experiments. But not only are 200-1000 ml chemostats expensive to run, they are also not parallelizable well.


To increase the effectiveness of metabolic engineering research, we made a DIY chemostat bioreactor in the 10 ml scale.


In addition to that we want to do our bit in spreading biotechnology. At the moment professional lab equipment is not affordable for smaller institutions like schools, community labs and even small universities. If synthetic biology should be announced to a wider public, it is necessary that education can start way earlier. Therefore our reactor system is cheap and DIY, that even school classes can assemble and use them in their biology courses and start exploring the world of biotechnology.

Aachen Reactor Overview 1.JPG
Tubes coming out of the reactors
Aachen Reactor Overview 3.JPG
OD device and pump box

We focused on building a highly modular system. Requirements on lab equipment change from experiment to experiment. Therefore it is useless to create a closed system that can do only one task at all. It should not matter if you need six pumps or just three analysis units or three whole reactors. With our system that is all possible and even more: The open implementation of the MCP makes it possible to easily add new components and stay ready for future requirements.










References


▲
Contact
CC-BY-SA iGEM Aachen 2015