thorlabs_tcube and MSYS2/CLANG64

jfniedermeyer

Hello all,

We're trying to update to the stable channel of ARTIQ 8 on a (IT security policy enforced) Windows machine. Since Conda isn't playing nicely with the stable build and because it's officially deprecated, we're moving over to MSYS2/CLANG64. We're having issues getting NDSPs to work (a related post will ask for help with artiq_influx_generic).

I've used pacman -S to install thorlabs_tcube as noted in the documentation. There seem to be some bugs moving from the Conda managed beta branch to the MSYS2 ecosystem. The package seems to need python-pyserial to be installed (otherwise the error is asyncserial has no attribute AsyncSerial, but that's straightforward to fix. After this is installed, when I try and start the connection through artiq_ctlmgr using the same device-db and commands that worked in the beta branch, the Thorlabs devices keep disconnecting. When ctlmgr does an RPC ping to the Thorlabs devices (which it seems to do periodically), there is first an OSError of [WinError 6] The handle is invalid followed by an asyncio error that Cancelling an overlapped future failed.

Has anyone been able to get thorlabs_tcube to work with MSYS2 yet? If so, what did you have to do?

Thanks in advance!
Justin

fsagbuya

jfniedermeyer
Can you try to ping using sipyco_rpctool? What result do you get? Also, could you share the full or a more detailed error log?

Edit: This issue might be related regarding a bug in Python 3.10 on Windows. ARTIQ-8 is shipped with Python 3.11 by default, but could you also check which Python version you are using in your MSYS2?

sb10q

Missing pyserial should be fixed by https://git.m-labs.hk/M-Labs/artiq-extrapkg/commit/b12ca4b92888068d62ced174869cb014b6a365c0

jfniedermeyer

fsagbuya Thanks for the replies. python -V says MSYS2 with ARTIQ is on 3.11.9, so that isn't the solution unfortunately.

sipyco_rpctool 127.0.0.1 4462 call ping gives a RuntimeError in the thorlabs_tcube driver with the following traceback:

WARNING<12>:thorlabs_tcube.driver:ping failed
Traceback (most recent call last):
  File "C:/msys64/clang64/lib/python3.11/site-packages/thorlabs_tcube/driver.py", line 277, in ping
    await self.hardware_request_information()
  File "C:/msys64/clang64/lib/python3.11/site-packages/thorlabs_tcube/driver.py", line 269, in hardware_request_information
    return await self.send_request(MGMSG.HW_REQ_INFO,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:/msys64/clang64/lib/python3.11/site-packages/thorlabs_tcube/driver.py", line 212, in send_request
    await self.send(Message(msgreq_id, param1, param2, data=data))
  File "C:/msys64/clang64/lib/python3.11/site-packages/thorlabs_tcube/driver.py", line 193, in send
    await self.port.write(message.pack())
RuntimeError: Task <Task pending name='Task-58' coro=<Server._handle_connection_cr() running at C:/msys64/clang64/lib/python3.11/site-packages/sipyco/pc_rpc.py:624>
 cb=[AsyncioServer._client_done()]> got Future <_OverlappedFuture pending> attached to a different loop

It may be worth mentioning that just running aqctl_thorlabs_tcube -p PORT --bind HOST -P device -d COMPORT does not error out. The periodic pings from artiq_ctlmgr seem to be causing the errors. Comparing the drivers between the beta version that works, ARTIQ v8.8674+dcf1bba.beta, and the stable I'm on, ARTIQ v8.8934+85c03ad, it looks like a lot of asyncio changes were made (perhaps due to changes between Python 3.11.0 and Python 3.11.9?). the sipyco_rpctool HOST PORT call ping does work and returns True. I'm unfortunately out of my depth trying to debug asyncio at this level. Any additional advice or help would be greatly appreciated.

fsagbuya

jfniedermeyer
The asyncio errors should now be fixed by: https://github.com/m-labs/artiq/commit/333623e24bdec00783bc89c1e8b6b49a74bc9e1c

You can update msys2 by following the manual section here.

After updating, you might also need to run:

pacman -S mingw-w64-clang-x86_64-python-asyncserial