Working with the GUI¶
Acconeer offers a comprehensive GUI for the Acconeer Exploration Tool to work with our sensors. The tool is meant as a companion throughout your project; it should help you getting started quickly with testing and evaluating our sensor for your use-case, but also support you in finding the optimal sensor settings and fine-tuning the data processing for your final product implementation.
The general work-flow with the Exploration Tool GUI is described in the following:
The Exploration Tool has been tested on the following operating systems
- Windows 10
- Ubuntu (18.04, 20.04)
- WSL (Windows Subsystem for Linux)
but others should work fine, too (such as macOS or other versions of Linux). Installing the Exploration Tool GUI on a Raspberry Pi is not supported! (You can still use the Exploration Tool without graphical interface on the Raspberry Pi.)
In order to get started, you need either a Raspberry Pi with an XC/XR112 (Setting up your Raspberry Pi EVK) or one of our modules with the latest firmware (Setting up your XM112, Setting up your XM122, Setting up your XM132).
First, you should clone the Exploration Tool repository from GitHub. There, you can find detailed instructions for installing our libraries; in a nut-shell:
Make sure you have Python 3.7 or newer installed.
Install the required packages (you might have to replace python with python3 or py):
python -m pip install -U --user setuptools wheel python -m pip install -U --user -r requirements.txt
Install the acconeer.exptool library:
python -m pip install -U --user .
Once, you have installed everything, you can start the GUI from the root of the repository via:
The GUI acts as a front-end to the Acconeer Exploration Tool. It handles sensor connections, sensor settings and allows you to test examples, tune detectors and save and load data for in-depth analysis or easy sharing. In below figure, you can find a top-level depiction of the data-flow and control connections between the GUI and the Exploration Tool.
The GUI never stores processed data, only the original service data, including all sensor and detector settings. Whenever you replay data (saved or buffered), the processing is always redone on the original sensor data.