Allied Vision Technologies GigE SDK API详细编程指南

需积分: 10 173 浏览量更新于2024-07-18 收藏 815KB PDF 举报

本资源是 Allied Vision Technologies (AVT) 的 GigE Vision 驱动程序及其 Application Programming Interface (API) 的程序员参考手册，版本为 V1.28，发布日期为 2015 年 3 月 20 日。AVT 提供的 PvAPI 接口适用于其所有的 GigE Vision 相机系列，包括但不限于各个家族的产品。该文档详细阐述了如何与 Allied Vision 的 GigE Vision 相机进行编程交互，涵盖了从联系公司、安装驱动到使用 API 的全方位指导。在使用方面，手册首先介绍了如何通过正确的平台（如 Windows 或 Linux）以及支持的编程语言（如 C++ 或 Python）来操作。它强调了多线程处理，确保了在并发应用程序中的稳定性和性能。此外，文档还涉及了驱动的分发和安装过程，包括AVTGigE Filter Driver 的使用。核心内容部分深入讲解了 API 的功能和操作方法，如如何列出可用的相机、打开相机并访问其属性，例如获取或设置布尔型、枚举型、浮点型、整数类型等属性值。图像捕获与帧队列管理也被详细讨论，比如如何利用模式激活/tPvFrame->AncillaryBuffer 功能，以及错误代码的识别和处理。对于 API 的函数引用部分，手册列举了众多功能，如 PvAttrBooleanGet 和 PvAttrBooleanSet 用于操作布尔型属性，PvAttrEnumGet 和 PvAttrEnumSet 用于枚举值的获取和设置，PvAttrInfo 则提供了关于属性的信息。还有针对不同数据类型的属性操作方法，如 PvAttrFloat32Get 和 PvAttrFloat32Set，以及字符串操作函数 PvAttrStringGet。这份指南为开发者提供了一个全面的工具，使他们能够有效地利用 Allied Vision Technologies 的 GigE Vision SDK API 进行高效且兼容的相机控制和图像处理。无论是初次接触该技术的开发者还是经验丰富的专业人士，都能从中找到所需的信息以实现高效的工作流程。

Using the API

AVT PvAPI Programmer’s Reference Manual V1.28

2. PvCaptureQueueFrame – queue frame buffer(s). As images arrive from the

camera, they are placed in the next frame buffer in the queue, and

returned to the user. More on frame queuing in the next section.

3. PvCaptureEnd – close the capture stream on driver.

Host/driver calls set up the host/driver to receive data from the camera.

Camera calls:

1. AcquisitionStart attribute – readies camera to receive frame triggers.

2. AcquisitionMode attribute – determines how many frame triggers the

camera receives.

3. FrameStartTriggerMode attribute – determines how frames are triggered.

4. AcquisitionStop – stops camera from receiving frame triggers.

Camera calls start the camera imaging, and sending data to host.

Example workflow:

//start driver stream

PvCaptureStart(Camera);

//queue frame

PvCaptureQueueFrame(Camera, Frame, NULL);

//set frame triggers to be generated internally

PvAttrEnumSet(Camera, "FrameStartTriggerMode", "Freerun");

//set camera to receive continuous number of frame triggers

PvAttrEnumSet(Camera, "AcquisitionMode", "Continuous");

//start camera receiving frame triggers

PvCommandRun(Camera, "AcquisitionStart");

do {

//wait for frame to return to host

PvCaptureWaitForFrameDone(Camera, Frame, PVINFINITE);

//do something with returned frame

//*****************

//requeue frame

PvCaptureQueueFrame(Camera, Frame, NULL);

}

while (some condition);

To guarantee a particular image is captured, you must ensure that a frame

buffer is queued before the camera is sent a frame trigger.

Frame Queuing

Frames are structures containing image data and related info. See tPvFrame in

PvApi.h. Users are responsible for managing their own queue of frames. This

allows for flexibility in how the queue is managed. Example queues: a 3 buffer

