66
iPORT CL-GigE External Frame Grabber User Guide
Understanding When Images are Removed from the Onboard Memory
The following actions remove the images from the CL-GigE’s onboard memory:
•
Streaming images from the onboard memory using one of the readout acquisition modes
(
ContinuousReadout
or
SingleFrameReadout
).
•
Power cycling the CL-GigE, which clears all images from the onboard memory.
•
Making any of the following
AcquisitionMode
changes and then clicking the
Play
button
(
AcquisitionStart
command):
Calculating How Many Images Can be Stored in Onboard Memory
First, take note of the
PayloadSize
, which appears under
TransportLayerControl
in the
Device Control
dialog box. Expert or Guru visibility level is required to access this feature.
The
PayloadSize
is automatically calculated by the CL-GigE based on the selected image settings, which
include Width, Height, OffsetX, OffsetY, PixelSize, any chunk data, as well as any padding that has to be
added to the image payload.
For example, for a CL-GigE configured to use Mono10p with images that are 1920 x 1080, the
PayloadSize
is equal to 2 592 000 bytes per image or 2.472 MB (2 592 000 / 1 048 576).
You can use the following equation to determine the number of images that can be saved in onboard
memory:
Available onboard memory MB / PayloadSize MB
= Number of images that can be saved
Using our example, the equation is:
120 MB / 2.472 MB = 48 images
Implementing the eBUS SDK
You can create your own image acquisition software for the CL-GigE. Consult the following guides for
information about creating custom image acquisition software:
•
eBUS SDK API Quick Start Guides
, available for C++, .NET, Linux, and macOS, which are available
on the Pleora Support Center at
.
•
eBUS SDK API Help Files
, which are installed on your computer during the installation of the eBUS
SDK. You can access this documentation from the Windows Start menu under
eBUS SDK
.
Table 23: Changes that Clear Images from the Onboard Memory
First you acquire images with...
And then you change the Acquisition mode to...
ContinuousRecording, MultiFrameRecording, or
SingleFrameRecording
Continuous, MultiFrame, or SingleFrame
SingleFrameReadout or ContinuousReadout
SingleFrame, MultiFrame, or Continuous
SingleFrameReadout or ContinuousReadout
ContinuousRecording, MultiFrameRecording, or
SingleFrameRecording