Radar sensor Forum Discussions
We are excited to announce the release of Radar Development Kit 3.5.1, which is now available for download from the Infineon Developer Center.
This release introduces a range of new features, improvements, and fixes, and includes the following components:
- Radar SDK v3.5.0
- Radar Fusion GUI v3.5.4
- ifxdaq v4.0.0
- RBB Firmware v2.6.0
Please see below for details on the new features and changes in this release.
New Features:
Radar SDK v3.5.0
- General API for Controlling FMCW Radar Devices
Radar SDK 3.5 introduces a new and versatile general API for controlling FMCW radar devices. The API can accommodate all FMCW-based radar sensors, and it includes a new configuration structure that supports multiple chirp configurations within a single frame. - Revised Continuous Wave API
The Continuous Wave API has been revised and is now structured similarly to the FMCW API. To create a Continuous Wave instance, it is no longer necessary to create a device instance and pass it as a parameter. The function call of ifx_cw_create returns a Continuous Wave instance, and the configurations for the ADC and baseband have also been restructured. The previous configuration (ifx_Avian_Config_t) no longer exists.
Radar Fusion GUI v3.5.4
- Support for BGT60UTR11AIP FMCW 60GHz Sensor
Radar Fusion GUI now supports the BGT66UTR11AIP FMCW 60GHz sensor. This includes sensor configuration, raw ADC data acquisition, and presence sensing application. - Expert Mode
An Expert Mode has been introduced for 60GHz FMCW sensors in the Radar Fusion GUI. This mode includes a Timing Model view for the given frame configuration, multiple chirp configurations within a frame, a Difference Deviation plot designed to characterize inter-chirp performance, and a power consumption value display at the status bar for Avian sensors. - Dummy Sensor Support
Dummy sensor support is now available for compatible sensors. Users can experiment with sensor configurations and import/export these configurations to the register file, and visualization of timing and power modes for configured chirps. - Recording of Raw ADC Data
The recording of raw ADC data format now standardizes to the ifxdaq recording format for FMCW 60GHz Sensors. Raw data is stored in standard .npy format, and meta-data and sensor configs are stored in a separate JSON format. The GUI offers playback of legacy recordings, but any recording from the GUI will be in the new format. A converter in the Recording menu is available to convert legacy recordings to the new format. - Register Export and Import
Register export and import options have been included for FMCW devices. - Presence Sensing App Upgrade
The presence sensing app has undergone an upgrade with a more robust algorithm. New additions include a separate visualization dedicated to presence sensing, and display of the range of strongest targets alongside presence information. - Range Spectrogram and Doppler Spectrogram Plots
New range spectrogram and Doppler spectrogram plots have been added. - Clipping Detection
A display indicating clipping detection has been integrated into the status bar. This alert will trigger if the ADC time domain signal exceeds the limits of [-1, +1].
Changes:
- The convention for displaying approaching targets on the positive side of the velocity axis of the range Doppler map has been aligned.
- The range and angle measurement algorithm has been enhanced to achieve detection ranges of over 10 meters.
- Simultaneous visualization of multiple Rx antennas has been added to the Range Doppler Map plot.
- Fix the import of registers in a dummy device mode (reported in v3.5.3)
- Fix the allowed RF frequency range for supported FMCW sensors (reported in v3.5.3)
Thank you for choosing Radar Development Kit!
Show LessDear Customer,
we are happy to announce you the launch of our next generation of XENSIV™ Radar 24GHz DEMO kits with Sense2GoL Pulse and Distance2GoL.
Following the said launch, please be informed that these XENSIV™ Radar 24GHz demo kits are therefore discontinued: Sense2Go, Sense2GoL, Distance2Go and Position2Go.
We are transferring our support capabilities towards the new kits. For the discontinued kits, we will reduce and eventually stop our support including telephone, chat, community support forum, or e-mail inquiries. We apologize for any inconvenience caused.
Please find all needed information on all our 24GHz radar products and kits on www.infineon.com/24ghz.
Sincerely,
Your Infineon team
Hello,
We are producing radar modules using BGT60UTR11AIP. We have found that the DC-offset of ADC data changes significantly between chips under the same conditions.
Is the DC-offset variation managed during the chip production? Or is there a way to calibrate it to a specific level?
Regards,
YK
Show LessI reconfigure the firmware in config.h: I just modify the bandwidth into 0MHz ,I try to transmit signle tone with my board.
And I also flash the new .hex file inro my board successfully with XMC Flasher.
When I reconnect my board with new FW into my PC, it's LED just like this, only one yellow LED lighting
And when I open GUI, it show no Device connected, and my matlab code also can't run:
Then how can I know this radar still work and really the bandwidth is 0MHz. And if it's still working, I want to extraxt raw data with my matlab code? How can I modify the original code? I really need help, thanks!
Show Less
I have rebuild the DAVE project, it shows successful. However, it seems nothing like .hex file is generated, so I can't choose a firmware file when I try to flash the new FW into my board by XMC Flasher. And I also don't find a release button in DAVE IDE to generate a firmware file for the new project. I can't find any info in the user manual. Please help me, how can I flash the new project into my board?
By the way, there is two micro b connector in the Disyance2GoL board, when I flash a new firmwave? which one should I plug in? the debugger connector or the regular one?
And can I configure the bandwith into 0MHz, I mean I want to make the radar transmit a signle tone. Can that be realized?
Show Less
Hi,
I am using the BGT60TR13C for vital sign extraction and I saw in other questions in the forum that the BGT60TR13C only outputs the I signal of the radar.
I tried to use the progression of each complex frequency component over time (chirp-to-chirp) as an IQ signal for each frequency component, as you suggested. But it is not working and I cannot extract meaningful information. For comparison, I did manage to extract specifically respiration rate using only the amplitude data in the output.
I would like your help to better understand how to extract phase from the output data and detect small vibrations.
Thank you!
Show Less
Hi,
I'm trying to implement FMCW mode in the BGT60TR13C radar sensor.
My application is to measure the water level inside the PVC pipe (The water level changes very slowly). Our hardware is based on STM32F4 MCU and BGT60TR13C.
I already followed the manual on the link:
https://github.com/Infineon/sensor-xensiv-bgt60trxx
Currently, I have got the FIFO data successfully.
I have some questions could you please help me clearly understand?
- Will the FMCW mode be suitable for my application?
- The BGT60TR13C has a frequency-modulated continuous wave (FMCW) radar, So the FMCW mode running by default, or need to be configured? How can I configure the BGT60TR13C to run in the FMCW mode? (I'm trying to follow section 10.2.1 Enabling the CW mode in the datasheet).
- Is it required to port the RDK for STM32F4 to implement the FMCW?
- What are the differences between SADC and FIFO data?
- How to convert a configure from Radar Fusion GUI to hex values (presence_radar_settings.h) ?
Thanks!
Show LessI intend to save radar values as numpy files without using the record feature of Fusion GUI. The reason is to decouple from the dependency on Fusion GUI in my code.
So, I utilized the source code provided in the SDK to save radar values as numpy files. When I plotted them using pyplot, I noticed discrepancies between the data obtained directly from the code and the data recorded by Fusion GUI.
The data obtained from the source code appears to be scaled similarly to values received from the antennas, ranging from 0 to 1. However, there is a significant difference in the y-axis compared to Fusion GUI. I want to retrieve data exactly as recorded by Fusion GUI. Could you please guide me on how to achieve this?
Additionally, if possible, could you also explain how to modify the current settings? Currently, the code is set to "num of samples per frame: 64, num of chirps per frame: 64", but I want to change it to "num of samples per frame: 128, num of chirps per frame: 128, etc...".
ps1. My radar model is the Infineon DEMO BGT60TR13C (60GHz sensor), along with Fusion GUI version 3.5.4.202310251420.
ps2. My python codes.
#=== recordinf.py ======
Hi,
Im using Psoc- 062s2- 43012 with #BGT60TR13c.The application that I'm running is very similar to the one provided in the library(https://github.com/Infineon/sensor-xensiv-bgt60trxx).I have just changed the logic to print samples[sample_idx] to print raw data.
I wanted to obtain raw data.After 14 frames
xensiv_bgt60trxx_get_fifo_data() functions throws a "XENSIV_BGT60TRXX_STATUS_GSR0_ERROR".
I tried hard_reset and soft_reset. But it did not work.
Any suggestion on this issue?
Thank you!!
Show LessHi team,
Actually I am using BGT60LTR11AIP sensor but I am only able to detect the object up to 3 meter can you provide me best configuration setting so that I will detect object up to 7 meter
this is my current configuration setting
Sr.No | Hold Time | Threshold | Pulse Width | Rx Gain | RF center Freq | Adaptive PRT | Tx Gain | PRT | Motion Detection |
1 | 5.1 sec | 192 | 10us | 50db | 61.25 | 0 | 500us | 3.5 m |
Hello everyone.
While using the DEMO BGT60TR13C, even when I click on "Start Recording" in the Radar Fusion GUI, only npy files are generated instead of raw.bin files. How can I ensure that raw.bin files are generated instead?
C:\Users\Sinhyuk\Documents\RadarFusionGUI\BGT60TR13C>tree /f
C:.
└─BGT60TR13C_record_20240312-161533
│ meta.json
│
└─RadarIfxAvian_00
config.json
format.version
meta.json
radar.npy
Where can I get Distance2GoL filmware example pack? I have one but it didn`t work, I`m sure I made debug properly. I tryed to use RADAR GUI but result is not satisfying, so I want to see actual sourse code example for this FMCW radar.
Show Less