The Pulsar Engineering Community Board

Not at the moment unfortunately. They also changed the way to access camera data and that's why you are getting the error with the UserDefinedValues thing. I found an example in the SDK on how to write data to BFS cameras and I evaluate it's about ~1 day job. Problem is I have plenty of things that ...

I was able to come up with a quickfix. It should be working with BFS cameras now except you won't be able to save wavelength calibration settings. Note that I did not have a BFS-31S4M camera so I made the fix using another BFS model. pointgrey.zip Tell me if it works! It would also be worth to send ...

Quick update : I was able to find a BFS camera and reproduce the bug. That will ease up the correction process!

You can also try with more directive settings like:

wavelength range: 500 - 700 nm
span: 100-120 nm
distortion: 0-10 nm

that should force the model to the proper initial settings

It's indeed not ideal but you should be able to perform a linear model at least.

What happens when you do that ? Can you send a screenshot ?

Hello Dave,

Up to now I have tested only with NE-2 lamp. Would you be kind enough to send a screenshot on what does the HG-2 lamp spectrum looks like ?

Yes that's correct -- you can see the bare fiber as a disk source with a cone whose half-angle is given by the NA of the fiber. So a lens in front of the fiber is sufficient to create a collimated beam.

Hi soleg, I'm running a bit out of time these days so I can give you a procedure that involves no coding to already dig a bit without having to wait for me. It's possible that the nodes names changed during the transition from BFLY series to BFS. I don't know if other people are using the BFS as wel...

They also look alot like the ScienceSurplus spectrometer that I tested a few years ago. nb to save extra $$$ in your design, replace directly the rotation mount with the slit by a regular mount with the fiber connector -- the fiber core diameter will act as a slit (use a 20-50 microns core depending...

I confirm that it is coming from a portion of the code that should never trigger (fail safe). For some reason, one of the mandatory parameter of the camera (exposure, gain, ROI...) cannot be accessed. Before we go further into the debug, I will ask you to perform a few operations and tell me if it's...