New in Echoview 3.10
for users of data from Simrad echosounders
This page summarizes the new features, improvements and other changes that have been implemented in Echoview 3.10 which specifically affect the use of data from Simrad echosounders.
See also: New features in Echoview 3.10 for a description of changes that may affect you but are not specific to data from Simrad echosounders.
EK500, EA500, and EY500
"Ex500" introduced into help file
The term Ex500 has been introduced into this help file as a collective term for the EK500, EA500, and EY500. Where content does not affect all echosounders in this series, the relevant echosounder(s) will be individually identified.
Note: When Ex500 is used in relation to live viewing it refers only to EK500 and EA500.
.DGn file naming format
An enhanced naming format for .DGn files has been introduced to ensure Echoview can conclusively identify the year in which data was logged. We strongly recommend that you rename your files before adding them to an EV file. For details of the enhanced file naming format see, EY500 data, and EK500 data logged with EP500 software (.dgn).
.DGn files from an EK500 logged by EP500 software
The ping geometry of variables based on sample telegrams (W, P, V and B) in .DGn format files logged from an EK500 (using the EP500 software) is now correctly interpreted.
EK60, EA600, EA400, ES60, EQ60 and EY60
"Ex60" introduced into help file
The term "Ex60" has been introduced into this help file as a collective term for the EK60, EA600, EA400. ES60, EQ60 and EY60 echosounders. Where content does not affect all echosounders in this series, the relevant echosounder(s) will be individually identified.
Note: When Ex60 is used in relation to logging EK500 compatible telegrams, Ex60 refers only to EK60, EQ60, ES60 and EY60; the EA600/400 cannot log these types of data.
Wavelength used in calculating Sv and TS from Ex60 raw data
The wavelength value that is used to calculate Sv and TS from Ex60 raw data calculations was previously calculated using a fixed value of 1470.6 m/s. Wavelength is now calculated using the same sound speed value that is used in all other places in the Sv and TS from Ex60 raw data calculations, i.e. the value entered on the Calibration page of the Variable Properties dialog box. See Simrad Ex60 Power to Sv and TS.
When you open existing EV files containing Ex60 data files, Sv and TS values will be recalculated automatically using the sound speed from the Calibration page. The expected magnitude of change is summarized below:
|
Sound speed |
Change in TS and Sv |
Change in NASC |
|
1450 |
0.1225 dB |
2.86% |
|
1470 |
0.0035 dB |
0.08% |
|
1500 |
-0.1719 dB |
-3.88% |
|
1550 |
-0.4567 dB |
-9.98% |
This change has been implemented to remain consistent with the latest version of Simrad's ER60 software which has also ceased using 1470.6 m/s and now uses the same configurable sound speed throughout the program.
ER60 (.DG) file support
Data files logged with Simrad ER60 software (.DG files) are now supported in Echoview and Echocheck, see the following pages for more information:
Note: Support for this file format is in beta testing release in Echoview 3.10. Please submit any feedback, suggestion or problems to Echoview support.
Warnings:
-
Version 2.0.0 of the Simrad ER60 logging software contains a known problem with the way it logs B telegrams. We strongly recommend that you do not log B telegrams with ER60 software until Simrad release a patch.
-
Applying calibration correction to variables derived from ER60 data files may result in recalibrated data that is inaccurate. We strongly recommend that you do not apply calibration correction until the algorithms that are used to derive raw power from logged TS and Sv values are improved. See Calibration settings for EK500 telegrams logged from an Ex60 echosounder.
TVG range correction offset for Ex60 data
Sv and TS variables derived by Echoview from Ex60 raw power data can be calibrated using a TVG range correction. This enables you to calibrate the Sv and TS values from raw power so they are consistent with Sv and TS values that are calculated by the Ex60 in Q, V and P telegrams (to which a TVG range correction is applied by the echosounder).
The variables that can be recalibrated using a time varied gain range correction offset are:
-
Sv raw pings
-
TS raw pings
-
Sv from power (W telegrams)
-
TS from power (W telegrams)
The TVG range correction offset is entered on the Calibration 2 page of the Variable Properties dialog box. This option is not applied to new and existing variables unless manually selected.
Note: The TVG range correction offset applied by Ex60 echosounders is not published by Simrad. For approximate values see the Raw variable calibration settings page.
ER60 and Echolog 500
You can use Echolog 500 to log all EK500 type telegrams via the ER60 Ethernet output (the EK60 mark 1 software was limited to Q and E telegrams via the BI500 port). If you wish to use Echolog 500 with the ER60, see, Ex60 setup for Echolog 500. If you have already been logging telegrams from the ER60 using Echolog 500, you should read the important warning in the Echolog application section below.
Vessel log support
Vessel logs can be derived from Ex60 .raw data files logged using ER60 software and from .ek60 or .ek6 files created from .raw data files logged using ER60 software. To write this data to .raw files you must:
-
set up the ER60 software to generate distance from speed, and
-
have a GPS attached or enter an estimated speed.
The vessel log can be used in Echoview in a number of ways, including:
-
to define the time/distance axis of a grid
-
as an analysis variable in exports, e.g. VL_Start, VL_Mid, VL_End, see General analysis variables
SM2000 FR
Calibration of SM2000 FR variables
You can now calibrate SM2000 FR variables that use non-standard head configurations. Echoview still reads the head type from the data file and applies standard values for the Radius and Interelement spacing calibration settings, but now allows you to override these settings on the Calibration page of the Variable Properties dialog box. See Simrad Mesotech SM2000 FR on the Raw variable calibration settings page for more information.
Multibeam phase variables
Echoview will now derive phase variables from complex multibeam data files. The data type of these variables is received signal phase (quadrature) in radians (-p to p). These variable share their calibration settings with amplitude variable derived from the same complex data file.
Echolog applications
Echolog 500 version 3.10
You must now enter the type of echosounder from which data is being logged. This information is written to the .ek5 file for use in Echoview. Echoview needs to be able to identify the echosounder that was used because Echoview variables require different processing and calibration settings depending upon the echosounder used to generate them. You record the type of echosounder being used in the Type of echosounder box on the Echolog 500 Settings dialog box.
Warning
All .ek5 data files logged by previous versions of Echolog 500 will be treated as though they came from an Ex500 echosounder. If you have logged sample telegrams from an ER60 using Echolog 500 3.00 or earlier, you should contact Echoview support prior to using these data files. Potential problems include: the sample height in Pn, Bn, and Vn variables will not be calculated correctly, the TVG correction for W telegrams will not be calculated correctly and incorrect calibration settings will be displayed on the Calibration page of the Variable properties dialog box.
Echoconfig 500 version 3.10
Echoconfig 500 can now prevent an unattended computer from going into standby mode or hibernating. Echoconfig 500 will only do this if the Automatically read EK500 parameters facility is enabled.