Team:Cambridge/Instrumentation

From 2012.igem.org

(Difference between revisions)
(→Electronics)
 
(8 intermediate revisions not shown)
Line 7: Line 7:
   $('div.mech_view').hide();
   $('div.mech_view').hide();
   // Watch for clicks on the "slide" link.
   // Watch for clicks on the "slide" link.
-
   $('div.slide').click(function() {
+
   $('div.slide0').click(function() {
   // When clicked, toggle the "mech_view" div.
   // When clicked, toggle the "mech_view" div.
   $('div.mech_view').slideToggle(400);
   $('div.mech_view').slideToggle(400);
Line 14: Line 14:
});
});
</script>
</script>
 +
 +
<script type="text/javascript">
 +
  $(document).ready(function() {
 +
  // Hide the "elec_view" div.
 +
  $('div.elec_view').hide();
 +
  // Watch for clicks on the "slide" link.
 +
  $('div.slide1').click(function() {
 +
  // When clicked, toggle the "elec_view" div.
 +
  $('div.elec_view').slideToggle(400);
 +
  return false;
 +
});
 +
});
 +
 +
</script>
 +
 +
</script>
 +
 +
<script type="text/javascript">
 +
  $(document).ready(function() {
 +
  // Hide the "soft_view" div.
 +
  $('div.soft_view').hide();
 +
  // Watch for clicks on the "slide" link.
 +
  $('div.slide2').click(function() {
 +
  // When clicked, toggle the "soft_view" div.
 +
  $('div.soft_view').slideToggle(400);
 +
  return false;
 +
});
 +
});
 +
 +
</script>
 +
</head>
</head>
</html>
</html>
-
===Instrumentation===
+
=Instrumentation=
The aim of the instrumentation project was to develop a cheap, reliable, open-source platform for detecting two emission spectra from our biological samples. In addition to this, our design was to be portable, have full functionality in the field and support any biological sensing input desired (if the biology for this exists that is). To achieve this our design comprises 3 main parts: a mechanical chassis, an electronic interface and the supporting software. We have developed a prototype as an example of how a practical solution could be implemented, however, we realise the potential for many different realisations of appropriate instrumentation and explore some ideas with respect to this below...
The aim of the instrumentation project was to develop a cheap, reliable, open-source platform for detecting two emission spectra from our biological samples. In addition to this, our design was to be portable, have full functionality in the field and support any biological sensing input desired (if the biology for this exists that is). To achieve this our design comprises 3 main parts: a mechanical chassis, an electronic interface and the supporting software. We have developed a prototype as an example of how a practical solution could be implemented, however, we realise the potential for many different realisations of appropriate instrumentation and explore some ideas with respect to this below...
Line 28: Line 59:
<html>
<html>
<body>
<body>
-
<div class="slide" style="cursor: pointer;">+ Show/Hide -</div>
+
<div class="slide0" style="cursor: pointer;">+ Show/Hide -</div>
<div class="mech_view">
<div class="mech_view">
<br>
<br>
Many potential mechanical designs were considered during the course of this project and the final implementation of our prototype is not necessarily our view of a "Best Solution" but also one that we could demonstrate and develop easily over the course of the summer. Some major designs investigated were:
Many potential mechanical designs were considered during the course of this project and the final implementation of our prototype is not necessarily our view of a "Best Solution" but also one that we could demonstrate and develop easily over the course of the summer. Some major designs investigated were:
<ul>
<ul>
-
<li>An integrated 2D array of detectors on a flat chip board that can be directly interfaced with an arduino. The analyte would be placed in micro-wells above the sensors and sealed off for complete darkness.
+
<li>An integrated 2D array of detectors on a flat chip board that can be directly interfaced with an arduino. The analyte would be placed in micro-wells above the sensors and sealed off for complete darkness.</li>
Advantages:
Advantages:
<ul>
<ul>
Line 59: Line 90:
</UL>
</UL>
</li>
</li>
-
<li>Bullet point</li>
 
</UL>
</UL>
</div>
</div>
Line 70: Line 100:
===Further Investigations===
===Further Investigations===
 +
<html>
 +
<body>
 +
<div class="slide1" style="cursor: pointer;">+ Show/Hide -</div>
 +
<div class="elec_view">
 +
<br>
 +
