Radar sensor Forum Discussions

I saw in the data sheet documentation that there are three modes of data flow in FIFO. Does each ADC correspond to an RX antenna? If so, is it necessary to restore the data sequence in ADC number order when receiving the 3ADC data stream.

For example: receiving ADC1, ADC2, ADC3, ADC1, ADC2... do you need to revert to ADC1, ADC1,... , ADC2, ADC2,... , ADC3,...

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E9%9B%B7%E8%BE%BE%E4%BC%A0%E6%84%9F%E5%99%A8/BGT60TR13C-FIFO%E6%95%B0%E6%8D%AE%E6%B5%81%E4%B8%AD%E7%9A%84%E6%95%B0%E6%8D%AE%E7%BB%84%E7%BB%87%E9%97%AE%E9%A2%98/td-p/676032

Show Less

 

Show Less

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 Less

Dear 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

Show Less

Hi @BenGBoo, 

Can you please let us know if you are looking for form factor compatibility? In that case, you are correct, the DEMO DISTANCE2GOL is Arduino header compatible whereas the DEMO BGT60LTR11AIP is Arduino MKR header compatible. The DISTANCE2GOL comes with an XMC 4700 baseboard that runs the Distance2GoL firmware.

Both these radar boards are 3.3 V compatible and can be used with an external microcontroller. These training videos should help with your query - 

DEMO DISTANCE2GOL 

DEMO BGT60LTR11AIP

Additionally, you can refer to the Distance2GoL (Software-Controlled FMCW radar) software user manual for information regarding the Distance2GoL firmware.

Please let me know if you have any further queries.

Show Less

Hello,

I'm using the Position2Go board with the provided Matlab code. I've used the code to successfully transmit/receive one frame obtain a [fast-time x antennas x slow-time] cube using the function

oRS.oEPRadarBase.get_frame_data

(oRS being the RadarSystem object generated by the provided code).

I would like to know which parameter I need to change in the RadarSystem object or which function I need to call to transmit/receive multiple frames, so to obtain a [fast-time x antennas x slow-time x frames] 4-dimensional array.

So far my initialization code is the following, with parameters from an external global structure "p" (p.fs, p.N, p.Ns, p.B_kHz, ...) :

% Create radar system object
szPort = findRSPort; % find the right COM Port
oRS = RadarSystem(szPort); % creates the Radarsystem API object

% Set endpoint properties
% The automatic trigger runs after startup by default
oRS.oEPRadarADCXMC.samplerate_Hz = p.fs; % updates the chirp duration oRS.oEPRadarBase.chirp_duration_ns (upchirp time)
oRS.oEPRadarBase.stop_automatic_frame_trigger;      % stop it to change values
%oRS.oEPRadarBase.set_automatic_frame_trigger(1000000);
oRS.oEPRadarFMCW.lower_frequency_kHz = 24.025e9 / 1000;    % lower FMCW frequency
oRS.oEPRadarFMCW.upper_frequency_kHz = oRS.oEPRadarFMCW.lower_frequency_kHz + p.B_kHz;    % upper FMCW frequency
oRS.oEPRadarFMCW.tx_power = oRS.oEPRadarBase.max_tx_power; % or put an integer value between [0,7], 0 being the lowest power level and 7 the highest
oRS.oEPRadarP2G.pga_level_val = 0; % put an integer value between [0,7], 0 being the lowest power level and 7 the highest
oRS.oEPRadarBase.num_chirps_per_frame = p.N;
oRS.oEPRadarBase.num_samples_per_chirp = p.Ns;       % % updates the chirp duration oRS.oEPRadarBase.chirp_duration_ns (upchirp time). Ns up to 4095 for single RX channel
oRS.oEPRadarBase.rx_mask = bin2dec('0011');         % enable RX1 & RX2 antenna
oRS.oEPRadarFMCW.direction = 'Up Only';

Thank you for your help! Show Less

Hi everyone,

I am working with the demo board Position2Go. I have successfully used the C Communication Library provided by Infineon on my Windows machine to stream the data from the board to my PC.
Now I am trying to make it work on my Ubuntu 16.04 machine, however, I have encountered some difficulties. When I run the script 'extract_raw_data.c' (without compile errors) it looks like my machine is unable to open the device for communication.
In particular, the function 'open()' used in the file COMPort_Unix.c returns -1. In the same file, the variable 'port_name' contains the correct location and name of the device: "/dev/serial/by-id/usb-Infineon_IFX_CDC-if00".
I would like to add that I have not installed any Infineon related software or driver on my Ubuntu machine.
Has anyone encountered a similar problem? What advice can you give? Any help is appreciated. I can provide additional details if necessary.

Thank you very much in advance. Show Less

Hello Infineon Community,

I have 3 queries namely:

1. Using the Matlab interface provided, I managed to capture the speed graph of my target as shown below. Is there any way to show the Fastest Speed, Slowest Speed, Average Speed of this graph? Any Matlab Code/Function that I can use for this?


2. Also, is there any way I can get the graph to display as a function of time instead of frames? From my understanding, my frames interval is left default at 150ms, does this means that there are 6.66 frames per second?

3. Is there any way for me to capture the time and coordinates (distance, degree)? The reason is that I would like to measure the distance my target travelled, so that I can find out the average speed of my target. Alternatively, is there any way I can measure the distance travelled and the average speed of my target?

Any pointers will be much appreciated. Thank you! 🙂 Show Less