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

IWR1443BOOST: How do i load a config file into my IWR1443 device

IWR6843AOP: custom config errors

Ryan Sarver
Intellectual 540 points
Part Number: IWR6843AOP

Hi,

I’m trying to upload a custom .cfg file using ‘mmWave Sensing Estimator’ tool and followed the procedure outlined here:

https://e2e.ti.com/support/sensors/f/1023/p/640604/2363699#2363699

So basically I copied the newly generated values into profileCfg and frameCfg in the original default working .cfg.

Trying to run the ROS point cloud visualizer with the new .cfg resulted in an error, however. Through trial and error of replacing the values one at a time in the working .cfg file, it was determined that the following 4 parameters result in an error:

ADC valid start time = 5.3

Ramp end time = 29.7

# of samples per chirp = 277

Sampling rate = 11837

I.e. changing any one of them from the default to the new value listed above creates an error (specifically, "Command failed (mmWave sensor did not respond with 'Done')")

Could I please have some details on why these parameters are causing issues? My configuration passes in the Sensing Estimator tool so there seems to be some disparity between that tool and what actually works for a .cfg.

If I replace these 4 parameters with the ones from the default .cfg file, then it works.

  • 0
    TI__Guru 50240 points

    Hi Ryan

    For this query please refer to this thread.

    Regards,

    AG

  • 0 in reply to Akash Gondalia
    Intellectual 540 points

    Hi Akash,

    So basically to summarize (please correct me if I'm wrong), the Sensing Estimator tool can generate any set of parameters that are within the realm of theoretical possibility for the radar. However, the SDK demos reduce the scope of possibility and that's where the errors are coming from.

    Am I correct in understanding then that there's currently no tool available for generating configs that operate within the SDK subspace?

    And if not, is there any resource you can direct me to for adapting a config generated by the Sensing Estimator so that it will work with the SDK demo, that doesn't involve doing a deep dive into the SDK software? For example, in the config I generated, it seems that the problematic parameters are all linked to the ADC (with exception perhaps to 'ramp end time', not sure about that one). So would you have any recommendations for how to adapt those ADC parameters to work with the SDK demo and still be more or less aligned with the other parameters of my custom config?

    thanks,

    Ryan

  • 0 in reply to Ryan Sarver
    Intellectual 540 points

    Seems like the mmWave Demo Visualizer tool is the one to use for generating custom .cfg files that work within the SDK subspace. The interface is different and the parameters don't seem to quite match up with the Sensing Estimator, but it generates working .cfg files.