-
current problemWhen the pyseabreeze backend is used, it gives an error 'usb.core.USBTimeoutError: [Errno 10060] Operation timed out' when the integration time is set beyond 1100 ms. The maximum integration time allowed for the HDX spectrometer is 10000 ms, and for the NIRQUEST512 spectrometer is 1600000 ms. When switching to the cseabreeze backend, it doesn't give time out errors. But the cseabreeze backend doesn't support the HDX model. It's good to have an integration time longer than 1 s given that the spectrometers can operate at a much longer integration time. Is there anything I can do to extend the integration time without triggering timeout errors using the pyseabreeze backend? Is it possible to use both pyseabreeze and cseabreeze backends at the same time so that both spectrometers can work properly? Many thanks! spectrometer and system information
To reproduce the problemimport seabreeze
seabreeze.use('pyseabreeze') # pyseabreeze backend supports both HDX and NIRQUEST
import seabreeze.spectrometers as oceanoptics
spectrometers = oceanoptics.list_devices()
print(spectrometers)
# connect to VIS spectrometer, change serial number accordingly
spectrometer_VIS = oceanoptics.Spectrometer.from_serial_number("HDX00902")
int_time_min, int_time_max = spectrometer_VIS.integration_time_micros_limits
print(int_time_min, int_time_max) # 1000 10000000
int_time = 50000 # 50 ms
spectrometer_VIS.integration_time_micros(int_time)
spectrometer_VIS.intensities()
int_time = 1100000 # 1100 ms
spectrometer_VIS.integration_time_micros(int_time)
spectrometer_VIS.intensities()
print("1100 ms") # ERROR afterwards
int_time = 50000 # 50 ms
spectrometer_VIS.integration_time_micros(int_time)
spectrometer_VIS.intensities()
print("50 ms") Error: usb.core.USBTimeoutError: [Errno 10060] Operation timed out Additional Info
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @RanTao97 can you try installing Cheers, |
Beta Was this translation helpful? Give feedback.
Hi @RanTao97
can you try installing
seabreeze==2.5.0
and report back? There was a change in how the maximum integration time is handled in version2.6.0
and it might have introduced this error.Cheers,
Andreas