Introduction
The DevWare application has a dialog plug-in API whereby an externally written and compiled module (DLL) can integrate with DevWare, present a dialog window to the user, and have access to sensor registers and image data.
The diagram below illustrates the main modules in DevWare that have call-backs into the plug-in DLL.
Features of the Dialog Plug-in API
Plug-ins can be used to create a UI for new sensor registers or third party or prototype hardware not supported by Sensor Control pages in DevWare, or for image processing or image data capture. The Plug-in API provides:
- Read and write access to any register and/or any field within a register, including registers on companion chips.
- Notification when another part of DevWare changes a register the plug-in is interested in so on-screen controls can be updated.
- Read and write access to captured image data, both raw data and the final RGB image that DevWare will display in the main window.
- Control of DevWare's software color pipeline features such as auto exposure, software color correction, etc.
DevWare supports up to 24 plug-in dialogs simultaneously. If plug-ins are present, DevWare will add a “Plug-ins” menu to its main window. The user can activate and deactivate plug-in windows at will.
Dialog Plugin API Details
These sections describe the API specifications. The API is rather simple. There are two required functions and a few optional functions your plug-in exports to DevWare, and DevWare will provide functions to the plug-in to access the sensor and control DevWare.
DevWare creates the plug-in windows when it starts a camera, and doesn't destroy them until the user switches to a new camera or exits the application. DevWare will show and hide your window when the user selects it on the Plug-in menu. If the user clicks your Close button, you should hide your window, not close it. Therefore you can continue processing image data even when your window is hidden, if desired.
Include Files
#include "ApBase.h" #include "DlgImport.h"
The files are in the include directory where the Aptina Imaging software is installed, typically C:\Aptina Imaging\include.
DLL Exported Functions
Function | Details | Calling Thread |
---|---|---|
OpenDialog | __declspec(dllexport) HWND CALLBACK (Only on Windows, if your plug-in is not using the Qt GUI library.) DevWare calls this function when it's starting up a camera or switching cameras. You should create your window but not show it. Return the Windows window handle for your window. DevWare will use the handle to show and hide your window. The title of your window will be used for the menu in DevWare. Do only basic initialization here. Do not access registers yet; you will have an opportunity to do that later. Parameters:
If something goes wrong return 0. If your plug-in should only work with certain devices you can examine the pCamera structure and return 0 if you plug-in is not designed for that device. Otherwise DevWare will add your plug-in to the “Plug-Ins” menu, using the title bar text from your window for its menu item. The API supports only one window per DLL. (But that window could be a tabbed dialog with any number of tabs, or could have child windows. Also, DevWare can load up to 24 DLLs simultaneously.) | GUI |
OpenQtDialog | __declspec(dllexport) QWidget * CALLBACK (If your plug-in is using the Qt GUI library. Any OS.) Same as OpenDialog(), but using Qt widgets instead of Windows window handles. | |
CloseDialog | CloseDialog() Called when DevWare is switching to another camera, or exiting. Destroy your window and free all allocated memory. If OpenDialog() returned 0, CloseDialog() will not be called. | GUI |
ImageData | __declspec(dllexport) void CALLBACK DevWare will pass all image data to your plug-in through this function. It will be called at least twice for every frame displayed by DevWare. Once with the data in sensor-dependent format, and again with the final RGB image that DevWare is going to display in its window. You do not need to export this function if your plug-in does not use the image data. Parameters:
This function can be used for analysis, image processing, or data capture. You can write to the image buffer and DevWare will use the new data. For example, you can write to the MI_RGB32 buffer to create indicator graphics in the image. You could also filter image data, etc. This function is called every frame regardless of whether your window is visible or not. If you want your processing to stop when your window is hidden then you must explicitly check for that case and return immediately from the function. You must be careful of what you do in this function because it is called from a different thread than the UI thread. You must not directly access your window controls from this function. If the UI needs to be updated use inter-thread communication such as PostMessage() or Qt signals to send a message to your window, or use some other communication mechanism such as common variables and critical sections. You should not call DevWare callback functions, except that it is permissible to read and write sensor registers. DevWare converts all Bayer data to MI_BAYER_S12 for processing. MI_BAYER_S12 uses a 16-bit signed 2s-complement integer for each pixel. The value 0 represents the Black Level, and the value 4095 represents the maximum brightness. Values outside this range are possible as a result of noise or image processing. The final image is always MI_RGB32, which is 32-bits per pixel, B-G-R-x byte order. The ImageData() function is optional. If you do not need image data then you do not need to have this function. OpenDialog() and CloseDialog() are required. | Display |
GrabFrame | __declspec(dllexport) void CALLBACK DevWare will call this function every time it gets a new frame from the camera. The parameters are a pointer to the data and the data length. The data is just as it came from the camera. You do not need to export this function if your plug-in does not need this notification. If you need to poll registers or update registers frequently, this function is the best place to do it. Register access here will have the least interference with the frame rate. Parameters:
This function can be used for analysis, image processing, or data capture. You can write to the image buffer and DevWare will use the new data. This function is called on every received frame regardless of whether your window is visible or not. If you want your processing to stop when your window is hidden then you must explicitly check for that case and return immediately from the function. You must be careful of what you do in this function because it is called from a different thread than the UI thread. You must not directly access your window controls from this function. You should not call DevWare callback functions, except that it is permissible to read and write sensor registers. The GrabFrame() function is optional. If you do not need the notifications then you do not need to have this function. | Camera |
SaveImage | __declspec(dllexport) void CALLBACK DevWare will call this function when it saves a captured image. The plug-in may save additional data files if desired. Parameters:
This function is called whenever the application saves a captured image, regardless of whether your window is visible or not. This function is typically called from the main thread. The SaveImage() function is optional. If you do not need the notifications then you do not need to have this function. | Display? |
RegisterChanged | __declspec(dllexport) void CALLBACK DevWare will call this function when a sensor register you are monitoring has been written. See MonitorRegister() below. Take any action needed. This function will be called even if your plug-in window is hidden. This function is typically called from the UI thread. The RegisterChanged() function is optional. If you do not need the notifications then you do not need to have this function. |
DevWare Callback Functions
DevWare passes function pointers to your OpenDialog() function in the DEVW_Callbacks structure.
Function Name | Details |
---|---|
ReadRegister() | int Callbacks.ReadRegister(const char *regname, const char *fieldname, int cached); Read a sensor register or field of a sensor register. If you want to read the whole register, pass NULL for the field name. You can only access registers and fields defined in the sensor data file. For performance, DevWare caches the last value written to a register. For most registers it is sufficient to only get the cached value. In that case pass 1 for cached. If a register can be changed by the hardware or if it can return a different value each time when read then pass 0 for cached to always read the hardware (cached = 0 for volatile registers). |
WriteRegister() | void Callbacks.WriteRegister(const char *regname, const char *fieldname, unsigned int value); Write a sensor register or field of a sensor register. If you want to write the whole register, pass NULL for the fieldname. You can only access registers and fields defined in the sensor data file. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around WriteRegister(). |
ReadRegisterAddr() | int Callbacks.ReadRegisterAddr(unsigned int nAddr, unsigned int nBitmask, unsigned int nAddrSpace, mi_addr_type nAddrType, int cached); Read a sensor register or field of a sensor register by register number and address space. If you want to read the whole register, pass 0 for nBitmask. You can only access registers defined in the sensor data file. |
WriteRegisterAddr() | void Callbacks.WriteRegisterAddr(unsigned int nAddr, unsigned int nBitmask, unsigned int nAddrSpace, mi_addr_type nAddrType, unsigned int value); Write a sensor register or field of a sensor register by register number and address space. If you want to write the whole register, pass 0 for nBitmask. You can only access registers defined in the sensor data file. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around WriteRegisterAddr(). |
PeekRegister() | int Callbacks.PeekRegister(unsigned int nBaseAddr, unsigned int nAddr, int nAddrSize, int nDataSize); Read a register by Serial I/O. Can be a sensor register or a register on another chip on the Serial bus. nAddrSize and nDataSize are the width in bits of the register address and register value parameters. Valid values of nAddrSize and nDataSize are 8 or 16. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around PeekRegister(). |
PokeRegister() | void Callbacks.PokeRegister(unsigned int nBaseAddr, unsigned int nAddr, unsigned int value, int nAddrSize, int nDataSize); Write a register by Serial I/O. Can be a sensor register or a register on another chip on the Serial bus. nAddrSize and nDataSize are the width in bits of the register address and register value parameters. Valid values of nAddrSize and nDataSize are 8 or 16. This is a “dangerous” register write. It goes straight to the hardware without any snooping or special handling by DevWare. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around PokeRegister(). |
PeekRegisters() | void Callbacks.PeekRegisters(unsigned int nBaseAddr, unsigned int nAddr, int count, void *pValues, int nAddrSize, int nDataSize); Read a sequence of successive registers by Serial I/O in one function call. Can be sensor registers or registers on another chip on the Serial bus. nAddrSize and nDataSize are the width in bits of the register address and register value parameters. Valid values of nAddrSize and nDataSize are 8 or 16. The pValues parameter is interpreted as either an unsigned char * or unsigned short * depending on the value of nDataSize. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around PeekRegisters(). |
PokeRegisters() | void Callbacks.PokeRegisters(unsigned int nBaseAddr, unsigned int nAddr, int count, void *pValues, int nAddrSize, int nDataSize); Write a sequence of successive registers by Serial I/O in one function call. Can be sensor registers or registers on another chip on the Serial bus. nAddrSize and nDataSize are the width in bits of the register address and register value parameters. Valid values of nAddrSize and nDataSize are 8 or 16. The pValues parameter is interpreted as either an unsigned char * or unsigned short * depending on the value of nDataSize. This is a “dangerous” register write. It goes straight to the hardware without any snooping or special handling by DevWare. Important: call Begin/EndAccessRegs(), SyncChanges() or Stop() if needed around PokeRegisters(). |
BeginAccessRegs() EndAccessRegs() | void Callbacks.BeginAccessRegs(); This function pauses the capture thread in DevWare if the device or device driver does not support simultaneous register access and image capture. Call BeginAccessRegs() before reading or writing registers and EndAccessRegs() afterward. When writing several registers, call this function once at the beginning and once again when done:
|
SyncChanges() | void Callbacks.SyncChanges(int sync); |
Stop() | void Callbacks.Stop(int stop); This function stops the image capture and image processing threads. Call Stop(TRUE) before writing registers that will change the image size or image pixel format. Call Stop(FALSE) afterward to restart image capturing: |
Pause() | void Callbacks.Pause(int pause); This function pauses the capture thread in DevWare. The image processing thread continues to run with the last captured image. |
MonitorRegister() | void Callbacks.MonitorRegister(const char *regname, int id, HWND hwnd); This provides a way for your plug-in to be notified if a register is written in another part of DevWare. If you have controls based on the register you can update your controls.
When a register you are monitoring changes, DevWare will send call your RegisterChagned() function. |
GetState() | int Callbacks.GetState(const char *state); int ae = Callbacks.GetState("Auto Exposure"); |
SetState() | void Callbacks.SetState(const char *state, int nVal); Callbacks.SetState("Auto Exposure", 0); // turn off software AE |
GetStateStr() | char * Callbacks.GetStateStr(const char *state); |
SetStateStr() | void Callbacks.SetStateStr(const char *state, const char *szVal); |
GetOption() | int Callbacks.GetOption(const char *option, int nDefault); int mode = Callbacks.GetOption("Myplugin Mode", 1); |
SetOption() | void Callbacks.SetOption(const char *option, int nVal); Callbacks.SetOption("AnalysisDlg Show", 1); // make Analysis Graph visible |
GetOptionStr() | void Callbacks.GetOptionStr(const char *option, char *szValue, int nBufSize, const char *szDefault); |
SetOptionStr() | void Callbacks.SetOptionStr(const char *option, const char *szValue); |
LoadPreset() | void Callbacks.LoadPreset(const char *szFilename, const char *szPreset); Callbacks.LoadPreset(NULL, "Demo Initialization"); |
RunPython() | int Callbacks.RunPython(const char *szStatements); CString stmt; stmt.Format("image_size(%d, %d)", width, height); Callbacks.RunPython(stmt); |
GetMouseSelection() | void Callbacks.GetMouseSelection(int* pnSelectType, int* pnStartX, int* pnStartY, int* pnEndX, int* pnEndY); |
SetMouseSelection() | void Callbacks.SetMouseSelection(int nSelectType, int nStartX, int nStartY, int nEndX, int nEndY); Callbacks.SetMouseSelection(1, 0, height / 2, 0, height / 2); |
GetIniFileName() | const char * Callbacks.GetIniFileName(int nSeq); CString sIniFile = Callbacks.GetIniFileName(0); |
SendCommand() | unsigned int Callbacks.SendCommand(unsigned int nCommand, unsigned int pParamSize, unsigned char *pParamBuffer, unsigned int nResultSize, unsigned char *pResultBuffer, unsigned int *pBytesReturned); Sends a host command to the camera. For network-connected or serial-connected cameras. |
Plug-ins Directory
The DLL file must be in the plug-ins directory so DevWare can find it and load it. By default it is the Plugins directory where your Aptina Imaging software is installed. Example:
C:\Aptina Imaging\Plugins
Sample Code
There is a sample plug-in dialog called DialogDll, located in the samples directory Where your Aptina Imaging software is installed. The sample code is in C++ and includes Microsoft Visual Studio project files.
The sample code demonstrates:
- Proper declarations of exported DLL functions.
- Sensor type and camera type information.
- Setting a register by a dialog control (slider).
- Automatically updating a control when the underlying register changes (WM_MONITOR).
- Handling hide and show of the window.
- Handling the Close button.
- Receiving image data and doing a simple analysis.
- Putting a graphic indicator in the RGB image.
- Updating dialog controls with image analysis results using PostMessage() and a custom window message to communicate from the worker thread to the main UI thread.
Additionally, there are two "blank" sample plug-ins with no dialog controls suitable for use as a starting point for a new plug-in. One uses the Qt GUI libary, the other uses MFC.
0 Comments