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.

AWR1843BOOST: AWR1843 tracking

Part Number: AWR1843BOOST

Hi Experts,

Good day.

I am making a deskop app thats like MRRVisualizer in lab7. As a reference, I am using the code in the read_serial_port_and_plot_object_location file. İn my program, I am getting tlvtype 3 when It's one object moving when I setup radar on the road and there are a lot of cars I am always getting tlv type 1 and numbers like 458701. I am doing exact same thing from read_serial_port_and_plot_object_location file. MMRVisualizer works perfectly on the road for tracking vehicles. what should I do to get tlv type 3 when I am on the road?

Regards,

Josel

  • Hi Josel,

    Are you saying that you are unable to obtain a complete TLV in the UART packet or its just issues with decoding it?

    Have you verified your parsing algorithm when compared with the Visualizer? If not, I would urge you to first do a comparison against the visualizer with known inputs.

    Regards,

    Kaushik

  • Hi Kaushik,

    I don't think I have issues with decoding because I am getting tlv type 3 when there is one object moving. I need to be able to track multiple vehicles but when I am on the road with multiple vehicles I am not getting tlv type 3. I verified my parsing algorithm according to Visualizer. My only problem is getting tlv type 3 when there are multiple vehicles.

    Please advise

    Regards,

    Josel

  • Hi Josel,

    Please confirm my understanding.

    • Device is sending the same UART TLV packets to both the MRR GUI by TI and your desktop application.
    • MRR GUI is able to pick up all the tracker outputs (More than 1 track per UART frame)
    • Your application is able to pick out only 1 tracker info from this packet.

    If my understanding is correct, then for the same amount of data sent out by the device, your application does not seem to fully parse the TLV data. I would urge you to check the same again. 

    If not, please re-iterate your issue with more details (images would help)

    Regards,

    Kaushik

  • Hi Kaushik,

    You are correct about understanding. İn my desktop app I am parsing tlv type and printing but I don't think I have a problem with tlv parsing because it works when I am experimenting with a small amount of objects. When I set up in the road I am only able to get tlv type 1. Do I have to write my own tracking algorithm on top of tlv type 1 or do I need to be able to get tracking tlv?

    Regards,

    Josel

  • Hi Josel,

    I still suspect there is some issue with your desktop app concerning parsing as the outputs seen in the visualizer seem to be as expected. The environment cannot possibly introduce some delta between 2 different data reception applications. Can you try sending a larger packet simulating that of the road? You can follow a flow as follows:

    Capture data from road using visualizer (working case) -> Resend the data captured out of device using visualizer for 1 frame fully -> Collect on your custom application -> Compare the results.

    This will easily pinpoint to the cause of the issue, and you should be able to resolve it.

    Regards,

    Kaushik