Team:UC Davis/Potentiostat Design
From 2014.igem.org
Line 69: | Line 69: | ||
<img src="http://web.chem.ucsb.edu/~kwp/cheapstat/cheaplayout.png" height="250px"/><img src="https://static.igem.org/mediawiki/2014/0/03/CheapStatActual.png" height="250px"/> | <img src="http://web.chem.ucsb.edu/~kwp/cheapstat/cheaplayout.png" height="250px"/><img src="https://static.igem.org/mediawiki/2014/0/03/CheapStatActual.png" height="250px"/> | ||
- | The CheapStat is a budget friendly device developed at UC Santa Barbara several years ago. We aspired to build this circuit and modify the software for our purposes, however, the microcontroller on the CheapStat was controlled predominantly in machine level code. The learning curve seemed unreasonable considering our deadline, so we had to find another solution.<br><br>We were forced to build our own. With a clean slate, we wanted to create a device that would fulfill our needs, but also be welcomed by the iGEM community. We aimed to match the performance of the CheapStat, but also improve in three ways: increase the effective range of the instrument, decrease the cost of the circuit, and convert to an arduino-friendly microcontroller. In this capacity, we have succeeded.<br><br> We modeled our circuit after the CheapStat, eventually including more than 30 components. We went on to create five iterative prototypes. The schematic and board files for the various prototypes are all available <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Software | + | The CheapStat is a budget friendly device developed at UC Santa Barbara several years ago. We aspired to build this circuit and modify the software for our purposes, however, the microcontroller on the CheapStat was controlled predominantly in machine level code. The learning curve seemed unreasonable considering our deadline, so we had to find another solution.<br><br>We were forced to build our own. With a clean slate, we wanted to create a device that would fulfill our needs, but also be welcomed by the iGEM community. We aimed to match the performance of the CheapStat, but also improve in three ways: increase the effective range of the instrument, decrease the cost of the circuit, and convert to an arduino-friendly microcontroller. In this capacity, we have succeeded.<br><br> We modeled our circuit after the CheapStat, eventually including more than 30 components. We went on to create five iterative prototypes. The schematic and board files for the various prototypes are all available <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Software">here</a>. <br><br> |
<b>To read more about the OliView hardware, click <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Inspiration_Iteration" class="brightlink">here</a>.</b> | <b>To read more about the OliView hardware, click <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Inspiration_Iteration" class="brightlink">here</a>.</b> | ||
Line 85: | Line 85: | ||
<p> | <p> | ||
<img src="https://static.igem.org/mediawiki/2014/d/d2/OliViewScreenShot.png" height="250px" style="float:left;margin-right:20px;margin-bottom:20px;" />The OliView software was written in C++ within the Qt Creator IDE. The backend of the software includes the GNU-licensed library QCustomPlot for graphing, and the open-source biquad library by Nigel Redmon, for digital signal processing. These elements have been incorporated with more than 1,200 lines of UC Davis code to create a feature-rich environment for controlling the OliView potentiostat. Our progress was updated through the UCDiGEM <a href="http://github.com/UCDiGEM/OliView" class="brightlink">OliView Github</a> . We included features for statistical analysis as well a .CSV exporting feature<br><br> | <img src="https://static.igem.org/mediawiki/2014/d/d2/OliViewScreenShot.png" height="250px" style="float:left;margin-right:20px;margin-bottom:20px;" />The OliView software was written in C++ within the Qt Creator IDE. The backend of the software includes the GNU-licensed library QCustomPlot for graphing, and the open-source biquad library by Nigel Redmon, for digital signal processing. These elements have been incorporated with more than 1,200 lines of UC Davis code to create a feature-rich environment for controlling the OliView potentiostat. Our progress was updated through the UCDiGEM <a href="http://github.com/UCDiGEM/OliView" class="brightlink">OliView Github</a> . We included features for statistical analysis as well a .CSV exporting feature<br><br> | ||
- | The downloads section includes all the files necessary to build and run the OliView system. Schematic and board files for the OliView potentiostat are provided in Eagle V6.6 format. CAM processing files have been optimized for production by <a href="http://www.seeedstudio.com | + | The downloads section includes all the files necessary to build and run the OliView system. Schematic and board files for the OliView potentiostat are provided in Eagle V6.6 format. CAM processing files have been optimized for production by <a href="http://www.seeedstudio.com">Seeed Studios, Inc</a>. |
<br><br> | <br><br> | ||
<b>To read more about the OliView hardware, click <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Software" class="brightlink">here</a>.</b> | <b>To read more about the OliView hardware, click <a href="https://2014.igem.org/Team:UC_Davis/Potentiostat_Design_Software" class="brightlink">here</a>.</b> |
Revision as of 22:20, 17 October 2014
A potentiostat is an instrument capable of maintaining a voltage bias between electrodes. The bias encourages diffusion but more importantly the transfer of electrons which are recorded, and ultimately related to the species present in solution. When faced with the decision to buy or build our potentiostat, we found that the available solutions did not fit our needs. We decided to create our own. We developed an abstract and found a microcontroller with a 16-bit ADC (13 bit ENOB). We then designed, modeled, built and tested our potentiostat under a range of conditions. We went on to create a catalog of prototypes. The final product is the OliView potentiostat: The first arduino-compatible potentiostat to incorporate a 16-bit ADC.
Hardware
The CheapStat is a budget friendly device developed at UC Santa Barbara several years ago. We aspired to build this circuit and modify the software for our purposes, however, the microcontroller on the CheapStat was controlled predominantly in machine level code. The learning curve seemed unreasonable considering our deadline, so we had to find another solution.
We were forced to build our own. With a clean slate, we wanted to create a device that would fulfill our needs, but also be welcomed by the iGEM community. We aimed to match the performance of the CheapStat, but also improve in three ways: increase the effective range of the instrument, decrease the cost of the circuit, and convert to an arduino-friendly microcontroller. In this capacity, we have succeeded.
We modeled our circuit after the CheapStat, eventually including more than 30 components. We went on to create five iterative prototypes. The schematic and board files for the various prototypes are all available here.
To read more about the OliView hardware, click here.
Software
The OliView software was written in C++ within the Qt Creator IDE. The backend of the software includes the GNU-licensed library QCustomPlot for graphing, and the open-source biquad library by Nigel Redmon, for digital signal processing. These elements have been incorporated with more than 1,200 lines of UC Davis code to create a feature-rich environment for controlling the OliView potentiostat. Our progress was updated through the UCDiGEM OliView Github . We included features for statistical analysis as well a .CSV exporting feature
The downloads section includes all the files necessary to build and run the OliView system. Schematic and board files for the OliView potentiostat are provided in Eagle V6.6 format. CAM processing files have been optimized for production by Seeed Studios, Inc.
To read more about the OliView hardware, click here.
Build Your Own
There five easy steps to getting started:
1. Order the PCB and the parts from the parts list.
Ready to build you own?, click here.