• State TI Thinks Resolved
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 43 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AWRL1432: Car Parkade Radar Sensor System

Shaun Rosario
Prodigy 10 points
Part Number: AWRL1432
Other Parts Discussed in Thread: MMWAVE-L-SDK, MMWAVE-SDK

Tool/software:

My group and I are working on an Indoor Car Parkade Project with the sole objective of having a display/dashboard with the count of available spaces in the lot. At present, we have decided to go forward with FMCW Radar Systems, but we are having trouble narrowing down the options with regard to the sensor.

For now, we have been looking at the AWRL1432 as an option, but wondering if, first, it is suitable for such a task, and secondly, if it is compatible with a Raspberry Pi for data transmission

The simple flow of the system in mind right now is AWRL1432-> Raspberry Pi -> Cloud Dashboard

Our requirements would be that the sensor would detect vehicles specifically, and we are trying to avoid accidental detection of persons or other inanimate objects. Any help or suggestions would be greatly appreciated!!!

  • 0
    TI__Genius 13156 points

    Hey Shaun,

    Thanks for reaching out! The Parking Garage Sensor Demo is probably the closest to your application, though it is made for our older IWR6843BOOST device. I would still review the code to get an idea of the processing chain which utilizes a dynamic and static objection detection algorithm (range FFT -> doppler FFT -> CFAR detection -> AoA estimation) and GTRACK for differentiating between parked vehicles and people. All of these DPUs exist within the AWRL1432 MMWAVE-L-SDK as well, though there will be differences in implementation. You can find documentation on the MMWAVE-L-SDK DPUs here and the MMWAVE-SDK DPUs can be found under <MMWAVE_SDK_INSTALL_DIR>/docs/mmwave_sdk_module_documentation.html if you have it downloaded.

    Regarding connecting up the AWRL1432 to Raspberry Pi, the AWRL1432 has support for UART, SPI, I2C, LIN, and CAN, so I'd choose an interface that best supports the needs of your application and data throughput requirements.

    Finally, regarding device selection, that will ultimately come down to the specific requirements. For example:

    • What is the maximum detection range for vehicles?
    • What is the maximum number of vehicles detectable?
    • Where will the sensor be positioned? How will it be oriented?

    Hopefully this helps, but let me know if you have any questions.

    Regards,

    Kristien