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.

AWR1843: AWR1843 - Serial communication with Raspberry Pi

Part Number: AWR1843
Other Parts Discussed in Thread: AWR1642

Hello,

We are currently working with the AWR1843 radar module for object detection using Raspberry Pi.

We generated a config file from mmWave Demo Visualizer for the radar with 2 transmitter and 4 receivers .

We are reading the collected data serially radar on Raspberry Pi  after sending the mentioned configuration file for further processing 

Following are a few queries/doubts we would like you to help us with:

1. While sending the configuration and reading the detected objects, we came across the term "Magic Number". We would like to know what exactly is it because, this number seems to change sometimes.

2. In the image below, we came across a field called "Descriptor" in the detected objects area. While referring to the "C:\ti\mmwave_sdk_03_01_00_02\packages\ti\demo\xwr18xx\mmw\docs\doxygen\html\index,html" file, in the "MmwDemo_transmitProcessedOutput" function we could not find any reference to the descriptor. It looks like the descriptor is no more valid in the newest sdk. Kindly let us know about it.

3. As we can see in the attached figure, the header has a total of 40 bytes(36 + 4 bytes for sub-frame as referred to index.html file).

    Suppose we detect 4 objects, the results are fine. The calculations are as follows:

    Data buffer = Header(40 bytes) + Detected Objects(Tag and Length)(8 bytes) + Payload(4*16), where 4 - # of objects detected.

    Data buffer = 112 bytes < 128 bytes (works fine in this case)

    If the # of objects detected is >5, Data buffer >128 and it gives an error.

    We would like to know why does this happen or are we missing anything.

5. We are using the attached file for Demo Data Structure v0.1 for AWR1642 as a reference. Is there a similar document for AWR1843 or does it follow the same format.

mmw_demo_datastructure_SDK2.pdf

  • Vipul,

    The magic word is part of the output header that is sent before any of the other TLV output data sent over UART.

    The magic word is the same for every set of output data. The GUI visualizer will typically use the magic word as part of validating the output data to confirm the start of a new set of output data. If someone you are not receiving the same magic number, you may need to review how you are parsing the received output data.

    If you are using a demo other than the Out-of-Box demo, you will need to review the documentation specific to that application to understand exactly what data is being sent out as the type and number of TLVs sent out for may be different.

    The attachment you have provided is for SDK v1.x and is not applicable for SDK v3.x. You need to review the TLVs to understand their structure and what the expected size for each TLV is.

    But at a high level, you need to understand at the source code level what the structure of each TLV is as it seems there is some confusion between your source code and the documentation.

    Regards,

    Kyle