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

AWR1843: Chirping without transmitting

Sebastian Brueckner
Intellectual 395 points
Part Number: AWR1843

Hi all,

I would like to implement 'listen before talk', scanning the spectrum before starting the actual radar waveform.

To do that, I need to generate chirps with the transmitter turned off. The receiver would be working normally and receiver LO would still be chirping, turning the AWR18 into a swept receiver that catches transmission from potential interferers.

I am using the mmwave SDK 3.5 AWR1843 OOB demo:

The only option to chirp with little Tx output appears to be setting the Tx power backoff to its maximum of 20 dB. Ideally it would like to reduce the transmit power further. Disabling the Tx in the "channelCfg" or "chirpCfg" CLI commands leads to an error.

Is there a better way to achieve the desired behavior?

Best regards

Sebastian

  • 0
    TI__Genius 17265 points

    Sebastian,

    You may want to take a look at the Interference Demo that is included in the mmWave Platform Toolbox. I believe the behavior in that lab may give you a good starting point.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    Alec,

    thanks for the pointer, I had not seen the interference lab before. I had a look at the code: It processes the ADC data during normal radar operation and removes any spikes caused by interference.

    Unfortunately, that does not help me with my original questions.

    Is it possible to configure a waveform to generate ramps without transmitting anything?

    - Sebastian

  • 0 in reply to Sebastian Brueckner
    TI__Genius 17265 points

    Sebastian,

    After digging into this a bit more, I see that at the device-level, a chirp with TX's disabled should work fine. I expect that there is something in the software that is considering it an error since this isn't a use case we expected to support. You may want to try to disable this error in the SW so that you can continue to send over a chirp cfg that doesn't utilize the TX antennas

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    Alec,

    thanks. I will report back once I had a chane to try with the error cecking disabled.

    Sebastian