AWR1642BOOST: How to into the collection mode for occupancy detection

Hi, 

The demo is deprecated in the latest toolbox. Please let me know the target application so that we can help you with the current demos. 

Regards, 

Sudharshan K N 

Hi Team:

  I use toolbox 3.0.0 and want to modify the detection area of occupancy vitalsigns detection. When I was doing Coefficent tuning, I used the practice provided by the occupancy detection example (I have read the User guide of occupancy vitalsigns detection, but it seems that no relevant tools are provided), but the results of the tuning are not good. So I want to confirm whether the coefficent tuning used by occupancy detection and occupancy vitalsigns detection is the same?

The chirp configs are set as follows

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 1
profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40
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 1
chirpCfg 3 3 0 0 0 0 0 2
frameCfg 0 3 128 0 160 1 0
lowPower 0 1
%heatmap size MUST be 32 for data collection mode
guiMonitor 0 1 32

%OD Demo commands:
% Note: secondary zones must always be listed last.
%zoneDef 6 9 10 8 14 9 10 26 14 24 10 8 14 24 10 26 14 9 10 8 32 24 10 8 32
zoneDef 2 20 6 12 6 20 6 32 6
% secZoneDef is for Matlab use only. The arguments are as follows: 1-based zone number is
% a secondary zone. It applies to 2 primary zones in this case, 1 and 2 or 3 and 4.
%secZoneDef 5 2 1 2
%secZoneDef 6 2 3 4

coeffMatrixRow 0 0 -1.218932 0.265320 0.559583 0.098494 0.314404 0.118768
coeffMatrixRow 0 1 -1.429470 0.536992 0.142466 1.293644 0.240890 0.012733
coeffMatrixRow 0 2 -1.463758 -0.710797 -0.750260 -0.213368 0.260609 -0.168671
coeffMatrixRow 0 3 -1.169826 -0.230648 -0.094954 0.208354 0.548181 0.072391
meanVector 0 15.812300 15.446816 -2.831587 -3.197071 0.131473
stdVector 0 0.089480 0.059255 0.038437 0.041994 0.314264

rowNoise 0 8 3.106228 2.694473 3.062507 4.701762 7.016233 10.097070 13.351712 17.348766
rowNoise 8 8 21.435425 24.456087 27.349701 31.464687 34.234699 35.344517 37.776081 40.780220
rowNoise 16 8 41.472107 42.080433 44.675781 45.670506 45.197586 46.849339 48.717022 47.903423
rowNoise 24 8 47.901569 50.175549 50.254444 49.225483 50.628826 51.961540 51.955933 56.832573
rowNoise 32 8 59.581142 54.199657 51.650806 53.338112 55.709354 55.763119 55.914028 57.273705
rowNoise 40 8 55.641941 54.065479 55.145973 55.895340 53.542904 54.920750 57.463428 55.867855
rowNoise 48 8 54.260815 57.270500 58.346401 55.830559 58.891968 60.730873 57.758041 53.471062
rowNoise 56 8 54.098488 53.485073 43.238174 27.188110 13.080183 5.134599 1.904554 1.871889

%mode: 1=operational, 2=zone tuning, 3=data collection (use 32 for heatmap size above)
oddemoParms 3 8 0.001 0.50 18 0.45
sensorStart

Hi Team:

I only have 1642 development tools. Using occupancy vitalsigns detection to modify should be a better way. Can you guide me on how to perform Coefficent tuning?

Hi, 

Sorry for the delay. we will check internally and get back to you next week. 

Regards, 

Sudharshan K N 

Is there any status update for this project?

Hi, 

Can you please let me what method was used to arrive at the new coefficients? 

Regards, 

Sudharshan K N 

Hi, 

From the profile config it looks like you are trying to use the demo with a different GUI. The parameters and the GUI may not match each other for different demo and this could be one of the possible reasons for the error. Have you tried to use the GUI from the same demo and check if it worked fine? 

Regards, 

Sudharshan K N