Experimental Physics and
Industrial Control System

tieman <[email protected]> · Fri, 20 Feb 2009 08:31:43 -0600

Mark,

However, there may be a quick solution to Brian's problem, since I suspect it is related to areaDetector?
...

It is related to AD and this "trick" is where I got burned to begin with

:) In my case (Perkin Elmer), I have an areaDetector device driver that

talks to a family of detectors: a 1 megapixel and a 4 megapixel panel

in this case. The vendor API is the same for each. I naively set the

mbbo for the detector timings to the values for the 1 megapixel detector

I've been developing with by setting the values in the detector template

file as you suggest. When we started using the 4 megapizel panel, the

frame rates were all wrong because it uses different timings.

I can create a different template file for each panel but the valid

timing values can be retrieved from the detector at run time. It would

be better to be able to set them somehow.

It looks like these panels may support a more arbitrary selection of

exposure timings and that the 8 preset timings provided by the vendor

API are more of a convenience. If this turns out to be true, I'll drop

the mbbo and use a more generic record type for this case, but I know of

other detectors where this may be an issue as well.

Brian

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System