Eclipse User Manual
Release 1.10.1 Page 47 of 58 Eclipse User Manual
To dump, go to SETUP page 3 DUMP (DATATYPE). Below is a list of the
types of data that you can dump. Press <DUMP> to actually do the deed.
Current Prog Dumps the currently running program. If received at the MIDI In port or at the serial
port, the Eclipse will load the received program.
Internal Progs
Dumps all programs stored in internal memory. If received at the MIDI In port or at the
serial port, the Eclipse will erase your Memory Card and replace its contents with the re-
ceived programs. If there is no Memory Card in place or if the Memory Card is too
small, the incoming data is ignored.
System Setup This function dumps the state of the Eclipse, covering all of the saved values in the
SETUP area and the LEVELS area. If received at the MIDI In port or at the serial port,
the Eclipse will replace the saved values in these areas with the incoming data.
If the device to which you sent the dump has the ability to send it back again (such as a sequencer), you can
use this as a way to "back up" your the Eclipse.
WARNING: If, for any reason, this dump gets corrupted in some way (beyond the Eclipse’s con-
trol) and then sent back to the Eclipse, you will lose all the information you are trying to back up,
as well as the Eclipse's contents. If you do a “backup” in this way, especially to a computer, it
would be a good idea to do it twice, to two separate files, and then to compare the size of the files
(On a PC, check the “property” of each file. Look at the number in parentheses. On a Macintosh,
“get info” on each file. Again, look at the number in parentheses.). If the sizes are identical, it’s a
good indication that the data sent from the Eclipse has been recorded accurately.
For the above reasons, it is recommended that setups be saved internally and reloaded when neces-
sary, rather than making heavy use of dumps.
!
!!
! see page
see page see page
see page 45
4545
45 to learn about
to learn about to learn about
to learn about Storing and Loading
Storing and LoadingStoring and Loading
Storing and Loading Setups
Setups Setups
Setups
Fixing and Initializing Internal Memory
The Eclipse uses solid-state memory circuits to store programs and setup
information internally, using a long-life battery to keep the memory alive
while the Eclipse is turned off. Whenever the computer in the Eclipse up-
dates that memory, it performs an operation called a “checksum” and stores the result. A checksum is a cal-
culation whose result characterizes what is stored in memory. A second run of the checksum calculation
should result in the same characterization, if the memory hasn’t changed. When the Eclipse is turned on, it runs a
checksum calculation on the memory and compares the result against the stored result. If there is a discrep-
ancy, the Eclipse reports an error.
In the unlikely event that an “internal memory checksum error” occurs, there may be a critical problem with
what is stored in memory. Pressing
SETUP page 3 SERVICE <FIX> <YES> will remove the checksum error by
forcing the new checksum result to be saved. This will not get rid of the corruption in the data, however.
Now, you can assume that the “checksum error” was no big deal, get a cup of coffee, and go back to work
(not advised) OR you can assume something nasty is going on and take immediate action (advised). Assum-
ing you take the latter (smart) course of action, the first thing you’ll want to do is to save all of your impor-
tant programs to a card
(see page 29) or to an external storage device (see page 46).
Internal memory “checksum errors” should occur infrequently, if ever. Should they occur more frequently
than “infrequently,” contact Eventide, as something is definitely amiss.
