• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 338 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.

IWR6843: SYNC Error by using Philip Hue with mmWave Lab 15 people count

Weiyi Zhang
Prodigy 20 points
Part Number: IWR6843

Hello, 

I extend the Matlab code of people Count with switching colours of Philip Hue. If there is only one Person to track the Connection to the Philip Hue works perfectly fine, but if there are more People to be tracked, on the Matlab command window appears error message:

Lost sync at fame 38102(823), Reason: SNR value is wrong, 31631 Bytes in Rx Buffer

Found sync at frame 38111(824), after 53.2ms.

and the Philip Hue is changing in different Colours unexpectedly while the lost Synchronisation.

                                

  • 0
    TI__Mastermind 28055 points

    Hi Weiyi,

    The gui loses sync at this point because it is getting negative SNR values, which the demo does not recieve, meaning there is a parsing error.  This is almost always caused because the loop in the gui takes too long.  Can you benchmark the loop run time with and without the addition of using the Hue?

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 20 points

    Hello Justin,

    I have tried out the People count lab without the GUI, but there was still SYNC error, when there were more than one person tracked.

    Best regards,

    Weiyi

  • 0 in reply to Weiyi Zhang
    TI__Mastermind 28055 points

    Hi Weiyi,

    Can you benchmark the runtime of the GUI loop on your machine? Typically we expect a few sync errors when trying to send as much data across UART as is sent in the lab. It is also possible that the loop is occasionally running over on your machine, which could also cause the sync error. 

    You can also try lowering the framerate of the demo.  Change the following lines:

    frameCfg 0 1 128 0 100 1 0 - 100 ms frame period

    trackingCfg 1 2 250 20 52 82 100 90 - tracker expecting 100 ms between frames

    Regards,

    Justin