• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 5392 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.

how to configure three different profiles

Slithice
Intellectual 295 points

Hi ,engineers

     I want to inquire a question.I will configure three different  mmwaves and the three mmwaves runs in loop.

Is it right if I set the profiles like this?

profileCfg 0 ....

profileCfg 1 ...

profileCfg 2 ...

chirpCfg (chirpStartIdx--chirpEndIdx)  0 127 0(profile 0) ....

chirpCfg(chirpStartIdx--chirpEndIdx)   0 127 1(profile 1) ....

chirpCfg(chirpStartIdx--chirpEndIdx)    0 127 2(profile 2) ....

FrameCfg (chirpStartIdx--chirpEndIdx)   0 127 numLoops = 1,numFrames = 0,numAdcSamples = 126,framePeriodicity = 60,

  • 0
    TI__Mastermind 22155 points

    Hello ,

    Yes you can set the profiles and chirps as you have mentioned in your query.

    For more details on the configuration (.cfg) file refer to "Sec 3.5 Configuration (.cfg) File Format" in the mmwave_sdk_user_guide.pdf

    Thanks,

    Raghu

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------

  • 0 in reply to Raghunandan Kamath
    Intellectual 295 points
    yes.I read the mmwave_sdk_user_guide , but it does not describe how to set kinds of profiles.And I want to ask whether it is right, like this:
    Chirp cfg#0: chirp start index = 0 ,chirp end index = 127,profile identifier = 0
    Chirp cfg#1: chirp start index = 128 ,chirp end index = 255 ,profile identifier = 1
    Chirp cfg#2: chirp start index = 256 ,chirp end index = 383 ,profile identifier = 2
    FrameCfg (chirpStartIdx--chirpEndIdx) 0 383 , numLoops = 1,numFrames = 0,numAdcSamples = 126,framePeriodicity = 60,
    I try many times ,but can not suceed.
  • 0 in reply to Slithice
    TI__Mastermind 22155 points
    Hello,

    Sorry for the confusion.

    The current SDK code will only support single profile configuration.

    However there is no limitation from the configuring the multiple profiles to the device.

    The current issue you will be facing is due to the limitation in the DSS code that requires reconfiguration of the EDMA etc for processing chirps with different profiles.

    Regards,
    Raghu
  • 0 in reply to Raghunandan Kamath
    Intellectual 295 points
    Chirp cfg#0: chirp start index = 0 ,chirp end index = 127,profile identifier = 0
    Chirp cfg#1: chirp start index = 128 ,chirp end index = 255 ,profile identifier = 1
    Chirp cfg#2: chirp start index = 256 ,chirp end index = 383 ,profile identifier = 2
    FrameCfg (chirpStartIdx--chirpEndIdx) 0 383 , numLoops = 1,numFrames = 0,numAdcSamples = 126,framePeriodicity = 60,
    It is wrong?It is diffferent from that I mention the configuration first tme.
  • 0 in reply to Raghunandan Kamath
    Intellectual 295 points
    can you give me an unambiguous answer,which method is correct?
  • 0 in reply to Slithice
    TI__Guru 69960 points

    Hello Slithice,

    In case you want to enable multiple profiles with different radar properties (Freq, slope, idle & ramp time etc.) in mmwave_sdk demo then DSS will throw an error. As in when DSP will get chirp data with the different property it needs to do the different version of processing on the go which is currently not supported by SDK.

    Having said that if you want to add multi profile feature in mmw demo then you need to take care of DSP processing logic on different profile version of chirp data.

    Further more while defining radar configuration parameters with multiple profiles you need to be cautious about validation of frame/chirp/profile parameters.

    Here is the app note which will help you with this.

    Now with respect to above-mentioned configuration

    Calculate total time taken by all  the chirps (ramp end time + chirp idle time) encapsulated in a frame, framePeriodicity = Total_chirp_time + frame_idle_time.

    Here Frame_idle_time you need to cool off the device after a sequence of chirping and do the DSP processing (e.g. 2-D/3-D FFT ).

    You may be getting an error with this configuration because total chirp time is going beyond 60 mSec which is given as framePeriodicity, please re-calculate and try with higher value.

    It will help us to understand your problem if you can share your uasecase of  this experiment (multi profile) 

    Regards,

    Jitendra Gupta

  • 0 in reply to Jitendra Gupta
    Intellectual 295 points
    one：
    Chirp cfg#0: chirp start index = 0 ,chirp end index = 127,profile identifier = 0
    Chirp cfg#1: chirp start index = 128 ,chirp end index = 255 ,profile identifier = 1
    Chirp cfg#2: chirp start index = 256 ,chirp end index = 383 ,profile identifier = 2

    two:
    ChirpCfg (chirpStartIdx--chirpEndIdx) chirp start index = 0，chirp end index = 127 ，profile identifier =0
    ChirpCfg(chirpStartIdx--chirpEndIdx) chirp start index = 0，chirp end index = 127 ，profile identifier =1
    ChirpCfg(chirpStartIdx--chirpEndIdx) chirp start index = 0，chirp end index = 127 ，profile identifier =2

    I query that the chirp start index and the chirp end index have any effect on setting the profile, just like the two exmples.And which confuration is correct?
  • 0 in reply to Slithice
    TI__Guru 69960 points
    Configuration #1 is correct where [chirp 0-383] are assigned to profile [0-2].

    Whereas in Config#2 chirpCfg [chirp index 0-127] is getting overwritten by next two configs and finally chirps [0-127] are assigned to profile [2].
  • 0 in reply to Jitendra Gupta
    Intellectual 295 points
    Thank you for giving me a hand ! And I want to ask a question.In order to set the three profiles and gain three different mmWave, is it necessary for me to use the rlSetAdvFrameConfig API to help enable this kind of configuration?
  • 0 in reply to Slithice
    TI__Guru 69960 points
    With above mentioned configuration you can use legacy frameConfig API whereas advFrameConfig allows for large flexibility to have multiple chirp configurations in a single frame.

    For your requirement you can either frame config API.

    We would recommend you to go over the Programming Radar document (link is given in last post) to gain the knwoledge about these APIs.


    Regards,
    Jitendra Gupta
  • 0 in reply to Jitendra Gupta
    Intellectual 295 points
    Thank you! I have resolved my problem ,thank you very much,my dear engineer!