• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 32 subscribers
  • Views 602 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR6843AOP: Vital signs lab – MSS expection in mss_main.c, line 635

Francois Charlot
Mastermind 28137 points
Part Number: IWR6843AOP
Other Parts Discussed in Thread: MMWAVEICBOOST, , AWR6843AOP

Hello,

My customer use IWR6843AOP on their customer board. The mmWave SDK 3.5 out-of-box demo works fine on it. They want to run the "68xx Vital Signs" from the Industrial SDK 4.12.0. Flashing works fine. Then sending the CLI commands through the terminal works fine (each command is acknowledged with a "Done") until sensorStart is sent, then the radar responds with an "MSS Exception: ../mss/mss_main.c, line 635."

The CLI commands and acknowledgments go through the CFG port with a terminal application, and the DATA (mss_logger, 921.600 b/s) port is monitored with another terminal application. No data come out from the latter at any time with the vital signs lab. Customer has followed this post and that one ("calibDcRangeSig -1 0 -5 8 256" is used).

Could you please point at what we are missing there?

Thank you.


Best regards,
François.

  • 0
    TI__Genius 10730 points

    Hi Francois,

    Is the customer working with the IWR6843AOP in standalone mode or with an mmwaveicboost attached?

    Thank you,

    Angie

  • 0 in reply to Angie Mitchell
    Prodigy 40 points

    Hi Angie, 

    Thnak you for you reply. 

    I'm working with the IWR6843AOP in standalone mode. i've tried the same project using IWR6843AOPEVM with the same steps described and in standalone mode. It works just fine. should I try it with an mmwaveicboost attached ? how could that make a difference ? 

  • 0 in reply to yasmine hanafi
    TI__Genius 10730 points

    Hi,

    Yes, for this lab the mmwaveicboost is needed as it depends on the XDS110 UART connection on the mmwaveicboost.

    Thanks,

    Angie

  • 0 in reply to Angie Mitchell
    Prodigy 40 points

    Hello Angie,

    I have tested the Lab using an external XDS110 UART connection and it's always the same problem as shown in the figure :  

    Doesn't this mean that the UART connection is working fine? 

    Thank you.

    Yasmine.

  • 0 in reply to Angie Mitchell
    TI__Mastermind 28137 points

    Hello Angie,

    At some time, customers need to drop the mmwaveicboost board... Besides the CFG and DATA ports which are available on the customer's board, what else is needed so that the MSS software does not throw this exception?

    I looked at the mss_main.c code but that does not help understanding what the error source could be... At line 585, the return value of MMWave_open() is checked for an error, and apparently none is detected there. It is only when the value of some fields of gMmwMssMCB.cfg.openCfg are verified that the assertion is raised at line 635. Connecting that to serial ports is not obvious...


    Best regards,
    François.

  • +1 in reply to Francois Charlot
    TI__Genius 10730 points

    Hi Francois and Yasmine,

    Thank you for reaching out on e2e. At this time our offering on the industrial toolbox requires an mmwaveicboost. 

    However, our Vital Signs with People Tracking lab is on the industrial toolbox as well and this lab uses an improved vital signs algorithm utilizing all the the transmitters and receivers and using BPM-MIMO mode. This lab also supports standalone mode for the AWR6843AOP. 

    To use this lab with fixed distance the “VSRangeIdxCfg 0 21” line in the configuration sets whether or not the tracker is used to determine the location of the person in the scene. By setting the first input to “1” the algorithm will then look for the person at a fixed location. A cli command of VSRangeIdxCfg 1 21 would enable fixed distance measurements at range bin 21. If you stick with the default range resolution that would be ~1.5m. This range bin can be modified based on where you expect the person to be in the scene.

    There is a bug in the GUI when used fixed range mode which can be fixed by modifying line 253 of the file parseTLVs.py to read “vitalsOutput ['id'] = vitalsData[0] – 1” instead of “vitalsOutput ['id'] = vitalsData[0]”.

    Thanks again,

    Angie

  • 0 in reply to Angie Mitchell
    Prodigy 40 points

    Hi Angie,

    Thank you for your reply. 

    I've tried Vital Signs with People Tracking lab with my custom board and it is working. 

    I don't understand why the lab "Vital Signs " needs the mmwaveicboost when it is working perfectly with the IWR6843AOPEVM in standalone mode.

    Is there anything else that should be modified in the Lab in order to work with my custom board in standalonne mode?

    Best Regards,

    Yasmine.

     

  • 0 in reply to yasmine hanafi
    TI__Mastermind 28137 points

    Hi Yasmine,

    Thank you, that's good news!

    As Angie said, the vital signs with people tracking lab uses an improved detection algorithm and works in standalone mode, with no mmwaveicboot board. Since it also operates in a fixed distance configuration, we suggest not to spend more time on the former vital signs lab.


    Best regards,
    François.

  • 0 in reply to Francois Charlot
    Prodigy 40 points

    Thank you for your help. 

    Best regards,

    Yasmine.