Software downloads
Acconeer provides everything you need to evaluate and develop applications based on the A1 radar sensor. On this page you can find all the software you need to use our Evaluation kits (EVK) and Modules. The downloads consist of module software and Software Development Kits (SDK). To use a module with the Exploration Tool for evaluation, you only need the module software. To use reference apps or build a full application using one of our modules, you also need the SDK. There is also SDKs provided for other selected microcontrollers and development environments.
Select your hardware setup in the menu to the left to find relevant software downloads.
To learn what’s included in the latest release, check out the Software Release Notes
XM122
This page contains SW for our IoT Module. This module includes Bluetooth and can be powered by a coin cell battery. It is optimized for IoT use cases but can of course also be used for other use cases which do not require a high processing power.
The XM122 can be used as a stand-alone module where customers can embed their application on top of the Acconeer RSS (Radar System Software). It can also be used with an external host controller where communication to the module is handled through a register command protocol.
XC112
This page contains SW for our Evaluation Kit. The XC112-XR112 Evaluation Kit have the advantage of supporting 4 sensors attached with flex cabling. Suitable for evaluation purposes of multi sensor solutions. The user will need a Raspberry Pi 3/3+ or 4 to power the sensors.
XM132
XC111
This page contains SW for our Evaluation Kit. The XC111-XR111 Evaluation Kit have the advantage of supporting 4 sensors in fixed mounting. Suitable for evaluation purposes of multi sensor solutions. The user will need a Raspberry Pi 3/3+ or 4 to power the sensors.
It is no longer possible to buy new XC111-XR111, as it is replaced by XC112-XR112. However, we will continue to support this evaluation kit with SW upgrades.
SPARKFUN
This page contains Raspberry PI software for the SparkFun Pulsed Radar Breakout – A111 board, which can be bought directly from Sparkfun.
The Sparkfun board is often a good choice for prototypes where you want to connect the A111 radar sensor to your preferred ARM Cortex M based MCU Dev Kit. In that case we suggest you download the software package for ARM Cortex M0, M4 or M7.
CORTEX M0
This page contains SW for Cortex M0 based HW. This SW should be used as a base for integration to your custom HW.
CORTEX M4
This page contains SW for Cortex M4 based HW. This SW should be used as a base for integration to your custom HW. For an evaluation reference we would recommend the XM122 module.
CORTEX M7
This page contains SW for Cortex M7 based HW. This SW should be used as a base for integration to your custom HW. For an evaluation reference we would recommend the XM112 module.
XM112
This page contains SW for our High Performance Module XM112. This Module is specified with the purpose to handle most, if not all, thinkable use cases for our sensor. The main purpose is for evaluation of your use case.
The XM112 can be used as a stand-alone module where customers can embed their application on top of the Acconeer RSS (Radar System Software). It can also be used with an external host controller where communication to the module is handled through a register command protocol.
Applications and tools
Acconeer Exploration Tool consists of a set of tools and examples to help you get started with our Evaluation Kits (EVK). With a graphical interface for your PC and python-based development, it allows you to quickly start exploring the world of Acconeer’s radar sensor technology.
You can download an executable version of Exploration Tool for Windows, or get the full version in our Exploration Tool repo on GitHub. The full version supports Linux and Windows.
Additional tools and example applications
In addition to Exploration Tool, we provide several example applications and other tools on the Acconeer GitHub page. These are frequently updated and new assets are added all the time, so head over to GitHub to find out more.
Example Android Applications
We have developed a few examples of how to control our sensor fron an Android Application and utilize a few basic use cases.
We do not plan to maintain or develop these further but you are free to download and use them.


