Pyexplabsys

PyExpLabSys Documentation
Release 1.5
CINF
Feb 09, 2018

Contents
1 Overview 3
1.1 Project Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Python 3 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 User Notes 17
2.1 Setting up logging of your program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Activating PyExpLabSys library logging in you program . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 Using PyExpLabSys drivers outside of PyExpLabSys . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 Common Software Components 21

3.1 The database_saver module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2 The loggers module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 The plotters module plotter backends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4 The sockets module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.5 The socket_client module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.6 The utilities module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.7 The combos module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.8 The settings module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4 File parsers 65
4.1 XML based file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.2 Binary File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5 Apps 73
5.1 The Bakeout App . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6 Hardware Drivers 75
6.1 The bio_logic module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2 The 4d Systems module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.3 The pfeiffer module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7 Hardware Drivers Autogenerated Docs Only 111

7.1 The NGC2D module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
7.2 The agilent_34410A module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
7.3 The agilent_34972A module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
7.4 The bronkhorst module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
i
7.5 The brooks_s_protocol module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7.6 The cpx400dp module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.7 The crowcon module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.8 The dataq_binary module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.9 The dataq_comm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.10 The edwards_agc module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
7.11 The edwards_nxds module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.12 The epimax module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.13 The freescale_mma7660fc module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.14 The fug module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.15 The galaxy_3500 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.16 The honeywell_6000 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
7.17 The inficon_sqm160 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.18 The innova module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.19 The intellemetrics_il800 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.20 The isotech_ips module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
7.21 The keithley_2700 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.22 The keithley_smu module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.23 The kjlc_pressure_gauge module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
7.24 The lascar module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
7.25 The mks_925_pirani module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
7.26 The mks_937b module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
7.27 The mks_g_series module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.28 The mks_pi_pc module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.29 The omega_D6400 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.30 The omega_cn7800 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7.31 The omega_cni module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7.32 The omegabus module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.33 The omron_d6fph module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.34 The pfeiffer_qmg420 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.35 The pfeiffer_qmg422 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.36 The pfeiffer_turbo_pump module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7.37 The polyscience_4100 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.38 The rosemount_nga2000 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.39 The scpi module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.40 The specs_XRC1000 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7.41 The specs_iqe11 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7.42 The srs_sr630 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
7.43 The stahl_hv_400 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
7.44 The stmicroelectronics_ais328dq module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.45 The stmicroelectronics_l3g4200d module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.46 The tenma module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.47 The vivo_technologies module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
7.48 The wpi_al1000 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
7.49 The xgs600 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8 How To’s 155

8.1 The Bakeout Box HOWTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
9 Developer Notes 157

9.1 Setting up logging for a component of PyExpLabSys . . . . . . . . . . . . . . . . . . . . . . . . . . 158
9.2 Editing/Updating Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
9.3 Writing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
ii
10 Indices and tables 165
Python Module Index 167
iii
iv
PyExpLabSys Documentation, Release 1.5
This page serves as documentation for the software activities at CINF. Of interest to the public are hardware drivers
for experimental equipment and data logging clients but the page also contain documentation for setup specific code.
Contents:
Contents 1
2 Contents
CHAPTER 1
Overview
This page contains different overviews of the PyExpLabSys archive and can work as an entry point for a new user.
Section Project Overview contains a short explanation of the different components that PyExpLabSys consist of and
the source code and documentation entries that are relevant for that part.
The table in section Module Overview contains an overview of all the modules in PyExpLabSys. The overview consist
of a short description (the first line of the module docstring) and its Python 2/3 support status.
PyExpLabSys strive to support Python version 2.7 and >=3.3. See the section Python 3 support about Python 3
support.
1.1 Project Overview
This section will explain how the different components of PyExpLabSys (and its sister project cinfdata) fits together.
The overall structure is illustrated in the overview figure. On the aquisition level, there is a number of machines which
could be e.g. Raspberry Pi’s or laboratory PC’s, which will use different parts of PyExpLabSys depending on its
purpose.
Machine 1 e.g. is used to parse already aquired data from local data files (File parsers) and send that data to the
database (Database Savers). Machine 2 aquires data via an equipment drivers (Drivers) and makes it available to
other machines on the network (Sockets) and uploads it to the database (Database Savers). Like machine 2, machine
3 also aquires data directly (Drivers), but it also makes use of the data that machine 2 makes available (Sockets).
On the server level there is a MySQL servers to which all data is saved and a webserver. The webserver runs a webpage
called “Cinfdata” (source code), which is used for data presentation and light data treatment.
On the user level, users will commonly access the data via the Cinfdata website in a browser on the desktop or on a
smart phone. To get the data locally to do more extensive data treament, it is possible to fetch the data directly from
MySQL server or to use an export function on the website.
In the following, each of these software components will be described in a little more detail.
3
Fig. 1.1: Figure illustrating how the different software components (boxes with blue edge) of PyExpLabSys (and
cinfdata) fits together.
1.1.1 Drivers
At this point PyExpLabSys contains a reasonable amount of drivers (46 files, 81 classes May-16) for general purpose
equipment (data cards, temperature readout etc.) and for equipment related specifically to the vacuum lab we work in
(pressure gauge controllers, mass spectrometers etc).
The source code for the drivers are in the drivers folder, in which the file names are either manufacturer and model or
just the manufacturer.
The documentation for the drivers are divided into two sections Hardware Drivers and Hardware Drivers Autogen-
erated Docs Only. The latter is the group for which there is only API documentation auto generated from the source
code and the former are the drivers that has more specific documentation with example usage etc.
1.1.2 File parsers
PyExpLabSys also contains a small number of parsers for custom file formats. The source code for these are in the
file_parsers folder and the documentation is in the File parsers section.
1.1.3 Database Savers
The database savers are some of the more frequently used classes in PyExpLabSys. Quite simply, they abstract away;
the database layout, the SQL and the queuing of data ofloading (to prevent loosing data in the event of data loss). The
source code for the database savers are in database_saver module in the common sub-package. The documentation is
located at The database_saver module.
4 Chapter 1. Overview
1.1.4 Sockets
The sockets are another set of very important and highly used classes in PyExpLabSys. Most of the sockets are socket
servers, which mean that they accept UDP requests and serves (or accepts) data. These are essentially used as network
variables, by either exposing a measurement on the network or accepting input. A final type of socket is the LiveSocket
which is used to live stream data to a live streaming proxy server. Furthermore, all sockets also expose system (health)
information to the network. The code for the sockets are found in the sockets module in the common sub-package.
The documentation is located at The sockets module.
1.1.5 Apps
The apps section contains stand alone programs which can be used directly and not only as service functions of larger
programs. Typically the apps sports text based guis and several apps also have ambitions for graphical guis. Notable
examples of apps are: socket supervisor This very simple app continously probes a port (typically a socket) and reports
back if the socket is running correctly.
Mass Spectrometer Controls a number of Pfeiffer mass spectrometers. The app includes support for an infinite amount
of meta-channels wich is pulled in via sockets.
Picture Logbook A graphical logbook system based on a barcode reader and a camera. The user of the equipment logs
in before use and out after use. A picture of the equipment is acquired at login and logout. Also contains support for
an external screen wich shows the currently logged in user.
Turbo pump controler Logs and controls Pfeiffer turbo pumps. A number of important parameters are shown in a
terminal and the values are also availble as live sockets.
1.1.6 Misc.
Besides from the items listed above PyExpLabSys contains a number of little helpers. The PyExpLabSys.
common.utilities (code, doc) module contains a convenience function to get a logger, that is configured that
way that we prefer, including email notification of anything warning level or above.
1.2 Python 3 support
We love Python 3. Unfortunately we are not hired to make software, but to keep a lab running. This means that
modules are only ported to Python 3, when it is either convinient or we are touching the code anyway.
1.3 Module Overview
PyExpLabSys.combos (Python 2 only1 )

• This module contains socket, database saver and logger heuristic combinations
PyExpLabSys.settings (Python 2 only1 )

• This module contains the modules used for settings for PyExpLabSys
PyExpLabSys.common.flow_control_bronkhorst (Python 2 and 3)

1 For these modules the Python 2/3 status is not indicated directly in the source code file and so the status is inferred.
1.2. Python 3 support 5

• Common code for Bronkhorst boxes
PyExpLabSys.common.valve_control (Python 2 and 3)

• This module implements the necessary interface to control a valve box using standard gpio commands
PyExpLabSys.common.plotters (Python 2 only1 )

• This module contains plotters for experimental data gathering applications. It contains a plotter for data sets.
PyExpLabSys.common.utilities (Python 2 only1 )

• This module contains a convenience function for easily setting up a logger with the logging module.
PyExpLabSys.common.analog_flow_control (Python 2 only1 )

• Control app for analog pressure controller on sniffer setup
PyExpLabSys.common.socket_clients (Python 2 only1 )

• This file implements Python clients for the DateDataPullSocket
PyExpLabSys.common.system_status (Python 2 only1 )

• This module contains the SystemStatus class
PyExpLabSys.common.database_saver (Python 2 and 3)

• Classes for saving coninuous data and data sets to a database
PyExpLabSys.common.plotters_backend_qwt (Python 2 only1 )

• This module contains plotting backends that use the PyQwt library
PyExpLabSys.common.chiller_reader (Python 2 and 3)

• Module for monitoring a polyscience chiller
PyExpLabSys.common.sockets (Python 2 and 3)

• The sockets module contains various implementations of UDP socket servers (at present 4 in total) for transmis-
sion of data over the network. The different implementations are tailored for a specific purposes, as described
below.
PyExpLabSys.common.loggers (Python 2 only1 )
• This module contains convinience classes for database logging. The classes implement queues to contain the
data before of loading to the database to ensure against network or server problems.
PyExpLabSys.common.microreactor_temperature_control (Python 2 and 3)

• Common code for microreactor heaters
PyExpLabSys.common.value_logger (Python 2 and 3)

• Read a continuously updated values and decides whether it is time to log a new point
PyExpLabSys.common.supported_versions (Python 2 and 3)

• Functions used to indicate and check for supported Python versions
PyExpLabSys.common.decorators (Python 2 only1 )

• This module contains general purpose decorators
PyExpLabSys.common.massspec.test (Python 2 only1 )

• Module to test the mass spec common components
PyExpLabSys.common.massspec.channel (Python 2 only1 )

• This module contains the implementation of a general purpose mass spectrometer channel
PyExpLabSys.common.massspec.qt (Python 2 only1 )

• Module that contains QT widgets for mass spectrometer channels and channel lists
PyExpLabSys.drivers.wpi_al1000 (Python 2 only1 )

• This module implements a driver for the AL1000 syringe pump from World Precision Instruments
PyExpLabSys.drivers.edwards_agc (Python 2 only1 )

• Driver and simple test case for Edwards Active Gauge Controler
PyExpLabSys.drivers.NGC2D (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.drivers.mks_937b (Python 2 and 3)

• Driver for MKS 937b gauge controller
1.3. Module Overview 7

PyExpLabSys.drivers.innova (Python 2 only1 )

• Driver for the Innova RT 6K UPS
PyExpLabSys.drivers.freescale_mma7660fc (Python 2 and 3)

• Driver for AIS328DQTR 3 axis accelerometer
PyExpLabSys.drivers.rosemount_nga2000 (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.drivers.specs_iqe11 (Python 2 only1 )

• Self contained module to run a SPECS sputter gun including fall-back text gui
PyExpLabSys.drivers.intellemetrics_il800 (Python 2 only1 )

• Driver for IL800 deposition controller
PyExpLabSys.drivers.fug (Python 2 only)

• Driver for “fug NTN 140 - 6,5 17965-01-01” power supply Communication via the Probus V serial interface.
PyExpLabSys.drivers.four_d_systems (Python 2 only1 )

• Drivers for the 4d systems displays
PyExpLabSys.drivers.vogtlin (Python 2 and 3)

• Minimal MODBUS driver for the red-y smart - meter GSM, - controller GSC, - pressure controller GSP and -
back pressure controller GSB.
PyExpLabSys.drivers.stmicroelectronics_ais328dq (Python 2 and 3)

• Driver for STMicroelectronics AIS328DQTR 3 axis accelerometer
PyExpLabSys.drivers.bio_logic (Python 2 only1 )

• This module is a Python implementation of a driver around the EC-lib DLL. It can be used to control at least the
SP-150 potentiostat from Bio-Logic under 32 bit Windows.
PyExpLabSys.drivers.stahl_hv_400 (Python 2 and 3)

• Driver for Stahl HV 400 Ion Optics Supply
PyExpLabSys.drivers.polyscience_4100 (Python 2 and 3)

• Driver and test case for Polyscience 4100
PyExpLabSys.drivers.pfeiffer_turbo_pump (Python 2 and 3)

• Self contained module to run a Pfeiffer turbo pump including fall-back text gui and data logging.
PyExpLabSys.drivers.srs_sr630 (Python 2 and 3)

• Driver for Standford Research Systems, Model SR630
PyExpLabSys.drivers.vivo_technologies (Python 2 only1 )

• Driver for a Vivo Technologies LS-689A barcode scanner
PyExpLabSys.drivers.inficon_sqm160 (Python 2 only1 )

• Driver for Inficon SQM160 QCM controller
PyExpLabSys.drivers.edwards_nxds (Python 2 and 3)

• Driver for Edwards, nXDS pumps
PyExpLabSys.drivers.omega_cn7800 (Python 2 only1 )

• Omega CN7800 Modbus driver. Might also work with other CN units
PyExpLabSys.drivers.tenma (Python 2 and 3)

• from __future__ import unicode_literals, print_function
PyExpLabSys.drivers.omron_d6fph (Python 2 and 3)

• Hint for implementation found at http://forum.arduino.cc/index.php?topic=285116.0
PyExpLabSys.drivers.pfeiffer_qmg422 (Python 2 and 3)

• This module contains the driver code for the QMG422 control box for a pfeiffer mass-spectrometer. The code
should in principle work for multiple type of electronics. It has so far been tested with a qme-125 box and a
qme-??? box. The module is ment as a driver and has very little function in itself. The module is ment to be
used as a sub-module for a large program providing the functionality to actually use the mass-spectrometer.
PyExpLabSys.drivers.xgs600 (Python 2 and 3)

• Driver class for XGS600 gauge controll
PyExpLabSys.drivers.stmicroelectronics_l3g4200d (Python 2 and 3)

• Driver for STMicroelectronics L3G4200D 3 axis gyroscope
PyExpLabSys.drivers.pfeiffer_qmg420 (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.drivers.dataq_binary (Python 2 and 3)

• DataQ Binary protocol driver
PyExpLabSys.drivers.omega_cni (Python 2 and 3)

• This module contains drivers for equipment from Omega. Specifically it contains a driver for the ??? thermo
couple read out unit.
PyExpLabSys.drivers.keithley_2700 (Python 2 and 3)

• Simple driver for Keithley Model 2700
PyExpLabSys.drivers.agilent_34410A (Python 2 and 3)

• Driver class for Agilent 34410A DMM
PyExpLabSys.drivers.brooks_s_protocol (Python 2 and 3)

• Driver for Brooks s-protocol
PyExpLabSys.drivers.agilent_34972A (Python 2 and 3)

• Driver class for Agilent 34972A multiplexer
PyExpLabSys.drivers.mks_pi_pc (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.drivers.isotech_ips (Python 2 only1 )

• Driver for ISO-TECH IPS power supply series
PyExpLabSys.drivers.galaxy_3500 (Python 2 and 3)

• Python interface for Galaxy 3500 UPS. The driver uses the telnet interface of the device.
PyExpLabSys.drivers.omegabus (Python 2 and 3)

• Driver for OmegaBus devices
PyExpLabSys.drivers.kjlc_pressure_gauge (Python 2 and 3)

• Module contains driver for KJLC 3000 pressure gauge
PyExpLabSys.drivers.pfeiffer (Python 2 only1 )

• This module contains drivers for the following equipment from Pfeiffer Vacuum:
PyExpLabSys.drivers.epimax (Python 2 and 3)

• Driver for the Epimax PVCi process vacuum controller
PyExpLabSys.drivers.dataq_comm (Python 2 and 3)

• Driver for DATAQ dac units
PyExpLabSys.drivers.honeywell_6000 (Python 2 and 3)

• Driver for HIH6000 class temperature and humidity sensors
PyExpLabSys.drivers.specs_XRC1000 (Python 2 only1 )

• Self contained module to run a SPECS sputter gun including fall-back text gui
PyExpLabSys.drivers.lascar (Python 2 only1 )

• Driver for the EL-USB-RT temperature and humidity USB device from Lascar
PyExpLabSys.drivers.bronkhorst (Python 2 and 3)

• Driver for Bronkhorst flow controllers, including simple test case
PyExpLabSys.drivers.omega_D6400 (Python 2 and 3)

• Driver for Omega D6400 daq card
PyExpLabSys.drivers.crowcon (Python 2 and 3)

• This module contains a driver for the Vortex gas alarm central

PyExpLabSys.drivers.mks_925_pirani (Python 2 and 3)

• Driver for MKS 925 micro pirani
PyExpLabSys.drivers.scpi (Python 2 and 3)

• Implementation of SCPI standard
PyExpLabSys.drivers.mks_g_series (Python 2 and 3)

• Driver for MKS g-series flow controller
PyExpLabSys.drivers.cpx400dp (Python 2 and 3)

• Driver for CPX400DP power supply
PyExpLabSys.drivers.keithley_smu (Python 2 and 3)

• Simple driver for Keithley SMU
PyExpLabSys.file_parsers.chemstation (Python 2 and 3)

• File parser for Chemstation files
PyExpLabSys.file_parsers.omicron (Python 2 only1 )

• File parser for the Omicron “Flattener” format
PyExpLabSys.file_parsers.avantage (Python 2 only1 )

• Test module for Avantage files
PyExpLabSys.file_parsers.specs (Python 2 and 3)

• This file is used to parse XPS and ISS data from XML files from the SPECS program.
PyExpLabSys.file_parsers.avantage_xlsx_export (Python 2 only1 )

• File parser for the Avantage xlsx export format
PyExpLabSys.apps.socket_tester (Python 2 only1 )

• A socket tester program for linux
PyExpLabSys.apps.ion_optics_controller (Python 2 only1 )

• Ion Optics Control software
PyExpLabSys.apps.wind_speed_logger (Python 2 and 3)

• Logger of cooling water temperature
PyExpLabSys.apps.turbo_logger (Python 2 and 3)

• App to log output from Pfeiffer Turbo Pumps
PyExpLabSys.apps.edwards_nxds_logger (Python 2 and 3)

• Logger for nXDSni roughing pump
PyExpLabSys.apps.socket_logger (Python 2 and 3)

• App for logging specific sockets into dateplots
PyExpLabSys.apps.emission_control (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.apps.mass_finder (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.apps.picture_logbook (Python 2 only1 )

• Module to run a graphical logbook of a specific area
PyExpLabSys.apps.socket_supervisor (Python 2 and 3)

• Module to check that local machine is living up to its duties
PyExpLabSys.apps.bakeout (Python 2 and 3)

• App to control PW-modulated bakeout boxes
PyExpLabSys.apps.rampreader (Python 2 only1 )

• NO DESCRIPTION

PyExpLabSys.apps.bakeoutweb.bakeoutweb (Python 2 only1 )

• Web app for the magnificient bakeout app
PyExpLabSys.apps.stepped_program_runner.stepped_program_runner (Python 2 only1 )

• A general stepped program runner
PyExpLabSys.apps.tof.fix_mass_axis (Python 2 and 3)

• Program to fix x-axis on TOF-spectra
PyExpLabSys.apps.tof.spectrum_plotter (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.apps.tof.helper_scripts.lm_test (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.apps.qms.qmg_status_output (Python 2 and 3)

• Text UI for mass spec program
PyExpLabSys.apps.qms.qmg_meta_channels (Python 2 and 3)

• Module to perform read-out of meta channels for qms
PyExpLabSys.apps.qms.mass_spec (Python 2 and 3)

• Mass spec program
PyExpLabSys.apps.qms.qms (Python 2 and 3)

• Mass Spec Main program
PyExpLabSys.auxiliary.tc_calculator (Python 2 only1 )

• NO DESCRIPTION
PyExpLabSys.auxiliary.pid (Python 2 and 3)

• PID calculator
PyExpLabSys.auxiliary.rtd_calculator (Python 2 and 3)
• NO DESCRIPTION
PyExpLabSys.thirdparty.cached_property (Python 2 only1 )

• Copy of the cached property project from https://github.com/pydanny/cached-property
PyExpLabSys.thirdparty.olefile (Python 2 only1 )

• Launched from the command line, this script parses OLE files and prints info.

CHAPTER 2
User Notes
This page has various different notes for using PyExpLabSys.
2.1 Setting up logging of your program
To set up logging of a program, it is possible to simply follow the standard library documentation. However, since
many of the programs that uses PyExpLabSys are programs that runs for extended periods without monitoring, a more
specific logging setup may be required. E.g. one that makes use of email handlers, so be notified by email in case of
errors or warnings.
For that purpose, PyExpLabSys has the get_logger() function in the utilities module that is a convinience
function to set up a logger with one or more of the commonly used log handlers i.e. a terminal handler, a rotating file
handler and email handlers. This may be used to things up and running in a hurry.
from PyExpLabSys.common import utilities
utilities.MAIL_HOST = 'my.mail.host'
utilities.WARNING_EMAIL = 'email-address-to-use-in-case-of-warnings@log.com'
utilities.ERROR_EMAIL = 'email-address-to-use-in-case-of-error@log.com'
# Returns a logger with terminal and emails handlers per default

LOG = utilities.get_logger('my_program_name')
# A rotating file handler can be added:

LOG = utilities.get_logger('my_program_name', file_log=True)
2.2 Activating PyExpLabSys library logging in you program
PyExpLabSys contains quite a few loggers and exposes a few convinience functions in the utilities mod-
ule for listing and activating them. To get a list of loggers that are relevant for the modules that you have im-
17
ported, you can use either the get_library_logger_names() function, which will return you a list or the
print_library_logger_names() function, which prints them out:
from PyExpLabSys.common import sockets
from PyExpLabSys.common.utilities import print_library_logger_names
print_library_logger_names()
produces the following output:

Current PyExpLabSys loggers
===========================
* PyExpLabSys.common.sockets.PullUDPHandler
* PyExpLabSys.common.sockets.DataPushSocket
* PyExpLabSys.common.sockets.PushUDPHandler
* PyExpLabSys.settings
* PyExpLabSys.common.sockets.DateDataPullSocket
* PyExpLabSys.common.sockets.CallBackThread
* PyExpLabSys.common
* PyExpLabSys.common.sockets.CommonDataPullSocket
* PyExpLabSys.common.sockets
* PyExpLabSys.common.sockets.DataPullSocket
* PyExpLabSys
* PyExpLabSys.common.sockets.LiveSocket
To activate a logger use the full path of the logger e.g. PyExpLabSys.common.sockets.DataPullSocket
and remembers that the loggers are configured as a tree, so activating PyExpLabSys.common.sockets will
activate all the loggers in that module and activating PyExpLabSys will activate all PyExpLabSys library loggers.
There are now two ways to activate a logger. One is to configure one from scratch, using the path of the logger and the
same options as in get_logger():
from PyExpLabSys.common.utilities import activate_library_logging
activate_library_logging(
'PyExpLabSys.common.sockets.DateDataPullSocket',
level='debug',
file_log=True,
file_name='socket_log.txt',
)
This would output all log message at debug level to a file called socket_log.txt.
The other way to activate a library logger is to ask it to enherit all the handlers and levels from an existing logger. This
will send all the library log messages to the same destination:
from PyExpLabSys.common.utilities import get_logger, activate_library_logging
LOG = get_logger('my_program_name')
LOG.info('My program started')
# Configure a library logger to use the same handlers
activate_library_logging(
'PyExpLabSys.common.sockets.DateDataPullSocket',
logger_to_inherit_from=LOG,
)
18 Chapter 2. User Notes

It is still possible, when inheriting from an existing logger, to set a custom level for the library logger, using the level
argument as in the example above.
2.3 Using PyExpLabSys drivers outside of PyExpLabSys
All I wanted was a banana, but what I got was a gorilla holding a banana
The quote above, is often used to refer to the fact that it can be difficult to use a component from a “framework”
separate from the framework.
PyExpLabSys is not a framework as such, but there are some common elements that are used across different in
principle independent modules. Specifically, most of the drivers in PyExpLabSys will work just fine outside of Py-
ExpLabSys, with a few very minor modifications, by just copying the file to where the driver is to be used. Most of
the drivers make use of just one other PyExpLabSys module that tie it to the package, the supported_versions
module. The only thing that this module does, is to mark the specific driver as working with Python 2, Python 3 or
both, and make a check at run-time of the Python version and possibly output a warning. It can therefore trivially be
removed. To do this, look to lines of code somewhat like this:
from PyExpLabSys.common.supported_versions import python2_and_3

python2_and_3(__file__)
and comment them out. The specific function that is imported and called, will vary depending on which versions is
supported, but that should be fairly simple to figure out.
2.3. Using PyExpLabSys drivers outside of PyExpLabSys 19

20 Chapter 2. User Notes

CHAPTER 3
Common Software Components
This section documents the common software components at CINF. These are general purpose modules and classes
that does not fit into the any of the other categories like drivers and parsers.
3.1 The database_saver module
3.1.1 Autogenerated API documentation for database_saver
Classes for saving coninuous data and data sets to a database

PyExpLabSys.common.database_saver.HOSTNAME = u'servcinf-sql'
Hostname of the database server
PyExpLabSys.common.database_saver.DATABASE = u'cinfdata'
Database name
class PyExpLabSys.common.database_saver.CustomColumn(value, format_string)
Bases: tuple
format_string
Alias for field number 1
value
class PyExpLabSys.common.database_saver.DataSetSaver(measurements_table,
xy_values_table, user-
name, password, measure-
ment_specs=None)
Bases: object
A class to save a measurement
measurement_ids
dict – Mapping of codenames to measurements ids
21
measurements_table
str – The measurements tables
xy_values_table
str – The x, y values tables
sql_saver
SqlSaver – The SqlSaver used to save points
insert_measurement_query
str – The query used to insert a measurement
insert_point_query
str – The query used to insert a point
insert_batch_query
str – The query used to insert a batch of points
connection
MySQLdb connection – The database connection used to register new measurements
cursor
MySQLdb cursor – The database cursor used to register new measurements
__init__(measurements_table, xy_values_table, username, password, measurement_specs=None)
Initialize local parameters
Parameters
• measurements_table (str) – The name of the measurements table
• xy_values_table (str) – The name of the xy values table
• username (str) – The database username
• passwork (str) – The database password
• measurement_specs (sequence) – A sequence of measurement_codename,
metadata pairs, see below
measurement_specs is used if you want to initialize all the measurements at __init__ time.
You can also do it later with add_measurement(). The expected value is a sequence of
measurement_codename, metadata e.g:
measurement_specs = [
['M2', {'type': 5, 'timestep': 0.1, 'mass_label': 'M2M'}],
]
As above, the expected metadata is simply a mapping of column names to column values in the
measurements_table.
Per default, the value will be put into the table as is. If it is necessary to do SQL processing on the value,
to make it fit the column type, then the value must be replaced with a CustomColumn instance, whose
arguments are the value and the format/processing string. The format/processing string must contain a
‘%s’ as a placeholder for the value. It could look like this:
measurement_specs = [
['M2', {'type': 5, 'time': CustomColumn(M2_timestamp, 'FROM_UNIXTIME(%s)
˓→')}],
22 Chapter 3. Common Software Components

['M28', {'type': 5, 'time': CustomColumn(M28_timestamp, 'FROM_UNIXTIME(%s)

˓→ ')}],
]
The most common use for this is the one shown above, where the time column is of type timestamp and
the time value (e.g. in M2_timestamp) is a unix timestamp. The unix timestamp is converted to a SQL
timestamp with the FROM_UNIXTIME SQL function.
Note: The SQL timestamp column understand the datetime.datetime type directly, so if the input
timestamp is already on that form, then there is no need to convert it
add_measurement(codename, metadata)
Add a measurement
This is equivalent to forming the entry in the measurements table with the metadata values and saving the
id of this entry locally for use with add_point().
Parameters
• codename (str) – The codename that this measurement should have
• metadata (dict) – The dictionary that holds the information for the measurements
table. See __init__() for details.
save_point(codename, point)
Save a point for a specific codename
Parameters
• codename (str) – The codename for the measurement to add the point to
• point (sequence) – A sequence of x, y
save_points_batch(codename, x_values, y_values, batchsize=1000)
Save a number points for the same codename in batches
Parameters
• codename (str) – The codename for the measurement to save the points for
• x_values (sequence) – A sequence of x values
• y_values (sequence) – A sequence of y values
• batchsize (int) – The number of points to send in the same batch. Defaults to 1000,
see the warning below before changing it
Warning: The batchsize is ultimately limited by the max package size that the MySQL server will
receive. The default is 1MB. Each point amounts to around 60 bytes in the final query. Rounding this
up to 100, means that the limit is ~10000 points. This means that the default of 1000 should be safe
and that if it is changed by the user, expect problems if exceeding the lower 10000ths.
get_unique_values_from_measurements(column)
Return a set of unique column values from the measurements database
This is commonly used in fileparsers to identify the files already uploaded
3.1. The database_saver module 23

Parameters column (str) – The column specification to extract values from. This can be
just a column name e.g. “time”, but it is also allowed to contain SQL processing e.g.
UNIX_TIMESTAMP(time). The value of column will be formatted directly into the query.
start()
Start the DataSetSaver
And the underlying SqlSaver.
stop()
Stop the MeasurementSaver
And shut down the underlying SqlSaver instance nicely.
wait_for_queue_to_empty()
Wait for the query queue in the SqlSaver to empty
This purpose of this method is to avoid usgin too much memory when uploading large amount of data.
class PyExpLabSys.common.database_saver.ContinuousDataSaver(continuous_data_table,
username, pass-
word, measure-
ment_codenames=None)
Bases: object
This class saves data to the database for continuous measurements
Continuous measurements are measurements of a single parameters as a function of datetime. The class can
ONLY be used with the new layout of tables for continous data, where there is only one table per setup, as
apposed to the old layout where there was one table per measurement type per setup. The class sends data to the
hostname and database named in HOSTNAME and DATABASE respectively.
__init__(continuous_data_table, username, password, measurement_codenames=None)
Initialize the continous logger
Parameters
• continuous_data_table (str) – The contunuous data table to log data to
• username (str) – The MySQL username
• password (str) – The password for username in the database
• measurement_codenames (sequence) – A sequence of measurement code-
names that this logger will send data to. These codenames can be given
here, to initialize them at the time of initialization or later by the use of the
add_continuous_measurement() method.
Note: The codenames are the ‘official’ codenames defined in the database for contionuous measurements
NOT codenames that can be userdefined
add_continuous_measurement(codename)
Add a continuous measurement codename to this saver
Parameters codename (str) – Codename for the measurement to add
Note: The codenames are the ‘official’ codenames defined in the database for contionuous measurements
NOT codenames that can be userdefined

save_point_now(codename, value)
Save a value and use now (a call to time.time()) as the timestamp
Parameters
• codename (str) – The measurement codename that this point will be saved under
• value (float) – The value to be logged
Returns The Unixtime used
Return type float
save_point(codename, point)
Save a point
Parameters
• point (sequence) – The point to be saved, as a sequence of 2 floats: (x, y)
start()
Starts the underlying SqlSaver
stop()
Stop the ContiniousDataSaver
And shut down the underlying SqlSaver instance nicely.
class PyExpLabSys.common.database_saver.SqlSaver(username, password, queue=None)
Bases: threading.Thread
The SqlSaver class administers a queue from which it executes SQL queries
Note: In general queries are added to the queue via the enqueue_query() method. If it is desired to add
elements manually, remember that they must be on the form of a (query, query_args) tuple. (These are
the arguments to the execute method on the cursor object)
queue
Queue.Queue – The queue the queries and qeury arguments are stored in. See note below.
commits
int – The number of commits the saver has performed
commit_time
float – The timespan the last commit took
connection
MySQLdb connection – The MySQLdb database connection
cursor
MySQLdb cursor – The MySQLdb database cursor
__init__(username, password, queue=None)
Initialize local variables
Parameters
• username (str) – The username for the MySQL database
• password (str) – The password for the MySQL database
3.1. The database_saver module 25

• queue (Queue.Queue) – A custom queue to use. If it is left out, a new Queue.Queue

object will be used.
stop()
Add stop word to queue to exit the loop when the queue is empty
enqueue_query(query, query_args=None)
Enqueue a qeury and arguments
Parameters
• query (str) – The SQL query to be executed
• query_args (sequence or mapping) – Optional sequence or mapping of argu-
ments to be formatted into the query. query and query_args in combination are the
arguments to cursor.execute.
run()
Execute SQL inserts from the queue until stopped
wait_for_queue_to_empty()
Wait for the queue to empty
This purpose of this method is to avoid using too much memory when uploading large amount of data.
PyExpLabSys.common.database_saver.run_module()
Run the module to perform elementary functional test
3.2 The loggers module
The logger module contains classes that hide some of all the repeated code associated with sending data to the data
base. The main component is the ContinousLogger class, which is used to send continuously logged data to the
data base.
3.2.1 The continuous logger
The ContinuousLogger class is meant to do as much of the manual work related to logging a parameter continu-
ously to the database as possible. The main features are:
• Simple single method usage. After the class is instantiated, a single call to enqueue_point() or
enqueue_point_now() is all that is needed to log a point. No manual database query manipulation is
required.
• Resistent to network or database down time. The class implements a queue for the data, from which points
will only be removed if they are successfully handed of to the data base and while it is not possible to hand the
data of, it will be stored in memory.
Warning: The resilience against network downtime has only been tested for the way it will fail if you disable
the network from the machine it is running on. Different kinds of failures may produce different kinds of failure
modes. If you encounter a failure mode that the class did not recover from you should report it as a bug.
Todo: Write that it uses new style database layout and refer to that section.

Usage Example
If code already exists to retrieve the data (e.g. a driver to interface a piece of equipment with), writing a data logger
can be reduced to as little as the following:
from PyExpLabSys.common.loggers import ContinuousLogger
db_logger = ContinuousLogger(table='dateplots_dummy',
username='dummy', password='dummy',
measurement_codenames = ['dummy_sine_one'])
db_logger.start()
# Initialize variable for the logging condition

while True:
new_value = driver.get_value()
if contition_to_log_is_true:
db_logger.enqueue_point_now('dummy_sine_one', new_value)
or if it is preferred to keep track of the timestamp manually:
import time
from PyExpLabSys.common.loggers import ContinuousLogger
# Initiate the logger to write to the dateplots_dummy table, with usernam

db_logger = ContinuousLogger(table='dateplots_dummy',
username='dummy', password='dummy',
measurement_codenames = ['dummy_sine_one'])
db_logger.start()
# Initialize variable for the logging condition

while True:
new_value = driver.get_value()
now = time.time()
if contition_to_log_is_true:
db_logger.enqueue_point('dummy_sine_one', (now, new_value))
Auto-generated module documentation
This module contains convinience classes for database logging. The classes implement queues to contain the data
before of loading to the database to ensure against network or server problems.
class PyExpLabSys.common.loggers.NoneResponse
__init__()
PyExpLabSys.common.loggers.NONE_RESPONSE = <PyExpLabSys.common.loggers.NoneResponse instanc
Module variable used to indicate a none response, currently is an instance if NoneResponse
class PyExpLabSys.common.loggers.InterruptableThread(cursor, query)
Class to run a MySQL query with a time out
__init__(cursor, query)
run()
Start the thread
3.2. The loggers module 27

PyExpLabSys.common.loggers.timeout_query(cursor, query, timeout_duration=3)

Run a mysql query with a timeout
Parameters
• cursor (MySQL cursor) – The database cursor
• query (str) – The query to execute
• timeout_duration (int) – The timeout duration
Returns
(tuple or NONE_RESPONSE): A tuple of results from the query or NONE_RESPONSE if the query
timed out
exception PyExpLabSys.common.loggers.StartupException(*args, **kwargs)

Bases: exceptions.Exception
Exception raised when the continous logger fails to start up
__init__(*args, **kwargs)
class PyExpLabSys.common.loggers.ContinuousLogger(table, username, password,
measurement_codenames,
dequeue_timeout=1, recon-
nect_waittime=60, dsn=None)
A logger for continous data as a function of datetime. The class can ONLY be used with the new layout of tables
for continous data, where there is only one table per setup, as apposed to the old layout where there was one table
per measurement type per setup. The class sends data to the cinfdata database at host servcinf-sql.
Variables
• host – Database host, value is servcinf-sql.
• database – Database name, value is cinfdata.
__init__(table, username, password, measurement_codenames, dequeue_timeout=1, recon-
nect_waittime=60, dsn=None)
Initialize the continous logger
Parameters
• table (str) – The table to log data to
• username (str) – The MySQL username (must have write rights to table)
• password (str) – The password for user in the database
• measurement_codenames (list) – List of measurement codenames that this logger
will send data to
• dequeue_timeout (float) – The timeout (in seconds) for dequeueing an element,
which also constitutes the max time to shutdown after the thread has been asked to stop.
Default is 1.
• reconnect_waittime (float) – Time to wait (in seconds) in between attempts to
re-connect to the MySQL database, if the connection has been lost
• dsn (str) – DSN name of ODBC connection, used on Windows only
Raises StartupException – If it is not possible to start the database connection or translate
the code names

stop()
Stop the thread
run()
Start the thread. Must be run before points are added.
enqueue_point_now(codename, value)
Add a point to the queue and use the current time as the time
Parameters
• value (float) – The value to be logged
Returns The Unixtime used
Return type float
enqueue_point(codename, point)
Add a point to the queue
Parameters
• point (iterable) – Current point as a list (or tuple) of 2 floats: [x, y]
3.3 The plotters module plotter backends
The plotters module contains classes for easy plotting of data.
3.3.1 The data logger
The DataLogger is a general purpose plotter that is suitable for plotting data sets as they are being gathered. The
data logger uses the qwt backend, though the class QwtPlot, that forms the plot by means of the PyQwt library.
Usage Example
import sys
import time
import random
import numpy as np
from PyQt4 import Qt, QtGui, QtCore
from PyExpLabSys.common.plotters import DataPlotter
class TestApp(QtGui.QWidget):
"""Test Qt application"""
def __init__(self):
super(TestApp, self).__init__()
# Form plotnames
self.plots_l = ['signal1', 'signal2']
self.plots_r = ['aux_signal1']
self.plotter = DataPlotter(
self.plots_l, right_plotlist=self.plots_r, parent=self,
3.3. The plotters module plotter backends 29

left_log=True, title='Awesome plots',

yaxis_left_label='Log sine, cos', yaxis_right_label='Noisy line',
xaxis_label='Time since start [s]',
legend='right', left_thickness=[2, 8], right_thickness=6,
left_colors=['firebrick', 'darkolivegreen'],
right_colors=['darksalmon'])
hbox = QtGui.QHBoxLayout()
hbox.addWidget(self.plotter.plot)
self.setLayout(hbox)
self.setGeometry(5, 5, 500, 500)
self.start = time.time()
QtCore.QTimer.singleShot(10, self.main)
def main(self):
"""Simulate gathering one set of points and adding them to plot"""
elapsed = time.time() - self.start
value = (np.sin(elapsed) + 1.1) * 1E-9
self.plotter.add_point('signal1', (elapsed, value))
value = (np.cos(elapsed) + 1.1) * 1E-8
self.plotter.add_point('signal2', (elapsed, value))
value = elapsed + random.random()
self.plotter.add_point('aux_signal1', (elapsed, value))
QtCore.QTimer.singleShot(100, self.main)
def main():
"""Main method"""
app = Qt.QApplication(sys.argv)
testapp = TestApp()
testapp.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
plotters module
This module contains plotters for experimental data gathering applications. It contains a plotter for data sets.
class PyExpLabSys.common.plotters.DataPlotter(left_plotlist, right_plotlist=None,
left_log=False, right_log=False,
auto_update=True, backend=’qwt’,
parent=None, **kwargs)
Bases: object
This class provides a data plotter for continuous data
__init__(left_plotlist, right_plotlist=None, left_log=False, right_log=False, auto_update=True,
backend=’qwt’, parent=None, **kwargs)
Initialize the plotting backend, data and local setting
Parameters
• left_plotlist (iterable with strs) – Codenames for the plots that should go
on the left y-axis
• right_plotlist – Codenames for the plots that should go in the right y-axis

• left_log (bool) – Left y-axis should be log

• right_log (bool) – Right y-axis should be log
• auto_update (bool) – Whether all data actions should trigger an update
• backend (str) – The plotting backend to use. Current only option is ‘qwt’
• parent (GUI object) – If a GUI backend is used that needs to know the parent GUI
object, then that should be supplied here
Kwargs:
Parameters
• title (str) – The title of the plot
• xaxis_label (str) – Label for the x axis
• yaxis_left_label (str) – Label for the left y axis
• yaxis_right_label (str) – Label for the right y axis
• left_labels (iterable with strs) – Labels for the plots on the left y-axis. If
none are given the codenames will be used.
• right_labels (iterable with strs) – Labels for the plots on the right y-axis.
If none are given the codenames will be used.
• legend (str) – Position of the legend. Possible values are: ‘left’, ‘right’, ‘bottom’,
‘top’. If no argument is given, the legend will not be shown.
• left_colors (iterable of strs) – Colors for the left curves (see back-
ground_color for details)
• right_colors (iterable of strs) – Colors for the right curves (see back-
• left_thickness (int or iterable of ints) – Line thickness. Either an in-
teger to apply for all left lines or a iterable of integers, one for each line.
• right_thickness (int or iterable of ints) – Line thickness. Either an
integer to apply for all right lines or a iterable of integers, one for each line.
• background_color (str) – The name in a str (as understood by QtGui.QColor(), see
Colors section for possible values) or a string with a hex value e.g. ‘#101010’ that should
be used as the background color.
add_point(plot, point, update=None)
Add a point to a plot
Parameters
• plot (str) – The codename for the plot
• point (Iterable with x and y value as two numpy.float) – The
point to add
• update – Whether a update should be performed after adding the point. If set, this value
will over write the auto_update value
Returns plot content or None
update()
Update the plot and possible return the content

data
Get and set the data
plot
Get the plot
class PyExpLabSys.common.plotters.ContinuousPlotter(left_plotlist, right_plotlist=None,
left_log=False, right_log=False,
timespan=600, preload=60,
auto_update=True, back-
end=’none’, **kwargs)
Bases: object
This class provides a data plotter for continuous data
__init__(left_plotlist, right_plotlist=None, left_log=False, right_log=False, timespan=600,
preload=60, auto_update=True, backend=’none’, **kwargs)
Initialize the plotting backend, data and local setting
Parameters
on the left y-axis
• timespan (int) – Numbers of seconds to show in the plot
• preload (int) – Number of seconds to jump ahead when reaching edge of plot
• auto_update (bool) – Whether all data actions should trigger a update
• backend (str) – The plotting backend to use. Current only option is ‘none’
Kwargs
TODO
add_point_now(plot, value, update=None)
Add a point to a plot using now as the time
Parameters
• value (numpy.float) – The value to add
add_point(plot, point, update=None)
Add a point to a plot
Parameters
• point (Iterable with unix time and value as two numpy.float) –
The point to add

update()
Update the plot and possible return the content
data
Get and set the data
plot
Get the plot
3.3.2 The qwt backend
plotters_backend_qwt
This module contains plotting backends that use the PyQwt library
class PyExpLabSys.common.plotters_backend_qwt.Colors
Class that gives plot colors
__init__()
get_color()
Return a color
class PyExpLabSys.common.plotters_backend_qwt.QwtPlot(parent, left_plotlist,
right_plotlist=None,
left_log=False,
right_log=False, **kwargs)
Bases: list
Class that represents a Qwt plot
__init__(parent, left_plotlist, right_plotlist=None, left_log=False, right_log=False, **kwargs)
Initialize the plot and local setting
Parameters
• parent (GUI object) – The parent GUI object, then that should be supplied here
on the left y-axis
Kwargs:
Parameters
• title (str) – The title of the plot
• xaxis_label (str) – Label for the x axis
• yaxis_left_label (str) – Label for the left y axis
• yaxis_right_label (str) – Label for the right y axis

• left_labels (iterable with strs) – Labels for the plots on the left y-axis. If
none are given the codenames will be used.
• right_labels (iterable with strs) – Labels for the plots on the right y-axis.
If none are given the codenames will be used.
• legend (str) – Position of the legend. Possible values are: ‘left’, ‘right’, ‘bottom’,
‘top’. If no argument is given, the legend will not be shown.
• left_colors (iterable of strs) – Colors for the left curves (see back-
• right_colors (iterable of strs) – Colors for the right curves (see back-
• left_thickness (int or iterable of ints) – Line thickness. Either an in-
teger to apply for all left lines or a iterable of integers, one for each line.
• right_thickness (int or iterable of ints) – Line thickness. Either an
integer to apply for all right lines or a iterable of integers, one for each line.
• background_color (str) – The name in a str (as understood by QtGui.QColor(), see
Colors section for possible values) or a string with a hex value e.g. ‘#101010’ that should
be used as the background color.
update(data)
Update the plot with new values and possibly move the xaxis
Parameters data (dict) – The data to plot. Should be a dict, where keys are plot code names
and values are data series as an iterable of (x, y) iterables. E.g. {‘plot1’: [(1, 1), (2, 2)]}
Colors
aliceblue antiquewhite aqua aquamarine

azure beige bisque black
blanchedalmond blue blueviolet brown
burlywood cadetblue chartreuse chocolate
coral cornflowerblue cornsilk crimson
cyan darkblue darkcyan darkgoldenrod
darkgray darkgreen darkgrey darkkhaki
darkmagenta darkolivegreen darkorange darkorchid
darkred darksalmon darkseagreen darkslateblue
darkslategray darkslategrey darkturquoise darkviolet
deeppink deepskyblue dimgray dimgrey
dodgerblue firebrick floralwhite forestgreen
fuchsia gainsboro ghostwhite gold
goldenrod gray green greenyellow
grey honeydew hotpink indianred
indigo ivory khaki lavender
lavenderblush lawngreen lemonchiffon lightblue
lightcoral lightcyan lightgoldenrodyellow lightgray
lightgreen lightgrey lightpink lightsalmon
lightseagreen lightskyblue lightslategray lightslategrey
lightsteelblue lightyellow lime limegreen
linen magenta maroon mediumaquamarine
Continued on next page

Table 3.1 – continued from previous page

mediumblue mediumorchid mediumpurple mediumseagreen
mediumslateblue mediumspringgreen mediumturquoise mediumvioletred
midnightblue mintcream mistyrose moccasin
navajowhite navy oldlace olive
olivedrab orange orangered orchid
palegoldenrod palegreen paleturquoise palevioletred
papayawhip peachpuff peru pink
plum powderblue purple red
rosybrown royalblue saddlebrown salmon
sandybrown seagreen seashell sienna
silver skyblue slateblue slategray
slategrey snow springgreen steelblue
tan teal thistle tomato
transparent turquoise violet wheat
white whitesmoke yellow yellowgreen
3.4 The sockets module
The data sockets are convenience classes that make it easier to send data back and forth between machines. All the
data sockets are socket servers, i.e. they handle requests, and to interact with them it is necessary to work as a client.
The main purpose of these sockets is to hide the complexity and present a easy-to-use interface while performing e.g.
error checking in the background.
The sockets are divided into push and pull sockets, which are intended to either pull data from or pushing data to.
The main advantages of the pull sockets are:
• Simple usage: After e.g. the DateDataPullSocket or DataPullSocket class is instantiated, a single
call to the set_point method is all that is needed to make a point available via the socket.
• Codename based: After instantiation, the different data slots are referred to by codenames. This makes code
easier to read and help to prevent e.g. indexing errors.
• Timeout safety to prevent serving obsolete data: The class can be instantiated with a timeout for each mea-
surement type. If the available point is too old an error message will be served.
The main advantages of the push socket are:
• Simple usage: If all that is required is to receive data in a variable like manner, both the last and the updated
variable values can be accessed via the DataPushSocket.last and DataPushSocket.updated prop-
erties.
• Flexible: The DataPushSocket offers a lot of functionality around what actions are performed when a data
set is received, including enqueue it or calling a callback function with the data set as an argument.
Table of Contents
• The sockets module

– Examples
* DateDataPullSocket make data available (network variable)

* DataPushSocket, send data (network variable)
* DataPushSocket, see all data sets received (enqueue them)
3.4. The sockets module 35

* DataPushSocket, make socket call function on reception (callback)

* DataPushSocket, control class and send return values back (callback with return)
– Port defaults
– Inheritance
– Status of a socket server
* Socket server status

* System status
– Auto-generated module documentation
3.4.1 Examples
In the following examples it is assumed, that all other code that is needed, such as e.g. an equipment driver, already
exists, and the places where such code is needed, is filled in with dummy code.
DateDataPullSocket make data available (network variable)
Making data available on the network for pulling can be achieved with:
from PyExpLabSys.common.sockets import DateDataPullSocket
# Create a data socket with timeouts and start the socket server
name = 'Last shot usage data from the giant laser on the moon'
codenames = ['moon_laser_power', 'moon_laser_duration']
moon_socket = DateDataPullSocket(name, codenames, timeouts=[1.0, 0.7])
moon_socket.start()
try:
while True:
power, duration = laser.get_values()
# To set a variable use its codename
moon_socket.set_point_now('moon_laser_power', power)
moon_socket.set_point_now('moon_laser_duration', duration)
except KeyboardInterrupt:
# Stop the socket server
moon_socket.stop()
or if it is preferred to keep track of the timestamp manually:
try:
while True:
now = time.time()
power, duration = driver.get_values()
moon_socket.set_point('moon_laser_power', (now, power))
moon_socket.set_point('moon_laser_duration', (now, duration))
# Stop the socket server
moon_socket.stop()
A few things to note from the examples. The port number used for the socket is 9000, which is the default for this
type is socket (see Port defaults). The two measurements have been setup to have different timeouts (maximum ages),

which is in seconds by the way, but it could also be set up to be the same, and if it is the same, it can be supplied as just
one float timeouts=0.7 instead of a list of floats. For the sockets, the codenames should be kept relatively short,
but for data safety reasons, they should contain an unambiguous reference to the setup, i.e. the ‘moon_laser’ part.
Client side
The client can be set up in the following manner:
import socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
# hostname can something like 'rasppi250', if that happens to be the one
# located on the moon
host_port = ('moon_raspberry_pi', 9000)
Command and data examples
With the initialization of the client as above, it is now possible to send the socket different commands and get appro-
priate responses. In the following, the different commands are listed, along with how to send it, receive (and decode)
the reply.
The name command
Used to get the name of the socket server, which can be used to make sure that data is being pulled from the correct
location:
command = 'name'
sock.sendto(command, host_port)
data = sock.recv(2048)
at which point the data variable, which contains the reply, will contain the string 'Last shot usage data
from the giant laser on the moon'.
The json_wn command
Tip: The ‘wn’ suffix is short for ‘with names’ and is used for all the sockets to indicate that data is sent or received
prefixed with names of the particular data channel
This command is used to get all the latest data encoded as json. It will retrieve all the data as a dictionary where the
keys are the names, encoded as json for transport:
import json
command = 'json_wn'
data = json.loads(sock.recv(2048))
at which point the data variable will contain a dict like this one:
{u'moon_laser_power': [1414150015.697648, 47.0], u'moon_laser_duration': [1414150015.

˓→697672, 42.0]}

The codenames_json and json commands
It is also possible to decouple the codenames. A possible use case might be to produce a plot of the data. In such a
case, the names are really only needed when setting up the plot, and then afterwards the data should just arrive in the
same order, to add points to the graph. This is exactly what these two command do:
import json
# Sent only once

command = 'codenames_json'
codenames = json.loads(sock.recv(2048))
# Sent repeatedly
command = 'json'
after which the codenames variable would contain a list of codenames:

[u'moon_laser_power', u'moon_laser_duration']
and the data variable would contain a list of points, returned in the same order as the codenames:
[[1414150538.551638, 47.0], [1414150538.551662, 42.0]]
The codename#json command
Note: The codename in the command should be substituted with an actual codename
It is also possible to ask for a single point by name.:

import json
command = 'moon_laser_power#json'
At which point the data variable would contains just a single point as a list:
[1414151366.400581, 47.0]
The raw_wn, codenames_raw, raw and codename#raw commands
These commands do exactly the same as their json counterparts, only that the data is not encoded as json, but with
the homemade raw encoding.
Warning: The raw encoding is manually serialized, which is an 100% guarantied error prone approach, so use
the json variant whenever possible. Even Labview® to some extent supports json as of version 2013.
Remember that when receiving data in the raw encoding, it should not be json decoded, so the code to work with these
commands will look like this:

command = 'some_raw_command' # E.g. raw_wn

data = sock.recv(2048)
There format if the raw encoding is documented in the API documentation for the PullUDPHandler.handle()
method.
Below are a simple list of each type of raw command and example out:
command = 'raw_wn'
# Output
'moon_laser_power:1414154338.17,47.0;moon_laser_duration:1414154338.17,42.0'
command = 'codenames_raw'
# Output
'moon_laser_power,moon_laser_duration'
command = 'raw'
# Output
'1414154433.4,47.0;1414154433.4,42.0'
command = 'moon_laser_power#raw'
# Output
'1414154485.08,47.0'
DataPushSocket, send data (network variable)
To receive data on a machine, the DataPushSocket can be used. To set it up simply to be able to see the last
received data and the updated total data, set it up like this:
from PyExpLabSys.common.sockets import DataPushSocket

name = 'Data receive socket for giant laser on the moon'
dps = DataPushSocket(name, action='store_last')
# Get data
timestamp_last, last = dps.last
timestamp_updated, updated = dps.updated
# ... do whatever and stop socket
dps.stop()
After settings this up, the last received data set will be available as a tuple in the DataPushSocket.last property,
where the first value is the Unix timestamp of reception and the second value is a dictionary with the last received
data (all data sent to the DataPushSocket is in dictionary form, see PushUDPHandler.handle() for details).
Alternatively, the DataPushSocket.updated property contains the last value received ever for each key in the
dict (i.e. not only in the last transmission).
Command examples
The socket server understands commands in two formats, a json and a raw encoded one. For details about how to
send commands to a socket server and receive the reply in the two different encodings, see the sections Client side and
Command and data examples from the DateDataPullSocket make data available (network variable) section.
The json commands looks like this:
json_wn#{"greeting": "Live long and prosper", "number": 47}

json_wn#{"number": 42}

After the first command the data values in both the DataPushSocket.last and the DataPushSocket.
updated properties are:
{u'greeting': u'Live long and prosper', u'number': 47}
After the second command the value in the DataPushSocket.last property is:
{u'number': 42}
and the value in the DataPushSocket.updated property is:
The commands can also be raw encoded, in which case the commands above will be:
raw_wn#greeting:str:Live long and prosper;number:int:47

raw_wn#number:int:42
Warning: See the warning about the raw encoding.
Upon receipt, the socket server will make a message available on the socket, that contains a status for the receipt and
a copy of the data it has gathered (in simple Python string representation). I will look like this:
ACK#{u'greeting': u'Live long and prosper', u'number': 47}
If it does not understand the data, e.g. if it is handed badly formatted raw data, it will return an error:
Sending: "raw_wn#number:88"
Will return: "ERROR#The data part 'number:88' did not match the expected format of 3
˓→parts divided by ':'"
Sending: "raw_wn#number:floats:88"
Will return: "ERROR#The data type 'floats' is unknown. Only ['int', 'float', 'bool',
˓→'str'] are allowed"
DataPushSocket, see all data sets received (enqueue them)
To receive data and make sure that each and every point is reacted to, it is possible to ask the socket to enqueue the
data. It is set up in the following manner:

name = 'Command receive socket for giant laser on the moon'
dps = DataPushSocket(name, action='enqueue')
queue = dps.queue # Local variable to hold the queue
# Get on point
print queue.get()
# Get all data
for _ in range(queue.qsize()):
print queue.get()
# ... do whatever and stop socket
dps.stop()
As seen above, the queue that holds the data items, is available as the DataPushSocket.queue attribute. Data
can be pulled out by calling get() on the queue. NOTE: The for-loop only gets all the data that was available at the

time of calling qsize(), so if the actions inside the for loop takes time, it is possible that new data will be enqueued
while the for-loop is running, which it will not pull out.
If it is desired to use an existing queue or to set up a queue with other than default settings, the DataPushSocket
can be instantiated with a custom queue.
Command examples
Examples of commands that can be sent are the same as in the code example above, after which the queue would end
up containing the two dictionaries:

{u'number': 42}
DataPushSocket, make socket call function on reception (callback)
With the DataPushSocket it is also possible to ask the socket to call a callback function on data reception:

import time
# Module variables
STATE = 'idle'
STOP = False
def callback_func(data):
"""Callback function for the socket"""
print 'Received: {}'.format(data)
#... do fancy stuff depending on the data, e.g. adjust laser settings
# or fire (may change STATE)
name = 'Command callback socket for giant laser on the moon'

dps = DataPushSocket(name, action='callback_async', callback=callback_func)
while not STOP:

# Check if there is a need for continuous activity e.g. monitor
# temperature of giant laser during usage
if STATE == 'fire':
# This function should end when STATE changes away from 'fire'
monitor_temperature()
time.sleep(1)
# After we are all done, stop the socket

dps.stop()
In this examples, the data for the callbacks (and therefore the callbacks themselves) will be queued up and happen
asynchronously. This makes it possible to send a batch of commands without waiting, but there is no monitoring of
whether the queue is filled faster than it can be emptied. It can of course be checked by the user, but if there is a need
for functionality in which the sockets make such checks itself and rejects data if there is too much in queue, then talk
to the development team about it.

Command examples
Command examples this kind of socket will as always be dicts, but in this case will likely have to contain some
information about which action to perform or method to call, but that is entirely up to the user, since that is implemented
by the user in the call back function. Some examples could be:
json_wn#{"action": "fire", "duration": 8, "intensity": 300}

json_wn#{"method": "fire", "duration": 8, "intensity": 300}
DataPushSocket, control class and send return values back (callback with return)
This is reduced version of an example that shows two things:

• How to get the return value when calling a function via the DataPushSocket
• How to control an entire class with a DataPushSocket
class LaserControl(object):
"""Class that controls the giant laser laser on the moon"""
def __init__(self):
self.settings = {'power': 100, 'focus': 100, 'target': None}
self._state = 'idle'
# Start socket
name = 'Laser control, callback socket, for giant laser on the moon'
self.dps = DataPushSocket(name, action='callback_direct',
callback=self.callback)
self.dps.start()
self.stop = False
# Assume one of the methods can set stop
while not self.stop:
# Do continuous stuff on command
time.sleep(1)
self.dps.stop()
def callback(self, data):

"""Callback and central control function"""
# Get the method name and don't pass it on as an argument
method_name = data.pop('method')
# Get the method
method = self.__getattribute__(method_name)
# Call the method and return its return value
return method(**data)
def update_settings(self, **kwargs):

"""Update settings"""
for key in kwargs.keys():
if key not in self.settings.keys():
message = 'Not settings for key: {}'.format(key)
raise ValueError(message)
self.settings.update(kwargs)
return 'Updated settings with: {}'.format(kwargs)

def state(self, state):

"""Set state"""
self._state = state
return 'State set to: {}'.format(state)
This socket would then be sent commands in the form of json encoded dicts from an UDP client in the secret lair.
These dicts could look like:
{'method': 'update_settings', 'power': 300, 'focus': 10}

# or
{'method': 'state', 'state': 'active'}
which would, respectively, make the update_settings method be called with the arguments power=300,
focus=10 and the state method be called with the argument state='active'. NOTE: In this implemen-
tation, it is the responsibility of the caller that the method name exists and that the arguments that are sent have the
correct names. An alternative, but less flexible, way to do the same, would be to make an if-elif-else structure on the
method name and format the arguments in manually:
def callback(self, data):

"""Callback and central control function"""
method_name = data.get('method')
if method_name == 'state':
if data.get('state') is None:
raise ValueError('Argument \'state\' missing')
out = self.state(data['state'])
elif method_name == 'update_settings':
# ....
pass
else:
raise ValueError('Unknown method: {}'.format(method_name))
return out
The complete and running example of both server and client for this example can be downloaded in these two files:
server, client.
Command examples
See the attached files with example code for command examples.
3.4.2 Port defaults
To make for easier configuration on both ends of the network communication, the different kinds of sockets each have
their own default port. They are as follows:
Socket Default port

DateDataPullSocket 9000
DataPullSocket 9010
DataPushSocket 8500
LiveSocket 8000
Again, to ease configuration also on the client side, if more than one socket of the same kind is needed on one machine,
then it is recommended to simply add 1 to the port number for each additional socket.

3.4.3 Inheritance
The DateDataPullSocket and DataPullSocket classes inherit common functionality, such as;
• Input checks
• Initialization of DATA
• Methods to start and stop the thread and reset DATA
from the CommonDataPullSocket class, as illustrated in the diagram below.
PyExpLabSys.common.sockets.PullUDPHandler
SocketServer.BaseRequestHandler
PyExpLabSys.common.sockets.PushUDPHandler
PyExpLabSys.common.sockets.PortStillReserved
PyExpLabSys.common.sockets.LiveSocket PyExpLabSys.common.sockets.CallBackThread
PyExpLabSys.common.sockets.DataPullSocket
threading.Thread PyExpLabSys.common.sockets.CommonDataPullSocket
PyExpLabSys.common.sockets.DateDataPullSocket
PyExpLabSys.common.sockets.DataPushSocket
3.4.4 Status of a socket server
All 4 socket servers understand the status command. This command will return some information about the status
of the machine the socket server is running on and the status of all socket servers running on this machine. The reason
the command returns the status for all the socket servers running on the machine is, that what this command is really
meant for, is to get the status of the system and so it should not be necessary to communicate with several socket
servers to get that.
The data returned is a json encoded dictionary, which looks like this:
{u'socket_server_status':
{u'8000': {u'name': u'my_live_socket',
u'since_last_activity': 0.0009279251098632812,
u'status': u'OK',
u'type': u'live'},
u'9000': {u'name': u'my_socket',
u'since_last_activity': 0.0011229515075683594,
u'status': u'OK',
u'type': u'date'}},
u'system_status':
{u'filesystem_usage': {u'free_bytes': 279182213120,
u'total_bytes': 309502345216},
u'last_apt_cache_change_unixtime': 1413984912.529932,
u'last_git_fetch_unixtime': 1413978995.4109764,
u'load_average': {u'15m': 0.14, u'1m': 0.1, u'5m': 0.15},
u'max_python_mem_usage_bytes': 37552128,
u'number_of_python_threads': 3,
u'uptime': {u'idle_sec': 321665.77,
u'uptime_sec': 190733.39}}}

Socket server status
The socket servers status is broken down into one dictionary for each socket server, indexed by their ports. The status
for the individual socket server comprise of the following items:
name (str) The name of the socket server
since_last_activity (float) The number of seconds since last activity on the socket server
status (str) The status of the socket server. It will return either 'OK' if the last activity was newer than
the activity timeout, or 'INACTIVE' if the last activity was older than the activity timeout or
'DISABLED' is activity monitoring is disabled for the socket server.
type The type of the socket server
System status
The system status items depends on the operating system the socket server is running on.
All operating systems
last_git_fetch_unixtime (float) The Unix timestamp of the last git fetch of the ‘origin’ remote, which
points at the Github archive
max_python_mem_usage_bytes (int) The maximum memory usage of Python in bytes
number_of_python_threads (int) The number of Python threads in use
Linux operating systems
uptime (dict) Information about system uptime (from /proc/uptime). The value 'uptime_sec'
contains the system uptime in seconds and the value 'idle_sec' contains the idle time in seconds.
NOTE: While the uptime is measured in wall time, the idle time is measured in CPU time, which
means that if the system is multi-core, it will add up idle time for all the cores.
last_apt_cache_change_unixtime (float) The Unix time stamp of the last change to the apt cache, which
should be a fair approximation to the last time the system was updated
load_average(dict) The load average (roughly number of active processes) over the last 1, 5 and 15
minutes (from /proc/loadavg). For a detailed explanation see the /proc/loadavg section from
the proc man-page
filesystem_usage (dict) The number of total and free bytes for the file-system the PyExpLabSys archive
is located on
3.4.5 Auto-generated module documentation
The sockets module contains various implementations of UDP socket servers (at present 4 in total) for transmission of
data over the network. The different implementations are tailored for a specific purposes, as described below.
In general, there is a distinction in the naming of the different socket server implementation between push socket
servers, that you can push data to, and pull socket servers, that you can pull data from.
Presently the module contains the following socket servers:

• DateDataPullSocket (DateDataPullSocket) This socket server is used to make continuous data (i.e. one-
value data as function of time) available on the network. It identifies different data channels by codenames and
has a timeout functionality to prevent serving old data to the client.
• DataPullSocket (DataPullSocket) This socket is similar to the date data server, but is used to make x, y
type data available on the network. It identifies different data channel by codenames and has timeout function-
ality to prevent serving old data.
• DataPushSocket (DataPushSocket) This socket is used to recieve data from the network. The data is
received in dictionary form and it identifies the data channels by codenames (keys) in the dictionaries. It will
save the last point, and the last value for each codename. It also has the option to, for each received data set,
to put them in a queue (that the user can then empty) or to call a callback function with the received data as en
argument.
• LiveSocket (LiveSocket) This socket is used only for serving data to the live socket server. It also is not
actually a socket server like the others, but it has a similar interface.
Note: The module variable DATA is a dict shared for all socket servers started from this module. It contains all the
data, queues, settings etc. It can be a good place to look if, to get a behind the scenes look at what is happening.
PyExpLabSys.common.sockets.bool_translate(string)
Returns boolean value from strings ‘True’ or ‘False’
PyExpLabSys.common.sockets.socket_server_status()
Returns the status of all socket servers
Returns
Dict with port to status dict mapping. The status dict has the following keys: name, type,
status (with str values) and since_last_activity with float value.
Return type dict
class PyExpLabSys.common.sockets.PullUDPHandler(request, client_address, server)
Bases: SocketServer.BaseRequestHandler
Request handler for the DateDataPullSocket and DateDataPullSocket socket servers. The com-
mands this request handler understands are documented in the handle() method.
handle()
Returns data corresponding to the request
The handler understands the following commands:
COMMANDS
• raw (str): Returns all values on the form x1,y1;x2,y2 in the order the codenames was given to
the DateDataPullSocket.__init__() or DataPullSocket.__init__() method
• json (str): Return all values as a list of points (which in themselves are lists) e.g: [[x1, y1],
[x2, y2]]), contained in a json string. The order is the same as in raw.
• raw_wn (str): (wn = with names) Same as raw but with names, e.g. codenam1:x1,y1;
codename2:x2,y2. The order is the same as in raw.
• json_wn (str): (wn = with names) Return all data as a dict contained in a json string. In the dict
the keys are the codenames.
• codename#raw (str): Return the value for codename on the form x,y
• codename#json (str): Return the value for codename as a list (e.g [x1, y1]) contained in a json
string

• codenames_raw (str): Return the list of codenames on the form name1,name2

• codenames_json (str): Return a list of the codenames contained in a json string
• name (str): Return the name of the socket server
• status (str): Return the system status and status for all socket servers.
class PyExpLabSys.common.sockets.CommonDataPullSocket(name, codenames, port,
default_x, default_y,
timeouts, check_activity,
activity_timeout,
init_timeouts=True,
handler_class=<class
PyExpLab-
Sys.common.sockets.PullUDPHandler>)
Abstract class that implements common data pull socket functionality.
This common class is responsible for:
• Initializing the thread
• Checking the inputs
• Starting the socket server with the correct handler
• Initializing DATA with common attributes
__init__(name, codenames, port, default_x, default_y, timeouts, check_activity,
activity_timeout, init_timeouts=True, handler_class=<class PyExpLab-
Sys.common.sockets.PullUDPHandler>)
Initializes internal variables and data structure in the DATA module variable
Parameters
• name (str) – The name of the DataPullSocket server. Used for identification and there-
fore should contain enough information about location and purpose to unambiguously
identify the socket server. E.g: 'DataPullSocket with data from giant
laser on the moon'
• codenames (list) – List of codenames for the measurements. The names must be
unique and cannot contain the characters: #,;: and SPACE
• port (int) – Network port to use for the socket (deafult 9010)
• default_x (float) – The x value the measurements are initiated with
• default_y (float) – The y value the measurements are initiated with
• timeouts (float or list of floats) – The timeouts (in seconds as floats) the
determines when the date data socket regards the data as being to old and reports that. If
a list of timeouts is supplied there must be one value for each codename and in the same
order.
• init_timeouts (bool) – Whether timeouts should be instantiated in the DATA mod-
ule variable
• handler_class (Sub-class of SocketServer.BaseRequestHandler) –
The UDP handler to use in the server
• check_activity (bool) – Whether the socket server should monitor activity. What
detemines activity is described in the derived socket servers.

• activity_timeout (float or int) – The timespan in seconds which constitutes

in-activity
run()
Starts the UPD socket server
stop()
Stops the UDP server
Note: Closing the server and deleting the socket server instance is necessary to free up the port for other
usage
poke()
Pokes the socket server to let it know that there is activity
class PyExpLabSys.common.sockets.DataPullSocket(name, codenames, port=9010, de-
fault_x=0.0, default_y=0.0, time-
outs=None, check_activity=True,
activity_timeout=900,
poke_on_set=True)
Bases: PyExpLabSys.common.sockets.CommonDataPullSocket
This class implements a UDP socket server for serving x, y type data. The UDP server uses the
PullUDPHandler class to handle the UDP requests. The commands that can be used with this socket server
are documented in the PullUDPHandler.handle() method.
__init__(name, codenames, port=9010, default_x=0.0, default_y=0.0, timeouts=None,
check_activity=True, activity_timeout=900, poke_on_set=True)
Initializes internal variables and UPD server
For parameter description of name, codenames, port, default_x, default_y, timeouts,
check_activity and activity_timeout see CommonDataPullSocket.__init__().
Parameters poke_on_set (bool) – Whether to poke the socket server when a point is set,
to let it know there is activity
set_point(codename, point, timestamp=None)
Sets the current point for codename
Parameters
• codename (str) – Name for the measurement whose current point should be set
• value (iterable) – Current point as a list or tuple of 2 floats: [x, y]
• timestamp (float) – A unix timestamp that indicates when the point was measured.
If it is not set, it is assumed to be now. This value is used to evaluate if the point is new
enough if timeouts are set.
class PyExpLabSys.common.sockets.DateDataPullSocket(name, codenames, port=9000,
default_x=0.0, de-
fault_y=0.0, timeouts=None,
check_activity=True,
activity_timeout=900,
poke_on_set=True)
Bases: PyExpLabSys.common.sockets.CommonDataPullSocket
This class implements a UDP socket server for serving data as a function of time. The UDP server uses the
PullUDPHandler class to handle the UDP requests. The commands that can be used with this socket server
are documented in the PullUDPHandler.handle() method.

__init__(name, codenames, port=9000, default_x=0.0, default_y=0.0, timeouts=None,

check_activity=True, activity_timeout=900, poke_on_set=True)
Init internal variavles and UPD server
For parameter description of name, codenames, port, default_x, default_y, timeouts,
check_activity and activity_timeout see CommonDataPullSocket.__init__().
Parameters poke_on_set (bool) – Whether to poke the socket server when a point is set,
to let it know there is activity
set_point_now(codename, value)
Sets the current y-value for codename using the current time as x
Parameters
• codename (str) – Name for the measurement whose current value should be set
• value (float) – y-value
set_point(codename, point)
Parameters
• point (iterable) – Current point as a list (or tuple) of 2 floats: [x, y]
class PyExpLabSys.common.sockets.PushUDPHandler(request, client_address, server)
Bases: SocketServer.BaseRequestHandler
This class handles the UDP requests for the DataPushSocket
handle()
Sets data corresponding to the request
The handler understands the following commands:
COMMANDS
• json_wn#data (str): Json with names. The data should be a JSON encoded dict with codename-
>value content. A complete command could look like:
'json_wn#{"greeting": "Live long and prosper", "number": 47}'
• raw_wn#data (str): Raw with names. The data should be a string with data on the following format:
codename1:type:data;codename2:type:data;... where type is the type of the data
and can be one of 'int', 'float', 'str' and 'bool'. NOTE; that neither the names or any
data strings can contain any of the characters in BAD_CHARS. The data is a comma separated list of
data items of that type. If there is more than one, they will be put in a list. An example of a complete
raw_wn string could look like:
'raw_wn#greeting:str:Live long and prosper;numbers:int:47,42'
• name (str): Return the name of the PushSocket server
• status (str): Return the system status and status for all socket servers.
• commands (str): Return a json encoded list of commands. The returns value is is prefixed with
PUSH_RET and ‘#’ so e.g. ‘RET#actual_date’

class PyExpLabSys.common.sockets.DataPushSocket(name, port=8500, ac-

tion=u’store_last’, queue=None, call-
back=None, return_format=u’json’,
check_activity=False, activ-
ity_timeout=900)
This class implements a data push socket and provides options for enqueuing, calling back or doing nothing on
reciept of data
__init__(name, port=8500, action=u’store_last’, queue=None, callback=None, re-
turn_format=u’json’, check_activity=False, activity_timeout=900)
Initializes the DataPushSocket
Parameters
• name (str) – The name of the socket server. Used for identification and therefore
should contain enough information about location and purpose to unambiguously iden-
tify the socket server. E.g: 'Driver push socket for giant laser on the
moon'
• port (int) – The network port to start the socket server on (default is 8500)
• action (string) – Determined the action performed on incoming data. The possible
values are:
– 'store_last' (default and always) the incoming data will be stored, as a dict, only
in the two properties; last and updated, where last contains only the data from
the last reception and updated contains the newest value for each codename that has
been received ever. Saving to these two properties will always be done, also with the
other actions.
– 'enqueue'; the incoming data will also be enqueued
– 'callback_async' a callback function will also be called with the incoming data as
an argument. The calls to the callback function will in this case happen asynchronously
in a seperate thread
– 'callback_direct' a callback function will also be called and the result will be
returned, provided it has a str representation. The return value format can be set with
return_format
• queue (Queue.Queue) – If action is ‘enqueue’ and this value is set, it will be used as
the data queue instead the default which is a new Queue.Queue instance without any
further configuration.
• callback (callable) – A callable that will be called on incoming data. The callable
should accept a single argument that is the data as a dictionary.
• return_format (str) – The return format used when sending callback return values
back (used with the 'callback_direct' action). The value can be:
– 'json', which, if possible, will send the value back encoded as json
– 'raw' which, if possible, will encode a dict of values, a list of lists or None. If it
is a dict, each value may be a list of values with same type, in the same way as they
are received with the 'raw_wn' command in the PushUDPHandler.handle()
method. If the return value is a list of lists (useful e.g. for several data points), then all
values must be of the same type. The format sent back looks like: '1.0,42.0&1.
5,45.6&2.0,47.0', where ‘&’ separates the inner lists and ‘,’ the points in those
lists

– 'string' in which the string representation of the value the call back returns will be
sent back. NOTE: These string representations may differ between Python 2 and 3, so
do not parse them
run()
Starts the UPD socket server
stop()
Stops the UDP socket server
Note: Closing the server and deleting the SocketServer.UDPServer socket instance is necessary
to free up the port for other usage
queue
Gets the queue, returns None if action is 'store_last' or 'callback_direct'
last
Gets a copy of the last data
Returns
tuple: (last_data_time, last_data) where last_data is the data from the last recep-
tion and last_data_time is the Unix timestamp of that reception. Returns (None, None)
if no data has been recieved.
updated
Gets a copy of the updated total data, returns empty dict if no data has been received yet
Returns
(updated_data_time, updated_data) where updated_data is the total up-
dated data after the last reception and updated_data_time is the Unix timestamp
of that reception. Returns (None, {}) if no data has been recieved.
Return type tuple
set_last_to_none()
Sets the last data point and last data point time to None
clear_updated()
Clears the total updated data and set the time of last update to None
poke()
Pokes the socket server to let it know that there is activity
class PyExpLabSys.common.sockets.CallBackThread(queue, callback)
Class to handle the calling back for a DataReceiveSocket
__init__(queue, callback)
Initialize the local variables
Parameters
• queue (Queue.Queue) – The queue that queues up the arguments for the callback
function
• callback (callable) – The callable that will be called when there are items in the
queue

run()
Starts the calling back
stop()
Stops the calling back
exception PyExpLabSys.common.sockets.PortStillReserved
Custom exception to explain socket server port still reserved even after closing the port
__init__()
class PyExpLabSys.common.sockets.LiveSocket(name, codenames, live_server=None,
no_internal_data_pull_socket=False, inter-
nal_data_pull_socket_port=8000)
Bases: object
This class implements a Live Socket
As of version 2 LiveSocket there are a few new features to note:
1. There is now support for values of any json-able object. The values can of course only be shown in a graph
if they are numbers, but all other types can be shown in a table.
2. There is now support for generic xy data. Simply use set_point() or set_batch() and give it x, y
values.
__init__(name, codenames, live_server=None, no_internal_data_pull_socket=False, inter-
nal_data_pull_socket_port=8000)
Intialize the LiveSocket
Parameters
• name (str) – The name of the socket
• codenames (sequence) – The codenames for the different data channels on this
LiveSocket
• live_server (sequence) – 2 element sequence of hostname and port for
the live server to connect to. Defaults to (Settings.common_liveserver_host, Set-
tings.common_liveserver_host).
• no_internal_data_pull_socket (bool) – Whether to not open an internal Dat-
aPullSocket. Defaults to False. See note below.
• internal_data_pull_socket_port (int) – Port for the internal DataPull-
Socket. Defaults to 8000. See note below.
Note: In general, any socket should also work as a status socket. But since the new design of the live
socket, it no longers runs a UDP server, as would be required for it to work as a status socket. Therefore,
LiveSocket now internally runs a DataPullSocket on port 8000 (that was the old LiveSocket port) to work
as a status socket. With default setting, everything should work as before.
start()
Starts the internal DataPullSocket
stop()
Stop the internal DataPullSocket
set_batch(data)
Set a batch of points now

Parameters data (dict) – Batch of data on the form {codename1: (x1, y1), codename2: (x2,
y2)}. Note, that for the live socket system, the y values need not be data in the form of a
float, it can also be an int, bool or str. This is done to make it possible to also transmit e.g.
equipment status to the live pages.
Note: All data is sent to the live socket proxy and onwards to the web browser clients as batches, so if the
data is on batch form, might as well send it as such and reduce the number of transmissions.
set_batch_now(data)
Set a batch of point now
Parameters data (dict) – A mapping of codenames to values without times or x-values (see
example below)
The format for data is:
{'measurement1': 47.0, 'measurement2': 42.0}
set_point_now(codename, value)
Sets the current value for codename using the current time as x
Parameters
• codename (str) – Name for the measurement whose current value should be set
• value (float, int, bool or str) – value
set_point(codename, point)
Parameters
• point (list or tuple) – Current value “point” as a list (or tuple) of items, the first
must be a float, the second can be float, int, bool or str
reset(codenames)
Send the reset signal for codenames
Parameters codenames (list) – List of codenames
PyExpLabSys.common.sockets.BAD_CHARS = [u'#', u',', u';', u':', u'&']
The list of characters that are not allowed in code names
PyExpLabSys.common.sockets.UNKNOWN_COMMAND = u'UNKNOWN_COMMMAND'
The string returned if an unknown command is sent to the socket
PyExpLabSys.common.sockets.OLD_DATA = u'OLD_DATA'
The string used to indicate old or obsoleted data
PyExpLabSys.common.sockets.PUSH_ERROR = u'ERROR'
The answer prefix used when a push failed
PyExpLabSys.common.sockets.PUSH_ACK = u'ACK'
The answer prefix used when a push succeds
PyExpLabSys.common.sockets.PUSH_EXCEP = u'EXCEP'
The answer prefix for when a callback or callback value formatting produces an exception
PyExpLabSys.common.sockets.PUSH_RET = u'RET'
The answer prefix for a callback return value

PyExpLabSys.common.sockets.DATA = {}
The variable used to contain all the data.
The format of the DATA variable is the following. The DATA variable is a dict, where each key is an integer port
number and the value is the data for the socket server on that port. The data for each individual socket server is
always a dict, but the contained values will depend on which kind of socket server it is, Examples below.
For a DateDataPullSocket the dict will resemble this example:
{'activity': {'activity_timeout': 900,

'check_activity': True,
'last_activity': 1413983209.82526},
'codenames': ['var1'],
'data': {'var1': (0.0, 0.0)},
'name': 'my_socket',
'timeouts': {'var1': None},
'type': 'date'}
For a DataPullSocket the dict will resemble this example:
{'activity': {'activity_timeout': 900,

'check_activity': True,
'last_activity': 1413983209.825451},
'codenames': ['var1'],
'data': {'var1': (0.0, 0.0)},
'name': 'my_data_socket',
'timeouts': {'var1': None},
'timestamps': {'var1': 0.0},
'type': 'data'}
For a DataPushSocket the dict will resemble this example:
{'action': 'store_last',
'activity': {'activity_timeout': 900,
'check_activity': False,
'last_activity': 1413983209.825681},
'last': None,
'last_time': None,
'name': 'my_push_socket',
'type': 'push',
'updated': {},
'updated_time': None}
PyExpLabSys.common.sockets.TYPE_FROM_STRING = {u'int': <type 'int'>, u'float': <type 'flo

The dict that transforms strings to convertion functions
PyExpLabSys.common.sockets.run_module()
This functions sets
3.5 The socket_client module
3.6 The utilities module
This module contains convenience functions for quick setup of common tasks.

Table of Contents
• The utilities module

– Get a logger
– get_logger usage examples
* Logging to terminal and send emails on warnings and above (default)

* Rotating file logger
* Getting the logger to send emails on un-caught exceptions
3.6.1 Get a logger
The get_logger() function is a convenience function to setup logging output. It will return a named logger, which
can be used inside programs. The function has the ability to setup logging both to a terminal, to a log file, including
setting up log rotation and for sending out email on log message at warning level or above.
3.6.2 get_logger usage examples
Logging to terminal and send emails on warnings and above (default)
To get a named logger that will output logging information to the terminal and send emails on warnings and above, do
the following:
from PyExpLabSys.common.utilities import get_logger

LOGGER = get_logger('name_of_my_logger')
where the name_of_my_logger should be some descriptive name for what the program/script does e.g. “cof-
fee_machine_count_monitor”.
From the returned LOGGER, information can now be logged via the usual .info(), .warning() methods etc.
To turn logging to the terminal of (and only use the other configured logging handlers), set the optional boolean
terminal_log parameter to False.
The email notification on warnings and above is on-by-default and is controlled by the two optional boolean parameters
email_on_warnings and email_on_errors. It will send emails on logged warnings to the warnings list and
on logged errors (and above) to the error list.
Rotating file logger
To get a named logger that also logs to a file do:

LOGGER = get_logger('name_of_my_logger', file_log=True)
The log will be written to the file name_of_my_logger.log. The file name can be changed via the option
file_name, the same way as the maximum log file size and number of saved backups can be changed, as documented
below.
3.6. The utilities module 55

Getting the logger to send emails on un-caught exceptions
To also make the logger send en email, containing any un-caught exception, do the following:

LOGGER = get_logger('Test logger')
def main():
pass # All your main code that might raise exceptions
if __name__ == '__main__':
try:
main()
pass # Shut down code here
except Exception:
LOGGER.exception("Main program failed")
# Possibly shut down code here
raise
Note: The argument to LOGGER.exception is a string, just like all other LOGGER methods. All the exception
information, like the traceback, line number etc., is picked up automatically by the logger. Also note, that the raise
will re-raise the caught exception, to make sure that the program fails like it is supposed to. That it is the caught
exception that is re-raised, is implicit when using raise without arguments in an except clause.
Note: In the example there is a seperate except for the KeyboardInterrupt exception, to make it possible to
use keyboard interrupts to shut the program down, without sending an exception email about it.
This module contains a convenience function for easily setting up a logger with the logging module.
This module uses the following settings from the Settings class:
• util_log_warning_email
• util_log_error_email
• util_log_mail_host
• util_log_max_emails_per_period (defaults to 5)
• util_log_email_throttle_time (defaults to 86400s = 1day)
• util_log_backlog_limit (defaults to 250)
Note: All of these settings are at present read from the settings module at import time, so if it is desired
to modify them at run time, it should be done before import
PyExpLabSys.common.utilities.SETTINGS = <PyExpLabSys.settings.Settings object>

The Settings object used in this module
PyExpLabSys.common.utilities.WARNING_EMAIL = 'FYS-list-CINF-FM@fysik.dtu.dk'
The email list warning emails are sent to

PyExpLabSys.common.utilities.ERROR_EMAIL = 'FYS-list-CINF-FM@fysik.dtu.dk'
The email list error emails are sent to
PyExpLabSys.common.utilities.MAIL_HOST = 'mail.fysik.dtu.dk'
The email host used to send emails on logged warnings and errors
PyExpLabSys.common.utilities.MAX_EMAILS_PER_PERIOD = 5
The maximum number of emails the logger will send in EMAIL_THROTTLE_TIME
PyExpLabSys.common.utilities.EMAIL_THROTTLE_TIME = 86400
The time period that the numbers of emails will be limited within
PyExpLabSys.common.utilities.EMAIL_BACKLOG_LIMIT = 250
The maximum number of messages in the email backlog that will be sent when the next email is let through
PyExpLabSys.common.utilities.get_logger(name, level=u’INFO’, termi-
nal_log=True, file_log=False,
file_name=None, file_max_bytes=1048576,
file_backup_count=1, email_on_warnings=True,
email_on_errors=True)
Setup and return a program logger
This is meant as a logger to be used in a top level program/script. The logger is set up for with terminal, file and
email handlers if requested.
Parameters
• name (str) – The name of the logger, e.g: ‘my_fancy_program’. Passing in an empty
string will return the root logger. See note below.
• level (str) – The level for the logger. Can be either 'DEBUG', 'INFO', 'WARNING',
'ERROR' or 'CRITICAL'. See logging for details. Default is 'INFO'.
• terminal_log (bool) – If True then logging to a terminal will be activated. Default is
True.
• file_log (bool) – If True then logging to a file, with log rotation, will be activated. If
file_name is not given, then name + '.log' will be used. Default is False.
• file_name (str) – Optional file name to log to
• file_max_size (int) – The maximum size of the log file in bytes. The default is
1048576 (1MB), which corresponds to roughly 10000 lines of log per file.
• file_backup_count (int) – The number of backup logs to keep. The default is 1.
• email_on_warnings (bool) – Whether to send an email to the WARNING_EMAIL
email list if a warning is logged. The default is True.
• email_on_error (bool) – Whether to send en email to the ERROR_EMAIL email list
if an error (or any logging level above) is logged. The default is True.
Returns A logger module with the requested setup
Return type logging.Logger
Note: Passing in the empty string as the name, will return the root logger. That means that all other library
loggers will inherit the level and handlers from this logger, which may potentially result in a lot of output. See
activate_library_logging() for a way to activate the library loggers from PyExpLabSys in a more
controlled manner.
3.6. The utilities module 57

PyExpLabSys.common.utilities.get_library_logger_names()
Return all loggers currently configured in PyExpLabSys
PyExpLabSys.common.utilities.print_library_logger_names()
Nicely printout all loggers currently configured in PyExpLabSys
PyExpLabSys.common.utilities.activate_library_logging(logger_name, log-
ger_to_inherit_from=None,
level=None, termi-
nal_log=True, file_log=False,
file_name=None,
file_max_bytes=1048576,
file_backup_count=1,
email_on_warnings=True,
email_on_errors=True)
Activate logging for a PyExpLabSys library logger
Parameters
• logger_name (str) – The name of the logger to activate, as returned by
get_library_logger_names()
• logger_to_inherit_from (logging.Logger) – (Optional) If this is set, the li-
brary logger will simply share the handlers that are present in this logger. The library to be
activated will also inherit the level from this logger, unless level is set, in which case it
will override. In case neither level nor the level on logger_to_inherit_from is
set, the level will not be changed.
• level (str) – (Optional) See docstring for get_logger(). If
logger_to_inherit_from is not set, it will default to ‘info’.
• terminal_log (bool) – See docstring for get_logger()
• file_log (bool) – See docstring for get_logger()
• file_name (str) – See docstring for get_logger()
• file_max_size (int) – See docstring for get_logger()
• file_backup_count (int) – See docstring for get_logger()
• email_on_warnings (bool) – See docstring for get_logger()
• email_on_error (bool) – See docstring for get_logger()
class PyExpLabSys.common.utilities.CustomSMTPHandler(mailhost, fromaddr, toaddrs,
subject, credentials=None, se-
cure=None)
Bases: logging.handlers.SMTPHandler
PyExpLabSys modified SMTP handler
emit(record)
Custom emit that throttles the number of email sent
getSubject(record)
Returns subject with hostname
class PyExpLabSys.common.utilities.CustomSMTPWarningHandler(mailhost, fromaddr,
toaddrs, subject,
credentials=None,
secure=None)
Bases: PyExpLabSys.common.utilities.CustomSMTPHandler

Custom SMTP handler to emit record only if: warning =< level < error
emit(record)
Custom emit that checks if: warning =< level < error
PyExpLabSys.common.utilities.call_spec_string()
Return the argument names and values of the method or function it was called from as a string
Returns
The argument string, e.g: (name=’hello’, codenames=[‘aa’, ‘bb’], port=8000)
Return type str
3.7 The combos module
The combos are cobinations of other PyExpLabSys components in commonly used configurations. Currently the only
implemented combination are:
• LiveContinuousLogger which combines a LiveSocket with a ContinuousDataSaver and
Table of Contents
• The combos module

– Examples
* LiveContinuousLogger
3.7.1 Examples
LiveContinuousLogger
This example shows the case of using the combo to log values individually, using the “now” variety of the method
(LiveContinuousLogger.log_point_now()), which uses the time now as the x-value:
from time import sleep
from random import random
from math import sin
from PyExpLabSys.combos import LiveContinuousLogger
# Initialize the combo and start it

combo = LiveContinuousLogger(
name='test',
codenames=['dummy_sine_one', 'dummy_sine_two'],
continuous_data_table='dateplots_dummy',
username='dummy',
password='dummy',
time_criteria=0.1,
)
combo.start()
# Measurement loop (typically runs forever, here just for 10 sec)
3.7. The combos module 59

for _ in range(10):
# The two sine values here emulate a value to be logged
sine_one = sin(random())
sine_two = sin(random())
combo.log_point_now('dummy_sine_one', sine_one)
combo.log_point_now('dummy_sine_two', sine_two)
sleep(1)
combo.stop()
or if it is preferred to keep track of the timestamp manually, the LiveContinuousLogger.log_point()

method which can be used instead:
from time import sleep, time
from math import sin, pi

name='test',
username='dummy',
password='dummy',
time_criteria=0.1,
)
combo.start()

for _ in range(10):
now = time()
sine_one = sin(now)
sine_two = sin(now + pi)
combo.log_point('dummy_sine_one', (now, sine_one))
combo.log_point('dummy_sine_two', (now, sine_two))
sleep(1)
combo.stop()
Of course, like most of the underlying code, the combo also takes data at batches, as shown in the following example
(using LiveContinuousLogger.log_batch()):
from time import sleep, time
from math import sin, pi

name='test',
username='dummy',
password='dummy',
time_criteria=0.1,
)

combo.start()

for _ in range(10):
now = time()
points = {
'dummy_sine_one': (now, sin(now)),
'dummy_sine_two': (now, sin(now + pi)),
}
combo.log_batch(points)
sleep(1)
combo.stop()
For the bacthes there is of course also a “now” variety (LiveContinuousLogger.log_batch_now()), which
there is no example for, but the difference is same as for the single point/value.
This module contains socket, database saver and logger heuristic combinations
class PyExpLabSys.combos.LiveContinuousLogger(name, codenames, continu-
ous_data_table, username, pass-
word, time_criteria=None,
absolute_criteria=None,
relative_criteria=None,
live_server_kwargs=None)
Bases: object
A combination of a LiveSocket and a ContinuousDataSaver that also does logging heuristics
FIXME explain the term log
__init__(name, codenames, continuous_data_table, username, password, time_criteria=None, abso-
lute_criteria=None, relative_criteria=None, live_server_kwargs=None)
Initialize local data
Parameters
• name (str) – The name to be used in the sockets
• codenames (sequence) – A sequence of codenames. These codenames are the mea-
surements codenames for the ContinuousDataSaver and they will also be used as
the codenames for the LiveSocket.
• continuous_data_table (str) – The continuous data table to log data to
• username (str) – The MySQL username
• password (str) – The password for username in the database
• time_criteria (float or dict) – (Optional) The time after which a point will
always be saved in the database. Either a single value, which will be used for all co-
denames or a dict of codenames to values. If supplying a dict, each codename must be
present as a key.
• absolute_criteria (float or dict) – (Optional) The absolute value difference
criteria. Either a single value or one for each codename, see time_criteria for details.
3.7. The combos module 61

• relative_criteria (float or dict) – (Optional) The relative value difference

criteria. Either a single value or one for each codename, see time_criteria for details.
• lives_server_kwargs (dict) – (Optinal) A dict of keyword arguments for the
LiveSocket. See the doc string for LiveSocket.__init__() for additional de-
tails.
start()
Start the underlying LiveSocket and ContinuousDataSaver
stop()
Stop the underlying LiveSocket and ContinuousDataSaver
log_point_now(codename, value)
Log a point now
As the time will be attached the time now.
For an explanation of what is meant by the term “log”, see the class docstring.
Parameters
• codename (str) – The codename to log this point for
• value (float) – The value to store with the time now (time.time())
log_point(codename, point)
Log a point
Parameters
• codename (str) – The codename to log this point for
• point (sequence) – A (unix_time, value) two item sequence (e.g. list or tuple), that
represents a point
log_batch_now(values)
Log a batch of values now
Parameters values (dict) – Dict of codenames to values. The values will be stored with the
time now (time.time())
log_batch(points)
Log a batch of points
Parameters points (dict) – Dict of codenames to points
3.8 The settings module
Settings for PyExpLabSys component are handled via the Settings class in the settings module.
3.8.1 Getting started
To use the settings module instantiate a Settings object and access the settings as attributes:

>>> from PyExpLabSys.settings import Settings

>>> settings = Settings()
>>> settings.util_log_max_emails_per_period
5
User settings can be modified at run time simply by assigning a new value to the attributes:
>>> settings.util_log_max_emails_per_period = 7
7
3.8.2 Details
The settings are handled in two layers; defaults and user settings.
The defaults are stored in the PyExpLabSys/defaults.yaml file.
Note: It is not possible to write to a setting that does not have a default
Note: In the defaults, a value of null is used to indicate a settings that must be overwritten by a user setting before
any modules tries to use it.
The user settings are stored in a user editable file. The path used is stored in the settings.USERSETTINGS_PATH
variable. On Linux system the user settings path is ~/.config.PyExpLabSys.user_settings.yaml.
Note: If the value is None, it means that your operating system is not yet supported by the sett ings module. This
should be reported as an issue on Github.
All Settings objects share the same settings, so changes made via one object will be used everywhere, in fact
that is what makes it possible to modify settings at runtime (as shown above). Do however note, that different
modules reads the settings at different points in time. Some will read them when an object from that module
is instantiated and others will read them at module import time. That means, that for some modules it will be
necessary to modify the settings before the rest of the PyExpLabSys modules is imported, in order to be able to modify
them at runtime. At which point in time the settings are read should be stated in the module documentation.
This module contains the modules used for settings for PyExpLabSys
To use the settings module instantiate a Settings object and access the settings as attributes:

5
The settings in the Settings are formed by 2 layers. The bottom layer are the defaults, that are stored in the
PyExpLabSys/defaults.yaml file. Op top of those are placed the user settings, that originate from the file whose path is
in the settings.USERSETTINGS_PATH variable. The user settings can me modified at run time as opposed to having
3.8. The settings module 63

to write them to the user settings file before running. This is done simply by writing to the properties on the settings
object:
>>> settings.util_log_max_emails_per_period = 7
7
All Settings objects share the same settings, so these changes will be used when using other parts of PyExpLabSys
that makes use of one of the settings. Do however note, that different parts of PyExpLabSys use the settings at
different times (instantiate, call etc.) so check with the documentation for each component when the settings needs to
be modified to take effect.
PyExpLabSys.settings.value_str(obj)
Return a object and type str or NOT_SET if obj is None
class PyExpLabSys.settings.Settings
Bases: object
The PyExpLabSys settings object
The settings are available to get and setable on this object as attributes i.e:

5
The settings are stored as a ChainMap of the defaults and the user settings and this ChainMap object containing
the current state of the settings is shared between all Settings objects.
To get a list of all available settings see the Settings.settings_names attribute. To get a pretty print of
all settings names, types, default values, user setting values (if any) use the Settings.print_settings()
method.
settings = ChainMap({'util_log_warning_email': 'FYS-list-CINF-FM@fysik.dtu.dk', 'util_
The settings ChainMap
settings_names = ['common_sql_reader_password', 'util_log_warning_email', 'util_log_err
The available setting names
__init__()
print_settings()
Pretty print of all default and user settings
PyExpLabSys.settings.main()
Main function used to simple testing

CHAPTER 4
File parsers
File parsers.
Table of Contents
• File parsers
– XML based file formats
* Specs File Format

– Binary File Formats
4.1 XML based file formats
4.1.1 Specs File Format
This file is used to parse XPS and ISS data from XML files from the SPECS program.
In this file format the spectra (called regions) are containd in region groups inside the files. This structure is mirrored
in the data structure below where classes are provided for the 3 top level objects:
Files -> Region Groups -> Regions
The parser is strict, in the sense that it will throw an exception if it encounters anything it does not understand. To
change this behavior set the EXCEPTION_ON_UNHANDLED module variable to False.
Usage examples
To use the file parse, simply feed the top level data structure a path to a data file and start to use it:
65
from PyExpLabSys.file_parsers.specs import SpecsFile

import matplotlib.pyplot as plt
file_ = SpecsFile('path_to_my_xps_file.xml')
# Access the regions groups by iteration
for region_group in file_:
print '{} regions groups in region group: {}'.format(
len(region_group), region_group.name)
# or by index
region_group = file_[0]
# And again access regions by iteration

for region in region_group:
print 'region: {}'.format(region.name)
# or by index
region = region_group[0]
# or you can search for them from the file level

region = list(file_.search_regions('Mo'))[0]
print region
# NOTE the search_regions method returns a generator of results, hence the
# conversion to list and subsequent indexing
# From the regions, the x data can be accessed either as kinetic

# or binding energy (for XPS only) and the y data can be accessed
# as averages of the counts, either as pure count numbers or as
# counts per second. These options works independently of each
# other.
# counts as function of kinetic energy

plt.plot(region.x, region.y_avg_counts)
plt.show()
# cps as function of binding energy

plt.plot(region.x_be, region.y_avg_cps)
plt.show()
# Files also have a useful str representation that shows the hierachi
print file_
Notes
The file format seems to basically be a dump, of a large low level data structure from the implementation language.
With an appropriate mapping of low level data structure types to python types (see details below and in the sim-
ple_convert function), this data structure could have been mapped in its entirety to python types, but in order to
provide a more clear data structure a more object oriented approach has been taken, where the top most level data
structures are implemented as classes. Inside of these classes, the data is parsed into numpy arrays and the remaining
low level data structures are parsed in python data structures with the simple_convert function.
Module Documentation
PyExpLabSys.file_parsers.specs.simple_convert(element)
Converts a XML data structure to pure python types.
66 Chapter 4. File parsers

Parameters element (xml.etree.ElementTree.Element) – The XML element to con-

vert
Returns A hierachi of python data structure
Return type object
Simple element types are converted as follows:
XML type | Python type

string str
ulong long
double float
boolean bool
struct dict
sequence list
Arrays are converted to numpy arrays, wherein the type conversion is:
XML type | Python type

ulong numpy.uint64
double numpy.double
Besides these types there are a few special elements that have a custom conversion.
• Enum are simply converted into their value, since enums are considered to be a program implementation
detail whose information is not relavant for a data file parser
• Any is skipped and replaced with its content
class PyExpLabSys.file_parsers.specs.SpecsFile(filepath, encoding=None)
Bases: list
This is the top structure for a parsed file which represents a list of RegionGroups
The class contains a ‘filepath’ attribute.
__init__(filepath, encoding=None)
Parse the XML and initialize the internal variables
regions_iter
Returns a iteration over the regions
search_regions_iter(search_term)
Returns an generator of search results for regions by name
Parameters search_term (str) – The term to search for (case sensitively)
Returns An iterator of maching regions
Return type generator
search_regions(search_term)
Returns an list of search results for regions by name
Parameters search_term (str) – The term to search for (case sensitively)
Returns A list of matching regions
Return type list
4.1. XML based file formats 67

unix_timestamp
Returns the unix timestamp of the first region
get_analysis_method()
Returns the analysis method of the file
Raises ValueError – If more than one analysis method is used
class PyExpLabSys.file_parsers.specs.RegionGroup(xml)
Bases: list
Class that represents a region group, which consist of a list of regions
The class contains a ‘name’ and and ‘parameters’ attribute.
__init__(xml)
Initializes the region group
Expects to find 3 subelement; the name, regions and parameters. Anything else raises an exception.
Parsing parameters is not supported and therefore logs a warning if there are any.
class PyExpLabSys.file_parsers.specs.Region(xml)
Bases: object
Class that represents a region
The class contains attributes for the items listed in the ‘information_names’ class variable.
Some useful ones are:
• name: The name of the region
• region: Contains information like, dwell_time, analysis_method, scan_delta, excitation_energy etc.
All auxiliary information is also available from the ‘info’ attribute.
__init__(xml)
Parse the XML and initialize internal variables
Parameters xml (xml.etree.ElementTree.Element) – The region XML element
x
Returns the kinetic energy x-values as a Numpy array
x_be
Returns the binding energy x-values as a Numpy array
iter_cycles
Returns a generator of cycles
Each cycle is in itself a generator of lists of scans. To iterate over single scans do:
for cycle in self.iter_cycles:

for scans in cycle:
for scan in scans:
print scan
or use iter_scans, which do just that.

iter_scans
Returns an generator of single scans, which in themselves are Numpy arrays
y_avg_counts
Returns the average counts as a Numpy array

y_avg_cps
Returns the average counts per second as a Numpy array
unix_timestamp
Returns the unix timestamp of the first cycle
exception PyExpLabSys.file_parsers.specs.NotXPSException
Exception for trying to interpret non-XPS data as XPS data
4.2 Binary File Formats
File parser for Chemstation files
Note: This file parser went through a large re-write on ??? which changed the data structures of the resulting objects.
This means that upon upgrading it will be necessary to update code. The re-write was done to fix some serious errors
from the first version, like relying on the Report.TXT file for injections summaries. These are now fetched from the
more ordered CSV files.
class PyExpLabSys.file_parsers.chemstation.CHFile(filepath)
Bases: object
Class that implementats the Agilent .ch file format version 179
Warning: Not all aspects of the file header is understood, so there may and probably is information that is
not parsed. See the method _parse_header_status() for an overview of which parts of the header is
understood.
Note: Although the fundamental storage of the actual data has change, lots of inspiration for the parsing of the
header has been drawn from the parser in the ImportAgilent.m file in the chemplexity/chromatography project
project. All credit for the parts of the header parsing that could be reused goes to the author of that project.
values
numpy.array – The internsity values (y-value) or the spectrum. The unit for the values is given in meta-
data[‘units’]
metadata
dict – The extracted metadata
filepath
str – The filepath this object was loaded from
__init__(filepath)
Instantiate object
Parameters filepath (str) – The path of the data file
times
The time values (x-value) for the data set in minutes
4.2. Binary File Formats 69

class PyExpLabSys.file_parsers.chemstation.Injection(injection_dirpath,
load_raw_spectra=True,
read_report_txt=True)
Bases: object
The Injection class for the Chemstation data format
Parameters
• injection_dirpath (str) – The path of the directory of this injection
• reports (defaultdict) – Signal -> list_of_report_lines dict. Each report line is dict
of column headers to type converted column content. E.g:
{u'Area': 22.81, u'Area %': 0.24, u'Height': 12.66,

u'Peak Number': 1, u'Peak Type': u'BB', u'Peak Widthmin':
0.027, u'Retention Timemin': 5.81}
The columns headers are also stored in :attr‘~metadata‘ under the columns key.
• reports_raw (defaultdict) – Same as reports except the content is not type con-
verted.
• metadata (dict) – Dict of metadata
• raw_files (dict) – Mapping of ch_file_name -> CHFile objects
• report_txt (str or None) – The content of the Report.TXT file from the injection
folder is any
__init__(injection_dirpath, load_raw_spectra=True, read_report_txt=True)
Instantiate Injection object
Parameters
• injection_dirpath (str) – The path of the injection directory
• load_raw_spectra (bool) – Whether to load raw spectra or not
• read_report_txt (bool) – Whether to read and save the Report.TXT file
exception PyExpLabSys.file_parsers.chemstation.NoInjections
Exception raised when there are no injections in the sequence
class PyExpLabSys.file_parsers.chemstation.Sequence(sequence_dir_path)
Bases: object
The Sequence class for the Chemstation data format
Parameters
• injections (list) – List of Injection’s in this sequence
• sequence_dir_path (str) – The path of this sequence directory
• metadata (dict) – Dict of metadata
__init__(sequence_dir_path)
Instantiate object properties
Parameters sequence_dir_path (str) – The path of the sequence
full_sequence_dataset(column_names=None)
Generate peak name specific dataset

This will collect area values for named peaks as a function of time over the different injections.
Parameters column_names (dict) – A dict of the column names needed from the report
lines. The dict should hold the keys: ‘peak_name’, ‘retention_time’ and ‘area’. It defaults to:
column_names = {‘peak_name’: ‘Compound Name’, ‘retention_time’: ‘Retention Timemin’,
‘area’: ‘Area’}
Returns Mapping of signal_and_peak names and the values
Return type dict
PyExpLabSys.file_parsers.chemstation.parse_utf16_string(file_, encod-
ing=u’UTF16’)
Parse a pascal type UTF16 encoded string from a binary file object
4.2. Binary File Formats 71


CHAPTER 5
Apps
This section documents the various apps in PyExpLabSys.
5.1 The Bakeout App
Contents
• The Bakeout App

– A Section
* A subsection
This app . . . FIXME
5.1.1 A Section
A subsection
73
74 Chapter 5. Apps
CHAPTER 6
Hardware Drivers
This section documents the hardware drivers developed at CINF. Most of the drivers are for equipment to surface
science such as mass spectrometers and pressure gauges, but there are also some drivers for more general equipment
like temperature read out units.
6.1 The bio_logic module
This module implements a driver for the SP-150 BioLogic potentiostat.

The implementation is built up around the notion of an instrument and techniques. To communicate with the device,
it is required to first create an instrument, and then a technique and then load the technique onto the instrument. This
implementation was chosen because it closely reflects that way the specification is written and the official ECLab
program is structured.
This driver communicates with the potentiostats via the EC-lib dll, which is present in the ECLab development pack-
ages. This package must be installed before the driver can be used. It can be downloaded from the BioLogic website.
See the Usage Example sections some examples on how to use this driver.
See the Inheritance diagram for an inheritance diagram, that gives a good overview over the available instruments and
techniques.
Note: See some important notes on 64 bit Windows and instruments series in the beginning of the API
documentation.
6.1.1 Implementation status and details
There is a whole range of potentiostats (VMP2/VMP3, BiStat, VSP, SP-50/SP-150, MGP2, HVP-803, SP-200, SP-
300) that are covered by the same interface and which therefore with very small adjustments could be supported by
this module as well. Currently only the SP-150 is implemented, because that is the only one we have in-house. See
the section Use/Implement a new potentiostat for details.
75
This module currently implements the handful of techniques that are used locally (see a complete list at the top of
the module documentation). It does however implement a Technique base class, which does all the hard work of
formatting the technique arguments correctly, which means that writing a adding a new technique is limited to writing
a new class in which it is only required to specify which input arguments the technique takes and which fields it outputs
data.
Inheritance diagram
An inheritance diagram for the instruments and techniques (click the classes to get to their API documentation):
PyExpLabSys.drivers.bio_logic.GeneralPotentiostat PyExpLabSys.drivers.bio_logic.SP150
PyExpLabSys.drivers.bio_logic.CA
PyExpLabSys.drivers.bio_logic.CP
PyExpLabSys.drivers.bio_logic.CV
PyExpLabSys.drivers.bio_logic.Technique PyExpLabSys.drivers.bio_logic.CVA
PyExpLabSys.drivers.bio_logic.MIR
PyExpLabSys.drivers.bio_logic.OCV
PyExpLabSys.drivers.bio_logic.SPEIS
6.1.2 Usage Example
The example below is a complete run-able file demonstrating how to use the module, demonstrated with the OCV
technique.
"""OCV example"""
from __future__ import print_function

import time
from PyExpLabSys.drivers.bio_logic import SP150, OCV
def run_ocv():
"""Test the OCV technique"""
ip_address = '192.168.0.257' # REPLACE THIS WITH A VALID IP
# Instantiate the instrument and connect to it
76 Chapter 6. Hardware Drivers

sp150 = SP150(ip_address)
sp150.connect()
# Instantiate the technique. Make sure to give values for all the
# arguments where the default values does not fit your purpose. The
# default values can be viewed in the API documentation for the
# technique.
ocv = OCV(rest_time_T=0.2,
record_every_dE=10.0,
record_every_dT=0.01)
# Load the technique onto channel 0 of the potentiostat and start it

sp150.load_technique(0, ocv)
sp150.start_channel(0)
time.sleep(0.1)
while True:
# Get the currently available data on channel 0 (only what has
# been gathered since last get_data)
data_out = sp150.get_data(0)
# If there is none, assume the technique has finished

if data_out is None:
break
# The data is available in lists as attributes on the data

# object. The available data fields are listed in the API
# documentation for the technique.
print("Time:", data_out.time)
print("Ewe:", data_out.Ewe)
# If numpy is installed, the data can also be retrieved as

# numpy arrays
#print('Time:', data_out.time_numpy)
#print('Ewe:', data_out.Ewe_numpy)
time.sleep(0.1)
sp150.stop_channel(0)
sp150.disconnect()
if __name__ == '__main__':
run_ocv()
This example covers how most of the techniques would be used. A noticeable exception is the SPEIS technique,
which returns data from two different processes, on two different sets of data fields. It will be necessary to take this
into account, where the data is retrieved along these lines:
while True:
time.sleep(0.1)
data_out = sp150.get_data(0)
if data_out is None:
break
print('Process index', data_out.process)

if data_out.process == 0:
print('time', data_out.time)
print('Ewe', data_out.Ewe)
print('I', data_out.I)
6.1. The bio_logic module 77

print('step', data_out.step)
else:
print('freq', data_out.freq)
print('abs_Ewe', data_out.abs_Ewe)
print('abs_I', data_out.abs_I)
print('Phase_Zwe', data_out.Phase_Zwe)
print('Ewe', data_out.Ewe)
print('I', data_out.I)
print('abs_Ece', data_out.abs_Ece)
print('abs_Ice', data_out.abs_Ice)
print('Phase_Zce', data_out.Phase_Zce)
print('Ece', data_out.Ece)
# Note, no time datafield, but a t
print('t', data_out.t)
print('Irange', data_out.Irange)
print('step', data_out.step)
For more examples of how to use the other techniques, see the integration test file on Github
External documentation
The full documentation for the EC-Lab Development Package is available from the BioLogic website BioLogic Web-
site and locally at CINF on the wiki.
Use/Implement a new potentiostat
To use a potentiostat that has not already been implemented, there are basically two options; implement it (3 lines of
code excluding documentation) or use the GeneralPotentiostat class directly.
6.1.3 Implement a new potentiostat
The SP150 class is implemented in the following manner:
class SP150(GeneralPotentiostat):
"""Specific driver for the SP-150 potentiostat"""
def __init__(self, address, EClib_dll_path=None):

"""Initialize the SP150 potentiostat driver
See the __init__ method for the GeneralPotentiostat class for an

explanation of the arguments.
"""
super(SP150, self).__init__(
type_='KBIO_DEV_SP150',
address=address,
EClib_dll_path=EClib_dll_path
)
As it can be seen, the implementation of a new potentiostat boils down to:

• Inherit from GeneralPotentiostat
• Take address and EClib_dll_path as arguments to __init__

• Call __init__ from GeneralPotentiostat with the potentiostat type string and forward the address
and EClib_dll_path. The complete list of potentiostat type strings are listed in DEVICE_CODES.
6.1.4 Use GeneralPotentionstat
As explained in Implement a new potentiostat, the only thing that is required to use a new potentiostat is to call
GeneralPotentiostat with the appropriate potentiostat type string. As an alternative to implementing the po-
tentiostat in the module, this can of course also be done directly. This example shows e.g. how to get a driver for the
BiStat potentiostat:
from PyExpLabSys.drivers.bio_logic import GeneralPotentiostat
potentiostat = GeneralPotentiostat(
type_='KBIO_DEV_BISTAT',
address='192.168.0.257', # Replace this with a valid IP ;)
EClib_dll_path=None
)
The complete list of potentiostat type strings are listed in DEVICE_CODES.
Use/Implement a new technique
To use a new technique, it will be required to implement it as a new class. This can of course both be done directly
in the module and contributed back upstream or in custom code. The implementation of the OCV technique looks as
follows:
class OCV(Technique):
"""Open Circuit Voltage (OCV) technique class.
The OCV technique returns data on fields (in order):
* time (float)
* Ewe (float)
* Ece (float) (only wmp3 series hardware)
"""
#: Data fields definition

data_fields = {
'vmp3': [DataField('Ewe', c_float), DataField('Ece', c_float)],
'sp300': [DataField('Ewe', c_float)],
}
def __init__(self, rest_time_T=10.0, record_every_dE=10.0,

record_every_dT=0.1, E_range='KBIO_ERANGE_AUTO'):
"""Initialize the OCV technique
Args:
rest_time_t (float): The amount of time to rest (s)
record_every_dE (float): Record every dE (V)
record_every_dT (float): Record evergy dT (s)
E_range (str): A string describing the E range to use, see the
:data:È_RANGES` module variable for possible values
"""
args = (
TechnArg('Rest_time_T', 'single', rest_time_T, '>=', 0),
TechnArg('Record_every_dE', 'single', record_every_dE, '>=', 0),
TechnArg('Record_every_dT', 'single', record_every_dT, '>=', 0),

TechnArg('E_Range', E_RANGES, E_range, 'in', E_RANGES.values()),

)
super(OCV, self).__init__(args, 'ocv.ecc')
As it can be seen, the new technique must inherit from Technique. This base class is responsible for bounds
checking of the arguments and for formatting them in the appropriate way before sending them to the potentiostat.
A class variable with a dict named data_fields must be defined, that describes which data fields the technique
makes data available at. See the docstring for Technique for a complete description of what the contents must be.
In the __init__ method, the technique implementation must reflect all the arguments the specification lists for
the technique (in this module, these arguments are made more Pythonic by; changing the names to follow naming
conventions except that symbols are still capital, infer the number of arguments in lists instead of specifically asking
for them and by leaving out arguments that can only have one value). All of the arguments from the specification must
then be put, in order, into the args tuple in the form the TechniqueArgument instances. The specification for the
arguments for the TechniqueArgument is in its docstring.
Then, finally, Technique.__init__() is called via super, with the args and the technique filename (is listed in
the specification) as arguments.
The last thing to do is to add an entry for the technique in the TECHNIQUE_IDENTIFIERS_TO_CLASS dict,
to indicate where the instrument should look, to figure out what the data layout is, when it receives data from this
technique. If the new technique is implemented in stand alone code, this will need to be hacked (see the attached
example).
In this file is a complete (re)implementation of the OCV technique as it would look if it was developed outside
of the module.
6.1.5 bio_logic API
This module is a Python implementation of a driver around the EC-lib DLL. It can be used to control at least the
SP-150 potentiostat from Bio-Logic under 32 bit Windows.
Note: If it is desired to run this driver and the EC-lab development DLL on Linux, this can be achieved with Wine.
This will require installing both the EC-lab development package AND Python inside Wine. Getting Python installed
is easiest, if it is a 32 bit Wine environment, so before starting, it is recommended to set such an environment up.
NOTE: In a cursory test, it appears that also EClab itself runs under Wine.
Note: When using the different techniques with the EC-lib DLL, different technique files must be passed to the
library, depending on which series the instrument is in (VMPW series or SP-300 series). However, the definition
of which instruments are in which series was not clear from the specification, so instead it was copied from one of the
examples. The definition used is that if the device id of your instrument (see DEVICE_CODES for the full list of device
ids) is in the SP300SERIES list, then it is regarded as a SP-300 series device. If problems are encountered when
loading the technique, then this might be the issues and it will posible be necessary to customize SP300SERIES.
Note: On 64-bit Windows systems, you should use the EClib64.dll instead of the EClib.dll. If the EC-lab
development package is installed in the default location, this driver will try and load the correct DLL automatically, if
not, the DLL path will need to passed explicitely and the user will need to take 32 vs. 64 bit into account. NOTE: The
relevant 32 vs. 64 bit status is that of Windows, not of Python.

Note: All methods mentioned in the documentation are implemented unless mentioned in the list below:
• (General) BL_GetVolumeSerialNumber (Not implemented)
• (Communications) BL_TestCommSpeed (Not implemented)
• (Communications) BL_GetUSBdeviceinfos (Not implemented)
• (Channel information) BL_GetHardConf (N/A, only available w. SP300 series)
• (Channel information) BL_SetHardConf (N/A, only available w. SP300 series)
• (Technique) BL_UpdateParameters (Not implemented)
• (Start stop) BL_StartChannels (Not implemented)
• (Start stop) BL_StopChannels (Not implemented)
• (Data) BL_GetFCTData (Not implemented)
• (Misc) BL_SetExperimentInfos (Not implemented)
• (Misc) BL_GetExperimentInfos (Not implemented)
• (Misc) BL_SendMsg (Not implemented)
• (Misc) BL_LoadFlash (Not implemented)
Instrument classes:
• GeneralPotentiostat
• SP150
Techniques:
• CA
• CP
• CV
• CVA
• MIR
• OCV
• SPEIS
• Technique
class PyExpLabSys.drivers.bio_logic.DataField(name, type)
Bases: tuple
A named tuple used to defined a return data field for a technique
_asdict()
Return a new OrderedDict which maps field names to their values
classmethod _make(iterable, new=<built-in method __new__ of type object at 0x906d60>,
len=<built-in function len>)
Make a new DataField object from a sequence or iterable
_replace(_self, **kwds)
Return a new DataField object replacing specified fields with new values

name
type
class PyExpLabSys.drivers.bio_logic.TechniqueArgument(label, type, value, check,
check_argument)
Bases: tuple
The TechniqueArgument instance, that are used as args arguments, are named tuples with the following fields
(in order):
• label (str): the argument label mentioned in the specification
• type (str): the type used in the specification (‘bool’, ‘single’ and ‘integer’) and possibly wrap [] around
to indicate an array e.g. [bool]`
• value: The value to be passed, will usually be forwarded from __init__ args
• check (str): The bounds check to perform (if any), possible values are ‘>=’, ‘in’ and ‘in_float_range’
• check_argument: The argument(s) for the bounds check. For ‘in’ should be a float or int, for ‘in’ should
be a sequence and for ‘in_float_range’ should be a tuple of two floats
_asdict()
Return a new OrderedDict which maps field names to their values
classmethod _make(iterable, new=<built-in method __new__ of type object at 0x906d60>,
len=<built-in function len>)
Make a new TechniqueArgument object from a sequence or iterable
_replace(_self, **kwds)
Return a new TechniqueArgument object replacing specified fields with new values
check
check_argument
label
type
value
class PyExpLabSys.drivers.bio_logic.GeneralPotentiostat(type_, address,
EClib_dll_path)
Bases: object
General driver for the potentiostats that can be controlled by the EC-lib DLL
A driver for a specific potentiostat type will inherit from this class.
Raises ECLibError – All regular methods in this class use the EC-lib DLL communications li-
brary to talk with the equipment and they will raise this exception if this library reports an error.
It will not be explicitly mentioned in every single method.
__init__(type_, address, EClib_dll_path)
Initialize the potentiostat driver

Parameters
• type (str) – The device type e.g. ‘KBIO_DEV_SP150’
• address (str) – The address of the instrument, either IP address or USB0, USB1 etc
• EClib_dll_path (str) – The path to the EClib DLL. The default directory of the
DLL is C:EC-Lab Development PackageEC-Lab Development Packageand the filename
is either EClib64.dll or EClib.dll depending on whether the operating system is 64 of 32
Windows respectively. If no value is given the default location will be used and the 32/64
bit status inferred.
Raises WindowsError – If the EClib DLL cannot be found
id_number
Return the device id as an int
device_info
Return the device information.
Returns
The device information as a dict or None if the device is not connected.
Return type dict or None
get_lib_version()
Return the version of the EClib communications library.
Returns The version string for the library
Return type str
get_error_message(error_code)
Return the error message corresponding to error_code
Parameters error_code (int) – The error number to translate
Returns The error message corresponding to error_code
Return type str
connect(timeout=5)
Connect to the instrument and return the device info.
Parameters timeout (int) – The connect timeout
Returns
The device information as a dict or None if the device is not connected.
Return type dict or None
Raises ECLibCustomException – If this class does not match the device type
disconnect()
Disconnect from the device
test_connection()
Test the connection
load_firmware(channels, force_reload=False)
Load the library firmware on the specified channels, if it is not already loaded
Parameters

• channels (list) – List with 1 integer per channel (usually 16), (0=False and 1=True),
that indicates which channels the firmware should be loaded on. NOTE: The length of
the list must correspond to the number of channels supported by the equipment, not the
number of channels installed. In most cases it will be 16.
• force_reload (bool) – If True the firmware is forcefully reloaded, even if it was
already loaded
Returns
List of integers indicating the success of loading the firmware on the specified channel. 0
is success and negative values are errors, whose error message can be retrieved with the
get_error_message method.
Return type list
is_channel_plugged(channel)
Test if the selected channel is plugged.
Parameters channel (int) – Selected channel (0-15 on most devices)
Returns Whether the channel is plugged
Return type bool
get_channels_plugged()
Get information about which channels are plugged.
Returns A list of channel plugged statusses as booleans
Return type (list)
get_channel_infos(channel)
Get information about the specified channel.
Parameters channel (int) – Selected channel, zero based (0-15 on most devices)
Returns
Channel infos dict. The dict is created by conversion from ChannelInfos class (type
ctypes.Structure). See the documentation for that class for a list of available dict
items. Besides the items listed, there are extra items for all the original items whose value
can be converted from an integer code to a string. The keys for those values are suffixed
by (translated).
Return type dict
get_message(channel)
Return a message from the firmware of a channel
load_technique(channel, technique, first=True, last=True)
Load a technique on the specified channel
Parameters
• channel (int) – The number of the channel to load the technique onto
• technique (Technique) – The technique to load
• first (bool) – Whether this technique is the first technique
• last (bool) – Thether this technique is the last technique
Raises ECLibError – On errors from the EClib communications library

define_bool_parameter(label, value, index, tecc_param)

Defines a boolean TECCParam for a technique
This is a library convinience function to fill out the TECCParam struct in the correct way for a boolean
value.
Parameters
• label (str) – The label of the parameter
• value (bool) – The boolean value for the parameter
• index (int) – The index of the parameter
• tecc_param (TECCParam) – An TECCParam struct
define_single_parameter(label, value, index, tecc_param)
Defines a single (float) TECCParam for a technique
This is a library convinience function to fill out the TECCParam struct in the correct way for a single (float)
value.
Parameters
• value (float) – The float value for the parameter
define_integer_parameter(label, value, index, tecc_param)
Defines an integer TECCParam for a technique
This is a library convinience function to fill out the TECCParam struct in the correct way for a integer
value.
Parameters
• value (int) – The integer value for the parameter
start_channel(channel)
Start the channel
Parameters channel (int) – The channel number
stop_channel(channel)
Stop the channel
Parameters channel (int) – The channel number
get_current_values(channel)
Get the current values for the spcified channel
Parameters channel (int) – The number of the channel (zero based)
Returns A dict of current values information
Return type dict

get_data(channel)
Get data for the specified channel
Parameters channel (int) – The number of the channel (zero based)
Returns
A KBIOData object or None if no data was available
Return type KBIOData
convert_numeric_into_single(numeric)
Convert a numeric (integer) into a float
The buffer used to get data out of the device consist only of uint32s (most likely to keep its layout simple).
To transfer a float, the EClib library uses a trick, wherein the value of the float is saved as a uint32, by giving
the uint32 the integer values, whose bit-representation corresponds to the float that it should describe. This
function is used to convert the integer back to the corresponding float.
NOTE: This trick can also be performed with ctypes along the lines of: c_float.
from_buffer(c_uint32(numeric)), but in this driver the library version is used.
Parameters numeric (int) – The integer that represents a float
Returns The float value
Return type float
check_eclib_return_code(error_code)
Check a ECLib return code and raise the appropriate exception
class PyExpLabSys.drivers.bio_logic.SP150(address, EClib_dll_path=None)
Bases: PyExpLabSys.drivers.bio_logic.GeneralPotentiostat
Specific driver for the SP-150 potentiostat
__init__(address, EClib_dll_path=None)
Initialize the SP150 potentiostat driver
See the __init__ method for the GeneralPotentiostat class for an explanation of the arguments.
class PyExpLabSys.drivers.bio_logic.KBIOData(c_databuffer, c_data_infos,
c_current_values, instrument)
Bases: object
Class used to represent data obtained with a get_data call
The data can be obtained as lists of floats through attributes on this class. The time is always available through
the ‘time’ attribute. The attribute names for the rest of the data, are the same as their names as listed in the
field_names attribute. E.g:
• kbio_data.Ewe
• kbio_data.I
Provided that numpy is installed, the data can also be obtained as numpy arrays by appending ‘_numpy’ to the
attribute name. E.g:
• kbio_data.Ewe.numpy
• kbio_data.I_numpy
__init__(c_databuffer, c_data_infos, c_current_values, instrument)
Initialize the KBIOData object
Parameters

• c_databuffer (Array of ctypes.c_uint32) – ctypes array of c_uint32 used as the

data buffer
• c_data_infos (DataInfos) – Data information structure
• c_current_values (CurrentValues) – Current values structure
• instrument (GeneralPotentiostat) – Instrument instance, should be an instance
of a subclass of GeneralPotentiostat
Raises ECLibCustomException – Where the error codes indicate the following:
• -20000 means that the technique has no entry in
TECHNIQUE_IDENTIFIERS_TO_CLASS
• -20001 means that the technique class has no data_fields class variable
• -20002 means that the data_fields class variables of the technique does not contain
the right information
_init_data_fields(instrument)
Initialize the data fields property
_parse_data(c_databuffer, timebase, instrument)
Parse the data
Parameters timebase (float) – The timebase for the time calculation
See __init__() for information about remaining args
data_field_names
Return a list of extra data fields names (besides time)
class PyExpLabSys.drivers.bio_logic.Technique(args, technique_filename)
Bases: object
Base class for techniques
All specific technique classes inherits from this class.
Properties available on the object:
• technique_filename (str): The name of the technique filename
• args (tuple): Tuple containing the Python version of the parameters (see __init__() for details)
• c_args (array of TECCParam): The c-types array of TECCParam
A specific technique, that inherits from this class must overwrite the data_fields class variable. It describes
what the form is, of the data that the technique can receive. The variable should be a dict on the following form:
• Some techniques, like OCV , have different data fields depending on the series of the instrument. In these
cases the dict must contain both a ‘wmp3’ and a ‘sp300’ key.
• For cases where the instrument class distinction mentioned above does not exist, like e.g. for CV , one can
simply define a ‘common’ key.
• All three cases above assume that the first field of the returned data is a specially formatted time field,
which must not be listed directly.
• Some techniques, like e.g. SPEIS returns data for two different processes, one of which does not contain
the time field (it is assumed that the process that contains time is 0 and the one that does not is 1). In
this case there must be a ‘common’ and a ‘no-time’ key (see the implementation of SPEIS for details).

All of the entries in the dict must point to an list of DataField named tuples, where the two arguments are
the name and the C type of the field (usually c_float or c_uint32). The list of fields must be in the order
the data fields is specified in the specification.
__init__(args, technique_filename)
Initialize a technique
Parameters
• args (tuple) – Tuple of technique arguments as TechniqueArgument instances
• technique_filename (str) – The name of the technique filename.
Note: This must be the vmp3 series version i.e. name.ecc NOT name4.ecc, the replace-
ment of technique file names are taken care of in load technique
c_args(instrument)
Return the arguments struct
Parameters instrument (GeneralPotentiostat) – Instrument instance, should be an
instance of a subclass of GeneralPotentiostat
Returns An ctypes array of TECCParam
Return type array of TECCParam
Raises ECLibCustomException – Where the error codes indicate the following:
• -10000 means that an TechniqueArgument failed the ‘in’ test
• -10001 means that an TechniqueArgument failed the ‘>=’ test
• -10002 means that an TechniqueArgument failed the ‘in_float_range’ test
• -10010 means that it was not possible to find a conversion function for the defined type
• -10011 means that the value cannot be converted with the conversion function
_init_c_args(instrument)
Initialize the arguments struct
Parameters instrument (GeneralPotentiostat) – Instrument instance, should be an
instance of a subclass of GeneralPotentiostat
static _check_arg(arg)
Perform bounds check on a single argument
class PyExpLabSys.drivers.bio_logic.OCV(rest_time_T=10.0, record_every_dE=10.0,
record_every_dT=0.1,
E_range=’KBIO_ERANGE_AUTO’)
Bases: PyExpLabSys.drivers.bio_logic.Technique
Open Circuit Voltage (OCV) technique class.
The OCV technique returns data on fields (in order):
• time (float)
• Ewe (float)
• Ece (float) (only wmp3 series hardware)
data_fields = {'vmp3': [DataField(name='Ewe', type=<class 'ctypes.c_float'>), DataFiel
Data fields definition

__init__(rest_time_T=10.0, record_every_dE=10.0, record_every_dT=0.1,

E_range=’KBIO_ERANGE_AUTO’)
Initialize the OCV technique
Parameters
• rest_time_t (float) – The amount of time to rest (s)
• record_every_dE (float) – Record every dE (V)
• record_every_dT (float) – Record evergy dT (s)
• E_range (str) – A string describing the E range to use, see the E_RANGES module
variable for possible values
class PyExpLabSys.drivers.bio_logic.CV(vs_initial, voltage_step, scan_rate,
record_every_dE=0.1, aver-
age_over_dE=True, N_cycles=0, be-
gin_measuring_I=0.5, end_measuring_I=1.0,
I_range=’KBIO_IRANGE_AUTO’,
E_range=’KBIO_ERANGE_2_5’, band-
width=’KBIO_BW_5’)
Cyclic Voltammetry (CV) technique class.
The CV technique returns data on fields (in order):
• time (float)
• Ec (float)
• I (float)
• Ewe (float)
• cycle (int)
data_fields = {'common': [DataField(name='Ec', type=<class 'ctypes.c_float'>), DataFie
__init__(vs_initial, voltage_step, scan_rate, record_every_dE=0.1, aver-
age_over_dE=True, N_cycles=0, begin_measuring_I=0.5, end_measuring_I=1.0,
I_range=’KBIO_IRANGE_AUTO’, E_range=’KBIO_ERANGE_2_5’, band-
Initialize the CV technique:
E_we
^
| E_1
| /\
| / \
| / \ E_f
| E_i/ \ /
| \ /
| \/
| E_2
+----------------------> t
Parameters
• vs_initial (list) – List (or tuple) of 5 booleans indicating whether the current step
is vs. the initial one

• voltage_step (list) – List (or tuple) of 5 floats (Ei, E1, E2, Ei, Ef) indicating the
voltage steps (V)
• scan_rate (list) – List (or tuple) of 5 floats indicating the scan rates (mV/s)
• average_over_dE (bool) – Whether averaging should be performed over dE
• N_cycles (int) – The number of cycles
• begin_measuring_I (float) – Begin step accumulation, 1 is 100%
• end_measuring_I (float) – Begin step accumulation, 1 is 100%
• I_Range (str) – A string describing the I range, see the I_RANGES module variable
for possible values
• Bandwidth (str) – A string describing the bandwidth setting, see the BANDWIDTHS
module variable for possible values
Raises ValueError – If vs_initial, voltage_step and scan_rate are not all of length 5
class PyExpLabSys.drivers.bio_logic.CVA(vs_initial_scan, voltage_scan, scan_rate,

vs_initial_step, voltage_step, duration_step,
record_every_dE=0.1, average_over_dE=True,
N_cycles=0, begin_measuring_I=0.5,
end_measuring_I=1.0, record_every_dT=0.1,
record_every_dI=1, trig_on_off=False,
Cyclic Voltammetry Advanced (CVA) technique class.
The CVA technique returns data on fields (in order):
• time (float)
• Ec (float)
• I (float)
• Ewe (float)
• cycle (int)
data_fields = {'common': [DataField(name='Ec', type=<class 'ctypes.c_float'>), DataFie
__init__(vs_initial_scan, voltage_scan, scan_rate, vs_initial_step, voltage_step, duration_step,
record_every_dE=0.1, average_over_dE=True, N_cycles=0, begin_measuring_I=0.5,
end_measuring_I=1.0, record_every_dT=0.1, record_every_dI=1, trig_on_off=False,
Initialize the CVA technique:
E_we
^
| E_1

| /\
| / \
| / \ E_f_____________
| E_i/ \ /<----------->|
| \ / t_f |_______E_i
| \/ |<----->
| E_2 | t_i
+------------------------------+-------------> t
|
trigger
Parameters
• vs_initial_scan (list) – List (or tuple) of 4 booleans indicating whether the cur-
rent scan is vs. the initial one
• voltage_scan (list) – List (or tuple) of 4 floats (Ei, E1, E2, Ef) indicating the voltage
steps (V) (see diagram above)
• scan_rate (list) – List (or tuple) of 4 floats indicating the scan rates (mV/s)
• average_over_dE (bool) – Whether averaging should be performed over dE
• N_cycles (int) – The number of cycles
• begin_measuring_I (float) – Begin step accumulation, 1 is 100%
• end_measuring_I (float) – Begin step accumulation, 1 is 100%
• vs_initial_step (list) – A list (or tuple) of 2 booleans indicating whether this
step is vs. the initial one
• voltage_step (list) – A list (or tuple) of 2 floats indicating the voltage steps (V)
• duration_step (list) – A list (or tuple) of 2 floats indicating the duration of each
step (s)
• record_every_dT (float) – A float indicating the change in time that leads to a
point being recorded (s)
• record_every_dI (float) – A float indicating the change in current that leads to a
point being recorded (A)
• trig_on_off (bool) – A boolean indicating whether to use the trigger
for possible values
Raises ValueError – If vs_initial, voltage_step and scan_rate are not all of length 5

class PyExpLabSys.drivers.bio_logic.CP(current_step=(5e-05, ), vs_initial=(False, ),

duration_step=(10.0, ), record_every_dT=0.1,
record_every_dE=0.001, N_cycles=0,
I_range=’KBIO_IRANGE_100uA’,
Chrono-Potentiometry (CP) technique class.
The CP technique returns data on fields (in order):
• time (float)
• Ewe (float)
• I (float)
• cycle (int)
data_fields = {'common': [DataField(name='Ewe', type=<class 'ctypes.c_float'>), DataFi
__init__(current_step=(5e-05, ), vs_initial=(False, ), duration_step=(10.0, ), record_every_dT=0.1,
record_every_dE=0.001, N_cycles=0, I_range=’KBIO_IRANGE_100uA’,
E_range=’KBIO_ERANGE_2_5’, bandwidth=’KBIO_BW_5’)
Initialize the CP technique
NOTE: The current_step, vs_initial and duration_step must be a list or tuple with the same length.
Parameters
• current_step (list) – List (or tuple) of floats indicating the current steps (A). See
NOTE above.
• vs_initial (list) – List (or tuple) of booleans indicating whether the current steps
is vs. the initial one. See NOTE above.
• duration_step (list) – List (or tuple) of floats indicating the duration of each step
(s). See NOTE above.
• record_every_dT (float) – Record every dT (s)
• N_cycles (int) – The number of times the technique is REPEATED. NOTE: This
means that the default value is 0 which means that the technique will be run once.
for possible values
Raises ValueError – On bad lengths for the list arguments
class PyExpLabSys.drivers.bio_logic.CA(voltage_step=(0.35, ), vs_initial=(False, ), du-
ration_step=(10.0, ), record_every_dT=0.1,
record_every_dI=5e-06, N_cycles=0,

Chrono-Amperometry (CA) technique class.
The CA technique returns data on fields (in order):
• time (float)
• Ewe (float)
• I (float)
• cycle (int)
data_fields = {'common': [DataField(name='Ewe', type=<class 'ctypes.c_float'>), DataFi
__init__(voltage_step=(0.35, ), vs_initial=(False, ), duration_step=(10.0, ), record_every_dT=0.1,
record_every_dI=5e-06, N_cycles=0, I_range=’KBIO_IRANGE_AUTO’,
E_range=’KBIO_ERANGE_2_5’, bandwidth=’KBIO_BW_5’)
Initialize the CA technique
NOTE: The voltage_step, vs_initial and duration_step must be a list or tuple with the same length.
Parameters
• voltage_step (list) – List (or tuple) of floats indicating the voltage steps (A). See
NOTE above.
• vs_initial (list) – List (or tuple) of booleans indicating whether the current steps
is vs. the initial one. See NOTE above.
• duration_step (list) – List (or tuple) of floats indicating the duration of each step
(s). See NOTE above.
• record_every_dI (float) – Record every dI (A)
• N_cycles (int) – The number of times the technique is REPEATED. NOTE: This
means that the default value is 0 which means that the technique will be run once.
for possible values
class PyExpLabSys.drivers.bio_logic.SPEIS(vs_initial, vs_final, initial_voltage_step, fi-
nal_voltage_step, duration_step, step_number,
record_every_dT=0.1, record_every_dI=5e-
06, final_frequency=100000.0, ini-
tial_frequency=100.0, sweep=True, ampli-
tude_voltage=0.1, frequency_number=1,
average_n_times=1, correc-
tion=False, wait_for_steady=1.0,

Staircase Potentio Electrochemical Impedance Spectroscopy (SPEIS) technique class

The SPEIS technique returns data with a different set of fields depending on which process steps it is in. If it is
in process step 0 it returns data on the following fields (in order):
• time (float)
• Ewe (float)
• I (float)
• step (int)
If it is in process 1 it returns data on the following fields:
• freq (float)
• abs_Ewe (float)
• abs_I (float)
• Phase_Zwe (float)
• Ewe (float)
• I (float)
• abs_Ece (float)
• abs_Ice (float)
• Phase_Zce (float)
• Ece (float)
• t (float)
• Irange (float)
• step (float)
Which process it is in, can be checked with the process property on the KBIOData object.
data_fields = {'no_time': [DataField(name='freq', type=<class 'ctypes.c_float'>), Data
__init__(vs_initial, vs_final, initial_voltage_step, final_voltage_step, duration_step,
step_number, record_every_dT=0.1, record_every_dI=5e-06, final_frequency=100000.0,
initial_frequency=100.0, sweep=True, amplitude_voltage=0.1, fre-
quency_number=1, average_n_times=1, correction=False, wait_for_steady=1.0,
Initialize the SPEIS technique
Parameters
• vs_initial (bool) – Whether the voltage step is vs. the initial one
• vs_final (bool) – Whether the voltage step is vs. the final one
• initial_step_voltage (float) – The initial step voltage (V)
• final_step_voltage (float) – The final step voltage (V)
• duration_step (float) – Duration of step (s)
• step_number (int) – The number of voltage steps

• record_every_dI (float) – Record every dI (A)

• final_frequency (float) – The final frequency (Hz)
• initial_frequency (float) – The initial frequency (Hz)
• sweep (bool) – Sweep linear/logarithmic (True for linear points spacing)
• amplitude_voltage (float) – Amplitude of sinus (V)
• frequency_number (int) – The number of frequencies
• average_n_times (int) – The number of repeat times used for frequency averaging
• correction (bool) – Non-stationary correction
• wait_for_steady (float) – The number of periods to wait before each frequency
for possible values
class PyExpLabSys.drivers.bio_logic.MIR(rcmp_value)
Manual IR (MIR) technique class
The MIR technique returns no data.
data_fields = {}
__init__(rcmp_value)
Initialize the MIR technique
Parameters rcmp_value (float) – The R value to compensate
class PyExpLabSys.drivers.bio_logic.DeviceInfos
Bases: _ctypes.Structure
Device information struct
Fields:
• DeviceCode <class ‘ctypes.c_int’>
• RAMsize <class ‘ctypes.c_int’>
• CPU <class ‘ctypes.c_int’>
• NumberOfChannels <class ‘ctypes.c_int’>
• NumberOfSlots <class ‘ctypes.c_int’>
• FirmwareVersion <class ‘ctypes.c_int’>
• FirmwareDate_yyyy <class ‘ctypes.c_int’>
• FirmwareDate_mm <class ‘ctypes.c_int’>
• FirmwareDate_dd <class ‘ctypes.c_int’>

• HTdisplayOn <class ‘ctypes.c_int’>

• NbOfConnectedPC <class ‘ctypes.c_int’>
class PyExpLabSys.drivers.bio_logic.ChannelInfos
Channel information structure
Fields:
• Channel <class ‘ctypes.c_int’>
• BoardVersion <class ‘ctypes.c_int’>
• BoardSerialNumber <class ‘ctypes.c_int’>
• FirmwareCode <class ‘ctypes.c_int’>
• FirmwareVersion <class ‘ctypes.c_int’>
• XilinxVersion <class ‘ctypes.c_int’>
• AmpCode <class ‘ctypes.c_int’>
• NbAmp <class ‘ctypes.c_int’>
• LCboard <class ‘ctypes.c_int’>
• Zboard <class ‘ctypes.c_int’>
• MUXboard <class ‘ctypes.c_int’>
• GPRAboard <class ‘ctypes.c_int’>
• MemSize <class ‘ctypes.c_int’>
• MemFilled <class ‘ctypes.c_int’>
• State <class ‘ctypes.c_int’>
• MaxIRange <class ‘ctypes.c_int’>
• MinIRange <class ‘ctypes.c_int’>
• MaxBandwidth <class ‘ctypes.c_int’>
• NbOfTechniques <class ‘ctypes.c_int’>
class PyExpLabSys.drivers.bio_logic.CurrentValues
Current values structure
Fields:
• State <class ‘ctypes.c_int’>
• MemFilled <class ‘ctypes.c_int’>
• TimeBase <class ‘ctypes.c_float’>
• Ewe <class ‘ctypes.c_float’>
• EweRangeMin <class ‘ctypes.c_float’>
• EweRangeMax <class ‘ctypes.c_float’>
• Ece <class ‘ctypes.c_float’>
• EceRangeMin <class ‘ctypes.c_float’>

• EceRangeMax <class ‘ctypes.c_float’>

• Eoverflow <class ‘ctypes.c_int’>
• I <class ‘ctypes.c_float’>
• IRange <class ‘ctypes.c_int’>
• Ioverflow <class ‘ctypes.c_int’>
• ElapsedTime <class ‘ctypes.c_float’>
• Freq <class ‘ctypes.c_float’>
• Rcomp <class ‘ctypes.c_float’>
• Saturation <class ‘ctypes.c_int’>
class PyExpLabSys.drivers.bio_logic.DataInfos
DataInfos structure
Fields:
• IRQskipped <class ‘ctypes.c_int’>
• NbRaws <class ‘ctypes.c_int’>
• NbCols <class ‘ctypes.c_int’>
• TechniqueIndex <class ‘ctypes.c_int’>
• TechniqueID <class ‘ctypes.c_int’>
• ProcessIndex <class ‘ctypes.c_int’>
• loop <class ‘ctypes.c_int’>
• StartTime <class ‘ctypes.c_double’>
class PyExpLabSys.drivers.bio_logic.TECCParam
Technique parameter
Fields:
• ParamStr <class ‘PyExpLabSys.drivers.bio_logic.c_char_Array_64’>
• ParamType <class ‘ctypes.c_int’>
• ParamVal <class ‘ctypes.c_int’>
• ParamIndex <class ‘ctypes.c_int’>
class PyExpLabSys.drivers.bio_logic.TECCParams
Technique parameters
Fields:
• len <class ‘ctypes.c_int’>
• pParams <class ‘PyExpLabSys.drivers.bio_logic.LP_TECCParam’>

exception PyExpLabSys.drivers.bio_logic.ECLibException(message, error_code)

Base exception for all ECLib exceptions
__init__(message, error_code)
exception PyExpLabSys.drivers.bio_logic.ECLibError(message, error_code)
Bases: PyExpLabSys.drivers.bio_logic.ECLibException
Exception for ECLib errors
exception PyExpLabSys.drivers.bio_logic.ECLibCustomException(message, er-
ror_code)
Bases: PyExpLabSys.drivers.bio_logic.ECLibException
Exceptions that does not originate from the lib
PyExpLabSys.drivers.bio_logic.structure_to_dict(structure)
Convert a ctypes.Structure to a dict
PyExpLabSys.drivers.bio_logic.reverse_dict(dict_)
Reverse the key/value status of a dict
PyExpLabSys.drivers.bio_logic.DEVICE_CODES = {0: 'KBIO_DEV_VMP', 1: 'KBIO_DEV_VMP2', 2:
Device number to device name translation dict
PyExpLabSys.drivers.bio_logic.FIRMWARE_CODES = {0: 'KBIO_FIRM_NONE', 1: 'KBIO_FIRM_INTERP
Firmware number to firmware name translation dict
PyExpLabSys.drivers.bio_logic.AMP_CODES = {0: 'KBIO_AMPL_NONE', 1: 'KBIO_AMPL_2A', 2: 'K
Amplifier number to aplifier name translation dict
PyExpLabSys.drivers.bio_logic.I_RANGES = {0: 'KBIO_IRANGE_100pA', 1: 'KBIO_IRANGE_1nA', 2
I range number to I range name translation dict
PyExpLabSys.drivers.bio_logic.BANDWIDTHS = {1: 'KBIO_BW_1', 2: 'KBIO_BW_2', 3: 'KBIO_BW_
Bandwidth number to bandwidth name translation dict
PyExpLabSys.drivers.bio_logic.E_RANGES = {0: 'KBIO_ERANGE_2_5', 1: 'KBIO_ERANGE_5', 2: '
E range number to E range name translation dict
PyExpLabSys.drivers.bio_logic.STATES = {0: 'KBIO_STATE_STOP', 1: 'KBIO_STATE_RUN', 2: 'K
State number to state name translation dict
PyExpLabSys.drivers.bio_logic.TECHNIQUE_IDENTIFIERS = {0: 'KBIO_TECHID_NONE', 100: 'KBIO_
Technique number to technique name translation dict
PyExpLabSys.drivers.bio_logic.TECHNIQUE_IDENTIFIERS_TO_CLASS = {'KBIO_TECHID_CV': <class 'P
Technique name to technique class translation dict. IMPORTANT. Add newly implemented techniques to this
dictionary
PyExpLabSys.drivers.bio_logic.SP300SERIES = ['KBIO_DEV_SP100', 'KBIO_DEV_SP200', 'KBIO_DEV_
List of devices in the WMP4/SP300 series

6.2 The 4d Systems module
6.2.1 Picaso Common
The 4d Systems module at present contains the Picaso Common driver, which at a minimum works for the Picaso
uLCD-28PTU LCD display, but likely will also work for other displays in the same series.
PyExpLabSys.drivers.four_d_systems.PicasoCommon PyExpLabSys.drivers.four_d_systems.PicasouLCD28PTU
Usage Example
import time
from PyExpLabSys.drivers.four_d_systems import PicasouLCD28PTU
# Text example
picaso = PicasouLCD28PTU(serial_device='/dev/ttyUSB0', baudrate=9600)
picaso.clear_screen()
for index in range(5):
picaso.move_cursor(index, index)
picaso.put_string('CINF')
# Touch example
picaso.move_cursor(7, 0)
picaso.put_string('Try and touch me!')
picaso.touch_set('enable')
for _ in range(25):
time.sleep(0.2)
print picaso.touch_get_status()
print picaso.touch_get_coordinates()
picaso.close()
four_d_systems module
Drivers for the 4d systems displays

For usage examples see the file PyExpLabSys/test/integration_tests/test_four_d_systems.py
Note: Only a small sub-set of the specification is plemented, but with the available examples it should be real easy to
add more commands.
Note: An internal method ‘_to_16_bit_rgb’ exists to convert a HTML hex color code or an RGB tuple of floats to the
irregular 16 bit RGB color scale this device use. It should make working with colors a lot easier.
6.2. The 4d Systems module 99

Note: The displays must be activated for serial communication. At present the only way we know how to do that, is
to follow the procedure described in the serial specification, which involves taking it past a Windows program.
Note: At present only communication via the USB connection has been tested. For communication directly via the
internal connection on the Raspberry Pi it may be necessary to do some preparation in order to free the pins up for
serial communication.
See also:
Docs for this implementation are on the wiki at: https://cinfwiki.fysik.dtu.dk/cinfwiki/Equipment#Picaso_
uLCD-28PTU or online at: http://www.4dsystems.com.au/product/4D_Workshop_4_IDE/downloads
PyExpLabSys.drivers.four_d_systems.to_ascii(string)
Convert non-ascii character in a unicode string to ascii
PyExpLabSys.drivers.four_d_systems.to_ascii_utf8(string)
Convert non-ascii character in a utf-8 encoded string to ascii
class PyExpLabSys.drivers.four_d_systems.PicasoCommon(serial_device=’/dev/ttyUSB0’,
baudrate=9600, de-
bug=False)
Bases: object
Implementation of the common parts of the serial communication to the Picaso devices
Raises serial.serialutil.SerialException - All public methods in this class may raise
this exception if there are problems with the serial communication
__init__(serial_device=’/dev/ttyUSB0’, baudrate=9600, debug=False)
Initialize the driver
The serial device and the baudrate are configurable, as described below. The rest of the serial communi-
cation parameters are; bytesize: 8 bits, parity: None, stopbits: one (as per the manual) and a timeout of 3
seconds.
Parameters
• serial_device (str) – The serial device to open communication on
• baud_rate (int) – The baudrate for the communication
• debug (bool) – Enable a check of whether there are bytes left in waiting after a reply
has been fetched.
close()
Close the serial communication
_send_command(command, reply_length=0)
Send a command and return status and reply
Parameters
• command (str) – The command to send as a hex string e.g. '001B' for 0x001B
• reply_length (int) – The length of the expected reply i.e. WITHOUT an acknowl-
edge
Returns Reply is requested, otherwise None
Return type str

Raises PicasoException – If the command fails or if the reply does not have the requested
length
static _to_16_bit_rgb(color)
Convert a color to the non regular 16 bit RGB.
Parameters
• color (str or tuple) – 24 bit RGB HTML hex string e.g. '#ffffff'
• RGB tuple or floats e.g. `` (or) –
Returns A 2 byte hex string e.g. 'FFFF'
Return type str
static _from_16_bit_rgb(color)
Convert a non regular 16 bit RGB to tuple of float e.g (1.0, 0.0, 1.0)
Parameters color (str) – Color as 16 bit RGB string
Returns Color as tuple of floats e.g. (1.0, 0.0, 1.0)
Return type tuple
move_cursor(line, column)
Move the cursor to line, column and return boolean for success
The actual position in which the cursor is placed is based on the current text parameters such as width and
height
Parameters
• line (int) – The line number to move the cursor to
• column (int) – The column to move the cursor to
Raises PicasoException – If the command fails
put_string(string)
Write a string on the display
Note: It has not been investigated whether characters outside of ASCII can be used. If that becomes
necessary, try, and possibly consult the manual
Parameters string (str) – Ascii string to write, max length 511 chars
Returns The number of bytes written
Return type int
Raises PicasoException – If the command fails or if the reply does not have the expected
length
character_width(character)
Get the width of a character in pixels with the current font
Parameters character (str) – Character to get the width of
Returns The width in pixels
Return type int

length
Raises ValueError - If character does not have length 1
character_height(character)
Get the height of a character in pixels with the current font
Parameters character (str) – Character to get the height of
Returns The height in pixels
Return type int
length
Raises ValueError - If character does not have length 1
text_foreground_color(color)
Sets the foreground color of the text
Parameters color (tuple or string) – 24 bit RGB HTML hex string e.g. ‘#ffffff’ or
RGB tuple or floats e.g. (1.0, 1.0, 1.0)
Returns Previous color as tuple of floats e.g. (1.0, 1.0, 1.0)
Return type tuple
length
text_background_color(color)
Sets the background color of the text
Parameters color (tuple or string) – 24 bit RGB HTML hex string e.g. ‘#ffffff’ or
RGB tuple or floats e.g. (1.0, 1.0, 1.0)
Returns Previous color as tuple of floats e.g. (1.0, 1.0, 1.0)
Return type tuple
length
text_width(factor)
Sets the text width
Parameters factor (int) – Width multiplier (1-16) relative to default width
Returns Previous width multiplier
Return type int
length
text_height(factor)
Sets the text height
Parameters factor (int) – Height multiplier (1-16) relative to default height
Returns Previous height multiplier
Return type int

length
text_factor(factor)
Sets the text width and height
Parameters factor (int) – Width and height multiplier (1-16) relative to default width and
height
Returns Previous width and height multipliers
Return type tuple
length
text_x_gap(pixels)
Sets the horizontal gap between chars in pixels
Parameters pixels (int) – The requested horizontal gap in pixels
Returns The previous horizontal gap in pixels
Return type int
length
text_y_gap(pixels)
Sets the vertical gap between chars in pixels
Parameters pixels (int) – The requested vertical gap in pixels
Returns The previous vertical gap in pixels
Return type int
length
text_attribute(attribute, status=True)
Sets the text attribute status
Parameters
• attribute (str) – The attribute to set, can be one of ‘bold’, ‘inverse’, ‘italic’, ‘opacity’
and ‘underline’ where ‘inverse’ inter changes the back and foreground colors of the text
• status (bool) – Boolean for the text attribute status, where True means ‘on’ or ‘opaque’
in the case of opacity
Returns The previous status
Return type bool
length
Raises ValueError - If attribute is unknown
clear_screen()
Clear the screen
draw_line(start, end, color)
Draw a line from x1, y1 to x2, y2 and return boolean for success

Parameters
• start (tuple) – Start point (x, y), where x and y are ints
• end (tuple) – End point (x, y), where x and y are ints
• color (tuple or string) – 24 bit RGB HTML hex string e.g. ‘#ffffff’ or RGB
tuple or floats e.g. (1.0, 1.0, 1.0)
draw_rectangle(top_left, bottom_right, color)
Draw a rectangle
Parameters
• top_left (tuple) – Coordinates of top left corner (x, y)
• bottom_right (tuple) – Coordinates of bottom right corner (x, y)
draw_filled_rectangle(top_left, bottom_right, color)
Draw a filled rectangle
Parameters
• top_left (tuple) – Coordinates of top left corner (x, y)
• bottom_right (tuple) – Coordinates of bottom right corner (x, y)
move_origin(x, y)
Move the origin to a point, forming the basis for the next graphics or text command
Parameters
• x (int) – X-coordinate for the new origin
• y (int) – Y-coordinate for the new origin
screen_mode(mode)
Sets the screen mode
Parameters mode (str) – The mode for the screen. Can be either 'landscape',
'landscape reverse', 'portrait' or 'portrait reverse'
Returns Returns previous screen mode on success or None on failure
Return type str
length
get_graphics_parameters(parameter)
Gets graphics parameters

Note: The meaning of the results from the 'last_object_*' parameters is not known. It was
expected to be coordinates, but they are much to large
Parameters
• parameter (str) – The parameter to fetch, can be 'x_max' for
• x resolution under the current orientation, 'y_max' for (the)
–
• y resolution under the current orientation, (the) –
• 'last_object_top', ('last_object_left',) –
• 'last_object_bottom' for the relevant ('last_object_right',) –
• for the last object. (parameter) –
Returns The requested parameter
Return type int
length
touch_detect_region(upper_left, bottom_right)
Specify a touch detection region
Parameters
• upper_left (tuple) – (x, y) for the upper left corner, where x and y are ints
• bottom_right (tuple) – (x, y) for the lower right corner, where x and y are ints
touch_set(mode)
Set touch screen related parameters
Parameters
• mode (string) – The mode to set. It can be either 'enable';
• enables and initializes the touch screen, 'disable' (which) –
• disables the touch screen or 'default' which will reset
(which) –
• current active region to the default which is the full
screen (the) –
• area. –
touch_get_status()
Return the state of the touch screen
Returns The state of the touch screen, can be either 'invalid/notouch', 'press',
'release', 'moving' or None on error
Return type str

length
touch_get_coordinates()
Return the coordinates of the LAST touch event
Returns (x, y) where x and y are ints
Return type tuple
length
get_display_model()
Get the display model
Returns The display model
Return type str
length
get_spe_version()
Get the version of the Serial Platform Environment
Returns The version or None on failure
Return type str
length
class PyExpLabSys.drivers.four_d_systems.PicasouLCD28PTU(serial_device=’/dev/ttyUSB0’,
baudrate=9600, de-
bug=False)
Bases: PyExpLabSys.drivers.four_d_systems.PicasoCommon
Driver for the Picaso 28 PTU Pi LCD display
For details on the methods that can be called on this class see the documentation for PicasoCommon
__init__(serial_device=’/dev/ttyUSB0’, baudrate=9600, debug=False)
exception PyExpLabSys.drivers.four_d_systems.PicasoException(message, excep-
tion_type)
Exception for Picaso communication
The exception_type parameter can be either, 'failed' or 'unexpected_reply'
__init__(message, exception_type)
class PyExpLabSys.drivers.four_d_systems.Button(picaso, top_left, bottom_right,
text, text_justify=’center’,
left_justify_indent=None,
text_color=’#000000’, inac-
tive_color=’#B2B2B2’, ac-
tive_color=’#979797’)
Bases: object
Class that represents a button to use in the interface
__init__(picaso, top_left, bottom_right, text, text_justify=’center’, left_justify_indent=None,
text_color=’#000000’, inactive_color=’#B2B2B2’, active_color=’#979797’)

set_position(top_left, bottom_right)
Set position of the button
draw_button(active=False)
Draw button with either its active or inactive background color
6.3 The pfeiffer module
The pfeiffer module contains drivers for equipment from Pfeiffer Vacuum. At present the module contains drivers for
the TPG 261 and TPG 262 pressure measurement and control units.
6.3.1 TPG 26x
The TPG 261 and TPG 262 has the same communications protocol and therefore the driver has been implemented as
a common driver in the TPG26x class, which the TPG261 and TPG262 classes inherit from, as illustrated below.
PyExpLabSys.drivers.pfeiffer.TPG261
PyExpLabSys.drivers.pfeiffer.TPG26x
PyExpLabSys.drivers.pfeiffer.TPG262
The driver implements only a sub set of the specification, but given that the ground work has already been done, it
should be simple to implement more methods as they are needed.
Usage Example
The driver classes can be instantiated by specifying just the address of the serial communications port the unit is
connected to:
from PyExpLabSys.drivers.pfeiffer import TPG262

tpg = TPG262(port='/dev/ttyUSB0')
value, (status_code, status_string) = tpg.pressure_gauge(1)
# or
value, _ = tpg.pressure_gauge(1)
unit = tpg.pressure_unit()
print 'pressure is {} {}'.format(value, unit)
If the baud rate on the TPG 26x unit has been changed away from the default setting of 9600, then the correct baud
rate will need to be given as a parameter.
pfeiffer module
This module contains drivers for the following equipment from Pfeiffer Vacuum:
• TPG 262 and TPG 261 Dual Gauge. Dual-Channel Measurement and Control Unit for Compact Gauges
6.3. The pfeiffer module 107

class PyExpLabSys.drivers.pfeiffer.TPG26x(port=’/dev/ttyUSB0’, baudrate=9600)

Bases: object
Abstract class that implements the common driver for the TPG 261 and TPG 262 dual channel measurement
and control unit. The driver implements the following 6 commands out the 39 in the specification:
• PNR: Program number (firmware version)
• PR[1,2]: Pressure measurement (measurement data) gauge [1, 2]
• PRX: Pressure measurement (measurement data) gauge 1 and 2
• TID: Transmitter identification (gauge identification)
• UNI: Pressure unit
• RST: RS232 test
This class also contains the following class variables, for the specific characters that are used in the communi-
cation:
Variables
• ETX – End text (Ctrl-c), chr(3), \x15
• CR – Carriage return, chr(13), \r
• LF – Line feed, chr(10), \n
• ENQ – Enquiry, chr(5), \x05
• ACK – Acknowledge, chr(6), \x06
• NAK – Negative acknowledge, chr(21), \x15
__init__(port=’/dev/ttyUSB0’, baudrate=9600)
Initialize internal variables and serial connection
Parameters
• port (str or int) – The COM port to open. See the documentation for pyserial for
an explanation of the possible value. The default value is ‘/dev/ttyUSB0’.
• baudrate (int) – 9600, 19200, 38400 where 9600 is the default
program_number()
Return the firmware version
Returns the firmware version
Return type str
pressure_gauge(gauge=1)
Return the pressure measured by gauge X
Parameters gauge (int) – The gauge number, 1 or 2
Raises ValueError – if gauge is not 1 or 2
Returns (value, (status_code, status_message))
Return type tuple
pressure_gauges()
Return the pressures measured by the gauges
Returns (value1, (status_code1, status_message1), value2, (status_code2, status_message2))
Return type tuple

gauge_identification()
Return the gauge identication
Returns (id_code_1, id_1, id_code_2, id_2)
Return type tuple
pressure_unit()
Return the pressure unit
Returns the pressure unit
Return type str
rs232_communication_test()
RS232 communication test
Returns the status of the communication test
Return type bool
class PyExpLabSys.drivers.pfeiffer.TPG262(port=’/dev/ttyUSB0’, baudrate=9600)
Bases: PyExpLabSys.drivers.pfeiffer.TPG26x
Driver for the TPG 262 dual channel measurement and control unit
Parameters
class PyExpLabSys.drivers.pfeiffer.TPG261(port=’/dev/ttyUSB0’, baudrate=9600)
Bases: PyExpLabSys.drivers.pfeiffer.TPG26x
Driver for the TPG 261 dual channel measurement and control unit
Parameters
6.3. The pfeiffer module 109


CHAPTER 7
Hardware Drivers Autogenerated Docs Only
This section documents the hardware drivers developed at CINF. Most of the drivers are for equipment to surface
science such as mass spectrometers and pressure gauges, but there are also some drivers for more general equipment
like temperature read out units.
The drivers in this section only has autogenerated API documentation.
7.1 The NGC2D module
7.1.1 Autogenerated API documentation for NGC2D
7.2 The agilent_34410A module
7.2.1 Autogenerated API documentation for agilent_34410A
Driver class for Agilent 34410A DMM

class PyExpLabSys.drivers.agilent_34410A.Agilent34410ADriver(interface=’lan’,
hostname=”, con-
nection_string=”)
Bases: PyExpLabSys.drivers.scpi.SCPI
Driver for Agilent 34410A DMM
__init__(interface=’lan’, hostname=”, connection_string=”)
config_current_measurement()
Configures the instrument to measure current.
config_resistance_measurement()
Configures the instrument to measure resistance.
111
select_measurement_function(function)
Select a measurement function.
Keyword arguments: Function – A string stating the wanted measurement function.
read_configuration()
Read device configuration
set_auto_input_z(auto=False)
Change internal resitance
read()
Read a value from the device
PyExpLabSys.drivers.agilent_34410A.main()
Main function
7.3 The agilent_34972A module
7.3.1 Autogenerated API documentation for agilent_34972A
Driver class for Agilent 34972A multiplexer

class PyExpLabSys.drivers.agilent_34972A.Agilent34972ADriver(interface=’lan’,
hostname=”, con-
nection_string=”)
Driver for Agilent 34972A multiplexer
__init__(interface=’lan’, hostname=”, connection_string=”)
read_single_scan()
Read a single scan-line
abort_scan()
Abort the scan
read_configuration()
Read device configuration
set_scan_interval(interval)
Set the scan interval
set_integration_time(channel, nplc)
Set integration time
read_scan_interval()
Read the scan interval
read_scan_list()
Return the scan list
set_scan_list(channels)
Set the scan list
112 Chapter 7. Hardware Drivers Autogenerated Docs Only

7.4 The bronkhorst module
7.4.1 Autogenerated API documentation for bronkhorst
Driver for Bronkhorst flow controllers, including simple test case

class PyExpLabSys.drivers.bronkhorst.Bronkhorst(port, max_flow)
Driver for Bronkhorst flow controllers
__init__(port, max_flow)
comm(command)
Send commands to device and recieve reply
read_setpoint()
Read the current setpoint
read_flow()
Read the actual flow
set_flow(setpoint)
Set the desired setpoint, which could be a pressure
read_counter_value()
Read valve counter. Not fully implemented
set_control_mode()
Set the control mode to accept rs232 setpoint
read_serial()
Read the serial number of device
read_unit()
Read the flow unit
read_capacity()
Read ?? from device
7.5 The brooks_s_protocol module
7.5.1 Autogenerated API documentation for brooks_s_protocol
Driver for Brooks s-protocol

class PyExpLabSys.drivers.brooks_s_protocol.Brooks(device, port=’/dev/ttyUSB0’)
Bases: object
Driver for Brooks s-protocol
__init__(device, port=’/dev/ttyUSB0’)
pack(input_string)
Turns a string in packed-ascii format
crc(command)
Calculate crc value of command
comm(command)
Implements low-level details of the s-protocol
7.4. The bronkhorst module 113

read_flow()
Read the current flow-rate
read_full_range()
Report the full range of the device Apparantly this does not work for SLA-series. . .
set_flow(flowrate)
Set the setpoint of the flow
7.6 The cpx400dp module
7.6.1 Autogenerated API documentation for cpx400dp
Driver for CPX400DP power supply

exception PyExpLabSys.drivers.cpx400dp.InterfaceOutOfBoundsError(value)
Error class for CPX400DP Driver
__init__(value)
class PyExpLabSys.drivers.cpx400dp.CPX400DPDriver(output, interface, hostname=”, de-
vice=”, tcp_port=0)
Actual driver for the CPX400DP
__init__(output, interface, hostname=”, device=”, tcp_port=0)
set_voltage(value)
Sets the voltage
set_current_limit(value)
Sets the current limit
read_set_voltage()
Reads the set voltage
read_current_limit()
Reads the current limit
read_configuration_mode()
Return the depency mode between the channels
set_dual_output(dual_output=True)
Sets voltage tracking or dual output If dual_output is True, Dual output will be activated. If dual_output is
False, Voltage tracking will be enabled
read_actual_voltage()
Reads the actual output voltage
read_actual_current()
Reads the actual output current
set_voltage_stepsize(value)
Sets the voltage step size
set_current_stepsize(value)
Sets the current step size

read_voltage_stepsize()
Reads the voltage step size
read_current_stepsize()
Read the current stepszie
increase_voltage()
Increase voltage one step
output_status(output_on=False)
Set the output status
read_output_status()
Read the output status
get_lock()
Lock the instrument for remote operation
7.7 The crowcon module
7.7.1 Autogenerated API documentation for crowcon
This module contains a driver for the Vortex gas alarm central
Copyright 2014 CINF (https://github.com/CINF)
This Vortex driver is part of PyExpLabSys.
PyExpLabSys is free software: you can redistribute it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later
version.
PyExpLabSys is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
Public License for more details.
You should have received a copy of the GNU General Public License along with PyExpLabSys. If not, see <http:
//www.gnu.org/licenses/>.
The documentation for the Vortex is the property of and copyrighted to Crowcon: http://www.crowcon.com/
See also:
Docs for this implementation are on the wiki at: https://cinfwiki.fysik.dtu.dk/cinfwiki/Equipment#Vortex_Gas_
Alarm_System or online at: http://www.crowcon.com/uk/products/control-panels/vortex.html
PyExpLabSys.drivers.crowcon.DetConfMap
alias of DetectorConfigurationMap
PyExpLabSys.drivers.crowcon.DetLev
alias of DetectorLevels
class PyExpLabSys.drivers.crowcon.Status(code, value)
Bases: tuple
code
value
7.7. The crowcon module 115

class PyExpLabSys.drivers.crowcon.Vortex(serial_device, slave_address, debug=False,

cache=True, retries=3)
Bases: minimalmodbus.Instrument
Driver for the Vortex gas alarm central
Note: In the manual the register numbers are 1-based, but when sent to minimal modbus they need to be 0
based.
__init__(serial_device, slave_address, debug=False, cache=True, retries=3)

Initialize the driver
Parameters
• serial_device (str) – The serial device to use
• slave_address (int) – The address of the slave device
• debug (bool) – Whether debugging output from minimal modbus should be enabled
• cache (bool) – Whether system configuration values (which are expected not to change
within the runtime of the program) should be cached
close()
Close the serial communication connection
detector_configuration(detector_number)
Read detector configuration
This value is cached if requested. See docstring for __init__().
Parameters detector_number (int) – The detector number. Detectors numbers are one
based
Returns Named tuple (DetConfMap) containing the detector configuration
Return type DetConfMap
get_detector_levels(detector_number)
Read detector levels
Parameters detector_number (int) – The number of the detector to get the levels of
Returns
DetLev named tuple containing the detector number, detector level, a list of status mes-
sages and a boolean that describes whether the detector is inhibited
Return type namedtuple
get_multiple_detector_levels(detector_numbers)
Get the levels for multiple detectors in one communication call
Parameters detector_numbers (sequence) – Sequence of integer detector numbers (re-
membe they are 1 based)
Warning: This method uses “hidden” functions in the minimal modbus module for value conversion.
As they are hidden, they are not guarantied to preserve their interface, which means that this method
may break at any time

get_number_installed_detectors()
Get the number of installed detector inputs
This value is cached if requested. See docstring for __init__().
Returns The number of installed detectors
Return type int
get_number_installed_digital_outputs()
Get the number of installed digital outputs
Returns The number of installed digital inputs
Return type int
get_serial_number()
Get the serial number
Returns The serial number
Return type str
get_system_name()
Get the serial number
Returns The system name
Return type str
get_system_power_status()
Get the system power status
Returns A Status named tuple containing status code and string
Return type Status
get_system_status()
Get the system status
Returns
[‘All OK’] if no status bits (section 5.1.1 in the manual) has been set, otherwise one
string for each of the status bits that was set.
Return type list
get_type()
Get the device type
Returns The type of the device e.g. ‘Vortex’
Return type str
read_bool(register)
Read int from register and convert to boolean value
0 is considered False, 65535 True and remaining integer values are invalid.
Parameters register (int) – The register to read from
Returns The boolean value
Return type bool
read_register(*args, **kwargs)
Read register from instrument (with retries)
7.7. The crowcon module 117

The argument definition is the same as for the minimalmodbus method, see the full documentation for
read_register for details.
read_string(*args, **kwargs)
Read string from instrument (with retries)
The argument definition is the same as for the minimalmodbus method, see the full documentation
read_string for details.
PyExpLabSys.drivers.crowcon.main()
Main function, used to simple functional test
PyExpLabSys.drivers.crowcon.register_to_bool(register)
Convert a register value to a boolean
0 is considered False, 65535 True and remaining integer values are invalid.
Parameters register (int) – The register value
Returns The boolean value
Return type bool
7.8 The dataq_binary module
7.8.1 Autogenerated API documentation for dataq_binary
DataQ Binary protocol driver

To get started using the one of the supported DataQ data cards, use one of the sub-classes of DataQBinary e.g. DI1110,
set scan list and start:
# Instantiate dataq object

dataq = DI1110('/dev/ttyUSB0')
# Get all available information from the data cards

print(repr(dataq.info()))
# Set sample rate frequence

dataq.sample_rate(1000)
# Set scan list (meaure on channel 1 first, then 0 and finnaly 2)

dataq.scan_list([1, 0, 2])
dataq.clear_buffer()
dataq.start()
sleep(0.1)
from pprint import pprint
try:
while True:
pprint(dataq.read())
sleep(0.5)
dataq.stop()
else:
dataq.stop()
dataq.clear_buffer()

If the data card is being used on the limit of emptying the data buffer before it overflow, it might be useful to put the
calls to read in a try except:
while True:
try:
dataq.read()
except dataq_binary.BufferOverflow:
# Re-start i.e. stop and start
or, to simple start and stop the card for a short amount of time, if slow measurements, which would otherwise fill
buffer are required:
while True:
dataq.start()
sleep(0.1)
dataq.read()
dataq.stop()
# We really only need to measure every 10s
sleep(10)
On some Linux system, at the end of 2017, some models, e.g. the DI-1110 wasn’t automatically mounted. In that
case, it can be manually mounted with a command like this one:
sudo modprobe usbserial vendor=0x0683 product=0x1110
On should be possible, on Debian based Linux systems to add an automatic mount rule along the lines of this thread:
https://askubuntu.com/questions/525016/cant-open-port-dev-ttyusb0
So, add a new udev rule /etc/udev/rules.d/99-dataq_di1110.rules
with this content:
# /etc/udev/rules.d/99-dataq_di1110.rules
# contains DataQ DI-1110 udev rule to patch default
# rules
SYSFS{idProduct}=="1110",
SYSFS{idVendor}=="0683",
RUN+="/sbin/modprobe -q usbserial product=0x1110 vendor=0x0683"
and aftwerwards run: sudo udevadm control –reload-rules

exception PyExpLabSys.drivers.dataq_binary.BufferOverflow
Custom exception to indicate a buffer overflow
class PyExpLabSys.drivers.dataq_binary.DataQBinary(device, serial_kwargs=None)
Bases: object
Base class for DataQBinary driver
end_char = '\r'
Serial communication end character
read_wait_time = 0.001
Wait time between serial write and read
infos = {'device name': 1, 'serial number': 6, 'vendor': 0, 'sample rate divisor':
Information items that can be retrieved along with their code number
7.8. The dataq_binary module 119

led_colors = {'blue': 1, 'black': 0, 'yellow': 6, 'cyan': 3, 'green': 2, 'magenta'

Supported LED colors along with the code number
buffer_overflow_size = 4095
Buffer overflow size, may be overwritte in sub classes
packet_sizes = {16: 0, 32: 1, 512: 5, 64: 2, 128: 3, 2048: 7, 256: 4, 1024: 6}
Packet sizes and code numbers
__init__(device, serial_kwargs=None)
Initialize local variables
Parameters
• device (str) – The device e.g: ‘/dev/ttyUSB0’ of ‘COM1’
• serial_kwargs (dict) – dict of keyword arguments for serial.Serial
clear_buffer()
Clear the buffer
info(info_name=’all’)
Return information about the device
Parameters info_name (str) – Name of the requested information item(s). If info_name is
one the specific info names, (the keys in DataQBinary.infos), a string will be returned with
the value. If info_name is ‘all’, all values will be returned in a dict
Returns Information items
Return type str or dict
start()
Start data acquisition
stop()
Stop data acquisition
This also implies clearing the buffer of any remaining data
scan_list(scan_list)
Set the scan list
The scan list is the list of inputs to acquire from on the data card. The scan list can hold up to 11 items,
since there are a total on 11 inputs and each element can only be there once. The analogue input channel are
numbered 0-7, 8 is the counter channel, 9 is the rate channel and 10 is the general purpose input channel.
0.7 are specified only by their number, 8, 9 and 10 are configured specially, which is not described here
yet.
Parameters scan_list (list) – Etc. [3, 5, 0] for analogue input chanel 3, 5 and 0. NOTE:
The numbers are integers, not strings.
sample_rate(rate)
Set the sample rate
The value values are calculated as being in the range of
sample rate divisor / 375 to sample rate divisor / 65535
So e.g. for the DI-1110 product, with a sample rate divisor of 60,000,000, the valid inputs are in range
from 915.5413 to 160000.
Parameters rate (float) – The sample rate given in number of elements in the scan list
sampled per second (i.e. in Hz). Valid values depend on the model and is given by the

“sample rate divisor” information item (see the info method). See information about how to
calculate the valid input range above.
packet_size(size)
Set the packet size
The packet size is he amount of data acquired before it is placed in the read buffer. The available packet
sizes are the keys in packet_sizes class variable.
Parameters size (int) – The requested packet size
led_color(color)
Set the LED color
Parameters color (str) – The available colors are the keys in the led_colors class variable
read()
Read all values waiting
This method reads all available damples from the data card and returns for every channel the mean of those
samples.
The returned data is on the form of a list with one item for each item in the scan list and in the same
order. Each of the items is in them selves a dict, which holds the mean value of the samples, the number
of samples in the mean, the channel number (0-based) and information about how full the data buffer was,
at the time when it was read out. An example could be:
[{'buffer_status': '3040/4095 bytes',

'channel': 1,
'samples': 506,
'value': -1.6224543756175889},
{'buffer_status': '3040/4095 bytes',
'channel': 0,
'samples': 507,
'value': -0.0044494267751479287},
{'buffer_status': '3040/4095 bytes',
'channel': 2,
'samples': 507,
'value': 1.6192735299556213}]
where the scan list was set to [1, 0, 2].

Returns
A list of values for each of the items in the scan-list and in the same order. For details of
returns values see above.
Return type list
Raises BufferOverflow – If the buffer was full at the time of reading. The behavior in this
case is ill-defined, so it is better to re-start the measurement if that happens.
class PyExpLabSys.drivers.dataq_binary.DI1110(device, serial_kwargs=None)
Bases: PyExpLabSys.drivers.dataq_binary.DataQBinary
FIXME
PyExpLabSys.drivers.dataq_binary.module_test()
Run primitive module tests
7.8. The dataq_binary module 121

7.9 The dataq_comm module
7.9.1 Autogenerated API documentation for dataq_comm
Driver for DATAQ dac units

class PyExpLabSys.drivers.dataq_comm.DataQ(port)
Bases: object
driver for the DataQ Instrument
__init__(port)
comm(command)
comm function
dataq()
Returns the string DATAQ
device_name()
Returns device name
firmware()
Returns firmware version
serial_number()
Returns device serial number
start_measurement()
Start a measurement scan
read_measurements()
Read the newest measurents
stop_measurement()
Stop a measurement scan
add_channel(channel)
Adds a channel to scan slist. So far only analog channels are accepted
set_ascii_mode()
change response mode to ACSII
set_float_mode()
change response mode to float
reset_scan_list()
Reseting the scan list
7.10 The edwards_agc module
7.10.1 Autogenerated API documentation for edwards_agc
Driver and simple test case for Edwards Active Gauge Controler
class PyExpLabSys.drivers.edwards_agc.EdwardsAGC(port=’/dev/ttyUSB0’)
Bases: object
Primitive driver for Edwards Active Gauge Controler Complete manual found at http://www.idealvac.com/files/
brochures/Edwards_AGC_D386-52-880_IssueM.pdf

__init__(port=’/dev/ttyUSB0’)
comm(command)
Implements basic communication
gauge_type(gauge_number)
Return the type of gauge
read_pressure(gauge_number)
Read the pressure of a gauge
pressure_unit(gauge_number)
Read the unit of a gauge
current_error()
Read the current error code
software_version()
Return the software version of the controller
7.11 The edwards_nxds module
7.11.1 Autogenerated API documentation for edwards_nxds
Driver for Edwards, nXDS pumps

class PyExpLabSys.drivers.edwards_nxds.EdwardsNxds(port)
Bases: object
Driver for the Edwards nXDS series of dry pumps
__init__(port)
comm(command)
Ensures correct protocol for instrument
read_pump_type()
Read identification information
read_pump_temperature()
Read Pump Temperature
read_serial_numbers()
Read Pump Serial numbers
read_run_hours()
Return number of run hours
set_run_state(on_state)
Start or stop the pump
status_to_bin(word)
Convert status word to array of binaries
bearing_service()
Status of bearings
pump_controller_status()
Read the status of the pump controller
7.11. The edwards_nxds module 123

read_normal_speed_threshold()
Read the value for acknowledge the pump as normally running
read_standby_speed()
Read the procentage of full speed on standby
read_pump_status()
Read the overall status of the pump
read_service_status()
Read the overall status of the pump
set_standby_mode(standbymode)
Set the pump on or off standby mode
7.12 The epimax module
7.12.1 Autogenerated API documentation for epimax
Driver for the Epimax PVCi process vacuum controller

There are three controllers share the same kind of communication:
• PVCX
• PVCi
• PVCiDuo
The structure of the communication to these devices is the same and a part of the parameters are also the same, but
there are also some parameters that differ. Therefore, the driver is implemented in such a way, that there is a base
class (PVCCommon) that contains the communication functionality and the parameter from the common parameter
definition. There can then be one class for each of the 3 specific devices, that adds in the parameters that are specific
to this device. To see how that works, look at the PVCi class.
The implementation in this file is based on the documents:
• “EMComm MODBUS Communications Handbook” version 3.10
• “PVCX, PVCi & PVCiDuo EMComm Parameter List Handbook” version 3.00 (hereafter referred to as the
parameter list)
Unfortunately, these documents are not (that I could find) available on the web and must be fetched by emailing
Epimax support.
Note: At present only the PVCi driver is implemented and only partially
Note: At present no writing is implemented
class PyExpLabSys.drivers.epimax.PVCCommon(port, slave_address=1,

check_hardware_version=True)
Bases: minimalmodbus.Instrument
Common base for the PVCX, PVCi and PVCiDuo devices
This common class must be sub-classed and the global_id and firmware_name class variables overwritten and
the self.fields dict updated if necessary. See the PVCi inplementation for details.

All requests for values (parameters) goes via value field names. To get a list of the available fields, have a look
at the keys in the fields dict of the common class and the sub-class. These fields names can then be used with
get_field() and get_fields() method or accessed as if they were attributes of the class.
Remember to call .close() after use.
__init__(port, slave_address=1, check_hardware_version=True)
Initialize communication
Parameters
• port (unicode) – The port specification of the device e.g. ‘/dev/????’
• slave_address (int) – The address of the slave device, default is 1
• check_hardware_version (bool) – Indicated whether a check should be per-
formed for correct hardware at __init__ time
close()
Close the serial connection
get_field(field_name)
Return the value for the field named field_name
Parameters field_name (str) – The name of the field to get. The names used are adapted
parameter names from the command list turned. See the keys in fields to see all possible
values.
Returns An object with type corresponding to the value (int, float or str)
Return type object
Raises KeyError – If the requested field_name is unknown
get_fields(fields=’common’)
Return a dict with fields and values for a list of fields
This method is specifically for getting multiple values in the shortest amount of time. It works by al-
ways reading the maximum amount of registers (32) at a time and then using the remaining payload for
subsequent values if they happen to be contained in the registers that have already been read.
Parameters fields (sequence or unicode) – A sequence (list, tuple) of fields names or
‘common’ which indicates fields with an address between 0x80 and 0x9E (this is the default)
or ‘all’.
Returns Field name to value mapping
Return type dict
class PyExpLabSys.drivers.epimax.PVCi(*args, **kwargs)
Bases: PyExpLabSys.drivers.epimax.PVCCommon
Driver for the PVCi device
For details of the functionality of this driver, see the docstring for the common base class PVCCommon
__init__(*args, **kwargs)
For specification for __init__ arguments, see PVCCommon.__init__()
PyExpLabSys.drivers.epimax.bytes_to_firmware_version(bytes_)
Convert 4 bytes to firmware type and version
PyExpLabSys.drivers.epimax.bytes_to_string(bytes_, valid_chars=None)
Convert the 16 bit integer values from registers to a string
7.12. The epimax module 125

Parameters valid_chars (sequence) – Sequence of two integers indicating the start and end
of a range of valid bytes (both values included). All chars outside the range will be filtered out.
PyExpLabSys.drivers.epimax.bytes_to_float(bytes_)
Convert 2 16 bit registers to a float
PyExpLabSys.drivers.epimax.bytes_to_slot_id(bytes_)
Convert 4 bytes to the slot ID
PyExpLabSys.drivers.epimax.bytes_to_status(bytes_, status_type)
Convert bytes to trip and digital input statuses
PyExpLabSys.drivers.epimax.byte_to_bits(byte)
Convert a byte to a list of bits
PyExpLabSys.drivers.epimax.raise_if_not_set(bits, index, parameter)
Raise a ValueError if bit is not set
PyExpLabSys.drivers.epimax.ion_gauge_status(bytes_, controller_type=None)
Read of ion gauge status
PyExpLabSys.drivers.epimax.bytes_to_bakeout_flags(bytes_)
Returns the bakeout flags from bytes
PyExpLabSys.drivers.epimax.run_module()
Tests basic functionality
Will init a PVCi on USB0 and out all info fields and gauge 1 pressure and bakeout info continuously
7.13 The freescale_mma7660fc module
7.13.1 Autogenerated API documentation for freescale_mma7660fc
Driver for AIS328DQTR 3 axis accelerometer

class PyExpLabSys.drivers.freescale_mma7660fc.MMA7660FC
Bases: object
Class for reading accelerometer output
__init__()
read_values()
Read a value from the sensor
7.14 The fug module
7.14.1 Autogenerated API documentation for fug
Driver for “fug NTN 140 - 6,5 17965-01-01” power supply Communication via the Probus V serial interface.
Written using the two documents:
1. Interface system Probus V - Documentation for RS232/RS422 Revision of document 2.4
2. Probus V - Command Reference Base Module ADDAT30 Firmware PIC0162 V4.0 Version of Document V2.22
Should be freely available from http://www.fug-elektronik.de/en/support/download.html (Available August 25 2017)

class PyExpLabSys.drivers.fug.FUGNTN140Driver(port=’/dev/ttyUSB0’, baudrate=9600,

parity=’N’, stopbits=1, bytesize=8,
device_reset=True)
Bases: object
Driver for fug NTN 140 power supply
Methods
• Private
– __init__
– _check_answer
– _flush_answer
– _get_answer
– _write_register
– _read_register
• Public
– reset()
– stop()
– is_on()
– output(state=True/False)
– get_state()
– identification_string()
– —
– set_voltage(value)
– get_voltage()
– monitor_voltage()
– ramp_voltage(value, program=0)
– ramp_voltage_running()
– —
– set_current(value)
– get_current()
– monitor_current()
– ramp_current(value, program=0)
– ramp_current_running()
__init__(port=’/dev/ttyUSB0’, baudrate=9600, parity=’N’, stopbits=1, bytesize=8, de-
vice_reset=True)
Initialize object variables
For settings port, baudrate, parity, stopbits, bytesize, see the pyserial documentation.
Parameters device_reset (bool) – If true, resets all device parameters to default values
7.14. The fug module 127

reset()
Resets device
stop(reset=True)
Closes device properly before exit
is_on()
Checks if output is ON (>DON) Returns True if ON
output(state=False)
Set output ON (>BON)
get_state()
Checks whether unit is in CV or CC mode (>DVR/>DIR)
identification_string()
Output serial number of device
set_voltage(value)
Sets the voltage (>S0)
get_voltage()
Reads the set point voltage (>S0A)
monitor_voltage()
Reads the actual (monitor) voltage (>M0)
ramp_voltage(value, program=0)
Activates ramp function for voltage value : ramp value in volts/second (>S0R)
pro- setvalue behaviour

gram
0 (default) no ramp function. Setpoint is implemented immediately
1 >S0A follows the value in >S0 with the adjusted ramp rate upwards and downwards
2 >S0A follows the value in >S0 with the adjusted ramp rate only upwards. When programming
downwards, >S0A follows >S0 immediately.
3 >S0A follows the value in >S0 with a special ramp function only upwards. When programming
downwards, >S0A follows >S0 immediately. Ramp between 0..1 with 11.11E-3 per second.
Above 1 : with >S0R
4 Same as 2, but >S0 as well as >S0A are set to zero if >DON is 0
ramp_voltage_running()
Return status of voltage ramp. True: still ramping False: ramp complete
set_current(value)
Sets the current (>S1)
get_current()
Reads the set point current (>S1A)
monitor_current()
Reads the actual (monitor) current (>M1)
ramp_current(value, program=0)
Activates ramp function for current. See ramp_voltage() for description.
ramp_current_running()
Return status of current ramp. True: still ramping False: ramp complete
read_H1()
Read H1 FIXME not yet done

print_states(t0=0)
Print the current state of the power supply
PyExpLabSys.drivers.fug.test()
Module test function
7.15 The galaxy_3500 module
7.15.1 Autogenerated API documentation for galaxy_3500
Python interface for Galaxy 3500 UPS. The driver uses the telnet interface of the device.
class PyExpLabSys.drivers.galaxy_3500.Galaxy3500(hostname)
Bases: object
Interface driver for a Galaxy3500 UPS.
__init__(hostname)
comm(command, keywords=None)
Send a command to the ups
alarms()
Return list of active alarms
battery_charge()
Return the battery charge state
temperature()
Return the temperature of the UPS
battery_status()
Return the battery voltage
output_measurements()
Return status of the device’s output
input_measurements()
Return status of the device’s output
7.16 The honeywell_6000 module
7.16.1 Autogenerated API documentation for honeywell_6000
Driver for HIH6000 class temperature and humidity sensors

class PyExpLabSys.drivers.honeywell_6000.HIH6130
Bases: object
Class for reading pressure and temperature from Honeywell HumidIcon HIH-6130/6131
__init__()
read_values()
7.15. The galaxy_3500 module 129

7.17 The inficon_sqm160 module
7.17.1 Autogenerated API documentation for inficon_sqm160
Driver for Inficon SQM160 QCM controller

class PyExpLabSys.drivers.inficon_sqm160.InficonSQM160(port=’/dev/ttyUSB0’)
Bases: object
Driver for Inficon SQM160 QCM controller
comm(command)
Implements actual communication with device
static crc_calc(input_string)
Calculate crc value of command
show_version()
Read the firmware version
show_film_parameters()
Read the film paramters
rate(channel=1)
Return the deposition rate
thickness(channel=1)
Return the film thickness
frequency(channel=1)
Return the frequency of the crystal
crystal_life(channel=1)
Read crystal life
7.18 The innova module
7.18.1 Autogenerated API documentation for innova
Driver for the Innova RT 6K UPS

Implemented from this document: http://networkupstools.org/protocols/megatec.htmlL
PyExpLabSys.drivers.innova.STATUS_INQUIRY_NAMES = ['input_voltage', 'input_fault_voltage',
The first 7 places of the response to the status inquiry are numbers, who are paired with the names in the list
below
PyExpLabSys.drivers.innova.STATUS_INQUIRY_BOOLEANS = ['utility_fail_immediate', 'battery_lo
The last section of the response to the status inquiry are 0’s and 1’s, which indicate the boolean status of the
fields listed below.
PyExpLabSys.drivers.innova.RATING_INFORMATION_FIELDS = ['rating_voltage', 'rating_current',
The names for the floats returned as section from the rating information command
class PyExpLabSys.drivers.innova.Megatec(device, baudrate=2400, timeout=2.0)
Bases: object
Driver that implements parts of the Megatech specification

__init__(device, baudrate=2400, timeout=2.0)

com(command)
Perform communication
get_status()
Return the status as a dict
The values in the dict are either float or booleans. The keys for the float values are:
• output_voltage
• input_voltage
• temperature_C
• input_frequency
• battery_voltage
• output_current_load_percent
• input_fault_voltage
The keys for the boolean values are:
• utility_fail_immediate
• battery_low
• bypass_boost_or_buck_active
• UPS_failed
• UPS_type_is_standby
• test_in_progress
• shutdown_active
• beeper_on
test_for_10_sec()
Run a test of the batteries for 10 sec and return to utility
ups_information()
Return the UPS information
ups_rating_information()
Return the UPS rating information as a dict
The dict contains float valus for the following 4 fields:
• battery_voltage
• frequency
• rating_current
• rating_voltage
class PyExpLabSys.drivers.innova.InnovaRT6K(device, baudrate=2400, timeout=2.0)
Bases: PyExpLabSys.drivers.innova.Megatec
for the InnovaRT6k UPS
7.18. The innova module 131

7.19 The intellemetrics_il800 module
7.19.1 Autogenerated API documentation for intellemetrics_il800
Driver for IL800 deposition controller

class PyExpLabSys.drivers.intellemetrics_il800.IL800(port)
Bases: object
Driver for IL800 depostition controller
__init__(port)
comm(command)
Communicate with instrument
rate()
Return the deposition rate in nm/s
thickness()
Return the currently measured thickness in nm
frequency()
Return the qrystal frequency in Hz
7.20 The isotech_ips module
7.20.1 Autogenerated API documentation for isotech_ips
Driver for ISO-TECH IPS power supply series

It has not been possible to get the device to give any meaningfull replys, but actually setting output values works.
class PyExpLabSys.drivers.isotech_ips.IPS(port)
Bases: object
Driver for IPS power supply
__init__(port)
comm(command)
Communicate with instrument
set_vlimit_to_max()
Set the voltage limit to the maximum the device deliver
set_ilimit_to_max()
Set the current limit to the maximum the device deliver
set_relay_status(status=False)
Turn the output on or off
set_output_voltage(voltage)
Set the output voltage
set_voltage_limit(voltage)
Set the voltage limit
set_current_limit(current)
Set the current limit

7.21 The keithley_2700 module
7.21.1 Autogenerated API documentation for keithley_2700
Simple driver for Keithley Model 2700

class PyExpLabSys.drivers.keithley_2700.KeithleySMU(interface, de-
vice=’/dev/ttyUSB0’)
Simple driver for Keithley Model 2700
__init__(interface, device=’/dev/ttyUSB0’)
select_measurement_function(function)
Select a measurement function.
Keyword arguments: Function – A string stating the wanted measurement function.
read()
Read a value from the device
7.22 The keithley_smu module
7.22.1 Autogenerated API documentation for keithley_smu
Simple driver for Keithley SMU

class PyExpLabSys.drivers.keithley_smu.KeithleySMU(interface, hostname=”, device=”,
baudrate=9600)
Simple driver for Keithley SMU
__init__(interface, hostname=”, device=”, baudrate=9600)
output_state(output_on=False, channel=1)
Turn the output on or off
set_current_measure_range(current_range=None, channel=1)
Set the current measurement range
set_integration_time(nplc=None, channel=1)
Set the measurement integration time
read_current(channel=1)
Read the measured current
read_voltage(channel=1)
Read the measured voltage
set_current_limit(current, channel=1)
Set the desired current limit
set_voltage(voltage, channel=1)
Set the desired voltage
set_voltage_limit(voltage, channel=1)
Set the desired voltate limit
7.21. The keithley_2700 module 133

set_current(current, channel=1)
Set the desired current
iv_scan(v_from, v_to, steps, settle_time, channel=1)
Perform iv_scan
7.23 The kjlc_pressure_gauge module
7.23.1 Autogenerated API documentation for kjlc_pressure_gauge
Module contains driver for KJLC 3000 pressure gauge

class PyExpLabSys.drivers.kjlc_pressure_gauge.KJLC300(port)
Bases: object
Class implements a KJLC interface
__init__(port)
close()
Closes connection
read_software_version()
Reads software version
read_pressure()
Reads pressure in Torr
7.24 The lascar module
7.24.1 Autogenerated API documentation for lascar
Driver for the EL-USB-RT temperature and humidity USB device from Lascar
Calling read on the device will return either the temperature or the humidity.
If the first byte is it is a temperature. The next 2 bytes is a unsigned integer which, is used to calculate the temperature
as:
temp = -100 * 0.1 * (unsigned_short)
If the first byte is it is humidity. The next byte is an unsigned char, which is used to calculate the relative humidity as:
humidity = 0.5 * (unsigned_char)
class PyExpLabSys.drivers.lascar.ElUsbRt(device_path=None)
Bases: object
Driver for the EL-USB-RT device
__init__(device_path=None)
get_temperature_and_humidity()
Returns the temperature (in celcius, float) and relative humidity (in %, float) in a dict
get_temperature()
Returns the temperature (in celcius, float)

7.25 The mks_925_pirani module
7.25.1 Autogenerated API documentation for mks_925_pirani
Driver for MKS 925 micro pirani

class PyExpLabSys.drivers.mks_925_pirani.Mks925(port)
Bases: object
Driver for MKS 925 micro pirani
__init__(port)
comm(command)
Implement communication protocol
read_pressure()
Read the pressure from the device
set_comm_speed(speed)
Change the baud rate
change_unit(unit)
Change the unit of the return value
read_serial()
Read the serial number of the device
7.26 The mks_937b module
7.26.1 Autogenerated API documentation for mks_937b
Driver for MKS 937b gauge controller

class PyExpLabSys.drivers.mks_937b.Mks937b(port)
Bases: object
Driver for MKS 937B Gauge Controller
__init__(port)
comm(command)
Implement communication protocol
read_pressure_gauge(gauge_number)
Read a specific pressure gauge
read_sensor_types()
Return a list of connected sensors
read_all_pressures()
Returns an overview of all sensors
pressure_unit(unit=None)
Read or configure pressure unit Legal values: torr, mbar, pascal, micron
7.25. The mks_925_pirani module 135

7.27 The mks_g_series module
7.27.1 Autogenerated API documentation for mks_g_series
Driver for MKS g-series flow controller

class PyExpLabSys.drivers.mks_g_series.MksGSeries(port=’/dev/ttyUSB0’)
Driver for G-series flow controllers from MKS
checksum(command)
Calculate checksum of command
comm(command, addr)
Implements communication protocol
read_full_scale_range(addr)
Read back the current full scale range from the instrument
read_device_address(address=254)
Read the device address
set_device_address(old_addr, new_addr)
Set the device address
read_current_gas_type(addr)
Read the current default gas type
read_run_hours(addr)
Return number of running hours of mfc
read_setpoint(addr)
Read current setpoint
set_flow(value, addr=254)
Set the flow setpoint
read_flow(addr=254)
Read the flow
read_serial_number(addr=254)
Read the serial number of the device
7.28 The mks_pi_pc module
7.28.1 Autogenerated API documentation for mks_pi_pc
7.29 The omega_D6400 module
7.29.1 Autogenerated API documentation for omega_D6400
Driver for Omega D6400 daq card

class PyExpLabSys.drivers.omega_D6400.OmegaD6400(address=1, port=’/dev/ttyUSB0’)
Bases: object

Driver for Omega D6400 daq card

__init__(address=1, port=’/dev/ttyUSB0’)
comm(command, value=None)
Communicates with the device
read_value(channel)
Read a measurement value from a channel
read_address(new_address=None)
Read the RS485 address of the device
write_enable()
Enable changes to setup values
range_codes(fullrange=0, action=None)
Returns the code corresponding to a given range
update_range_and_function(channel, fullrange=None, action=None)
Set the range and measurement type for a channel
7.30 The omega_cn7800 module
7.30.1 Autogenerated API documentation for omega_cn7800
Omega CN7800 Modbus driver. Might also work with other CN units
class PyExpLabSys.drivers.omega_cn7800.CN7800(port)
Bases: object
Driver for the omega CN7800
__init__(port)
read_temperature()
Read the temperature from the device
7.31 The omega_cni module
7.31.1 Autogenerated API documentation for omega_cni
This module contains drivers for equipment from Omega. Specifically it contains a driver for the ??? thermo couple
read out unit.
class PyExpLabSys.drivers.omega_cni.ISeries(port, baudrate=19200,
comm_stnd=’rs232’)
Bases: object
Driver for the iSeries omega temperature controllers
__init__(port, baudrate=19200, comm_stnd=’rs232’)
Initialize internal parameters
Parameters port – A serial port designation as understood by pySerial
command(command, response_length=None, address=None)
Run a command and return the result
7.30. The omega_cn7800 module 137

Parameters
• command (str) – The command to execute
• response_length (int) – The expected legth of the response. Will force the driver
to wait untill this many characters is ready as a response from the device.
reset_device(address=None)
Reset the device
identify_device(address=None)
Return the identity of the device
read_temperature(address=None)
Return the temperature
close()
Close the connection to the device
class PyExpLabSys.drivers.omega_cni.CNi3244_C24(port)
Bases: PyExpLabSys.drivers.omega_cni.ISeries
Driver for the CNi3244_C24 device
__init__(port)
Initialize internal parameters
Parameters port – A serial port designation as understood by pySerial
7.32 The omegabus module
7.32.1 Autogenerated API documentation for omegabus
Driver for OmegaBus devices

class PyExpLabSys.drivers.omegabus.OmegaBus(device=’/dev/ttyUSB0’, model=’D5251’,
baud=300)
Bases: object
Driver for OmegaBus devices
__init__(device=’/dev/ttyUSB0’, model=’D5251’, baud=300)
comm(command)
Handles serial protocol
read_value(channel, convert_to_celcius=True)
Read the measurement value
read_max(channel)
The maximum read-out value
read_min(channel)
The minimum read-out value
read_setup()
Read Device setup information

7.33 The omron_d6fph module
7.33.1 Autogenerated API documentation for omron_d6fph
Hint for implementation found at http://forum.arduino.cc/index.php?topic=285116.0

class PyExpLabSys.drivers.omron_d6fph.OmronD6fph
Bases: object
Class for reading pressure and temperature from Omron D6F-PH series Ranging not implemented for all models
__init__()
init_device()
Sensor needs to be initiated after power up
read_value(command)
read_pressure()
Read the pressure value
read_temperature()
Read the temperature value
7.34 The pfeiffer_qmg420 module
7.34.1 Autogenerated API documentation for pfeiffer_qmg420
7.35 The pfeiffer_qmg422 module
7.35.1 Autogenerated API documentation for pfeiffer_qmg422
This module contains the driver code for the QMG422 control box for a pfeiffer mass-spectrometer. The code should
in principle work for multiple type of electronics. It has so far been tested with a qme-125 box and a qme-??? box.
The module is ment as a driver and has very little function in itself. The module is ment to be used as a sub-module
for a large program providing the functionality to actually use the mass-spectrometer.
Known bugs: Not all code has a proper distinction between the various electronics. The qme-125 has many limitations
compared to the qme-??? and these limitations are not always properly expressed in the code or the output of the
module
class PyExpLabSys.drivers.pfeiffer_qmg422.qmg_422(port=’/dev/ttyS0’, speed=19200)
Bases: object
The actual driver class.
__init__(port=’/dev/ttyS0’, speed=19200)
Initialize the module
comm(command)
Communicates with Baltzers/Pferiffer Mass Spectrometer
Implements the low-level protocol for RS-232 communication with the instrument. High-level protocol
can be implemented using this as a helper
7.33. The omron_d6fph module 139

Parameters command (str) – The command to send

Returns The reply associated with the last command
Return type str
communication_mode(computer_control=False)
Returns and sets the communication mode.
Parameters computer_control (bool) – Activates ASCII communication with the device
Returns The current communication mode
Return type str
simulation()
Chekcs wheter the instruments returns real or simulated data
Returns Message telling whether the device is in simulation mode
Return type str
set_channel(channel)
Set the current channel :param channel: The channel number :type channel: integer
read_sem_voltage()
Read the SEM Voltage :return: The SEM voltage :rtype: str
read_preamp_range()
Read the preamp range This function is not fully implemented :return: The preamp range :rtype: str
read_timestep()
Reads the integration period of a measurement :return: The integration period in non-physical unit :rtype:
str
sem_status(voltage=-1, turn_off=False, turn_on=False)
Get or set the SEM status :param voltage: The wanted SEM-voltage :type voltage: integer :param turn_off:
If True SEM will be turned on (unless turn_of==True) :type turn_off: boolean :param turn_on: If True
SEM will be turned off (unless turn_on==True) :type turn_on: boolean :return: The SEM voltage, The
SEM status, True means voltage on :rtype: integer, boolan
emission_status(current=-1, turn_off=False, turn_on=False)
Get or set the emission status. :param current: The wanted emission status. Only works for QME??? :type
current: integer :param turn_off: If True emission will be turned on (unless turn_of==True) :type turn_off:
boolean :param turn_on: If True emission will be turned off (unless turn_on==True) :type turn_on: boolean
:return: The emission value (for QME???), The emission status, True means filament on :rtype: integer,
boolan
detector_status(SEM=False, faraday_cup=False)
Choose between SEM and Faraday cup measurements
read_voltages()
Read the qme-voltages
start_measurement()
Start the measurement
actual_range(amp_range)
Returns the range that should be send to achieve the desired range
get_single_sample()
Read a single sample from the device

get_multiple_samples(number)
Read multiple samples from the device
config_channel(channel, mass=-1, speed=-1, enable=”, amp_range=0)
Config a MS channel for measurement
measurement_running()
Check if a measurement is running
waiting_samples()
Return number of waiting samples
mass_scan(first_mass, scan_width, amp_range=0)
Setup the mass spec for a mass scan
mass_time(ns)
Setup the mass spec for a mass-time measurement
7.36 The pfeiffer_turbo_pump module
7.36.1 Autogenerated API documentation for pfeiffer_turbo_pump
Self contained module to run a Pfeiffer turbo pump including fall-back text gui and data logging.
class PyExpLabSys.drivers.pfeiffer_turbo_pump.CursesTui(turbo_instance)
Text gui for controlling the pump
__init__(turbo_instance)
stop()
Cleanup terminal
class PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboReader(turbo_instance)
Keeps track of all data from a turbo pump with the intend of logging them
__init__(turbo_instance)
class PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboLogger(turboreader, parameter,
maximumtime=600)
Read a specific value and determine whether it should be logged
__init__(turboreader, parameter, maximumtime=600)
read_value()
Read the value of the logger
class PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboDriver(adress=1,
port=’/dev/ttyUSB3’)
The actual driver that will communicate with the pump
__init__(adress=1, port=’/dev/ttyUSB3’)
7.36. The pfeiffer_turbo_pump module 141

comm(command, read=True)
Implementaion of the communication protocol with the pump. The function deals with common syntax
need for all commands.
Parameters
• command (str) – The command to send to the pump
• read (Boolean) – If True, read only not action performed
Returns The reply from the pump
Return type Str
crc_calc(command)
Helper function to calculate crc for commands :param command: The command for which to calculate crc
:type command: str :return: The crc value :rtype: Str
read_rotation_speed()
Read the rotational speed of the pump
Returns The rotaional speed in Hz
Return type Float
read_set_rotation_speed()
Read the intended rotational speed of the pump
Returns The intended rotaional speed in Hz
Return type Int
read_operating_hours()
Read the number of operating hours
Returns Number of operating hours
Return type Int
read_gas_mode()
Read the gas mode :return: The gas mode :rtype: Str
read_vent_mode()
Read the venting mode :return: The venting mode :rtype: Str
read_sealing_gas()
Read whether sealing gas is applied :return: The sealing gas mode :rtype: Str
is_pump_accelerating()
Read if pump is accelerating :return: True if pump is accelerating, false if not :rtype: Boolean
turn_pump_on(off=False)
Spin the pump up or down :param off: If True the pump will spin down :type off: Boolean :return: Always
returns True :rtype: Boolean
read_temperature()
Read the various measured temperatures of the pump :return: Dictionary with temperatures :rtype: Dict
read_drive_power()
Read the current power consumption of the pump :return: Dictionary containing voltage, current and power
:rtype: Dict

7.37 The polyscience_4100 module
7.37.1 Autogenerated API documentation for polyscience_4100
Driver and test case for Polyscience 4100

class PyExpLabSys.drivers.polyscience_4100.Polyscience4100(port=’/dev/ttyUSB0’)
Bases: object
Driver for Polyscience 4100 chiller
comm(command)
Send serial commands to the instrument
set_setpoint(value)
Set the temperature setpoint
turn_unit_on(turn_on)
Turn on or off the unit
read_setpoint()
Read the current value of the setpoint
read_unit()
Read the measure unit
read_temperature()
Read the actual temperature of the water
read_pressure()
Read the output pressure
read_flow_rate()
Read the flow rate
read_ambient_temperature()
Read the ambient temperature in the device
read_status()
Answers if the device is turned on
7.38 The rosemount_nga2000 module
7.38.1 Autogenerated API documentation for rosemount_nga2000
7.39 The scpi module
7.39.1 Autogenerated API documentation for scpi
Implementation of SCPI standard

class PyExpLabSys.drivers.scpi.SCPI(interface, device=”, tcp_port=5025, hostname=”, bau-
drate=9600, visa_string=”, line_ending=’r’)
Bases: object
Driver for scpi communication
7.37. The polyscience_4100 module 143

__init__(interface, device=”, tcp_port=5025, hostname=”, baudrate=9600, visa_string=”,

line_ending=’\r’)
scpi_comm(command, expect_return=False)
Implements actual communication with SCPI instrument
Read version string from device
reset_device()
Rest device
device_clear()
Stop current operation
clear_error_queue()
Clear error queue
7.40 The specs_XRC1000 module
7.40.1 Autogenerated API documentation for specs_XRC1000
Self contained module to run a SPECS sputter gun including fall-back text gui
class PyExpLabSys.drivers.specs_XRC1000.CursesTui(sourcecontrol)
Defines a fallback text-gui for the source control.
__init__(sourcecontrol)
stop()
Cleanup the terminal
class PyExpLabSys.drivers.specs_XRC1000.XRC1000(port=None)
Driver for X-ray Source Control - XRC 1000
__init__(port=None)
Initialize module
Establish serial connection and create status variable to expose the status for the instrument for the various
gui’s
comm(command)
Communication with the instrument
Implements the synatx need to send commands to instrument including handling carrige returns and extra
lines of ‘OK’ and other pecularities of the instrument.
Returns The reply to the command striped for protocol technicalities
Return type str
posible comands: REM?, IEM?, UAN?, IHV?, IFI?, UFI?, PAN?, SERNO?, ANO?, STAT?, OPE? REM,
LOC, IEM 20e-3, UAN 10e3, OFF, COOL, STAN, UAON, OPE, ANO 1, ANO 2
read_water_flow()
read the water flow from external hardware :return: water flow in L/min :rtype float

read_emission_current()
Read the emission current. Unit A :return: The emission current :rtype: float
read_filament_voltage()
Read the filament voltage. Unit V :return: The filament voltage :rtype: float
read_filament_current()
Read the filament current. Unit A :return: The filament current :rtype: float
read_anode_voltage()
Read the anode voltage. Unit V :return: The anode voltage :rtype: float
read_anode_power()
Read the anode voltage. Unit W :return: The anode voltage :rtype: float
standby()
Set the device on standby The function is not working entirely as intended. TODO: Implement check to
see if the device is alrady in standby :return: The direct reply from the device :rtype: str
operate()
Set the device in operation mode TODO: This function should only be activated from standby!!! :return:
The direct reply from the device :rtype: str
remote_enable(local=False)
Enable or disable remote mode :param local: If True the device is set to local, otherwise to remote :type
local: Boolean :return: The direct reply from the device :rtype: str
change_control()
cooling()
Enable or disable water cooling :type local: Boolean :return: The direct reply from the device :rtype: str
update_status()
Update the status of the instrument
Runs a number of status queries and updates self.status
Returns The direct reply from the device
Return type str
7.41 The specs_iqe11 module
7.41.1 Autogenerated API documentation for specs_iqe11
Self contained module to run a SPECS sputter gun including fall-back text gui
class PyExpLabSys.drivers.specs_iqe11.CursesTui(sputtergun)
Defines a fallback text-gui for the sputter gun.
__init__(sputtergun)
stop()
Cleanup the terminal
7.41. The specs_iqe11 module 145

class PyExpLabSys.drivers.specs_iqe11.Puiqe11(simulate=False)
Driver for ion sputter guns from SPECS
__init__(simulate=False)
Initialize module
Establish serial connection and create status variable to expose the status for the instrument for the various
gui’s
comm(command)
Communication with the instrument
Implements the synatx need to send commands to instrument including handling carrige returns and extra
lines of ‘OK’ and other pecularities of the instrument.
Returns The reply to the command striped for protocol technicalities
Return type str
read_sputter_current()
Read the sputter current. Unit mA :return: The sputter current :rtype: float
read_filament_voltage()
Read the filament voltage. Unit V :return: The filament voltage :rtype: float
read_filament_current()
Read the filament current. Unit A :return: The filament current :rtype: float
read_emission_current()
Read the emission current. Unit mA :return: The emission current :rtype: float
read_acceleration_voltage()
Read the acceleration voltage. Unit V :return: The acceleration voltage :rtype: float
read_temperature_energy_module()
Read the temperature of the electronics module This value is not extremely correct, use only as guideline.
:return: The temperature :rtype: float
standby()
Set the device on standby The function is not working entirely as intended. TODO: Implement check to
see if the device is alrady in standby :return: The direct reply from the device :rtype: str
operate()
Set the device in operation mode TODO: This function should only be activated from standby!!! :return:
The direct reply from the device :rtype: str
remote_enable(local=False)
update_status()
Update the status of the instrument
Runs a number of status queries and updates self.status
Returns The direct reply from the device
Return type str

7.42 The srs_sr630 module
7.42.1 Autogenerated API documentation for srs_sr630
Driver for Standford Research Systems, Model SR630

class PyExpLabSys.drivers.srs_sr630.SRS_SR630(port)
Driver for Standford Research Systems, Model SR630
__init__(port)
comm(command)
Ensures correct protocol for instrument
config_analog_channel(channel, follow_temperature=False, value=0)
Configure an analog out channel
set_unit(channel, unit)
Set the measurement unit for a channel
tc_types()
List all configuration of all channels
read_open_status()
Check for open output on all channels
read_serial_number()
Return the serial number of the device
read_channel(channel)
Read the actual value of a channel
7.43 The stahl_hv_400 module
7.43.1 Autogenerated API documentation for stahl_hv_400
Driver for Stahl HV 400 Ion Optics Supply

class PyExpLabSys.drivers.stahl_hv_400.StahlHV400(port=’/dev/ttyUSB0’)
Bases: object
comm(command)
Perform actual communication with instrument
identify_device()
Return the serial number of the device
query_voltage(channel)
Something is all wrong here. . .
set_voltage(channel, value)
Set the voltage of a channel
read_temperature()
Read temperature of device
7.42. The srs_sr630 module 147

check_channel_status()
Check status of channel
7.44 The stmicroelectronics_ais328dq module
7.44.1 Autogenerated API documentation for stmicroelectronics_ais328dq
Driver for STMicroelectronics AIS328DQTR 3 axis accelerometer

class PyExpLabSys.drivers.stmicroelectronics_ais328dq.AIS328DQTR
Bases: object
__init__()
who_am_i()
Device identification
read_values()
7.45 The stmicroelectronics_l3g4200d module
7.45.1 Autogenerated API documentation for stmicroelectronics_l3g4200d
Driver for STMicroelectronics L3G4200D 3 axis gyroscope

class PyExpLabSys.drivers.stmicroelectronics_l3g4200d.L3G4200D
Bases: object
__init__()
who_am_i()
Device identification
read_values()
7.46 The tenma module
7.46.1 Autogenerated API documentation for tenma
Complete serial driver for the Tenma 72-2535, *72-2540, *72-2545, *72-2550, 72-2930 and *72-2940 (see details
below)
Note: * The driver has not been tested on the models with a *. However, the two models that has been
tested, seems like are built from the same template, so there is a very high probability that the generic
TenmaBase driver will work with those as well.

Implemented according to “Series Protocol V2.0 of Remote Control” (referred to in inline comments as the spec)
which can be downloaded from the link below.
Manual and specification can be downloaded from here: https://www.element14.com/community/ docs/DOC-
75108/l/protocol-information-for-tenma-72-2550-and-tenma-72-2535-qa-window- driver
class PyExpLabSys.drivers.tenma.Tenma722535(device, sleep_after_command=0.1)
Bases: PyExpLabSys.drivers.tenma.TenmaBase
Driver for the Tenma 72-2535 power supply
class PyExpLabSys.drivers.tenma.TenmaBase(device, sleep_after_command=0.1)
Bases: serial.serialposix.Serial
Serial driver for the Tenma 72-2535, *72-2540, *72-2545, *72-2550, 72-2930 and *72-2940 power supplies
Note: * The driver has not been tested on the models with a *. However, the two models that has been tested,
seems like are built from the same template, so there is a very high probability that the generic TenmaBase
driver will work with those as well.
__init__(device, sleep_after_command=0.1)
Initialize driver
Parameters
• device (str) – The serial device to connect to e.g. COM4 or /dev/ttyUSB0
• sleep_after_command (float) – (Optional) The time to sleep after sending a com-
mand, to make sure that the device is ready for another one. Defaults to 0.1, but quick tests
suggest that 0.05 might be enough.
com(command, decode_reply=True)
Send command to the device and possibly return reply
Parameters
• command (str) – Command as unicode object
• decode_reply (bool) – (Optional) Whether the reply should be utf-8 decoded to re-
turn a unicode object
get_actual_current()
Return the actual_current
Returns The actual current
Return type float
get_actual_voltage()
Return the actual voltage
Returns The actual coltage
Return type float
7.46. The tenma module 149

get_current()
Return the current setpoint
Returns The current setpoint
Return type float
get_identification()
Return the device identification
Returns E.g: ‘TENMA 72-2535 V2.0’
Return type str
get_voltage()
Return the voltage setpoint
Returns The voltage setpoint
Return type float
recall_memory(memory_number)
Recall memory of panel settings
Note: Recalling memory will automaticall disable output
Parameters number (int) – The number of the panel settings memory to recall
Raises ValueError – On invalid memory_number
save_memory(memory_number)
Recall memory of panel settings
Note: Saving to a memory slot seems to only be available for the memory slot currently active
Parameters number (int) – The number of the panel settings memory to recall
Raises ValueError – On invalid memory_number
set_beep(on_off )
Turn the beep on or off
on_off (bool): The beep status to set
set_current(current)
Sets the current setpoint
Parameters current (float) – The current to set
set_output(on_off )
Turn the output of or off
on_off (bool): The otput status to set
set_overcurrent_protection(on_off )
Set the over current protection (OCP) on or off
Parameters on_off (bool) – The overcurrent protection mode to set

set_overvoltage_protection(on_off )
Set the over voltage protection (OVP) on or off
Parameters on_off (bool) – The overvoltage protection mode to set
set_voltage(voltage)
Sets the voltage setpoint
Parameters voltage (float) – The voltage to set
status()
Return the status
The output is a dict with the following keys and types:
status = {
'channel1_mode': 'CV', # or 'CC' for constand current of voltage
'channel2_mode': 'CV', # or 'CC' for constand current of voltage
'beep_on': True,
'lock_on': False,
'output_on': True,
'tracking_status: 'Independent', # or 'Series' or 'Parallel'
}
Returns See fields specification above

Return type dict
PyExpLabSys.drivers.tenma.main()
Main module function, used for testing simple functional test
7.47 The vivo_technologies module
7.47.1 Autogenerated API documentation for vivo_technologies
Driver for a Vivo Technologies LS-689A barcode scanner

PyExpLabSys.drivers.vivo_technologies.detect_barcode_device()
Return the input device path of the Barcode Scanner
Iterates over all devices in /dev/input/event?? and looks for one that has ‘Barcode Reader’ in its description.
Returns The Barcode Scanner device path
Return type str
class PyExpLabSys.drivers.vivo_technologies.BlockingBarcodeReader(device_path)
Bases: object
Blocking Barcode Reader
__init__(device_path)
read_barcode()
Wait for a barcode and return it
close()
Close the device
7.47. The vivo_technologies module 151

class PyExpLabSys.drivers.vivo_technologies.ThreadedBarcodeReader(device_path)
Threaded Barcode Scanner that holds only the last value
__init__(device_path)
run()
The threaded run method
last_barcode_in_queue
Last barcode in the queue
wait_for_barcode
Last barcode property
oldest_barcode_from_queue
Get one barcode from the queue if there is one
close()
Close the device
7.48 The wpi_al1000 module
7.48.1 Autogenerated API documentation for wpi_al1000
This module implements a driver for the AL1000 syringe pump from World Precision Instruments
class PyExpLabSys.drivers.wpi_al1000.AL1000(port=’/dev/ttyUSB0’, baudrate=19200)
Bases: object
Driver for the AL1000 syringe pump
get_firmware()
Retrieves the firmware version
Returns The firmware version
Return type str
get_rate()
Retrieves the pump rate
Returns The pumping rate
set_rate(num, unit=False)
Sets the pump rate.
Parameters
• num (float) – The flow rate (0 mL/min - 34.38 mL/min)
• unit (str) – For valid values see below.
Valid units are: UM=microL/min MM=milliL/min UH=microL/hr MH=milliL/hour
Returns Notihing. Printing the function yields space for success or error message
set_vol(num)
Sets the pumped volume to the pump. The pump will pump until the given volume has been dispensed.

Parameters num (float) – The volume to de dispensed (no limits)

get_vol_disp()
Retrieves the dispensed volume since last reset.
Returns The dispensed volume
clear_vol_disp(direction=’both’)
Clear pumped volume for one or more dircetions.
Parameters direction (string) – The pumping direction. Valid directions are:
INF=inflation, WDR=withdrawn, both=both directions. Default is both
set_fun(phase)
Sets the program function
set_safe_mode(num)
Enables or disables safe mode.
Parameters num=0 --> Safe mode disables (If) – If num>0 –> Safe mode enables
with the requirement that valid communication must be received every num seconds
get_direction()
Retrieves the curret pumping direction
set_direction(direction)
Sets the pumping direction
Parameters --> Pumping dirction set to infuse (directoin=INF) –
directoin=WDR –> Pumping dirction set to Withdraw directoin=REV –> Pumping dirc-
tion set to the reverse current pumping direction
retract_pump()
Fully retracts the pump. REMEMBER TO STOP MANUALLY!
7.49 The xgs600 module
7.49.1 Autogenerated API documentation for xgs600
Driver class for XGS600 gauge controll

class PyExpLabSys.drivers.xgs600.XGS600Driver(port=’/dev/ttyUSB1’)
Driver for XGS600 gauge controller
xgs_comm(command)
Implements basic communication
7.49. The xgs600 module 153

read_all_pressures()
Read pressure from all sensors
list_all_gauges()
List all installed gauge cards
read_pressure(gauge_id)
Read the pressure from a specific gauge
filament_lit(gauge_id)
Report if the filament of a given gauge is lid
emission_status(gauge_id)
Read the status of the emission for a given gauge
set_smission_off(gauge_id)
Turn off emission from a given gauge
set_emission_on(gauge_id, filament)
Turn on emission for a given gauge
Read gauge controller firmware version
read_pressure_unit()
Read which pressure unit is used

CHAPTER 8
How To’s
This section contain howtos for different procedures associated with elements of PyExpLabSys. This could e.g. be the
installation and configuration of a requirement.
8.1 The Bakeout Box HOWTO
Contents
• The Bakeout Box HOWTO

– A Section
* A subsection
This HOWTO explains how to setup and configure a new bakeout box . . . FIXME
8.1.1 A Section
A subsection
155
156 Chapter 8. How To’s

CHAPTER 9
Developer Notes
This chapter contains information useful for developers of PyExpLabSys. The documentation has the form of little
sections that each describe a small task.
Table of Contents
• Developer Notes
– Setting up logging for a component of PyExpLabSys
– Editing/Updating Documentation
* Adding a driver documentation stub for a new driver

* Adding additional documentation for a driver
– Writing Documentation
* Hint: Disable Browser Cache

* Restructured Text Quick Reference
· Inline Markup and External Links
· Sections
· Labels and References
· Source code blocks
· Lists
· References to code documentation
* Writing docstring with Napoleon
157
9.1 Setting up logging for a component of PyExpLabSys
This section describes how to set up logging for a component in PyExpLabSys with the logging module (i.e. the
meaning of the word “logging” that refers to text output of debug and status information to e.g. terminal and text files
NOT sending data to the database).
Note: This section specifically deals with setting up logging for a component in PyExpLabSys, not of a program
merely using PyExpLabSys. For information about how to set up logging for a program merely using PyExpLabSys,
see the standard library documentation and Setting up logging of your program for how to use some convenience
functions in PyExpLabSys.
Setting up a logger for a component of PyExpLabSys should be done in the manner recommended by the standard
library documentation for logging from libraries. I.e. in the beginning of the file to the following:
import logging
LOG = logging.getLogger(__name__)
LOG.addHandler(logging.NullHandler())
Where using __name__ as the name, will ensure that it gets a name that is the full qualified name of the module e.g.
PyExpLabSys.common.utilities.
If more fine grained logging is required, e.g. if a module consist of several large classes and it would preferable with
a logger per class, they can be set up in the same manner. Such class loggers should keep the __name__ as a prefix
followed by a “.” and the name of the class, i.e:
# Assuming logging is already imported for the module logger

MYCLASS_LOG = logging.getLogger(__name__ + '.MyClass')
MYCLASS_LOG.addHandler(logging.NullHandler())
class MyClass(object):
"""My fancy class"""
pass
9.2 Editing/Updating Documentation
9.2.1 Adding a driver documentation stub for a new driver
After adding a new driver run the script: PyExpLabSys/doc/source/

update-driver-only-autogen-stubs.py. It will generate driver documentation stubs for all the drivers that
did not previously have one. The stubs are placed in PyExpLabSys/doc/source/drivers-autogen-only.
After generating the stubs add and commit the new stubs with git.
cd PYEXPLABSYSPATH/doc/source
python update-driver-only-autogen-stubs.py
git add drivers-autogen-only/*.rst
git cm "doc: Added new driver documentation stubs for <name of your driver>"
9.2.2 Adding additional documentation for a driver
To add additional documentation for a driver, e.g. usage examples, that is not well suited to be placed directly in the
source file, follow this procedure.
158 Chapter 9. Developer Notes

In the PyExpLabSys documentation the driver documentation files are located in two different folders depending on
whether it is a stub or has extra documentation. To add extra documentation, first git move the file and then start to
edit and commit it as usual:
cd PYEXPLABSYSPATH/doc/source
git mv drivers-autogen-only/<name_of_your_driver_module>.rst drivers/
# Edit and commit as usual
9.3 Writing Documentation
9.3.1 Hint: Disable Browser Cache
It is useful to disable caching in your browser temporarily, when it is being used to preview local Sphinx pages. The
easiest way to disable browser cache temporarily, is to disable caching when the developer tools are open. For Firefox,
the procedure is:
1. Open developer view (F12).
2. Open the settings for developer view (there is a little gear in the headline of developer view, third icon from the
right)
3. Under “Advanced Settings” click “Disable Cache (when tool is open)”
In Chromium, the procedure is similar, except the check box is under “General”.
9.3.2 Restructured Text Quick Reference
General restructured text primer is located here: http://sphinx-doc.org/rest.html. Most of the examples are from there.
Super short summary of that follows:
Inline Markup and External Links
**bold**, *italics*, ``code``.

External weblinks: http://xkcd.com/ or with custom title `Coolest comic ever <http://xkcd.
com/>`_.
Sections
The way to mark something as a section title is:
#####
parts
#####
********
chapters
********
sections
========
subsections
9.3. Writing Documentation 159

-----------
subsubsections
^^^^^^^^^^^^^^
paragraphs
""""""""""
The following is the convention for how to use those in PyExpLabSys and the overall structure.
• index.rst
– Uses parts
– includes the main table of contents that links to chapter files for common, drivers, apps etc.
– common.rst (or any other chapter file)
* Starts sections at chapter level

* May include an additions table of contents tree for sub files e.g. common_contionuous_logger
* common_contionuous_logger.rst
· Once again starts at chapter level
How these sections level work, I (Kenneth) must admit I have not investigated in detail. It seems, that you can re-use
section levels at a lower level in the document hierarchy, if they are included in a table of contents tree, so we do. At
some point it would probably be good to try and understand that better
Labels and References
.. _my-reference-label:
Section to Cross-Reference
--------------------------
References to its own section: :ref:`my-reference-label` or :ref:`Link title

<my-reference-label>``
Source code blocks
.. code-block:: python
import time
t0 = time.time()
# Stuff that takes time
print(time.time() - t0)
Lists
Bullet lists
* Item over two lines. Item over two lines. Item over two lines.
Item over two lines. Item over two lines. Item over two lines.

* Lists can be nested, but must be separated by a blank line
* Also when going back in level
Numbered lists
1. This is a numbered list.

2. It has two items too.
#. This is a numbered list.

#. It has two items too.
References to code documentation
Examples
• :py:class:`PyExpLabSys.common.sockets.DateDataPullSocket` will create a link to the

documentation like this: PyExpLabSys.common.sockets.DateDataPullSocket
• :py:class:`~PyExpLabSys.common.sockets.DateDataPullSocket` will shorten the link
text to only the class name: DateDataPullSocket
• :py:meth:`.close` will make a link to the close method of the current class.
• :py:meth:`~.close` as above using only ‘close’ as the link text
• :py:meth:`the close method <.close>` will create a reference to the close method of the current
class with the link text ‘the close method’
Details
In general cross references are: :role:`target` or :role:`title <target>`

In this form, the role would usually be prefixed with a domain, so it could be e.g. :py:func: to refer to a Python
function. However, the py domain is the default, so it can be dropped from the role (shortened form).
For Python the relevant roles (in shortened form) are :
• :mod: for modules
• :func: for functions
• :data: for module level variables
• :class: for classes
• :meth: for methods
• :attr: for attributes
• :const: a “constant”, a variable that is not supposed to be changed
• :exc: for exceptions
• :obj: for objects of unspecified type
Whatever is written as the target is searched in the order:
1. Without any further qualification (directly importable I think)
2. Then with the current module preprended

3. Then with the current module and class (if any) preprended
If you prefix the target with a ., then this search order is reversed.
Prefixing the target with a ~ will shorten the link text to only show the last part.
9.3.3 Writing docstring with Napoleon
The standard way of writing docstrings, with arguments definitions, in Sphinx is quite ugly and almost unreadable as
pure text (which is annoying if you use an editor or IDE which will show you the standard help-invoked documentation.
The Napoleon extension to Sphinx (PyPi page) aims to fix this by letting you write docstring in the Google-style.
An example:
def old_data(self, codename, timeout=900, unixtime=None):

"""Checks if the data for codename has timed out
Args:
codename (str): The codename whose data should be checked for
timeout
Kwargs:
timeout (float): The timeout to use in seconds, defaults to 900s.
timestamp (float): Unix timestamp to compare to. Defaults to now.
Raises:
ValueError: If codename is unknown
TypeError: If timeout or unixtime are not floats (or ints where appropriate)
Returns:
bool: Whether the data is too old or not
"""
A few things to note:

• Positional arguments, keyword arguments, exceptions and return values (Args, Kwargs, Raises, Returns) are
written into sections. There are several aliases for each of them, but these are the recommended ones for
PyExpLabSys (all possibly sections).
• All are optional! Do not feel obligated to fill in Raises if it is not relevant.
• Args and kwargs are on the form: name (type): description
• Raises and Returns (which has no name) are on the form: type: description
• If the description needs to continue on the next line, it will need to be indented another level
The call signature for instantiation should be documented in __init__.
In classes, attributes that are not defined explicitly with decorators, are documented in the class docstring under the
Attributes section:
class MyClass(object):
"""Class that describes me
Attributes:
name (str): The name of me
birthdate (float): Unix timestamp for my birthdate and time
"""
def __init__(self, name, birthdate):

"""Initialize parameters"""
self.name = name
self.birthdate = birthdate
@property
def age(self):
"""The approximate age of me in years"""
return (time.time() - self.birthdate) / (math.pi * 10**7)
A few things to notice:

• The attributes are listed in the same manner as arguments
• The age attribute, which is explicitely declared, will automatically be documented by its docstring


CHAPTER 10
Indices and tables
• genindex
• modindex
• search
165
166 Chapter 10. Indices and tables

Python Module Index
p PyExpLabSys.drivers.mks_937b, 135
PyExpLabSys.combos, 61 PyExpLabSys.drivers.mks_g_series, 136
PyExpLabSys.common.database_saver, 21 PyExpLabSys.drivers.mks_pi_pc, 136
PyExpLabSys.common.loggers, 27 PyExpLabSys.drivers.NGC2D, 111
PyExpLabSys.common.plotters, 30 PyExpLabSys.drivers.omega_cn7800, 137
PyExpLabSys.common.plotters_backend_qwt, PyExpLabSys.drivers.omega_cni, 137
33 PyExpLabSys.drivers.omega_D6400, 136
PyExpLabSys.common.sockets, 45 PyExpLabSys.drivers.omegabus, 138
PyExpLabSys.common.utilities, 56 PyExpLabSys.drivers.omron_d6fph, 139
PyExpLabSys.drivers.agilent_34410A, 111 PyExpLabSys.drivers.pfeiffer, 107
PyExpLabSys.drivers.agilent_34972A, 112 PyExpLabSys.drivers.pfeiffer_qmg420, 139
PyExpLabSys.drivers.bio_logic, 80 PyExpLabSys.drivers.pfeiffer_qmg422, 139
PyExpLabSys.drivers.bronkhorst, 113 PyExpLabSys.drivers.pfeiffer_turbo_pump,
PyExpLabSys.drivers.brooks_s_protocol, 141
113 PyExpLabSys.drivers.polyscience_4100,
PyExpLabSys.drivers.cpx400dp, 114 143
PyExpLabSys.drivers.crowcon, 115 PyExpLabSys.drivers.rosemount_nga2000,
PyExpLabSys.drivers.dataq_binary, 118 143
PyExpLabSys.drivers.dataq_comm, 122 PyExpLabSys.drivers.scpi, 143
PyExpLabSys.drivers.edwards_agc, 122 PyExpLabSys.drivers.specs_iqe11, 145
PyExpLabSys.drivers.edwards_nxds, 123 PyExpLabSys.drivers.specs_XRC1000, 144
PyExpLabSys.drivers.epimax, 124 PyExpLabSys.drivers.srs_sr630, 147
PyExpLabSys.drivers.four_d_systems, 99 PyExpLabSys.drivers.stahl_hv_400, 147
PyExpLabSys.drivers.freescale_mma7660fc, PyExpLabSys.drivers.stmicroelectronics_ais328dq,
126 148
PyExpLabSys.drivers.fug, 126 PyExpLabSys.drivers.stmicroelectronics_l3g4200d,
PyExpLabSys.drivers.galaxy_3500, 129 148
PyExpLabSys.drivers.honeywell_6000, 129 PyExpLabSys.drivers.tenma, 148
PyExpLabSys.drivers.inficon_sqm160, 130 PyExpLabSys.drivers.vivo_technologies,
PyExpLabSys.drivers.innova, 130 151
PyExpLabSys.drivers.intellemetrics_il800,PyExpLabSys.drivers.wpi_al1000, 152
132 PyExpLabSys.drivers.xgs600, 153
PyExpLabSys.drivers.isotech_ips, 132 PyExpLabSys.file_parsers.chemstation,
PyExpLabSys.drivers.keithley_2700, 133 69
PyExpLabSys.drivers.keithley_smu, 133 PyExpLabSys.file_parsers.specs, 65
PyExpLabSys.drivers.kjlc_pressure_gauge, PyExpLabSys.settings, 63
134
PyExpLabSys.drivers.lascar, 134
PyExpLabSys.drivers.mks_925_pirani, 135
167
168 Python Module Index

Index
Symbols __init__() (PyExpLabSys.drivers.agilent_34410A.Agilent34410ADriver

__init__() (PyExpLabSys.combos.LiveContinuousLogger method), 111
method), 61 __init__() (PyExpLabSys.drivers.agilent_34972A.Agilent34972ADriver
__init__() (PyExpLabSys.common.database_saver.ContinuousDataSaver method), 112
method), 24 __init__() (PyExpLabSys.drivers.bio_logic.CA method),
__init__() (PyExpLabSys.common.database_saver.DataSetSaver 93
method), 22 __init__() (PyExpLabSys.drivers.bio_logic.CP method),
__init__() (PyExpLabSys.common.database_saver.SqlSaver 92
method), 25 __init__() (PyExpLabSys.drivers.bio_logic.CV method),
__init__() (PyExpLabSys.common.loggers.ContinuousLogger 89
method), 28 __init__() (PyExpLabSys.drivers.bio_logic.CVA
__init__() (PyExpLabSys.common.loggers.InterruptableThread method), 90
method), 27 __init__() (PyExpLabSys.drivers.bio_logic.ECLibCustomException
__init__() (PyExpLabSys.common.loggers.NoneResponse method), 98
method), 27 __init__() (PyExpLabSys.drivers.bio_logic.ECLibError
__init__() (PyExpLabSys.common.loggers.StartupException method), 98
method), 28 __init__() (PyExpLabSys.drivers.bio_logic.ECLibException
__init__() (PyExpLabSys.common.plotters.ContinuousPlotter method), 98
method), 32 __init__() (PyExpLabSys.drivers.bio_logic.GeneralPotentiostat
__init__() (PyExpLabSys.common.plotters.DataPlotter method), 82
method), 30 __init__() (PyExpLabSys.drivers.bio_logic.KBIOData
__init__() (PyExpLabSys.common.plotters_backend_qwt.Colors method), 86
method), 33 __init__() (PyExpLabSys.drivers.bio_logic.MIR
__init__() (PyExpLabSys.common.plotters_backend_qwt.QwtPlot method), 95
method), 33 __init__() (PyExpLabSys.drivers.bio_logic.OCV
__init__() (PyExpLabSys.common.sockets.CallBackThread method), 88
method), 51 __init__() (PyExpLabSys.drivers.bio_logic.SP150
__init__() (PyExpLabSys.common.sockets.CommonDataPullSocket method), 86
method), 47 __init__() (PyExpLabSys.drivers.bio_logic.SPEIS
__init__() (PyExpLabSys.common.sockets.DataPullSocket method), 94
method), 48 __init__() (PyExpLabSys.drivers.bio_logic.Technique
__init__() (PyExpLabSys.common.sockets.DataPushSocket method), 88
method), 50 __init__() (PyExpLabSys.drivers.bronkhorst.Bronkhorst
__init__() (PyExpLabSys.common.sockets.DateDataPullSocket method), 113
method), 48 __init__() (PyExpLabSys.drivers.brooks_s_protocol.Brooks
__init__() (PyExpLabSys.common.sockets.LiveSocket method), 113
method), 52 __init__() (PyExpLabSys.drivers.cpx400dp.CPX400DPDriver
__init__() (PyExpLabSys.common.sockets.PortStillReserved method), 114
method), 52 __init__() (PyExpLabSys.drivers.cpx400dp.InterfaceOutOfBoundsError
method), 114
169
__init__() (PyExpLabSys.drivers.crowcon.Vortex __init__() (PyExpLabSys.drivers.omega_cn7800.CN7800

method), 116 method), 137
__init__() (PyExpLabSys.drivers.dataq_binary.DataQBinary__init__() (PyExpLabSys.drivers.omega_cni.CNi3244_C24
__init__() (PyExpLabSys.drivers.dataq_comm.DataQ __init__() (PyExpLabSys.drivers.omega_cni.ISeries
__init__() (PyExpLabSys.drivers.edwards_agc.EdwardsAGC__init__() (PyExpLabSys.drivers.omegabus.OmegaBus
__init__() (PyExpLabSys.drivers.edwards_nxds.EdwardsNxds __init__() (PyExpLabSys.drivers.omron_d6fph.OmronD6fph
__init__() (PyExpLabSys.drivers.epimax.PVCCommon __init__() (PyExpLabSys.drivers.pfeiffer.TPG261
__init__() (PyExpLabSys.drivers.epimax.PVCi method), __init__() (PyExpLabSys.drivers.pfeiffer.TPG262
125 method), 109
__init__() (PyExpLabSys.drivers.four_d_systems.Button __init__() (PyExpLabSys.drivers.pfeiffer.TPG26x
__init__() (PyExpLabSys.drivers.four_d_systems.PicasoCommon
__init__() (PyExpLabSys.drivers.pfeiffer_qmg422.qmg_422
__init__() (PyExpLabSys.drivers.four_d_systems.PicasoException
__init__() (PyExpLabSys.drivers.pfeiffer_turbo_pump.CursesTui
__init__() (PyExpLabSys.drivers.four_d_systems.PicasouLCD28PTU
__init__() (PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboDriver
__init__() (PyExpLabSys.drivers.freescale_mma7660fc.MMA7660FC
__init__() (PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboLogger
__init__() (PyExpLabSys.drivers.fug.FUGNTN140Driver __init__() (PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboReader
__init__() (PyExpLabSys.drivers.galaxy_3500.Galaxy3500 __init__() (PyExpLabSys.drivers.polyscience_4100.Polyscience4100
__init__() (PyExpLabSys.drivers.honeywell_6000.HIH6130__init__() (PyExpLabSys.drivers.scpi.SCPI method), 143
method), 129 __init__() (PyExpLabSys.drivers.specs_XRC1000.CursesTui
__init__() (PyExpLabSys.drivers.inficon_sqm160.InficonSQM160 method), 144
method), 130 __init__() (PyExpLabSys.drivers.specs_XRC1000.XRC1000
__init__() (PyExpLabSys.drivers.innova.Megatec method), 144
method), 130 __init__() (PyExpLabSys.drivers.specs_iqe11.CursesTui
__init__() (PyExpLabSys.drivers.intellemetrics_il800.IL800 method), 145
method), 132 __init__() (PyExpLabSys.drivers.specs_iqe11.Puiqe11
__init__() (PyExpLabSys.drivers.isotech_ips.IPS method), 146
method), 132 __init__() (PyExpLabSys.drivers.srs_sr630.SRS_SR630
__init__() (PyExpLabSys.drivers.keithley_2700.KeithleySMU method), 147
method), 133 __init__() (PyExpLabSys.drivers.stahl_hv_400.StahlHV400
__init__() (PyExpLabSys.drivers.keithley_smu.KeithleySMU method), 147
method), 133 __init__() (PyExpLabSys.drivers.stmicroelectronics_ais328dq.AIS328DQT
__init__() (PyExpLabSys.drivers.kjlc_pressure_gauge.KJLC300 method), 148
method), 134 __init__() (PyExpLabSys.drivers.stmicroelectronics_l3g4200d.L3G4200D
__init__() (PyExpLabSys.drivers.lascar.ElUsbRt method), 148
method), 134 __init__() (PyExpLabSys.drivers.tenma.TenmaBase
__init__() (PyExpLabSys.drivers.mks_925_pirani.Mks925 method), 149
method), 135 __init__() (PyExpLabSys.drivers.vivo_technologies.BlockingBarcodeReade
__init__() (PyExpLabSys.drivers.mks_937b.Mks937b method), 151
method), 135 __init__() (PyExpLabSys.drivers.vivo_technologies.ThreadedBarcodeReade
__init__() (PyExpLabSys.drivers.mks_g_series.MksGSeries method), 152
method), 136 __init__() (PyExpLabSys.drivers.wpi_al1000.AL1000
__init__() (PyExpLabSys.drivers.omega_D6400.OmegaD6400 method), 152
method), 137 __init__() (PyExpLabSys.drivers.xgs600.XGS600Driver
170 Index
method), 153 actual_range() (PyExpLab-

__init__() (PyExpLabSys.file_parsers.chemstation.CHFile Sys.drivers.pfeiffer_qmg422.qmg_422
__init__() (PyExpLabSys.file_parsers.chemstation.Injection add_channel() (PyExpLab-
method), 70 Sys.drivers.dataq_comm.DataQ method),
__init__() (PyExpLabSys.file_parsers.chemstation.Sequence 122
method), 70 add_continuous_measurement() (PyExpLab-
__init__() (PyExpLabSys.file_parsers.specs.Region Sys.common.database_saver.ContinuousDataSaver
__init__() (PyExpLabSys.file_parsers.specs.RegionGroup add_measurement() (PyExpLab-
method), 68 Sys.common.database_saver.DataSetSaver
__init__() (PyExpLabSys.file_parsers.specs.SpecsFile method), 23
method), 67 add_point() (PyExpLab-
__init__() (PyExpLabSys.settings.Settings method), 64 Sys.common.plotters.ContinuousPlotter
_asdict() (PyExpLabSys.drivers.bio_logic.DataField method), 32
method), 81 add_point() (PyExpLabSys.common.plotters.DataPlotter
_asdict() (PyExpLabSys.drivers.bio_logic.TechniqueArgument method), 31
method), 82 add_point_now() (PyExpLab-
_check_arg() (PyExpLabSys.drivers.bio_logic.Technique Sys.common.plotters.ContinuousPlotter
static method), 88 method), 32
_from_16_bit_rgb() (PyExpLab- Agilent34410ADriver (class in PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.drivers.agilent_34410A), 111
static method), 101 Agilent34972ADriver (class in PyExpLab-
_init_c_args() (PyExpLab- Sys.drivers.agilent_34972A), 112
Sys.drivers.bio_logic.Technique method), AIS328DQTR (class in PyExpLab-
88 Sys.drivers.stmicroelectronics_ais328dq),
_init_data_fields() (PyExpLab- 148
Sys.drivers.bio_logic.KBIOData method), AL1000 (class in PyExpLabSys.drivers.wpi_al1000), 152
87 alarms() (PyExpLabSys.drivers.galaxy_3500.Galaxy3500
_make() (PyExpLabSys.drivers.bio_logic.DataField class method), 129
method), 81 AMP_CODES (in module PyExpLab-
_make() (PyExpLabSys.drivers.bio_logic.TechniqueArgument Sys.drivers.bio_logic), 98
class method), 82
_parse_data() (PyExpLab- B
Sys.drivers.bio_logic.KBIOData method), BAD_CHARS (in module PyExpLab-
87 Sys.common.sockets), 53
_replace() (PyExpLabSys.drivers.bio_logic.DataField BANDWIDTHS (in module PyExpLab-
method), 81 Sys.drivers.bio_logic), 98
_replace() (PyExpLabSys.drivers.bio_logic.TechniqueArgumentbattery_charge() (PyExpLab-
method), 82 Sys.drivers.galaxy_3500.Galaxy3500 method),
_send_command() (PyExpLab- 129
Sys.drivers.four_d_systems.PicasoCommon battery_status() (PyExpLab-
method), 100 Sys.drivers.galaxy_3500.Galaxy3500 method),
_to_16_bit_rgb() (PyExpLab- 129
Sys.drivers.four_d_systems.PicasoCommon bearing_service() (PyExpLab-
static method), 101 Sys.drivers.edwards_nxds.EdwardsNxds
method), 123
A BlockingBarcodeReader (class in PyExpLab-
abort_scan() (PyExpLab- Sys.drivers.vivo_technologies), 151
Sys.drivers.agilent_34972A.Agilent34972ADriverbool_translate() (in module PyExpLab-
method), 112 Sys.common.sockets), 46
activate_library_logging() (in module PyExpLab- Bronkhorst (class in PyExpLabSys.drivers.bronkhorst),
Sys.common.utilities), 58 113
Index 171
Brooks (class in PyExpLab- check_eclib_return_code() (PyExpLab-

Sys.drivers.brooks_s_protocol), 113 Sys.drivers.bio_logic.GeneralPotentiostat
buffer_overflow_size (PyExpLab- method), 86
Sys.drivers.dataq_binary.DataQBinary at- checksum() (PyExpLab-
tribute), 120 Sys.drivers.mks_g_series.MksGSeries
BufferOverflow, 119 method), 136
Button (class in PyExpLabSys.drivers.four_d_systems), CHFile (class in PyExpLabSys.file_parsers.chemstation),
106 69
byte_to_bits() (in module PyExpLabSys.drivers.epimax), clear_buffer() (PyExpLab-
126 Sys.drivers.dataq_binary.DataQBinary
bytes_to_bakeout_flags() (in module PyExpLab- method), 120
Sys.drivers.epimax), 126 clear_error_queue() (PyExpLabSys.drivers.scpi.SCPI
bytes_to_firmware_version() (in module PyExpLab- method), 144
Sys.drivers.epimax), 125 clear_screen() (PyExpLab-
bytes_to_float() (in module PyExpLab- Sys.drivers.four_d_systems.PicasoCommon
Sys.drivers.epimax), 126 method), 103
bytes_to_slot_id() (in module PyExpLab- clear_updated() (PyExpLab-
Sys.drivers.epimax), 126 Sys.common.sockets.DataPushSocket method),
bytes_to_status() (in module PyExpLab- 51
Sys.drivers.epimax), 126 clear_vol_disp() (PyExpLab-
bytes_to_string() (in module PyExpLab- Sys.drivers.wpi_al1000.AL1000 method),
Sys.drivers.epimax), 125 153
close() (PyExpLabSys.drivers.crowcon.Vortex method),
C 116
c_args() (PyExpLabSys.drivers.bio_logic.Technique close() (PyExpLabSys.drivers.epimax.PVCCommon
CA (class in PyExpLabSys.drivers.bio_logic), 92 close() (PyExpLabSys.drivers.four_d_systems.PicasoCommon
call_spec_string() (in module PyExpLab- method), 100
Sys.common.utilities), 59 close() (PyExpLabSys.drivers.kjlc_pressure_gauge.KJLC300
CallBackThread (class in PyExpLab- method), 134
Sys.common.sockets), 51 close() (PyExpLabSys.drivers.omega_cni.ISeries
change_control() (PyExpLab- method), 138
Sys.drivers.specs_XRC1000.XRC1000 close() (PyExpLabSys.drivers.vivo_technologies.BlockingBarcodeReader
change_unit() (PyExpLab- close() (PyExpLabSys.drivers.vivo_technologies.ThreadedBarcodeReader
Sys.drivers.mks_925_pirani.Mks925 method), method), 152
135 CN7800 (class in PyExpLabSys.drivers.omega_cn7800),
ChannelInfos (class in PyExpLabSys.drivers.bio_logic), 137
96 CNi3244_C24 (class in PyExpLab-
character_height() (PyExpLab- Sys.drivers.omega_cni), 138
Sys.drivers.four_d_systems.PicasoCommon code (PyExpLabSys.drivers.crowcon.Status attribute),
method), 102 115
character_width() (PyExpLab- Colors (class in PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.common.plotters_backend_qwt), 33
method), 101 com() (PyExpLabSys.drivers.innova.Megatec method),
check (PyExpLabSys.drivers.bio_logic.TechniqueArgument 131
attribute), 82 com() (PyExpLabSys.drivers.tenma.TenmaBase method),
check_argument (PyExpLab- 149
Sys.drivers.bio_logic.TechniqueArgument comm() (PyExpLabSys.drivers.bronkhorst.Bronkhorst
attribute), 82 method), 113
check_channel_status() (PyExpLab- comm() (PyExpLabSys.drivers.brooks_s_protocol.Brooks
Sys.drivers.stahl_hv_400.StahlHV400 method), 113
method), 148 comm() (PyExpLabSys.drivers.dataq_comm.DataQ
method), 122
172 Index
comm() (PyExpLabSys.drivers.edwards_agc.EdwardsAGC config_current_measurement() (PyExpLab-

method), 123 Sys.drivers.agilent_34410A.Agilent34410ADriver
comm() (PyExpLabSys.drivers.edwards_nxds.EdwardsNxds method), 111
method), 123 config_resistance_measurement() (PyExpLab-
comm() (PyExpLabSys.drivers.galaxy_3500.Galaxy3500 Sys.drivers.agilent_34410A.Agilent34410ADriver
comm() (PyExpLabSys.drivers.inficon_sqm160.InficonSQM160
connect() (PyExpLabSys.drivers.bio_logic.GeneralPotentiostat
comm() (PyExpLabSys.drivers.intellemetrics_il800.IL800 connection (PyExpLab-
method), 132 Sys.common.database_saver.DataSetSaver
comm() (PyExpLabSys.drivers.isotech_ips.IPS method), attribute), 22
132 connection (PyExpLab-
comm() (PyExpLabSys.drivers.mks_925_pirani.Mks925 Sys.common.database_saver.SqlSaver at-
method), 135 tribute), 25
comm() (PyExpLabSys.drivers.mks_937b.Mks937b ContinuousDataSaver (class in PyExpLab-
method), 135 Sys.common.database_saver), 24
comm() (PyExpLabSys.drivers.mks_g_series.MksGSeries ContinuousLogger (class in PyExpLab-
method), 136 Sys.common.loggers), 28
comm() (PyExpLabSys.drivers.omega_D6400.OmegaD6400ContinuousPlotter (class in PyExpLab-
method), 137 Sys.common.plotters), 32
comm() (PyExpLabSys.drivers.omegabus.OmegaBus convert_numeric_into_single() (PyExpLab-
method), 138 Sys.drivers.bio_logic.GeneralPotentiostat
comm() (PyExpLabSys.drivers.pfeiffer_qmg422.qmg_422 method), 86
method), 139 cooling() (PyExpLabSys.drivers.specs_XRC1000.XRC1000
comm() (PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboDriver method), 145
method), 141 CP (class in PyExpLabSys.drivers.bio_logic), 91
comm() (PyExpLabSys.drivers.polyscience_4100.Polyscience4100
CPX400DPDriver (class in PyExpLab-
method), 143 Sys.drivers.cpx400dp), 114
comm() (PyExpLabSys.drivers.specs_iqe11.Puiqe11 crc() (PyExpLabSys.drivers.brooks_s_protocol.Brooks
comm() (PyExpLabSys.drivers.specs_XRC1000.XRC1000 crc_calc() (PyExpLabSys.drivers.inficon_sqm160.InficonSQM160
method), 144 static method), 130
comm() (PyExpLabSys.drivers.srs_sr630.SRS_SR630 crc_calc() (PyExpLabSys.drivers.pfeiffer_turbo_pump.TurboDriver
comm() (PyExpLabSys.drivers.stahl_hv_400.StahlHV400 crystal_life() (PyExpLab-
method), 147 Sys.drivers.inficon_sqm160.InficonSQM160
command() (PyExpLabSys.drivers.omega_cni.ISeries method), 130
method), 137 current_error() (PyExpLab-
commit_time (PyExpLab- Sys.drivers.edwards_agc.EdwardsAGC
Sys.common.database_saver.SqlSaver at- method), 123
tribute), 25 CurrentValues (class in PyExpLabSys.drivers.bio_logic),
commits (PyExpLabSys.common.database_saver.SqlSaver 96
attribute), 25 CursesTui (class in PyExpLab-
CommonDataPullSocket (class in PyExpLab- Sys.drivers.pfeiffer_turbo_pump), 141
Sys.common.sockets), 47 CursesTui (class in PyExpLabSys.drivers.specs_iqe11),
communication_mode() (PyExpLab- 145
Sys.drivers.pfeiffer_qmg422.qmg_422 CursesTui (class in PyExpLab-
method), 140 Sys.drivers.specs_XRC1000), 144
config_analog_channel() (PyExpLab- cursor (PyExpLabSys.common.database_saver.DataSetSaver
Sys.drivers.srs_sr630.SRS_SR630 method), attribute), 22
147 cursor (PyExpLabSys.common.database_saver.SqlSaver
config_channel() (PyExpLab- attribute), 25
Sys.drivers.pfeiffer_qmg422.qmg_422 CustomColumn (class in PyExpLab-
method), 141 Sys.common.database_saver), 21
Index 173
CustomSMTPHandler (class in PyExpLab- define_single_parameter() (PyExpLab-

Sys.common.utilities), 58 Sys.drivers.bio_logic.GeneralPotentiostat
CustomSMTPWarningHandler (class in PyExpLab- method), 85
Sys.common.utilities), 58 DetConfMap (in module PyExpLabSys.drivers.crowcon),
CV (class in PyExpLabSys.drivers.bio_logic), 89 115
CVA (class in PyExpLabSys.drivers.bio_logic), 90 detect_barcode_device() (in module PyExpLab-
Sys.drivers.vivo_technologies), 151
D detector_configuration() (PyExpLab-
DATA (in module PyExpLabSys.common.sockets), 53 Sys.drivers.crowcon.Vortex method), 116
data (PyExpLabSys.common.plotters.ContinuousPlotter detector_status() (PyExpLab-
attribute), 33 Sys.drivers.pfeiffer_qmg422.qmg_422
data (PyExpLabSys.common.plotters.DataPlotter at- method), 140
tribute), 31 DetLev (in module PyExpLabSys.drivers.crowcon), 115
data_field_names (PyExpLab- device_clear() (PyExpLabSys.drivers.scpi.SCPI method),
Sys.drivers.bio_logic.KBIOData attribute), 144
87 DEVICE_CODES (in module PyExpLab-
data_fields (PyExpLabSys.drivers.bio_logic.CA at- Sys.drivers.bio_logic), 98
tribute), 93 device_info (PyExpLab-
data_fields (PyExpLabSys.drivers.bio_logic.CP at- Sys.drivers.bio_logic.GeneralPotentiostat
tribute), 92 attribute), 83
data_fields (PyExpLabSys.drivers.bio_logic.CV at- device_name() (PyExpLab-
tribute), 89 Sys.drivers.dataq_comm.DataQ method),
data_fields (PyExpLabSys.drivers.bio_logic.CVA at- 122
tribute), 90 DeviceInfos (class in PyExpLabSys.drivers.bio_logic), 95
data_fields (PyExpLabSys.drivers.bio_logic.MIR at- DI1110 (class in PyExpLabSys.drivers.dataq_binary),
tribute), 95 121
data_fields (PyExpLabSys.drivers.bio_logic.OCV at- disconnect() (PyExpLab-
tribute), 88 Sys.drivers.bio_logic.GeneralPotentiostat
data_fields (PyExpLabSys.drivers.bio_logic.SPEIS at- method), 83
tribute), 94 draw_button() (PyExpLab-
DATABASE (in module PyExpLab- Sys.drivers.four_d_systems.Button method),
Sys.common.database_saver), 21 107
DataField (class in PyExpLabSys.drivers.bio_logic), 81 draw_filled_rectangle() (PyExpLab-
DataInfos (class in PyExpLabSys.drivers.bio_logic), 97 Sys.drivers.four_d_systems.PicasoCommon
DataPlotter (class in PyExpLabSys.common.plotters), 30 method), 104
DataPullSocket (class in PyExpLab- draw_line() (PyExpLab-
Sys.common.sockets), 48 Sys.drivers.four_d_systems.PicasoCommon
DataPushSocket (class in PyExpLab- method), 103
Sys.common.sockets), 49 draw_rectangle() (PyExpLab-
DataQ (class in PyExpLabSys.drivers.dataq_comm), 122 Sys.drivers.four_d_systems.PicasoCommon
dataq() (PyExpLabSys.drivers.dataq_comm.DataQ method), 104
method), 122
DataQBinary (class in PyExpLab- E
Sys.drivers.dataq_binary), 119 E_RANGES (in module PyExpLab-
DataSetSaver (class in PyExpLab- Sys.drivers.bio_logic), 98
Sys.common.database_saver), 21 ECLibCustomException, 98
DateDataPullSocket (class in PyExpLab- ECLibError, 98
Sys.common.sockets), 48 ECLibException, 97
define_bool_parameter() (PyExpLab- EdwardsAGC (class in PyExpLab-
Sys.drivers.bio_logic.GeneralPotentiostat Sys.drivers.edwards_agc), 122
method), 84 EdwardsNxds (class in PyExpLab-
define_integer_parameter() (PyExpLab- Sys.drivers.edwards_nxds), 123
Sys.drivers.bio_logic.GeneralPotentiostat ElUsbRt (class in PyExpLabSys.drivers.lascar), 134
method), 85
174 Index
EMAIL_BACKLOG_LIMIT (in module PyExpLab- G

Sys.common.utilities), 57 Galaxy3500 (class in PyExpLab-
EMAIL_THROTTLE_TIME (in module PyExpLab- Sys.drivers.galaxy_3500), 129
Sys.common.utilities), 57 gauge_identification() (PyExpLab-
emission_status() (PyExpLab- Sys.drivers.pfeiffer.TPG26x method), 108
Sys.drivers.pfeiffer_qmg422.qmg_422 gauge_type() (PyExpLab-
method), 140 Sys.drivers.edwards_agc.EdwardsAGC
emission_status() (PyExpLab- method), 123
Sys.drivers.xgs600.XGS600Driver method), GeneralPotentiostat (class in PyExpLab-
154 Sys.drivers.bio_logic), 82
emit() (PyExpLabSys.common.utilities.CustomSMTPHandler get_actual_current() (PyExpLab-
method), 58 Sys.drivers.tenma.TenmaBase method),
emit() (PyExpLabSys.common.utilities.CustomSMTPWarningHandler149
method), 59 get_actual_voltage() (PyExpLab-
end_char (PyExpLabSys.drivers.dataq_binary.DataQBinary Sys.drivers.tenma.TenmaBase method),
attribute), 119 149
enqueue_point() (PyExpLab- get_analysis_method() (PyExpLab-
Sys.common.loggers.ContinuousLogger Sys.file_parsers.specs.SpecsFile method),
method), 29 68
enqueue_point_now() (PyExpLab- get_channel_infos() (PyExpLab-
Sys.common.loggers.ContinuousLogger Sys.drivers.bio_logic.GeneralPotentiostat
enqueue_query() (PyExpLab- get_channels_plugged() (PyExpLab-
Sys.common.database_saver.SqlSaver Sys.drivers.bio_logic.GeneralPotentiostat
ERROR_EMAIL (in module PyExpLab- get_color() (PyExpLab-
Sys.common.utilities), 56 Sys.common.plotters_backend_qwt.Colors
method), 33
F get_current() (PyExpLab-
filament_lit() (PyExpLab- Sys.drivers.fug.FUGNTN140Driver method),
Sys.drivers.xgs600.XGS600Driver method), 128
154 get_current() (PyExpLabSys.drivers.tenma.TenmaBase
filepath (PyExpLabSys.file_parsers.chemstation.CHFile method), 149
attribute), 69 get_current_values() (PyExpLab-
firmware() (PyExpLabSys.drivers.dataq_comm.DataQ Sys.drivers.bio_logic.GeneralPotentiostat
FIRMWARE_CODES (in module PyExpLab- get_data() (PyExpLabSys.drivers.bio_logic.GeneralPotentiostat
Sys.drivers.bio_logic), 98 method), 85
format_string (PyExpLab- get_detector_levels() (PyExpLab-
Sys.common.database_saver.CustomColumn Sys.drivers.crowcon.Vortex method), 116
attribute), 21 get_direction() (PyExpLab-
frequency() (PyExpLab- Sys.drivers.wpi_al1000.AL1000 method),
Sys.drivers.inficon_sqm160.InficonSQM160 153
method), 130 get_display_model() (PyExpLab-
frequency() (PyExpLab- Sys.drivers.four_d_systems.PicasoCommon
Sys.drivers.intellemetrics_il800.IL800 method), 106
method), 132 get_error_message() (PyExpLab-
FUGNTN140Driver (class in PyExpLabSys.drivers.fug), Sys.drivers.bio_logic.GeneralPotentiostat
126 method), 83
full_sequence_dataset() (PyExpLab- get_field() (PyExpLabSys.drivers.epimax.PVCCommon
Sys.file_parsers.chemstation.Sequence method), 125
method), 70 get_fields() (PyExpLabSys.drivers.epimax.PVCCommon
method), 125
get_firmware() (PyExpLab-
Index 175
Sys.drivers.wpi_al1000.AL1000 method), get_type() (PyExpLabSys.drivers.crowcon.Vortex

152 method), 117
get_graphics_parameters() (PyExpLab- get_unique_values_from_measurements() (PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.common.database_saver.DataSetSaver
get_identification() (PyExpLab- get_vol_disp() (PyExpLab-
Sys.drivers.tenma.TenmaBase method), Sys.drivers.wpi_al1000.AL1000 method),
150 153
get_lib_version() (PyExpLab- get_voltage() (PyExpLab-
Sys.drivers.bio_logic.GeneralPotentiostat Sys.drivers.fug.FUGNTN140Driver method),
method), 83 128
get_library_logger_names() (in module PyExpLab- get_voltage() (PyExpLabSys.drivers.tenma.TenmaBase
Sys.common.utilities), 57 method), 150
get_lock() (PyExpLabSys.drivers.cpx400dp.CPX400DPDriver getSubject() (PyExpLab-
method), 115 Sys.common.utilities.CustomSMTPHandler
get_logger() (in module PyExpLabSys.common.utilities), method), 58
57
get_message() (PyExpLab- H
Sys.drivers.bio_logic.GeneralPotentiostat handle() (PyExpLabSys.common.sockets.PullUDPHandler
get_multiple_detector_levels() (PyExpLab- handle() (PyExpLabSys.common.sockets.PushUDPHandler
Sys.drivers.crowcon.Vortex method), 116 method), 49
get_multiple_samples() (PyExpLab- HIH6130 (class in PyExpLab-
Sys.drivers.pfeiffer_qmg422.qmg_422 Sys.drivers.honeywell_6000), 129
method), 140 HOSTNAME (in module PyExpLab-
get_number_installed_detectors() (PyExpLab- Sys.common.database_saver), 21
Sys.drivers.crowcon.Vortex method), 116
get_number_installed_digital_outputs() (PyExpLab- I
Sys.drivers.crowcon.Vortex method), 117 I_RANGES (in module PyExpLabSys.drivers.bio_logic),
get_rate() (PyExpLabSys.drivers.wpi_al1000.AL1000 98
method), 152 id_number (PyExpLab-
get_serial_number() (PyExpLab- Sys.drivers.bio_logic.GeneralPotentiostat
Sys.drivers.crowcon.Vortex method), 117 attribute), 83
get_single_sample() (PyExpLab- identification_string() (PyExpLab-
Sys.drivers.pfeiffer_qmg422.qmg_422 Sys.drivers.fug.FUGNTN140Driver method),
method), 140 128
get_spe_version() (PyExpLab- identify_device() (PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.drivers.omega_cni.ISeries method),
method), 106 138
get_state() (PyExpLab- identify_device() (PyExpLab-
Sys.drivers.fug.FUGNTN140Driver method), Sys.drivers.stahl_hv_400.StahlHV400
128 method), 147
get_status() (PyExpLabSys.drivers.innova.Megatec IL800 (class in PyExpLab-
method), 131 Sys.drivers.intellemetrics_il800), 132
get_system_name() (PyExpLab- increase_voltage() (PyExpLab-
Sys.drivers.crowcon.Vortex method), 117 Sys.drivers.cpx400dp.CPX400DPDriver
get_system_power_status() (PyExpLab- method), 115
Sys.drivers.crowcon.Vortex method), 117 InficonSQM160 (class in PyExpLab-
get_system_status() (PyExpLab- Sys.drivers.inficon_sqm160), 130
Sys.drivers.crowcon.Vortex method), 117 info() (PyExpLabSys.drivers.dataq_binary.DataQBinary
get_temperature() (PyExpLabSys.drivers.lascar.ElUsbRt method), 120
method), 134 infos (PyExpLabSys.drivers.dataq_binary.DataQBinary
get_temperature_and_humidity() (PyExpLab- attribute), 119
Sys.drivers.lascar.ElUsbRt method), 134
176 Index
init_device() (PyExpLab- label (PyExpLabSys.drivers.bio_logic.TechniqueArgument

Sys.drivers.omron_d6fph.OmronD6fph attribute), 82
method), 139 last (PyExpLabSys.common.sockets.DataPushSocket at-
Injection (class in PyExpLab- tribute), 51
Sys.file_parsers.chemstation), 69 last_barcode_in_queue (PyExpLab-
InnovaRT6K (class in PyExpLabSys.drivers.innova), 131 Sys.drivers.vivo_technologies.ThreadedBarcodeReader
input_measurements() (PyExpLab- attribute), 152
Sys.drivers.galaxy_3500.Galaxy3500 method), led_color() (PyExpLab-
insert_batch_query (PyExpLab- method), 121
Sys.common.database_saver.DataSetSaver led_colors (PyExpLab-
attribute), 22 Sys.drivers.dataq_binary.DataQBinary at-
insert_measurement_query (PyExpLab- tribute), 119
Sys.common.database_saver.DataSetSaver list_all_gauges() (PyExpLab-
attribute), 22 Sys.drivers.xgs600.XGS600Driver method),
insert_point_query (PyExpLab- 154
Sys.common.database_saver.DataSetSaver LiveContinuousLogger (class in PyExpLabSys.combos),
attribute), 22 61
InterfaceOutOfBoundsError, 114 LiveSocket (class in PyExpLabSys.common.sockets), 52
InterruptableThread (class in PyExpLab- load_firmware() (PyExpLab-
Sys.common.loggers), 27 Sys.drivers.bio_logic.GeneralPotentiostat
ion_gauge_status() (in module PyExpLab- method), 83
Sys.drivers.epimax), 126 load_technique() (PyExpLab-
IPS (class in PyExpLabSys.drivers.isotech_ips), 132 Sys.drivers.bio_logic.GeneralPotentiostat
is_channel_plugged() (PyExpLab- method), 84
Sys.drivers.bio_logic.GeneralPotentiostat log_batch() (PyExpLab-
method), 84 Sys.combos.LiveContinuousLogger method),
is_on() (PyExpLabSys.drivers.fug.FUGNTN140Driver 62
method), 128 log_batch_now() (PyExpLab-
is_pump_accelerating() (PyExpLab- Sys.combos.LiveContinuousLogger method),
Sys.drivers.pfeiffer_turbo_pump.TurboDriver 62
method), 142 log_point() (PyExpLab-
ISeries (class in PyExpLabSys.drivers.omega_cni), 137 Sys.combos.LiveContinuousLogger method),
iter_cycles (PyExpLabSys.file_parsers.specs.Region at- 62
tribute), 68 log_point_now() (PyExpLab-
iter_scans (PyExpLabSys.file_parsers.specs.Region at- Sys.combos.LiveContinuousLogger method),
tribute), 68 62
iv_scan() (PyExpLabSys.drivers.keithley_smu.KeithleySMU
method), 134 M
MAIL_HOST (in module PyExpLab-
K Sys.common.utilities), 57
KBIOData (class in PyExpLabSys.drivers.bio_logic), 86 main() (in module PyExpLab-
KeithleySMU (class in PyExpLab- Sys.drivers.agilent_34410A), 112
Sys.drivers.keithley_2700), 133 main() (in module PyExpLabSys.drivers.crowcon), 118
KeithleySMU (class in PyExpLab- main() (in module PyExpLabSys.drivers.tenma), 151
Sys.drivers.keithley_smu), 133 main() (in module PyExpLabSys.settings), 64
KJLC300 (class in PyExpLab- mass_scan() (PyExpLab-
Sys.drivers.kjlc_pressure_gauge), 134 Sys.drivers.pfeiffer_qmg422.qmg_422
method), 141
L mass_time() (PyExpLab-
L3G4200D (class in PyExpLab- Sys.drivers.pfeiffer_qmg422.qmg_422
Sys.drivers.stmicroelectronics_l3g4200d), method), 141
148 MAX_EMAILS_PER_PERIOD (in module PyExpLab-
Sys.common.utilities), 57
Index 177
measurement_ids (PyExpLab- OmegaD6400 (class in PyExpLab-

Sys.common.database_saver.DataSetSaver Sys.drivers.omega_D6400), 136
attribute), 21 OmronD6fph (class in PyExpLab-
measurement_running() (PyExpLab- Sys.drivers.omron_d6fph), 139
Sys.drivers.pfeiffer_qmg422.qmg_422 operate() (PyExpLabSys.drivers.specs_iqe11.Puiqe11
measurements_table (PyExpLab- operate() (PyExpLabSys.drivers.specs_XRC1000.XRC1000
Sys.common.database_saver.DataSetSaver method), 145
attribute), 21 output() (PyExpLabSys.drivers.fug.FUGNTN140Driver
Megatec (class in PyExpLabSys.drivers.innova), 130 method), 128
metadata (PyExpLabSys.file_parsers.chemstation.CHFile output_measurements() (PyExpLab-
attribute), 69 Sys.drivers.galaxy_3500.Galaxy3500 method),
MIR (class in PyExpLabSys.drivers.bio_logic), 95 129
Mks925 (class in PyExpLabSys.drivers.mks_925_pirani), output_state() (PyExpLab-
135 Sys.drivers.keithley_smu.KeithleySMU
Mks937b (class in PyExpLabSys.drivers.mks_937b), 135 method), 133
MksGSeries (class in PyExpLab- output_status() (PyExpLab-
Sys.drivers.mks_g_series), 136 Sys.drivers.cpx400dp.CPX400DPDriver
MMA7660FC (class in PyExpLab- method), 115
Sys.drivers.freescale_mma7660fc), 126
module_test() (in module PyExpLab- P
Sys.drivers.dataq_binary), 121 pack() (PyExpLabSys.drivers.brooks_s_protocol.Brooks
monitor_current() (PyExpLab- method), 113
Sys.drivers.fug.FUGNTN140Driver method), packet_size() (PyExpLab-
monitor_voltage() (PyExpLab- method), 121
Sys.drivers.fug.FUGNTN140Driver method), packet_sizes (PyExpLab-
128 Sys.drivers.dataq_binary.DataQBinary at-
move_cursor() (PyExpLab- tribute), 120
Sys.drivers.four_d_systems.PicasoCommon parse_utf16_string() (in module PyExpLab-
method), 101 Sys.file_parsers.chemstation), 71
move_origin() (PyExpLab- PicasoCommon (class in PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.drivers.four_d_systems), 100
method), 104 PicasoException, 106
PicasouLCD28PTU (class in PyExpLab-
N Sys.drivers.four_d_systems), 106
name (PyExpLabSys.drivers.bio_logic.DataField at- plot (PyExpLabSys.common.plotters.ContinuousPlotter
tribute), 81 attribute), 33
NoInjections, 70 plot (PyExpLabSys.common.plotters.DataPlotter at-
NONE_RESPONSE (in module PyExpLab- tribute), 32
Sys.common.loggers), 27 poke() (PyExpLabSys.common.sockets.CommonDataPullSocket
NoneResponse (class in PyExpLabSys.common.loggers), method), 48
27 poke() (PyExpLabSys.common.sockets.DataPushSocket
NotXPSException, 69 method), 51
Polyscience4100 (class in PyExpLab-
O Sys.drivers.polyscience_4100), 143
OCV (class in PyExpLabSys.drivers.bio_logic), 88 PortStillReserved, 52
OLD_DATA (in module PyExpLabSys.common.sockets), pressure_gauge() (PyExpLabSys.drivers.pfeiffer.TPG26x
53 method), 108
oldest_barcode_from_queue (PyExpLab- pressure_gauges() (PyExpLab-
Sys.drivers.vivo_technologies.ThreadedBarcodeReader Sys.drivers.pfeiffer.TPG26x method), 108
attribute), 152 pressure_unit() (PyExpLab-
OmegaBus (class in PyExpLabSys.drivers.omegabus), Sys.drivers.edwards_agc.EdwardsAGC
138 method), 123
178 Index
pressure_unit() (PyExpLab- PyExpLabSys.drivers.edwards_nxds (module), 123

Sys.drivers.mks_937b.Mks937b method), PyExpLabSys.drivers.epimax (module), 124
135 PyExpLabSys.drivers.four_d_systems (module), 99
pressure_unit() (PyExpLabSys.drivers.pfeiffer.TPG26x PyExpLabSys.drivers.freescale_mma7660fc (module),
method), 109 126
print_library_logger_names() (in module PyExpLab- PyExpLabSys.drivers.fug (module), 126
Sys.common.utilities), 58 PyExpLabSys.drivers.galaxy_3500 (module), 129
print_settings() (PyExpLabSys.settings.Settings method), PyExpLabSys.drivers.honeywell_6000 (module), 129
64 PyExpLabSys.drivers.inficon_sqm160 (module), 130
print_states() (PyExpLab- PyExpLabSys.drivers.innova (module), 130
Sys.drivers.fug.FUGNTN140Driver method), PyExpLabSys.drivers.intellemetrics_il800 (module), 132
128 PyExpLabSys.drivers.isotech_ips (module), 132
program_number() (PyExpLab- PyExpLabSys.drivers.keithley_2700 (module), 133
Sys.drivers.pfeiffer.TPG26x method), 108 PyExpLabSys.drivers.keithley_smu (module), 133
Puiqe11 (class in PyExpLabSys.drivers.specs_iqe11), 145 PyExpLabSys.drivers.kjlc_pressure_gauge (module), 134
PullUDPHandler (class in PyExpLab- PyExpLabSys.drivers.lascar (module), 134
Sys.common.sockets), 46 PyExpLabSys.drivers.mks_925_pirani (module), 135
pump_controller_status() (PyExpLab- PyExpLabSys.drivers.mks_937b (module), 135
Sys.drivers.edwards_nxds.EdwardsNxds PyExpLabSys.drivers.mks_g_series (module), 136
method), 123 PyExpLabSys.drivers.mks_pi_pc (module), 136
PUSH_ACK (in module PyExpLab- PyExpLabSys.drivers.NGC2D (module), 111
Sys.common.sockets), 53 PyExpLabSys.drivers.omega_cn7800 (module), 137
PUSH_ERROR (in module PyExpLab- PyExpLabSys.drivers.omega_cni (module), 137
Sys.common.sockets), 53 PyExpLabSys.drivers.omega_D6400 (module), 136
PUSH_EXCEP (in module PyExpLab- PyExpLabSys.drivers.omegabus (module), 138
Sys.common.sockets), 53 PyExpLabSys.drivers.omron_d6fph (module), 139
PUSH_RET (in module PyExpLabSys.common.sockets), PyExpLabSys.drivers.pfeiffer (module), 107
53 PyExpLabSys.drivers.pfeiffer_qmg420 (module), 139
PushUDPHandler (class in PyExpLab- PyExpLabSys.drivers.pfeiffer_qmg422 (module), 139
Sys.common.sockets), 49 PyExpLabSys.drivers.pfeiffer_turbo_pump (module),
put_string() (PyExpLab- 141
Sys.drivers.four_d_systems.PicasoCommon PyExpLabSys.drivers.polyscience_4100 (module), 143
method), 101 PyExpLabSys.drivers.rosemount_nga2000 (module), 143
PVCCommon (class in PyExpLabSys.drivers.epimax), PyExpLabSys.drivers.scpi (module), 143
124 PyExpLabSys.drivers.specs_iqe11 (module), 145
PVCi (class in PyExpLabSys.drivers.epimax), 125 PyExpLabSys.drivers.specs_XRC1000 (module), 144
PyExpLabSys.combos (module), 61 PyExpLabSys.drivers.srs_sr630 (module), 147
PyExpLabSys.common.database_saver (module), 21 PyExpLabSys.drivers.stahl_hv_400 (module), 147
PyExpLabSys.common.loggers (module), 27 PyExpLabSys.drivers.stmicroelectronics_ais328dq (mod-
PyExpLabSys.common.plotters (module), 30 ule), 148
PyExpLabSys.common.plotters_backend_qwt (module), PyExpLabSys.drivers.stmicroelectronics_l3g4200d
33 (module), 148
PyExpLabSys.common.sockets (module), 45 PyExpLabSys.drivers.tenma (module), 148
PyExpLabSys.common.utilities (module), 56 PyExpLabSys.drivers.vivo_technologies (module), 151
PyExpLabSys.drivers.agilent_34410A (module), 111 PyExpLabSys.drivers.wpi_al1000 (module), 152
PyExpLabSys.drivers.agilent_34972A (module), 112 PyExpLabSys.drivers.xgs600 (module), 153
PyExpLabSys.drivers.bio_logic (module), 80 PyExpLabSys.file_parsers.chemstation (module), 69
PyExpLabSys.drivers.bronkhorst (module), 113 PyExpLabSys.file_parsers.specs (module), 65
PyExpLabSys.drivers.brooks_s_protocol (module), 113 PyExpLabSys.settings (module), 63
PyExpLabSys.drivers.cpx400dp (module), 114
PyExpLabSys.drivers.crowcon (module), 115 Q
PyExpLabSys.drivers.dataq_binary (module), 118 qmg_422 (class in PyExpLab-
PyExpLabSys.drivers.dataq_comm (module), 122 Sys.drivers.pfeiffer_qmg422), 139
PyExpLabSys.drivers.edwards_agc (module), 122
Index 179
query_voltage() (PyExpLab- 135

Sys.drivers.stahl_hv_400.StahlHV400 read_all_pressures() (PyExpLab-
method), 147 Sys.drivers.xgs600.XGS600Driver method),
queue (PyExpLabSys.common.database_saver.SqlSaver 153
attribute), 25 read_ambient_temperature() (PyExpLab-
queue (PyExpLabSys.common.sockets.DataPushSocket Sys.drivers.polyscience_4100.Polyscience4100
attribute), 51 method), 143
QwtPlot (class in PyExpLab- read_anode_power() (PyExpLab-
Sys.common.plotters_backend_qwt), 33 Sys.drivers.specs_XRC1000.XRC1000
method), 145
R read_anode_voltage() (PyExpLab-
raise_if_not_set() (in module PyExpLab- Sys.drivers.specs_XRC1000.XRC1000
Sys.drivers.epimax), 126 method), 145
ramp_current() (PyExpLab- read_barcode() (PyExpLab-
Sys.drivers.fug.FUGNTN140Driver method), Sys.drivers.vivo_technologies.BlockingBarcodeReader
128 method), 151
ramp_current_running() (PyExpLab- read_bool() (PyExpLabSys.drivers.crowcon.Vortex
Sys.drivers.fug.FUGNTN140Driver method), method), 117
128 read_capacity() (PyExpLab-
ramp_voltage() (PyExpLab- Sys.drivers.bronkhorst.Bronkhorst method),
Sys.drivers.fug.FUGNTN140Driver method), 113
128 read_channel() (PyExpLab-
ramp_voltage_running() (PyExpLab- Sys.drivers.srs_sr630.SRS_SR630 method),
128 read_configuration() (PyExpLab-
range_codes() (PyExpLab- Sys.drivers.agilent_34410A.Agilent34410ADriver
Sys.drivers.omega_D6400.OmegaD6400 method), 112
method), 137 read_configuration() (PyExpLab-
rate() (PyExpLabSys.drivers.inficon_sqm160.InficonSQM160 Sys.drivers.agilent_34972A.Agilent34972ADriver
rate() (PyExpLabSys.drivers.intellemetrics_il800.IL800 read_configuration_mode() (PyExpLab-
method), 132 Sys.drivers.cpx400dp.CPX400DPDriver
RATING_INFORMATION_FIELDS (in module PyEx- method), 114
pLabSys.drivers.innova), 130 read_counter_value() (PyExpLab-
read() (PyExpLabSys.drivers.agilent_34410A.Agilent34410ADriver Sys.drivers.bronkhorst.Bronkhorst method),
method), 112 113
read() (PyExpLabSys.drivers.dataq_binary.DataQBinary read_current() (PyExpLab-
method), 121 Sys.drivers.keithley_smu.KeithleySMU
read() (PyExpLabSys.drivers.keithley_2700.KeithleySMU method), 133
method), 133 read_current_gas_type() (PyExpLab-
read_acceleration_voltage() (PyExpLab- Sys.drivers.mks_g_series.MksGSeries
Sys.drivers.specs_iqe11.Puiqe11 method), method), 136
146 read_current_limit() (PyExpLab-
read_actual_current() (PyExpLab- Sys.drivers.cpx400dp.CPX400DPDriver
Sys.drivers.cpx400dp.CPX400DPDriver method), 114
method), 114 read_current_stepsize() (PyExpLab-
read_actual_voltage() (PyExpLab- Sys.drivers.cpx400dp.CPX400DPDriver
method), 114 read_device_address() (PyExpLab-
read_address() (PyExpLab- Sys.drivers.mks_g_series.MksGSeries
Sys.drivers.omega_D6400.OmegaD6400 method), 136
method), 137 read_drive_power() (PyExpLab-
read_all_pressures() (PyExpLab- Sys.drivers.pfeiffer_turbo_pump.TurboDriver
Sys.drivers.mks_937b.Mks937b method), method), 142
180 Index
read_emission_current() (PyExpLab- read_operating_hours() (PyExpLab-

Sys.drivers.specs_iqe11.Puiqe11 method), Sys.drivers.pfeiffer_turbo_pump.TurboDriver
146 method), 142
read_emission_current() (PyExpLab- read_output_status() (PyExpLab-
Sys.drivers.specs_XRC1000.XRC1000 Sys.drivers.cpx400dp.CPX400DPDriver
read_filament_current() (PyExpLab- read_preamp_range() (PyExpLab-
Sys.drivers.specs_iqe11.Puiqe11 method), Sys.drivers.pfeiffer_qmg422.qmg_422
146 method), 140
read_filament_current() (PyExpLab- read_pressure() (PyExpLab-
Sys.drivers.specs_XRC1000.XRC1000 Sys.drivers.edwards_agc.EdwardsAGC
read_filament_voltage() (PyExpLab- read_pressure() (PyExpLab-
Sys.drivers.specs_iqe11.Puiqe11 method), Sys.drivers.kjlc_pressure_gauge.KJLC300
146 method), 134
read_filament_voltage() (PyExpLab- read_pressure() (PyExpLab-
Sys.drivers.specs_XRC1000.XRC1000 Sys.drivers.mks_925_pirani.Mks925 method),
method), 145 135
read_flow() (PyExpLab- read_pressure() (PyExpLab-
Sys.drivers.bronkhorst.Bronkhorst method), Sys.drivers.omron_d6fph.OmronD6fph
113 method), 139
Sys.drivers.brooks_s_protocol.Brooks Sys.drivers.polyscience_4100.Polyscience4100
Sys.drivers.mks_g_series.MksGSeries Sys.drivers.xgs600.XGS600Driver method),
method), 136 154
read_flow_rate() (PyExpLab- read_pressure_gauge() (PyExpLab-
Sys.drivers.polyscience_4100.Polyscience4100 Sys.drivers.mks_937b.Mks937b method),
method), 143 135
read_full_range() (PyExpLab- read_pressure_unit() (PyExpLab-
Sys.drivers.brooks_s_protocol.Brooks Sys.drivers.xgs600.XGS600Driver method),
method), 114 154
read_full_scale_range() (PyExpLab- read_pump_status() (PyExpLab-
Sys.drivers.mks_g_series.MksGSeries Sys.drivers.edwards_nxds.EdwardsNxds
read_gas_mode() (PyExpLab- read_pump_temperature() (PyExpLab-
Sys.drivers.pfeiffer_turbo_pump.TurboDriver Sys.drivers.edwards_nxds.EdwardsNxds
read_H1() (PyExpLabSys.drivers.fug.FUGNTN140Driver read_pump_type() (PyExpLab-
method), 128 Sys.drivers.edwards_nxds.EdwardsNxds
read_max() (PyExpLabSys.drivers.omegabus.OmegaBus method), 123
method), 138 read_register() (PyExpLabSys.drivers.crowcon.Vortex
read_measurements() (PyExpLab- method), 117
Sys.drivers.dataq_comm.DataQ method), read_rotation_speed() (PyExpLab-
122 Sys.drivers.pfeiffer_turbo_pump.TurboDriver
read_min() (PyExpLabSys.drivers.omegabus.OmegaBus method), 142
method), 138 read_run_hours() (PyExpLab-
read_normal_speed_threshold() (PyExpLab- Sys.drivers.edwards_nxds.EdwardsNxds
Sys.drivers.edwards_nxds.EdwardsNxds method), 123
method), 123 read_run_hours() (PyExpLab-
read_open_status() (PyExpLab- Sys.drivers.mks_g_series.MksGSeries
Sys.drivers.srs_sr630.SRS_SR630 method), method), 136
147 read_scan_interval() (PyExpLab-
Index 181
Sys.drivers.agilent_34972A.Agilent34972ADriver Sys.drivers.kjlc_pressure_gauge.KJLC300
read_scan_list() (PyExpLab- read_software_version() (PyExpLab-
Sys.drivers.agilent_34972A.Agilent34972ADriver Sys.drivers.scpi.SCPI method), 144
method), 112 read_software_version() (PyExpLab-
read_sealing_gas() (PyExpLab- Sys.drivers.xgs600.XGS600Driver method),
Sys.drivers.pfeiffer_turbo_pump.TurboDriver 154
method), 142 read_sputter_current() (PyExpLab-
read_sem_voltage() (PyExpLab- Sys.drivers.specs_iqe11.Puiqe11 method),
Sys.drivers.pfeiffer_qmg422.qmg_422 146
method), 140 read_standby_speed() (PyExpLab-
read_sensor_types() (PyExpLab- Sys.drivers.edwards_nxds.EdwardsNxds
Sys.drivers.mks_937b.Mks937b method), method), 124
135 read_status() (PyExpLab-
read_serial() (PyExpLab- Sys.drivers.polyscience_4100.Polyscience4100
Sys.drivers.bronkhorst.Bronkhorst method), method), 143
113 read_string() (PyExpLabSys.drivers.crowcon.Vortex
read_serial() (PyExpLab- method), 118
Sys.drivers.mks_925_pirani.Mks925 method), read_temperature() (PyExpLab-
135 Sys.drivers.omega_cn7800.CN7800 method),
read_serial_number() (PyExpLab- 137
Sys.drivers.mks_g_series.MksGSeries read_temperature() (PyExpLab-
method), 136 Sys.drivers.omega_cni.ISeries method),
read_serial_number() (PyExpLab- 138
Sys.drivers.srs_sr630.SRS_SR630 method), read_temperature() (PyExpLab-
147 Sys.drivers.omron_d6fph.OmronD6fph
read_serial_numbers() (PyExpLab- method), 139
Sys.drivers.edwards_nxds.EdwardsNxds read_temperature() (PyExpLab-
method), 123 Sys.drivers.pfeiffer_turbo_pump.TurboDriver
read_service_status() (PyExpLab- method), 142
Sys.drivers.edwards_nxds.EdwardsNxds read_temperature() (PyExpLab-
method), 124 Sys.drivers.polyscience_4100.Polyscience4100
read_set_rotation_speed() (PyExpLab- method), 143
Sys.drivers.pfeiffer_turbo_pump.TurboDriver read_temperature() (PyExpLab-
method), 142 Sys.drivers.stahl_hv_400.StahlHV400
read_set_voltage() (PyExpLab- method), 147
Sys.drivers.cpx400dp.CPX400DPDriver read_temperature_energy_module() (PyExpLab-
method), 114 Sys.drivers.specs_iqe11.Puiqe11 method),
read_setpoint() (PyExpLab- 146
Sys.drivers.bronkhorst.Bronkhorst method), read_timestep() (PyExpLab-
113 Sys.drivers.pfeiffer_qmg422.qmg_422
read_setpoint() (PyExpLab- method), 140
Sys.drivers.mks_g_series.MksGSeries read_unit() (PyExpLabSys.drivers.bronkhorst.Bronkhorst
read_setpoint() (PyExpLab- read_unit() (PyExpLab-
Sys.drivers.polyscience_4100.Polyscience4100 Sys.drivers.polyscience_4100.Polyscience4100
read_setup() (PyExpLab- read_value() (PyExpLab-
Sys.drivers.omegabus.OmegaBus method), Sys.drivers.omega_D6400.OmegaD6400
138 method), 137
read_single_scan() (PyExpLab- read_value() (PyExpLab-
Sys.drivers.agilent_34972A.Agilent34972ADriver Sys.drivers.omegabus.OmegaBus method),
method), 112 138
read_software_version() (PyExpLab- read_value() (PyExpLab-
182 Index
Sys.drivers.omron_d6fph.OmronD6fph method), 127

method), 139 reset_device() (PyExpLabSys.drivers.omega_cni.ISeries
read_value() (PyExpLab- method), 138
Sys.drivers.pfeiffer_turbo_pump.TurboLogger reset_device() (PyExpLabSys.drivers.scpi.SCPI method),
method), 141 144
read_values() (PyExpLab- reset_scan_list() (PyExpLab-
Sys.drivers.freescale_mma7660fc.MMA7660FC Sys.drivers.dataq_comm.DataQ method),
method), 126 122
read_values() (PyExpLab- retract_pump() (PyExpLab-
Sys.drivers.honeywell_6000.HIH6130 Sys.drivers.wpi_al1000.AL1000 method),
method), 129 153
read_values() (PyExpLab- reverse_dict() (in module PyExpLab-
Sys.drivers.stmicroelectronics_ais328dq.AIS328DQTR Sys.drivers.bio_logic), 98
method), 148 rs232_communication_test() (PyExpLab-
read_values() (PyExpLab- Sys.drivers.pfeiffer.TPG26x method), 109
Sys.drivers.stmicroelectronics_l3g4200d.L3G4200D
run() (PyExpLabSys.common.database_saver.SqlSaver
read_vent_mode() (PyExpLab- run() (PyExpLabSys.common.loggers.ContinuousLogger
Sys.drivers.pfeiffer_turbo_pump.TurboDriver method), 29
method), 142 run() (PyExpLabSys.common.loggers.InterruptableThread
read_voltage() (PyExpLab- method), 27
Sys.drivers.keithley_smu.KeithleySMU run() (PyExpLabSys.common.sockets.CallBackThread
read_voltage_stepsize() (PyExpLab- run() (PyExpLabSys.common.sockets.CommonDataPullSocket
method), 114 run() (PyExpLabSys.common.sockets.DataPushSocket
read_voltages() (PyExpLab- method), 51
Sys.drivers.pfeiffer_qmg422.qmg_422 run() (PyExpLabSys.drivers.vivo_technologies.ThreadedBarcodeReader
read_wait_time (PyExpLab- run_module() (in module PyExpLab-
Sys.drivers.dataq_binary.DataQBinary at- Sys.common.database_saver), 26
tribute), 119 run_module() (in module PyExpLab-
read_water_flow() (PyExpLab- Sys.common.sockets), 54
Sys.drivers.specs_XRC1000.XRC1000 run_module() (in module PyExpLabSys.drivers.epimax),
method), 144 126
recall_memory() (PyExpLab-
Sys.drivers.tenma.TenmaBase method), S
150 sample_rate() (PyExpLab-
Region (class in PyExpLabSys.file_parsers.specs), 68 Sys.drivers.dataq_binary.DataQBinary
RegionGroup (class in PyExpLabSys.file_parsers.specs), method), 120
68 save_memory() (PyExpLab-
regions_iter (PyExpLabSys.file_parsers.specs.SpecsFile Sys.drivers.tenma.TenmaBase method),
attribute), 67 150
register_to_bool() (in module PyExpLab- save_point() (PyExpLab-
Sys.drivers.crowcon), 118 Sys.common.database_saver.ContinuousDataSaver
remote_enable() (PyExpLab- method), 25
Sys.drivers.specs_iqe11.Puiqe11 method), save_point() (PyExpLab-
146 Sys.common.database_saver.DataSetSaver
remote_enable() (PyExpLab- method), 23
Sys.drivers.specs_XRC1000.XRC1000 save_point_now() (PyExpLab-
method), 145 Sys.common.database_saver.ContinuousDataSaver
reset() (PyExpLabSys.common.sockets.LiveSocket method), 24
method), 53 save_points_batch() (PyExpLab-
reset() (PyExpLabSys.drivers.fug.FUGNTN140Driver Sys.common.database_saver.DataSetSaver
Index 183
method), 23 128
scan_list() (PyExpLab- set_current() (PyExpLab-
Sys.drivers.dataq_binary.DataQBinary Sys.drivers.keithley_smu.KeithleySMU
SCPI (class in PyExpLabSys.drivers.scpi), 143 set_current() (PyExpLabSys.drivers.tenma.TenmaBase
scpi_comm() (PyExpLabSys.drivers.scpi.SCPI method), method), 150
144 set_current_limit() (PyExpLab-
screen_mode() (PyExpLab- Sys.drivers.cpx400dp.CPX400DPDriver
Sys.drivers.four_d_systems.PicasoCommon method), 114
method), 104 set_current_limit() (PyExpLab-
search_regions() (PyExpLab- Sys.drivers.isotech_ips.IPS method), 132
Sys.file_parsers.specs.SpecsFile method), set_current_limit() (PyExpLab-
search_regions_iter() (PyExpLab- method), 133
Sys.file_parsers.specs.SpecsFile method), set_current_measure_range() (PyExpLab-
select_measurement_function() (PyExpLab- method), 133
Sys.drivers.agilent_34410A.Agilent34410ADriverset_current_stepsize() (PyExpLab-
method), 111 Sys.drivers.cpx400dp.CPX400DPDriver
select_measurement_function() (PyExpLab- method), 114
Sys.drivers.keithley_2700.KeithleySMU set_device_address() (PyExpLab-
method), 133 Sys.drivers.mks_g_series.MksGSeries
sem_status() (PyExpLab- method), 136
Sys.drivers.pfeiffer_qmg422.qmg_422 set_direction() (PyExpLab-
method), 140 Sys.drivers.wpi_al1000.AL1000 method),
Sequence (class in PyExpLab- 153
Sys.file_parsers.chemstation), 70 set_dual_output() (PyExpLab-
serial_number() (PyExpLab- Sys.drivers.cpx400dp.CPX400DPDriver
Sys.drivers.dataq_comm.DataQ method), method), 114
122 set_emission_on() (PyExpLab-
set_ascii_mode() (PyExpLab- Sys.drivers.xgs600.XGS600Driver method),
Sys.drivers.dataq_comm.DataQ method), 154
122 set_float_mode() (PyExpLab-
set_auto_input_z() (PyExpLab- Sys.drivers.dataq_comm.DataQ method),
Sys.drivers.agilent_34410A.Agilent34410ADriver 122
method), 112 set_flow() (PyExpLabSys.drivers.bronkhorst.Bronkhorst
set_batch() (PyExpLabSys.common.sockets.LiveSocket method), 113
method), 52 set_flow() (PyExpLabSys.drivers.brooks_s_protocol.Brooks
set_batch_now() (PyExpLab- method), 114
Sys.common.sockets.LiveSocket method), set_flow() (PyExpLabSys.drivers.mks_g_series.MksGSeries
53 method), 136
set_beep() (PyExpLabSys.drivers.tenma.TenmaBase set_fun() (PyExpLabSys.drivers.wpi_al1000.AL1000
set_channel() (PyExpLab- set_ilimit_to_max() (PyExpLab-
Sys.drivers.pfeiffer_qmg422.qmg_422 Sys.drivers.isotech_ips.IPS method), 132
method), 140 set_integration_time() (PyExpLab-
set_comm_speed() (PyExpLab- Sys.drivers.agilent_34972A.Agilent34972ADriver
Sys.drivers.mks_925_pirani.Mks925 method), method), 112
135 set_integration_time() (PyExpLab-
set_control_mode() (PyExpLab- Sys.drivers.keithley_smu.KeithleySMU
Sys.drivers.bronkhorst.Bronkhorst method), method), 133
113 set_last_to_none() (PyExpLab-
set_current() (PyExpLab- Sys.common.sockets.DataPushSocket method),
184 Index
set_output() (PyExpLabSys.drivers.tenma.TenmaBase set_vlimit_to_max() (PyExpLab-

method), 150 Sys.drivers.isotech_ips.IPS method), 132
set_output_voltage() (PyExpLab- set_vol() (PyExpLabSys.drivers.wpi_al1000.AL1000
Sys.drivers.isotech_ips.IPS method), 132 method), 152
set_overcurrent_protection() (PyExpLab- set_voltage() (PyExpLab-
Sys.drivers.tenma.TenmaBase method), Sys.drivers.cpx400dp.CPX400DPDriver
150 method), 114
set_overvoltage_protection() (PyExpLab- set_voltage() (PyExpLab-
Sys.drivers.tenma.TenmaBase method), Sys.drivers.fug.FUGNTN140Driver method),
150 128
set_point() (PyExpLab- set_voltage() (PyExpLab-
Sys.common.sockets.DataPullSocket method), Sys.drivers.keithley_smu.KeithleySMU
48 method), 133
set_point() (PyExpLab- set_voltage() (PyExpLab-
Sys.common.sockets.DateDataPullSocket Sys.drivers.stahl_hv_400.StahlHV400
set_point() (PyExpLabSys.common.sockets.LiveSocket set_voltage() (PyExpLabSys.drivers.tenma.TenmaBase
set_point_now() (PyExpLab- set_voltage_limit() (PyExpLab-
Sys.common.sockets.DateDataPullSocket Sys.drivers.isotech_ips.IPS method), 132
method), 49 set_voltage_limit() (PyExpLab-
set_point_now() (PyExpLab- Sys.drivers.keithley_smu.KeithleySMU
Sys.common.sockets.LiveSocket method), method), 133
53 set_voltage_stepsize() (PyExpLab-
set_position() (PyExpLab- Sys.drivers.cpx400dp.CPX400DPDriver
Sys.drivers.four_d_systems.Button method), method), 114
106 Settings (class in PyExpLabSys.settings), 64
set_rate() (PyExpLabSys.drivers.wpi_al1000.AL1000 SETTINGS (in module PyExpLabSys.common.utilities),
method), 152 56
set_relay_status() (PyExpLabSys.drivers.isotech_ips.IPS settings (PyExpLabSys.settings.Settings attribute), 64
method), 132 settings_names (PyExpLabSys.settings.Settings at-
set_run_state() (PyExpLab- tribute), 64
Sys.drivers.edwards_nxds.EdwardsNxds show_film_parameters() (PyExpLab-
method), 123 Sys.drivers.inficon_sqm160.InficonSQM160
set_safe_mode() (PyExpLab- method), 130
Sys.drivers.wpi_al1000.AL1000 method), show_version() (PyExpLab-
153 Sys.drivers.inficon_sqm160.InficonSQM160
set_scan_interval() (PyExpLab- method), 130
Sys.drivers.agilent_34972A.Agilent34972ADriversimple_convert() (in module PyExpLab-
method), 112 Sys.file_parsers.specs), 66
set_scan_list() (PyExpLab- simulation() (PyExpLab-
Sys.drivers.agilent_34972A.Agilent34972ADriver Sys.drivers.pfeiffer_qmg422.qmg_422
set_setpoint() (PyExpLab- socket_server_status() (in module PyExpLab-
Sys.drivers.polyscience_4100.Polyscience4100 Sys.common.sockets), 46
method), 143 software_version() (PyExpLab-
set_smission_off() (PyExpLab- Sys.drivers.edwards_agc.EdwardsAGC
Sys.drivers.xgs600.XGS600Driver method), method), 123
154 SP150 (class in PyExpLabSys.drivers.bio_logic), 86
set_standby_mode() (PyExpLab- SP300SERIES (in module PyExpLab-
Sys.drivers.edwards_nxds.EdwardsNxds Sys.drivers.bio_logic), 98
method), 124 SpecsFile (class in PyExpLabSys.file_parsers.specs), 67
set_unit() (PyExpLabSys.drivers.srs_sr630.SRS_SR630 SPEIS (class in PyExpLabSys.drivers.bio_logic), 93
method), 147 sql_saver (PyExpLabSys.common.database_saver.DataSetSaver
Index 185
attribute), 22 stop() (PyExpLabSys.common.sockets.CommonDataPullSocket

SqlSaver (class in PyExpLab- method), 48
Sys.common.database_saver), 25 stop() (PyExpLabSys.common.sockets.DataPushSocket
SRS_SR630 (class in PyExpLabSys.drivers.srs_sr630), method), 51
147 stop() (PyExpLabSys.common.sockets.LiveSocket
StahlHV400 (class in PyExpLab- method), 52
Sys.drivers.stahl_hv_400), 147 stop() (PyExpLabSys.drivers.dataq_binary.DataQBinary
standby() (PyExpLabSys.drivers.specs_iqe11.Puiqe11 method), 120
method), 146 stop() (PyExpLabSys.drivers.fug.FUGNTN140Driver
standby() (PyExpLabSys.drivers.specs_XRC1000.XRC1000 method), 128
method), 145 stop() (PyExpLabSys.drivers.pfeiffer_turbo_pump.CursesTui
start() (PyExpLabSys.combos.LiveContinuousLogger method), 141
method), 62 stop() (PyExpLabSys.drivers.specs_iqe11.CursesTui
start() (PyExpLabSys.common.database_saver.ContinuousDataSaver method), 145
method), 25 stop() (PyExpLabSys.drivers.specs_XRC1000.CursesTui
start() (PyExpLabSys.common.database_saver.DataSetSaver method), 144
method), 24 stop_channel() (PyExpLab-
start() (PyExpLabSys.common.sockets.LiveSocket Sys.drivers.bio_logic.GeneralPotentiostat
start() (PyExpLabSys.drivers.dataq_binary.DataQBinary stop_measurement() (PyExpLab-
method), 120 Sys.drivers.dataq_comm.DataQ method),
start_channel() (PyExpLab- 122
Sys.drivers.bio_logic.GeneralPotentiostat structure_to_dict() (in module PyExpLab-
start_measurement() (PyExpLab-
Sys.drivers.dataq_comm.DataQ method), T
122 tc_types() (PyExpLabSys.drivers.srs_sr630.SRS_SR630
start_measurement() (PyExpLab- method), 147
Sys.drivers.pfeiffer_qmg422.qmg_422 TECCParam (class in PyExpLabSys.drivers.bio_logic),
method), 140 97
StartupException, 28 TECCParams (class in PyExpLabSys.drivers.bio_logic),
STATES (in module PyExpLabSys.drivers.bio_logic), 98 97
Status (class in PyExpLabSys.drivers.crowcon), 115 Technique (class in PyExpLabSys.drivers.bio_logic), 87
status() (PyExpLabSys.drivers.tenma.TenmaBase TECHNIQUE_IDENTIFIERS (in module PyExpLab-
STATUS_INQUIRY_BOOLEANS (in module PyEx- TECHNIQUE_IDENTIFIERS_TO_CLASS (in module
pLabSys.drivers.innova), 130 PyExpLabSys.drivers.bio_logic), 98
STATUS_INQUIRY_NAMES (in module PyExpLab- TechniqueArgument (class in PyExpLab-
Sys.drivers.innova), 130 Sys.drivers.bio_logic), 82
status_to_bin() (PyExpLab- temperature() (PyExpLab-
Sys.drivers.edwards_nxds.EdwardsNxds Sys.drivers.galaxy_3500.Galaxy3500 method),
method), 123 129
stop() (PyExpLabSys.combos.LiveContinuousLogger Tenma722535 (class in PyExpLabSys.drivers.tenma), 149
method), 62 Tenma722550 (class in PyExpLabSys.drivers.tenma), 149
stop() (PyExpLabSys.common.database_saver.ContinuousDataSaver
Tenma722930 (class in PyExpLabSys.drivers.tenma), 149
method), 25 TenmaBase (class in PyExpLabSys.drivers.tenma), 149
stop() (PyExpLabSys.common.database_saver.DataSetSavertest() (in module PyExpLabSys.drivers.fug), 129
method), 24 test_connection() (PyExpLab-
stop() (PyExpLabSys.common.database_saver.SqlSaver Sys.drivers.bio_logic.GeneralPotentiostat
stop() (PyExpLabSys.common.loggers.ContinuousLogger test_for_10_sec() (PyExpLabSys.drivers.innova.Megatec
stop() (PyExpLabSys.common.sockets.CallBackThread text_attribute() (PyExpLab-
method), 52 Sys.drivers.four_d_systems.PicasoCommon
186 Index
method), 103 Sys.drivers.pfeiffer_turbo_pump), 141

text_background_color() (PyExpLab- TurboLogger (class in PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.drivers.pfeiffer_turbo_pump), 141
method), 102 TurboReader (class in PyExpLab-
text_factor() (PyExpLab- Sys.drivers.pfeiffer_turbo_pump), 141
Sys.drivers.four_d_systems.PicasoCommon turn_pump_on() (PyExpLab-
method), 103 Sys.drivers.pfeiffer_turbo_pump.TurboDriver
text_foreground_color() (PyExpLab- method), 142
Sys.drivers.four_d_systems.PicasoCommon turn_unit_on() (PyExpLab-
method), 102 Sys.drivers.polyscience_4100.Polyscience4100
text_height() (PyExpLab- method), 143
Sys.drivers.four_d_systems.PicasoCommon type (PyExpLabSys.drivers.bio_logic.DataField at-
method), 102 tribute), 82
text_width() (PyExpLab- type (PyExpLabSys.drivers.bio_logic.TechniqueArgument
Sys.drivers.four_d_systems.PicasoCommon attribute), 82
method), 102 TYPE_FROM_STRING (in module PyExpLab-
text_x_gap() (PyExpLab- Sys.common.sockets), 54
Sys.drivers.four_d_systems.PicasoCommon
method), 103 U
text_y_gap() (PyExpLab- unix_timestamp (PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.file_parsers.specs.Region attribute),
method), 103 69
thickness() (PyExpLab- unix_timestamp (PyExpLab-
Sys.drivers.inficon_sqm160.InficonSQM160 Sys.file_parsers.specs.SpecsFile attribute),
method), 130 67
thickness() (PyExpLab- UNKNOWN_COMMAND (in module PyExpLab-
Sys.drivers.intellemetrics_il800.IL800 Sys.common.sockets), 53
method), 132 update() (PyExpLabSys.common.plotters.ContinuousPlotter
ThreadedBarcodeReader (class in PyExpLab- method), 33
Sys.drivers.vivo_technologies), 151 update() (PyExpLabSys.common.plotters.DataPlotter
timeout_query() (in module PyExpLab- method), 31
Sys.common.loggers), 27 update() (PyExpLabSys.common.plotters_backend_qwt.QwtPlot
times (PyExpLabSys.file_parsers.chemstation.CHFile at- method), 34
tribute), 69 update_range_and_function() (PyExpLab-
to_ascii() (in module PyExpLab- Sys.drivers.omega_D6400.OmegaD6400
Sys.drivers.four_d_systems), 100 method), 137
to_ascii_utf8() (in module PyExpLab- update_status() (PyExpLab-
Sys.drivers.four_d_systems), 100 Sys.drivers.specs_iqe11.Puiqe11 method),
touch_detect_region() (PyExpLab- 146
Sys.drivers.four_d_systems.PicasoCommon update_status() (PyExpLab-
method), 105 Sys.drivers.specs_XRC1000.XRC1000
touch_get_coordinates() (PyExpLab- method), 145
Sys.drivers.four_d_systems.PicasoCommon updated (PyExpLabSys.common.sockets.DataPushSocket
method), 106 attribute), 51
touch_get_status() (PyExpLab- ups_information() (PyExpLab-
Sys.drivers.four_d_systems.PicasoCommon Sys.drivers.innova.Megatec method), 131
method), 105 ups_rating_information() (PyExpLab-
touch_set() (PyExpLab- Sys.drivers.innova.Megatec method), 131
Sys.drivers.four_d_systems.PicasoCommon
method), 105 V
TPG261 (class in PyExpLabSys.drivers.pfeiffer), 109 value (PyExpLabSys.common.database_saver.CustomColumn
TPG262 (class in PyExpLabSys.drivers.pfeiffer), 109 attribute), 21
TPG26x (class in PyExpLabSys.drivers.pfeiffer), 107 value (PyExpLabSys.drivers.bio_logic.TechniqueArgument
TurboDriver (class in PyExpLab- attribute), 82
Index 187
value (PyExpLabSys.drivers.crowcon.Status attribute),

115
value_str() (in module PyExpLabSys.settings), 64
values (PyExpLabSys.file_parsers.chemstation.CHFile
attribute), 69
Vortex (class in PyExpLabSys.drivers.crowcon), 115
W
wait_for_barcode (PyExpLab-
Sys.drivers.vivo_technologies.ThreadedBarcodeReader
attribute), 152
wait_for_queue_to_empty() (PyExpLab-
Sys.common.database_saver.DataSetSaver
method), 24
wait_for_queue_to_empty() (PyExpLab-
Sys.common.database_saver.SqlSaver
method), 26
waiting_samples() (PyExpLab-
Sys.drivers.pfeiffer_qmg422.qmg_422
method), 141
WARNING_EMAIL (in module PyExpLab-
Sys.common.utilities), 56
who_am_i() (PyExpLab-
Sys.drivers.stmicroelectronics_ais328dq.AIS328DQTR
method), 148
who_am_i() (PyExpLab-
Sys.drivers.stmicroelectronics_l3g4200d.L3G4200D
method), 148
write_enable() (PyExpLab-
Sys.drivers.omega_D6400.OmegaD6400
method), 137
X
x (PyExpLabSys.file_parsers.specs.Region attribute), 68
x_be (PyExpLabSys.file_parsers.specs.Region attribute),
68
XGS600Driver (class in PyExpLabSys.drivers.xgs600),
153
xgs_comm() (PyExpLab-
Sys.drivers.xgs600.XGS600Driver method),
153
XRC1000 (class in PyExpLab-
Sys.drivers.specs_XRC1000), 144
xy_values_table (PyExpLab-
Sys.common.database_saver.DataSetSaver
attribute), 22
Y
y_avg_counts (PyExpLabSys.file_parsers.specs.Region
attribute), 68
y_avg_cps (PyExpLabSys.file_parsers.specs.Region at-
tribute), 68
188 Index

Pyexplabsys

Uploaded by

Pyexplabsys

Uploaded by

PyExpLabSys Documentation

Feb 09, 2018

3 Common Software Components 21

7 Hardware Drivers Autogenerated Docs Only 111

8 How To’s 155

9 Developer Notes 157

Python Module Index 167

1.1 Project Overview

1.1.2 File parsers

1.1.3 Database Savers

1.2 Python 3 support

1.3 Module Overview

PyExpLabSys.combos (Python 2 only1 )

PyExpLabSys.settings (Python 2 only1 )

PyExpLabSys.common.flow_control_bronkhorst (Python 2 and 3)

1.2. Python 3 support 5

• Common code for Bronkhorst boxes

PyExpLabSys.common.valve_control (Python 2 and 3)

PyExpLabSys.common.plotters (Python 2 only1 )

PyExpLabSys.common.utilities (Python 2 only1 )

PyExpLabSys.common.analog_flow_control (Python 2 only1 )

PyExpLabSys.common.socket_clients (Python 2 only1 )

PyExpLabSys.common.system_status (Python 2 only1 )

PyExpLabSys.common.database_saver (Python 2 and 3)

PyExpLabSys.common.plotters_backend_qwt (Python 2 only1 )

PyExpLabSys.common.chiller_reader (Python 2 and 3)

PyExpLabSys.common.sockets (Python 2 and 3)

PyExpLabSys.common.loggers (Python 2 only1 )

PyExpLabSys.common.microreactor_temperature_control (Python 2 and 3)

PyExpLabSys.common.value_logger (Python 2 and 3)

PyExpLabSys.common.supported_versions (Python 2 and 3)

PyExpLabSys.common.decorators (Python 2 only1 )

PyExpLabSys.common.massspec.test (Python 2 only1 )

PyExpLabSys.common.massspec.channel (Python 2 only1 )

PyExpLabSys.common.massspec.qt (Python 2 only1 )

PyExpLabSys.drivers.wpi_al1000 (Python 2 only1 )

PyExpLabSys.drivers.edwards_agc (Python 2 only1 )

PyExpLabSys.drivers.NGC2D (Python 2 only1 )

PyExpLabSys.drivers.mks_937b (Python 2 and 3)

1.3. Module Overview 7

PyExpLabSys.drivers.innova (Python 2 only1 )

PyExpLabSys.drivers.freescale_mma7660fc (Python 2 and 3)

PyExpLabSys.drivers.rosemount_nga2000 (Python 2 only1 )

PyExpLabSys.drivers.specs_iqe11 (Python 2 only1 )

PyExpLabSys.drivers.intellemetrics_il800 (Python 2 only1 )

PyExpLabSys.drivers.fug (Python 2 only)

PyExpLabSys.drivers.four_d_systems (Python 2 only1 )

PyExpLabSys.drivers.vogtlin (Python 2 and 3)

PyExpLabSys.drivers.stmicroelectronics_ais328dq (Python 2 and 3)

PyExpLabSys.drivers.bio_logic (Python 2 only1 )

PyExpLabSys.drivers.stahl_hv_400 (Python 2 and 3)

PyExpLabSys.drivers.polyscience_4100 (Python 2 and 3)

PyExpLabSys.drivers.pfeiffer_turbo_pump (Python 2 and 3)

PyExpLabSys.drivers.srs_sr630 (Python 2 and 3)

PyExpLabSys.drivers.vivo_technologies (Python 2 only1 )

PyExpLabSys.drivers.inficon_sqm160 (Python 2 only1 )

PyExpLabSys.drivers.edwards_nxds (Python 2 and 3)

PyExpLabSys.drivers.omega_cn7800 (Python 2 only1 )

PyExpLabSys.drivers.tenma (Python 2 and 3)

PyExpLabSys.drivers.omron_d6fph (Python 2 and 3)

PyExpLabSys.drivers.pfeiffer_qmg422 (Python 2 and 3)

PyExpLabSys.drivers.xgs600 (Python 2 and 3)

1.3. Module Overview 9

• Driver class for XGS600 gauge controll

PyExpLabSys.drivers.stmicroelectronics_l3g4200d (Python 2 and 3)

PyExpLabSys.drivers.pfeiffer_qmg420 (Python 2 only1 )

PyExpLabSys.drivers.dataq_binary (Python 2 and 3)

PyExpLabSys.drivers.omega_cni (Python 2 and 3)

PyExpLabSys.drivers.keithley_2700 (Python 2 and 3)

PyExpLabSys.drivers.agilent_34410A (Python 2 and 3)

PyExpLabSys.drivers.brooks_s_protocol (Python 2 and 3)

PyExpLabSys.drivers.agilent_34972A (Python 2 and 3)

PyExpLabSys.drivers.mks_pi_pc (Python 2 only1 )

PyExpLabSys.drivers.isotech_ips (Python 2 only1 )

PyExpLabSys.drivers.galaxy_3500 (Python 2 and 3)

PyExpLabSys.drivers.omegabus (Python 2 and 3)