In designing the electronic interface for our instrumentation we first considered different ways of obtaining information from the bacteria and the range of possibilities that exist for the processing of this information, below are a few important ideas we considered:
 +
<ul>
 +
<li>Colour sensors</li>
 +
Advantages:
 +
<ul>
 +
<li>Very good for giving an exact value of colour - narrow band detection</li>
 +
</UL>
 +
Disadvantages:
 +
<ul>
 +
<li>Do not provide an intensity value unless using expensive sensors that would work better on an integrated sensor chip</li>
 +
<li>More wires needed for data collection</li>
 +
</UL>
 +
</li>
 +
<br>
 +
<li>Use of a Raspberry Pi</li>
 +
Advantages:
 +
<ul>
 +
<li>compact portable system that interfaces easily with arduino</li>
 +
<li>cheap and highly flexible</li>
 +
</UL>
 +
Disadvantages:
 +
<ul>
 +
<li>Requires external input and output devices</li>
 +
<li>Not as nicely packaged for field work as e.g. a tablet</li>
 +
</UL>
 +
</li>
 +
<br>
 +
<li>Digital readouts instead of potential divider circuit</li>
 +
Advantages:
 +
<ul>
 +
<li>No need to worry about circuit bias changing (e.g. with temperature, current)</li>
 +
<li>Processing potentially more accurate (done on a computer)</li>
 +
</UL>
 +
Disadvantages:
 +
<ul>
 +
<li>Larger potential for noise and discrepancies between channels that are not well matched</li>
 +
<li>Less elegant solution, less intergrated</li>
 +
</UL>
 +
</li>
 +
</UL>
 +
</div>
 +
</body>
 +
</html>
==Software==
==Software==
Line 76: Line 154:
===Further investigations===
===Further investigations===
 +
<html>
 +
<body>
 +
<div class="slide2" style="cursor: pointer;">+ Show/Hide -</div>
 +
<div class="soft_view">
 +
<br>
 +
Software is always the most flexible part of any instrumentation system as there are an infinite number of ways of presenting information to the data and an infinite number of ways to code this. As we are not working on a software project we tried to keep things simple, cheap (free!) and relatively light in terms of functionality. However, we did discuss other possibilities that might be considered by other programmers:
 +
<ul>
 +
<li>Programming languages</li>
 +
<ul>
 +
<li>C++</li>
 +
Advantages:
 +
<ul>
 +
<li>Extremely flexible and useful for accessing serial ports</li>
 +
<li>A huge amount of online documentation and help forums exist</li>
 +
<li>Easily expandable with wxWidgets for developing GUIs>
 +
</UL>
 +
Disadvantages
 +
<ul>
 +
<li>Slightly cumbersome to program with</li>
 +
<li>Requires compilation<li>
 +
</UL>
 +
</UL>
 +
</UL>
 +
</div>
 +
</body>
 +
</html>
{{Template:Team:Cambridge/CAM_2012_TEMPLATE_FOOT}}
{{Template:Team:Cambridge/CAM_2012_TEMPLATE_FOOT}}

Latest revision as of 15:55, 21 August 2012

Previous iGEM teams have charaterised an impressive array of inducible promoters, along with other elements of biosensing circuitry... Read More






Contents

Instrumentation

The aim of the instrumentation project was to develop a cheap, reliable, open-source platform for detecting two emission spectra from our biological samples. In addition to this, our design was to be portable, have full functionality in the field and support any biological sensing input desired (if the biology for this exists that is). To achieve this our design comprises 3 main parts: a mechanical chassis, an electronic interface and the supporting software. We have developed a prototype as an example of how a practical solution could be implemented, however, we realise the potential for many different realisations of appropriate instrumentation and explore some ideas with respect to this below...

Mechanical Design

The Prototype

The prototype chassis consists of 6 slots in a rotary platform that can spin about its central axis. The main reason for selecting this rotary design was cost as it was assumed that one sensor and a motor would be cheaper than having separate sensors for each sample being tested. Furthermore, it means that the device can easily be scaled in the future to meet particular needs. Each slot fits a small cuvette and housing, with reflective film (to concentrate light output) on the inside, into which the appropriately engineered B. Subtilis is placed in desiccated form. By adding the analyte and potentially some germination medium, the B. Subtilis will begin to produce light that can be detected by the sensors above. A further potential addition to the whole design is to include a thermo-regulated box which would facilitate the germination of B.Subtilis spores (A prototype of which has been developed in the Cambridge MET department as part of a separate project); the germination time could also be improved using the motor controlled chassis to perform a shake cycle.