Documents and learning
In this section you find product documentation as well as development user guides. Select your hardware in the menu to the left to find relevant documents regarding software development, and product specifications (datasheet). Have a look under A111 for detailed information about Acconeer’s radar sensor and technology, hardware integration, and regulatory compliance.
XM132/XE132
A111
Here you can find documentation which is valid for our A111 sensor independent of the HW context in which it is used. We strongly recommend for all users to read the Sensor Introduction and the Hardware and Physical Integration Guidelines to avoid mistakes that is easy to avoid in the beginning of a project but could turn out costly later.
SW
Here you find the User Guides for our RSS (Radar System SW). Services, Detectors as well as HAL Integration Guidelines. You will be able to educate yourself everything from how to control the IQ Data Service and Sparse Service to Obstacle Detector and Smart Presence Detector. And more…
XM112/XB112
On this page we have the HW User Guides for XM112 and XB112 as well as Getting Started Guides. Our goal is for the user to be up and running in no time.
XM122/XB122/XA122
On this page we have the HW User Guides for XM122, XB122 and XA122 as well as Getting Started Guides. Our goal is for the user to be up and running in no time.
XC112/XR112
On this page we have the HW User Guides for XC112 and XR112 as well as Getting Started Guides. Our goal is for the user to be up and running in no time.
LH112/LH122/LH132
Here you can find documents covering our Lens Evaluation Kit. The Guide covers both our Hyperbolic lens and the Fresnel lens. We will extend our range of lenses going forward.
XC111/XR111
On this page we have the HW User Guides for XC111 and XR111 as well as Getting Started Guides. Our goal is for the user to be up and running in no time.
STM32CubeIDE
Here are guidelines of how to integrate our sensor using the STM32Cube IDE.
Media
In this section we will publish links to our instruction videos and demo videos on our Acconeer Youtube Channel. Have a look at the videos below for inspiration to how you can use Acconeer’s radar technology. For more videos, including tutorials and development guides, go to our Acconeer YouTube channel. In this section we will publish links to our instruction videos and demo videos on our Acconeer Youtube Channel.
FAQ
On this page you find some of the most common questions we receive from customers during their development and integration. If you can’t find the answer you need here, submit a ticket to us!
HW
The frequency of the crystal oscillator connected to A111 is specified between 20-80MHz. It must be at least 20.625MHz in order for the SPI frequency to reach 50MHz which is necessary in order to obtain the 1500Hz update rate.
The main purpose of having a range for the input frequency on XIN between 20MHz and 80 MHz is to allow for a flexible hardware integration. It allows the customer to choose a crystal oscillator more freely and an already existing reference clock in the design could be reused for the A111. It must however be ensured that the crystal or the reference clock that is to be used fulfils the requirements stated in the datasheet.
The use of a crystal oscillator or reference clock with higher frequency could benefit the accuracy of the sensor measurement if the relative increase in phase noise is smaller or equal to the relative increase in frequency. The use of a crystal oscillator or reference clock with higher frequency will however increase the power consumption of the A111.
SW
Acconeer have extended support for STM32L476 (ST-Micro) and STMCubeIDE.
Any MCU based on ARM CM0, CM4 and CM7 can be used by downloading the corresponding SDK and by implementing the HAL layer as described in the HAL SW Integration User Guide.
Accessing A111 registers via the SPI interface is not supported. The main reason is that to make changes to the registers, one must have knowledge about proprietary design details which are confidential. The performance of the sensor also depends on nontrivial calibration and signal processing software that is included in the software libraries.
The sensor is controlled using the Software API “Radar Services” and all settings are done using this API. A description of how to change the settings as well as a description of the radar data provided by the different services is documented in the user guides that are available on the Acconeer webpage.
No, you can use open source software such as gdb and openocd.
This is the direct leakage caused by TX leaking over to RX directly without bouncing on a real object. Increasing the start range solves the problem.
QUESTION: Test result after S/W Compile shows reaching distance no further than 40cm. It is normal or do we expet to see up to 2m?
ANSWER: This is as expected, the test program you are running is probably set to measure up to 40cm. To make other measurements you include other input parameters in the Distancestrongest API. For guidance please look at API user manual, found in doc/html,with index file, when extracting SW zip file to a new directory.
Load More
Software downloads
Acconeer
provides everything you need to evaluate and develop applications based on the
A1 radar sensor. On this page you can find all the software you need to use our
Evaluation kits (EVK) and Modules. The downloads consist of module software and
Software Development Kits (SDK). To use a module with the Exploration Tool for
evaluation, you only need the module software. To use reference apps or build a
full application using one of our modules, you also need the SDK. There is also
SDKs provided for other selected microcontrollers and development environments.
Select your
hardware setup in the menu to the left to find relevant software downloads.
To learn what’s included in the latest
release, check out the Software Release
Notes
Applications and tools
Acconeer
Exploration Tool consists of a set of tools and examples to help you get
started with our Evaluation Kits (EVK). With a graphical interface for your PC
and python-based development, it allows you to quickly start exploring the
world of Acconeer’s radar sensor technology.
You can download an executable version of Exploration Tool for Windows, or get the full version in our Exploration Tool repo on GitHub. The full version supports Linux and Windows.
Additional tools and
example applications
In addition to Exploration Tool, we provide several example applications and other tools on the Acconeer GitHub page. These are frequently updated and new assets are added all the time, so head over to GitHub to find out more.
Example Android Applications
We have developed a few examples of how to control our sensor fron an Android Application and utilize a few basic use cases.
We do not plan to maintain or develop these further but you are free to download and use them.


