| Table of Contents |
|---|
Note:The new application name for DevWare is "DevWareX".
DevWareX is a multi-platform implementation of DevWare, created with a more flexible GUI-generation tool. It has the same layout and controls as DevWare, but with additional features.
Here's a link to a description of DevWareX , and its new features.The documentation in on this page still applies to DevWareX.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
DevWareX
Application setup:
Installation(See 2.1.1)
Running the Application(See 2.1.2)
Application layout and options:
Menu Commands(See 2.2.1)
Toolbar Buttons(See 2.2.2)
Display Screen (See 2.2.3)
Main Dialogs:
Info Dialog (See 2.2.5)
Sensor Control Pages(See 2.2.4)
Presets Dialog (See 2.2.6)
Register Dialog(See 2.2.7)
Register Log Dialog(See 2.2.8)
Analysis Graph Dialog(See 2.2.9)
Magnifier(See 2.2.10)
Peek & Poke(See 2.2.12)
Watch Dialog (See 2.2.13)
Embedded Data Viewer(See 2.2.14)
Options Dialog (See 2.2.15)
Troubleshooting:
Warning Messages(See 2.2.16)
Troubleshooting(See 2.2.17)
Reporting a Bug(See 2.2.18) (mail to: Aptina-IMAGING_DEMO_BUGS@onsemi.com)
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
DevWareX Help
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
The program can now be opened by going to the start menu and selecting "Programs" then "Aptina Imaging" then "DevWareDevWareX". A popup window will appear while DevWare DevWareX probes for attached devices. Then the main DevWare DevWareX window and a dialog box will appear that is slightly different for each sensor. Select the appropriate settings and click finish. Unless an error occurs(See 2.2.17) the application will open the display dialog and start capturing and displaying sensor images.
Note: Sensor data files can be manually loaded. Click the esc key to exit automatic probe. Make sure that the box next to "Automatically probe at startup" is unchecked. Click on "Sensor..." to browse for the corresponding sensor data (sdat) file. The file will be found in C:\Aptina Imaging\sensor_data.
...
DevSuite is ready to use on the Vista and Windows 7 operating systems when installed in the correct folder, but there is a requirement that the Demo2X demo board have a FW version of 28 or newer to match to the USB driver.
Note; the Demo3 FW is already Windows 7 compatible.
Firmware Upgrade
Note that a demo board with FW older than version 28 can only be upgraded on an XP operating system since only the XP-based USB driver supports the older versions of the FW. As of May of 2010, all newly delivered Demo2X boards will have version 28 of the FW. Demo2X boards received earlier than that may have an older FW version, and the FW version should be verified on an XP-based system before proceeding.
If you aren't sure that your FW has version 28 or newer, install the DevSuite SW on an XP-based system by following the instructions thru the section titled "Starting Up the Software" as found in "DevSuite Quick-Start Guide", which can be accessed from the DevWare DevWareX menu item "Documents". Then follow the FW upgrade instructions as found in "Demo FW User Guide", which can be accessed from the DevWare DevWareX menu item "Documents -> User Guides".
If you are fairly sure that your FW has version 28 or newer, then install the DevSuite SW on your Vista or Windows 7-based system by follow the instructions thru "Starting Up the Software" section of the Quick-Start guide. Once the USB cable is connected to the Demo2X demo board, Vista and Windows 7 will automatically attempt to download the matching USB driver from the Microsoft driver web site; if the driver installs correctly then your FW is current and no further action is required - continue with the instructions found in the Quick-Start guide.
If the USB driver download fails, it is either due to downgraded FW or a network problem. You can attempt to load the USB driver manually by following the instructions in the "Aptina Drivers User Guide", which can be accessed from the DevWare DevWareX menu item "Documents -> User Guides".
If the USB driver installs correctly then your FW is current and no further action is required - continue with the instructions found in the Quick-Start guide.
If the USB driver manual load failed, you will need to use an XP-based operating system to upgrade your Demo2X demo board as described earlier in this document.
Software Installation
Do not install DevSuite in "C:\Program Files", due to the strict system security checking performed by Vista and Windows7.
The installer defaults to the recommended installation location of "C:\Aptina Imaging". If necessary this can be changed when prompted for the installation location.
...
Command line parameters can be used with DevWareDevWareX.
Usage
Open a "CMD" window, navigate to the installation folder of C:\Aptina Imaging, and provide any of the following parameters.Note that parameters can be in all upper-case or all lower-case, and can be provided in any order.
...
- /help or ? - Display this page. You are given the option to continue to DevWareX or to exit. Note: if "?" is used, all other parameters are ignored.
- /ini=filename or /ini="filename" - Specify the INI file to be used, overriding the one selected by DevWare DevWareX if "Probe" is enabled.
- /preset[=name] or /preset[="name"] - Run the optionally supplied specified preset. Note that the Startup Wizard dialog will be skipped whether or not the preset name is supplied.
- /checksensor[=0 | 1 (default if not supplied)] - Disable | Force reading of sensor registers at startup. Disabled gives faster startup.
- /camera=<number in decimal> - Force a specific camera id selection, in case more than one camera was detected.
- /probe[=0 | 1 (default if not supplied)] - Disable | Force a "Probe". Note: ignored if SDAT filename is provided, and no "Probe" is performed if the parameter itself is not supplied.
- /fullauto[=0 | 1 (default if not supplied)] - Disable | Force "Full Auto" option on the Startup Wizard. Note: enabled if parameter itself is not supplied.
- /mono[=0 | 1 (default if not supplied)] - Disable | Force "Monochrome" option on the Startup Wizard. Note: disabled if parameter itself is not supplied.
- /play[=0 | 1 (default if not supplied)] - Disable | Force "Play on Start" option on the Startup Wizard. Note: enabled if parameter itself is not supplied.
- <sensor_sdat_file>.sdat - Specify the SDAT file to be used, overriding the one selected by DevWare DevWareX if "Probe" is enabled.
- /nul - start without HW needing to be attached. An SDAT file can be loaded, and Presets can be run as long as it doesn't expect register reads to provide valid data.
- /detfar - detect FAR sensor on start.
- /warnings=filename - Specify the warnings file name.
- /restorepresets - 1 to restore the additional Presets windows from the last session, 0 to not restore the windows.
- /suppressallwindows - Start DevWareX will all windows suppressed - only the image display is enabled.
- /startfullscreen - Start DevWareX in full screen mode.
- /dll=DLLname. Include a new Transport DLL. And alternative is to copy the DLL to the Plugins folder.
- <sensor_sdat_file>.xsdat - if opening an .xsdat file with no directory path given and the file doesn't exist, the sensor_data directory will be searched.
...
| Anchor | ||||
|---|---|---|---|---|
|
Introduction
The DevWare DevWareX application framework includes the ability to extend and customize its behavior. Two types of extensions are supported:
- Dialog Plug-in - a dynamically linked library (DLL) which can be integrated with DevWare DevWareX and can be used to:
- Display custom user interfaces.
- Access and run DevWare DevWareX INI presets.
- Access sensor registers.
- Process the image data.
...
- Midlib Transport DLL - a DLL which can be integrated with the midlib library in order to create a "driver" for midlib/DevWare DevWareX in order to support new devices. With a midlib Transport DLL you can:
- Support an ON Semiconductor sensor on a device other than the Demo System camera so DevWare DevWareX or any other midlib-based application will work with the device.
- Create a software simulated camera and sensor, simulating either an existing sensor or new sensor, and be able to use DevWare DevWareX as the user interface for the simulation.
...
The toolbar is displayed across the top of the application window, below the menu bar. The toolbar provides quick access to many tools used in DevWareDevWareX.
To hide or display the Toolbar, choose Toolbar from the View menu (ALT-V, T).
...
For "'Raw Bayer Color - Sensor Output", disable all DevWare DevWareX ColorPipe options.
Bayer Bypass/SW FRF Advanced
This page implements a Flat Region Filter using Sigma, Edge, and Chroma thresholds..
Bayer Bypass/SW Green Balance
This page allows the user to enable Green Balance Correction for the DevWare DevWareX SW ColorPipe and adjust Highlights and Shadows.
Bayer Bypass/SW Black Color Kill
This page allows the user to enable Black Color Kill for the DevWare DevWareX SW ColorPipe and adjust its thresholds.
...
These sensor control pages are only displayed for Bayer sensors. For example, the: A-0360, A-0366, A-1300, A-1310, A-2010, A-3100, etc. For the most part, they control software image processing algorithms in DevWareDevWareX.
Note: The available sensor control pages and features depend on the type and version of the image sensor.
| Anchor | ||||
|---|---|---|---|---|
|
This page gives some control over the demosaicing algorithms that are used to convert the bayer image into an RGB color image.
...
There are two distinct modes of still capture. In the Current Displayed Image mode the still capture only freezes the currently displayed image and lets you save it to a file. No sensor registers are affected.
In the Full Resolution Image mode DevWare DevWareX will perform a still capture procedure on the sensor. It could involve changing the image size, using global shutter mode, activating a flash lamp and so on. On an SOC it would involve activating the still image sequence on the sensor.
...
Image Save Options Page Anchor imagesaveoptions imagesaveoptions
This dialog is used to set the various image save options that are available.
The "Save Options" selection allows the user to select the type of data to be written to files. Raw Data is the unprocessed data coming from the sensor, which will be in the format the sensor is outputting, for example Bayer or YCbCr data. The Processed Data is RGB output data which has been converted from Bayer or YCbCr by DevWareDevWareX. The image will also include any of the image processing pipeline that has been enabled. The Processed Data can be saved in either a 24bpp Bitmap file or 48bpp TIFF file. By default the register information is saved in the accompanying .TXT file.
Also available are the options on where to save the images. Note; if both "Auto File Name Increment and Save" and "Hold Still Image in Main Window" are disabled, the "Grab" and "Snapshot" will not be able to actual provide images to save.
After a Still Image is captured, the "Filmstrip" dialog appears if the "Hold Still Image in Main Window" option is selected. This dialog shows thumbnails of the captured image(s). The user can then right-click on the image for various options, including opening the image for view, saving the image, and selecting the type of image.
"Save Mouse Selection Rectangle Only"; only the saved image will show the rectangle-only - the filmstrip will show the full image.
...
You can use WMV instead of AVI for unlimited file length. DevWare DevWareX does not use compression with AVI. Usually the codec is just RGB-24. WMV is compressed in software.
- There is a frame rate value stored in the wmv file. There is a check box and numerical entry on the Sensor Control -> Video Record dialog page where you can provide a frame rate to put in the file. If that is not checked DevWare DevWareX uses the Display FPS.
- But that value comes from before recording started. During recording there could be considerable disk overhead or compression overhead so that the actual frame rate during recording is lower than it was before recording started. In that case the frame rate in the file will not match the actual frame rate of the recording.
...
- RAW files will play back in DevWareDevWareX, but will need to be converted to AVI to be imported into other applications. You can use DevWare DevWareX as a RAW to AVI file converter. Load the RAW file in DevWare DevWareX and verify that the image looks correct. On the Video Capture dialog page select AVI recording format and turn off Capture to RAM. Click the Stop button on the Toolbar(See 2.2.2). Click the Record button on the Toolbar(See 2.2.2).
- The "Frame rate" listed in the info.txt file (RAW only) is the rate displayed on the Info Panel "FPS (Display)".
A specific frame rate can be set via Sensor Control / Video Record "Specify playback frame rate", or via the INI file using the STATE commands "VidCap Auto Play FPS" and "VidCap Play FPS". - “Specify playback frame rate”; DevWare DevWareX video playback speed is not precise.
- MPEG-4 requires at least 20 frames to be recorded.
...
The Info dialog appears at the left edge of the DevWare DevWareX window and displays information about the image sensor, the frames displayed and the mouse position. Additionally, it has list box controls to change the mouse selection area (for use with the Analysis Dialog(See 2.2.9)) and to select between multiple sensors (only appearing if more than one sensor is attached).
Property fields:
...