SWRU587A November   2021  – March 2023 AWR2944

 

  1.   Trademarks
  2. 1Setup Instructions
    1. 1.1 Browser Setup (First Time Only)
    2. 1.2 mmWave Device Setup
    3. 1.3 Serial Port Setup
  3. 2CONFIGURE Tab
    1. 2.1  Platform
    2. 2.2  SDK Version
    3. 2.3  Antenna Config (Azimuth Resolution - Degrees)
    4. 2.4  Processing Chain
    5. 2.5  Desirable Configuration
    6. 2.6  Frequency Band (GHz)
    7. 2.7  Scene Selection – Best Range Resolution
      1. 2.7.1 Frame Rate (fps)
      2. 2.7.2 Range Resolution (m)
      3. 2.7.3 Maximum Unambiguous Range (m)
      4. 2.7.4 Maximum Radial Velocity (m/s)
      5. 2.7.5 Radial Velocity Resolution (m/s)
    8. 2.8  Scene Selection – Best Velocity Resolution
      1. 2.8.1 Frame Rate (fps)
      2. 2.8.2 Radial Velocity Resolution (m/s)
      3. 2.8.3 Maximum Radial Velocity (m/s)
      4. 2.8.4 Range Resolution (m)
      5. 2.8.5 Maximum Unambiguous Range (m)
    9. 2.9  Scene Selection – Best Range
      1. 2.9.1 Frame Rate (fps)
      2. 2.9.2 Maximum Unambiguous Range (m)
      3. 2.9.3 Range Resolution (m)
      4. 2.9.4 Maximum Radial Velocity (m/s)
    10. 2.10 Plot Selection
      1. 2.10.1 Scatter Plot
      2. 2.10.2 Range Profile
      3. 2.10.3 Noise Profile
      4. 2.10.4 Range Azimuth Heat Map
      5. 2.10.5 Range Doppler Heat Map
      6. 2.10.6 Statistics
    11. 2.11 User Selected Configuration
      1. 2.11.1 Send Configuration to mmWave Device
      2. 2.11.2 Saving Configuration to PC
      3. 2.11.3 Reset Selection
  4. 3PLOTS Tab
    1. 3.1  X-Y Scatter Plot
    2. 3.2  Doppler Range Plot
    3. 3.3  Range Profile
    4. 3.4  CPU Load
    5. 3.5  Range-Doppler Heatmap
    6. 3.6  Range-Azimuth Heatmap
    7. 3.7  3-D Scatter Plot
    8. 3.8  Display Parameters
      1. 3.8.1 Profiling Parameters
      2. 3.8.2 Scene Parameters
      3. 3.8.3 Chirp/Frame Parameters
    9. 3.9  Real-Time Tuning
      1. 3.9.1 Group Peaks From Same Object
      2. 3.9.2 Static Clutter Removal
      3. 3.9.3 Range Detection Threshold (0 to 100 dB)
      4. 3.9.4 Doppler Detection Threshold (0 to 100 dB)
    10. 3.10 Advanced Commands
      1. 3.10.1 Special Note About Range and Angle Bias Compensation Configuration
    11. 3.11 Plot Settings
  5. 4Advanced Options
    1. 4.1 Load Configuration From PC
    2. 4.2 Getting the Version
    3. 4.3 RCS
      1. 4.3.1 Desired Radar Cross Section (sq. m)
      2. 4.3.2 Maximum Range for Desired RCS (m)
      3. 4.3.3 RCS at Maximum Unambiguous Range (sq. m)
    4. 4.4 Concurrent Recording of Processed Stream From mmWave Device
  6. 5Troubleshooting
    1. 5.1 Console Message: Errors Returned by Device
    2. 5.2 Serial Port Status Message: Not Switching to Hardware Connected or Both Ports Are Not Showing Up
    3. 5.3 Console Message: sensorStart Message Not Sent to Host
    4. 5.4 Warning for Plots and Frame Rate
    5. 5.5 Configuration Successful, but Plots Not Updating
  7. 6Customizing the mmWave Demo Visualizer
  8.   Revision History

5.3 Console Message: sensorStart Message Not Sent to Host

If the user sees some messages appear in the console messages, but not all of them and the last message is not sensorStart, then the following common errors could be the root cause:

  • Commands sent earlier generated an error. User must correct the source of error (fix the user-generated configuration file, move the sliders, and so on) and try again.
  • Commands sent earlier caused the software running on the device to crash and an assert or exception message is displayed. Users can connect the Code Composer Studio™ (CCS) debugger to the target device to debug this situation further. In the absence of CCS, reboot the device and start again. If the device still does not work for a given config, check the config against the mmWave MCUPLUS SDK User's Guide.
    • One reason could be that the number of plots selected caused the shipment of the output data to exceed one frame duration.
  • Sometimes the UART on the target device does not receive all the characters or messages (for example, the PC sends configuration data over the UART faster than the device can process). Just repeat the action (Send Config.. or Load Config..) and try again.