IWR6843ISK: How does IWR6843ISK extend max velocity and the problem encounter in improved velocity resolution

Chia Hsing Yang

Part Number: IWR6843ISK

Hello I have some question about IWR6843ISK

1)We know IWR6843ISK support to extend maximum velocity to 2x, we want to know what principle is used. And does it needs to operate in a specific mode (e.g.: MIMO).

2)Known radar cube size is 768kB in IWR6843ISK, we want to improve velocity resolution. Now we encounter some terrible by increase chirp numbers(M) in a frame.

Our goal is to achieve max range is 90m, range resolution 40cm, max velocity 90km/hr, and velocity resolution 1km/hr at the same time.

Below is the cfg. file setting we want to tune:

profileCfg 0 60 22 7 28 0 0 20 1 256 12500 0 0 48

frameCfg 0 1 96 0 50 1 0

we calculate N=256 and M=96 will not exceed 768kB, but now we only can set M=80, which can let radar work.

The error report return by MATLAB tm_visualizer is:

The original M is 64, we also tune M value within 64 to 80 but most of the value can not let the radar work. The error report is the same as the above.

Looking forward to your reply.

over 5 years ago

0 Chia Hsing Yang over 5 years ago

Prodigy 30 points

The error report return by MATLAB tm_visualizer is:

0 Vaibhav Mahimkar over 5 years ago in reply to Chia Hsing Yang

TI__Mastermind 23725 points

Hello

Can you please confirm if you have tired the extendedMaxVelocity feature in the SDK's OOB demo and confirmed that it provides the velocity extension.

Please see the User's guide and relevant implementation in the DPU for Velocity estimation.

https://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/latest/exports/mmwave_sdk_user_guide.pdf

Thank you,

Vaibhav

0 Former Member over 5 years ago in reply to Vaibhav Mahimkar

Can you provide the full log file of the console? It should be in the same path as the gui

0 Chia Hsing Yang over 5 years ago in reply to Former Member

Prodigy 30 points

Hi Amanda:

Here is the full log file of the console.

Fullscreen tm_console_log.txt Download

COM6 opened. 
COM7 opened. 
Warning: Directory already exists. 
> In tm_visualizer_modify_0902 (line 49) 
Opening tm_demo_uart_stream_1.txt. Ready to log data. 
Opening configuration file 
Parsing configuration file...
Skip parsing for: sensorStop command
Skip parsing for: flushCfg command
Skip parsing for: sensorStart command
COM6 opened. 
COM7 opened. 
Sending cfg file to device...
sensorStop
flushCfg
Done
dfeDataOutputMode 1
Done
channelCfg 15 5 0
Done
adcCfg 2 1
Done
adcbufCfg -1 0 1 1 1
Done
profileCfg 0 60 22 7 28 0 0 20 1 256 12500 0 0 48
Done
chirpCfg 0 0 0 0 0 0 0 1
Done
chirpCfg 1 1 0 0 0 0 0 4
Done
frameCfg 0 1 96 0 50 1 0
Done
lowPower 0 0
Done
guiMonitor -1 1 0 0 0 0 0
Done
cfarCfg -1 0 2 8 4 3 0 10 0
Done
cfarCfg -1 1 0 4 2 3 1 12 0
Done
multiObjBeamForming -1 1 0.5
Done
clutterRemoval -1 1
Done
calibDcRangeSig -1 0 -5 8 256
Done
extendedMaxVelocity -1 1
Done
bpmCfg -1 0 0 1
Done
lvdsStreamCfg -1 0 0 0
Done
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
Done
measureRangeBiasAndRxChanPhase 0 1.5 0.2
Done
CQRxSatMonitor 0 3 4 63 0
Done
CQSigImgMonitor 0 127 4
Done
analogMonitor 0 0
Done
aoaFovCfg -1 -90 90 -90 90
Done
cfarFovCfg -1 0 0 80
Done
cfarFovCfg -1 1 -30 30.00
Done
staticBoundaryBox -40 40 20 70 -3 3
Done
boundaryBox -50 50 10 80 -3 3
Done
gatingParam 20 15 15 15 200
Done
stateParam 15 10 10 1000 10
Done
allocationParam 60 50 1 3 5 50.0
Done
maxAcceleration 50 50 0.1
Done
trackingCfg 1 2 250 20 113 355 50 90
Done
sensorStart
Warning: A timeout occurred before the Terminator was reached.
'serial' unable to read all requested data. For more information on possible reasons, see Serial Read
Warnings.

0 Former Member over 5 years ago in reply to Chia Hsing Yang

Hello,

Does the same profile and frameCfg work with the out of box demo?

Please try the chirp with the out of box demo first. There are instructions in the UG for running the demo in CCS debug mode please do so and provide the error message that occurs in the console window.

It appears from the log you provided that the device is crashing. This could be do to a timing issue - you can try increasing the frame period from 50ms to 100ms and see if this resolves the error. Depending on what output and processing options you have enabled you may be running out of interframe period.

Amanda

Sensors

Sensors forum

IWR6843ISK: How does IWR6843ISK extend max velocity and the problem encounter in improved velocity resolution