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.

IWR6843ISK: UART Communication protocol for config and data flux in "Long Range People Detection" lab

Part Number: IWR6843ISK

Dear Sirs,

We have started to work with IWR6843ISK to realize a device based on the “long range people detection” lab. We have successfully worked with the visualizer which displays the detection and tracked object data received via UART. With the same tool we have configured the board using the cfg files. At this point it could be interesting to use the IWR6843ISK board like a sensor controlled via UART in one of our device, but for this goal it is important a detailed comprehension of the UART protocol used to configure the radar and the protocol applied to data flux containing information from radar.

Do you have some document describing the protocol to configure the board IWR6843ISK and to recover data of the informations read by the sensor?

regards

Andrea Colombo

  • Hi Andrea,

    There are two parts to this, which conveniently align with the two com ports that you will see when you connect the device.

    The configuration is typically done via CLI commands sent over the Application UART port. There are some commands that may be specific to this demo (you can check the user guide and provided .cfg's to confirm) but the vast majority of them will be documented in the mmWave SDK user's guide, section "Configuration (.cfg) File Format".

    The application UART data output comes out over the second UART port, and this format can vary depending on the specific demo/lab. For this demo, it is described in the user guide for the lab (68xx_long_range_people_det_user_guide) under the section "Data Formats".

    If you wish to change these formats, I would recommend that you look at how the CLI and UART output are implemented in the project and make modifications as you see fit. Let me know if you have any further questions.

    Best Regards,
    Alec


  • Thanks Alec,
    I have found required informations. I have another question. Continuing our work on “long range people” lab, We have tried to configure the IWR6843ISK board with configuration file (people_detection_and_tracking_100m_2D_advanced.cfg) for “beam forming” and the gui application replied with an error in the parameters as you can see in the attached picture.
    Can you please help me to understand why there is this error mesage?

    regards

    Andrea Colombo

  • Hi Andrea,

    Are you able to open the matlab GUI to see where this issue is occuring? And just to confirm, the application, config, and gui should all be unmodified here, correct?

    Best Regards,
    Alec

  • Andrea,

    After some internal discussion, someone on the team pointed out the following thread regarding a similar issue, could you go through it and the feedback provided and let me know if it resolves your issue?

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/989593/iwr6843isk-100m-cfg-file-in-long-range-people-detection-lab

    Best Regards,
    Alec

  • HI Alec,
    You are right, the suggested thread seems to speak exactly of the same problem, but unfortunately, like the guy requiring support in that thread, I haven't matlab compiler and I can’t test suggested modifications. Another thing to verify is also that in the suggested thread seemed that the problem should be fixed in the version 4.6.0, but I’m working with 4.7.0 version and the problem is still present.
    Can you please supply a fixed version of the file "tm_visualizer.exe" that is the visualizer suggested in the “long_range_people_detection” lab for all configuration modes of the radar?
    Thanks for your help.
    Best Regards,

    Andrea

  • Hi Andrea,

    I just checked and this issue is expected to be resolved in the near future (my apologies that it wasn't fixed previously). I cannot provide this type of file over e2e, but there are a few options for you in the meantime. You could try to leverage the Matlab trial version to do a one-time rebuild of the exe, you could use the 50m cfg temporarily, or you can experiment with your own gui in your preferred environment. 

    Best Regards,
    Alec