Persistent connection issues with Moku:Go on Windows App (USB-C & Wi-Fi)

Dear Liquid Instruments Support Team,

I am writing to seek assistance with a persistent connection issue I am experiencing with my Moku:Go when using the Windows desktop app.

Here is my device information for your reference:

  • Model: Moku:Go (M2)

  • Serial number: 004744

  • Hardware version: 4.0

  • MokuOS: 4.1.2

  • Firmware version: 635.0

Issue Description: I am having trouble connecting to the device on Windows. The issue occurs consistently whether I connect via USB-C or Wi-Fi. The device rarely shows up in the app, and it takes a long time to appear if it does at all.

When it occasionally appears and I click to connect, one of the following two things happens:

  1. The connection progress bar flashes briefly, and then the connection drops entirely.

  2. It manages to enter the instrument selection menu. However, if I launch the Oscilloscope, I cannot see any signal whatsoever (not even the noise floor), which leads me to suspect that a stable data connection was never actually established.

Troubleshooting Steps I Have Taken: To isolate the root cause, I have performed the following tests:

  • Hardware Check: I connected the device to an iPad via the Moku Wi-Fi network, and everything works perfectly. This seems to rule out any hardware defects with the Moku:Go itself.

  • Official Guide Followed: I followed the steps in your article Troubleshooting USB connection on Windows App.

    • The network adapter shows up normally in Device Manager.

    • IPv6 is activated.

    • I ran the command netsh interface ipv6 show neighbors | findstr "70-69-79", and it successfully found the Moku’s IPv6 address (fe80::...:7269:79ff:feb9:4a22).

    • However, when I try to use the “Manual Connection” feature in the Moku desktop app with this IPv6 address, it still fails to establish a connection.

  • Cross-testing: I have tested this exact setup on two different Windows computers, and the results are identical on both. Both the Moku firmware and the Windows app are updated to the latest versions.

Given that the iPad connection works perfectly but two different Windows PCs fail to connect despite the IPv6 address being pingable/visible, it seems to be an issue specific to the Windows App’s ability to establish or hold the connection.

Could you please advise on what further steps I can take to resolve this?

Thank you for your time and support.

Best regards,

Xiangyu Wei

Hello @xiangyuwei ,

Thank you for reaching out and very sorry to hear you are dealing with this issue. When did you start experiencing this issue; was it after a firmware update? If you connect over ethernet do you experience the same issues? Have you been able to reliably connect with APIs? Looking forward to hearing from you!

-Dylan