📖
eVOLVER
  • eVOLVER Documentation Wiki
  • General
    • About Us
    • eVOLVER Community
      • Code of Conduct
  • Getting Started
    • Buying eVOLVER
    • Part Sourcing
    • Unboxing and Setting Up
    • Software Installation
      • DPU Installation
      • Electron App (GUI) Installation
    • Configuring Computer and Networking
      • Router Setup
    • Calibrations
      • Temperature Calibration
      • Optical Density Calibration
      • Pump Calibration
      • Manual Calibration - calibrate.py
  • Upgrade Base eVOLVER Hardware
  • Experiments
    • Starting an Experiment
      • Carboy Media Prep
      • Preparing Vials
      • Setup Waste Carboy
      • Sterilizing Lines
      • Loading Vials and Setting Initial Conditions
      • OD Blank
      • GUI Start Guide
      • Command Line Start Guide
      • Cleaning Up After Experiment
    • Growth Curve
    • Chemostat
    • Turbidostat
    • FAQs
    • Tips and Tricks
  • Guides
    • Use the GUI to Control Parameters
    • Building a Smart Sleeve
    • Making media bottles and splitters
    • Emergency Efflux
    • View the Server Log and Restart Server
    • Updating the eVOLVER Server
    • Change Your conf.yml File
    • Arduino Software Installation
    • Raspberry Pi Configuration
    • Command Line Usage
    • Millifluidics Guides
      • Designing Millifluidics Using Eagle
      • Constructing Laser Cut Millifluidics
      • Constructing Millifluidics via SLA Printing
      • Calibrating IPPs
      • Operating Millifluidics
  • Troubleshooting
    • Troubleshooting Overview
    • Experiment Troubleshooting
      • Contamination
      • Vial Overflow, Pump Failure, and Spills
      • Tubing and Connector Blockage and Bursting
    • Optical Density (OD) Readings
    • Vial Troubleshooting
      • Replacing Photodiodes and LEDs
      • Heating Element
      • Stirring
    • Server Troubleshooting
    • Vial Platform Troubleshooting
      • Motherboard Troubleshooting/Replacement
      • 12V Power Supply Troubleshooting/Replacement
    • GUI Troubleshooting
    • eVOLVER Maintenance
  • Hardware
    • Overview of Hardware Architecture
    • Overview of Fluidics
      • Tubing and connectors
      • Peristaltic Pumps
      • Fluidics box
    • Overview of Millifluidics
      • IPPs (Integrated Peristaltic Pumps)
      • Pressure Regulator
    • Vial Caps
      • Universal Vial Cap Construction Guide (Luer Connectors Only)
      • 5 and 7 Port Nylon Tubing Caps Construction Protocol
    • Smart Sleeve
      • Vial Board
      • 🌪️Stirring
      • Temperature
      • Optical Density
        • OD90 vs OD135
    • Motherboard Layout and Circuitry
      • 🌡️Arduino
      • Sensor/Actuator Board Slots
      • Pulse Width Modulation (PWM) Boards
      • Analog-to-Digital Converter (ADC) Boards
    • Raspberry Pi
    • Chassis
    • Light Blocker / Splash Guard
    • Known Issues
  • Software
    • Overview of Software Architecture
    • DPU
      • Calibration
      • custom_script.py
      • Experiment Data Files
      • eVOLVER.py
    • Arduino
    • Server (Raspberry Pi)
      • Calibration Files
      • Configuration Files (conf.yml)
    • Known Issues
  • Extensions
    • Adding A New Experimental Parameter
      • Power Supply
      • Specific Applications
      • Custom Calibration Code
    • Custom Experiments
      • ePACE
        • ATTiny1634 Writing
        • LUX Board Troubleshooting
      • Morbidostat
      • Extractor Column
        • Extractor Volume Maintenance
        • Experiment Start
          • Sterilizing Extractor Fluidics
          • Setting up your experiment
          • Using the extractor script
        • Extractor Analysis
        • Troubleshooting
        • Example protocols
      • Phototroph Growth
        • Setup Phototroph eVOLVER
        • Photo-eVOLVER Smart Sleeves
          • Photo-eVOLVER Smart Sleeve Construction Guide
        • Experiment Guide
    • Custom Fluidics
      • Adding a Third Pump Rack
      • Bubblers / In-Vial Aeration
        • Bubbler Construction Protocol
        • Bubbler Cleaning Protocol
      • Running the slow pumps
    • min-eVOLVER
      • About
      • min-eVOLVER Construction
        • Parts
        • Construction Protocol
      • Fluidics Setup
      • Software Installation and Startup
      • send_command.py
      • Calibrations
      • Starting an Experiment
      • ePACE with min-eVOLVER
        • [v1.1] ePACE with min-eVOLVER
      • Troubleshooting
    • Interfacing with Other Systems
  • Contributing
    • Guidelines for Contribution
    • Reporting a Bug / Hardware Failure
    • Documentation
      • Making a Forum Post
      • How to Edit the Wiki
    • Software Development
    • Hardware Development
Powered by GitBook
On this page
  • Questions?
  • Software Installation
  • Server Startup
  • Multiple min-eVOLVERs
  • Test min-eV Hardware
  • Startup
  • Familiarize yourself with send_command.py and make sure you can:
  • test_hardware.py

Was this helpful?

Edit on GitHub
Export as PDF
  1. Extensions
  2. min-eVOLVER

Software Installation and Startup

PreviousFluidics SetupNextsend_command.py

