Page Comparison

<type> [, RANGE= <min>:<max>] //<comment>

Defines a data type and optional valid range for a register or bitfield. The data type is used by DevWare when displaying the value in decimal format in the Registers window and Watch window. The range is used for the slider control on the Registers window.

Possible values for <type> are: unsigned, signed (2's complement), signmag (sign-magnitude), fixed1…fixed32 (2's complement fixed-point), ufixed1…ufixed32, float16, float (IEEE single precision).

Example: RED_GAIN register has five fractional bits.
DATATYPE = RED_GAIN, ufixed5
Example: CAM_HUE_ANGLE is signed and ranges from -22 to 22.
DATATYPE= CAM_HUE_ANGLE, signed, RANGE= -22:22

on the first attached camera. The <page> parameter is required. If the sensor doesn't use paged register addressing use 0 for the page number.

The optional mask parameter lets you set a bitfield, like the BITFIELD command.
Example: Set bit 5 in register 0x3044 on the attached camera
FAR1= 0, 0x3044, 0x0020, 1

Defines the icon image and button state for a User Toolbar button in DevWare. Only takes effect if the preset name begins with “Toolbar:” or “Toolbar2:”.

If the <icon name> contains a dot “.” character, it's interpreted as a filename with a path relative to the ini file. The icon file can be a .ico or a .bmp (24x24 pixels, 32-bpp, R-G-B-alpha) file.

Example: Load icon from file zoom.ico.
ICON = zoom.ico

Otherwise the name specifies a built-in icon image. The built-in images are different colored shapes. Specify the shape and color. The shapes are circle, square, triangle and star. The colors are black, brown, red, orange, yellow, green, blue, violet, gray and white.

Example: Use a built-in icon image.
ICON= green square.

Optionally you can define the 'checked' (pressed-in) and enabled (not grayed out) state for the button, based on the value of a register, bitfield or DevWare STATE variable. The <condition> can be ==, !=, <, >, <=, or >= followed by a numerical constant. Use the RADIO keyword for a group of mutually exclusive buttons. Use the CHECKED keyword for independent buttons.

Example: Load icon from file antishake.bmp, and declare that the button should be pressed-in when SEQ_STATE_CFG_2_AS equals 1 and not pressed otherwise.
ICON= antishake.bmp, CHECKED= SEQ_STATE_CFG_2_AS == 1

Example: Load icon from file Zoom1.bmp, and declare that the button should be pressed-in when the DevWare STATE variable Display Zoom Percent equals 100.
ICON= Zoom1.bmp, CHECKED= STATE:Display Zoom Percent == 100

See also the MENUITEM= and TOOLTIP= commands.

register.

Example: Read register SHUTTER_WIDTH_LIM_AE, if it is greater than 0x100, load preset [Night mode], otherwise, load preset [

Day mode].
IF_

FIELD= SHUTTER_WIDTH_LIM_AE,>0x100, LOAD=

Night mode, ELSELOAD=

Day mode

Context is optional, and represents the context number to apply the settings to.  Value is 0 to n, where n is the maximum number of contexts - 1.

Example: Tell the software that the sensor output will be 808 x 608, 10-bit Bayer.
IMAGE = 808, 608, BAYER-10, 0

name>|:<mask>]|STATE:<STATE variable> <condition>][,SHORTCUT=<key combination>]  //<comment>

Defines a drop-down menu item for a User Toolbar button in DevWare. Only takes effect if the preset name begins with "Toolbar:" or "Toolbar2:". This command causes the toolbar button behavior to change to a drop-down menu action.

The

83269893=, CHECKED=, RADIO= and ENABLED= attributes work as in the ICON= command, except they apply only to the menu item, not the toolbar button. The icon file must be a .bmp (32-bpp, R-G-B-alpha) file, 13x13 pixels for the normal Windows text size. SHORTCUT= attribute works like the SHORTCUT= command, but applies only to this menu item.

If ICON= is used then CHECKED= or RADIO= will may have no visible effect depending on OS or GUI library.

The maximum number of menu items on a single toolbar button is 25.

Example: Group multiple presets under one button, with a separator between Parallel and HiSPi.
[Toolbar: 1280x720]
MENUITEM= "Parallel 1280x720 36.19fps", LOAD= Parallel 1280x720 36.19fps XBin2YBin2_BinSum
MENUITEM= "Parallel 1280x720 51.69fps", LOAD= Parallel 1280x720 51.69fps XBin2YSkip2_ColSum2
MENUITEM="-"
MENUITEM= "HiSPi 1280x720 51.69fps", LOAD= HiSPi 1280x720 51.69fps XBin2YSkip2_ColSum2

