Team:TU-Eindhoven/LEC/Device

• Introduction
  • Home page
  • Background
    information
  • About us
  • Contact us
  • Our photos
• Project
  • Project description
  • Lab approach
  • Device information
  • Initial model
  • Yeast model
  • Lab results
  • Our BioBricks^TM
  • Our
    accomplishments
• Considerations
  • Public outreach
  • Safety questions
  • Other thoughts
• Future applications
  • Human interest
  • Further
    developments
• Notebook
  • Before week 1
  • Week 1
  • Week 2
  • Week 3
  • Week 4
  • Week 5
  • Week 6
  • Week 7
  • Week 8
  • Week 9
  • Week 10
  • Week 11
  • Week 12
  • After week 12
  • Lab protocols
• Partners
  • ICMS TU/e
  • Team collaborations
  • Attributions and Contributions
  • Our sponsors

A picture of our finished device. This will be used to test the response of the yeast cells to electrical stimulation in the laboratory.

The heart of the screen

We have yeast cells that light up when an electric current passes over the membrane. To complete our SOMY-LCD, we also needed something that makes the current on the right places at the right time. For this purpose we created a device with software to provide this control. We will use the yeast in a fluid culture so it can be easily refreshed and in the future the ‘food’ for the yeast can be refilled for long time use of the screen. The fluid culture will consist of a single large medium bath, this causes the resolution to be limited by the device that is used to control the cells only.

Device

The use of a fluid yeast culture adds some requirements to our device, because now the device not only has to be fully bio-compatible (non-toxic to the yeast), it also has to survive in the harsh conditions of electrolysis in water and high ion concentrations. Therefore we couldn’t use copper for the electrodes. Not only is copper, as a heavy metal, highly toxic to our yeast, the copper would react with the electrolysis releasing the toxic copper ions into the solution and corroding away our electrodes.

Therefore platinum was chosen as the electrode material and we made sure that this was the only metal that came into contact with the medium. All the other metals are covered by either resin or plastic. Because we use the device with living cells we need a way to clean the device properly, therefore all the materials can withstand the temperature of autoclavation and the device can be easily decoupled from the PC to device interface.

For the interface between the PC and the device we used two USB-DAQs (Data AcQuisition). Both of them have 4 output channels. By using a matrix configuration for our device we have 16 pixels with these 8 electrodes. These DAQs are then controlled by LabVIEW, in which thus our device software is written. The DAQs can have an output voltage of +10V to -10V with a maximum output of 10mA.

Software

During the development of the software, a few stages are passed. The first version of the software was capable of setting a different voltage to every channel, but this had to be done manually. Although this is enough to test the device in the lab environment, it can’t produce even a single image on the screen.

The first step to creating an image is to keep a pixel on without constantly providing an electric signal. Thus some sort of periodic signal is needed. We achieved this by implementing a single square wave to one pixel. Now a periodic on/off signal can be given to one pixel, which results in one pixel being constantly ‘on’.

To do this for all pixels, we need 16 square waves (one per pixel). These square waves then are dephased so that only one square wave gives an ‘on’ signal at a time. This allows us to display a single image constantly on our screen. To display multiple images we looked at time. We used the time to select which of the images should be shown and reset the square waves so that they are synchronized with the change of the image so that the device now can produce a moving image.

However this software still has a lot of overhead (inefficient use of CPU time) as we have a square wave for each pixel while only one is in the ‘on’ state at any given time. By using the time again we cut it down to just one square wave. The advantages this brings isn’t measurable with 16 pixels, but a Full HD screen containing 2.073.600 pixels, has to calculate 2.073.599 less square waves due to this small change in the software.