CCS/AWR1843BOOST: Raw data capture

Kazu Hira

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

Tool/software: Code Composer Studio

Hi,

I want to capture raw data from AWR1843 by DCA1000EVM CLI.
It seems that logging was success but conveting script doesn't work well.
I used 'DCA1000 With x16xx and IWR6843 MATLAB Example' below document.
www.ti.com/.../swra581b.pdf

I have checked LogFile and I think this recorded data lost some packets.
I tried many times with short recording(1sec,10frame) but all recorded data lost some packets.

I have some questions.
・Is data format of AWR1843 raw data same as IWR6843?
・Is this problem occurred by packet loss?
・Do you have sample scripts for raw data which lost some packets?

[LogFile]
Start record configuration :

Log mode : Raw
LVDS lane mode : 2 lane
Duration mode : Duration (500)
Max file size (MB) : 1024
*DT 1
14560 10192

Raw Data :
Out of sequence count - 1
Out of sequence seen from 10 to 18
First Packet ID - 1
Last Packet ID - 2695
Number of received packets - 2688
Number of zero filled packets - 7
Number of zero filled bytes - 10192
Capture start time - Tue Jul 07 11:23:58 2020
Capture end time - Tue Jul 07 11:23:59 2020
Duration(sec) - 1

[radar]
AWR1843
[SDK]
mmwave_sdk_03_03_00_03
[Demo]
'...\ti\mmwave_industrial_toolbox_4_2_1\labs\out_of_box_demo\18xx_mmwave_sdk'
[CCS]
8.3.1.00004

Regards,
Kazuki

over 5 years ago

0 zigang Yang over 5 years ago

TI__Mastermind 40195 points

Hi, Kazuki:

1) It is required to start DCA1000 data capture before mmwave sensor start. Are you doing that? What is your json file?

2) What is your sensor configuration? LVDS also has speed limitation. You can add some idle time between chirps to slow down the data rate.

Best,

Zigang

0 Kazu Hira over 5 years ago in reply to zigang Yang

Intellectual 680 points

Hi Zigang,

Yes, I start DCA1000 data capture before mmwave sensor.

I show json file and sensor configuration below.

Lost packets is resolved when I change PC. I think packet lost is caused by low performance of my PC.

Anyway, I think lost packet can happen with any configuration.

Let me know if you have any solutions for packet lost.

I have tried to convert raw data(without lost packets) by your scripts.

www.ti.com/.../swra581b.pdf

But this script doesn't work well.

I understand captured data size is calculated by '2bytes * 2(IQ mode) *no. of sample* no. of Tx * no. of Rx * no. of chirp'.

But recorded data size is a little big.

Is there any additional information such as header information?

I think your script doesn't work if captured data includes additional information.

[radar configuration]

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 7 0

adcCfg 2 1

adcbufCfg -1 0 1 1 1

profileCfg 0 76.570703125 2.6 4.5 30.6 131586 0 11.71875 1 256 10000 0 0 30

chirpCfg 0 0 0 0 0 0 0 1

chirpCfg 1 1 0 0 0 0 0 4

chirpCfg 2 2 0 0 0 0 0 2

frameCfg 0 2 60 0 100 1 0

lowPower 0 1

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 1 1 1

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

sensorStart

[JSON]

{

"DCA1000Config": {

"dataLoggingMode": "raw",

"dataTransferMode": "LVDSCapture",

"dataCaptureMode": "ethernetStream",

"lvdsMode": 2,

"dataFormatMode": 3,

"packetDelay_us": 25,

"ethernetConfig": {

"DCA1000IPAddress": "192.168.33.180",

"DCA1000ConfigPort": 4096,

"DCA1000DataPort": 4098

"ethernetConfigUpdate": {

"systemIPAddress": "192.168.33.30",

"DCA1000IPAddress": "192.168.33.180",

"DCA1000MACAddress": "12.34.56.78.90.12",

"DCA1000ConfigPort": 4096,

"DCA1000DataPort": 4098

"captureConfig": {

"fileBasePath": "C:\\Users\\0000107257\\Documents\\mmr\\data",

"filePrefix": "test_capture",

"maxRecFileSize_MB": 1024,

"sequenceNumberEnable": 1,

"captureStopMode": "duration",

"bytesToCapture": 50000,

"durationToCapture_ms": 500,

"framesToCapture":100

"dataFormatConfig": {

"MSBToggle": 0,

"reorderEnable": 1,

"laneFmtMap": 0,

"dataPortConfig": [

{

"portIdx": 0,

"dataType": "complex"

{

"portIdx": 1,

"dataType": "complex"

{

"portIdx": 2,

"dataType": "complex"

{

"portIdx": 3,

"dataType": "complex"

{

"portIdx": 4,

"dataType": "complex"

}

]

}

Regards,

Kazuki

0 zigang Yang over 5 years ago in reply to Kazu Hira

TI__Mastermind 40195 points

HI, Kazuki:

Your lvdsStreamCfg has included header and point cloud result. Please search lvdsStreamCfg in the SDK users guide to understand each parameter.

lvdsStreamCfg -1 1 1 1

I would recommend to change to skip the header and point cloud data, and just have the ADC raw data out.

lvdsStreamCfg -1 0 1 0

For the data format, with reorderEnable set to 1 in datacard config json file, the data is already in the order of complex pairs. In addition, the out of box demo only support the adcbufCfg with Q samples before I samples. (Note that the original data format is listed in figure 11 before reorderEnable at: http://www.ti.com/lit/an/swra581b/swra581b.pdf). You can find the reorderEnable option and other capture size option inside following documentation: C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\ReferenceCode\DCA1000\Docs

Best,

Zigang

Sensors

Sensors forum

CCS/AWR1843BOOST: Raw data capture