Kurzweil K2661, Musician’S Reference Manual

Page: 66 / 500

7-4
System Exclusive Protocol
K2661 System Exclusive Implementation
NEW = 06h type(2) idno(2) size(3) mode(1) name(n)
Creates a new object and responds with an INFO message of the created object. The object’s data
will not be initialized to any default values. If
idno
is zero, the fi rst available object ID number
will be assigned. If
mode
is 0, the request will fail if the object exists. If
mode
is 1, and the object
exists in ROM, a RAM copy will be made. If
mode
is 1, and the object exists in RAM, no action is
taken.
DEL = 07h type(2) idno(2)
Deletes an existing object and responds with an INFO message for the deleted object. If there is
only a RAM copy of the object, the response will indicate that the object doesn’t exist anymore.
However, if the deletion of a RAM object uncovers a ROM object, the INFO response will refer
to the ROM object. A ROM object cannot be deleted.
CHANGE = 08h type(2) idno(2) newid(2) name(n)
Changes the name and/or ID number of an existing object. If
newid
is zero or
newid
equals
idno
,
the ID number is not changed. If
newid
is a legal object id number for the object’s type, then the
existing object will be relocated in the database at the new ID number. This will cause the
deletion of any object which was previously assigned to the
newid
. If the
name
fi eld is null, the
name will not change. Otherwise, the name is changed to the (null-terminated) string in the
name
fi eld.
WRITE = 09h type(2) idno(2) size(3) mode(1) name(n) form(1) data(n) xsum(1)
Writes an entire object’s data directly into the database. It functions like the message sequence
DEL followed by NEW followed by a LOAD of one complete object data structure. It
fi rst
deletes any object already existing at the same type/ID. If no RAM object currently exists there,
a new one will be allocated and the data will be written into it. The object name will be set if the
name
string is non-null. The response to this message will either be a DACK or a DNAK, as with
the load message. The
offs
fi eld of the response will be zero. The K2661 will send a WRITE
message whenever an object is dumped from the front-panel (using a Dump soft button), or in
response to a READ message.
The
mode
fi eld is used to determine how the
idno
fi eld is interpreted.
If
mode
= 0, the
idno
speci fi es the absolute ID number to write to, which must exist (must be
valid). If
idno
equals zero, write to the fi rst available ID number.
If
mode
= 1, the object is written at the fi rst available ID number after what is speci fi ed by
idno
.
It doesn’t matter if
idno
is a legal ID number. Remember that for certain object types, the 100s
through 900s banks allow fewer than 100 objects to be stored (for example, the 100s bank will
store Quick-Access banks at IDs 100–119 only). In this mode, if
idno
were 313, the object would
be written to ID 400 if available.
READ = 0Ah type(2) idno(2) form(1)
Requests the K2661 to send a WRITE message for the given object. No response will be sent if
the object does not exist.
READBANK = 0Bh type(2) bank(1) form(1) ramonly(1)
Requests the K2661 to send a WRITE message for multiple objects within one or all banks.
type
and
bank
specify the group of objects to be returned in WRITE messages. The
type
fi eld
speci fi es a single object type, unless it is zero, in which case objects of all user types will be