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
Dears,
I have an issue about launching my program to the board and I got these errors and my debug configuration. For Source Template I choose KIT-BGT60TR13C-EMBEDD. I am using Xensiv Connected Sensor Kit and I am taking this error even with the basic Hello World code.
Could anyone help me about this. I tried some solutions that I find in Web but they did not help me.
Kind regards,
Eray
Show Less
In the documentation folder of "Radar BGT60ATR24C P2S", there is RDK_Aurix_FW_Getting_Started_Guide_v1.0.docx
However, it is just a rudimentary overview of the firmware, and the source code folder structure explained in the doc doesn't even match the real source code folder structure.
Are there any more detailed and updated documentation on the firmware?
Show LessThe first problem is that cmake will report that the version is too new. The second is that after the compilation is completed, I open the project and start compiling. I can run many packages, but in the end it will prompt me that the all_build folder in debug cannot be accessed.
Show LessHi Infineon
What the difference of functions in BGT60UTR11AIP with BGT60LTR11AIP , when can get BGT60UTR11AIP EVB board for verify, Thanks!!
Show Less
Hello
We have the BGT60TR13C development board in hand, we bought it very early, at that time your official website was temporarily out of stock, we bought it from the network dealer at a markup. But the radar board needs to be registered, and the product cannot be registered due to the lack of order code purchased from the dealer, and Infineon's more cutting-edge research cannot be understood, is there a solution?
Have a good day
Hi all,
We are considering development using a radar sensor (BGT60TR13C).
# Application: heart rate, blood pressure.
# Inquiry:
- Can you confirm that any of Infineon's products have been mass produced or are in the process of mass production for heart rate and blood pressure applications?
Currently reviewing the 60 GHz BGT60TR13C. However, if you have a history of mass production with other products, please recommend other products.
Have a nice day.
Regards,
Alex
Show LessHello Good afternoon
We recently conducted research using the BGT60TR13C radar development board to evaluate whether it can be used to detect heart rate and breathing. We have looked at many sample codes on the official website, but have not found a specific demo to support direct detection of heart rate, do you have cutting-edge research or code to support direct detection?
Bless you.
Hi everyone
I have the following versions of Demo BGT60TR13C on hand.
■ Radar Baseboard MCU7 v2.1 10-2019
Shield Board BGT60TR13C v2.1
What FW version should I write if I want to evaluate using FUSION Radar GUI?
If I can't use the FUSION Radar GUI, what tools can I use to evaluate it?
Thanks
Yang
Show Less測試了3顆BGT24LTR11N16的VCO頻率,發現VCO頻率不一樣,是否正確?
雖然規範上標明VCO頻率範圍是24.05~24.25GHz,但是在固定電路和BOM中,VCO頻率會有所不同嗎?
例如:
1 號樣品的 VCO 頻率為 24.15GHz
2 號樣品的 VCO 頻率為 24.128GHz
3 號樣品的 VCO 頻率為 24.142GHz
Dear Community,
I have a problem with the #BGT60ATR24C# radar sensor. In my application I use a MCU to control the sensor via SPI/QSPI. I have the following problem: I initialize the sensor registers that I have generated from the Infineon Sensor GUI in normal SPI mode. Then to test if the register values are taken over, all register values are read out in QSPI burst mode. At the first readout I get all register values back as they were initialized by the normal SPI write mode (So I would guess, that the QSPI setting are the right - CLK, Dummy_Cycles, ADR/CMD. However, when I directly read the registers a second time in QSPI mode, all register values are reset to the default values described in the datasheet. Now my assumption is that the registers are reset by the first QSPI read operation, here the question arises, what can cause such a behavior of the sensor
As a note I can say here that I have tested the same read operation in SPI burst mode and here the sensor does not reset and can also be read multiple times.
Can you please give me some more context for the QSPI read mode, because in the datasheet only a brief description of the interface is given, on which behavior of the QSPI interface such a chip reset can be triggered. If you have Logic Analyzer screenshot of an ideal QSPI reading operation would be very helpful!
Thank You in advance!
Best regards,
Jurni_JasteD