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: Change vitalsign demo to support standalone mode

Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST, , IWR6843

Hello

we are currently using the vitalsign lab with the MMWAVEICBOOST card. We would like to see how we can use this lab in standalone mode.

I'm looking at the forum, but I'm not sure if I simply need to change the main MSS class or cli class in the lab to support stand-alone.

Do you have any examples or clues to guide me in making this change?

thanks 

  • Hi,

    You will need the MMWAVEICBOOST only if want to debug with CCS. For running the demo standalone, MMWAVEICBOOST  is not needed.

    You can flash the vital signs image to IWR6843ISK and boot in functional mode and send the cfg through the industrial visualizer.

    For running only the demo, IWR6843ISK is sufficient.

    Regards

  • Hi ,

    thanks for your answer,

    I made some test with the IWR6843ISK in standalone mode.

    I put the pin in standalone mode. I flashed the card with the vitalsign lab and after send standard commands.
    When i send commands to the IWR6843isk, i d'ont have the right answer and it seems that the firmware doesn't understand commands.

    Did i miss something in the communication configuration (i keep same baudrate) ?

    In addition, i find some thread that says : vital sign gui only support UART COM ports exposed by the XDS110 UART controller. (On my side, i use pyserial on python to connect to IWR6843isk and it works fine with the ICBOOST) 

    thanks

  • Hi

    1. Have you changed the boot mode after flashing. Once you have flashed the image successfully, you need to change the boot mode to functional mode and power on the module

    2.You need to connect to the below COM ports when using 6843ISK in standalone mode

    Regards

  • Hi ,

    thanks for you help, 

    After the flashing process, i reboot the card in functional mode.
    I can send command to the radar sensor but it doesn"t answer, or sometimes it send me some bad answer ( answer from radar to my command =>  dfeDataOutputMode 1 : dfeDatDebug: Init Calibration Status = 0x11e / channelCfg 15 3 0 : channeMSS Exception: ../mss/mss_main.c, line 635. /....)


    in addition : i talk about VitalSign without tracking. 

    thanks 

  • Hi,

    1. Before you run the vital signs demo, can you try to run the Out of box demo from the SDK or radar tool box.

    2. Are you using the industrial visualizer from radar tool box? You can use the visualizer to send the cfg from the below location

    radar_toolbox_2_00_00_02\tools\visualizers\Applications_Visualizer\Industrial_Visualizer

    Below are the switch settings for IWR6843ISK

    For Flashing
    S.1 ON
    S.2 OFF
    S.3 ON
    S.4 ON
    S.5 OFF
    S.6 NA

    For Functional
    S.1 OFF
    S.2 OFF
    S.3 ON
    S.4 ON
    S.5 OFF
    S.6 NA


    For UART on the ISKEVM (standalone)
    S.5 is OFF

    For UART on the MMWAVEICBOOST (using MMWAVEICBOOST )
    S.5 is ON

    Regards,

  • Hi,

    thanks for your help.

    I have configured the switch settings as you share (it's the configuration that i've done for my previous test). 
    I run the out of the box demo in standalone and it works with mmw_visualizer.

    After, i flash the IWR6843 in standalone with the vital sign (without tracking) and i try the old GUI, the Industrial_Visualizer (it's only possible to use vital signs with tracking) and our own backend services that work fine with ICBOOST.

    None of them works

    I see a lot of difference between the architecture of vital sign with and without tracking and in particular the mode (isolation with tracking and cooperative without). 

    did you have any idea about the difference that explain the problem (packaging, mode, software architecture) ?

    thanks

  • HI Romain,

    Abhishek is on holiday this week. He will get back to you by next week.

    Best,

    Nate

  • Hi Nate,

    Thanks for your feedback,

    Regards,

    Romain

  • Hi,

    From algorithm perspective, there is not much difference in the way vitals are calculated. In the demo with tracking, tracking information is sent to the vitals chain. Vitals chain takes the tracker centroid as the input and locates the person in the azimuth and elevation and then proceeds to compute vitals. The person needs to be stationary for 30s for correct vitals to be obtained. 

    In the demo where tracking is not used, it is assumed that person is sitting infront of the sensor at 2m and vitals operate with this consideration. If the person moves or not present at exactly 2m, incorrect vitals are obtained

    Regards

  • Hi ,

    I finally find the problem.

    On the client side, i use pyserial library and i reset buffer before launching commands. It seems that the reset blocks the radar. I removed this reset and it works really fine.

    thanks for your help,

    Regards