IWR6843: Traffic Monitoring Demo

Hello Curtis,

The simplest method is to use the software from the 50m Outdoor People Tracking and False Detection Filtering lab -68xx. This is the same processing chain as the 1642 traffic monitoring lab and includes updates and bug fixes to the gtrack algorithm.

Other than the software, you will need to update your chirp configuration so that it is compatible with IWR6843. At minimum these are the changes that should be made to adapt your chirp cfg:

- channelCfg 15 3 0  to channelCfg 15 5 0, (There are 3 TX antennas on the 6843. The two azimuth TX antennas are TX0 and TX2 for the 6843)

- In profileCfg, at minimum the start frequency needs to be changed to be 60.25 (valid bandwidth for the 6843 is 60.25-64Ghz). However depending on your chirp the other parameters such as slope may need to be changed to be within the valid bandwidth.

- chirpCfg, as noted above, the TX antenna indices are different so cfgs that referenced TX1 need to be changed to TX2

Example: 

For 1642

chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2

For 6843

chirpCfg 0 0 0 0 0 0 0 1 (Same since TX0 remains the same)
chirpCfg 1 1 0 0 0 0 0 4 (Changed to reference TX2 instead of TX1)

- lowPower can be disabled so lowPower 0 0 is also supported (as opposed to lowPower 0 1 being mandatory for ES2.0 1642)

The configuration commands for gtrack have been modified slightly with the updates 

- SceneryParam <Left X Bound> <Right X Bound> <Near Y Bound> <Far Y Bound> (Here the SceneryParam command only supports one boundary box and one static box. The four parameters define the bounds of both boxes - in other words the static and boundary box have the same dimensions)

- GatingParam  <gating volume> <length> <width> <doppler> (No change other than capitalization of command)

- StateParam <det2act> <det2free> <act2free> <stat2free> <exit2free> (No change other than capitalization of command)

- AllocationParam <SNR threshold> <min velocity> <min points> <max distance> <max velocity> (No change other than capitalization of command)

- MaxAcceleration <max X Acceleration> <max Y Acceleration> <max Z Acceleration> Previously these values were defined in the source code and could not be modified at run time by cfg. These parameters are now exposed and can be set by cfg command (the previous hard coded values were max X Acceleration = 0, max Y acceleration 4, max Z acceleration = 1).

These are the minimum updates that attention should be paid to when updating the traffic monitoring cfg. The people counting cfg provided in the lab can also be used for reference.

 Amanda

Thanks Amanda, this is exactly what I needed.

Cheers,

Curtis