• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 419 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.

IWR1642BOOST: People Counting and Tracking with Wireless Configuration Using CC1352R1

Isaac Mears
Intellectual 530 points
Part Number: IWR1642BOOST

I am doing the People Counting and Tracking Using mmWave Radar Sensor With Sub-1 GHz Ref Design. In section 2.2.4.3  of this document it says "Added additional command "pointCloudEn 0\r" to disable the point cloud to reduce the burden of the CC1352 device by providing a smaller frame for it to read." We want to actually use the People Counting GUI with our wireless configuration. 

Is this possible? Can I  delete that command from the firmware and use the People Counting GUI wirelessly? How will this affect the system?

  • 0
    TI__Mastermind 28055 points
    Hi Isaac,

    Currently, the People Counting Firmware automatically configures. As such, you will not be able to edit that command in the configuration file. If you want a more robust code-base, please see section 3.1.2.4 of the TI Design to find a starting point to use to build the lab. You will have to modify the CC1352 code to accept the point cloud data as well as the tracker data.

    Regards,
    Justin
  • 0 in reply to Justin Curewitz
    Intellectual 530 points
    Ok, can you please provide information on how to do this?
  • 0 in reply to Isaac Mears
    TI__Mastermind 28055 points

    Hi Isaac,

    Currently, the situation is that the firmware that has been built for the CC1352 will only work to send the track data, and is not built to send the point cloud data. Do the following:

    1. Modify the configuration the CC1352 sends to the IWR to enable the point cloud instead of disabling it.
    2. The CC1352 parses the output from the IWR and sends a simpler bit stream.  This parsing will need to be modified to send all of the data you need.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Intellectual 530 points
    How do I navigate to the parsing and how do I modify it?
  • 0 in reply to Isaac Mears
    TI__Mastermind 29021 points

    The people counting TI design does not support point cloud data for a couple of reasons.  First, the sheer amount of point-cloud data generated by the IWR can be significant enough that the sensor (IWR+CC1352) will end up consuming significant bandwidth on the 15.4g network.  Other sensors in the same network can be significantly impacted.  Second, in our testing the UART driver has limitations that prevent it from meeting the real-time requirements to sample the data from the IWR device operating at a full frame rate (20 frames/sec).

    You can enable point-cloud data by modifying the PointCloudEn parameter in the CommandList array in mmwave_sensor.c.  Just be aware that further modifications/debugging will be needed.  You can configure the frame rate by modifying the frameCfg parameter in the CommandList.  Also in mmwave_sensor.c you will find the function readmmwave() which parses the data stream from the IWR.

    frameCfg 0 1 128 0 50 1 0

    >> The 50 refers to a frame period of 50ms (or 20 frames/sec)

  • 0 in reply to Gus Martinez
    Intellectual 530 points
    When you say further modifications are needed, are these purely limited to changing the frame rate and the readmmwave() function, or are there further changes that need to be made? If so, what are these modifications?
    Also, what would I change about the readmmwave() function so that it allows me to transmit the full point cloud?
  • 0 in reply to Isaac Mears
    TI__Mastermind 29021 points
    You can enable point cloud and reduce the frame rate. If the system is stable & performance meets your requirements, then no further modifications are needed. If the system is not stable (e.g. CC1352 MCU keeps going off into the weeds), then you can consider other changes like only sending point cloud data for every other frame. The readmmave() is where all the IWR data parsing happens, so I was merely pointing out where would be a place to start. What the ultimate changes will be, I do not know. That's where the debug comes in.
  • 0 in reply to Gus Martinez
    Intellectual 530 points
    I'm assumimg that I will need to change the readmmwave() function anyways so that the CC1352 doesn't cut off the data. Is there an example in the people counting lab documentation that I could use to model how I parse the data?
  • 0 in reply to Isaac Mears
    TI__Mastermind 28055 points

    Hi Isaac,

    Please see the Data Formats section in the People Counting User's guide.

    Regards,

    Justin