AW00123409000 Features
Basler ace USB 3.0 315
An Example of Event Notification
An example related to the Frame Start Overtrigger event illustrates how event notification works.
The example assumes that your system is set for event notification (see below) and that the camera
has received an external frame start trigger when the camera is not in a "waiting for frame start
trigger" acquisition status. In this case:
1. A Frame Start Overtrigger event is created. The event contains the event in the strict sense
plus supplementary information:
An Event Type Identifier. In this case, the identifier would show that a frame start overtrigger
type event has occurred.
A Timestamp. This is a timestamp indicating when the event occurred. (The time stamp
timer starts running at power off/on or at camera reset. The timestamp [ns] is a 64 bit value.)
2. The event message will be sent to the computer if transmission time is available and if no
major number of younger event messages were generated.
a. After the camera sends an event message, it waits for an acknowledgement. If no
acknowledgement is received within a specified timeout, the camera will resend the event
message. If an acknowledgement is still not received, the timeout and resend mechanism
will repeat until a specified maximum number of retries is reached. If the maximum number
of retries is reached and no acknowledge has been received, the message will be dropped.
While the camera is waiting for an acknowledgement, no new event messages can be
transmitted.
3. Event notification involves making some additional software-related steps and settings. For
more information, see the "Camera Events" code sample included with the pylon software
development kit.
To Next Page
Loading...
Need help?
General
