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
Hi,
How to run C-based D2GL_basics example in Linux.
Thank you
I have a mmwave bgt60tr24 sensor and i am trying to understand the IF Signal, i think it's amplitude vs time. I get around 36 frames in a second and each frame has 32 samples.
I am trying to calculate distance of an object from the sensor.
Any help is appreciated
Thanks
Show LessI know I can extract Raw data with Radar GUI. I was also able to use the C library to do it. But can I do this with the processed data, or is it mandatory for me to process it?
Show Less
Hello ,
I am using BGT60 TR13C for human detection i used presence detection and range angle algorithm, but the problem I got is that it displays the result after 3 to 4 sec, and it counts it twice. can you provide me with some suggestion that I can detect instantly?
Show LessHi,
I am trying to use the Rapid IoT Connect Platform with the XENSIV™ KIT CSK BGT60TR13C.
When I get to the submit step I am trying to press "save" but nothing happens and no error appears. What could I be doing wrong to make it not work like this?
Thank you!
Hi everyone
Could you tell me more about Sensitivity within the "Radar Fusion GUI" tool?
For example, which register settings will be used?
Also, how can I configure settings when using the SDK (Python sample source code)?
Thanks
Yang
Show LessDear Sir,
Currently, we are testing DISTANCE2GOL EVM , however, we found it only can detect one object at a time and a maximum speed around 10km/hour. Are both functions fixed in this kit? Can we detect more objects and implement more high speed? thanks.
1. Detection one object
2.10km/hour
Show Less
Hello there,
I recently got a BGT60TR13C DEMO board for my research. I have downloaded the Python API and the radar fusion GUI, which both work well and are quite useful. However, I have some questions regarding the parameters of the radar sensor itself. For real-time applications, I need to know more about the chirp and frame design. Below is a screenshot of my configuration of the sensor:
As you can see, now we have some known parameters:
chirp_repetition _time = 591μs
frame_repetition_time = 0.04 sec
ADC_sampling_frequency = 2 MHz
num_samples_per_chirp = 64
num_chirps_per_frame = 64
However, I have some confusions in the following questions, could you confirm whether my understanding is correct? If not, could you provide the right answer?
a) The chirp repetition time here is actually the up-chirp time + the inter-chirp idle time, right?
b) As ADC_sampling_rate * num_samples_per_chirp = 32 μs, comparing with the chirp_repetition_time 591 μs, this is weirdly small. Does that mean the up-chirp time is actually 32 μs and the rest of the time is just the inter-chirp idle time? In this case, the sensor's duty cycle is less than 10%, this can't be true. Is there a possibility that the actual up-chirp time is a fixed value and it is much longer than my calculation, you are just sampling some of the data from the start of the chirp based on the setting of num_samples_per_chirp? Where can I find these parameters, such as the actual up-chirp time, inter-chirp idle time, and the inter-frame idle time?
c) As chirp_repetition_time * num_chirps_per_frame = 0.037824 sec, so the inter-chirp idle time is : frame_repetition_time - 0.037824 = 0.002176 sec. Is this correct? Did I miss anything in the calculation?
d) Is there a way to get the actual time index of each ADC data point? Or you normally just use the entire frame data as one measurement of range-doppler and the small time differences in real-time can be neglected? In this case, it is equivalent to getting 25 measurements per second, and the time index for the measurement is simply 0.04 * chirp number.
e) This question is specifically related to the python api. The rx_mask will determine which receiver is activated. For example, When rx_mask = 1, the R1 is activated. But how this actually works? It seems like rx_mask = 7 will activate all receivers 1,2, and 3. What if I want to select receiver 2 or 3 solely?
Thank you very much for your time and patience, and I am looking forward to your replies.
Best regards
Show Less