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
Hi,
We started a while ago working with the BGT60TR13C development kit to follow the suggested learning curve before jumping into our own design. We have already tried some succesful configurations by using the dev kit and Radar Fusion GUI, so now we have moved to our own PCB, where we have a dedicated host MCU (instead of the one from the Dev Kit).
The SPI communication in our board between the host and the radar works as expected, as also does the initialization (get device id to verify not only that the radar is connected but also that it is a BGT60TR13C, amongst other steps). Just for some context, we are also following the guidelines provided in Inifineon's repository (https://github.com/Infineon/sensor-xensiv-bgt60trxx). We are also using the default presence settings configuration parameters provided with the SDK.
So far so good... except that there was no way of getting data into the FIFO, it constantly reports as if it is empty. We focused on using the data test mode, to discard any issue with the configuration, but still in the data test mode (SFCTL:LFSR_EN= 1B), the FIFO is never filled.
We are following the same sequence as the one implemented in https://github.com/Infineon/sensor-xensiv-bgt60trxx and double checked it also with the one described in the datasheet (10.Enhanced Functions->10.1 Data Test Mode).
Any clue were the issue could be? Is there any other step needed to make the test mode work that is not documented in the datasheet? We are running out of ideas here, so we would really appreciate any help anyone could provide.
Thanks in advance.
Show LessHello,
i am trying to get get Demo BGT60LTR11AIP running in CW mode in Python.
As described in the SDK documentation, the setting for the CW mode would be mode = 1.
But when i run the" device.get_next_Frame(<time>) " method in python, i get the following error:
"ErrorTimeout: device did not acquire a complete time domain data frame within the expected time (IFX_ERROR_TIMEOUT)"
I am not able to find a solution for this problem, to gather the data in cw mode.Am i missing something?
Also i can not find examples for the Sensor, as there seems to only exist examples for other Radarsensors in radar_sdk\examples\py
SDK: 3.5.1
FW 2.6.0
Best,
Kai
Show LessHello sir,
Greetings of the day!
We are developing one project using BGT24LTR11N16E6327XTSA1. For that we need 24GHz 4x1 microstrip patch array antenna.
Can you please suggest the antenna part number or can you provide the document related to the design of 24GHz 4x1 microstrip patch array antenna.
Thanks & Regards
Manisha Tamboli
altiux innovations pvt ltd
Show LessHi,
I am working with BGT60TR13C. I have a demo kit from Infineon on which I run the presence detection code. We have developed a custom PCB with that same BGT60TR13C with ESP32 as MCU interfacing. I received a presence detection code from Infineon running on ESP32. It is working and detecting presence. The output of both the custom PCB and Infineon demo kit slightly differ.
With the same position of both boards, one by one the detection angle in custom PCB is lesser than in the demo kit. The demo kit gives a wider range whereas the custom PCB has less range in terms of angle. I doubt about RF-related issues. for that, I am attaching the PCB reference here . In the Custom PCB center is the Sensor and the rest area is copper and some other sensor.
Radar configuration data is the same in both the cases I have reverse-engineered and make than same in both.
Regards,
Parth Suthar.
Show Less
I just got the demo board for the BGT60TR13C and when I connect it, the Radar Fusion GUI v3.5.4 (on Windows 10) does not detect it.
In the device manager it shows up as a "broken" serial device. The status LED on the board blinks green.
Radar Baseboard MCU 7 V2.2 04-2023
What can I do to debug this?
Thanks
Show LessThis is the error I run into when configuring one of the my scripts:
Error using RadarDevice.check_error_code
a frame was dropped due to communication or buffering issues (data rate too high for
underlying link or memory allocation mismatch) (IFX_ERROR_FRAME_ACQUISITION_FAILED)
These are the parameters I am using:
This seems to run fine on the RadarFusion GUI, so is there a reason why this wouldn't work in a script?
Show Less
Dear all,
I'm in the process of identifying the optimal solution for a range-angle and segmentation algorithm, tailored to a customized device configuration as shown in the figure below. My system is STM32H7, 550MHz with EtherNet TCP interface. Could you please recommend the most suitable configuration for both algorithms?
Thank you very much.
#ifndef XENSIV_BGT60TRXX_CONF_H
#define XENSIV_BGT60TRXX_CONF_H
#define XENSIV_BGT60TRXX_CONF_DEVICE (XENSIV_DEVICE_BGT60TR13C)
#define XENSIV_BGT60TRXX_CONF_START_FREQ_HZ (58500000000)
#define XENSIV_BGT60TRXX_CONF_END_FREQ_HZ (63000000000)
#define XENSIV_BGT60TRXX_CONF_NUM_SAMPLES_PER_CHIRP (64)
#define XENSIV_BGT60TRXX_CONF_NUM_CHIRPS_PER_FRAME (32)
#define XENSIV_BGT60TRXX_CONF_NUM_RX_ANTENNAS (3)
#define XENSIV_BGT60TRXX_CONF_NUM_TX_ANTENNAS (1)
#define XENSIV_BGT60TRXX_CONF_SAMPLE_RATE (2000000)
#define XENSIV_BGT60TRXX_CONF_CHIRP_REPETITION_TIME_S (0.000299787)
#define XENSIV_BGT60TRXX_CONF_FRAME_REPETITION_TIME_S (0.100086)
#define XENSIV_BGT60TRXX_CONF_NUM_REGS (38)
#if defined(XENSIV_BGT60TRXX_CONF_IMPL)
const uint32_t register_list[] = {
0x11e8270UL,
0x30a0210UL,
0x9e967fdUL,
0xb0805b4UL,
0xd102bffUL,
0xf010d00UL,
0x11000000UL,
0x13000000UL,
0x15000000UL,
0x17000be0UL,
0x19000000UL,
0x1b000000UL,
0x1d000000UL,
0x1f000b60UL,
0x2113fc51UL,
0x237ff41fUL,
0x25001ce7UL,
0x2d000490UL,
0x3b000480UL,
0x49000480UL,
0x57000480UL,
0x5911be0eUL,
0x5b66dc0aUL,
0x5d01f000UL,
0x5f787e1eUL,
0x61b07deaUL,
0x63000a41UL,
0x65000172UL,
0x67000040UL,
0x69000000UL,
0x6b000000UL,
0x6d000000UL,
0x6f2a0b10UL,
0x7f000100UL,
0x8f000100UL,
0x9f000100UL,
0xad000000UL,
0xb7000000UL
};
#endif /* XENSIV_BGT60TRXX_CONF_IMPL */
#endif /* XENSIV_BGT60TRXX_CONF_H */
Show Less
Hi,
May I ask if it's possible for me to read the raw data from BGT60TR13C Radar Demo Board directly by connecting SPI or UART pins of Demo Board to ESP32 board?
For now, the BGT60TR13C Radar Demo Board can only transmit the data to my laptop via USB. However, I want to configure it to wireless data transmission with Bluetooth or WiFi, which reminds me of connecting it with ESP32. I noticed that there are Arduino MKR connectors available on Demo boards but I don't know how to configure them to make MCU transmit raw data via those pins.
May anyone offer me any help? It will be appreciated a lot!
Regards,
Sam
Show LessCan Doppler the Doppler modulation mode of this radar measure speed? BGT60LTR11AIP How do you know if the Doppler modulating mode is pulsed or continuous? How do I know the FM Slope and FM Bandwidth of My Radar? The written text document is shown in Fig.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E9%9B%B7%E8%BE%BE%E4%BC%A0%E6%84%9F%E5%99%A8/Excuse-me-BGT60LTR11AIP-can-the-Doppler-modulation-mode-of-this-radar-measure/td-p/653487
Show LessI am using the static_distance.py algorithm from the RDK. Is it possible to change the radar field of view from the standard 40/45 degrees? I would like to narrow this 3D conical field of view to receive data from the radar at a more precise location. If this is possible, which file can I edit to achieve this?
Show Less