Skip to main content
Skip table of contents

Singlebeam Echosounder


Parent Item
System:List with all available singlebeam echosounder transducers that exist in the currently selected Qinsy database.
(see General Layout Information about loading a Qinsy database).
Note that a singlebeam echosounder system may have more than one transducer defined.
Computation:

This option to select a computation is only needed for transducer node sub items (e.g. Td Easting, Td Northing, Td Height + Depth, etc.)

  • The first entry is always [Priority List]
  • The rest of the list will show all available computations, as defined in the Computation Setup of the current Qinsy database.

Note that when the layout is used for Export (offline), you can not select entry [Priority List], you must select a 'real' computation from the list.
Skew:
  • No
    Transducer Node Position for the time as calculated by the Position Filter.
  • Yes
    Skewed to the time of output/trigger time, using the current Transducer Node Position (Horizontal), Time, SOG and COG.
    Notice that the SOG and COG depend on the Controller's Computation Setup, Object COG / SOG - Prediction Parameters Settings.

Notes:

  • The skew option is only applicable to 'Td xxx' sub items which are actually node results. Skewing has no effect on the raw singlebeam values.
  • Transducer Height values are never skewed, only the horizontal components.
  • When skew is enabled for Export (offline), the transducer node results will be interpolated to the moment of the layout trigger update time.
    This can be useful in the following scenario:
    Suppose your trigger time comes from this singlebeam system with observations at 10Hz and your positioning system has 1Hz.
    When you now export all depth values together with the transducer node results, you get a skewed transducer position for each raw depth update.

Note that terminology 'Deskew' and 'Skew' means the same in Qinsy: they are not opposites of each other.
So where-ever you read the term 'skewing' in Qinsy it means the same as if you would read 'deskewing'.

Sub ItemDescriptionValue Type
Comment

User-defined free text

Text Format
  • Normal Text
    Your own free plain text
  • Binary
    Enter one or more ASCII character codes, comma or space separated, in the range between 1 and 127.
    For example '2' for a binary STX character, '3' for a binary ETX character, or '13, 10' for CR+LF.
    See table ASCII Codes for an overview of all possible characters.

  • New Line
    Same as Binary but already formatted as '13, 10' (meaning CR+LF) and without a possible Field Delimiter.
    A Field Delimiter may be present when your layout purpose is for Export or ASCII Logging.

text
Name

Name of the Singlebeam Echosounder System (plus the Transducer label) as defined in Database Setup

text
TimeTime of the last raw updatetime
Depth

Value depends on the Apply C-O property.

Apply C-O
  • No
    The measured depth (i.e. depth below transducer) as reported by the unit and possibly uncorrected for the draft.
    Same value as seen in an Observation Physics Display Raw column.
  • Yes
    The reported depth corrected for draft and sound velocity as defined in the Controller Echosounder Refraction settings.
    So the value depends on the selected Sound velocity mode and/or defined Used manual draft.
    Same value as seen in an Observation Physics Display Corrected column.
double
Sound Velocity

The used sound velocity value as reported by the unit.

In case the unit (message format) does not output the used sound velocity (see also Status Flag) then it will be the used sound velocity as entered in Database Setup.

Apply C-O
  • No
    The used sound velocity as reported by the unit or as entered in the Controller Echosounder Refraction setting.
  • Yes
    The sound velocity value that is actually used to improve the reported depth from the unit.
    So it depends on the Sound velocity mode as selected in the Controller Echosounder Refraction setting:
    the entered calibrated sound velocity, the selected velocity observation, or the average sound velocity from the selected profile.
double
Velocity Mode

An integer value (code) representing the selected Sound velocity mode as defined in the Controller Echosounder Refraction setting.

By default a translation table is added to convert the code into readable text:

CodeSound Velocity Mode
0UNITAs used by the unit
1CALIBRATEDFrom calibrated sound velocity
2PROFILEFrom velocity profile
3OBSERVATIONFrom velocity observation

Feel free to modify or remove the translation table.

int
Draft

Decoded transducer draft value from the unit (see also Status Flag) or the manual draft value as entered in the Controller Echosounder Refraction setting.

Note that the draft here is the distance between waterline and transducer and should not be confused with the vessel's draft as defined in the Computation Setup, Object Height.

double
Heave

Decoded heave value from the unit.

Value will be empty when the unit does not output a heave (see also Status Flag).

double
Index

Decoded index offset value from the unit.

Value will be empty when the unit does not output an index offset (see also Status Flag).

Index (or index offset, is also known as constant k, initial delay or electronic delay) is a fixed offset which depends on the transducer hardware being used and should be determined by a calibration procedure.

double
Status Flag

This integer value represents a bit-wise flag where each bit indicates if the sound velocity, the draft, heave and/or the index offset is part of the output message from the unit.

BitStatusMask (decimal)
0Used sound velocity1
1Transducer Draft2
2Heave4
3Index offset8

For example when the status flag value is 3 it means that the echosounder unit is outputting the used sound velocity and draft.

If the status flag value is zero then none of these additional values are known by the driver.

int
Ping Number

Normally an increasing number.

This value is decoded from the header data, coming from the echosounder system itself.

int
Age

The difference between the triggering time and the time of the last raw update. Normally a positive value in seconds.

Note that the Age value for export will be the difference between the time of the current observation and the previous exported one.

Formula:

  • Online  (Generic Display, Generic Output Driver, Generic ASCII Logger)
    Age = Triggering time - Observation time
  • Offline (Generic Export)
    Age = Observation time - Previous observation time

double
Quality  Same quality as seen in Observation Physics Display.double
Td Name

The name of the node, as defined in Database Setup.

This node is selected as transducer in the echosounder system setup on the 2nd wizard page.

text

Td Easting


Td Northing

The easting and northing of the transducer node as calculated by the selected computation.

Easting and Northing are always on Survey Datum (also known as Horizontal Datum)

double

Td Latitude


Td Longitude

The latitude and longitude of the transducer node as calculated by the selected computation.

Latitude and Longitude are by default on Survey Datum (or Horizontal Datum), but the 2nd datum may also be selected if available in the Geodetic Configuration.

Datum:
  • Survey Datum ( Name )
    Geographical position will be on the selected survey datum ellipsoid, e.g. 'ED50'.
    Note that Survey datum (or Horizontal Datum) is set in the Geodetic Configuration as Project Coordinate System.
  • 2nd Datum ( Name )
    Geographical position will be on the selected Source Coordinate System in the Geodetic Configuration, e.g. 'WGS 84', 'ITRF2008' or 'ETRS89'.

geo

Td Height

The height of the transducer node as calculated by the selected computation.

Height is by default on Chart Datum (also known as Vertical Datum) but other datums can also be selected.

Datum:
  • Survey Datum ( Name )
    Height value will be on the selected survey datum ellipsoid, e.g 'ED50'.
    Note that Survey datum (or Horizontal Datum) is set in the Geodetic Configuration as Project Coordinate System.
  • 2nd Datum ( Name )
    Height value will be on the selected Source Coordinate System in the Geodetic Configuration, e.g. 'WGS 84', 'ITRF2008' or 'ETRS89'.
  • Chart Datum ( Name ) - Default
    Height value on the selected vertical datum, e.g 'NAP - De Min Geoide'.
    Note that Chart Datum (or Vertical Datum) is set in the Geodetic configuration as Vertical Datum under the Project Coordinate System.
  • Actual Water Level
    Height value above the actual water (or sea) level.
    The following formula is used: Geoid Level + Tide + Swell
    The swell is derived from the roll, pitch and heave of the reference node, and the offset of the selected node to the reference node.
    The heave value of the reference node can be monitored under the heave column of the Height Aiding driver.
  • Mean Water Level
    Height value above 'mean' water (or sea) level.
    The following formula is used: Geoid Model + Level Model + Offset
  • Geoid Model Level
    Height value above input geoid model. Only used in case of River Height Model.

double

Td Height + Depth

A combination of the transducer height plus the corrected depth value.

For this combination the height reference is always Chart datum and the depth value is already corrected for the sound velocity mode as defined in the Controller Echosounder Refraction setting.

Note that this value is not as accurate as the final DTM Results (actual calculated footprint value using SVP ray tracing, etc.) but it gives a good indication of the current water depth.

double
Td Depth

The depth of the transducer node with respect to the actual water level.

double
Td Z Offset

The vertical offset of the transducer node from the object reference point as defined in the Database Setup.

A negative value means that the transducer node is below the object reference point.

double
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.