SICK Ranger E

Reference Manual Chapter 8
Ranger E/D
©SICK AG • Advanced Industrial Sensors • www.sick.com • All rights reserved 93
iCon API
0 1 2 3 4 n
……
Figure 8.3 – Example of an IconBuffer when measuring with a Hi3D and a Gray compo-
nent
The order in which the profiles are stored in a scan cannot be known in advance. The data
type – byte, word or double – of each measurement value is also dependent on the cur-
rent configuration. Within a profile, the values are however always stored in sequence –
that is, the first value is from column 1 in the ROI, the next from column 2, etc.
The order and format of the measurement data is described by a data format, which can
be retrieved from the camera. This data format can be passed to the FrameGrabber
object and transformed into a DataFormat object, which your application can use for
locating the requested profile within a scan.
The DataFormat object contains Component objects, which each corresponds to an
enabled measurement component in the current configuration. Each Component object
consists of one or more SubComponent objects, where a sub-component corresponds to
a type of profile.
Figure 8.4 –Data format
8.2.2 Accessing the Measurement Data
To access a single scan within a buffer, you call the getReadPointer() or -
getWritePointer() method of the buffer, to get a pointer to the beginning of the
scan’s measurement data.
Component
Sub-
component
offset()
Range profile from
Hi3D component
Intensity profile from
Hi3D component
Intensity profile from
Gray component
offset
Scan 1
Scan 2
…
IconBuffer
Data Format
IconBuffer
Gray
Hi3D
Intensity
Range
Intensity
Scan 1
Scan 2
…