-
Notifications
You must be signed in to change notification settings - Fork 10
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
Wavelength change seems not to change power #13
Comments
Thank you for pointing out this bug. On need to add the unit to the sting send to the instrument. I don't have a powermeter on hand to test. Could you test it ? |
I tested it but the problem is still there. |
The beamdiameter also won't change but changing the average count works fine for me. |
I initially tought that Thorlabs requires the unit when the command is send. The commit d77ad7d add an automatic test for the wavelength. It works on my device. Now the command : |
I am testing it on the PM101. The commands in the manual are the same on first sight. I have a sensor with wavelength range of 800-1700 nm but power_meter.sense.correction.wavelength = 1310 f.e. doesn't work. |
OK on the Thorlabs PM100D everything works fine. The only thing that is not clear for me is how to change the configuration from CURR to POW. |
This is a different question. I think that : |
According to the datasheet, it should work with the PM101. |
The result is 800. I already contacted the Thorlabs tech support. Let's see what they say about it. |
I now figured out what caused the problem. In the wavelength class it says: Interestingly on the PM100D its working perfectly fine with and without the unit whereas on the PM101 it only works without the unit. Therefore I think the unit should be removed on every setter command. That is also what the Throlabs technical support told me. |
When I use powermeter.sense.correction.wavelength = 1550 or 800 the obtained optical power from powermeter.read does not change while it does change on the powermeter software from thorlabs. Is this a bug? powermeter.sense.correction.max_wavelength works fine for example.
The text was updated successfully, but these errors were encountered: