• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 829 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.

Linux/IWR1443BOOST: Number of frames commands over serial.

Rahul Sharma
Expert 2725 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443

Tool/software: Linux

Hi,

I made a python program to config and start the data flow from my IWR1443 to beaglebone over serial port.

Currently i am providing a sleep of 1 sec in receiver side, then i am getting the continous data of around 4095 bytes. The starting header/magic words are appearing 2-3 times within that 4095 bytes data.

Now i want to have the data frame by frame so that i can segregate the information at one time. For that i did a change in framecfg parameter in cfg list while sending to the mmwave. 

i did - 'frameCfg 0 1 16 1 100 1 0' that shows 1 frame to be send. Here i guess i am making a mistake because i am getting the exact 627 bytes of data starting properly with magic bytes and ended with few null bytes which is essentially for multiplication factor by 32. But after that no data is there yet my mmwave YELLOW LED is on and i have to reset the mmwave to use it again.

Any suggestion?

Thanks.

  • 0
    TI__Mastermind 30405 points
    Hi Rahul,

    How much total data are you expecting? You haven't provided the complete chirp configuration so it is not possible to figure out how much data will come out for one frame. Also, if you've configured only one frame, you will get data only for one frame and the system will stop. You'll need to call sensor stop and send the configuration again in order to re-configure the demo to get data for more RX frames.

    Regards
    -Nitin
  • 0 in reply to Nitin Sakhuja
    Expert 2725 points

    Hi Nitin,

    My chirp config is-

    dfeDataOutputMode 1

    channelCfg 15 7 0

    adcCfg 2 1

    adcbufCfg 0 1 0 1

    profileCfg 0 77 267 7 57.14 0 0 70 1 240 4884 0 0 30

    chirpCfg 0 0 0 0 0 0 0 1

    chirpCfg 1 1 0 0 0 0 0 4

    chirpCfg 2 2 0 0 0 0 0 2

    frameCfg 0 2 16 0 100 1 0

    guiMonitor 1 1 0 0 0 1

    cfarCfg 0 2 8 4 3 0 1280

    peakGrouping 1 1 1 1 229

    multiObjBeamForming 1 0.5

    calibDcRangeSig 0 -5 8 256

    Now can you please elaborate for sending only 1 frame? Here i changed the framecfg as 0 2 16 1 100 1 0 for getting only 1 frame and the sensor should stop sending data. Is this correct or something else needed to be corrected?

    My second doubt is in profielCfg the values after frequency parameters, are default as shown in sdk user guide-

    But in my above cfg parameter list(profileCfg 0 77 267 7 57.14 0 0 70 1 240 4884 0 0 30), values are found from mmwave demo gui app. Which are correct?

    Thanks.

  • 0 in reply to Rahul Sharma
    TI__Mastermind 30405 points

    Hi Rahul,

    As discussed earlier, if you set the number of frames to 1 in the frame_cfg command, the sensor will stop transmitting and receiving after one frame. You need to send the sensor_start command on the mmWave Demo CLI to re-enable the sensor with the same configuration. A value of 0 means infinite mumber of frames.

    On your second question, the values supplied in the mmWave Sensor Configuration commands (profileCfg, frameCfg, chirpCfg etc) depend upon the desired scene  parameters such as max range, max velocity, range resolution, velocity resolution, RCS of the object etc. The values given in the sdk user guide are as you said, the default values. The values you see in the configuration from mmwave demo gui, are based on the desired scene parameters selected in the GUI. Both values are correct. I would recommend you to go through the following app note to understand how the scene parameters are translated to chirp parameters:

    Programming Chirp Parameters in TI Radar Devices

    We also have the mmWave Sensing Estimator tool which takes the application level parameters (such as range, velocity etc) as input and generates the corresponding profile and frame configuration parameters which are then plugged into the above commands to configure the sensor for the desired scene configurations. 

    Thanks

    -Nitin