Home

Awesome

LabPowerQt

Build Status LabPowerQt license GPL Latest release

<!-- START doctoc generated TOC please keep comment here to allow auto update --> <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> <!-- END doctoc generated TOC please keep comment here to allow auto update -->

LabPowerQt is an application to control laboratory power supplies and to record and visualize the data.

The software is written using the Qt Framework and therefor works on Linux, Windows and macOS. Although it works cross platform the main target platforms for this project are Linux and macOS.

The application is in an early stage of development make sure to read the known issues section.

LabPowerQt main screen LabPowerQt running on archlinux and Gnome 3.20

Features

Getting LabPowerQt

Linux

Linux users have two different options to run the application. Either install a package provided by your distribution or use the AppImage to run the LabPowerQt without the need to compile the source code or install any dependencies. You can download the AppImage from the github releases tab for this project.

The AppImage was tested on these distributions:

If you have used the AppImage on other distributions please let me know if it worked for you.

LabPowerQt packages are available on these Linux distributions:

Windows

I am providing an InnoSetup based installer for x86 and amd64 containing all dependencies. It is downloadable from github.com

Compiling from source

Dependencies

The following dependencies are required to run this software:

Compilation

You can obtain the source code from github.

If you want to compile LabPowerQt yourself you will find these cmake options useful:

Linux and macOS

Compiling LabPowerQt on Linux and macOS using unix make files.

# download the source code and change to the directory
# create a build directory
mkdir build
cd build
# run cmake to create makefiles. Use -DCMAKE_PREFIX_PATH if cmake doesn't find
# your installation of Qt5
cmake -DCMAKE_BUILD_TYPE=Release ../
# now compile the source code and create the application. You can speed up
# compilation with make's j option.
make
# install the application
sudo make install

Windows

You can compile LabPowerQt on Windows using cmake's Visual Studio Generator.

# create build directory inside labpowerqt source directory
mkdir build
cd build
# Assuming you are using Visual Studio 2015 on a 64bit windows installation and
# Qt 5.6 installed to C:\\Qt
# Please change these options so they suit your build evironment.
cmake -G"Visual Studio 14 2015 Win64" -DCMAKE_PREFIX_PATH="C:\\Qt\\5.6\\msvc2015_64" ../

You may now open the solution file with visual studio and compile the application.

Other possibilities are cmake's NMake Generator or mingw.

Supported Hardware

Currently the application only supports Devices using the Korad SCPI Protocol

Using the Application

The Application is easy to use and most things should be self explanatory. Many controls offer tooltips about what they do.

To control the device connected to your computer you have to use the Control Area in the main window. It consists of green and orange elements and serves for two purposes at the same time. The current state of the device is displayed there and you can use the orange elements to control the device (by double-clicking them).

The data of the device is stored in memory. You can also persist the data in a SQLite database by turning on a Recording.

The data is not only displayed in the control area but can also be visualized in a Plot on the right side of the main window. Have a look at the buttons above the Plot to discover all the possibilities you have (e.g. change graph colors or line style, export plot as image, discard data and many more).

The settings dialog is important as you have to use the build in device wizard to add a device. Other things can be set there as well.

Screenshots

LabPowerQt running on Windows 8.1 LabPowerQt running on Windows 8.1 32bit

LabPowerQt recordings history Recordings listed in a table

LabPowerQt example Plot export image Exported image of the Plot in LabPowerQt

Development

Brief overview over the development process.

Repositories

The github repository of labpowerqt has several different branches.

Coding standards

The source code is formatted with clang-format using the following configuration

Language                            : Cpp,
BasedOnStyle                        : LLVM,
AccessModifierOffset                : -4,
AllowShortIfStatementsOnASingleLine : false,
AlwaysBreakTemplateDeclarations     : true,
ColumnLimit                         : 81,
IndentCaseLabels                    : false,
Standard                            : Cpp11,
IndentWidth                         : 4,
TabWidth                            : 4,
BreakBeforeBraces                   : Linux,
CommentPragmas                      : '(^ IWYU pragma:)|(^.*\[.*\]\(.*\).*$)|(^.*@brief|@param|@return|@throw.*$)|(/\*\*<.*\*/)'

Versioning

I decided to use semantic versioning

Continuous Integration

Build Status

Travis CI is used as continuous integration service. The labpowerqt github repository is linked to Travis CI. You can see the build history for the master branch and all release branches on the travis project page.

ToDo

Have a look in the todo folder. I am using the todo.txt format for my todo lists.

Bugs, feature requests, ideas

Please use the github bugtracker to submit bugs or feature requests

Known issues

License

Copyright (C) 2015, 2016, 2017 Christian Rapp

This program 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.

This program 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 this program.  If not, see <http://www.gnu.org/licenses/>.