MBARI OASIS3 Mooring Guide

Reset Commands in OASIS3

Reset Commands

OASIS3 uses the RESET command slightly differently than OASIS. There are 4 variations of RESET, depending on where you reset to and what happens to the log data after reset.

RESET	All log data is flushed to CFM files and saved. Then causes a system reset, the same as if the reset button had gotten a "long reset" or there was a power cycle.
RESET LOG	Does not reset the processor at all. Instead, this command simply discards all log data (in memory or CFM files) and restarts the logging from Block 0 Log Number 0.
RESET ALL	Discards all log data (from memory and erases CFM files), then causes system reset (similar to "long reset" or power cycle).
RESET PICO	All log data is flushed to CFM files and saved. Then causes a jump to PicoDOS, regardless of the "boot" state. Useful for returning to PicoDOS in order to load new code. Make sure you erase the OASISDAT.nnn files via PicoDOS before starting new code (see below).

Reset Button

The reset button on the OASIS serial cable can cause two types of behavior, traditionally called "short reset" and "long reset". Note that there are now only two behaviors. In OASIS, there were three.

"Short reset" is caused by pressing the reset button momentarily (<3 seconds), and is not a reset at all. It merely wakes up the user interface task, which causes it to print the "OASIS>" prompt to serial port 0, and wait for user commands.

"Long reset" is caused by pressing the reset button for >4 seconds. It causes the RESET signal to be asserted to the CPU on the CF2 card. What happens next is dependent on the state of the boot variable in PicoDOS.

In a deployable can, the system is set to boot OASIS3. In this case, OASIS3 will restart from scratch. If it finds files named "OASISDAT.nnn", where nnn is 000 to 999, it takes those as existing data files, and starts the data log subsequent to those files. As a result, if you hit "long reset" while OASIS3 is running, OASIS3 will restart with the next log block after the existing data. Note, though, that any data in the memory-resident ping-pong buffers will be lost. There is no opportunity for OASIS3 to flush those buffers to CFM when you hit "long reset". Typically, this will cause the loss of up to 16 KB of data, which can be several hours (or longer!) of data.
In a test system with boot set to "Pico", "long reset" will reset to PicoDOS. You can then use the native PicoDOS commands, load new code, etc. However, if you don't erase the "OASISDAT.nnn" files, then the next time you run OASIS3, data logging will start subsequent to those files. Thus, if your intention is to load new code and start over, you should use PicoDOS to erase the "OASISDAT.nnn" files.