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.

CCS/AWR1642BOOST: AWR1642BOOST

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH, AWR1642

Tool/software: Code Composer Studio

Dear reader,

I am trying to implement the short range radar code and driver vital signs from resource explorer in ccs.

I downloaded the PC GUI for both cases.

In the first one the GUI comes up but nothing happens, in the notes there is something about binarys, downloading them and flashing them on the radar. Where are these files located? And is that why it isn't working?Moreover does this show the usage of 80m and 20m together?

In the second case when i try to play the program i get the missing Qt5Gui.dll error. I tried puting the file in the same directory as the program and in system but it didn't work. How can i fix this?

Also are the codes the one used in the program or something else?

Kind regards,

Nilo

  • Hello Nilo,

    Have you referred to the "Developer's guide" that comes as a part of the SRR demo in TI resource explorer? That lists down all the prerequisites required to make it work. Here is the link to the same.

    Regards,

    Ishita

  • Hello Ishita,

    Yes, at least i tried to. It's likely i've missed something but none that i know of.

    Regards,

    Nilo

  • Hello Nilo,

    First, you need to flash the binary file to AWR device using Uniflash which is available under prebuilt_binaries.

    Follow the user guide for the flashing instruction.

    In case of SRR: AWR1642 is configured to be a multi-mode radar, meaning that, while it tracks objects at 80m, it can also generate a rich point cloud of objects at 20m, so that both objects at a distance and smaller obstacles close-by can be detected.

     

    Regards,

    Jitendra

  • Dear Jitendra,

    Thank you that helped.

    One of them works now. 

    For the other one (human vital sign). Nothing happens when i use the gui.In other words the gui comes up but detects nothing. What am i doing wrong?

    Also what is the 120 m code for then?

    And can i implement the human vital sign with TSWR and EVM?

    Kind regards,

    Nilo

  • Hello Nilo,

    Please make sure that you use the same HW and the prebuilt binary for Human Vital sign demo. Ideally default binary provided in the labs should work without any problem.

    I assume you are refering to SRR demo for 120m code. You can enable SRR-120m feature by un-commenting 'SRR_RANGE_120m' macro in srr_config_consts.h file and recompile the application.

     

    TSWR: you meant of TSW1400 for ADC data capture?? You can capture raw ADC data on PC using TSW1400/DCA1000 +EVM but for processing and get the vital sign info you need to implement your own processing code/script.

     

    Regards,

    JG

  • Thank you for your answer.

    I am using the binary file locted in C:\ti\mmwave_automotive_toolbox_3_1_0\labs\incabinsensing\driver_vital_signs\vitalSigns_target\pre-built-Binaries\xwr16xx_vitalSignsDemo_lab.bin

    Is that the right one? I don't seem to find another one.

    I treid to play the other method of appling vital signal demo using the codes and ccs but i got a lot of errors. I've read that i should be using mmWave SDK 1.1.0.2, but i can't seem to find the file to download it. I have the newer version.

    Right, yes. Thank you. When i do that does the same gui only works in 120 m range? or should i only run that code?

    I see, would that be hard to implement? Any suggestion on how i should go about implementing it in mmWave studio?

    Kind regards,

    Nilo

  • Hello Nilo,

    Here your queries are mixed for vital sign and SRR labs. Both of lab applications required different image and GUI to work.

    For Vital Sign GUI: make sure that you have followed the instructions given in DriverVitalSigns_GettingStartedGuide.pdf  (step 3: install Visual Studio Runtime )

    For SRR: 120m, make the code change as mentioned in last reply. And to recompile it with new SDK version, refer this e2e thread-

    https://e2e.ti.com/support/sensors/f/1023/p/938511/3466351#3466351

     

    To run with mmWave Studio, you need to first get all the configuration handy then same you can configure using Studio GUI to achieve the same behaviors.

    Regards,

    Jitendra

  • Hello Jitendra,

    Thanks again for your reply.

    Yes i know, the other short range radar worked. Now i'm attempting to make the human virtual signs working.

    I'm follwing it but i'm not sure what i'm missing.

    Yes the visual studio runtime is installed and i repared and restarted the computer but it still not working. What could be the reason?

    There are of course other microsaft visual C ++ redestributable installed.

    Okay, thank you.

    Kind regards,

    Nilo

  • Is this program only for version one?

    Mine is version 2, is that why it's not working?

  • Hello Nilo,

    Sorry for the delayed response, it was a long holiday here.

    Let me confirm few points here

    1. Which version of Vital Sign you are using? Version 2.0.0 is the latest one.

    2. Above version will work only with AWR1642 ES2.0 device only, so make sure that you have same ES version device with you.

    3. And hopefully you are using default pre-built binary file from the package for this experiment.

    Just to verify if application is running properly and sending the result data over UART- could you connect TeraTerm or any other serial terminal tool over both COM port instead of GUI*.exe

    Connect User Data COM port at 115200 baudrate and data COM port at 921600 baud rate. Then on User Data COM port with some Enter press you should see command prompt, which confirms that application is booted up.

    Now send CLI command from vitalSigns_host\profiles\xwr1642_profile_VitalSigns_20fps_Back.cfg file one by one over User Data COM port

    At 'sensorStart' CLI command, on the other COM port you should see some data (it may be unreadable ASCII values), it is object result data which GUI.exe parse and plot it.

    If you are able to see data coming over Data COM port with above experiment then device works file and now the problem is with GUI compatibility.

    At this point, try a different PC to run this GUI where you may need to install Visual Studio 2017 runtime vc_redist.x64.exe from the link provided in the user guide.

     Regards,

    JG

  • Hi,

    Thank you for your reply.

    Um, how can i tell which version i am using? in the notes it says it is version 1. And there is only one GUI available fro download, right?

    I tried using Tera Term, but when i plug it in and try to use it nothing happens and i don't really know how to make it work. Should it just show data with out me doing something?

    I know the radar is fine because i tried it with other programms.

    I tried another PC as well, that didn't work.

    Kind regards,

    Nilo

  • Hello Nilo,

    Vital sign demo is based on SDK 1.1 which required AWR1642 ES1.0, and looks like you have AWR1642 ES2.0 board which is why that demo doesn't work.

    https://e2e.ti.com/support/sensors/f/1023/t/699519

    Could you try this demo - https://dev.ti.com/tirex/explore/node?node=AA8pcBP.iyV9dp1jMD0Pbg__AocYeEd__LATEST

    Occupancy and Vital sign demo which is based on AWR1642 ES2.0??

    Regards,

    Jitendra