Features
214 Basler pilot
However if you are operating the camera at high frame rates with a small AOI, the camera may be
able to generate and queue events faster than they can be transmitted and acknowledged. In this
case:
1. The queue will fill and events will be dropped.
2. An event overrun will occur.
3. Assuming that you have event overrun reporting enabled, the camera will generate an "event
overrun event" and place it in the queue.
4. As soon as transmission time is available, an event message containing the event overrun
event will be transmitted to the PC.
The event overrun event is simply a warning that events are being dropped. The notification
contains no specific information about how many or which events have been dropped.
Setting Your System for Event Reporting
To use event reporting, two conditions must be met:
Event reporting must be enabled in the camera
A pylon "event grabber" must be created within your application (assuming that you are using
the pylon API)
The main purpose of the pylon event grabber is to receive incoming event messages.
Another purpose of the pylon event grabber is to handle event message acknowledgement. The
values for the event message timeout and the event message retry count are set via the event
grabber.
An event adapter object of the event grabber can be used to parse the information contained within
each event message.
You can enable event reporting, create a pylon event grabber, and use the event adapter object
from within your application software by using the pylon API. The pylon software development kit
includes a "Camera Events" code sample that illustrates the entire process.
For more detailed information about using the pylon API, refer to the Basler pylon Programmer’s
Guide and API Reference.
To Next Page
Loading...
Need help?
General
