Hi Team,
Consumer wants to beamforming the IWR1843 radar. The image currently burned is xwr18xx_mmw_demo.bin They want to change the txPhaseShifter in the .cfg file by modifying it to implement the beamforming straight ahead and display them in the visualizer for verification.
1) Open the visualizer settings slide panel, Save Config to PC. The configuration file at this point can be configured correctly and the mmWave device can be started.
2) Referring to the Phase Calculator in the Enable TX beamforming document, the value of txPhaseShifter with theta of 90 is calculated to be 16842752.
Then modify the value of the txPhaseShifter field only in the config file exported in the first step, and then load config from PC and send in the visualizer, the following error is reported:
3) The customer attempts to modify the .cfg file directly using the example provided in the Enable TX beamforming document, with the following changes:
- DfeDataOutputMode: Changed 1 to 3.
- Delete the frameCfg parameter (only for dfeDataOutputMode 1)
- Add the following code snippet:
But it still report the following error:
4) TI has MRR Beamsteering Lab to burn bin. However, the customer's data capture program is for xwr18xx_mmw_demo.bin, which is currently burned, and the burn of other images may be incompatible. So they're not considering that yet.
5) Could you help look into the following questions?
A. Burn the bin unboxing routine image, is it possible to modify the cfg file to implement beamforming? And visualization in visualizer (mmWave Demo Visualizer (TI.com)?
B. In addition to the currently modified parts, which parts need to be modified?
C. What constraint causes an error in the .cfg file, and how should this constraint be met?
The full .cfg file is as follows:
% *************************************************************** % Created for SDK ver:03.06 % Created using Visualizer ver:3.6.0.0 % Frequency:77 % Platform:xWR18xx % Scene Classifier:best_range_res % Azimuth Resolution(deg):15 % Range Resolution(m):0.044 % Maximum unambiguous Range(m):9.02 % Maximum Radial Velocity(m/s):1 % Radial velocity resolution(m/s):0.13 % Frame Duration(msec):250 % RF calibration data:None % Range Detection Threshold (dB):15 % Doppler Detection Threshold (dB):15 % Range Peak Grouping:enabled % Doppler Peak Grouping:enabled % Static clutter removal:disabled % Angle of Arrival FoV: Full FoV % Range FoV: Full FoV % Doppler FoV: Full FoV % *************************************************************** sensorStop flushCfg dfeDataOutputMode 3 channelCfg 15 5 0 adcCfg 2 1 adcbufCfg -1 0 1 1 1 profileCfg 0 61.0 10 6 135 0 14970880 1.8 1 256 2000 0 0 48 profileCfg 1 61.0 10 6 135 0 10276864 1.8 1 256 2000 0 0 48 profileCfg 2 61.0 10 6 135 0 6565888 1.8 1 256 2000 0 0 48 profileCfg 3 61.0 10 6 135 0 1871872 1.8 1 256 2000 0 0 48 chirpCfg 0 0 0 0 0 0 0 7 chirpCfg 1 1 1 0 0 0 0 7 chirpCfg 2 2 2 0 0 0 0 7 chirpCfg 3 3 3 0 0 0 0 7 advFrameCfg 4 0 0 1 0 subFrameCfg 0 0 0 1 128 80 0 1 1 80 subFrameCfg 1 0 1 1 128 80 0 1 1 80 subFrameCfg 2 0 2 1 128 80 0 1 1 80 subFrameCfg 3 0 3 1 128 80 0 1 1 160 lowPower 0 0 guiMonitor -1 1 1 0 1 1 1 cfarCfg -1 0 2 8 4 3 0 15 1 cfarCfg -1 1 0 4 2 3 1 15 1 multiObjBeamForming -1 1 0.5 clutterRemoval -1 0 calibDcRangeSig -1 0 -5 8 256 extendedMaxVelocity -1 0 lvdsStreamCfg -1 0 0 0 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 measureRangeBiasAndRxChanPhase 0 1.5 0.2 CQRxSatMonitor 0 3 5 121 0 CQSigImgMonitor 0 127 4 analogMonitor 0 0 aoaFovCfg -1 -90 90 -90 90 cfarFovCfg -1 0 0 8.92 cfarFovCfg -1 1 -1 1.00 calibData 0 0 0 sensorStart
Could you help check this case? Thanks.
Best Regards,
Cherry
