AWRL6432BOOST: Change numOfChirpsAccum in burst mode

Hi,

This should be fine. Can you specify what error you are getting, as well as maybe provide some screenshots or more context?

Regards,

Tim

Hello 

Error message is as follows.

The cli command value is as follows.

sensorStop 0
channelCfg 7 3 0
chirpComnCfg 16 0 0 128 4 28 0
chirpTimingCfg 6 32 0 27 60.5
frameCfg 2 4 200 64 100 0
antGeometryCfg 0 0 1 1 0 2 0 1 1 2 0 3 2.418 2.418
guiMonitor 2 3 0 0 0 1 0 0 1 1 1
sigProcChainCfg 32 2 3 2 8 8 1 0.3
cfarCfg 2 16 4 4 0 6.0 0 0.5 0 1 1 1
aoaFovCfg -60 60 -40 40
rangeSelCfg 0.1 15.0
clutterRemoval 1
compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000
adcDataSource 0 adc_data_0001_CtestAdc6Ant.bin
adcLogging 0
lowPowerCfg 1
factoryCalibCfg 1 0 40 0 0x1ff000
mpdBoundaryArc 1 1 15 -30 30 0.5 2
mpdBoundaryArc 2 1 15 -60 -31 0.5 2
mpdBoundaryArc 3 1 15 31 60 0.5 2
boundaryBox -16 16 0 16 -0.5 3
sensorPosition 0 0 1.9 0 0
majorStateCfg 8 6 60 20 15 150 4 4
clusterCfg 1 0.5 2
gatingParam 3 2 2 2 4
stateParam 3 3 12 50 5 200
allocationParam 4 10 0.1 2 0.5 20
maxAcceleration 0.4 0.4 0.1
trackingCfg 1 2 100 1 61.4 191.8 100
presenceBoundaryBox -3 3 0.5 7.5 0 3
microDopplerCfg 1 0 0.5 0 1 1 12.5 87.5 1
classifierCfg 1 3 4
baudRate 1250000
sensorStart 0 0 0 0

I loaded the same .cfg file,  it doesn't work in the industrial visualizer, but it works in the mmwave radar visualizer.

What's the problem?

Hi,

Are you trying to run the Out of Box demo?

Does it work with the default .cfg file we provide?

Please make sure you fully reset the device before trying to run the visualizer.

Regards,

Tim

Hello

Are you trying to run the Out of Box demo?
>Yes, AWRL6432 Out of box

Does it work with the default .cfg file we provide?
> Yes, The problem occurs when the numOfChirpsAccum is changed to 4.

(if you set the numOfChirpsAccum to 0, it works well.)

Please make sure you fully reset the device before trying to run the visualizer.
> Yes, I did it after resetting

Thansk.

Hi,

Please try:

frameCfg 4 4 300 64 100 0

so you have 4 chirps in a burst.

Regards,

Tim

Hello,

I changed it to frameCfg 4 4 300 64 100 0.

However, an error occurred in the sensing estimator, so I modified the CLI commands as follows.

chirpComnCfg 16 0 0 128 4 40 0
chirpTimingCfg 6 32 0 20 60.5
channelCfg 7 3 0
frameCfg 4 4 300 64 100 0

But, the same error message still occurs.

And I have another question.
The document says as follows, can I change the numofChirpInBursts to 4?

 " Burst Mode: The numOfBurstsInFrame can be configured to >1, but the numOfChirpsInBurst
must be configured to 1 (when only 1 TX is enabled) or 2 (when both TXs are enabled). Then the
numOfBurstsInFrame will correspond the total number of chirps in a frame per TX antenna. "

Thank you.

INHO CHOI said:

e document says as follows, can I change the numofChirpInBursts to 4?

Yes this should be possible.

Can you please try sending the config over tera term so we can see what error code is being printed by the device? This should help us narrow down.

Regards,

Tim

Hello

