Closed pikestefan closed 2 years ago
Hi @pikestefan.
Your example illustrates that your issue has nothing to do with qudi itself. Apparently your pyvisa
package installation or the used system visa binary installation is somehow broken.
I bet you can reproduce the same problem just running the code in the same Python environment (without qudi).
Hi @Neverhorst, Do you mean I should get the same error when trying to use the resource manager within the qudi environment? I gave it a quick try in the anaconda prompt, but nothing looks amiss there.
Ok, that's very strange. If you are absolutely sure you are using the same conda environment for both tests I'm at a loss.
qudi does not alter pyvisa
in any way. The only thing that could have an effect are paths that are inserted at the beginning of sys.path
during qudi startup. But I do not suspect this to break visa
.
I mean the pyvisa
package is used in most qudi hardware modules so far...
A last resort that comes to my mind is to re-install the system VISA library (e.g. from NI, Keysight, etc.) and the qudi conda environment. Just in case something got mixed up there. (would not be the first time for conda and binary bindings).
Thanks a lot for your reply! It turns out the problem was indeed the VISA library itself: after uninstalling and reinstalling the distribution, the error stopped popping up.
Glad everything worked out.
What is affected by this bug?
Hello, I have forked qudi in July 2020. I have found an issue when loading the microwave.mw_source_srssg.MicrowaveSRSSG class.
When does this occur?
When I load the hardware module, I get the error pasted at the end of this message. With a bit of debugging I found out that the issue occurs whenever the visa.ResourceManager() does any type of query (e.g. listing resources or connecting to a device).
How do we replicate the issue?
I managed to reproduce the error with this fake hardware module:
Error message