eBUS SDK .NET API
  • Getting Started
    • Getting started with the eBUS SDK .NET API
    • Configuring Your IDE
    • Receiving Data from a GigE Vision or USB3 Vision Transmitter
    • Sample Applications
    • GigE Vision Device Communication Parameters
    • USB3 Vision Device Communication Parameters
    • PvStream USB3 Vision Parameters
    • PvStream GigE Vision Parameters
  • eBUS SDK .NET API Reference
    • API Overview
    • eBUSDotNet
    • eBUSDotNetReceive
    • eBUSDotNetEdge
Search Results for

    Show / Hide Table of Contents
    • Getting started with the eBUS SDK .NET API
    • Configuring Your IDE
    • Receiving Data from a GigE Vision or USB3 Vision Transmitter
    • Sample Applications
    • GigE Vision Device Communication Parameters
    • USB3 Vision Device Communication Parameters
    • PvStream USB3 Vision Parameters
    • PvStream GigE Vision Parameters

    Receiving Data from a GigE Vision or USB3 Vision Transmitter


    For the latest eBUS SDK documentation and support, visit https://supportcenter.pleora.com
    Getting started with the eBUS SDK .NET API


    A GigE Vision or USB3 Vision device (transmitter) transmits blocks of data (such as images) over a network or USB connection.

    The software component that receives and assembles streaming packets into a usable block of memory is commonly referred to as a data receiver.

    For GigE Vision, a filter driver called eBUS Universal Pro is bundled with the eBUS SDK and can optionally be applied to a network adapter in order to maximize streaming performance (bypassing the standard network stack to achieve lower CPU usage and better data throughput).

    For USB3 Vision, a USB driver bundled with the eBUS SDK must be installed and used to communicate with USB3 Vision devices. Streaming from USB3 Vision devices is handled by this driver.

    PvStream is the base class which contains all the methods common to both PvStreamGEV and PvStreamU3V.

    PvStream provides access to a PvGenParameterArray containing all the data receiver properties and statistics. The parameters are different for GigE Vision and USB3 Vision data receivers.

    The process of receiving data from a transmitter involves queuing buffers into the data receiver ensuring that there are always buffers available for the incoming data. A PvStream object is normally used in conjunction with a PvPipeline object which helps manage the process of allocating and pushing buffers into the data receiver as needed.

    Opening a PvPipeline object allocates a pool of available buffers (configurable by calling PvPipeline.SetBufferCount(System.UInt32) and PvPipeline.SetBufferSize(System.UInt32)) and starts a thread that continually feeds buffers into the data receiver. Each time a new block (such as an image or raw data) becomes available, its associated buffer is placed in a queue of available buffers that can be retrieved by calling PvPipeline.RetrieveNextBuffer(System.Int32).

    If the calling application cannot retrieve buffers at the rate that data is arriving, buffers are silently dropped. To obtain a count of dropped buffers, refer to the stream parameters accessible from PvStream.Parameters .

    To control a GigE Vision or USB3 Vision device (i.e. tell it when and where to transmit data), the eBUS SDK provides a class called PvDevice. For a complete working sample that connects to a device, opens a stream and tells the device when and where to begin streaming, refer to the PvPipelineSample included with the SDK.

    In some cases, it may be desirable for an application to manage the process of allocating and pushing buffers into the data receiver without making use of a PvPipeline object. For complete working samples that incorporate this concept, refer to PvStreamSample.


    See Also

    Reference
    PvStream
    PvStreamGEV
    PvStreamU3V
    PvPipeline
    PvDevice



    eBUS SDK | Pleora Technologies Inc.
    Copyright (c) 2002-2026 Pleora Technologies Inc.

    Send comments on this topic to info@pleora.com

    • Edit this page
    In this article
    Back to top Generated by DocFX