• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 366 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.

IWR1443: startFreq value in the profileCfg

MCV
Intellectual 1300 points
Part Number: IWR1443
Other Parts Discussed in Thread: TIDEP-0091

I read the IWR1443 datasheet again, and it says that it's possible to set the measurement between 76-77GHz.

Then I read the mmwave_sdk_user_guide.pdf and set the startFreq value in the profileCfg, but I didn't see any significant change in the frequency.

What value do I need to change in order to reduce the frequency?

  • 0
    TI__Genius 10730 points

    Hi Matt,

    Just to confirm, you set the startFreq value to 76, correct?

    Thanks,

    Angie

  • 0 in reply to Angie Mitchell
    Prodigy 80 points

    Hi Angie, Hi Matt,

    We used a modified version of TIDEP-0091 (level sense demo).  The original software was a bit inaccurate, so it needed to be modified.

    We only changed the values of the following two variables in order to change the frequency:

      gMmwMCB.openCfg.freqLimitLow  = LSCFG_CAL_FREQ_LOW; //We changed its value to 760 from 770;

      gMmwMCB.openCfg.freqLimitHigh = LSCFG_CAL_FREQ_HIGH; //We changed its value to 770 from 810;

    Modification of the variable didn't result in modification of the frequency.

    Best regards,
    Richard

  • 0 in reply to Richard Lazar
    TI__Mastermind 23177 points

    Hello Richard,

    Just to confirm you are using the 14xx high accuracy lab from the Radar Toolbox correct? What does the configuration file sent look like? Is the frequency setup there potentially overwriting what is hardcoded in the source? Also by default it seems the parameters end with a "U" and just to make everything be consistent and the same can you confirm that the value is setup like this as well?

    Best Regards,

    Pedrhom

  • +1 in reply to Pedrhom Nafisi
    TI__Intellectual 1300 points

    Just to close it if someone visits this thread:

    initially the value of FreqSlopeUsec was a const value, and not calculated with a formula 

    Having it calculated, the software works fine.

    Thanks for the help again.