• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 224 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.

AWR1843BOOST: AWR1843BOOST: Porting USRR chirp commands of MRR demo to CLI commands for OOB demo

Rehman
Intellectual 265 points
Part Number: AWR1843BOOST

Tool/software:

Hai,

Actually i need to modify the chirp configuration of AWR1843OOB demo as it's only 8m range.

So i went through MRR demo and read SDK userguide and tried to port USRR50m chirp config to CLI format as given below.

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 1
profileCfg 0 77.01 5 3 44 0 0 37.5 1 512 12500 0 0 30
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 32 0 60 1 0
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 3 0 15.0 0
cfarCfg -1 1 0 4 2 3 1 15.0 0
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5 8 512
clutterRemoval -1 0
compRangeBiasAndRxChanPhase 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. 0.2
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0.25 45
cfarFovCfg -1 1 -6.62 6.62
extendedMaxVelocity -1 0
CQRxSatMonitor 0 3 10 121 0
CQSigImgMonitor 0 127 8
analogMonitor 0 0
lvdsStreamCfg -1 0 0 0
calibData 0 0 0
sensorStart
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
After giving this CLI command i'm getting :- " Debug: Init Calibration Status = 0x1ffe"
Not getting what is the error.
 
Thanks & Regards,
Rehman
  • 0
    TI__Guru*** 148804 points

    Hi,

    I recommend starting with following config:

    C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\demo\xwr18xx\mmw\profiles\profile_3d.cfg

    Then modifying the Slope of the ramp to increase the range.

    Please try the following

    profileCfg 0 77 7 7 44 0 0 15 1 128 6200 0 0 40

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 265 points

    Hi,

    The give profileCfg is working fine, but when the Radar is pointed to an open environment with many objects the Radar is getting freezed.

    But the old chirp profile(8m) is working fine when pointed to the same open environment.

    Is it because of the more no.of objects detected it is getting freezed? Is there any way to figure it out?

    Thank you,

    Rehman

  • 0 in reply to Rehman
    TI__Guru*** 148804 points

    Hi,

    The radar should not freeze even if there are many objects.

    Are you using the sdk OOB demo and GUI or do you have your own GUI? 

    C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\demo\xwr18xx

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 265 points

    Hai Cesar,

    Actually we have made our custom GUI.

    We also have implemented CAN functionality in it. So the thing which we noted is that when it is in CANFD mode it is working fine but when changed to ClassicCAN mode the Radar is getting freezed after few minutes.

    We also are using Custom Chirp CFG of 50m which u have shared.

    While keeping the inbuilt CFG for 8m the Radar is not getting freezed even in ClassicCAN mode.

    Thanks & Regards,

    Rehman

  • 0 in reply to Rehman
    TI__Guru*** 148804 points

    Hi,

    Usually, as you mentioned, when using the 50m CFG there are more detected points. So, it is possible that the ClassicCAN interface does not have sufficient bandwidth to send the data.

    Cesar