AWR1843AOP: Radar Monitoring APIs implementation

Hi Koichiro,

Can you please confirm the reason for not using the same back-off for power monitor as functional chirp? This is Possible by creating a dummy profile in the profile configuration API with a different Back-Off. While configuring the Tx Power monitor, there we can pass the dummy profile id.

FW decides the RF frequencies for monitoring chirps and the Chirp Bandwidth cannot be increased as these are in FW control.

Hi Koichiro-san,

Koichiro Tashiro said:

He also want to change transmit chirp bandwidth, chirp interval, etc. used for TX Power Monitor.
Currently transmit chirp bandwidth is 100MHz, interval is 50usec. He want to change them.
Is it feasible?

No, this is not feasible. The monitoring chirps which are sent over by the device the user does not have control over them. In AWR2944 device only that control is provided for only some of the monitors. 

Koichiro Tashiro said:

My customer is trying to implement Radar Monitoring API.
He wants to change transmit power (BackOff) used in TX Power Monitor and asks for sample code how to implement AWR_CAL_MON_FREQUENCY_TX_POWER_LIMITS_SB.
Do you have sample code?

In the configuration of the TX power monitor the user can choose which profile to be used for the monitoring. For this profile the user can set the desired backoff and that itself will be used for the monitoring.  

You can refer to the OOB demo for reference implementation. 

Thanks,

Pradipta.

Hi Pradipta,

Pradipta Bandyopadhyay said:

You can refer to the OOB demo for reference implementation. 

The customer checked OOB demo source code, but could not find the reference code for Radar Monitoring API implementation.
Could you point me exact location (file and line#)?

Thanks and regards,
Koichiro Tashiro