diff --git a/documentation/prosilicaDoc.html b/documentation/prosilicaDoc.html index 49777e4..38078e9 100755 --- a/documentation/prosilicaDoc.html +++ b/documentation/prosilicaDoc.html @@ -31,10 +31,10 @@
This is a driver for Gigabit Ethernet and Firewire cameras from Prosilica. The driver is only supported under Windows (EPICS win32-x86 architecture), - Linux and Mac OS X because the vendor library is provided as a pre-built binary for - those operating systems only. The vendor library provided by Prosilica does callbacks - to a user-supplied function each time there is a new frame. Thus, the driver does - not need to create a thread itself for callbacks." + Linux and Mac OS X because the vendor library is provided as a pre-built binary + for those operating systems only. The vendor library provided by Prosilica does + callbacks to a user-supplied function each time there is a new frame. Thus, the + driver does not need to create a thread itself for callbacks."
This driver inherits from ADDriver. @@ -525,6 +525,27 @@
int prosilicaConfig(char *portName,
const char* cameraId,
int maxBuffers, size_t maxMemory,
- int priority, int stackSize)
+ int priority, int stackSize, int maxPvAPIFrames)
The cameraId string can be any of the following:
-Using the UniqueId has the advantage that the cameras can be configured to use DHCP, - and hence have non-predictable TCP/IP addresses. However, if the UniqueId is used then the areaDetector - IOC must be on the same subnet as the camera, since cameras cannot be found by UniqueID - through routers. The simplest way to determine the uniqueId of a camera is to run - the Prosilica GigEViewer application, select the camera, and press the "i" icon - on the bottom of the main window to show the camera information for this camera. - The Unique ID will be displayed on the first line in the information window.
-The IP address or IP DNS name - can be used for cameras with fixed IP addresses, and must be used for cameras that are not - on the local subnet.
-For details on the meaning of the other parameters to this function refer to the detailed
- documentation on the prosilicaConfig function in the
+
+ Using the UniqueId has the advantage that the cameras can be configured to use DHCP,
+ and hence have non-predictable TCP/IP addresses. However, if the UniqueId is used
+ then the areaDetector IOC must be on the same subnet as the camera, since cameras
+ cannot be found by UniqueID through routers. The simplest way to determine the uniqueId
+ of a camera is to run the Prosilica GigEViewer application, select the camera, and
+ press the "i" icon on the bottom of the main window to show the camera information
+ for this camera. The Unique ID will be displayed on the first line in the information
+ window.
+ The IP address or IP DNS name can be used for cameras with fixed IP addresses, and
+ must be used for cameras that are not on the local subnet.
+ The maxPvAPIFrames parameter controls how many frame buffers will be used by the
+ PvAPI library. This is the last parameter in the prosilicaConfig command, and if
+ it is absent the default value of 2 is used, which is sufficient in most circumstances.
+ However, with very high frame rates or busy IOCs increasing this value can reduce
+ dropped frames.
+ For details on the meaning of the other parameters to this function refer to the
+ detailed documentation on the prosilicaConfig function in the
prosilica.cpp documentation and in the documentation for the constructor for
the prosilica class.
+
+