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'm trying to evaluate data I recorded with the RadarGUI to get the same results as the RadarGUI shows me. I'm working with a Distance2Go Demo Board.
The D2G board detects two targets and displays both in the RadarGUI, so far so good. Then I used the record function to record the IQ data, the FFT data and the target info data.
Now I'm trying to evaluate the recorded FFT data to get the same target info (range and level) as the RadarGUI shows me. However, I cannot get it to work (I'm using MATLAB).
The recored FFT data (can be easily pasted into MATLAB) is attached to this post. The FFT bin size is the sampling frequency divided by the FFT size which is 166666 Hz/1024=162.76 Hz. To get the desired info I should have peaks with a beatfrequency as follows:
1304.6 Hz, 2609.3 Hz. Therefore the results I should get are: target 1) level: 1341, range 260 cm and target 2) level: 882, range 139 cm. So the 1304 Hz are connected to target #2, and the 2609 Hz to target #1.
I am trying to find the FFT peaks with the following MATLAB function:
[lvl,idx]=findpeaks(fftdata,'MinPeakHeight',10);, where 10 is the range threshold and fftdata is a vector that contains the data from the attached file.
The values in lvl correspond to the levels mentioned above. But there is a problem with the beatfrequency. I calculate it by
fbeat=idx.*binsize;. By doing so, I don't end up with the frequencies mentioned above. What am I doing wrong?
Another problem is that I get 11 instead of 2 results by doing that...
I appreciate your help! Show Less
in D2G v1.2.0 (Radar_D2G_Doppler_FMCW project in DAVE) there are two IF scale factors defined, one for FMCW range processing and another one for Doppler/speed evaluation.
In Radar_D2G_Doppler_FMCW\Algorithm\src\fmcw.h, line 95 it is said: 'Floating point scale applied to the FFT spectrum to enhance the visibility of targets'. The value is calculated by the following formula in fmcw.c:
(FMCW_IQ_SCALE * 3.3f / 4095.0f) = 16*3.3/4095 = 0.001289.
In Radar_D2G_Doppler_FMCW\Algorithm\src\doppler.h, line 77 it is said: 'Scale to be applied to the raw IQ data defined by \ref DOPPLER_IQ_SCALE'. The formula in doppler.c is:
(if_scale * 3.3f / 4095.0f) = 8*3.3/4095 = 0.00645.
Can someone tell me more details about these values? Why do they enhance the visibility of targets? What is the idea behind the formulas? Why 3.3? Why 4095? Is the 4095 related to the 12 Bit ADCs, so it would be (2^12)-1=4095? Why?
I appreciate your help 🙂 Show Less
I'm using the Distance2Go board with the Doppler and FMCW firmware (Radar_D2G_Doppler_FMCW in DAVE) and in /Algorithm/src/doppler.c line 130 it is said:
g_doppler_velocity = g_doppler_frequency / 44.4f;
where
g_doppler_frequency = maxBin * doppler_Hz_per_bin
is defined the line above.
doppler_Hz_per_bin = sampling_freq / (float32_t)FFT_SIZE; which would be 20 kHz / 1024 = 19.53125 Hz per bin in my case (FFT size is 1024).
This gives a g_doppler_velocity of maxBin * 19.53125 Hz / 44.4.
What does the 44.4 stand for? Does it have to do with the velocity resolution? How is that calculated? What is the unit of 44.4? Since the result needs to be in km/h, Hz is 1/s and maxBin is just a value with no unit, the 44.4 should be in 1/km if the factor 3.6 for m/s to km/h is already included.
But where does that come from? And is that even valid? Isn't it that I converted 1/km in m/s which is not possible?
I'd appreciate your help to find out about the 44.4. Too bad there isn't any comment in the source code...
In addition I'd like to know how long is the Doppler CW chirp? Does it have the same duration as the global variable for the chirp time for the FMCW chirps?
Thanks! Show Less
When I record data I can read it into Matlab, but then I'm not sure what I'm looking at!
For example, if I record Time domain data, the help file says its I and Q signals, but the data recorded as a string of complex numbers, so I'm not sure how this relates to time domain data
Can anyone explain this, maybe with an example of how to process it? Show Less
I've changed IFI and IFQ to high gain going into ADC. However, when I load Radar GUI go into Time Domain ADC values, I still see old, low gain values. Is it because Radar GUI is hardcoded? Is it recommended to import data into Matlab and do FFT myself? Show Less
I am new on Microwave sensor and we are planned to use BGT23MTR11 as Motion sensor we have some specific requirement which is,
1.Human presence detection without false triggering
2.Avoid to detect Inanimate object Ex. Curtains, Plant, Fan
3.Detect fine Motion of person ex.Typing action
Thanks & Regards,
Rahul Surawase Show Less
I'm thinking kinda like people do with the Xbox Kinect. See this link for an example https://youtu.be/_cKb3oEM47E?t=1m29s
Thanks for any help or explanations that you can give 🙂 Show Less
The COM port dropdown list is empty. Is there some needed firmware on the device that is not loaded? Since nothing was showing, I loaded the Radar_D2G_FMCW.hex and still nothing. What am I missing here? Show Less
What is the accurate TX and RX port impedance of BGT24LTR11N16 ?
In Table 4 of the LTR11 datasheet, the TX load impedance is 50 ohm, and in Table 5, RX input impedance is also 50 ohm.
In fact, the impedance should be a complex, e.g. in datasheet of BGT24MTR12, the two RFIN port impedance are15.9-j18.4 and 15.7-j18.9.
I need the port impedance of LTR11 because I've to design a specified microstrip structure.
Thanks in advance.
Best Regards,
Jhon Show Less