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.

AWR1843BOOST: ERROR: Ramp duration is not enough to capture

Part Number: AWR1843BOOST
Other Parts Discussed in Thread: DCA1000EVM, , IWR1843, IWR6843, AWR1843

Tool/software:

Issue Report: Ramp duration is not enough to capture 128 samples with 200ksps

 

Product: DCA1000EVM / AWR18xx  

Description of the Issue:

Subject: ADC Sampling Rate Configuration Issue in mmWave Studio

 

Hello,

 

I am currently working with mmWave Studio to configure parameters for long-range operation (70 m) using my mmWave sensor. I have configured the chirp and other related parameters as per the guidelines, specifically setting the ADC sampling rate to 11.414 ksps to accommodate the desired range.

 

However, I am encountering an issue where the ADC sampling rate automatically resets to 200 ksps, despite my configuration. This leads to an error message stating:

 

"Ramp duration is not enough to capture 128 samples with 200ksps."

 

This discrepancy prevents me from achieving the intended configuration for long-range detection. I have checked the configuration settings multiple times and confirmed they align with the parameters recommended in the TI estimator.

 

Could you please provide assistance or guidance on how to resolve this issue? Any insights into why the ADC sampling rate resets or how to maintain my desired settings would be greatly appreciated.

 

please find the screenshots and the output window log for more understanding of the problem

Thank you for your support!

 

