Back to FabImage Library website
You are here: Start » Function Reference » Camera Support » Basler » Pylon_GetUsbStatistics
Header: | ThirdPartySdk.h |
---|---|
Namespace: | fil |
Module: | ThirdParty |
Gets GigeVision device statistics data.
Syntax
void fil::Pylon_GetUsbStatistics ( Pylon_State& ioState, ftl::Optional<const ftl::String&> inDeviceID, ftl::int64& outTotalBufferCount, ftl::int64& outFailedBufferCount, ftl::int64& outLastFailedBufferStatus, ftl::String& outLastFailedBufferStatusText, ftl::int64& outMissedFrameCount, ftl::int64& outResynchronizationCount, ftl::int64& outLastBlockId, ftl::int64& outNumEmptyBuffers, ftl::int64& outNumQueuedBuffers, ftl::int64& outNumReadyBuffers, ftl::int64& outOutputQueueSize )
Parameters
Name | Type | Default | Description | |
---|---|---|---|---|
![]() |
ioState | Pylon_State& | Object used to maintain state of the function. | |
![]() |
inDeviceID | Optional<const String&> | NIL | Device identifying address |
![]() |
outTotalBufferCount | int64& | The total count of processed buffers | |
![]() |
outFailedBufferCount | int64& | The count of buffers that returned with an error status | |
![]() |
outLastFailedBufferStatus | int64& | The status code of the last failed buffer | |
![]() |
outLastFailedBufferStatusText | String& | The message text of the status code of the last failed buffer | |
![]() |
outMissedFrameCount | int64& | The count of bad or missed frames between successfully grabbed images | |
![]() |
outResynchronizationCount | int64& | The count of stream resynchronizations | |
![]() |
outLastBlockId | int64& | The last grabbed block ID | |
![]() |
outNumEmptyBuffers | int64& | The number of empty buffers that are not used for grabbing yet | |
![]() |
outNumQueuedBuffers | int64& | The number of buffers queued at Low Level API stream grabber | |
![]() |
outNumReadyBuffers | int64& | The number of grab result buffers in the output queue that are ready for retrieval | |
![]() |
outOutputQueueSize | int64& | The size of the grab result buffer output queue |
Multithreaded environment
This function is not guaranteed to be thread-safe. When used in multithreaded environment, it has to be manually synchronized.