IWR6843: IWR6843 traffic monitoring application development

Sam KIM

Part Number: IWR6843

Dear experts

My name is Sam (Myeong), KIM (you can call me just KIM) and I would like to develop my own radar detector for traffic business.

IWR1642EVM is one of what I would like to develop, but it uses 76GHz, which is not allowed in Korea for traffic industrial business (like vehicle enforcement system, traffic data - volume, speed, occupancy collector).

My questions are;

1) Does IWR6843 have a similar one like IWR1642EVM traffic monitoring application?

2) If not, then I would like to have the IWR6843 with the options produced by Estimator (please see the attached). Does this require additional cost?

3) In order to develop, test, and make my own radar detector, what else I have to buy? like an antenna, controller board, etc...

I understand that my requests may not be proper for this Sensors forum. I am sorry for this and thanks for your understanding in advance.

KIM

over 6 years ago

0 Nitin Sakhuja over 6 years ago

TI__Mastermind 30405 points

Hi Kim,

We don't have a traffic monitoring lab for IWR6843 however the 50m Outdoor People Tracking and False Detection Filtering lab -68xx lab can be configured for traffic monitoring as explained in the following post:

IWR6843: Traffic Monitoring Demo

Regarding your other requirements:

1. TX and RX antenna gains are a function of antenna design so you will need to design your own custom high gain antenna (i.e. board) for this.

2. Transmit Power: The maximum transmit power on IWR6843 is 10dBm per TX channel.

Also, your maximum Range, Range Resolution and Velocity requirements appear to cause the Sensing Estrimator to generate invalid value (e.g. negative slope, negative bandwidth etc). We will look into why the Sensing estimator is generating these invalid values instead of generating errors. But these invalid values indicate that the specified application parameters cannot be achieved as is so you may try to reduce your requirements such as maximum velocity, velocity resolution, range resolution etc and see if that still fits your use case.

Regards

-Nitin