circular queue, 100 frame one time use queue.

To create a frame, fill out a tPvFrame structure with associated tPvFrame →

ImageBuffer (use attribute TotalBytesPerFrame to calculate ImageBuffer size),

and place the frame structure on the queue with PvCaptureQueueFrame.

Using the API

AVT PvAPI Programmer’s Reference Manual V1.28

ModeActive / tPvFrame->AncillaryBuffer

As of latest camera firmware, frames may also receive the associated chunk

mode data from the camera:

To enable the receiving of this data, allocate your tPvFrame →AncillaryBuffer

and enable the ChunkModeActive attribute. AncillaryBufferSize =

NonImagePayloadSize attribute value, valid when ChunkModeActive = True.

[Bytes 1 – 4] Acquisition count

[Byte 5] These 8 bits indicate the following EF lens settings:

• Bit 7 (Error): When this bit is set to 1, the EF lens is in an error state, bits 2 – 5 indicate enumerated

value of last error, and all other bits and Bytes will be 0.

• Bit 6 (Lens attached): When this bit is set to 1, an EF lens is attached to camera.

• Bit 5 (Auto focus): When this bit is set to 1, the EF lens manual/auto focus switch is set to the auto

focus position.

• Bits 2 – 4 (Last error): Enumerated error value:

– 0: No error detected

–1: Lens failed query by camera

– 2: Lens communication error (can occur when removing lens)

– 3: Lens communication error (can occur when removing lens)

– 4: Lens remained busy for longer than 10 seconds

– 5: Lens focus “Zero Stop” not detected

– 6: Lens focus “Infinity Stop” not detected

• Bits 0 – 1: Upper 2 bits of focus percentage value (see Byte 6).

[Byte 6] These 8 bits in conjunction with bits 0 – 1 of Byte 5, indicate the current focus position of the EF

lens in (percentage of maximum focus range) * 10 (i.e. 1000 = 100 percent = Infinity Stop).

If the lens manual/auto focus switch is in the manual position these bits will be 0.

[Byte7] These 8 bits indicate the current aperture position of the EF lens in Dn. To convert Dn to FStop

value, use formula: FStop = 2 (Dn – 8) /16.

[Byte 8] These 8 bits indicate the current focal length of the EF lens in mm.

[Bytes 9 – 12] Exposure value in μs.

[Bytes 13 – 16] Gain value in dB.

[Bytes 17 – 18] Sync in levels. A bit field. Bit 0 is sync-in 0, bit 1 is sync-in 1, etc. A bit value of 1 = level

high, and a bit value of 0 = level low.

[Bytes 19 – 20] Sync out levels. A bit field. Bit 0 is sync-out 0, bit 1 is sync-out 1, etc. A bit value of 1 =

level high, and a bit value of 0 = level low.

[Bytes 21 – 24] Reserved. 0

[Bytes 25 – 28] Reserved. 0

[Bytes 29 – 32] Reserved. 0

[Bytes 33 – 36] Reserved. 0

[Bytes 37 – 40] Reserved. 0

[Bytes 41 – 44] Chunk ID. 1000

[Bytes 45 – 48] Chunk length.

剩余64页未读，继续阅读

weixin_40902111

粉丝: 0
资源: 1

Allied Vision Technologies GigE SDK API详细编程指南

GigEVisionSDK_Interface.chm

GigE-Vision-2.0中文版.pdf

（Allied Vision）Avt的使用文档

<AvtGigE_api.h>

依据Vimba Cpp Manual开发一个将GigE相机图像数据传输到ARM核上的程序

能否找到Vimba armv7 32-bit版的下载途径

AVT::VmbAPI::VimbaSystem& GetVimbaSystem()是什么意思

AVT::VmbAPI::VimbaSystem& GetVimbaSystem()中& 的作用是什么

allied standard avionics architecture council(asaac)标准体系架构

Drow Ranger

最新资源