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.

AWR6843AOPEVM: Using CAN protocol

Part Number: AWR6843AOPEVM
Other Parts Discussed in Thread: AWR6843AOP, AWR1642

Hello TI's,

I have looked over the forum and doc to get guidance on how to use the CAN protocol with my board, basically I want to add CAN transmission to the out-of-box demo to send the detection data through CAN.

I found related CAN driver file when exploring the sdk drivers folder, but having never used CAN I'd like some guidance on how to proceed.

If any tutorial/user guide is available, I'd like to have it.

Many thanks,

Lilia. 

  • Hello Lilia,

    Thank you for reaching out to Texas Instruments. Below is an excerpt from the following thread

    ---------------------------------------------------------------------------

    Object Data Over CAN Demo

    In the mmWave Radar Toolbox there is an example of CAN output communication.

    The standard SDK demo ( an older version) was modified to send the output data through CAN instead of UART

    mmwave_automotive_toolbox_3_6_0\labs\lab0005_object_data_over_can

    PCAN CAN to USB converter was used to communicate with PC

    Two relevant application notes were used

    https://www.ti.com/lit/an/spracg9/spracg9.pdf

    https://www.ti.com/lit/an/swra606/swra606.pdf

    ---------------------------------------------------------------------------

    Hope this helps,

    Ehtesham Shareef

  • Hello Ehtesham,

    Thank you for the reply, it helped a lot.

    I have another question in the same matter. My radar will send data through the CAN interface to a microcontroller USB port. For that I will be receiving a USB-CAN adapter soon. I will use simple DetectedPoint TLV.

    Now, my question is about how data should be retreived. When I check the Radar data through the UART on my PC, here is what I get : 

    I know the DetectedPoint TLV has 16bytes (x,y,z,velocity) which gives 32 Hex characters for each point. However when converting the Hex to values (each 8 Hex starting after the second line F character for example to get the x data), I get really weird values. I know I must be doing something wrong. So here are my questions : 

    - How do I retreive the radar data that will be received through my USB port to get the real x,y,z and velocity values ?

    - Another question, what happens when the radar detects nothing, does it send nothing or does it send a specified value to affirm that there is no detection (I will need this to set my actuators decisions).

    Thanks for the reply in advance.

    Lilia.

  • Hello Lilia,

    The values you are getting needs further investigation. I'm looking into your query and will get back to you soon

    Thanks,

    -Shareef

  • Hello Shareef, 

    A kind reminder for I am still in need of a response in this matter if you have any guidance please.

    Also, would you mind looking at my last reply in this THREAD, regardless of the code (which is non TI), I wish if possible to have answers for my questions and the reason why my data is similar to the X-Y scatter plot of the mmWave Visualizer (with no z), is there any way to adjust this please ?

    In hope to get an answer.

    Many thanks to you,

    Lilia.

  • Apologies for the delay, I have been backed up with other tasks. I am forwarding you to our In-Cabin team. 

  • Will be waiting for any return.

    Thanks a lot.

    Lilia.

  • Hey Lilia,

    I would recommend reviewing the following resource as it may help with this post and your other thread on UART data: 

    https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.10.00.13&node=A__ADnbI7zK9bSRgZqeAxprvQ__radar_toolbox__1AslXXD__1.10.00.13

    In summary of the above link, the 40 bytes after the 0xFF byte on the second line of the output is the start of the frame header. This is normally indicated by the magic word sequence, 0x0102, 0x0304, 0x0506, 0x0708, but it appears that the data might be displayed or retrieved as little-endian. The packet appears to contain normal data after correcting for the endianness - see the text file below for the translated output for the frame header and first detected point. 

    Let me know if you have any questions.

    Regards,

    Kristien

  • Hello Kristien,

    I don't know if I should keep CAN requests on this thread since it has been a bit mixed up (Please tell me if I should open a new one).

    While working with CAN on the AWR6843AOP EVM board with CCS 12.0.3 and Radar toolbox 1.10.00.13, I am trying to modify the Object data over CAN example on the AWR1642 BOOST to make it work with my board (still not the case), for that I have the following questions : 

    1- I saw in a thread that there are certain switch positions for CAN, could you inform me of the ones I need in my AWR6843AOP board once the code is flashed ?

    2- The board I use has 2 CAN-FD interfaces, how do I select the one I want to use ? is there a default one ?

    3- In the example there is a use of a mmWve CAN Visualizer, is this tool still available (I cannot find it) ? Also are my board + my CAN adapter (which is The following) compatible with its use ?

    4- A last thing, when using CAN, can I use the UART port (Number 1 in image) simultaneously, or do I only use the port 2 for supply needs ?

     

    Thanks and regards,

    Lilia.

  • Hey Lilia,

    I would recommend opening up a new thread since it seems these new questions would expand the scope of this thread; you can just copy and paste your questions into that new thread if you want. If you could post a link to the new thread here once its been opened, I will reply in the new thread once I have all the solutions to your questions. Once you've posted the link here and if you believe my previous reply solved your original question, then I would appreciate if you could mark this post as resolved so that I can close it. 

    Regards,

    Kristien

  • Hello Kristien,

    Thanks for the answer, here is the new thread.

    I am closing this one as solved.

    Thanks again,

    Lilia.