Choosing a service or detector#

At this point, you should have connected to your sensor via one of the available options. By default, the GUI selects the Envelope service, if no other service has been selected. Other services or detectors can be selected via the drop down list.

Our sensor can be run in one of these four basic services:


Data Type

Example Use Case

Envelope (Power Bins)

Amplitude only
Absolute distance (e.g. water level)
Static presence (e.g. parking sensor)


Amplitude and Phase
Obstacle detection (e.g. lawn mower, RVC, <30 cm/s)
Relative distance (down to 50 microns)


Instantaneous amplitude
at high rep-rate
Speed (up to m/s)
Presence detection (moving objects)
People counting

Figure 39 Service and detector drop-down menu in the GUI#

Each of these services has it’s own advantages and disadvantages and knowing about the capabilities of each service will help you select the correct one for your use-case.

In order to better understand the type of information you can get with each service, the GUI can be used to look at the unprocessed data of each of those. Just select any of those services from the Select service and detectors drop-down menu and click Start measurement.


Using the Acconeer Exploration Tool interface, you can only use one service/detector at a time. Even when using several sensors, you cannot use different service types or detectors on different sensors with the GUI.


Each detector is based on one of the above listed services, but applies post-processing to the data in order to work out the information relevant to the detector. In the drop-down list, you can see the used service added in brackets after the detector name (see Figure 39). At the moment we have the following examples and detectors to choose from:

  1. Envelope Service

  2. IQ Service

  3. Sparse Service

    • Presence Detection (Detector)

    • Sparse short-time FFT (Example)

    • Sparse long-time FFT (Example)

    • Speed (Example)

The main difference between a detector and an example is that for detectors, we have the matching C-code available.


All settings and names you can find for the detector in the GUI are kept the same in the C-code and the processing is identical to allow tuning parameters in the GUI and just copy & pasting the settings to your C-code implementation.