• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 730 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.

IWR6843ISK: Maximum duty cycle. Limitation?

Lubo Zegov
Prodigy 50 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843

Hello, 

I have trouble with setting duty cycle of the IWR6843 to 100%. Say if I have a chirp of total time 100us, which is repeated 100 times per frame, and the frame time is set to 10ms, then the duty cycle would be 100%. However, those kinds of settings do not produce results, e.g., when I trigger a frame no data is recorded. Is there some limit on the duty cycle and how is that calculated. 

Thanks. 

  • 0
    TI__Mastermind 30405 points

    Hello,

    Are you using the SDK out of box demo for these tests? Please note that the SDK demo includes software processing to generate point cloud from the ADC data and requires sufficient interframe idle time for the software processing so you cannot configure 100% duty cycle. Please refer to the data path timing in the SDK HTML documentation as shown below:

    file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/demo/xwr68xx/mmw/docs/doxygen/html/index.html

     

    Thanks

  • 0 in reply to Nitin Sakhuja
    Prodigy 50 points

    Hello Nitin, 

    Thank you for you reply. Actually, I think I my question was not clearly defined. I use mmwave studio to acquire raw data and process it with a custom algorithm. So I do not use the SDK out of the box demo. Since I use mmwave studio, I would assume that the processing you mentioned above is only done when I press the "post process button". I do not see a reason why I do not acquire data when duty cycle is 100%, can you please explain if there are some limitation or I am missing something here?

    Thank you in advance, 

    Lubo

  • 0 in reply to Lubo Zegov
    TI__Mastermind 30405 points

    Hi Lubo,

    Thanks for clarifying. Please allow me a few days to check this internally. I will get back to you by Wednesday next week.

    Thanks

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points

    Hi Lubo,

    Thanks for your patience. There is a minimum required interframe blank time of 300us as mentioned in the following thread. 

    https://e2e.ti.com/support/sensors/f/1023/t/979928

    For your given scenario (a chirp of total time 100us, which is repeated 100 times per frame, and the frame time is set to 10ms), you should be able to configure ~99% duty cycle.

    Regards

    -Nitin