Position2Go Interframe Time

[dc98]

Hello, I am currently working on running some experiments on the Pos2Go radar. I had a few questions regarding the interframe time and the set automatic frame trigger property. Can I set the interframe time to 0 and have the radar continuously send chirps, for example send a first frame with 32 chirps and then immediately (ideally 0 or 100 micro seconds after to be considered as idle time) send another frame with 32 chirps. If not what is the minimal interframe time possible and how is it set or specified.

[George_T]

Hi @dc98 ,

Please note that the inter-frame time/delay can not be set to zero as this will make the distance estimation difficult as there is no reference.

While using Radar GUI for recording the data, the inter-frame delay can not be changed.

Thanks and regards

George

[Montassar-BR · Accepted solution]

Hi @dc98 

Please downlaod the https://softwaretools.infineon.com/tools/com.ifx.tb.tool.position2gokit2 package where you can find the Position2Go FW Source files. In radar_base.c file, refor radar_get_min_frame_interval() API, where the min frame interval is computed.

  *min_frame_interval_usec = ds_device_get_settings()->pll_num_of_chirps_per_frame * (ds_device_get_settings()->pll_chirp_time_usec + PLL_RAMP_DOWM_TIME_USEC + PLL_STEADY_STATE_USEC) + bgt_duty_cycle_delay_usec + ALGO_PROCESS_TIME_USEC;

The min frame interval (inter-frame time) is dependent on:

• pll_num_of_chirps_per_frame: default 16
• pll_chirp_time_usec: default 300us
• PLL_RAMP_DOWM_TIME_USEC: Ramp down time for SawTooth Chirps in the PLL: 100us
• PLL_STEADY_STATE_USEC: Steady state delay before starting next chirp in the PLL: 100us
• bgt_duty_cycle_delay_usec: 1000us or 3000us (depends on duty-cycle)
• ALGO_PROCESS_TIME_USEC

Hope that gives on overview on the timing charac on the Position2Go.

Cheers,

Montassar.