John and Zachary,
Both the ImageJ and IDL visualization tools provided with areaDetector put a CA monitor on the UniqueID PV. When that PV changes the code does a caget from the ArrayData PV. This is simpler than putting a monitor on the ArrayData itself, in which case the monitor would need to be cancelled and reissued each time the data type or size of the image changed.
The Point Grey driver is new. I have tested it on a Flea2 camera, but not on a Flea3 camera.
In the constructor of the Point Grey driver I tell their SDK to embed a frame counter in each image:
embeddedInfo.frameCounter.onOff = true;
In the function that reads the image and constructs the NDArray I copy that frame counter to the NDArray->uniqueID.
pRaw_->uniqueId = metaData.embeddedFrameCounter;
That is working fine for Flea2, BlackFly, and Grasshopper3 cameras. For some reason it does not seem to be working for your Flea3 camera. Can you look at the hardware-specific documentation for your camera and see if it discusses what embedded image information that camera supports?
Mark
________________________________
From: [email protected] [[email protected]] on behalf of John Dobbins [[email protected]]
Sent: Friday, May 02, 2014 1:57 PM
To: Zachary A. Brown; [email protected]
Subject: RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems
A quick look at the source code for ImageJ shows that it is looking for a UniqueID change, so I don't think ImageJ will work without the Unique ID updating.
John Dobbins
________________________________
From: [email protected] <[email protected]> on behalf of Zachary Brown <[email protected]>
Sent: Friday, May 02, 2014 2:00 PM
To: [email protected]
Subject: Re: Point Grey Flea3 areaDetector ImageJ Viewer Problems
From more testing:
A camonitor on PG1:image1:ArrayData shows that the values in the array are changing as the camera is moved around, so the array is getting updated.
ImageJ still shows a zero-value array. The image shown from the plugin is 1280x1024 (8-bit) as it should be, but no pixel values.
The Array Counter in for the StdArray increases with the image count, but I did notice that the Unique ID for each array does not change (not sure if this is relevent, have not paid attention to this parameter before).
-Zachary Brown, John Dobbins
On Fri, May 2, 2014 at 1:02 PM, Zachary Brown <[email protected]<mailto:[email protected]>> wrote:
Hello,
I am using the new Point Grey pre-built in windows 7 x64. I am having issues streaming the images to the ImageJ areaDetector plugin.
I am able to acquire images in all image modes (single, multiple, continuous) and save the images using the TIFF plugin, but the NDStdArrays plugin does not seem to be getting any data, so the callbacks do not update, so the ImageJ plugin does not stream.
PG1:cam1:ArrayCallbacks is set to Enable
PG1:image1:EnableCallbacks is set to Enable
If any more information would be helpful, please contact me, thank you,
-ZB
- Replies:
- RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems John Dobbins
- References:
- Re: Point Grey Flea3 areaDetector ImageJ Viewer Problems Zachary Brown
- RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems John Dobbins
- Navigate by Date:
- Prev:
Re: Point Grey Flea3 areaDetector ImageJ Viewer Problems Zachary Brown
- Next:
RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems John Dobbins
- Next:
RE: Point Grey Flea3 areaDetector ImageJ Viewer Problems John Dobbins
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|