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.

AWR1642BOOST: moving from demo to real application

Part Number: AWR1642BOOST

Hi everyone,

I have AWR1642BOOST SENSOR and start development with the DEMO application which can only detect objects in 4 meters range, I want  to develop this sensor to work in longer range and also need a documentation to help me understand CANFD messages that the sensor send.

Thanks,

Basel tahboub.

  • Basel,

    If you are looking to build an application to send out CANFD messages, you can take a look at the "Object Data Over Can" Lab that is part of the Automotive Toolbox found on TI's Resource Explorer and can be found here: http://dev.ti.com/tirex/explore/node?node=ADWAvz1GWDvSfSVkncqhEw__AocYeEd__LATEST

    For determining the type of chirp that you need in your target application, please take a look at the mmWave Sensing Estimator Tool found here: https://dev.ti.com/gallery/view/1792614/mmWaveSensingEstimator/ver/1.3.0/

    Regards,
    Kyle

  • Hi Kyle,

    I have already run "Object Data Over Can" Lab and it works properly, but now I want understand the CAN messages sent by the sensor via CANFD.

    I have problem with the source code that I can't find where the CAN messages sent and what is the meaning of the frames that i received on "PEAK can bus monitor".

     to make things clear, I want to read CANFD messages sent from sensor by SPC584B micro-controller and determine by this micro-controller (number ,position and velocity) for the objects detected by the mmw sensor.

    Thanks,

    Basel

  • Basel,

    This TI E2E forum does not provide support for STM microcontrollers. If you are trying to learn more about the CANFD messages, please refer to the mss_main.c files in the "Object Data Over Can" lab and search for "can_message". You can also search for the "can_transmit" to find the CAN specific functions to send out the data over CAN.

    The way that the output messages are populated is the same in this demo as it is in the SDK Out-of-Box Demo. The differences comes from the fact that we are sending the output messages through CAN and not through UART.

    This involves understanding TLV (Type Length Vector) messages that are used in our mmWave demos.

    Regards,
    Kyle