Other Parts Discussed in Thread: TIDEP-0090
Dear experts,
I see two solutions from TI to resolve speed ambiguity in MIMO TDM:
1. Extended Vmax CLI command that enables a correction procedure based on 3 hypotheses and corresponding angular spectra. The one with the biggest peak gives both correct speed and azimuth. This allows to unroll speed up to 3*Vmax and delivers a correct point cloud within one measurement cycle.
2. G-track automatically unrolls the aliased speed by range rate analysis over 3-5 measurement cycles. However, in case of MIMO the raw point cloud with aliased speed contains also incorrect azimuth due to unmatched Doppler compensation. Does G-track resolve both interrelated issues then? Is there any global parameter that tells G-track to take care of speed ambiguity?
Solution 1 can fail in case of multiple targets in the same range-Doppler bin or in case of large Doppler spread from a single target at a short range. Can G-track do the disambiguation all alone in case of MIMO at the cost of a few measurement cycles? Thanks in advance for shedding light on this.
Best,
Tim