Last updated 1 year ago

Was this helpful?

Questions?

Ask questions about this guide on the forum .

As with the main eVOLVER, you should have a dedicated computer to run min-eVOLVER. We recommend Macs for their stability and ease software of installation.

Software Installation

  1. Download files from GitHub repositories for the (experiment code) and (communicator with min-eVOLVER).

    1. We will use the virtual environment made here to run the experiment

    2. Note: as of now, there is no GUI integration. Command line only.

  1. Create a server virtual environment

    1. In the command line still, open a new tab or window

    2. If necessary, deactivate the dpu virtual environment with the command below.

      1. deactivate

    3. Navigate to the server directory evolver-min

    4. Make a server virtual environment

      1. To avoid confusion with the dpu environment, call your server virtual environment server-env

      Mac:

      python3.9 -m venv server-env

      source server-env/bin/activate

      Windows PowerShell:

      py -3.9 -m venv server-env

      server-env\Scripts\Activate.ps1

    5. Use poetry to install all necessary dependencies.

      poetry install

If you are setting up more than one min-eVOLVER, simply make an additional folder and label it something like evolver-min2. No need to make an additional virtual environment. Any time you need to start a server just use the one you made in the first server folder.

Server Startup

  1. Plug the min-eVOLVER in to your computer using micro-USB and THEN plug it in to the 12V DC power supply.

Plugging in the 12V first may make the server not able to connect properly.

Whenever possible, avoid plugging / unplugging the min-eVOLVER micro-USB, which is fragile. Instead, leave the micro-USB plugged in and plug / unplug the regular USB to your computer.

  1. Make sure that you are in the server virtual environment

  2. This means navigating to the server folder in a command line window and inputting commands:

    1. Mac OS:

      source server-env/bin/activate

    2. On Windows PowerShell:

      server-env\Scripts\Activate.ps1

  3. Navigate to the /evolver/ folder inside the evolver-min server code

  4. Attempt to run the server using the following command:

    1. Mac OS: python3 evolver.py

    2. Windows Powershell: py evolver.py

Hereafter, only the Mac OS command will be given. Windows users, swap python3 with py.

  1. This will tell you the list of min-eVOLVERs plugged in to the computer

  2. Exit from the server log using control + C

  3. Copy the full port address into the serial_port variable in the conf.yml file for the server

    1. On Mac OS for example: serial_port: /dev/cu.usbmodem1301

Be careful to not alter the conf.yml file structure, only the variables (after the ":"). Changing the file structure in the wrong way will result in the server failing to run.

  1. Start the server using python3 evolver.py

  2. Observe the server for expected behavior

    1. The server cycles once every 20 seconds

    2. If the server is not connected to the min-eVOLVER, commands will fail

Multiple min-eVOLVERs

You can connect multiple min-eVOLVERs to one computer, as long as you have enough USB ports!

  1. Make a duplicate min-eVOLVER server code file with a new number ie evolver-min2

  2. Plug in the new min-eVOLVER and follow the Server Startup guide

    1. The new min-eVOLVER will have a different serial_port because it is plugged in to a different USB port

    2. You need to define a different port number (try 5556) in the conf.yml file

  3. Make sure you're in the right server code folder when starting the new server

  4. Use a different command line window for each min-eVOLVER server

Make sure you don't swap your min-eVOLVERs USB ports without meaning to!

  • Calibration files are for a specific min-eVOLVER

  • serial_port numbers on your computer are linked to a specific USB port, NOT to a specific min-eVOLVER

  • So for example:

    • min-eVOLVER 1 with serial_port: /dev/cu.usbmodem1201

    • min-eVOLVER 2 with serial_port: /dev/cu.usbmodem1301

    • Plugging min-eVOLVER 2 into /dev/cu.usbmodem1201 will mean that running the min-eVOLVER 1 server will load calibrations for the wrong min-eVOLVER and vice versa

Test min-eV Hardware

Startup

  1. Plug in the micro-USB and then the 12V power supply

  2. Start the server

  3. In another terminal window, enter the dpu virtual environment

  4. Navigate to the /dpu/experiment/ folder

  1. Send a pump command to all pumps to make sure they actuate

  2. Send a command to start and stop stirring

  3. Turn temperature off

  4. Check the server log as commands go in, these should be received and become the new values in the server cycle

test_hardware.py

  1. Run a full hardware test using test_hardware.py

  2. Use the command: python3 test_hardware.py

  1. Check that all pumps actuate individually

  2. Check that stirring turns off and on

  3. Check that OD sensing works as expected (values decrease with OD LED on)

    1. Look at the "Data from min-eVOLVER" for the below values

    2. Example values with OD LED OFF: 'od_90': ['65208', '65190']

    3. Example values with OD LED ON: 'od_90': ['62515', '59678']

  4. Check to see that the temperature values decreased towards [25000,25000] over time as the script is running

    1. Example start values: 'temp': ['35514', '35440']

    2. Example end values: 'temp': ['30618', '31029']

Follow the dpu installation .

Optional: for more information about the eVOLVER server you can check .

If using more than one min-eVOLVER, check the at the bottom of this page

If you want to know more about the server code or how commands work click .

Familiarize yourself with and make sure you can:

guide
here
here
send_command.py
note
here
dpu
server
Make sure you are on the 'min' branch (upper left) and click the code button to download the .zip file for the code
An example min-eVOLVER server readout.
An example data output from the min-eVOLVER, soon after it has been turned on. This same data can be found continuously in the server window.