Echoview supports data files from three models of Furuno echosounder:
Echoview does not directly support .hacorg files logged by FQ80 echosounders. It supports .hac files that are created from these files by Furuno's FQ80 Analyser software (see Furuno FQ80 Analyser documentation for more information).
The following FQ80 files types are supported.
|
File type |
Description |
|
PingAn01.hac |
Mechanical angle pings |
|
SCSVn06.hac |
Sv small-cell pings |
|
SSVn03.hac |
Sv pings |
|
TSn04.hac |
Single target detection pings |
Where n = channel number
Pos.hac files (GPS positions) are also supported but cannot be added to a fileset directly. Echoview will look for a pos.hac file in the Position folder when any of the files types listed above are added to a fileset. If a pos.hac file is found, Echoview will derive a position GPS fixes variable which can be viewed as a cruise track.
Support for other FQ80 file types is being considered for inclusion in future versions of Echoview. Please contact Echoview support to discuss your requirements.
Echoview requires that data files are stored in the folders to which they were written by the FQ80 during logging, i.e. for any root folder, the following folders must exist:
\Channel
\Echo
\Ping or \PingAngle
\Position (this folder is optional)
Note: Echoview and associated programs do not support the use of some international character sets. If any folders in the filepath contain characters other than Latin alphabet characters, you should rename the folders. See International character support for more information.
Echoview will look for files using their default file names (see above). Do not change file names or Echoview may not read the file at all or may read it as an incorrect file type.
The Furuno FQ80 stores and names data files quite differently to any other supported echosounder. As a result, you cannot add data files to a fileset in the same way that you would for files from other echosounders. Two rules apply to adding FQ80 files to a fileset:
You can only add a single data file to each fileset.
You can only add SCSVn06.hac, SSVn03.hac, and TSn04.hac files to a fileset from the Ping folder
You can only add PingAn01.hac files to a fileset from the PingAngle folder
Note: Although you can only add data files from the folders listed above, Echoview requires that certain files be present in other folders. For example, you cannot add a file from the Ping folder to a fileset unless a file of the same name (excluding channel number) exists in the Channel folder and Echo folder. The required files will have been written during logging and must not have been renamed or moved out of the folder to which they were written.
See Adding and removing data files for general information about adding data files to a fileset.
The transmit time for pings is stored at a resolution of one second. If the transducer's ping rate was greater than one ping per second during logging, multiple pings are assigned the same transmit time. Echoview requires that all pings have an unique transmit time and will shift transmit times as required. Echoview will shift each duplicate transmit time by 0.1 of the ping interval value read from the fff.hac file in the Echo folder (where fff is the same filename as the data file from the Ping folder that was added to the fileset).
The following information is presented as a reference. You do not need to be familiar with this information in order to make use of your data.
The sound speed value used in any calculations will be the value read from the fff.hac file in the Echo folder (where fff is the same filename as the data file from the Ping folder that was added to the fileset).
For a file fff.hac in the Ping folder that was added to a fileset, the sample thickness value used for ping geometry and other calculations will be calculated by Echoview as follows:
sample thickness = c / f / 2
Where:
c = sound speed (read from the fff.hac file in the Echo folder)
f = channel sampling frequency (read from the fff.hac file in the Channel folder)
The sample range value from fff.hac file in the Echo folder (where fff is the same filename as the data file from the Ping folder that was added to the fileset ) is not used.
The transmitted pulse length used in calculations will be calculated by Echoview. See FQ80 Pulse length for more information.
Echoview supports ETR-30N data files with the following naming system:
TTYYYYMMDDhhmm.bin
Where:
TT identifies the type of data stored in the the file and is one of:
for high frequency Sv ping data for low frequency Sv ping data for position data PhHF for high frequency phase data PhLF for low frequency phase data YYYYMMDDhhmm identifies the date and time of data logging as follows:
year month day hour minute
Sv values from ETR-30N Ping data files are calibrated (in the file). Echoview provides the option of applying a calibration offset is desired.
See About entering calibration settings for more information.
The following information is presented as a reference. You do not need to be familiar with this information in order to make use of your data.
The sample thickness value used for ping geometry and other calculations will be calculated by Echoview as follows:
sample thickness = c / f / 2
Where:
c = SoundSpeed, as entered on the Calibration page of the Variable properties dialog box
f = FurunoETRSamplingFrequency, as entered on the Calibration page of the Variable properties dialog box
Echoview supports Furuno FCV-30 data wrtitten by the instrument in a .hac format. Echoview reads the tuples that include the Ping U-32 tuple, Ping-32-16 angles tuple and standard HAC version 1.0 Standard navigation tuple (30). Single target data can be achieved using the Echoview operator called Single target detection - furuno FCV-30. This operator finds Furuno single targets in processed compensated TS data output by the Furuno FCV-30 sounder.
In addition a proprietary Furuno beam compenstation model is available for use with Echoview's Single target detection - split beam (Method 1 and Method 2) operators. For more information about the Furuno beam compensation model please contact Furuno.
Raw variables derived from Furuno data files
Calibration settings for Furuno FQ80 data
Calibration settings for Furuno FSV data
Calibration settings for Furuno ETR-30N data