Changes between Version 10 and Version 11 of UnifiedCameraAccess
- Timestamp:
- Feb 24, 2011, 2:43:26 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UnifiedCameraAccess
v10 v11 3 3 `libuca` is a thin wrapper to make the different cameras (via !CameraLink or PCIe) accessible in an easy way. 4 4 5 == Specification ==5 == Specification of Properties == 6 6 7 7 Properties of cameras are accessed in a vendor-neutral way by specifying the property names as defined in [http://ufo.kit.edu/ufo/browser/vogelgesang/uca/src/uca.h uca.h]. The following list is the definite specification of basic properties that all devices must implement. If a property cannot be set or get via `uca_(get|set)_property()` the function shall return UCA_ERR_PROP_INVALID. … … 24 24 25 25 ||= Property Name =||= Property String =||= Unit =||= Access =||= Meaning =|| 26 || `UCA_PROP_TIMESTAMP_MODE` || `timestamp-mode` || bitmask (see below) || r/w || Print a timestamp || 26 27 || `UCA_PROP_INTERLACE_SAMPLE_RATE` || `interlace-sample-rate` || integer quantity || r/w || Take only every `interlace-sample-rate` rows into account for the Fast-Reject algorithm || 27 28 || `UCA_PROP_INTERLACE_PIXEL_THRESH` || `interlace-pixel-threshold` || number of pixels || r/w || Row is classified as triggered, when more than `interlace-row-threshold` pixels trigger || 28 29 || `UCA_PROP_INTERLACE_ROW_THRESH` || `interlace-row-threshold` || number of rows || r/w || Ignore row trigger when less than `interlace-row-threshold` rows trigger || 29 || `UCA_PROP_CORRECTION_MODE` || `correction-mode` || 32-bitbitmask (see below) || r/w || Enable/disable certain correction modes ||30 || `UCA_PROP_CORRECTION_MODE` || `correction-mode` || bitmask (see below) || r/w || Enable/disable certain correction modes || 30 31 31 A camera may use different trigger signals to start exposure via `UCA_PROP_TRIGGER_MODE`. Possible values are: 32 === Values === 33 34 `UCA_PROP_TIMESTAMP_MODE` (boolean combinations possible): 35 36 ||= Timestamp bit =||= Meaning =|| 37 || UCA_TIMESTAMP_BINARY || Binary encoded timestamp || 38 || UCA_TIMESTAMP_ASCII || Human-readable ASCII timestamp || 39 40 `UCA_PROP_TRIGGER_MODE`: 32 41 33 42 ||= Trigger Name =||= Meaning =|| … … 36 45 || `UCA_TRIGGER_EXTERNAL` || Trigger via external hardware || 37 46 38 The following correction modes and boolean combinations of them can be applied 47 `UCA_PROP_CORRECTION_MODE` (boolean combinations possible): 39 48 40 49 ||= Correction bit =||= Meaning =||