Other Parts Discussed in Thread: MMWAVEICBOOST,
Hi,
I'm doing raw ADC data capture with the IWR6843ISK+MMWAVEICBOOST+DCA100EVM. Using DCA100 CLI plus Studio CLI (from the platform toolbox).
In the mmWave SDK User Guide dated Sept 30, 2020 under the frameConfig settings description "frame periodicity in ms (float values allowed)" there is the following limitation:
"However frame should not have more than 50% duty cycle (i.e. active chirp time should be <= 50% of frame period)."
1) Does this limitation relate to the (activeFrameTime/frameTime) duty cycle where:
activeFrameTime = numChirps*(idleTime+rampEndTime)*numLoops
frameTime = "frame periodicity in ms (float values allowed)" ?
Or is it only when the Tx is actually on so excluding the idleTime?
2) What is the main reason for the 50% duty cycle limitation described in the SDK User Guide?
Is it related to temperature, inter-frame processing in the DSP/HWA, shipping out the demo data on the UART or something else?
Main reason for the questions is to understand what the duty cycle limitation (activeFrameTime/frameTime) really is when using DCA100 CLI plus Studio CLI (from the platform toolbox) for raw ADC capture.
Can I go to 80%, 90%, 100%?
Many thanks,
Neil