• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 334 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.

Original question:

TDA3: Monopulse Algorithm plugin

TDA3LA: Monopulse Algorithm Plugin Development

Khai Trinh
Genius 4140 points

Part Number: TDA3LA

If I have a usecase as below:

UseCase: chains_radarMetawaveMonopulse

IssCapture -> Alg_RadarProcess_fft (DSP1) -> Dup_fft (DSP1)
Dup_fft (DSP1) -> Merge_swms (DSP1)
Dup_fft (DSP1) -> Alg_RadarProcess_pkDetect (DSP1) -> Merge_swms (DSP1)
Dup_fft (DSP1) -> Alg_RadarProcess_pkDetect (DSP1) -> Merge_swms (DSP1)

Merge_swms -> Alg_RadarProcess_guardRemoval (DSP1) -> Sync_network -> NetworkTx (IPU1_1)

The output of 2D FFT will produce 4 RDMs from 4 RX and 1 TX channels. It is then duplicated into 3 streams with 2 streams going into 2 pkDetect as inputs. We would like the two pkDetect links to operate on different RX channels. For example, we would like pkDetect 1 to process RX0 and RX1 while pkDetect 2 to process RX2 and RX3.

My question is how can we instruct (configure) each of the pkDetect link in the graph to process different RX channels. If both paths process all 4 RXes, that would be easy but we like them to only process 2 out of 4.

Thanks,

--Khai