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
My radar is Distance2GoL.
I reconfigure the firmware in config.h, make the one frame is 40ms, each frame has 10 pulses, and each pulse lasts 2ms.
First when I charge the board and use OSC to watch it's TX_EN, everything is finr just like I set. Here is the picture of the TX_EN:
But, when I start use matlab to acquire the raw data, when I run the matlab code, it has been changed.
Here is the TX_EN when I start to rum the matlab code:
Please tell me why this matlab code just for acquire the raw data will affect the radar, what should I do to modify the matlab code?
Show LessAre there available instructions or guidance on connecting the BGT60TR13C development kit to a jetson orin nano? Or a way to compile the sdk for the jetson? Following the "Building SDK from source code" in the RFS SDK Documentation in the radar_sdk didn't work for compile or install using python wheel.
Show Less
I tried to configure it using the above code, but it reports an error at device.set_acquisition_sequence(sequence).
Using the sample program found in the official distance_fft.py, using the
Perform the configuration. Is there any way to use config to configure it, or convert config to metrics and then configure it?
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E9%9B%B7%E8%BE%BE%E4%BC%A0%E6%84%9F%E5%99%A8/BGT60TR13C-%E5%A6%82%E4%BD%95%E4%BD%BF%E7%94%A8%E5%8F%82%E6%95%B0%E9%85%8D%E7%BD%AE%E4%BC%A0%E6%84%9F%E5%99%A8%E8%8E%B7%E5%8F%96%E6%95%B0%E6%8D%AE/td-p/743081
Show LessHi
I am developing a radar module using BGT60TR13C+ STM32F730.
Since the library provided by Infineon cannot be used directly on the STM32 chip, we are developing a method of writing/reading information by directly accessing the registers provided in the manual.
I would like to ask a question as I have found some problems in proceeding with this method.
1) Is BGT60TR13C operated at default settings when external power is connected?
2) If there is no default setting, which register should be set to operate TX, ADC, etc. of BGT60TR13C?
3) What settings value are needed to drive BGT60TR13C for basic operation?
4) Is there a register full manual for setting and obtaining information?
5) Is there a way to apply/port the code provided by Infineon to the STM32 chip?
Thanks for your time
Regards
Oneman
Show LessHi, I am new to radar sensors.
To analyze radar data, I have plotted FIFO data read from BGT60TR13C in time domain.
My concern is whether the data in the form below is read correctly.
Could you please tell me what the raw data in the time domain usually looks like and if it is correct?
Show Less
I am now using the ESP32 to stream the raw radar data from XENSIV™ BGT60TR13C radar wing board (SP005568071) through UDP. For each chirp in the radar setting, I have 128 ADC samples. But I found that there was always a noise at a fixed frequency as shown in the attached figure. I tried to change the sampling frequency but this noise was still there. Do you know what caused this issue?
Thank you!
Show LessI set up a new project to test the MCU 4700. And I try to use P2.8 output a high level, because according to your user manual that P2.8 is not connected to any signal.
Here is my testing firmware:
However, it still does not work, I can't test a high level in P2.8.
Could you please tell me what' going on here?
Show LessIn the BGT60LTR11AIP shield XENSIV™ 60 GHz radar system platform application note, under SPI mode and motion detection algorithm, it states that a detection range of 14m is possible and that the firmware used to achieve this is the “Radar Advanced Motion Sensing with SPI” application available from the Radar Fusion GUI is used. However, I have tried downloading the radar fusion GUI and it is not clear how this algorithm works. I am trying to integrate the BGT60LTR11AIP into a product that will be mounted at 8m and currently i am only getting detection at around 4m so would like to see how this advanced motion detection range is possible.
Show LessMy radar is Distance2GoL. When I change the FMCW_PULSE_REPEAT_TIME from 5ms to 2.5ms
I use an oscilloscope to check the TX_EN, however, it's look like this:
I think it's wrong. If one frame lasts 100ms, and there should be 10 chirps in one frame and every chirp lasts 25ms. However, the TX_EN shows that this is only one chirp in a frame and the chirp lasts 25ms??? It's contradictory with the firmware.
Could you please tell me why?
And I here is my requirement, colud you please provide some suggestions for firmware modification? Because ADC only only works in the up chirp time(1.5ms) according to your doc. And in pluse repetition time(5ms_default), only 1.5ms/5ms=30% duty cycle when the radar is acquaring raw data. I want to realize the radar acquires raw data as the most as possible. So I think if I change the pluse repetition time(5ms_default) to 2.5ms, the duty cycle becomes 1.5/2.5=60%. So I met the problem I describe above.
And I think just modify pluse repetition time is not enough, Because frame rate is 10Hz, and every 100 ms there is a frame. In the frame, just the first 2.5ms*10 chirps=25ms the radar will acquire the raw data(in fact only every 1.5ms*10 chirps in this 25ms ADC works). So Can you provide some suggestions?
Hi, currently i am running MQTT Client : Human Presence Detection using KIT_CSK_BGT60TR13C. When I doing step 3 at the Operation it shows an error at the Eclipse IDE Terminal. The error "MQTT connection failed with error code 0x8260007. Retrying in 2000 ms. Retries left: 75"
How to solve this error ? I would prefer to use Local Mosquitto Broker than AWS
Show Less