Database Setup

Setup in QINSy template database

On this page:

Add Eventing System


There are two choices for the Eventing System driver: one has an interactive dialog box online from which events are fired and event properties are entered, the other does not.
In terms of driver definition in Database Setup the only difference is which driver is selected.

Please refer to the mother page 'How-to Eventing' for information on how the two drivers differ in practice.

Start Database Setup

  • Add System of type 'Eventing System' to the template.
  • Select as driver 'Generic Eventing System' (or 'Generic Eventing System (No User Interface)').
  • Select the Event Definitions, i.e. the previously created *.xml file.
    If multiple Event Xml's are found all are shown in the Event Definitions drop down list.

  • Press the Finish button and save the template database.

Add Miscellaneous Drivers

It is possible to use values input from an external system to:

  • Automatically trigger an event to fire on receipt of an input number string that matches an event ID number in the Xml file.
  • Modify the output of event data and reports based on recorded observation values from a Miscellaneous System.

Automatic firing of event when online

If data recording is required to start on deployment of a towed body (maybe a dredge head or a trenching tool) it can be done if the winch sends a signal (say the number '1') to QINSy when the deployment starts, and another signal (say the number '2') when the towed body is recovered.

If a 'Start Tow' event has an ID of '1' and an 'End Tow' event has an ID of '2', the Eventing Driver can be set up in such a way that when a '1' is received from the winch system, the 'Start Tow' event is automatically fired.
If the action 'Select mainline and start recording' is associated with the 'Start Tow' event, receipt of the number '1' will both fire the event and start recording.
Receipt of a value '2' from the winch system automatically triggers the 'End Tow' event, which, if associated with the 'End recording' action also stops online recording.

To make this work, in the Generic Eventing Driver window online, select Options from the Events menu.
At the bottom of the page activate 'Enable from observation' and select the deployment observation.

Another example comes from the dredging industry.
A number of observations received from a PLC (programmable logic controller) are defined in a Miscellaneous System. 
The 'Status Dredging' observation is received as either a '0=Not Dredging' or a '1=Dredging'.
As above this value can be used to automatically fire both the Start Dredging event and data recording.

Enable Modification of Event Data Export and Report

Many of the other miscellaneous observations cited above can be used to tailor the Event Editor output to file and to report - see Event Editor Report Options.

Eventing Support for Generic Data Logger (ASCII Logging) & Generic Display

When a generic eventing system is defined in the template database setup, the Generic Data Logger System and Generic Display can be used to show and export the event data.
All kinds of eventing related items can be displayed while generating events online.

Add Generic ASCII Data Logger System

In Database Setup enter a new system:

Create Generic ASCII Data Logger XML File

Start the Generic Layout Editor from the lower panel of the Console.

  1. Choose Log File for the Layout Purpose.
  2. Set the Log Mode to Event based, and the Event triggering to [fired event].
  3. Click on the RESULT DATA tab at bottom left to select layout items for events.

  1. Click on RESULT DATA.
  2. Click on Eventing button at bottom left.
  3. Click on Add button to load an Eventing System parent item.
  4. Eventing System is added.
  5. Select the appropriate system XML file.
  6. In the Available Sub-Items column, double click on an item to move it across to Selected Sub-Item.
    To output ASCII data to a log file based on firing events, item 'Id' must be selected, along with any other items required in the ASCII file.
    The field Event Id is used to assign a specific ID of a user-defined event. This ID corresponds to the ID as seen in the Event Output I/O Driver Editor.


Positions are updated and published to the ASCII file a fraction later than the actual raw event is triggered by the user.

Therefore in Controller\Session Setup\Storage\LogFile do not use 'triggering on system based' (i.e. the eventing system) for generic output.
Instead use 'Event Based' for Output Mode.


More detailed explanations regarding the Generic ASCII Data Logger system is provided in other QINSy documentation.
Refer to the Drivers & Interfacing Manual and the Knowledge Base.

Return to: How-to Eventing