This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hi there
I have a question in AWRL1432_ADAS_BSD_DEMO_v2.0.
We just want to know in BSD Extend Vmax function is support RDmap function?
In config, we turn on
guiMonitor 2 1 0 0 1 1 0 0 1 0 0
In the number 5 place is RDmap enable, and number 2 place is range profile enable.
We saw in ccs code have function to using RD map, then when we check and do experiment, we get the range is correct but doppler is wrong.
the doppler part, half are zero values in doppler bins and MATLAB analyze surf figure like follow:
our engineer analyze, and turn on range profile function to compare between with RD map, there where have the same of single performance in range bins. (figure as follow)
RD map (x is range, y is single value)
Range profile
But speed(doppler) is wrong because we recorded data in RD map, half are zero values in doppler bins.
Now, the first question is how can we solve this or it's not support using RD map function?
second, the scaling function in range profile is 20*log10(data), does the TI team have RD map's scaling function?
third, in the detect point, we can get the point information like SNR and Noise, but the target's Amp(SNR + Noise) single is too different with range profile's single.
Thank you,
Leo Lin
Hi,
The "pGuiMonSel->rangeDopplerHeatMap" is not supported in this release. There is not sufficient time to transfer the RDMap.
One would need to increase the frame duration to 100ms and try again
thank you
Cesar
hello Cesar
Thank you for your reply.
in above case, my frame duration parameter is set 4s, so I thinks I have enough time to transfer the RD Map.
I add some information for your reference.
Hardware is AWRL1432 EVM Board 2-patch antennas, ES 2.0.
SDK version is 5.4.0.1.
config setting as follow:
sensorStop 0
channelCfg 7 3 0
chirpComnCfg 10 0 0 256 4 30.50 0
chirpTimingCfg 216.4 39 0 63.71 77
extendedMaxVelocity 1 6 7 3 4 2 1
frameCfg 256 0 63351 1 4000 1
antGeometryCfg 0 0 0 1 0 2 0 3 0 4 0 5
guiMonitor 2 1 0 0 1 1 0 0 1 0 0
sigProcChainCfg 64 2 1 0 0 0 0 0
boundaryBox -15 15 0 15
sensorPosition 0 0 0.0 0 0
staticBoundaryBox -3 3 0.5 7.5
gatingParam 3 5 5 10
stateParam 3 3 12 50 5 200
allocationParam 6 0.1 3 3 20
maxAcceleration -4 4
trackingCfg 1 2 100 32 400 50 60
presenceBoundaryBox -3 3 0.5 150 0 3
cfarCfg 2 8 4 3 0 12.0 0 0.95 0 1 1 1
cfarScndPassCfg 1 2 8 4 3 1 12.0 0
aoaFovCfg -80 80 -90 90
rangeSelCfg 0.3 10.0
clutterRemoval 0
dynClutterRemoval 0 0.90 10 10 2 2 0 16 0.90 20
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
lowPowerCfg 0
factoryCalibCfg 0 0 40 0 0x1ff000
compressionCfg 1 0.5
baudRate 1250000
sensorStart 0 0 0 0
If it's not support, where can I see the relevant information.
In CCS awrl1432_adas_bsd_evm_demo_es2 demo code, the function mmwDemo_DpcExecute() shows that
if(gMmwMssMCB.ifSlowFrame==true)
{
result->rngDopplerHeatMap = (uint32_t *) gMmwMssMCB.detMatrixSlow.data;
}
else
{
result->rngDopplerHeatMap = (uint32_t *) gMmwMssMCB.detMatrixFast.data;
}
so let me confirm again, CCS demo code is "have" this code, but "can not" use, right?
or after release new SDK version like 5.5 or 5.6 will support it?
thank you,
Leo Lin
Hi Lin,
On a different note, If you find that the enabling Range doppler heatmap in guiMontior cfg is giving you wrong results you can save the data in the MATLAB gui in fhist, surf and plot it to see RD heatmap. The MATLAB gui also provides range doppler point plot already
Hello Zorah
I thinks you don't understand my means. But I also find the not support information on SDK 5.4.0.1 document "MotionPresenceDetectionDemo_TuningGuide.pdf".
it's says NoiseProfile and RangeDopplerHeatMap are not used in the correct SDK, always set to 0.
So now, If we want to using this, just to wait a new release if TI add this function.
Thank you,
Leo Lin