• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 248 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR1843BOOST: Why is the azimuth tilt of the sensor not supported in the GTrack configuration?

Ansis Sprugevics
Prodigy 30 points
Part Number: IWR1843BOOST

Hello,

I am using Traffic Monitoring from the industrial toolbox v4.10.1.

The documentation for people counting (which is meant to be referenced for TM tuning purposes too) says the following about the sensorPosition command:

Why is the azimuth tilt adjustment not supported? I've noticed that the tracking precision is greatly impacted by the azimuth sensor tilt.

If I want to monitor, say, an intersection from a corner, should I try to keep the sensor as straight as possible and limit the FOV via the boundaryBox command? Or should I just tilt the sensor without doing any configuration adjustments?

  • +1
    TI__Genius 14415 points

    Hello,

    The azimuth tilt is not currently supported by the tracker, but will be included in a future release. If you look through the tracker code where the elevTilt correction is applied you can see how to add an additional correction for azimuth tilt. There is no fundamental limitation, it just wasn't added into the sample code at this point.

    However, this tilt only affects the boundaryBox which will gate the tracks, but has no affect on the underlying radar signal processing. My suggestion is to point the radar system and center of the antenna radiation pattern toward the area of interest. Then, if the rectangular boundary box doesn't cover all the area, I would increase the boundaryBox size and widen the tracker range.

    Regards,

    Jackson