• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 692 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:

CCS/IWR1642BOOST: open configuration failed IWR 1642Boost

CCS/IWR1642BOOST: Configuration Error in Vital Signs Demo

user5812271
Intellectual 370 points
Part Number: IWR1642BOOST

Tool/software: Code Composer Studio

Hello,

I have slightly modified the vital signs configuration from its default and I'm getting errors when I try to run it. I have successfully used this configuration in mmWave Studio (when doing a raw data capture), but for some reason it does not work with the Vital Signs Demo. I have attached screen shots of the terminal window from the GUI, the CCS console error message, the mmWave Studio configuration, and the configuration file that I am sending to the Vital Signs Demo. For the configuration file I only changed values in the "profileCfg" and "frameCfg" lines. I believe the numbers from mmWave Studio all match up to the correct field in the configuration file so I'm not sure what the error is.

Thanks,

Josh 

  • 0
    TI__Guru*** 147964 points
    Hi,

    The sampling Frequency is too high.

    Can you please try 6.4MHz instead of 11MHz?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Intellectual 370 points
    Hi Cesar,

    I tried this and got the same error messages.

    Josh
  • 0 in reply to user5812271
    TI__Mastermind 24955 points
    Josh,

    It appears that you have decreased the frame periodicity from 50 ms to 10 ms. Please keep in mind that the Vital Signs Processing chain does need enough inter frame processing time to complete the heart and breath rate calculations.

    You also have increased the number of chirps from 2 to 128. Was there a reason for increasing the number of chirps? In the Developer's Guide, it states that only the first chirp in the frame is needed for processing. Is there a reason you have so many extra chirps when this not necessary.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 370 points

    Hi Kyle,

    I changed these parameters to get a better duty cycle percentage. The duty cycle is 81.9% with 128 chirps and 10 ms frame periodicity vs. 0.3% with 2 chirps and 50 ms frame periodicity. The higher duty cycle was giving me better results with raw data processing (especially when I averaged FFT outputs of the 128 chirps for each frame), so I thought I'd try out these parameters on the vital signs demo. That being said, even when I change these parameters back to their original values (as well as the sampling rate) I get the same error messages as before, which makes me think there's an issue with changing the number of ADC samples from 200 to 512. I'm not sure I understand why this is an issue--is the original value of 200 ADC samples hardcoded somewhere in one of the C files? It just seems like there is very little customizability from the radar front end.

    Josh