312 • Addendums Nano Series GigE Vision Camera
Nano model. The following XML code sample forms the template for the user to build bad pixel
maps for any of their Nano cameras.
Note: Identifying bad pixels is left to the user’s discretion, but Teledyne DALSA technical support
can provide guidance.
Example User Defective Pixel Map XML File
The following example shows the required components of the defective pixel map file. Each bad
pixel position (relative to the image origin which is the upper left corner), must be identified by the
XML statement:
<DefectivePixel OffsetX=”
number
” OffsetY=”
number
”/>
The pixel format (whether 8, 10, 12-bit) is handled transparently, thus requires no special
consideration by the user.
This example XML listing has four “bad” pixels identified (maximum number of entries is model
dependent). The Algorithm descriptions that follow define the rules used by the Nano firmware to
replace an identified bad pixel.
<?xml version=”1.0” encoding=”UTF-8” ?>
<!–-Example User Defective Pixel Map
<!--maximum number of coordinates dependent on sensor “Defective Pixel Replacement” value
<!–-filename: NanoExampleBadPixels.xml
<Coordinates>
<DefectivePixel OffsetX=”100” OffsetY=”0”/>
<DefectivePixel OffsetX=”28” OffsetY=”345”/>
<DefectivePixel OffsetX=”468” OffsetY=”50”/>
<DefectivePixel OffsetX=”800” OffsetY=”600”/>
</Coordinates>
An sample editable defective pixel map replacement file will be available to download with Nano
firmware files.
Monochrome Defective Pixel Replacement Algorithm
Description
The replacement algorithm follows a few basic rules as defined below, which in general provides
satisfactory results. There is no embedded intelligence to adapt the rules to avoid replacing a bad
pixel with possibly other bad data.
Monochrome Sensors (case 1: single bad pixel)
• A bad even pixel is replaced by the good odd pixel of the same pixel pair.
• A bad odd pixel is replaced by the good even pixel of the same pixel pair.
To Next Page
Loading...
Need help?
General
