Short Description
Coaxlink products feature a powerful event management that allows the application to be notified of the occurrence of various events.
In addition to the GenTL standard EVENT_NEW_BUFFER event, the Coaxlink GenTL producer provide a wide set of custom event sources. The event sources are grouped by types according to the function block and the GenTL module they belong to.
Each custom event source is associated with a counter that counts the number of occurrences.
For each notified custom event, the following event context data is recorded and made available to the application:
- Identifier of the event source
- Time stamp (expressed in microseconds)
- 3 user-defined context data
Each individual event source is configurable:
- The event notification can enabled or disabled.
- The content of each user-defined context data.
Event data are temporarily stored in the Event Queue Buffer. The Coaxlink Driver is notified, using an interruption mechanism, of the availability of one or more event entries in the Coaxlink Event Queue Buffer.
The Coaxlink Driver implements the GenTL signaling mechanism for reporting the occurrence of asynchronous events to the application software.
The EGrabber API provides 3 callback threading models:
- CallbackOnDemand: This is the simplest model which gives complete control over when and how callbacks are invoked. Events are processed on demand.
- CallbackSingleThread: This model delivers events to callbacks in their chronological order, sequentially, in a dedicated thread context. Events are processed automatically as soon as they are available.
- CallbackMultiThread: This model delivers events to callbacks in separate threads (one thread per event DATA type). Events are processed automatically as soon as they are available.