Droplet based microfluidics
The purpose of this Jupyter Notebook is to work as a quick guide to the SDK development with the Elveflow products. The process is shown using a OB1 Pressure Controller with a FS5D Flow Sensor, but it works also for any other Elvesys product.
Before starting with this introduction, make sure you have read all the documentation related to your purchased products. Disregarding that information could increase the risk of damage to the equipment, or the risk of personal injuries. In case you don’t have a copy, you can download all the documents from our website.
The content of this chapter of the tutorial is the following:
This tutorial has been written and tested using Windows 10, 64bits, Python 3.8.8, Jupyter Notebook 6.3.0 in October, 2021. The pressure controller is an OB1 MK3+ and the flow sensor a FS5D.
The Elveflow Software Development Kit (SDK) latest stable version can be downloaded from the Elveflow website. To alleviate bandwidth and access issues, two links for the same file are provided. You can also find the ESI in the same zip archive file. In case you previously installed the ESI software, a zip folder will also have been added in the same folder of ESI. Unzip it at an easily accessible path like ‘C:/dev/SDK’ as for now, it is necessary to hardcode some paths on the library to customize it for your own system.
Then, go into: ‘../SDK/Python64’ (at the path where you unzipped the SDK), or your eauivalent for 32bits, open the file ‘Elveflow.py’ with a text editor and edit the fifth line of the code to match the path of your SDK.
# This python routine load the ElveflowDLL. # It defines all function prototype for use with python lib from ctypes import * ElveflowDLL=CDLL('C:/dev/SDK/DLL64/DLL64/Elveflow64.dll')# <- change this path
Now, change the paths of the following code cell to match the one of yours and run it. If everything is fine, it should not print any message on the screen.
# tested with Python 3.5.1 and 3.8.8 (IDE Eclipse V4.5.2 + Pydev V5.0.0) # add python_xx and python_xx/DLL to the project path # coding: utf8 import sys from email.header import UTF8 sys.path.append('C:/dev/SDK/DLL64/DLL64')#add the path of the library here sys.path.append('C:/dev/SDK/Python_64')#add the path of the LoadElveflow.py from ctypes import * from array import array from Elveflow64 import *
Did you get some outputs? Maybe something is wrong.
In some computers with 64bits, it is necessary to install some additional libraries. To do it, just go again into your SDK folder, find the path ‘../SDK/Installx64/Extra Install For x64 Libraries’ and run the setup application that you will find inside. Then, try to launch again the previous code cell.
Once the SDK has been correctly installed, it is also necessary to configure it to work with the desired system. If you previously installed the ESI, an application called NI MAX should have been installed as well. It is needed to check the exact name of the device.
How? First, connect your device to the power supply, connect its USB cable to the computer you are using and turn it on. After that, go to Windows search bar and type ‘NI MAX’ without the quotes. It should appear as the first result as you can see in the following figure:
Then, just unzip the left tabs: ‘My System > Devices and Interfaces > …’ like you can see as follows.
If you don’t have more National Instrument’s devices connected to your computer, the only result should be the OB1 Pressure Controller (or the one that you try to configure). Click on it and write down its Serial Number. You will need it for your custom software to interact with the device. In this example, the device Serial Number is 01BECD3F.
The next step is to know the arrangement of pressure regulators that your system has, because our OB1 can be customized to have the right pressure setup for the client. In order to identify them, you can check it on the OB1 User guide, at the installation chapter.
Each regulator value has a different encoding value. The correspondance is the following:
I am raw html block.Click edit button to change this html
At max, the OB1 controller will have four pressure outputs, thus, in the OB1_Initialization() call of the following code cell, after the serial number, you must specify the regulator type of every channel, setting a zero if a channel is not physically installed. In the following code, only two pressure outputs are installed with regulators of type 3 and 2 respectively.
# # Initialization of OB1 ( ! ! ! REMEMBER TO USE .encode('ascii') ! ! ! ) # Instr_ID = c_int32() print("Instrument name and regulator types are hardcoded in the Python script") # See User Guide to determine regulator types and NIMAX to determine the instrument name # error = OB1_Initialization('01BECD3F'.encode('ascii'),3,2,0,0,byref(Instr_ID)) error = OB1_Initialization('01CF6A61'.encode('ascii'),2,3,4,4,byref(Instr_ID)) # All functions will return error codes to help you to debug your code, for further information refer to User Guide print('error:%d' % error) print("OB1 ID: %d" % Instr_ID.value)
Instrument name and regulator types are hardcoded in the Python script error:0 OB1 ID: 0
If everything went fine, you should have received a simple message as follows:
If it is not the case, one or several of the following issues can be happening:
Once the OB1 has been fully configured, the sensor, or sensors, must be added so they can be read later. To do it, the function: “OB1_Add_Sens()” must be called.
The arguments for the function are:
To know the sensor type you can use this table which can be also found at the end of the SDK guide:
Note. Level sensor type stands for all types of level sensor such as bubble detector.
The following is the encoding of the possible resolution bits:
# Add one digital flow sensor with water calibration (OB1 MK3+ only), all information to declare sensors are described in the User Guide # error = OB1_Add_Sens(Instr_ID, 2, 4, 1, 0, 7, 0) # (CustomSens_Voltage_5_to_25 only works with CustomSensors and OB1 from 2020 and after) # To test the pressure sensors error=OB1_Add_Sens(Instr_ID, 1, 10, 0, 0, 7, 0) error=OB1_Add_Sens(Instr_ID, 2, 10, 0, 0, 7, 0) error=OB1_Add_Sens(Instr_ID, 3, 10, 0, 0, 7, 0) print('error add digit flow sensor:%d' % error)
error add digit flow sensor:0
Here you can choose, essentially, one of the three available options: default, load and new. The calibration consists of an array which stores the actual values associated to your instrument.
If you previously proceeded with a calibration process, you can load it from the Calib_path that you must previously specify. Otherwise, if you want to run a calibration process, ensure that ALL channels are properly closed with adequate caps. You can find more detailed instructions about the calibration procedure at the OB1 User Guide.
Calib = (c_double*1000)() # Always define array this way, calibration should have 1000 elements while True: answer = input('select calibration type (default, load, new ) : ') Calib_path = 'C:\\Users\\Public\\Desktop\\Calibration\\Calib.txt' if answer == 'default': error = Elveflow_Calibration_Default (byref(Calib),1000) break if answer == 'load': error = Elveflow_Calibration_Load (Calib_path.encode('ascii'), byref(Calib), 1000) break if answer == 'new': OB1_Calib (Instr_ID.value, Calib, 1000) error = Elveflow_Calibration_Save(Calib_path.encode('ascii'), byref(Calib), 1000) print('Calib saved in %s' % Calib_path.encode('ascii')) break
select calibration type (default, load, new ) : default
The expected output would be something like:
And nothing else.
Once that your system is configured and running, you can run the following main routine with which you will be able to basically control the instrument’s pressure output as well as to read the pressure and flow signal if desired.
You can see a summary of the commands of the example at the following table:
Note. If you need to check the usage of one function from our SDK, you can find the API reference at the SDK User Guide at any moment.
while True: answer=input('what to do (set_p, get_p, get_sens, or exit) : ') if answer=='set_p': set_channel=input("select channel(1-4) : ") set_channel=int(set_channel) # convert to int set_channel=c_int32(set_channel) # convert to c_int32 set_pressure=input("select pressure (-1000 to 8000 mbars) : ") set_pressure=float(set_pressure) set_pressure=c_double(set_pressure) # convert to c_double error=OB1_Set_Press(Instr_ID.value, set_channel, set_pressure, byref(Calib),1000) if answer=="get_sens": data_sens=c_double() set_channel=input("select channel(1-4) : ") set_channel=int(set_channel) # convert to int set_channel=c_int32(set_channel) # convert to c_int32 error=OB1_Get_Sens_Data(Instr_ID.value,set_channel, 1,byref(data_sens)) # Acquire_data=1 -> read all the analog values print('Press or Flow ch', set_channel.value,': ',data_sens.value) if answer=='get_p': set_channel=input("select channel(1-4) : ") set_channel=c_int32( int(set_channel) ) # convert to c_int32 get_pressure=c_double() error=OB1_Get_Press(Instr_ID.value, set_channel, 1, byref(Calib),byref(get_pressure), 1000) # Acquire_data=1 -> read all the analog values print('error: ', error) print('ch',set_channel,': ',get_pressure.value) print( 'error :', error) if answer=='exit': break
what to do (set_p, get_p, get_sens, or exit) : set_p select channel(1-4) : 1 select pressure (-1000 to 8000 mbars) : 300 error : 0 what to do (set_p, get_p, get_sens, or exit) : get_sens select channel(1-4) : 2 Press or Flow ch 2 : 123.98571679255377 error : 0 what to do (set_p, get_p, get_sens, or exit) : get_sens select channel(1-4) : 1 Press or Flow ch 1 : 255.49368963149433 error : 0 what to do (set_p, get_p, get_sens, or exit) : get_sens select channel(1-4) : 3 Press or Flow ch 3 : -24.7761020828564 error : 0 what to do (set_p, get_p, get_sens, or exit) : set_p select channel(1-4) : 1 select pressure (-1000 to 8000 mbars) : 0 error : 0 what to do (set_p, get_p, get_sens, or exit) : exit error : 0
The output can be something like the following:
what to do (set_p, get_p, get_sens, or exit) : get_sens select channel(1-4) : 2 Press or Flow ch 2 : 4.724137931034483 what to do (set_p, get_p, get_sens, or exit) : exit error : 0
Here it finishes the first part of the tutorial. Go for the second part to know how to perform automatic control with our instruments.
How can we help you?
Name*
Email*
Message
Newsletter subscription
We will answer within 24 hours
By filling in your info you accept that we use your data.
Do you want tips on how to best set up your microfluidic experiment? Do you need inspiration or a different angle to take on your specific problem? Well, we probably have an application note just for you, feel free to check them out!
Microfluidics is the science of handling small amounts of liquids, inside micrometer scale channels. Discover how to handle fluids for your microfluidic experiments.
This application note demonstrates a smart use ouf Elveflow's Pressure sensor and sensor reader for Direct-Ink-Writing flow control.
This user guide will show you how to run microfluidic colocalization studies of single molecule spectroscopy.
This application note explores the basic principle of pneumatic pumps and a flow controller based on the basic principle of pneumatic pumps, known as pressure driven flow control. It also demonstrates the applications of pressure driven flow control in a range of industrial & research fields.
Flow regulation is a compulsory operation in most of the microfluidics operations. In some applications such as 2D or 3D cell culture, flow regulation is essential since accurate micro-environmental parameters control is required. Elveflow do it’s best to make this operation as easy as possible to help you to focus on what really matter in your setup.
Study the impact of molecular transport on cell cultures with a cross flow membrane chip and microfluidic instruments.
Precise liquid injection system for manipulation of small volumes of fluids using the MUX distribution and the MUX recirculation valve.
This application note explains how to set up a robust and reproducible microfluidic platform for liposomes assembly with improved encapsulation efficiency and reduced polydispersity in size.
Single-wall carbon nanotubes (SWCNTs) are considered as quasi 1-dimensional (1D) carbon nanostructures, which are known for their outstanding anisotropic electronic, mechanical, thermal and optical properties.
This application note describes how to combine and synchronise liquid perfusion and imaging using an Olympus spinning disc confocal microscope together with an Elveflow pressure-driven flow controlled microfluidic system.
Mixing is a crucial step for several microfluidic applications like chemical synthesis, clinical diagnostics, sequencing and synthesis of nucleic acids
This application note describes how microfluidic can be employed as a nanoparticle generator based on the example of PLGA bead generation.
Learn how to perform PLGA nanoparticle preparation with Elveflow instruments and a microfluidic chip
The application note describes how to convert various units of shear stress and/or pressure from one to another: shear stress conversion from Pascal, atmosphere, and N/m²...!
Get a quote
Collaborations
Need customer support?
Serial Number of your product
Support Type AdviceHardware SupportSoftware Support
Subject*
I hereby agree that Elveflow uses my personal data Newsletter subscription
Message I hereby agree that Elveflow uses my personal data Newsletter subscription