Cheetah Pregius Camera with GigE Vision
®
Interface – User Manual
August 27, 2019
Page
112
of
123
Rev 1.0
5.17 Configuration Memory
The camera has built-in configuration memory divided into four segments: Work Space,
Factory Space (Default), User Space #1, #2, #3 or #4. The Work Space segment contains the
current camera settings while the camera is powered up and operational. All camera registers
are located in this space. You can program these registers and change the camera
configuration through these registers.
The Work Space is RAM based. All camera registers clear upon camera power-down. The
Factory Space (Default) segment is ROM based, write protected, and contains the default
camera settings. This space is available for read operations only. User Space #1, #2, #3 and #4
are non-volatile, flash-based, and used to store up to four user defined configurations or User
Sets. Upon power up or software reset, the camera firmware loads the Work Space registers
from the Factory Space (Default), User Space #1, #2, #3 or #4 as determined by a User Set
Default Selector setting. At any time, a user can instruct the camera to load its Work Space
with the contents of the Factory Space, User Space #1, #2, #3 or #4 using the User Set Load
command. Similarly, the user can instruct the camera to save the current Work Space settings
into either User Space #1, #2, #3 or #4 using the User Set Save command.
The non-volatile parameter Flash memory also contains the Bad Pixel Map (BPM), Flat Field
Correction (FFC) tables and LUT #1, #2, #3 and #4 which you can load to the camera’s internal
memory upon enabling the corresponding camera feature. You can create custom LUT tables
using the Imperx IPX Toolkit utility and upload these tables to the parameter Flash using the
Imperx Upload Utility. Both the IPX Toolkit and IPX Upload Utility are available from the
.Imperx also has an application note describing
how to update or create custom Bad Pixel Maps (BPM) which can then be uploaded to the
camera using the Imperx Upload Utility.
