Raw variables derived from Simrad data files

This page describes the variables that Echoview can derive from data files logged by Simrad echosounders.

• Data files containing EK500 telegrams (.ek5, .dg, .dgn, -ping, -vlog, -data, -info, -work)
• Data files containing EK500 telegrams logged with ER60 software
• Data files containing Ex60 raw data (.raw, .ek60, .ek6)
• Data files containing SM2000 raw data (.raw, .raw.sm2000, .nnn)
• Data files containing SM2000 beamformed data (.bfm, .bmf, .bfm.sm2000, .bmf.sm2000, .nnn)
• Data files containing ME70 raw data (.raw)
• Data files containing SH80 data (.dat, .dzt)
• Data files containing SP70 data (.dat, .dzt)

Notes:

• Simrad is a subsidiary of Kongsberg. See also Raw variables derived from Kongsberg data files.
• The variables that are derived from any given data file will depend on the transducer type and transducer calibration used during logging.
• Vessel logs can be derived from some data files, but cannot be displayed in Echoview. They can however:
  • be used as the source of distance for time/distance grids,
  • be used as the source of distance for schools detection, and
  • be included in exported data, see About analysis variables.
• Sv raw pings, TS raw pings and angular position raw pings may all be multiplexed by users with specific hardware. Multiplexed variables will have "(channel c)" appended to their name - where c is the channel number. See Multiplexed variables.

Data files containing EK500 telegrams (.ek5, .dg, .dgn, -ping, -vlog, -data, -info, -work)

 Echoview can derive the following variables from data files containing EK500 telegrams:

• angular position Bt telegrams Tt                 cannot be derived from -ping, -vlog, -data, -info, -work files

• Sv Wt telegrams (power) Tt                       cannot be derived from -ping, -vlog, -data, -info, -work files

• Sv Vt telegrams Tt                                    cannot be derived from -ping, -vlog, -data, -info, -work files

• Sv Qt telegrams Tt

• Sv Qt telegrams with expanded bottom Tt

• TS Qt telegrams Tt

• TS Qt telegrams with expanded bottom Tt

• TS Wt telegrams (power) Tt                        cannot be derived from -ping, -vlog, -data, -info, -work files

• TS Pt telegrams Tt                                     cannot be derived from -ping, -vlog, -data, -info, -work files

• single target detections Et telegrams Tt

• parameter settings PE telegrams                 can only be derived from .dg files

• vessel logs

• position GPS fixes

Data files containing Ex60 raw data (.raw, .ek60, .ek6)

Echoview can derive the following variables from .raw, .ek60 and .ek6 files:

• Sv raw pings Tt

• TS raw pings Tt

• angular position raw pings Tt

• position GPS fixes

• vessel logs

• heading data

Data files containing SM2000 raw data (.raw, .raw.sm2000, .nnn)

Echoview can derive the following variables from .raw and .raw.sm2000 files:

• magnitude raw beam pings

• magnitude beamformed raw beam pings

• phase raw beam pings

• phase beamformed raw beam pings

• Sv beamformed raw beam pings

• position GPS fixes

• heading data

• roll data

Data files containing SM2000 beamformed data (.bfm, .bmf, .bfm.sm2000, .bmf.sm2000, .nnn)

Echoview can derive the following variables from .bfm, .bmf, .bfm.sm2000, .bmf.sm2000 files:

• magnitude beamformed pings

• magnitude complex beamformed pings

• phase complex beamformed pings

• Sv beamformed pings

• position GPS fixes

• heading data

• roll data

Data files containing ME70 raw data (.raw)

Echoview can derive the following variables from ME70 .raw files:

• Sv raw pings Tt

• TS raw pings Tt

• angular position raw pings Tt

• Sv pings formed beams

• position GPS fixes

• vessel logs

• heading data

Data files containing SH80 data (.dat, .dzt)

• Sv pings SH80 Omni (H-mode)
• Sv pings SH80 Vertical slice (V-mode)
• unspecified dB pings SH80 Omni (H-mode)
• unspecified dB pings SH80 Vertical slice (V-mode)
• position GPS fixes
• heading data

Data files containing SP70 data (.dat, .dzt)

• Sv pings SP70 Omni (H-mode)
• unspecified dB pings SP70 Omni (H-mode)
• position GPS fixes
• heading data

Legend

t = the transducer number (1 to 9)

See also

Calibrating EK500 telegrams logged with Ex500
Calibrating EK500 telegrams logged with Ex60
Calibrating Ex60 raw data
Calibrating SM2000 data
Calibrating ME70 data
Calibrating SH80 data
Calibrating SP70 data

Echoview Help file 5.2.21 for Echoview 5.2.55 Monday 21st May 2012

Please report any errors or omissions to support@echoview.com.