-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the API in Python #38
Comments
I am also interested in this. |
Hello! For the question from July of last year: this method of accessing the instrument is not supported on current instrument control software versions, sorry. This presumably would include all Exploris versions. Older Exactive and Q-Exactive versions may be supported; please leave a comment here indicating if that would be useful to know, and I will try to find out. For the more recent question, I don't have experience with this. Can you build a C# app to access the instrument and handle events, and then connect your python code to the C# app (and the event handler)? |
Hi, Yes, what you have suggested works just fine. I was hoping to handle the events directly in python, but I guess they are not exposed. |
I'm trying to use the API in my Python program via pywin32 package that allows accessing COM objects and calling their methods.
Similarly to "the old way" described in the Power Point presentation:
in Python I instantiate the COM object:
o = win32.client.Dispatch('Thermo Exactive.API_Clr2_32_V1')
and this works fine. However, when I try to get an InstrumentAccess object by calling Get method of the COM object, I get the following error:
Unable to load an assembly set being able to write RAW files
I've tested this in both 32-bit and 64-bit builds of Python. Moreover, a C# program implementing this "old way" of accessing the API throws the same error. The new way of accessing the API via loading the .NET assembly works fine.
Do I miss anything? Maybe, "the old way" does not work anymore?
The text was updated successfully, but these errors were encountered: