CSD - Dredging Sensor

Dredging Sensor Definition

Prior to defining a dredging system the observations that support the dredging system should be defined (usually part of a dredging sensor system type). For example the dredging status (e.g. dumping/dredging/sailing loaded), current measurement, open/close bay door observation etc.
Note that this is optional, all the values can also be entered/overruled online.

image2016-1-28 14:21:14.png Add a new system by selecting “Edit” from the menu bar, and then “New” and “System”, or right click on the item System in the item tree.

The following dialog opens. It is the first page of a wizard that steps you through the system definition process.

image2016-1-28 14:25:32.png Enter an appropriate name that provides instant recognition in Online displays.

image2016-1-28 14:26:4.png Select Dredging Sensor from the drop down list.

image2016-1-28 14:29:8.png From the drop down list select the driver that corresponds to the data message output by the system to which QINSy is interfaced.

Note that the interfacing can be either serial or network so make sure to select the correct type.

image2016-1-28 14:32:27.png Enter interface port parameters.

Please refer to A Note on Interfacing Parameters.

image2016-1-28 14:43:31.png Enter the data update parameters. Depending on the driver selected one or other, or both, these parameters are shown:

Updates
Maximum update rate	Enter a value to determine how often data will be decoded by the interface driver. Some equipment is capable of outputting data at high output rates, but it may not be necessary to use each update. A sensor system may for example output values hundreds of times per second, where five times per second is sufficient. In this case, enter a value of 0.20s. Any data not decoded by the driver is lost and cannot be recovered later.
Latency	Latency is the time between the actual measurement made in the sensor system and the time the data message arrives at the port. The time in QINSy will thus be the arrival time corrected with the latency. Modern sensor systems will exhibit no latency, or will have compensated for the latency in the time tag of each data message.

Updates

Maximum update rate

Enter a value to determine how often data will be decoded by the interface driver. Some equipment is capable of outputting data at high output rates, but it may not be necessary to use each update. A sensor system may for example output values hundreds of times per second, where five times per second is sufficient. In this case, enter a value of 0.20s. Any data not decoded by the driver is lost and cannot be recovered later.

Latency

Latency is the time between the actual measurement made in the sensor system and the time the data message arrives at the port. The time in QINSy will thus be the arrival time corrected with the latency.
Modern sensor systems will exhibit no latency, or will have compensated for the latency in the time tag of each data message.

image2016-1-28 14:45:51.png Press Next to advance to the second page of the wizard which will look like this:

image2016-1-28 14:57:37.png Initially the dialog is empty. Select the object upon which the sensor is located. In this case it does not really matter so select the primary object.

image2016-1-28 14:59:31.png Click on the Add button which brings up the Define Observation dialog.

image2016-1-28 15:2:21.png Select the type of observation that is to be read from the sensor. Then enter an observation name.

image2016-1-28 15:3:52.png Select a node at which the sensor observation is made. In this case just use the CoG of the primary object.

image2016-1-28 15:8:34.png Click OK to return to the Observation Definition dialog.

image2016-1-28 15:9:57.png Click on Edit Slot and enter a numeric, alphabetic or alphanumeric identifier.

This slot ID must match the identification associated with the parameter in the data message received from the sensor. In this case 'Density' is the identification used in the data message that differentiates the density data field from all other data fields in the message.

image2016-1-28 15:45:51.png Repeat the process by clicking on Add to define other observations that will be decoded from the data message received from the sensor.

In many cases the data message will not include all of these observations.

image2016-1-28 15:50:9.png Click Next to advance to the wizard's third page.

image2016-1-28 15:53:43.png Observations add on the previous page of the wizard are listed. Click on each observation in turn and enter values for its associated parameters.

Observation parameters
Name	Enter a descriptive name for the observation.
Unit	Select the appropriate observation unit. In some cases there will only be one choice.
a-priori SD	Enter the SD for each observation in turn.
Fixed C-O	Constant correction to the parameter value.
Variable C-O	Variable correction to the parameter value.
Scale factor	Use scale factor to convert the raw output to units in the Acquisition Software. For example if local output is in centimeters, then enter scale factor 0.01 here to convert to meters.

image2016-1-28 15:54:28.png Click on Finish to complete the sensor definition.

Return to top of page.

Return to: Cutter Suction Dredger (CSD) - System Definitions