Further investigations

+ Show/Hide -

Many potential mechanical designs were considered during the course of this project and the final implementation of our prototype is not necessarily our view of a "Best Solution" but also one that we could demonstrate and develop easily over the course of the summer. Some major designs investigated were:
  • An integrated 2D array of detectors on a flat chip board that can be directly interfaced with an arduino. The analyte would be placed in micro-wells above the sensors and sealed off for complete darkness.
    • Advantages:
    • Compact
    • Potential for better sensing accuracy
    • Easier to interface with arduino
    Disadvantages:
    • No movement for an incubation cycle
    • Potentially expensive

  • Microfluidic architecture for cleaning out non-disposable containers and delivery of desiccated culture. There could be an array of sensors or a single rotary system
    • Advantages:
    • Closed system - better for transport and storage
    • Fully integratable system with lower margin for human error
    Disadvantages:
    • Expensive microfluidics!
    • Hard to debug spurious results

Electronics

Prototype

The system, as illustrated (right), is made up of a sensor, a motor, an arduino and a breadboard. A Bluetooth modem (Bluesmirf) can also act as an addition to allow the communication with mobile devices (e.g. Android tablets). The sensor is made up of two light dependent resistors that sit in a potential divider circuit allowing for a direct ratiometric output without further calculations needing to be made in the software. To distinguish between the two spectra from our bioluminescent output, plastic filter gels (like the ones used in theatres) have been glued to the top of the sensors. There is also a circuit for running a DC motor, which will turn the rotating parts of our device. The whole system has been incorporated into the mechanical chassis for an attractive, ergonomic overall design.

Further Investigations

+ Show/Hide -

In designing the electronic interface for our instrumentation we first considered different ways of obtaining information from the bacteria and the range of possibilities that exist for the processing of this information, below are a few important ideas we considered:
  • Colour sensors
    • Advantages:
    • Very good for giving an exact value of colour - narrow band detection
    Disadvantages:
    • Do not provide an intensity value unless using expensive sensors that would work better on an integrated sensor chip
    • More wires needed for data collection

  • Use of a Raspberry Pi
    • Advantages:
    • compact portable system that interfaces easily with arduino
    • cheap and highly flexible
    Disadvantages:
    • Requires external input and output devices
    • Not as nicely packaged for field work as e.g. a tablet

  • Digital readouts instead of potential divider circuit
    • Advantages:
    • No need to worry about circuit bias changing (e.g. with temperature, current)
    • Processing potentially more accurate (done on a computer)
    Disadvantages:
    • Larger potential for noise and discrepancies between channels that are not well matched
    • Less elegant solution, less intergrated

Software

Prototype

The software is being developed for both computers and android devices for extra flexibility whatever the final application of the product is. The computer software is written in the free open-source language python with cross-platform wxWidgets used to implement a GUI. The current idea is to develop a fully functional GUI for collecting sensor data from all six inputs and display these as line graphs and in a final bar chart. The data to the left was recorded by moving luciferase-producing E.coli being moved towards and away from the sensor. To the right is a screengrab of the GUI under development and testing its ratiometric ability. The higher values are when one sensor is covered, the lower for the other and no change is observed when both are illuminated equally. What is actually presented is the Morse Code of the word IGEM!!! The android GUI was made in Java using Eclipse based on Amarino open-source code. The first screen (shown below) asks for the MAC address of the Arduino device and currently the application can successfully connect and read real-time data from any Android phone/tablet (all versions are compatible).

Further investigations

+ Show/Hide -

Software is always the most flexible part of any instrumentation system as there are an infinite number of ways of presenting information to the data and an infinite number of ways to code this. As we are not working on a software project we tried to keep things simple, cheap (free!) and relatively light in terms of functionality. However, we did discuss other possibilities that might be considered by other programmers:
  • Programming languages
    • C++
      • Advantages:
      • Extremely flexible and useful for accessing serial ports
      • A huge amount of online documentation and help forums exist
      • Easily expandable with wxWidgets for developing GUIs>
      Disadvantages
      • Slightly cumbersome to program with
      • Requires compilation

Retrieved from "http://2012.igem.org/Team:Cambridge/Instrumentation"