Example: Image Orientation control for a SMIA sensor using radio button icons
[Toolbar: Orientation]
MENUITEM= "Normal", LOAD= Normal, RADIO= IMAGE_ORIENTATION==0
MENUITEM= "Mirror", LOAD= Horiz Mirror, RADIO= IMAGE_ORIENTATION==1
MENUITEM= "Flip", LOAD= Vertical Flip, RADIO= IMAGE_ORIENTATION==2
MENUITEM= "Rotate 180", LOAD= Rotate 180, RADIO= IMAGE_ORIENTATION==3
[Normal]
FIELD_WR= IMAGE_ORIENTATION, 0
[Horiz Mirror]
FIELD_WR= IMAGE_ORIENTATION, 1
[Vertical Flip]
FIELD_WR= IMAGE_ORIENTATION, 2
[Rotate 180]
FIELD_WR= IMAGE_ORIENTATION, 3

Note: if "LOAD=" is not supplied, then that MENUITEM will be disabled but still displayed. 
To to provide visual separators between MENUITEM sections, use MENUITEM= "-".

See also the ICON=, SHORTCUT= and TOOLTIP= commands.

automatically added so the user can choose to do nothing. The user can stop execution of the current preset by clicking Cancel.

"OKONLY" is optional. When present and the user does not select "OK", a new Prompt will be displaying warning the user that not selecting OK may have unintended results.
The choices are optional. If there are no choices then the dialog only shows the message and OK and Cancel buttons that will continue execution of the current preset or stop

execution.

Commas are allowed inside quoted strings. The \n sequence in the message will convert to a newline.

Example: Ask user whether to do parallel or serial configuration.
PROMPT= "Is this camera using a parallel or serial interface?", "Parallel". LOAD=Parallel Init, "Serial", LOAD=Serial Init

USB has a limit of 64 bytes per command, so that is the limit. DevWare allows the REG_BURST command to be any length, but if it is longer than 64 bytes (including the address at the beginning) then it will be split into several commands.

Example: Set registers 0xC8 through 0xCB on page 1
REG_BURST= 1, 0xC8, 0x03A1, 0x4444, 0xC902, 0x3E56

Usage rules for filename:

1. If only a file name is given, it will be saved at the location set in "Image Save Options".
2. If a path is supplied, it must be a full path including a leading drive and/or "\" - relative paths are not supported.
3. If a path is supplied and a folder doesn't exist in that path, only a single folder can be created in the path.
The folder to be created can be either a single folder (e.g. c:\f1 - f1 is created) or the last folder in the path (e.g c:\f1\f2 - f1 exists and f2 is created).

Example:
SAVE_IMAGE = capture.raw

Note:

using a built-in shortcut used by DevWare can disable it; see section 2.2.2 of the DevWare Detailed documentation for a list of built-in shortcuts.

Any key can be used for the shortcut, for example SHORTCUT= Z, or SHORTCUT=

F7. The key name is not case-sensitive. Also modifier keys Shift, Ctrl and Alt can be specified with the key name. Use a plus sign + between the modifier key name and the main key name, for example SHORTCUT= Shift+F6, or SHORTCUT= Ctrl+E. Multiple modifiers can be used, for example SHORTCUT= Ctrl+Shift+F6. The modifiers must come before the main key name, but they can be in any order. Spaces between the modifier and key name are OK.

When deciding on shortcut keys, keep in mind the keyboard layout and existing conventions. For example Shift+= is impossible on U.S. keyboards as the = sign is on the unshifted key. On some international keyboards the opposite may be true. Also, keys like Home may have different names on international keyboards. But always specify modifier keys with "Shift", "Ctrl" and "Alt" (the U.S. keyboard names) even for international keyboards. The Alt key is typically used for menu navigation, so it's use should be limited to a few function keys, or avoided.

SHORTCUT= key definitions will override the default key definitions in DevWare, so this feature can be used to reassign keys if you don't need the default action. These key assignments (as well as the default key assignments) only take effect when the main DevWare window has keyboard focus, not if a dialog or other UI control has keyboard focus. This means that it is OK to use numbers and letters for shortcuts, and you will still be able to enter text in edit boxes, etc.

Example: Define a keyboard shortcut for a toolbar button.
[Toolbar: Zoom 1X]
SHORTCUT= Ctrl+1

STATE Variables for a list of supported states.

Example: Set Auto Exposure Target to 50
STATE= Auto Exposure Target, 50