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.

LDC1101EVM: GUI can't connect to the EVM Board in Winodws 11(x64) system

Part Number: LDC1101EVM
Other Parts Discussed in Thread: LDC1101

Tool/software:

LDC1101EVM and it's GUI software how to work on Windows11 x64 system? 

EVM Board connected to NB, and we can see the "USB Serial Devices COM 8".

  

Then open the " Sensing Solutions EVM GUI-1.10.0",   it can catch the EVM board and connection OK. 

But, LDC1101EVM GUI can't connect to the EVM. 

How does the 1101 EVM work on Windows 11 (x64) ? 

Thanks you so much.

  • Hello Sophia,

    Thanks for considering to use Texas Instruments. You will need to match up the COM port drop down selection with what you are seeing in the device manager.  For me it was COM 11 and you might need to toggle the Active/sleep mode button prior to COM port selection.  This GUI is unfortunately kind of old and glitchy.  My screenshot is from my laptop which has Windows 11 (x64).

  • Dear Patrick:

    Good day. 

    Thanks for the replying.

    I have selected the COM 8, and the EVM board still can't catch by the GUI software.

    GUI is showing "NOT CONNECTED" in the bottom. 

    And then,  I try to use below path to reflash the EVM's driver, 

    C:\ti\Sensing Solutions EVM GUI-1.10.0\EVM Firmware\LDC1101

    the date of LDC1101's driver file is  2017/5/6

    should I use another driver file which is in "C:\Program Files (x86)\Texas Instruments\LDC1101 EVM GUI\Firmware"

    or , I need to change the setting of COM8's port ? 

     

    Thanks you so much.

  • Hey Sophia,

    The files you listed have the same dates on my machine when you account for the timezone difference.  As for the port settings, below are what I have.  Today when I tried loading up the GUI it actually was rather difficult and I imagine very similar to what you are experiencing.  I had to try selecting the COM port numerous times before it would stick.  I also tried toggling the Active/sleep mode button several times between selecting the port and even tried selecting the incorrect port, before I could select the correct port and the GUI magically started working. There could be a time component where something is getting setup in the background or perhaps some higher priority signal or process is preventing the program from getting the resources it needs.  At this point, I would suggest waiting a little after the hardware is plugged in and the GUI is open and then having some persistence with choosing the port. I understand this not desirable and I think our team should revise this GUI for greater user experience when we have the resources.