I entered the CLI command using Teraterm and received an error message return.

If my test method is wrong, can you explain the method in detail?

******************************************
xWRL6432 MMW Demo 05.03.00.02
******************************************
mmwDemo:/>sensorStop 0
Done

mmwDemo:/>channelCfg 7 3 0
Done

mmwDemo:/>chirpComnCfg 16 0 0 128 4 40 0
Done

mmwDemo:/>chirpTimingCfg 6 32 0 20 60.5
Done

mmwDemo:/>frameCfg 4 4 300 64 100 0
Done

mmwDemo:/>antGeometryCfg 0 0 1 1 0 2 0 1 1 2 0 3 2.418 2.418
Done

mmwDemo:/>guiMonitor 2 3 0 0 0 1 0 0 1 1 1
Done

mmwDemo:/>sigProcChainCfg 32 2 3 2 8 8 1 0.3
Done

mmwDemo:/>cfarCfg 2 13 4 4 0 6.0 0 0.5 0 1 1 1
Done

mmwDemo:/>aoaFovCfg -60 60 -40 40
Done

mmwDemo:/>rangeSelCfg 0.1 15.0
Done

mmwDemo:/>clutterRemoval 1
Done

mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000
Done

mmwDemo:/>adcDataSource 0 adc_data_0001_CtestAdc6Ant.bin
Done

mmwDemo:/>adcLogging 0
Done

mmwDemo:/>lowPowerCfg 1
Done

mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000
Done

mmwDemo:/>mpdBoundaryArc 1 1 15 -30 30 0.5 2
'mpdBoundaryArc' is not recognized as a CLI command
mmwDemo:/>mpdBoundaryArc 2 1 15 -60 -31 0.5 2
'mpdBoundaryArc' is not recognized as a CLI command
mmwDemo:/>mpdBoundaryArc 3 1 15 31 60 0.5 2
'mpdBoundaryArc' is not recognized as a CLI command
mmwDemo:/>boundaryBox -16 16 0 16 -0.5 3
Done

mmwDemo:/>sensorPosition 0 0 1.9 0 0
Done

mmwDemo:/>majorStateCfg 8 6 60 20 15 150 4 4
Done

mmwDemo:/>clusterCfg 1 0.5 2
Done

mmwDemo:/>gatingParam 3 2 2 2 4
Done

mmwDemo:/>stateParam 3 3 12 50 5 200
Done

mmwDemo:/>allocationParam 4 10 0.5 2 0.5 20
Done

mmwDemo:/>maxAcceleration 0.4 0.4 0.1
Done

mmwDemo:/>trackingCfg 1 2 100 1 61.4 191.8 100
Done

mmwDemo:/>presenceBoundaryBox -3 3 0.5 7.5 0 3
Done

mmwDemo:/>microDopplerCfg 1 0 0.5 0 1 1 12.5 87.5 1
Done

mmwDemo:/>classifierCfg 1 3 4
Done

mmwDemo:/>baudRate 115200
Done

mmwDemo:/>sensorStart 0 0 0 0
Error: Error in setting up doa profile:-30201

Hello,

Changed framecfg to 2 4 400 64 100 0.

It works, but after the frame is operated between 1 and 7, the following error appears and stops working.

ERROR: No data detected on COM Port, read timed out
Be sure that the device is in the proper mode, and that the cfg you are sending is valid

So I increased the burst time to 500 or 600, and the same thing happens.

Thanks.

Hello,

Can you try and use TDM mode instead of BPM? This is set in chirpComnCfg (change 4 to a 1)

Regards,

Tim

Hello,

I try TDM mode instead of BPM. But, I got the same error. 

ERROR: No data detected on COM Port, read timed out
Be sure that the device is in the proper mode, and that the cfg you are sending is valid

Thanks.

Hello,

I use a tera term and send the .cfg . (chirpComnCfg change 4 to a 1)

But, tera term stops and the error does not appear.

Thanks.