Campbell CR3000 Micrologger, Руководство оператора, Страница: 125 / 644

Section 7. Installation
125
Pros/Cons
This is a good way to recover a CR3000 that has gone into an unresponsive state.
Often, an operating system can be loaded even if you are unable to communicate
with the CR3000 through other means.
Loading an operating system through this method will do the following:
1. Restore all CR3000 settings to factory defaults
2. Delete data in final storage
3. Delete data from and remove the USR drive
4. Delete program files stored on the datalogger
7.5.2.1.2 OS Update with File Control
This method is very similar to sending an OS as a program, with the exception
that you have to manually prepare the datalogger to accept the new OS.
How
1. Connect to the CR3000 with Connect or DevConfig
2. Collect data
3. Transfer a default.CR1
(p. 119)
program file to the CR3000 CPU: drive
4. Stop the current program and select the option to delete associated data (this
will free up SRAM memory allocated for data storage)
5. Collect files from the USR: drive (if applicable)
6. Delete the USR: drive (if applicable)
7. Send the new .obj OS file to the CR3000
8. Restart the previous program (default.CR1 will be running after OS compiles)
Pros/Cons
This method is preferred because the user must manually configure the datalogger
to receive an OS and thus should be cognizant of what is happening (loss of data,
program being stopped, etc.).
Loading an operating system through this method will do the following:
1. Preserve all CR3000 settings
2. Delete all data in final storage
3. Delete USR: drive