Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Thu, 16 Jun 2011 20:32:30 -0500

Hi Bob,

areaDetector 1.6 uses PvApi 1.18, but the current Subversion version of areaDetector (soon to be release 1.7) uses PvApi 1.24.  I have changed the driver quite a bit for the 1.24 version, so it would be good if you could make your changes to the SVN version, which is available here:

https://subversion.xor.aps.anl.gov/synApps/areaDetector/trunk/

This is from the release notes for the upcoming 1.7 release:

*	Prosilica driver. 

*	Removed support for writing TIFF files using the driver library. This was a problem because their driver uses an incompatible version of libtiff that conflicts with the new version used by GraphicsMagick. The driver TIFF writer had no advantage over using the NDFileTIFF and NDFileMagick plugins, which have more features and can run in their own threads.
*	Fixed a bug that could cause a blue-screen crash on Windows 7. The new version of their library requires clearing a structure to 0 before using it.
*	Upgraded to version 1.24 of the AVT SDK, and 1.20 of the Windows filter driver. Users should install the latest Sample Viewer and filter driver 1.20 on Windows machines so that the areaDetector application can use the filter driver. The filter driver version in areaDetector must match the one installed on Windows in order to use it.

Thanks,
Mark

________________________________

From: Bob Gunion [mailto:[email protected]]
Sent: Thu 6/16/2011 7:13 PM
To: Mark Rivers
Cc: Robert Petkus; [email protected]
Subject: Re: AreaDetector: Prosilica camera on different subnet?

Mark,

Thanks for the pointer.  I got it to work, but I had to download the latest version of the PvApi library.  Version 1.18 of PvApi is included in areaDetector 1.6, but PvCameraOpenByAddr didn't work.  When I tried version 1.24 it worked just fine.  Still testing - I haven't tried retrieving an image yet - so I'll wait until I have a little more confidence before sending you my (fairly minimal) changes.

Thanks again,
Bob

On Jun 15, 2011, at 6:09 PM, Mark Rivers wrote:

> Bob,
>
> If you change the configuration routine and constructor from
>
> int prosilicaConfig(char *portName,
>                    int uniqueId,
>                    int maxBuffers, size_t maxMemory,
>                    int priority, int stackSize)
>
> to
>
> int prosilicaConfig(char *portName,
>                    const char* address,
>                    int maxBuffers, size_t maxMemory,
>                    int priority, int stackSize)
>
> Then you can test "address" to see if it is an integer.  If so, it is a UniqueID, if not it is an IP address or IP name.  Then call the appropriate PvCameraOpen function.  The nice thing about making this change is that it is backwards compatible with existing startup scripts, since the iocsh can pass a unique ID as an integer or a string without requiring quotes.
>
> I'm on travel or I would try it myself.
>
> Mark

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System