• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 120 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1843BOOST: Configuration file has issues in OOD demo

Xi Zhang1
Intellectual 265 points
Part Number: IWR1843BOOST

Hi TI team:

I am tring to set that range resolution equals to 0.04m and frame period equals to 10ms. However the configuration was not sucessful to set the out of box demo. It returns error code as -1.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 77 10 7 75.8 0 0 71.5 1 256 6300 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 500 9 1 0
lowPower 0 0
guiMonitor -1 0 1 1 0 0 0
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 1 0.5
clutterRemoval -1 0
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
lvdsStreamCfg -1 0 1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
CQRxSatMonitor 0 3 5 121 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 8.92
cfarFovCfg -1 1 -1 1.00
calibData 0 0 0
sensorStart

Warm Regards,

Xi

  • 0
    TI__Expert 7510 points

    Xi:

    Please go to the following sensing estimator to generate your .cfg file then try to see if it works in the OOB. Note that it may not. The OOB demo visualizer should be used to generate the .cfg to guaranteed that it works with the demo. The sensing estimator is a tool which generates configuration files which will work with the constraints of the radar device. This does not apply to the visualizer which is more restrictive. You may need to your own visualizer or modify the existing one if you need to view the data from a configuration file that the demo does not accept.

    Sensing Estimator: https://dev.ti.com/gallery/view/1792614/mmWaveSensingEstimator/ver/1.3.0/

    Also please go to the following default chirps and see if one of these would fit your application:

    <MMWAVE_INDUSTRIAL_TOOLBOX_INSTALL_PATH>\chirps

    Best regards,

    Connor Desmond

  • 0 in reply to Connor Desmond
    Intellectual 265 points

    Hi Connor:

    First of all, I have used these tools but the configuration file generated by them is not what I want. And I have check all the parameter in the .cfg file with the SDK user guide so I know what the setting means in the .cfg file. The sensing estimator can only generate json file, I am wondering how to use json format file in the OOB demo or  demo visualizer. This one I uploaded is according to the generated parameter by the sensing estimator but I manaully set them in the .cfg file.

    I am actually seeking help for checking my .cfg file.

    And also there is no desired the chirp file in toolbox that you menthioned.

    I think my specification is clear, I want a configuration file which has 4cm range resolution and 10ms frame period at same time.

    The demo visulizer can only up to 30 frames in 1 second.

    And I actually capture the raw data from the OOB demo, So I am not care about the real time visualization.

     

    Warm regards,

    Xi

  • 0 in reply to Xi Zhang1
    TI__Expert 7510 points

    Xi:

    1. The chirps I referenced above are located at the following link in the most recent Industrial Toolbox release:

    https://dev.ti.com/tirex/explore/node?node=ALYHkY2xyhq2-EgWIUuw-Q__VLyFKFf__LATEST

    2. Along side using the sensing estimator please watch the following training video:

    https://training.ti.com/mmwave-sensing-estimator-overview

    3. To be able to take what the Sensing Estimator returns to .cfg files you will need to do that translation manually, or come up with a script that that takes in a .json file and creates a .cfg file.

    4. The sensing estimator is used to inform the user of what is possible and what is not possible for a given device. As is is referenced in the video linked above this just applies to configuration of the analog front end. For all other configurations please reference the SDK User's Guide. The sensing estimator is a tool which lets you know if you problem constraints are possible. In your case 4cm range resolution is right on the edge of what is possible with a 4GHz bandwidth. A 10ms frame time would be 100 frame/s which can might be possible, but you will have to limit number of chirps as well as samples per chirp, so that for a given frame there is enough time to send the point cloud over UART which has trade offs as well. There are a variety of trade offs that take place in configuring this device and I would highly suggest becoming familiar with those trade offs.

    5. Please refer to the following white paper that pertains to configuring out devices.

    www.ti.com/.../swra553a.pdf

    6. This forums role is to provide you with the necessary resources so that you can accomplish your goals and answer specific questions that come up during that process. The role is not to provide any user with a specialized configuration file. That is your responsibility to create. 

    Best regards,

    Connor Desmond

  • 0 in reply to Connor Desmond
    Intellectual 265 points

    Hi Connor,

    Thanks for your help.

    The doc is what I wanted.

    Finally, I fix the problem and it turns allright.

    Warm regards,

    Xi

  • +1 in reply to Xi Zhang1
    TI__Expert 7510 points

    Xi:

    I am glad that your problem is fixed. If you could please resolve the issue on your end that would be greatly appreciated.

    Best regards,

    Connor Desmond