User manual

Table Of Contents
Commands sent through the SIM/UIM system always take one of two forms:
#nnCOMMAND or bnnCOMMAND.
The nn is the UIM identification and is used by the UIM to identify whether a command
is directed toward it. If the command is meant to be handled by the UIM, the COMMAND
portion is relayed to the serial instrument (in this case the MMP).
The ‘#’, indicates that the SIM and UIM are awaiting ascii data terminated with a
pre-defined termination character.
The ‘b’, indicates that the SIM and UIM are awaiting binary data terminated by a
transmission gap.
The timeouts are different for the two cases and are explained in the SeaBird
documentation.
Transmission Sequence Scenario
This section provides a sample transmission sequence session. For detailed descriptions
of file transmission protocols, see page J-6.
NOTE
To confirm the communications link, the UIM initially powers ‘on’ after ‘V’ (Verify and
Proceed) is selected from the MMP Deployment menu. The UIM remains on until profile 0 (the
initial MMP dive) begins, then powers off and remains off until the next scheduled transmission
session. This is a verification feature only. The MMP firmware itself remains in Low Power
Sleep (LPS) and does not listen or respond to the UIM until the scheduled transmission session.
1. The ‘Tone detect’ board attached to the SIM receives a tone and responds by setting its
detect line (JP4 pin 2) low. If the MMP does not receive a response from the surface
within 40 seconds, the tone will be sent again a maximum of two more times (spaced 40
seconds apart).
Appendix J-
3