User manual

Data Format
When a file or combination of files is requested, the MMP first sends the metadata for the
next file to be transmitted.
NOTE
Mooring ID (a three position numeric identifier) is defined from the Deployment Menu and
embedded in the metadata to identify files from multiple profilers on the same mooring line.
The metadata structure is as follows:
typedef struct
{
char fileName[13]; // filename.ext - followed by white space
char profileEndTime[20]; // mm dd yyyy hh mm ss - followed "
char mooringID[4]; // ### - followed by "
char byteCount[12]; // ###### - followed by "
char term[2];
} metaDataStruct;
Each character field is terminated by a white space, rather than a null. The metadata for a
single file is followed by a series of data packets and ends with an EOD packet. Each packet is
prefaced with the packet header:
typedef struct
{
char dataHdr[4]; // "DAT", “CRC”
short byteCount; // of whole pkt 8 + pktdatasize
short CRC; // CRC
} packetHeader;
The character field dataHdr is terminated by a white space. Immediately after the packet
header, the packet content is transmitted. A “DAT” packet will contain up to 4KB of data; a
“CRC” packet will indicate that there are no more packets to be sent. There is no content for the
CRC packet. The CRC value reported in this packet is the value for the entire file.
File Transmission Protocol
The data files that the MMP sends to the surface will adhere to the protocol described in
the table shown next.
Appendix J-6