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 a student at the University of Trento, Italy. I am currently working on Distance2go board as part of my thesis project. I am facing problem regarding data processing on the board. The raw I and Q data is recevied in MATLAB via the communication library. The data received doesn't show any changes for a stationary object while for moving object shows spikes. My application requires me to observe stationary object. The firmware uploaded to the board is modified version of the generic firmware provided by infineon. The MATLAB script is developed to send pulse, turn off the radar, change frequency and repeat the process.
Is the I and Q data preprocessed before MATLAB receives it? Is there any filtering performed on the data which I am not aware of. Also, what would be timing delay the MATLAB script to actually control the radar? and will this timing delays effect the appication? Let me know if more information is needed to help with this particular problem. According to theory, I should get a spike in magnitude for each object placed between radar and reflector, but I can't even get a spike for the reflector.
Show Less
Here are some questions,
1) Is it possible to run continuosly the CW signal? I understand that I will get target change of displacement as time goes on.
2) If i have a metallic surface (high RCS) that moves about 1mm every 2sec, would this 24GHz doppler radar be able to see? If yes, is there a specific setting to make it happen?
3) I had tried the Infineon Toolbox with various firmware included. What is the difference between the D2G_FMCW.hex and D2G_Doppler_FMCW.hex in terms of chirp/doppler timing? Please explain how the ADC signal is being formed in time. If there is a way to just run Doppler, please point me section in firmware and or Dave project on to enable it.
4) I had seen the Matlab scripts too, same question, is there way to run Dooppler on it by itself?
We are looking at this Infineon as possible HW xx production soon. Any help in our evaluation task would be appreciated. Thank you. Show Less
TIA
Need some clarification on the ramp period.
Existing D2G firmware is pre-configured with 200 us ramp down period (for 'up-chirp only' mode) - #define RAMP_DOWM_TIME_usec (200U) .
The *.tdd file is the result from mixed between received signal and reference.
Basically the signal tx and rx comprises:
up-ramp (user defined) + down-ramp (pre-config) + waiting time between chirps (pre-config) = 1 single chirp.
Q1 - In real, it transmit and receive an almost triangle chirp, right?
Q2 - The *.tdd is result by mixing this two signals in time domain inclusive the down-ramp part?
(If yes, i can use my current code to process a triangle chirp)
Need your clarification as I am post-processing the 'tdd' file via matlab to combine multiple signals (from multiple D2G) to create a MIMO.
Many thanks! 🙂 Show Less
sample UI
I want to built a custom UI for the demo board POSITION2GO. The interface will be like a military radar. I want to fetch the demo board output from serial port and plot those in my custom Radar user interface.
Can anybody please help me how to decode the serial output of the position2go board to get the angle and distance of the object.
Thank you.
Regards 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 read about this in an article and its very cool! Just to clarify - is this dev kit capable of detecting the x,y,z co-ordinates as well as the velocity/motion of the target? Show Less
I'm using BGT24MTR11 chip and I need to calculate VCO frequency based on tuning voltage. Vfine and Vcoarse are equal.
I have found a graph in BGT24MTR11 application note 305, but without equation I can only assume if, for example, at 25 degrees and 1.5V frequency is 24.3GHz or 24.4GHz?
Thanks in advance for any help.
Best regards,
Nenad Show Less
We have purchased 24 GHz Radar and were trying to do some measurements. However there are too many ghost targets appearing on the GUI. We are doing in open space indoor measurements.
Available Options:
Receiver : Rx1,
Gain : High
Target Threshold : 30
Gap Around Target : 1
Filter Static Objects : Off
RCS Compensation : Off
When these settings are done, we are not able to detect the correct range of the target or the angle of arrival.
We removed the metal plate from the current position (7 metres) and asked a human to walk with the same settings, unless he comes to 4.5 m -3.5 m , I dont see any target being detected at all , however we dont see many ghost targets appearing [ Case: Filter Static Objects :On]
I have gone through the code to get the relationship between Gap around the target and Target Threshold, however looks very tedious to find ? Can someone suggest what are the best settings to detect the target stable without ghost targets !!
Thanks and regards,
Kalyan Show Less