Das motion_modules-Package Dieses Package ist als Zusatzpaket zum motion-Paket zu sehen und enthält optionale Kamera-Kernelmodule. Es basiert auf dem von Thomas Unger (Email:info(at)tomblom(dot)eisfairi(dot)net) entwickeltem mod_usbcam-Paket und wurde von Jürgen Edner (Email:fli4l-eisfair(at)telejeck(dot)de) für das motion-Paket adaptiert und weiterentwickelt. Einleitung In diesem Paket wurden verschiedenste Komponenten zusammengestellt, die für die Ansteuerung verschiedenster Kamera-Hardware über USB oder die parallel Schnittstelle benötigt werden. Für die Visualisierung der Video-Streams oder Bilder muss z.B. das motion-Paket installiert werden. Installation Das motion_modules-Paket wird über das Setup-Menü installiert. Nach dem Installieren der Kernelmodule können diese direkt verwendet werden. Funktionen Das motion_modules-Paket besteht im Einzelnen aus folgenden Komponenten: * CPIA - Linux Treiber für CPiA Webcams (http://webcam.sourceforge.net) * NW802 - Linux Treiber für NW802 Chipsatz (http://nw802.sourceforge.net/news.html) * OV511 / OV518 - Linux Treiber für OVCams (http://alpha.dyndns.org/ov511/) * PWC / PWCX - Linux Treiber für Philips USB Webcams (http://www.smcc.demon.nl/webcam/) * QC-MESSENGER - Linux Treiber für Quickcam Messenger & Communicate (http://home.mag.cx/messenger/) * QUICKCAM - Linux Treiber für Quickcam USB Kameras (http://qce-ga.sourceforge.net) * SPCA - Linux Treiber für Kameras mit Sunplus Chipsatz (http://mxhaard.free.fr/download.html) * STV680 - Linux Treiber für Kameras mit STMicroelectronics Chipsatz (http://stv0680-usb.sourceforge.net/) * USBCAM - Linux Treiber für USB-Kameras * SETPWC - Programm um Philips-spezifische (und kompatible Logitech und Creative Webkameras) Parameter zu setzen. (http://www.vanheusden.com/setpwc/) Voraussetzungen Dieses Paket benötigt einzig einen Kernel der Version 2.4.26-1 oder 2.4.35-wt1. Informationen zu den einzelnen Kernelmodulen cpia / cpia_pp / cpia_usb ------------------------- Weitere Informationen zu den cpia-Kernelmodulen findet man unter: http://webcam.sourceforge.net/ nw802 ----- Modulparameter: debug "Debug level: 0-5 (default=0)" debug_uv "Debug level of USB Video: 0-2 (default=0)" size "Video size: 0=160x120 1=176x144 2=320x240 3=352x288 4=640x480 (default=2)" Supported WebCam: iRez Kritter, D-link dru-350c, QuickCam Pro (with dark ring), The Scope USB Microscope M2 (ProScope), Conceptronic Video Pro (CVIDEOPRO USB Webcam CCD), Trust SpaceCam120, SpaceCam100 PORTABLE, Chicony TwinkleCam Mustek WCam300, BTC SurfCam CMOS300k ov511 ----- You can set these with: modprobe ov511 NAME=VALUE There is currently no way to set these on a per-camera basis. NAME: autobright TYPE: integer (Boolean) DEFAULT: 1 DESC: Brightness is normally under automatic control and can't be set manually by the video app. Set to 0 for manual control. NAME: autogain TYPE: integer (Boolean) DEFAULT: 1 DESC: Auto Gain Control enable. This feature is not yet implemented. NAME: autoexp TYPE: integer (Boolean) DEFAULT: 1 DESC: Auto Exposure Control enable. This feature is not yet implemented. NAME: debug TYPE: integer (0-6) DEFAULT: 3 DESC: Sets the threshold for printing debug messages. The higher the value, the more is printed. The levels are cumulative, and are as follows: 0=no debug messages 1=init/detection/unload and other significant messages 2=some warning messages 3=config/control function calls 4=most function calls and data parsing messages 5=highly repetitive mesgs NAME: fix_rgb_offset TYPE: integer (Boolean) DEFAULT: 0 DESC: Some people have reported that the blue component of the image is one or so lines higher than the red component. This is only apparent in images with white objects on black backgrounds at 640x480. Setting this to 1 will realign the color planes correctly. NOTE: You will likely need a fast (500 MHz) CPU. NAME: snapshot TYPE: integer (Boolean) DEFAULT: 0 DESC: Set to 1 to enable snapshot mode. read()/VIDIOCSYNC will block until the snapshot button is pressed. Note: enabling this mode disables /proc/video/ov511//button NAME: force_rgb (Deprecated; may be removed in the future) TYPE: integer (Boolean) DEFAULT: 0 DESC: Force image to be read in RGB instead of BGR. This option allow programs that expect RGB data (e.g. gqcam) to work with this driver. If your colors look VERY wrong, you may want to change this. NAME: cams TYPE: integer (1-4 for OV511, 1-31 for OV511+) DEFAULT: 1 DESC: Number of cameras allowed to stream simultaneously on a single bus. Values higher than 1 reduce the data rate of each camera, allowing two or more to be used at once. If you have a complicated setup involving both OV511 and OV511+ cameras, trial-and-error may be necessary for finding the optimum setting. NAME: compress TYPE: integer (Boolean) DEFAULT: 0 DESC: Set this to 1 to turn on the camera's compression engine. This can potentially increase the frame rate at the expense of quality, if you have a fast CPU. You must load the proper compression module for your camera before starting your application (ov511_decomp or ov518_decomp). NAME: testpat TYPE: integer (Boolean) DEFAULT: 0 DESC: This configures the camera's sensor to transmit a colored test-pattern instead of an image. This does not work correctly yet. NAME: dumppix TYPE: integer (0-2) DEFAULT: 0 DESC: Dumps raw pixel data and skips post-processing and format conversion. It is for debugging purposes only. Options are: 0: Disable (default) 1: Dump raw data from camera, excluding headers and trailers 2: Dumps data exactly as received from camera NAME: led TYPE: integer (0-2) DEFAULT: 1 (Always on) DESC: Controls whether the LED (the little light) on the front of the camera is always off (0), always on (1), or only on when driver is open (2). This is not supported with the OV511, and might only work with certain cameras (ones that actually have the LED wired to the control pin, and not just hard-wired to be on all the time). NAME: dump_bridge TYPE: integer (Boolean) DEFAULT: 0 DESC: Dumps the bridge (OV511[+] or OV518[+]) register values to the system log. Only useful for serious debugging/development purposes. NAME: dump_sensor TYPE: integer (Boolean) DEFAULT: 0 DESC: Dumps the sensor register values to the system log. Only useful for serious debugging/development purposes. NAME: printph TYPE: integer (Boolean) DEFAULT: 0 DESC: Setting this to 1 will dump the first 12 bytes of each isoc frame. This is only useful if you are trying to debug problems with the isoc data stream (i.e.: camera initializes, but vidcat hangs until Ctrl-C). Be warned that this dumps a large number of messages to your kernel log. NAME: phy, phuv, pvy, pvuv, qhy, qhuv, qvy, qvuv TYPE: integer (0-63 for phy and phuv, 0-255 for rest) DEFAULT: OV511 default values DESC: These are registers 70h - 77h of the OV511, which control the prediction ranges and quantization thresholds of the compressor, for the Y and UV channels in the horizontal and vertical directions. See the OV511 or OV511+ data sheet for more detailed descriptions. These normally do not need to be changed. NAME: lightfreq TYPE: integer (0, 50, or 60) DEFAULT: 0 (use sensor default) DESC: Sets the sensor to match your lighting frequency. This can reduce the appearance of "banding", i.e. horizontal lines or waves of light and dark that are often caused by artificial lighting. Valid values are: 0 - Use default (depends on sensor, most likely 60 Hz) 50 - For European and Asian 50 Hz power 60 - For American 60 Hz power NAME: bandingfilter TYPE: integer (Boolean) DEFAULT: 0 (off) DESC: Enables the sensor´s banding filter exposure algorithm. This reduces or stabilizes the "banding" caused by some artificial light sources (especially fluorescent). You might have to set lightfreq correctly for this to work right. As an added bonus, this sometimes makes it possible to capture your monitor´s output. NAME: fastset TYPE: integer (Boolean) DEFAULT: 0 (off) DESC: Allows picture settings (brightness, contrast, color, and hue) to take effect immediately, even in the middle of a frame. This reduces the time to change settings, but can ruin frames during the change. Only affects OmniVision sensors. NAME: force_palette TYPE: integer DEFAULT: 0 (off) DESC: Forces the palette (color format) to a specific value. If an application requests a different palette, it will be rejected, thereby forcing it to try others until it succeeds. This is useful for forcing greyscale mode with a color camera, for example. Supported modes are: 0 (Allows all the following formats) 1 VIDEO_PALETTE_GREY (Linear greyscale) 3 VIDEO_PALETTE_RGB565 (565 16 bit RGB) 4 VIDEO_PALETTE_RGB24 (24bit RGB) 7 VIDEO_PALETTE_YUV422 (YUV422 capture) 8 VIDEO_PALETTE_YUYV (YUV422 capture; same as 7) 10 VIDEO_PALETTE_YUV420 (YUV 4:2:0 Planar) 13 VIDEO_PALETTE_YUV422P (YUV 4:2:2 Planar) 15 VIDEO_PALETTE_YUV420P (YUV 4:2:0 Planar, same as 10) NAME: backlight TYPE: integer (Boolean) DEFAULT: 0 (off) DESC: Setting this flag changes the exposure algorithm for OmniVision sensors such that objects in the camera's view (i.e. your head) can be clearly seen when they are illuminated from behind. It reduces or eliminates the sensor's auto-exposure function, so it should only be used when needed. Additionally, it is only supported with the OV6620 and OV7620. NAME: unit_video TYPE: Up to 16 comma-separated integers DEFAULT: 0,0,0... (automatically assign the next available minor(s)) DESC: You can specify up to 16 minor numbers to be assigned to ov511 devices. For example, "unit_video=1,3" will make the driver use /dev/video1 and /dev/video3 for the first two devices it detects. Additional devices will be assigned automatically starting at the first available device node (/dev/video0 in this case). Note that you cannot specify 0 as a minor number. This feature requires kernel version 2.4.5 or higher. NAME: remove_zeros TYPE: integer (Boolean) DEFAULT: 0 (do not skip any incoming data) DESC: Setting this to 1 will remove zero-padding from incoming data. This will compensate for the blocks of corruption that can appear when the camera cannot keep up with the speed of the USB bus (eg. at low frame resolutions). This feature is always enabled when compression is on. NAME: mirror TYPE: integer (Boolean) DEFAULT: 0 (off) DESC: Setting this to 1 will reverse ("mirror") the image horizontally. This might be necessary if your camera has a custom lens assembly. This has no effect with video capture devices. NAME: ov518_color TYPE: integer (Boolean) DEFAULT: 0 (off) DESC: Enable OV518 color support. This is off by default since it doesn't work most of the time. If you want to try it, you must also load ov518_decomp with the "nouv=0" parameter. If you get improper colors or diagonal lines through the image, restart your video app and try again. Repeat as necessary. Weitere Informationen zum Kernelmodul ov511 findest du auf http://alpha.dyndns.org/ov511 pwc --- Modulparameter: size: string description "Initial image size. One of sqcif, qsif, qcif, sif, cif, vga" fps: int description "Initial frames per second. Varies with model, useful range 5-30" fbufs: int description "Number of internal frame buffers to reserve" mbufs: int description "Number of external (mmap()ed) image buffers" trace: int description "For debugging purposes" power_save: int description "Turn power save feature in camera on or off" compression: int description "Preferred compression quality. Range 0 (uncompressed) to 3 (high compression)" leds: int array (min = 2, max = 2) description "LED on,off time in milliseconds" dev_hint string array (min = 0, max = 20) description "Device node hints" mod_quickcam / qcmessenger -------------------------- The behaviour of the qce-ga driver can be modified using a series of options passed when the module is being loaded using modprobe. The current options are documented below: debug 1 | 2 | 4 | 8 | 16 | 32 Sets the debug output (1,2,4,8,16,32). Setting this high will cause the driver to slow down as it generates lots of useful output for developers. interpolation 0 | 1 This changes the way in which the Bayer-RGB within the sensor is interpolated to give the final output image. Default is 0 which is standard interpolation, 1 is bilinear interpolation which gives better results but is slightly slower. mode 0 | 1 Set the image size between full size (352*288) and half size (176*144). A smaller image has less detail but gives a correspondingly higher frame rate. Default is 0 which is full size. keepexposure 0 | 1 Default 0. Setting this option to 1 causes the driver to remember the last exposure settings. Useful when being used as a webcam since the camera normally takes several seconds to adjust after the video device has been opened. tobgr 0 | 1 Automatic RGB -> BGR conversion. Defaults to 0 where the driver automatically attempts to determine the correct RGB/BGR order of the graphics card. rgain (0-255) bgain (0-255) ggain (0-255) Overrides the automatic gain control on the sensor. Useful for applications where the default gain control gives poor results. bright (0-65535) Overrides the automatic brightness control on the sensor. Useful for applications where the default brightness control gives poor results. video_nr N Set the video device number to /dev/videoN. Useful when more than one V4L device exists on a system. Defaults to 0. For example, to configure the driver to use /dev/video1 with half-size frames you would use: modprobe mod_quickcam video_nr=1 mode=1 Weitere Informationen zum Kernelmodul mod_quickcam findest du unter: http://qce-ga.sourceforge.net quickcam -------- Modulparameter: qcdebug "Sets the debug output (bitfield)" keepsettings "Keep picture settings across one open to another (0-1)" settle "Maximum number of frames to wait picture brightness to settle (0-255)" subsample "Sets subsampling (0-1)" compress "Enable compressed mode (0-1)" frameskip "How frequently capture frames (0-10)" quality "Sets the picture quality (0-5)" adaptive "Automatic adaptive brightness control (0-1)" equalize "Equalize image (0-1)" userlut "Apply user-specified lookup-table (0-1)" retryerrors "Retry if image capture fails, otherwise return error code (0-1)" compatible "Enable workaround for bugs in application programs (bitfield)" video_nr "Set videodevice number (/dev/videoX)" spca50x/spca5xx --------------- There are several parameter that can be passed in: force_rgb = 1 Set reverse rgb order OffRed = -16 Initial red offset range [-128..+128] OffBlue = -16 Initial blue offset OffGreen = -16 Initial green offset GRed = 256 Initial gain setting to 1 range [0..512] GBlue = 256 Initial gain setting to 1 GGreen = 256 Intial gain seting to 1 gamma = 3 Set gamma table to 1 range [0..7] usbgrabber = 1 if you use an usb grabber usbid 0x0733:0x430 otherwise usbgrabber=0 bright=25 <-- Set camera initial brightness (25 for greyscale, ~90 for colour) contrast=16 <-- Set camera initial contrast (16 for greyscale, ~32-64 for colour) debug= <-- set debug level ccd=0 <-- SPCA505 only. Switch between the internal CCD (zero) and the external video input (non-zero) osd=1 <-- Enable on-screen display if kernel patches applied (see below) Weitere Informationen zum Kernelmodul spca50x findest du unter: http://spca50x.sourceforge.net/spca50x.php spca50x_spec ------------ This is a experimental driver for support Logitech with ICM-Chip. The features are the same like spca50x/spca5xx. stv680 ------ usbcam ------