Page Comparison

Sensor

The ON Semiconductor Imaging sensor being used (only appears if value is different than "Part Number").

Part numberNumber

The ON Semiconductor part number for this sensor.

Sensor version

The version of the image sensor.

Sensor type

Either 'Bayer' or 'SOC' sensor.

Software:

Build name

The version and type of build (either Release or Beta).

Build version

The full version number (major.minor.revision.build) of the DevWareX application.

Build date

Date the software was compiled. (MM/DD/YYYY)

Demo Board:

Type of Demo board being used (for example: DEMO2X or DEMO3).
Note: The FW version and FPGA version is displayed in parentheses.

Firmware

Array Clock

The oscillator frequency being used (in MHz).
Note: This value can be modified by the user through the Options Dialog(See 2.2.15).

Pixel Output Clock

The pixel clock output as calculated by DevWareX based on the specific configuration of the attached device.
It is intended to be the pixel rate at the sensor output.
DevWareX has different ways of deriving clocks from each other.  In most cases, array clock was derived from external clock, and then pixel clock was derived from array clock.

Array Clock is nominally the sensor array clock. It's the clock used to calculate row time, exposure time, etc.
Pixel Clock is PIXCLK for the parallel interface, or the pixel rate. There is also Input Clock which is the clock input to the sensor.

Normally, the clock rates are re-measured when a PLL register is changed. Depending on the demo kit configuration, it may not be possible to measure the clocks from software. Demo2X can measure PIXCLK if the sensor is streaming in parallel mode. Demo3 can measure Input Clock if it is hooked up to the Demo3 clock sense line. Once one of the clocks is measured, the other two can be calculated from the PLL settings.

The clock speed on the Options dialog sets the Array Clock value (in case DevWareX can't measure it), and Pixel Clock and Input Clock will be automatically calculated according to the PLL settings.

Width

The pixel width of the displayed sensor image.

Height

The pixel height of the displayed sensor image.

FormatImage Type

The current sensor image format (for example 'YCbCr', 'Bayer 8', 'Bayer 10', etc.).

Frames

A frame counter that gets increased for each displayed sensor image.

Dropped frames

Dropped frames are possible under the following circumstances:

• The application couldn't determine the end-of-frame because of a change in the data flow (this is not a sensor issue).
• The image data is sent faster then the computer can handle. This can happen on slower PC's/laptops or when other applications are slowing down the computer.
  To view the dropped (incomplete) frames regardless, go to the Options Dialog(See 2.2.15) and enable 'Debug Mode (show dropped frames)'.

FPS (Sensor)

The computed number of Frames Per Second that the sensor is running at based on register settings and oscillator (see Clock above) value.
Note: SOC sensors dynamically change the frame rate for exposure purposes. To update the FPS number click the 'Refresh' button at the bottom of the main Sensor Control dialog(See 2.2.4).

FPS (Datalink)

The number of Frames Per Second that the camera sends to the host computer via USB (or other data link). This number can be influenced by the speed of the computer, or the host controller and drivers.

FPS (Display)

The number of Frames Per Second that are displayed on the computer. A camera frame is first converted from its native format (see above) to a 32bit RGB image and finally converted to the display adapter's resolution (preferably also 32 bit). Software image processing can slow down the display frame rate. The display frame rate is also affected by the host computer's display drivers. The Accelerated selection on the Options(See 2.2.15) dialog can help.

Cursor pos

The mouse cursor position when the mouse is over the display area. Expressed as a positive (width, height) value relative to the upper-right most pixel (0,0).

Raw Data

The unprocessed sensor data at the mouse cursor position. For SOC sensors the data is separated into Y, Cb, and Cr values. For Bayer sensors there is a single data value, with the Bayer color pattern position indicated in parentheses (R, Gr, Gb, or B).

R: Output

The value of the Red component of the displayed image at the mouse cursor position.

G: Output

The value of the Green component of the displayed image at the mouse cursor position.

B: Output

The value of the Blue component of the displayed image at the mouse cursor position.

Open Sensor Data File 

Open a specific sensor data (SDAT) file for the current sensor.

Open Image or Video File

Open an image file and display the image, instead of a sensor.

Open Default Presets

Open Default Presets

Open an INI file as the default presets file. (same as the Browse... button on the Presets dialog).

Open Additional Presets

Open an INI file as an additional presets file. This INI file will not affect the dfault presets file, and it will not be used to specify the actions of the DevWareX toolbar.

Refresh Register List

Reopen a specific sensor data (SDAT) file for the current sensor(Using file browse).

Probe for Devices

Re-run the device probe that will determine what sensor you have attached and automatically select the right SDAT file.

Capture Image

Capture the currently displayed sensor image to hard disk <F9 >.

Take Snapshot

Capture the sensor image to hard disk <Ctrl-F9 >.

Record Video

Record the image stream to hard disk Note: the video is uncompressed and will take significant hard disk space. This mode is for characterization only.

Exit

Exit the application. <Alt-F4>.

Help Topics

Offers you an index to topics on which you can get help.

Bug report

When you find a problem with this software, please file for a bug report by following the information in the Bug Report Dialog.

About

Version and copyright information.