OceanFX Showing as FlameX with incorrect minimum integration time #275
Replies: 1 comment 4 replies
-
Resolved the issue, by using the FLAMEX spectrometer source file in libseabreeze and updating minimum integration time, as that's what the OCEANFX shows as by default. Kept receiving timeout errors when adding the OCEANFX specifications to devices.py and trying to use pyseabreeze directly. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Im hoping to get some advice on how best to get an OceanFX spectrometer to go below 1000uS integration time, all functionality still working, windows with version 2.10.0. I have tried adding OceanFX with USB connection to the devices.py file but with no success.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions