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.

AWR1843AOP: AWR1843AOP

Part Number: AWR1843AOP
Other Parts Discussed in Thread: AWR1843BOOST, AWR1843, AWR2944

Hello,

We are currently working on AWR1843AOP for one of the ADAS application. We have a desired detection range of 100m and above and by changing the initial  configuration parameters, we have been able to achieve max range of 40m for a two-wheeler bike. We also used the TI sensing estimator to find out the desired configuration to achieve 100 m range and found out following configuration that is desirable for  more than 90m. However, when we use the configuration, we are unable to receive the detections. Can you check on it once?

Following are the details of chirp and frame configurations

% with mmWaveBasic SDK without calibrating digital processing chain.
% ===============================================================================
profileCfg 0 77 2 5 21.26 0 0 9.75 1 62 4064 0 0 30
channelCfg 15 7 0
adcbufCfg -1 0 1 1 1
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2 334 0 40 1 0

We had chosen AWR1843 AOP to focus more on the SW design rather than the RF design due to the limited competence on the RF design, If if AWR1843AOP is limited to a range detection <100m, then we'll have to go  with other TI radar solutions. In that case, can you suggest the alternatives to AWR1843AOP in the frequency band of 77-81GHz? Also, Is there a reference document  on designing  our solution AWR1843BOOST with patch antenna just like the one available on EVM board?

  • Hi,

    Let me check on this on my bench and get back to you with an update on this.

    Thanks,

    Pradipta.

  • Hi Abhisha,

    Thank you for reaching out on e2e!

    • When you say you are not getting any points, can you confirm if the device is still active or if it has thrown some assertions for potential invalid cases?
    • Has this configuration been generated by you or the sensing estimator?
    • Would it be possible for you to send the full cfg file that you have sent to the device so that I can reproduce the "no detections" case on my end?
    • In the case of you seeing detections till 40m, have you played around with other point cloud filtering algorithms such as CFAR and peak grouping? I would strongly recommend you do so, if your chirp design supports that max range.
    • By detections are you referring to tracked points or from the list of objects?

    Please find my response to your further questions below:

    1. There are a few solutions from TI that can meet your usecase such as the AW1843 and AWR2944 that can be used to obtain a range much greater than 100m. 
    2. There is no guide or reference document for antenna design available yet. You can alternatively also refer to some third-party services from the link below for antenna design services.
      https://www.ti.com/tool/MMWAVE-3P-SEARCH

    Regards,

    Kaushik

  • Hi.

    I had generated the configuration from the TI sensing estimator.  By detections, I mean the raw detections(without clustering/tracking). When I use the configuration file, I am unable to get even the raw detections. Please find the configuraton attached below:

    % ***************************************************************
    % Created for SDK ver:03.06
    % Created using SENSING ESTIMATOR BASED OFF OOB DEMO VISUALIZER
    % Frequency:77
    % Platform:xWR18xx
    % Scene Classifier:best_range_res
    % Azimuth Resolution(deg):15 + Elevation
    % Range Resolution(m):0.044
    % Maximum unambiguous Range(m):9.02
    % Maximum Radial Velocity(m/s):1
    % Radial velocity resolution(m/s):0.13
    % Frame Duration(msec):100
    % RF calibration data:None
    % Range Detection Threshold (dB):15
    % Doppler Detection Threshold (dB):15
    % Range Peak Grouping:enabled
    % Doppler Peak Grouping:enabled
    % Static clutter removal:disabled
    % Angle of Arrival FoV: Full FoV
    % Range FoV: Full FoV
    % Doppler FoV: Full FoV
    % ***************************************************************
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 7 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 77 2 5 21.26 0 0 9.75 1 62 4064 0 0 30
    channelCfg 15 7 0
    adcbufCfg -1 0 1 1 1
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    chirpCfg 2 2 0 0 0 0 0 4
    frameCfg 0 2 334 0 40 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 0 0 1
    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 0 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

  • Hi Abhisha,

    Thank you for sharing your cfg. I will review the same and reproduce your issue on my end and get back to you by early next week. Can you run the same config with the demo debug binaries on CCS (load the .xer4f and .xe64)? Need to make sure the demo is taking in the cfg without any issues.

    Regards,

    Kaushik