Software
Copyright © 2015 Coda Octopus Products Ltd
124
F180R MOTION Sensor User and Reference Guide
Due to the nature of the processing filter, there is an initialisation time associated with the
iHeave output. During this time the application is collating data to populate the filter prior to
starting processing. It takes a period of approximately 9.0*(filter period) before iHeave output
will become available. Thereafter, the iHeave output will lag the real-time F180R System
output by a factor of 4.5*(filter period).
630 seconds (10 min 30 sec)
315 seconds (5 min 15 sec)
630 seconds (10 min 30 sec)
315 seconds (5 min 15 sec)
270 seconds ( 4 min 30 sec)
135 seconds (2 min 15 sec)
In practical terms, this means that after heading initialisation the F180R System will take
approximately 10 minutes and 30 seconds to start outputting the iHeave data. You should
therefore ensure adequate time is allocated prior to commencing the survey line to ensure
that the iHeave filter is active and outputting valid data.
See iHeave Data Logging for further details on logging the processed data.
5.6.2 iHeave Data Files
The standard internal data storage format of the F180R System is the MCOM format. This is a
proprietary data format defined by CodaOctopus to capture all the relevant data generated by
the F180R System.
NOTE: CodaOctopus publish the MCOM format and it is freely available to third parties
to implement decode libraries in their applications. For further details on the MCOM
format please contact Technical Support.
In logging mode, the F180R System will store 3 types of data file when you start logging data :
File written in original MCOM format to aid diagnostics and
troubleshooting if required by CodaOctopus.
This is the primary data storage file of the F180R System. It
contains processed iHeave values and the associated
timestamp information as well as all the motion and GPS
data.
This file stores a date and timestamp along with the
processed heave value and the real-time heave value.
To Next Page
Loading...