AWR1843AOPEVM: Demo Questions

Gregory Miller

Part Number: AWR1843AOPEVM

Tool/software:

I have got the demo to run and have run it on the Industrial visualizer. However, there is a problem with the visualizer. When I move my hand left and right it tracks just fine but, when I move my hand up and down it shows me moving left and right why is that?

I think that I have looked through the code enough to know that it is not a problem with the python code but I am not entirely sure.

Please advise.

7 months ago

0 Zorah Ahmad 7 months ago

TI__Expert 3805 points

can you share the orientation of your radar?

0 Gregory Miller 7 months ago in reply to Zorah Ahmad

Prodigy 30 points

It is vertically placed with the radar chip close to the top.

0 Zorah Ahmad 7 months ago in reply to Gregory Miller

TI__Expert 3805 points

what is flashed on your device and what cfg are you using?

0 Gregory Miller 7 months ago in reply to Zorah Ahmad

Prodigy 30 points

The demo given in the sdk xwr18xx_mmw_demo and the cfg is the profile_3d

0 Zorah Ahmad 7 months ago in reply to Gregory Miller

TI__Expert 3805 points

Please try with the following visualizer: https://dev.ti.com
/mmWaveDemoVisualizer

0 Gregory Miller 7 months ago in reply to Zorah Ahmad

Prodigy 30 points

I tried that but is there a way to change the direction of the 3d plot?

like I can not tell if I am moving in x or z direction because I cannot change the camera

0 Gregory Miller 7 months ago in reply to Gregory Miller

Prodigy 30 points

Actually from that demo I do not think it is even tracking me it just shows a bunch of dots that are near but they do not follow my hand up or down left or right.

0 Zorah Ahmad 7 months ago in reply to Gregory Miller

TI__Expert 3805 points

Gregory,

The out of box demo does not come with tracking. The recommended visualizer is the https://dev.ti.com/mmWaveDemoVisualizer, only what is provided as part of the visualizer is supported

0 Gregory Miller 7 months ago in reply to Zorah Ahmad

Prodigy 30 points

I do not mean tracking but if I move my hand the dots should also move in the next frame. like in the industrial visualizer.

0 Gregory Miller 7 months ago in reply to Gregory Miller

Prodigy 30 points

The visualizer that I am talking about is the one provided in the mmwave toolbox

0 Gregory Miller 6 months ago in reply to Gregory Miller

Prodigy 30 points

Please respond

0 Zorah Ahmad 6 months ago in reply to Gregory Miller

TI__Expert 3805 points

Please send me the path of the visualizer you are trying to run from the toolbox

0 Gregory Miller 6 months ago in reply to Zorah Ahmad

Prodigy 30 points

C:\ti\radar_toolbox_2_10_00_04\tools\visualizers\Applications_Visualizer\Body_And_Chassis_Visualizer

0 Kristien Everett 6 months ago in reply to Gregory Miller

TI__Expert 8765 points

Hey Greg,

For the board, it should be oriented where the sensor is along the left side of the board similar to the orientation of the xWR6843AOP board shown below.

For the tracking in the visualizer, you can lower the number of frames that persist to 1 to help discern the current points coming in.

As for camera orientation, the visualizer always opens with the sensor in the following orientation. You can rotate the camera by left clicking in the plot area, pan horizontally with middle mouse button, and pan vertically with ctrl + middle mouse button.

Let me know if this information clears up any confusion on interpreting detected points.

Regards,

Kristien

0 Gregory Miller 6 months ago in reply to Kristien Everett

Prodigy 30 points

I oriented the chip like you said to and when I move left and right it tracks left and right but when I move up and down it tracks left and right

+1 Gregory Miller 6 months ago in reply to Gregory Miller

Prodigy 30 points

I figured it out I uniFlashed a different bin file and it seems to be working now

0 Gregory Miller 6 months ago in reply to Gregory Miller

Prodigy 30 points

where in this cfg would I set the frame rate? For example I want a frame rate of 12.5 or 0.08 Hz

% Carrier frequency GHz 77

% Ramp Slope MHz/us 100

% Num ADC Samples 256

% ADC Sampling Rate Msps 7.2

% ADC Collection Time us 35.56

% Extra ramp time required (start time) us 3

% Chirp time (end time - start time) us 36

% Chirp duration (end time) us 39

% Sweep BW (useful) MHz 3555.56

% Total BW MHz 3900

% Max beat freq (80% of ADC sampling rate) MHz 5.76

% Max distance (80%) m 8.64

% Range resolution m 0.042

% Range resolution (meter per 1D-FFT bin) m/bin 0.042

% Inter-chirp duration us 7

% Number of chirp intervals in frame - 96

% Number of TX (TDM MIMO) 3

% Number of Tx elevation antennas 0

% Number of RX channels - 4

% Max umambiguous relative velocity kmph 25.41

% mileph 15.88

% Max extended relative velocity kmph 76.23

% mileph 47.64

% Frame time (total) ms 4.416

% Frame time (active) ms 3.744

% Range FFT size - 256

% Doppler FFT size - 32

% Radar data memory required KB 400

% Velocity resolution m/s 0.44

% Velocity resolution (m/s per 2D-FFT bin) m/s/bin 0.44

% Velocity Maximum m/s 7.06

% Extended Maximum Velocity m/s 21.17

% Maximum sweep accorss range bins range bin 0.74

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 7 0

adcCfg 2 1

adcbufCfg -1 0 1 1 1

lowPower 0 0

profileCfg 0 77 7 3 39 0 0 100 1 256 7200 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 32 0 100 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 256

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 8.64

cfarFovCfg -1 1 -7.06 7.06

extendedMaxVelocity -1 0

CQRxSatMonitor 0 3 11 121 0

CQSigImgMonitor 0 127 8

analogMonitor 0 0

lvdsStreamCfg -1 0 0 0

calibData 0 0 0

sensorStart

+1 Kristien Everett 6 months ago in reply to Gregory Miller

TI__Expert 8765 points

Hey Gregory,

I'm glad you were able to resolve the original issue on your end! I'll answer this new question this time, but if you do have additional questions that are not related to the original question, please create a new post, so that its easier for others to also find answers to similar queries.

The fifth parameter of the frameCfg, currently set to 100 ms, specifies the frame period, so a frame period of 80 ms would match 12.5 Hz. I would also recommend taking a look at the mmWave Sensing Estimator, specifically the advanced tab, which helps users create, modify, and understand chirp configuration files.

Regards,

Kristien

0 Gregory Miller 6 months ago in reply to Kristien Everett

Prodigy 30 points

Perfect thank you

0 Kristien Everett 6 months ago in reply to Gregory Miller

TI__Expert 8765 points

No problem, Gregory!

Sensors

Sensors forum

AWR1843AOPEVM: Demo Questions