• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 319 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:

IWR6843AOP: Speed up the frame rate of overhead_3d_people_count

IWR6843AOP: about the chirp pattern of overhead_people_counting

Tom Fisher
Expert 1440 points
Part Number: IWR6843AOP

Hi,

I am working on the overhead_people_counting demo and find there is a line in the gui/overhead_demo_visulaizer.m:

P.dataPath.numTxElevAnt = 0;

Why is the numTxElevAnt is 0? Is this demo not a 3-D based?

Cheers,

Tom

  • 0
    TI__Mastermind 30405 points

    Hi Tom,

    The demo is 3D based as you can confirm from the configuration file as well as the point cloud and tracker visualization. If you have Matlab, you can run the visualizer from source in Matab, which will allow you to rotate the point cloud and tracking window views in 3D to confirm this.

    The following lines in the configuration show the enabled TX channels (bitmap:  Binary 111) and their association with the respective chirps:

    channelCfg 15 7 0

    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    lowPower 0 0
    profileCfg 0 61.2 60.00 17.00 50 657930 0 55.27 1 64 2000.00 2 1 36
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    chirpCfg 2 2 0 0 0 0 0 4

    The configuration file is sent as-is to the demo program running on the sensor as you can see from the Terminal window opened by the visualizer.

    I will need to check on if and what the above variable is used for so please allow me a couple of days. I will get back by Tuesday next week.

    Regards

    -Nitin 

  • 0 in reply to Nitin Sakhuja
    Expert 1440 points

    Hi Nitin,

    Thanks for your reply and take your time.

    Cheers,

    Tom

  • 0 in reply to Tom Fisher
    TI__Mastermind 30405 points

    Thanks for your patience.

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points

    Hi Tom,

    Thanks for your patience again. I got a chance to look at the visualizer code. If you look at the statement just above the one you mentioned, it's counting all three antennas in the numTxAzimAnt itself. The overhead demo is inherently a 3D only demo and always expects all three TX antennas to be enabled.

    Line 1135

                P.dataPath.numTxAzimAnt = bitand(bitshift(P.channelCfg.txChannelEn,0),1) +...
            bitand(bitshift(P.channelCfg.txChannelEn,-1),1) + ...
            bitand(bitshift(P.channelCfg.txChannelEn,-2),1);
            P.dataPath.numTxElevAnt = 0;

    Hope this answers your question.

  • 0 in reply to Nitin Sakhuja
    Expert 1440 points

    Hi Nitin,

    From the point of the RF front, all three TX antennas are used to build chirps for both azimuth and elevation directions. However, only two TX antennas are used from the point view of data processing namely Data Path and this is why the line I mentioned is confusing me. 

    I read all the matlab code in the visualizer and you are absolutely right that line is just for displaying the number of antennas used and irrelavent with the Data Path. It seems that I have to dig inside into the firmware code.

    Thanks

    Tom