Kurzweil K2600 - MUSICIANS GUIDE REV A PART NUMBER 910331 CHAP 7 Manual page 5

returned (see object type table below). The bank Þeld speciÞes a single bank, 0Ð9, unless it is set
to 127, in which case objects from all banks will be returned.
form requests the format of the binary data in the WRITE messages. If ramonly is one, only
objects in RAM will be returned. If ramonly is zero, both RAM and ROM objects are returned.
The responses, a stream of complete WRITE messages, will come out in order of object type,
while objects of a given type are in order by ID number, from lowest to highest. If no objects are
found that match the speciÞcations, no WRITE messages will be returned. After the last WRITE
message, an ENDOFBANK message (deÞned below) is sent to indicate the completion of the
bank dump.
The K2600 will insert a small delay (50ms) between WRITE messages that it issues in response to
a READBANK message.
A bank dump can be sent in its entirety to another K2600, which will add all of the objects
contained in the dump to its own object database. Important: If the K2600 receives a large bank
dump for a bank or banks that already contain objects, errors may result unless the sender waits
for the DACK message before sending the next objectÕs WRITE message. One way to avoid
transmission errors such as this is to make sure that the bank being dumped is clear in the K2600
before sending the dump, so that the K2600 will not miss parts of the dump while its CPU is
busy deleting already existing objects. This can be done using the DELBANK message (deÞned
below). If the destination bank in the K2600 is clear, it is not necessary to wait for the DACK
before sending. Even if the sender chooses not to wait for the DACK before sending the next
message, it may be necessary to preserve the 50ms delay between the WRITE messages.
Due to the large amount of incoming data during a bank dump containing many objects, the
receiving K2600 may have a more sluggish response to front-panel use and keyboard playing
during the data transfer. This is normal behavior and the machine will become fully responsive
as soon as the dump is Þnished.
DIRBANK = 0Ch
This is similar to the READBANK message. The DIRBANK message requests an INFO message
(containing object size, name, and memory information) be returned for each object meeting the
speciÞcations in the type and bank Þelds. Following the last INFO response will be an
ENDOFBANK message.
ENDOFBANK = 0Dh
This message is returned after the last WRITE or INFO response to a READBANK or DIRBANK
message. If no objects matched the speciÞcations in one of these messages, ENDOFBANK will
be the only response.
DELBANK = 0Eh
This message will cause banks of objects (of one or all types) to be deleted from RAM. The type
and bank speciÞcations are the same as for the READBANK message. The deletion will take
place with no conÞrmation. SpeciÞcally, the sender of this message could just as easily delete
every RAM object from the K2600 (for example, type = 0 and bank = 127) as it could delete all
studios from bank 7 (for example, type = 113, bank = 7.)
MOVEBANK = 0Fh
This message is used to move entire banks of RAM objects from one bank to another. A speciÞc
object type may be selected with the type Þeld. Otherwise, if the type Þeld is unspeciÞed (0), all
object types in the bank will be moved. The bank and newbank Þelds must be between 0 and 9.
The acknowledgement is an ENDOFBANK message, with the bank Þeld equal to the new bank
type(2) bank(1) ramonly(1)
type(2) bank(1)
type(2) bank(1)
type(2) bank(1) newbank(1)
System Exclusive Protocol
K2600 System Exclusive Implementation
7-5