`mokucli list` Command Fails with KeyError (b'txtver') on Moku:Pro

Support & Troubleshooting
1

Moku model:
Moku:Pro
Operating system:
Windows 11 Enterprise
23H2
22631.2861
Software version:
Moku: 3.3.2.2(build 3251), firmware: 601.0
mokucli 2.3.0
Bug or support request description:
When running the command mokucli list, the following error is displayed:

Name                 Serial  HW     FW     IP
---------------------------------------------------------------
Task exception was never retrieved
future: <Task finished name='Task-4' coro=<Finder._display_moku_info() done, defined at mokucli\helpers\finder.py:91> exception=KeyError(b'txtver')>
Traceback (most recent call last):
  File "mokucli\helpers\finder.py", line 96, in _display_moku_info
KeyError: b'txtver'

Troubleshooting Steps Taken:

  1. reboot system,
  2. reboot moku
  3. reinstall mokucli.
    Additional Observations:
  • My Moku:Pro is connected via an Ethernet cable, and the Moku app is unable to detect the instrument.
  • When connected via USB, the Moku app can detect the instrument, but mokucli list still results in the same error.
  • The Python API functions correctly.
  • Last night, mokucli list worked successfully and provided the IP address. I ran measurements overnight via the Python API without issues.
  • This morning, mokucli list stopped working, but the Python API still connects properly.
  • I also tested communication with my Moku:Pro using an iPad, and it works as expected. The instrument itself appears to be functioning normally.
2

Hi @xiangyuwei,

This is quite unusual that you are seeing this error, do you know if you have any other Mokus on the same network as you? Especially if they are older units or are on an older firmware?

If you can discover the Moku on your iPad app then maybe you can use that to find your IP address in the meantime, while we debug this. To do this you can long-press on the Moku until the pop up shows your Moku’s details, including the IP address.

Some reasons for why your Windows App cannot discover your Moku may be because of company/enterprise network and discovery restrictions which can block the network connection between your computer and Moku that may not be present for your iPad or via USB connection, or if it has accidentally connected to a different or sub-network?

Let me know how you go,
Indira