Standard Features AW00011916000
310 Basler scout GigE
12.15 Event Reporting
Event reporting is available on the camera. With event reporting, the camera can generate an
"event" and after some intermediate steps transmit a related event message to the PC whenever a
specific situation has occurred:
The camera can generate and transmit events for these types of situations:
An acquisition start trigger has occurred (AcquisitionStartEventData)
Overtriggering of the acquisition start trigger has occurred
(AcquisitionStartOvertriggerEventData)
A frame start trigger has occurred (FrameStartEventData)
Overtriggering of the frame start trigger has occurred (FrameStartOvertriggerEventData)
The end of an exposure has occurred (ExposureEndEventData)
An event overrun has occurred (EventOverrunEventData); see below for more information.
An Example of Event Reporting
An example related to the Exposure End event illustrates how event reporting works. The example
assumes that your system is set for event reporting (see below), and that an end of exposure has
just occurred in the camera. In this case:
1. An Exposure End event is generated. The event contains the event in the strict sense and sup-
plementary information:
An Event Type Identifier. In this case, the identifier would show that an exposure end type
event has occurred.
A Frame ID. This number indicates the frame count at the time that the event occurred.
A Stream Channel Identifier. Currently this identifier is always 0.
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 unit for the timer is "ticks" where
one tick = 8 ns. The timestamp is a 64 bit value.)
2. The event is placed in an internal queue in the camera.
3. As soon as network transmission time is available, an event message will be sent to the PC.
If only one event is in the queue, the message will contain the single event. If more than one
event is in the queue, the message will contain multiple events.
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.
During the time that the camera is waiting for an acknowledgement, no new event
messages can be transmitted.
4. Event Reporting involves some further software-related steps and settings to be made. For
more information, see the "Camera Events" code sample included with the pylon software
development kit.