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
I am working on a presence sensing applications, using BGT24LTR11 radar sensor. The sensor is connected to STM32G0 micro-controller. I need help to start the project. Any sample code or driver code will be very helpful. Also attaching the schematics.
Show LessHello,
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 LessHello,
I am trying to connect KIT_CSK_BGT60TR13C with my laptop according to instructions provided in User Guide for XENSIV™ KIT CSK BGT60TR13C.
The error I am facing is the following,
------------------------------
[INFO] Erasing Device Flash
Error: unable to find CMSIS-DAP device
[ERROR] Unable to erase device flash. Close all software accessing the kit, if open.
------------------------------
Version is 1.1.0. Light on the board keeps blinking instead of staying stable.
I tried different usb cables, ports and multiple laptops however I am still facing the same issue. May you kindly advise how can I solve this issue?
Thank you in advance.
Show LessHi.
I would like to ask what is the model number of the programming dongle in the first section of chapter 4 of the application note on your company's website.
How to purchase it, and can this programming dongle change the radar's sensitivity and other parameters?
Test Board : DEMO_60LTR11_AUTO_BLE
Application note link : Getting started with the XENSIV™ wireless presence detection sensor (infineon.com)
Thanks
Yang
Show LessI notice that distance2GoL is designed for low-power via duty-cycle frame. But I don't need low-power and I need the radar to tranmit and receive data for all the frame. I mean, I don't hope Frame_off time, when the radar stop working. I also want to make the EIRP of tx power bigger. Could you please tell me how to modify the firmware.
Show LessI want to cascade two radars and let them transmit signals at each other's Frame_off time, so as to achieve the purpose of working on the whole Frame. Could you please give me some suggestions on how to modify the firmware and how to do it?
Like the following picture shows:
Show Less
I would like to ask how to achieve BGT60TR13C how to display the speed in real time, just like static_distance, is there a routine or formula
1.I know there is a pulse repetition time, which is 5ms. But according to your doc in this 5ms, ADC works only in the ramp up time that is 1.5ms, which means it acquire raw data in this 1.5ms but not whole 5ms. And if samples per chirp is 256, how to compute the real sample rate? I think in 1.5ms, there are 256 samples, so the sample cycle=1.5ms/256, as a result the sample rate=256/1.5ms=170KHz, What's wrong with it? Could you please show me how to compute the sample rate?
2.sample_rate = number_of_chirps_per_frame/frame_time_sec=10 chirps / 100ms = 100Hz, in this setting up, it's 100Hz, it is right. This frame includes 10 chirps and this frame lasts 100 ms. If you think sample rate is 10 chirps / 100ms=100Hz, which means samples per chirp is 1. So 10 chirps have 10 samples, and in 100ms there are 10 samples. However, samples per chirp is 256. Besides, I think in this one frame 100ms, the TX_EN happens in the first 50ms and there are 10 chirps happens in this first 50ms, whithin every repetition only 1.5ms ADC works. I am so confused about the real sample rate. And I still need you to tell me. And in your User docment I don't see how to compute this varible sample_rate.
3. If I use the original bandwidth 200MHz, what is the sample rate? Could you please show me how to compute it with all the parameters? Just give me an example? really thanks for your time. And If I change the Bandwidth to 1MHz, what is the sample rate?
Show LessHi,
I am using a DEMO BGT60TR13C to capture radar data using the Python SDK.
When my host system is under heavy load, the radar SDK crashes with the mentioned error.
How to reproduce:
from ifxAvian import Avian
with Avian.Device() as radar:
metrics = Avian.DeviceMetrics(
sample_rate_Hz= 2909090,
rx_mask= 7,
tx_mask= 1,
tx_power_level= 31,
if_gain_dB= 33,
range_resolution_m= 0.05,
max_range_m=5,
max_speed_m_s=8,
speed_resolution_m_s=0.5,
frame_repetition_time_s=(1 / 60),
center_frequency_Hz= 60e9
)
radar_config = radar.metrics_to_config(metrics)
radar.set_config(radar_config)
print(radar_config)
while True:
radar.get_next_frame()
Run the python code and a stress test at the same time. For example: stress --cpu 32.
Depending on the system, the python code will crash after a few seconds with:
...
File "/home/stjischl/.local/lib/python3.10/site-packages/ifxAvian/Avian.py", line 300, in get_next_frame
check_rc(self._dll)
File "/home/stjischl/.local/lib/python3.10/site-packages/ifxAvian/Common.py", line 98, in check_rc
raise_exception_for_error_code(error_code, error_description)
File "/home/stjischl/.local/lib/python3.10/site-packages/ifxAvian/Error.py", line 95, in raise_exception_for_error_code
raise globals()[error_name](error_description)
ifxAvian.Error.ErrorCommunicationError: communication error between host and device (IFX_ERROR_COMMUNICATION_ERROR)
This happens on Linux and on both x64 and armv7l. I did not test Windows.
The only solution I found is to manually increase chirp_repetition_time_s and frame_repetition_time_s.