Kurzweil K2000 - MUSICIANS GUIDE Musician's Manual page 455

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 K2vx 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 K2vx, which will add all of the objects
contained in the dump to its own object database. IMPORTANT: If the K2vx 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 K2vx before sending the dump, so that the K2vx 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 K2vx is pre-cleared, 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 K2vx 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 type(2) bank(1) ramonly(1)
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 = 0Dhtype(2) bank(1)
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 type(2) bank(1)
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 K2vx (e.g. ÔtypeÕ = 0 and ÔbankÕ = 127) as it could delete all
effects from bank 7 (e.g. ÔtypeÕ = 113, ÔbankÕ = 7.)
MOVEBANK = 0Fh type(2) bank(1) newbank(1)
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
System Exclusive Protocol
K2vx System Exclusive Implementation
30-5