• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 5 answers
  • Subscribers 31 subscribers
  • Views 686 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR1843BOOST: Improve TLV3 frequency

Ben Babu
Prodigy 90 points
Part Number: IWR1843BOOST


how we can increase TLV3 frequency and what code modifications needs to be done for the same? we are trying to improve number of points to cluster so is it possible to increase the number of TLV3 by modifying any parameter?

  • 0
    TI__Mastermind 20770 points

    Hello.

    Are you referring to the TLV associated with the noise profile?  If you are looking to increase the number of points detected, I would recommend you change the CFAR threshold in the cfarCfg so that more points are included in the pointcloud.  However, if you need a higher baud rate to transmit the data, there is a CLI command in SDK 5 called baudRate that allows you to change the UART baudrate.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points

    Hi Sir, Thank you for your reply.

    I referred the CFAR threshold, but didn't find any particular variable that directly influence the number of points. Could you please mention the change required and in which file I can found it.

  • 0 in reply to Ben Babu
    TI__Mastermind 20770 points

    Hello.

    In the configuration file, if you look at the second to last argument in the cfarCfg CLI command, this threshold will determine whether more points are picked up or less points are picked up by the sensor.  As this number decreases, the threshold to be classified as a point decreases, meaning you will have more points to work with(albeit those points may have a lower SNR).  But this will allow you to increase the number of points in the scene.  Please refer to the SDK user guide for more information on this.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points

    HI sir, we are using MRR demo, so is it possible to configure that binary also?
    I have seen that the RF config parameters can't sent via UART.
    I tried and succeeded the modification of SNR value with the out of box demo given TI radar toolbox itself, but in our case we are using MRR demo, and analyzing using MRR visualizer.

  • 0 in reply to Ben Babu
    TI__Guru**** 150704 points

    Hi,

    Please let us know for what type of application you plan to use the MRR demo. Are you using the MRR mode only or the USRR mode only or both modes?

    TLV3 is related to tracking, so you are probably using MRR mode since only MRR mode supports tracking.

    The MRR demo has been optimized for specific use cases and may not be working for other .

    What frame rate are you trying to achieve?

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 90 points

    Hi Cesar, we are using both MRR and USRR mode. And we are trying to achieve 15 to 20 FPS

  • 0 in reply to Ben Babu
    TI__Guru**** 150704 points

    Hi,

    The frame rate is dependent on the the MRR SUBFRAME PERIODICITY and the USRR SUBFRAME PERIODICITY

    Please see

    mrr_config_chirp_design_MRR120.h

    #define SUBFRAME_MRR_PERIODICITY_VAL           (6000000U) // 30ms

    mrr_config_chirp_design_USRR30.h

    #define SUBFRAME_USRR_PERIODICITY_VAL           (6000000U) // 30ms

    So currently, the demo runs at 16.6 FPS

    Please try to decrease these values and check if the demo still runs.

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 90 points

    Hi Cesar,

    How we can interpret that how much FPS that we getting while testing with our required scenario. I have got the point to increase FPS by modifying PERIODICITY.

  • 0 in reply to Ben Babu
    TI__Guru**** 150704 points

    Hi,

    I think the easiest way is to decrease the following values to determine what is the smallest periodicity that works for your use case

    Ben Babu said:
    How we can interpret that how much FPS that we getting while testing with our required scenario.

    mrr_config_chirp_design_MRR120.h

    #define SUBFRAME_MRR_PERIODICITY_VAL           (6000000U) // 30ms

    mrr_config_chirp_design_USRR30.h

    #define SUBFRAME_USRR_PERIODICITY_VAL           (6000000U) // 30ms

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 90 points

    HI,
    understood that modifying periodicity will effect in FPS, my question is that Can I monitor that how much FPS that I'm getting using any visualizer or any kind of tool. Also as you mentioned periodicity in mrr_config_chirp_design_MRR120.h and mrr_config_chirp_design_USRR30.h, but here we have additionally

    * mrr_config_chirp_design_MRR80.h, 

    * mrr_config_chirp_design_USRR20.h, 

    * mrr_config_chirp_design_USRR50.h.

    So do I need to modify them also?

  • 0 in reply to Ben Babu
    TI__Guru**** 150704 points

    Hi,

    Ben Babu said:
    understood that modifying periodicity will effect in FPS, my question is that Can I monitor that how much FPS that I'm getting using any visualizer or any kind of tool.

    The application will run at the FPS that was configured. There is no need to monitor it.

    Ben Babu said:

    * mrr_config_chirp_design_MRR80.h, 

    * mrr_config_chirp_design_USRR20.h, 

    * mrr_config_chirp_design_USRR50.h.

    So do I need to modify them also?

    These files are provided as examples of different configurations.

    Only one configuration is included in the built and used.

    Please see

    labs\lab0007_medium_range_radar\src\common\mrr_config_consts.h

    I will close this thread.

    For new questions please start a new thread

    thank you

    Cesar