Simrad EK500 configuration

The following information may not apply if you are using the DFO/NHP/DAT CH1 logging software. Please consult the documentation for that software.

Echolog 500 can log all Ethernet telegrams from the EK500 including all those not currently processed by Echoview.

Echoview does not use all EK500 telegrams and requires certain restrictions on the use of some telegrams.

Simrad EK500 firmware

Echoview is designed for use with telegram formats from V5.2 and V5.3 of the EK500 firmware. If you wish to use other versions of EK500 firmware please check that the telegram formats do not differ from these versions. If relevant telegram formats do differ from V5.2 and V5.3 then Echoview Software should be able to add support for the different formats if provided with the specification and sample data files.

Simrad EK500 telegrams currently used by Echoview

  • Q1, Q2 and Q3 (echogram telegrams, transceivers 1, 2 and 3)

  • E1, E2 and E3 (echotrace telegrams, transceivers 1, 2 and 3)

  • V1, V2 and V3 (sample Sv, transceivers 1, 2 and 3)

  • W1, W2 and W3 (sample power, transceivers 1, 2 and 3)

  • B1, B2 and B3 (angular positions, transceivers 1, 2, and 3)

  • P1, P2 and P3 (sample TS, transceivers 1, 2 and 3)

  • GL (geographical location) telegrams. See Interpretation of Simrad GL Telegrams.

  • VL (vessel log) telegrams

  • LL (list layer) telegrams are used to obtain date information only

  • CS (comment string) telegrams are converted to marker regions

  • PE (parameter entered) telegrams are used by Echoconfig 500

  • PR (parameter request) telegrams are used by Echoconfig 500

Echogram telegram: important restrictions

EK500 echogram ('Q' telegram) data must be output by the acquisition software with a "20logR" time-varied gain if the logged data is to be used for echo integration in Echoview. Logged echogram data that was output with a "40logR" time-varied gain setting will be displayed in Echoview as a TS raw variable which cannot be used in Echoview for echo integration. Moreover such data is not valid TS (point backscatter) data and should not be used for identification of single targets, or for the determination of their target strength. If you need to convert between these data types please contact Echoview support for further advice.

Echogram (Qn) telegrams can contain a bottom-referenced echogram in addition to the normal surface-referenced echogram. If bottom-referenced echogram data are available and is of higher resolution than the surface-referenced data, then Echoview can build a composite echogram containing all the data at the maximum available resolution, and covering the range of the surface-relative echogram. These variables are called "Sv Qn telegrams with expanded bottom" in Echoview. See EK500 expanded bottom variables for more information.

Echoview is not limited to a fixed number of data points, so you can vary the number of surface-relative and bottom-relative data points to best fit your application. The EK500 imposes the following limitations:

  • The number of surface-relative data points cannot be more than 700.

  • The number of bottom-relative data points cannot be more than 500.

  • The total number of data points cannot be more than 714.

Note: Only the bottom-relative data within the range of the surface-relative echogram can be used by Echoview.

For a pelagic survey, you would probably set the number of surface-relative data points to 700 and the number of bottom-relative data points to 0.

For a bottom-classification survey, you could set the number of surface-relative data points to 214 and the number of bottom-relative data points to 500, to give you the maximum data resolution near the bottom. For example:

  • Ethernet/Echogram Menu -# Menu

  • Range = 450

  • Range Start = 50

  • Auto Range = Off

  • Bottom Range = 75

  • Bot. Range Start = 50

  • No. of Main Val. = 214

  • No. of Bot. Val. = 500

  • TVG = 20 log R

This will log 214 data points over the range 50m to 500m, and 500 data points between 50m above the bottom and 25m below the bottom. Note that bottom-relative data above 50m or below 500m will not be available within Echoview.

Sound speed: restrictions

A constant sound speed must be used over the full depth range of data logged for echo integration.

Sound speed profiles (that is, sound speed varying down the water column) are NOT supported by Echoview at this time.

Simrad EK500 time and date considerations

The EK500 does not attach date information to all telegrams. Echoview relies on the date information in the VL and/or LL telegrams for date information. Where date is not available from VL or LL telegrams the date recorded in the logged EK5 file name is used. Echoview Software recommends that VL telegrams are turned on at all times while logging data from the EK500.

If no vessel log input is connected to the EK500 then we recommend that the EK500 vessel log is run in "speed" mode. This requires the following settings:

  • Log Menu/Mode = Speed

  • Navigation Menu/Speed Input = Manual

  • Navigation Menu/Manual Speed = 5.0*

* This can be any speed from 0.1 to 25.0 knots.

The date and time on the EK500 should be synchronized with the date and time on any computers running Echolog 500, and any computers running Echoview for live viewing. Please take note of the External clock setting on the EK500 (on the Utility menu).

Draft considerations

Echoview Software strongly recommends logging data with the Transducer depth setting (on the Transceiver menu) set to 0. Echoview's transducer geometry allows you to model the draft when live viewing and processing data.

If you do log data with an embedded draft (that is, a non-zero transducer depth) you should read Logged draft warning before processing your data in Echoview.

See also

Simrad EK500 and EA500 setup for Echolog 500