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: People Counting GUI can not select/input cfg.

Part Number: IWR6843ISK

Hi TI,
I have the weirdest error for people counting today. I tried to run people counting GUI using anaconda (python version 3.9), but when I tried to select CFG, the button is refused to do anything.

I tried to run python outside anaconda, even install python ver 3.6, and run from gui_main.exe and fallDetection_main.exe, but all are futile.

Some with command error of "invalid literal for int() with base 10: '4_10_'
No cfg file selected!"

Do you have any clue why it's happened? And how to solve it.

Thank You very much.

Sincerely Yours,

Wolfgang 

PS: Usually it run smoothly. Just happened today

  • Hi,

    Thanks for reaching out and sorry for the delay in responses due to the holidays. 

    So we have just released the mmwave industrial toolbox 4.10 and apparently the new name length is throwing off one of the functions in the people counting gui. 

    There are two methods to fix this.

    One is renaming your industrial toolbox to "mmwave_industrial_toolbox_4_100" instead of "mmwave_industrial_toolbox_4_10_0". This will allow everything to work including the gui.exe versions. 

    The other method is to go into the gui_main.py and make this code change. Reassign numstr = name[26:] instead of name[26:31]. 

    Note that none of the exe gui will work with this method and only works with running from the source code. 

    We are working to get this fixed quickly and hopefully this helps fix the issue. 

    Thanks,

    Alex Chan

  • Thanks Chan.

    This is solved all this problem, hahaha. I choose the first method, because easier and I want to play with new 3d people counting + vital sign, which yet to have the source code.

    Thank you 

    Regards,

    Wolfgang

  • Hello,

    I had the same problem. I used the second method and can confirm it also solve the problem.

    Best regards,

    Maciek

  • Hi Maciek,

    We have updated the toolbox with version 4.10.1 with the fixes so that these workarounds are no longer needed. Please download the latest one. 

    Thank you for your response and input. 

    Thanks,

    Alex Chan