OceanFX Showing as FlameX with incorrect minimum integration time

[ThomasPleavin]

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?

[ThomasPleavin]

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.

[ap--]

Hi @ThomasPleavin

Great to hear that you found a workaround. OceanFX support was so far always covered by cseabreeze. And so it's great to hear that the PR worked for you. I'd like to merge it, but need to make sure that we don't introduce a bug. I provided a code snippet in #61. could you try and test it?

[ThomasPleavin]

Hi @ap--

Happy to test but cannot find code snippet?

[ap--]

Ah sorry, I provided the wrong link... https://github.com/ap--/python-seabreeze/pull/237#issuecomment-2618178888

[ThomasPleavin]

Thanks,

In that case, main problem resolved. On out end we have robustly tested functionality of the OceanFX spectrometer, and we able to use an auto-integrate function to accurately capture spectrums. We don't specifically use functionality that the OceanFX enables, mostly interested in the low minimum integration time. If you wanted me to test any specific functionality, I'm happy to do so