• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 519 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.

CCS/IWR1642BOOST: Cannot get all cfg files from CCS resource explorer to run on EVM

Ryen Elith
Intellectual 300 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642

Tool/software: Code Composer Studio

Hi,

I am having difficulties to successfully upload all the example cfg files provided on CCS resource explorer. More specifically, the sensor stops sending data when trying to upload any one of the following cfg files:

- RobotApplications

- Traffic monitor (mid range)

- Traffic monitor (long range)

- Elevator

I also tried loading the cfg files using the ros node mmWaveQuickConfig, which failed in the same cases. For further debugging, I removed the flushCfg command and added stopSensor before each CLI command and a startSensor after each command to check where the cfg. is causing problems. In the cases of RobotApplications and Traffic Monitoring, the sensor didn't respond with Done when loading the frameCfg statement. The remaining configuration files (Traffic monitor long range and Elevator) caused problems when trying to upload the guiMonitor and channelCfg CLI commands.

Is the upload procedure supposed to work when the token 3 of frameCfg is not a power of 2 as in some example cfg files? Are there any settings on the EVM side or computer side to make these examples load successfully? Also, are the relations between CLI tokens and constraints for these documented somewhere?

Thanks in advance for your help.

  • 0
    TI__Mastermind 30405 points

    Hi Ryen,

    Are you trying to test the above chirp config files with the Out of Box Demo? As mentioned in the Testing and Results sections, these chirp configurations have been tested to correctly configure the sensor front-end for the provided use case without generating any mmWaveLink API errors.However the OOB demo digital processing chain may need to be modified for it to be able to process the resulting output from the front-end.

    The Traffic Monitoring use cases are based on TI's mmWave Traffic Monitoring Object Detection and Tracking Reference Design which includes the corresponding application (including source code) which you can load on the IWR1642 EVM and test the chirp configuration and other advanced functionality including clustering and tracking. As mentioned in the Introduction section of the Traffic Monitoring Radar chirp designs, please refer to the design webpage for more details.

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Intellectual 300 points

    Hi Nitin,

    Thanks for your reply, it was helpful.

    I would like to continue using the ti_mmWave_rospkg, which has been working well. If I understood correctly, the rospackage works for the out-of-the box demo only, correct? Is it possible to configure the EVM to get longer range (such as in the traffic monitoring configuration) using the out-of-the-box demo app?

    Thanks for your help.

    Ryen

  • 0 in reply to Ryen Elith
    TI__Mastermind 30405 points

    Hi Ryen,

    You're right, the ROS visualizer package works only with the out of the box demo. You can change the chirp profile in the ROS point cloud visualizer demo as mentioned on page 11 of the corresponding user guide (section: Reconfiguring the chirp profile) and shown in the snapshot below:

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points
    Hi Ryen,

    Can you please mark this thread answered if your query was resolved? Thanks.

    Regards
    -Nitin