EDR4 & EDA

Elements Data Reader

The EDR4 software interface enables an easy control of all the eONE, multichannel amplifiers and nanopore readers, showing and saving data in real time. Input current ranges, bandwidth, voltage stimuli and electrode offset compensation can all be easily selected and modified.

Resistance, Capacitance and rms noise can be continuously monitored.

Data can be stored in commonly used formats like .dat or .abf

The online analysis module enhances the EDR4 features.

A variety of analysis can be done on live experiments, such as current histograms, Dwell and inter-event time histograms, I/V graph, FFT.

Elements Data Analyzer

Elements Data Analyzer is a data visualization and analysis software for data acquired with Elements instruments in the .dat and .abf format. The intuitive graphical user interface allows a quick and easy data visualization. EDA performs fast data conversion between the supported data format (.dat, .abf and .csv).

Supported features are current histograms, current events detection, current spectrum (FFT), I/V graph, current step detection, filters. Lab book entries are visualized as labels on the current traces.

Application Programming Interface

Master your Elements’ amplifier by programmatically controlling it via the communication libraries.

Via the libraries you can:

  • Script complex behavior that will be executed automatically
  • Implement closed loop controls to make your amplifier react to the acquired signals
  • Use the amplifier in combination with other laboratory instrumentation

The libraries are provided as static or dynamic C++ libraries. For some amplifiers, Python and/or labVIEW® wrappers are available. 

Compatibility with Devices

Open EDR Software and click the “?” menu and select “Device Information”. Check if the connected device that you have is compatible with EDR4 based on the table below. If your device is not compatible, please download EDR3 here. 

 

Model                  Version                      Subversion Firmware
e1b 9

2

       >=4
eONE-Light 9

4

       >=2
9

7

       >=1
eONE-Plus 9

5

       >=6
9

8

       >=1
eONE-HC 9

6

       >=7
9

9

       >=1
Nanopore Reader 100 kHz 8

2

       >=8
Nanopore Reader 10 MHz

Not compatible
ePatch VC and VC-CC

Not compatible
e4 4

8

       >=15
e16 3

8

       >=11
e16-HC

Compatible with all subv. and firmw.

Requirements

Minimum:

  • Windows 10, 11
  • Dual core 2.0 GHz CPU
  • 4 GB RAM
  • 1366 x 768 Display
  • 1 USB 2.0 port

Recommended:

  • Quad core 2.6 GHz CPU
  • 8 GB RAM
  • 1920 x 1080 Display

API

Libraries Terms and Conditions

  • License: for free, MIT license
  • Distribution: provided as-is (*), without warranty
  • Support: no guaranteed support (**)

If you find any bugs feel free to contact [email protected] to report them.

 

Documentation and Usage

  • Entry Functions: all the entry functions of the libraries are documented with doxygen style comments in the main header files
  • Libraries Basic Usage: the basic usage of the libraries is shown via example projects packed within the library bundle
  • Readme File: please read the readme file included in the library bundle for additional info

 

Important note

Control loops closed by the software are inherently subject to loop delays due to the software/amplifier communication and the data buffering. Therefore, delays of up to tens of milliseconds are to be expected. For this reason, this functionality can only work for tasks like unclogging a pore with a voltage pulse, but not for tasks that require microsecond reaction times.

 

Link to download

 

(*) Modifications to the libraries, such the addition of new features, will be invoiced. Any new feature developed by Elements on request, and developed for a fee, will be released as open source code and it will be usable by Elements to improve the documentation or to help other customers.

(**) Free support is provided only for clarifications, in case the documentation is effectively lacking. For any other kind of support, Elements will estimate the required effort and invoice accordingly. Any additional code developed by Elements on request, and developed for a fee, will be released as open source code and it will be usable by Elements to improve the documentation or to help other customers.