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/AWR1443BOOST: JSON to cfg convertion.

Part Number: AWR1443BOOST
Other Parts Discussed in Thread: TIDEP-0091

Tool/software: Linux

Hello,

From "mmWave Demo Visualizer" a .cfg file can be saved and used in the ROS package. But from "mmWave Sensing Estimator" a .json is saved. How can I use it in ROS package? The following link "https://e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/640270?IWR1642BOOST-JSON-to-cfg-convertion-" says "ProfileCfg and FrameCfg" can be copied to use, but is this two parameters enough for a .cfg file?

Best Regards,

Tao Wang

Automodality Inc.

  • Hi Tao,

    Those two are going to be the most configured part of your chirp configuration. You can comfortably keep your other parameters the same if you are using hte same ProfileCfg and FrameCfg.

    One thing to note is that the visualizer provides an out of box experience and is not at all indicative of the full capabilities of the sensor. There are certain configurations that will not work for the visualizer but are more than appropriate for the sensor.


    Cheers,
    Akash
  • Hello Akash,

    Thanks for your answer. So I can just change the two line of "ProfileCfg and FrameCfg" to get the configuration?

    I see about the visualizer, and this is why I would like to know to use the configuration from the estimator.

    I have another concern is if it is possible to do the configuration in the code, i.e., is there API functions in the SDK do this configuration job?

    Best Regards,
    Tao Wang
  • Hi Tao,

    Yes the "ProfileCfg and FrameCfg" are all you really need to change.

    Also, yes it is possible to code the configuration although this isn't recommended when it comes to evaluation. There is an example of this in TIDEP-0091 in the demo.c file.


    Cheers,
    Akash