-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Timeout, or abort, needed for proper trigger support #146
Comments
Hi @drmcnelson, This will be a bit more involved. It's possible to change the I will implement the functionality for I'll update this issue when I start work on this. Cheers, |
Yes, I saw where it would go in the pyseabreeze code. An abort could be a useful alternative for some use cases. |
Note to self: It seems there's no easy hacky way to do this with the sync interface: https://libusb.sourceforge.io/api-1.0/libusb_io.html#sync |
Yes, it looks messy. The comment that they need to be called to handle events seems a little concerning. I have been using the device in triggered mode for clocked data acquisitions. So I'm getting along with out it for the moment. Thank you for looking into it. |
user space thread to implement a watchdog timer? (provided the overhead is small) But again, I don't want to cause you extra work. It has been working very well as is, for my clocked data acquisitions. At this point, I am pretty sure I would not change my code to use the timeout. |
spectrometer and system information
USB2000, etc - all models with external trigger capability
current problem
To adequately support triggered operation, the API to retrieve spectra, absolutely needs to have a timeout parameter, or at least a way to abort the intensities() call while it is waiting for a trigger.
The text was updated successfully, but these errors were encountered: