Hello
We are currently experimenting with the Overhead_3d_people_counting Demo from the Industrial Toolbox.
When we use the given chrip configuration "pc_6843_pc_aop_overhead_3m_radial.cfg" (code block below), everything is working fine. The radar is working and we can see the detected points in the Ti Visualizer.
sensorStop flushCfg dfeDataOutputMode 1 channelCfg 15 7 0 adcCfg 2 1 adcbufCfg -1 0 1 1 1 lowPower 0 0 profileCfg 0 61.2 60.00 17.00 50 328965 0 55.27 1 64 2000.00 2 1 36 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 4 frameCfg 0 2 224 0 120.00 1 0 dynamicRACfarCfg -1 10 1 1 1 8 8 6 4 4.00 6.00 0.50 1 1 staticRACfarCfg -1 4 4 2 2 8 16 4 6 6.00 13.00 0.50 0 0 dynamicRangeAngleCfg -1 7.000 0.0010 2 0 dynamic2DAngleCfg -1 5 1 1 1.00 15.00 2 staticRangeAngleCfg -1 0 1 1 %classifierCfg 1 1 1 500 0.6 1.0 0.95 10 antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0 antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2 antPhaseRot -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 fovCfg -1 64.0 64.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 staticBoundaryBox -3 3 -3 3 -0.5 3 boundaryBox -4 4 -4 4 -0.5 3 sensorPosition 2.9 0 90 gatingParam 3 2 2 3 4 stateParam 3 3 6 20 3 1000 allocationParam 20 20 0.05 20 1.5 20 maxAcceleration 1 0.1 1 trackingCfg 1 4 800 20 37 33 120 1 presenceBoundaryBox -4 4 -4 4 0.5 2.5 sensorStart
But we need for our case a bit more range, so we thought, we increase the number of ADC Values and the digOutSampleRate in the profileCfg Config and decrease the number of chirp loops in frameCfg (so that the radar cube will not be to large and the timing will be still correct.)
So we set the number of ADC values to 128, the digOutSampleRate to 4000 and the number of chirp loops to 112.
New profile:
sensorStop flushCfg dfeDataOutputMode 1 channelCfg 15 7 0 adcCfg 2 1 adcbufCfg -1 0 1 1 1 lowPower 0 0 profileCfg 0 61.2 60.00 17.00 50 328965 0 55.27 1 128 4000.00 2 1 36 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 4 frameCfg 0 2 112 0 120.00 1 0 dynamicRACfarCfg -1 10 1 1 1 8 8 6 4 4.00 6.00 0.50 1 1 staticRACfarCfg -1 4 4 2 2 8 16 4 6 6.00 13.00 0.50 0 0 dynamicRangeAngleCfg -1 7.000 0.0010 2 0 dynamic2DAngleCfg -1 5 1 1 1.00 15.00 2 staticRangeAngleCfg -1 0 1 1 %classifierCfg 1 1 1 500 0.6 1.0 0.95 10 antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0 antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2 antPhaseRot -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 fovCfg -1 64.0 64.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 staticBoundaryBox -3 3 -3 3 -0.5 3 boundaryBox -4 4 -4 4 -0.5 3 sensorPosition 2.9 0 90 gatingParam 3 2 2 3 4 stateParam 3 3 6 20 3 1000 allocationParam 20 20 0.05 20 1.5 20 maxAcceleration 1 0.1 1 trackingCfg 1 4 800 20 37 33 120 1 presenceBoundaryBox -4 4 -4 4 0.5 2.5 sensorStart
But with this new profile, the radar will not working. We experimented a bit, and we found out, that as soon as we increase the number of ADC values to something bigger than 64, the radar will not work anymore.
Does the demo has some limitation to the ADC value number? Or can someone give us a hint what we are doing wrong in our profile?
Many thanks in advance.
Best Regards,
Tobias