[19:44:02] [RadarAPI]: Opening Gpio Control Port()
[19:44:02] [RadarAPI]: Status: Passed
[19:44:02] [RadarAPI]: ar1.Disconnect()
[19:44:02] [RadarAPI]: ar1.Calling_ATE_DisconnectTarget()
[19:44:02] [RadarAPI]: ar1.Calling_IsConnected()
[19:44:02] [RadarAPI]: ar1.SaveSettings('C:\Users\KarthikJami(ELD-IND)\AppData\Roaming\RSTD\ar1gui.ini')
[19:44:02] [RadarAPI]: Opening Board Control Port()
[19:44:02] [RadarAPI]: Status: Passed
[19:44:03] [RadarAPI]: ar1.FullReset()
[19:44:03] [RadarAPI]: Status: Passed
[19:44:04] [RadarAPI]: Closing Board Control Port()
[19:44:04] [RadarAPI]: Status: Passed
[19:44:04] [RadarAPI]: Closing Gpio Control Port()
[19:44:04] [RadarAPI]: Status: Passed
[19:44:04] [RadarAPI]: ar1.SOPControl(2)
[19:44:04] [RadarAPI]: Status: Passed
[19:44:07] [RadarAPI]: ar1.Connect(34,921600,1000)
[19:44:10] [RadarAPI]: Warning: Connected with baudrate 115200
[19:44:11] [RadarAPI]: Warning: Disconnected existing BaudRate
[19:44:11] [RadarAPI]: Warning: Trying to connect with baudrate 921600
[19:44:12] [RadarAPI]: ar1.Calling_IsConnected()
[19:44:14] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[19:44:14] [RadarAPI]: Status: Passed
[19:44:14] [RadarAPI]: ar1.SelectChipVersion("XWR1843")
[19:44:14] [RadarAPI]: Status: Passed
[19:44:14] Device Status : XWR1843/ASIL-B/SOP:2/ES:2
[19:44:14] [RadarAPI]: ar1.SaveSettings('C:\Users\KarthikJami(ELD-IND)\AppData\Roaming\RSTD\ar1gui.ini')
[19:44:16] [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\radarss\\xwr18xx_radarss.bin")
[19:44:17] [RadarAPI]: Downloading BSS Patch RPRC Binary..
[19:44:18] [RadarAPI]: ar1.GetBSSFwVersion()
[19:44:18] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[19:44:19] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[19:44:19] [RadarAPI]: BSSPatchFwVersion:(01.02.05.02 (30/04/19))
[19:44:20] [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\masterss\\xwr18xx_masterss.bin")
[19:44:21] [RadarAPI]: Downloading MSS RPRC Binary..
[19:44:23] [RadarAPI]: ar1.GetMSSFwVersion()
[19:44:23] [RadarAPI]: MSSFwVersion:(01.02.05.02 (16/07/19))
[19:44:24] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
[19:44:24] MSS power up done async event received!
[19:44:24] [RadarAPI]: Status: Passed
[19:44:27] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[19:44:27] [RadarAPI]: Status: Passed
[19:44:27] [RadarAPI]: ar1.SelectChipVersion("XWR1843")
[19:44:27] [RadarAPI]: Status: Passed
[19:44:27] Device Status : XWR1843/ASIL-B/SOP:2/ES:2
[19:44:27] [RadarAPI]: ar1.RfEnable()
[19:44:27] BSS power up done async event received!
[19:44:27] [RadarAPI]: Status: Passed
[19:44:27] [RadarAPI]: ar1.GetMSSFwVersion()
[19:44:27] [RadarAPI]: MSSFwVersion:(01.02.05.02 (16/07/19))
[19:44:28] [RadarAPI]: ar1.GetBSSFwVersion()
[19:44:28] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[19:44:29] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[19:44:29] [RadarAPI]: BSSPatchFwVersion:(01.02.05.02 (30/04/19))
[19:44:38] [RadarAPI]: ar1.ChanNAdcConfig(1, 1, 0, 1, 1, 1, 1, 2, 1, 0)
[19:44:38] [RadarAPI]: Status: Passed
[19:44:40] [RadarAPI]: ar1.LPModConfig(0, 0)
[19:44:40] [RadarAPI]: Status: Passed
[19:44:41] [RadarAPI]: ar1.RfInit()
[19:44:41] RF Init async event received!
[19:44:41] [RadarAPI]: Time stamp, Temperture: 13897,39; APLL Status, Update: 1, 0; SynthVCO1 Status, Update: 1, 1; SynthVCO2 Status, Update: 1, 1; LODist Status, Update: 1, 1; RxADCDC Status, Update: 1, 1; HPFcutoff Status, Update: 1, 1; LPFcutoff Status, Update: 1, 1; PeakDetector Status, Update: 1, 1; TxPower Status, Update: 1, 1; RxGain Status, Update: 1, 1; TxPhase Status, Update: 1, 1; RxIQMM Status, Update: 1, 1;
[19:44:41] [RadarAPI]: Status: Passed
[19:44:45] [RadarAPI]: ar1.DataPathConfig(513, 1216644097, 0)
[19:44:45] [RadarAPI]: Status: Passed
[19:44:47] [RadarAPI]: ar1.LvdsClkConfig(1, 1)
[19:44:47] [RadarAPI]: Status: Passed
[19:44:48] [RadarAPI]: ar1.LVDSLaneConfig(0, 1, 1, 0, 0, 1, 0, 0)
[19:44:48] [RadarAPI]: Status: Passed

  • Hello,

    Putting your config into the SensingEstimator's advanced tab show several issues, and what I would use to validate configurations. I would mostly avoid using the basic tab for low level evaluation like this unless you are familiar with it. We also recommend sampling rate to be a minimum of 2000 ks/s.

    Best Regards,

    Pedrhom

  • thank you for your comment

    https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ver/2.4.0/

    we have used this TI Estimater  to caluclate and configure chirp parameters in mmwave studio AWR1843BOOST

    as you said the values seens to be incorrectly caluclated or computed by the Estimater could you please help us computing proper chirp parameters for a long range (70 meter) . 

    if you can provide some ways to caluclate or direcly providing chirp paramteres for long range also be appreciated.....

  • Hello,

    For long ranges, I would start with one of the Long Range People Detection configurations:
    C:\ti\<RADAR_TOOLBOX>\source\ti\examples\Long_Range_People_Detection\chirp_configs.

    There you will find 50m and 100m example configurations. That said this is an Industrial project correct? Is there a specific reason that the AWR1843 is being used as opposed to IWR6843 or IWR1843?

    Best Regards,

    Pedrhom