Access to information is restricted depending on your login. Request login-information through our contact form.


Using Keith&Koep Camera Driver

The Keith&Koep camera driver has a custom interface to get pictures and control camera features.
It consists of a camera-specific and a common part.

Registry Settings

Camera-timings are configured through registry.

   "Dll"="camera.dll"                ; common camera.dll
   "Prefix"="CXM"                    ; together with Index,
   "Index"=dword:1                   ; specifies to create driver at CXM1:
   "FriendlyName"="Camera Driver"
!-- For the older camera driver (pre 02.07.2009) the registry settings
!-- for a camera are here:
   "Control0"=dword:900003f9         ; see PXA-Developers-Manual for details
   "Control1"=dword:013f8112         ; on Control0 to Control4.
   "Timeout"=dword:007BFA48	     ; 5s
   "CameraDLL"="ov7660.dll"          ; custom camera-specific DLL.
!-- For new camera drivers, each camera has its own sub-key.
!-- Which camera will be used is determined by the "Name"-key:
   "Name"="ov7660"                   ; Name of the camera.
   "Control1"=dword:013f8112         ; on Control0 to Control4.
   "Timeout"=dword:007BFA48	     ; 5s
   "CameraDLL"="ov7660.dll"          ; custom camera-specific DLL.

The Custom/Camera-Specific Part

The custom camera DLL needs to export following functions:

  • int InitCamera( void)
  • BOOL IoctlCamera( DWORD dwCode, PVOID pBufIn, DWORD dwLenIn, PDWORD pdwBufOut, DWORD dwLenOut, PDWORD pdwActualOut)
  • int DeInitCamera( void)


This function gets called on the CreateFile(…)-call of the application.


This function gets called on the CloseHandle(…)-call of the application.


This function gets called on every DeviceIoControl(…)-call to the camera-driver.
If this function returns TRUE, it indicates that this ioctl-call is handled by the custom-driver.
If it returns FALSE it indicates, that the common-camera-driver should do additional action. i.e. when using IOCTL_SET_CAMERA_FEATURE with CAM_RESOLUTION you would typically set some registers in the camera and return FALSE, so the common driver adjust the resolution of the quick-capture-interface of the processor.


The application should open the camera-driver with a call to:

hCamera = CreateFile( TEXT("CXM1:"),  GENERIC_READ|GENERIC_WRITE, 0, 0, OPEN_EXISTING, 0, 0);

and close it with:

CloseHandle( hCamera);

To get a picture call:

DeviceIoControl( hCamera, IOCTL_GET_PICTURE, NULL, 0, g_pFrame, FRAME_SIZE, NULL, NULL);

Where g_pFrame is a pointer to a memory-region which should receive the captured data and FRAME_SIZE is the size of the memory-region reserved at g_pFrame.


PXACamera sample with new Camera Driver. Direct preview within camera driver made for Trizeps IV IPAN7 with PAL color conversion. 50fps:

PXACamera sample application for Windows Embbedded CE6 (Trizeps IV & Trizeps V):

Sample of custom camera drivers: (Trizeps IV & Trizeps V)

Windows Embedded CE6-Image for Trizeps5 running on uConXS (Spark) and using Omnivision OV9655 camera:

Cookies helfen bei der Bereitstellung von Inhalten. Durch die Nutzung dieser Seiten erklären Sie sich damit einverstanden, dass Cookies auf Ihrem Rechner gespeichert werden. Weitere Information
service/wince/appnotepub/pxacamera.txt · Zuletzt geändert: 2015/10/14 11:13 von