User manual

Table Of Contents
Appendix B
System Architecture
The MMP system architecture is explained in detail in this Appendix. The architecture
overview begins with the steps in the deployment process.
Starting a Deployment
1. An operator programs the MMP and initiates the autonomous portion of a
deployment.
2. The firmware places the TT8v2 into Low Power Sleep (LPS) for a user-specified
interval, while the operator sets the mooring and launches of the profiler.
3. The TT8v2 wakes from LPS (based on an alarm signal set by the firmware, the
programmed schedule, or when commanded to wake-up by an operator).
4. The system conducts Profile 0 to move the MMP to the bottom of the
programmed range. Subsequent profiles are numbered 1, 2, 3, … and are
conducted following the schedule programmed by the operator (odd numbered
profiles go from the bottom of the programmed range to the top and even
numbered profiles go from top to bottom).
5. The sensors turn on and begin logging data two minutes before the scheduled
start time of each profile.
6. Profiler motion starts at the scheduled start time. During the profile the sensors
log data autonomously and the MMP records engineering and status information.
7. Motion stops when the end of the programmed profiling range is detected. The
sensors continue to log internally for two minutes.
8. The system stops the sensors and transfers sensor data to the flash card (a profile
is complete when the sensor and engineering files have been closed).
9. The system enters LPS again and waits for the next scheduled profile. The
interval of sensor logging between motion start and stop provides data for use
during post-processing to correct for sensor drift. Other conditions, such as an
obstacle blocking the mooring cable, can be detected during a profile and may
trigger changes in profiling action.
10. The system continues to conduct profiles until the deployment is terminated.
Appendix B-1