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
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 LessHello,
Regarding below content,
"Can XENSIV™ BGT60LTR11AIP radar sensor operate on Japanese ISM band?"
https://community.infineon.com/t5/Knowledge-Base-Articles/Can-XENSIV-BGT60LTR11AIP-radar-sensor-operate-on-Japanese-ISM-band/ta-p/696899?emcs_t=S2h8ZW1haWx8Ym9hcmRfc3Vic2NyaXB0aW9ufExTVDJQOTZXWFFXQUlXfDY5Njg5OXxTVUJTQ1JJUFRJT05TfGhL
How can I use the JPN frequency on the BGT60LTR11AIP shield when using the FUSION GUI?
I would like to know the specific method if possible.
And is it possible to use the FUSION GUI if the BGT60LTR11AIP MMIC on the BGT60LTR11AIP Shield is replaced to the BGT60LTR11BAIP MMIC ? I understand that replacing the item will void the warranty.
Best Regards,
Nakamura
我最近打算用bgt24ltr11测量距离,请问我采集到中频信号之后该如何处理才能得到静止目标的距离信息?我的发射方法是脉冲线性调频,即用锯齿波调制vco,每隔一段时间发一次。最开始我才用对回波做fft的方法查看频谱,寻找峰值以确定距离,但是在官方demo板中这种方法用来测量动目标,并未提及静止目标测量办法。
Show LessI use a MCU7 RBB with the AiP34V1.0 shield. When I start the Radar Fusion GUI_3.5.4 I can flash the firmware successfully. But when I click the button, the software crashes.
Any ideas how to avoid the crash and use the board?
Show Less
I'm trying to measure range using BGT60TR13C and SDK.
I did a range fft, but the results are questionable.
The image above is a stem result of my range fft. I think the red mark I checked is the target.
Even though I did DC removal, I confirmed that DC and its surrounding frequency components had a larger amplitude than the target.
Please explain about this situration. Is my code wrong? or This situration is normal?
Below is the code I wrote.
---------------------------------------------------------------------------------------------------
I want to use stm32 to drive BGT60TR13C, but I have encountered some difficulties. When reading the CHIP ID, I cannot find the correct ID, and the value read each time is the same. The following is the chip ID read and my code
Show Less
I need to pull raw data from XENSIV 60GHz radar sensor (REF_BGT60LTR11AIP_MO). I have an XMC Link and was able to connect this to Micrium based GUI but it cannot see the radar. Is there a way to solve this?
Show LessAccording to the User Manual to extract radar raw data from radar distance2GOL via Matlab code, I run the code:"extract_raw_data.m" in my computer when I have the radar connected to my computer. However there are errors happen like this:
******************************************************************
[resetRS] Reset the following port(s):
{'COM7'}
Connected RadarSystem:
oRS =
RadarSystem with no properties.
Unrecognized method, property, or field 'oEPRadarBase' for class
'RadarSystem'.
Error in extract_raw_data (line 52)
oRS.oEPRadarBase.set_automatic_frame_trigger(1000000);
I have try my best to debug, but I still can't make it, have someone also met this error before? Please give me some tips.
I collected data from BGT60TR13C radar and used the code below to read bin file and convert to the numpy array. But the size of the numpy array is less than the size of the 4d adc data obtained on reading the .txt file? Can anyone explain why? And How to interpret .bin and .txt file that we get from the Radar Fusion GUI. Thanks
import numpy as np