Radar sensor Forum Discussions
text.format{('custom.tabs.no.results')}
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
What is the sample rate of the Distance2GoL? Here are some my openion from Infeinon documents:
1. From the above pictures from your documents, I find that it seems that radar samples data only in the period of Ramp Up time and I find that in firaware file the Ramp up time is 1.5ms which can be changed. And if I set number of samples in one chirp is 256 like above pictures, So does it mean in 1.5 ms,there will be 256 samples, so the sample rate=1/(1.5ms/256s)=170.6KHz. Is that right?
2. However, from your matlab code: extract raw data.m, you write:"sample_rate =number_of_chirps_per_frame/frame_time_sec", in this setting up, it's 100Hz??? Really? I think every chirp have 256 samples but not 1 samples. And it's strange that in this code defining a varible sample_rate and I don't find this varible used in the following code. Is that right?
I try to sample data by this radar , so I really need to know the real sample rate. And when I change the Bandwidth to 1MHz, does it change the sample rate of not? I am not sure. Please help me. Thanks.
Is there a way to get the status of TDet and PDet via registers notably in pulsed mode setup via SPI?
Or is there a way to find out the status of TDet and PDet with an algorithm from the ADC values or something else got from the SPI registers?
Show LessHi,
I am developing a very light weight FMCW radar platform with STM32 microcontroller.
It would be very helpful if you can provide a smaller driver than Stratula that supports basic FMCW measurements so I can focus more on signal processing.
The driver should configure the registers and read out FIFO with polling.
Thank you in advance.
Show LessHi. May I know if this KIT_CSK_BGT60TR13C can do heartbeat detection or vital sensing ? What they mean by macro and micro sensing ? If this KIT_CSK_BGT60TR13C can do vital sensing, how to make it, any source code ?
Show LessHi, I have a DEMO BGT60TR13C board and I am having trouble getting it to connect with my computer. When I plug it in using USB, the green LED blinks periodically like it is supposed to, but the SDK example programs can't find the device. I checked the windows USB debugging tool and it isn't even showing up there.
The strange thing is, I have another copy of the exact same board, and it was working just fine. Is this board just a manufacturing error, or is there something else I am missing?
Show LessHi, I am currently developing a radar system based on BGT60TR13C and STM32H7. I followed the code provided on Github, but there are still some problem with my programme.
The bgt60tr13c can be successfully initialized, but the get_fifo_data failed and it returned XENSIV_BGT60TRXX_STATUS_GSR0_ERROR. I found that my GSR0 is like in the figure.
Then I tried the FIFO reset
if (fifo_rslt == XENSIV_BGT60TRXX_STATUS_OK)
{
{
HAL_GPIO_WritePin(GPIOD, PIN_LED_GREEN, GPIO_PIN_SET);
custom_delay(50);
HAL_GPIO_WritePin(GPIOD, PIN_LED_GREEN, GPIO_PIN_RESET);
}
for (int32_t sample_idx = 0; sample_idx < NUM_SAMPLES_PER_FRAME; ++sample_idx)
{
if (test_word != samples[sample_idx])
{
printf("Frame %" PRIu32 " error detected. " \
"Expected: %" PRIu16 ". " \
"Received: %" PRIu16 "\n", \
frame_idx, test_word, samples[sample_idx]);
assert_param(0);
}
// Generate next test_word
test_word = xensiv_bgt60trxx_get_next_test_word(test_word);
HAL_GPIO_WritePin(GPIOD, GPIO_PIN_14, GPIO_PIN_SET);
custom_delay(10);
HAL_GPIO_WritePin(GPIOD, GPIO_PIN_14, GPIO_PIN_RESET);
}
printf("Frame %" PRIu32 " received correctly\n", frame_idx);
frame_idx++;
CDC_Transmit_FS((uint8_t *)samples, NUM_SAMPLES_PER_FRAME * sizeof(uint16_t));
}
else
{
int32_t status = xensiv_bgt60trxx_soft_reset(&my_sensor, XENSIV_BGT60TRXX_RESET_FIFO);
HAL_GPIO_WritePin(GPIOD, PIN_LED_BLUE, GPIO_PIN_RESET);
custom_delay(100);
HAL_GPIO_WritePin(GPIOD, PIN_LED_BLUE, GPIO_PIN_SET);
}
the status for this reset is XENSIV_BGT60TRXX_STATUS_OK, but after that my GSR0 is still the value as I mentioned above.
Could you point me how to make the GSR0 all zero condition as demonstrated in the datasheet that indicates no error?
Thanks!
Show LessI 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 LessProject to sense the child in the car. To avoid the driver accidentally left over the child in the car.
Need to sense with heard beat, body temperature when the child is cover by blanket or in the baby car seat.
Show Less