• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 451 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.

AWR1843BOOST: Radar interference measurement setup

User1704
Prodigy 100 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: DCA1000EVM, AWR1843

I need to put together a mutual Radar interference scenario, for which I'm planning to use the AWR1843 boosterpacks. My question really is, what additional kit will I require to make a realtime measurement setup? Will only the boosterpacks suffice, or will I need the DCA1000EVM as well? Also some pointers to any accessories that would make our life easy to either program the kits or transfer the data to the computer or auxiliary processing to complete our test setup will be great! We need a realtime demonstrator rather than offline processing. I need to connect each kit to a PC and display the interference from the other radars in realtime. Then I will implement some processing algorithms on each kit to see how well each radar processor has handled the interference.

  • 0
    TI__Genius 15046 points

    Hi,

    We will be releasing a new lab for interference detection and mitigation shortly under the mmWave platform toolbox. It is expected to be live on TIREX by the end of this week or early next week.

    An easy real-time metric of interference and interference mitigation capabilities is the noise profile in the mmWave Demo Visualizer. If The device encounters interference continuously, its noise profile would be raised. If interference mitigation techniques implemented work well, the noise profile would not be as high in the presence of an interferer.

    If you are interested in real time visualization only, a data capture board isn't necessary, but it might come in handy if you would like to capture raw ADC data for the development of your interference detection/mitigation algorithms.

    One thing to keep in mind is the synchronization between the two boards. If both boards are configured to chirp normally, it would be hard to get predictable and repeatable interference events due to the RF idle time. Our solution was to use an EVM as a dedicated interferer transmitting continuously at a fixed frequency (see mmwavelink's rlSetContModeConfig and rlEnableContMode). This interferer EVM won't output any data. A second victim EVM running the mmWave out of box demo can be used to see the effects of interference. This would always lead to one interference event per chirp (as long as the interferer's fixed frequency falls in the band of the victim EVM)

    If you must configure both EVMs to chirp and output data, you would need to synchronize them with each other to get repeatable interference events. This can be done, but will be more involved.

    Finally, you can see this app note for details of interference detection, mitigation and avoidance techniques on our sensors.

    Regards,

    Aayush