Documents and learning
In this section you find product documentation as well as development user guides. Select your hardware in the menu to the left to find relevant documents regarding software development, and product specifications (datasheet). Have a look under A111 for detailed information about Acconeer’s radar sensor and technology, hardware integration, and regulatory compliance.
Media
In this section we will publish links to our instruction videos and demo videos on our Acconeer Youtube Channel. Have a look at the videos below for inspiration to how you can use Acconeer’s radar technology. For more videos, including tutorials and development guides, go to our Acconeer YouTube channel. In this section we will publish links to our instruction videos and demo videos on our Acconeer Youtube Channel.
FAQ
On this page you find some of the most common questions we receive from customers during their development and integration. If you can’t find the answer you need here, submit a ticket to us!
HW
The frequency of the crystal oscillator connected to A111 is specified between 20-80MHz. It must be at least 20.625MHz in order for the SPI frequency to reach 50MHz which is necessary in order to obtain the 1500Hz update rate.
The main purpose of having a range for the input frequency on XIN between 20MHz and 80 MHz is to allow for a flexible hardware integration. It allows the customer to choose a crystal oscillator more freely and an already existing reference clock in the design could be reused for the A111. It must however be ensured that the crystal or the reference clock that is to be used fulfils the requirements stated in the datasheet.
The use of a crystal oscillator or reference clock with higher frequency could benefit the accuracy of the sensor measurement if the relative increase in phase noise is smaller or equal to the relative increase in frequency. The use of a crystal oscillator or reference clock with higher frequency will however increase the power consumption of the A111.
SW
Acconeer have extended support for STM32L476 (ST-Micro) and STMCubeIDE.
Any MCU based on ARM CM0, CM4 and CM7 can be used by downloading the corresponding SDK and by implementing the HAL layer as described in the HAL SW Integration User Guide.
Accessing A111 registers via the SPI interface is not supported. The main reason is that to make changes to the registers, one must have knowledge about proprietary design details which are confidential. The performance of the sensor also depends on nontrivial calibration and signal processing software that is included in the software libraries.
The sensor is controlled using the Software API “Radar Services” and all settings are done using this API. A description of how to change the settings as well as a description of the radar data provided by the different services is documented in the user guides that are available on the Acconeer webpage.
No, you can use open source software such as gdb and openocd.
This is the direct leakage caused by TX leaking over to RX directly without bouncing on a real object. Increasing the start range solves the problem.
QUESTION: Test result after S/W Compile shows reaching distance no further than 40cm. It is normal or do we expet to see up to 2m?
ANSWER: This is as expected, the test program you are running is probably set to measure up to 40cm. To make other measurements you include other input parameters in the Distancestrongest API. For guidance please look at API user manual, found in doc/html,with index file, when extracting SW zip file to a new directory.
Load More
You will need an account in order to gain full access to this site.. Create one here.
Do you already have an Acconeer account? Log in here.
Forgot your password? Recover your password here.Would you like to receive updates on our company and products? Sign up for our newsletter here.