1.3.1Sound Generator Common Block .......................................................................................................... 5
1.3.2Instrument Part Block............................................................................................................................. 6
2Timbre Type Specific Operation ...................................................................................................... 7
3Conditions that Disable Message Send and Receive ...................................................................... 7
6Note Off ........................................................................................................................................... 8
7Note On ........................................................................................................................................... 8
9.13.1Pitch Bend Sensitivity .......................................................................................................................... 14
10.1All Notes Off (7BH) ............................................................................................................................ 16
10.2Omni Off (7CH).................................................................................................................................. 16
10.3Omni On (7DH).................................................................................................................................. 16
18.1.2Master Fine Tuning .............................................................................................................................. 20
18.2Instrument-Specific System Exclusive Message ............................................................................... 23
Part IVInstrument-Specific System Exclusive Messages
19 Format ........................................................................................................................................... 24
19.3Format of Each Field ......................................................................................................................... 25
19.3.1SX : System Exclusive Message Status ............................................................................................... 25
19.3.2MAN : Manufacturer's ID .................................................................................................................... 25
19.3.3MOD : Model ID.................................................................................................................................. 25
19.3.4dev : MIDI Device ID 00H-7FH .......................................................................................................... 26
19.3.7mem : Memory Area ID ....................................................................................................................... 28
19.3.8pset : Parameter Set Number................................................................................................................28
19.3.9blk : Block Number .............................................................................................................................. 29
19.3.10 pkt : Packet Number .............................................................................................................................29
19.3.11 prm : Parameter ID ............................................................................................................................... 29
19.3.12 idx : Data Index Number ...................................................................................................................... 29
19.3.13 len : Data Length .................................................................................................................................. 30
19.3.14 data : Parameter Data ........................................................................................................................... 30
19.3.15 Single Parameter Data Size Limit ........................................................................................................ 30
19.3.16 img : Parameter Set Image ................................................................................................................... 31
19.3.17 sum : Check Sum.................................................................................................................................. 31
19.3.18 EOX : End of System Exclusive Message ........................................................................................... 31
21.1.1One-way and Handshake......................................................................................................................32
21.1.2Session and Subsession ........................................................................................................................ 33
21.2One-way Mode Communication Flow................................................................................................ 33
21.3Handshake Mode Communication Flow ............................................................................................ 34
Part VParameter List
22 Using the Parameter List ............................................................................................................... 38
23 System Parameters ....................................................................................................................... 38
23.1System Information Parameter .......................................................................................................... 38
In terms of a MIDI device, this Instrument consists of a System Section, Performance Controller Section, and Sound Generator
Section. Each of these sections can send and receive specific MIDI Messages in accordance with its function.
1.1System Section
The System Section manages the Instrument status and user data. A communication method known as a "bulk dump" is
supported, which allows two-way transfer of user data between the Instrument and a computer.
1.2Performance Controller Section
The Performance Controller Section performs keyboard play and controller operations, and generates performance messages
in accordance with auto play, etc. Basically, generated performance messages are sent to external destinations while also
being transmitted to the Sound Generator Section. The channel number of the sent channel message is in accordance with
Instrument's instrument part number.
MIDI Output Performance Information
The following describes the performance information that is output and is not output as MIDI signals.
•Output performance
– Keyboard play by the performer
– Auto accompaniment
– Recorder playback
•Non-output performance
– Demo performance
– Song playback
– Lesson function
– Music Challenge
1.3Sound Generator Section
The Sound Generator Section consists of a channel-independent common block and an independent instrument part specific
to each channel. Mainly it receives performance information and sound source setting information.
1.3.1Sound Generator Common Block
The common block consists of system effects, mixer master control, etc. These can be controlled by system exclusive
messages that are basically exclusive to this particular instrument, but several parameters also can be controlled by general
universal system exclusive messages.
5
1.3.2Instrument Part Block
The instrument parts of the sound generator can be operated or their settings can be changed with Instrument-specific system
exclusive messages and channel messages.
The 32 instrument parts of this Instrument are divided between Group A and Group B, each of which has 16 instrument
parts. Only Group B can be controlled by external channel messages. As shown in the following table, there is a fixed
relationship between channel message receive channel numbers and instrument parts.
The sound source operation performed for a received message depends on the current Timbre Type value (see "11.1 About
the Timbre Type), which is the operation mode of each sound generator instrument part. For details, see the explanation
for each message.
3Conditions that Disable Message Send and Receive
All MIDI message send and receive is temporarily disabled while any one of the following processes is in progress.
The channel number of the channel message received by each part is shown in the table under "1.3.2 Instrument Part Block".
5Send Channel
Basically, the MIDI channel of the channel message sent when the Instrument is played coincides with the MIDI channel
of the part being played. Note, however, that the MIDI channel of the performance information that corresponds to the
keyboard main part is the Keyboard Channel setting value.
6Note Off
Format
Message Format: 8nH kkH vvH
9nH kkH 00H (receive only)
n: MIDI Channel Number
kk: Key Number
vv: Velocity
Send40H
ReceiveIgnored
Send
Sent when something is played on the keyboard or when auto accompaniment is used. For keyboard play, the key number
range is changed in accordance with the octave shift function.
Receive
Received by Instrument parts corresponding to MIDI. The velocity value is ignored. A part that is turned off by the Part
Enable Parameter value explained under "24.3 Part Parameter" is not received.
7Note On
Format
Message Format: 9nH kkH vvH
n: MIDI Channel Number
kk: Key Number
vv: Velocity
Send
Sent when something is played on the keyboard. The key number range is changed in accordance with the octave shift
function.
Receive
Received by Instrument parts corresponding to MIDI. The velocity value is ignored. A part that is turned off by the Part
Enable Parameter value explained under "24.3 Part Parameter" is not received.
8
8Polyphonic Key Pressure
Format
Message Format: AnH kkH vvH
n: MIDI Channel Number
kk: Key Number
vv: Pressure Value
Send
This message is not sent by this Instrument.
Receive
This message is not received by this Instrument.
9Control Change
Format
Message Format: BnH ccH vvH
n: MIDI Channel Number
cc: Control Number
vv: Value
Send
Sent when the Instrument's pedal is operated or when Instrument settings are changed.
Receive
Receipt changes the pedal and other performance conditions, and Instrument settings.
9.1Bank Select (00H,20H)
Format
Message Format: BnH 00H mmH (MSB)
BnH 20H llH (LSB)
n: MIDI Channel Number
mm: MSB Value (Note1)
ll: LSB Value
Send00H
ReceiveIgnored
Note 1:
For details about the relationship between the MSB value and the tone, see the Tone List that comes with the Instrument.
Send
Sent when a tone is selected. The LSB value is always 00H.
Receive
Receipt causes a change in the tone bank number stored in Instrument memory, but the tone is not actually changed until
a Program Change message is received.
For details, see "11 Program Change". The LSB value is ignored.
9
9.2Modulation (01H)
Format
Message Format: BnH 01H vvH
n: MIDI Channel Number
vv: Value
Send
This message is not sent by this Instrument.
Receive
Receipt adds, to the tone being sounded, modulation of a depth specified by the value. In the case of a tone that already
has modulation applied, receipt of this message increases the modulation depth. The modulation effect differs according
to the tone being used.
9.3Data Entry (06H,26H)
Format
Message Format: BnH 06H mmH (MSB)
BnH 26H llH (LSB)
n: MIDI Channel Number
mm: MSB Value
ll: LSB Value
Send
Sent when there is a change to the parameter assigned to RPN. This Instrument does not have a parameter that corresponds
to NRPN.
Receive
Receipt changes the parameter assigned to RPN. This Instrument does not have a parameter that corresponds to NRPN.
9.4Volume (07H)
Format
Message Format: BnH 07H vvH
n: MIDI Channel Number
vv: Value
Send
Sent when auto accompaniment is used.
Receive
Receipt changes the volume of the corresponding part.
10
9.5Pan (0AH)
Format
Message Format: BnH 0AH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "33.3 Pan Setting Value Table"
in "Part VII Setting Values and Send/Receive Values".
Send
Sent when auto accompaniment is used.
Receive
Receipt changes the pan setting of the corresponding part.
9.6Expression (0BH)
Format
Message Format: BnH 0BH vvH
n: MIDI Channel Number
vv: Value
Send
Sent when auto accompaniment is used.
Receive
Receipt changes the Expression value.
9.7Hold1 (40H)
Format
Message Format: BnH 40H vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see the "33.1 Off/On Setting Value
Table" in "Part VII Setting Values and Send/Receive Values" of this document.
Send
Sent when a pedal that has a sustain (damper) function is operated.
Receive
Receipt performs an operation equivalent to a sustain pedal operation.
11
Timbre Type Specific Operation
This operation differs in accordance with the Timbre Type (see "11.1 About the Timbre Type") setting.
•Timbre Type: Melody
Sustain off/on control is performed in accordance with the value of the received message.
•Timbre Type: Drum
The received message does not affect sound source operation.
9.8Sostenuto (42H)
Format
Message Format: BnH 42H vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see the "33.1 Off/On Setting Value
Table" in "Part VII Setting Values and Send/Receive Values" of this document.
Send
Sent when a pedal that has a sostenuto function is operated.
Receive
Receipt performs an operation equivalent to a sostenuto pedal operation.
9.9Soft (43H)
Format
Message Format: BnH 43H vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see the "33.1 Off/On Setting Value
Table" in "Part VII Setting Values and Send/Receive Values" of this document.
Send
Sent when a pedal that has a soft function is operated.
Receive
Receipt performs an operation equivalent to a soft pedal operation.
9.10Reverb Send (5BH)
Format
Message Format: BnH 5BH vvH
n: MIDI Channel Number
vv: Value
12
Send
Sent when auto accompaniment is used.
Receive
Changes Reverb Send.
9.11Chorus Send (5DH)
Format
Message Format: BnH 5DH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
The setting value matches the value that is sent and received.
Send
Sent when auto accompaniment is used and when a Chorus on/off operation is performed.
Receive
Changes Chorus Send.
9.12NRPN (62H,63H)
Format
Message Format: BnH 62H llH (LSB)
BnH 63H mmH (MSB)
n: MIDI Channel Number
ll: LSB Value
mm: MSB Value
Send
This message is not sent by this Instrument.
Receive
This Instrument does not have a corresponding NRPN message.
9.13RPN (64H,65H)
Format
Message Format: BnH 64H llH (LSB)
BnH 65H mmH (MSB)
n: MIDI Channel Number
11: LSB Value
mm: MSB Value
13
9.13.1Pitch Bend Sensitivity
Format
Message Format: BnH 64H 00H
BnH 65H 00H
BnH 06H mmH
BnH 26H llH
n: MIDI Channel Number
mm: MSB Value 0 - 12
ll: LSB Value
Send00H
ReceiveIgnored
Send
Sent when the Bend Range is changed on the CTK-5000, WK-500, or CDP-200R.
Receive
Receipt changes Bend Range.
9.13.2Fine Tune
Format
Message Format: BnH 64H 01H
BnH 65H 00H
BnH 06H mmH
BnH 26H llH
n: MIDI Channel Number
mm: MSB Value
ll: LSB Value
Send
This message is not sent by this Instrument.
Receive
Receipt changes Channel Fine Tune.
9.13.3Coarse Tune
Format
Message Format: BnH 64H 02H
BnH 65H 00H
BnH 06H mmH
BnH 26H llH
n: MIDI Channel Number
mm: MSB Value
ll: LSB Value
14
Send
This message is not sent by this Instrument.
Receive
Receipt changes Channel Coarse Tune. Does not affect sound source operation when the Timbre Type is Drum.
9.13.4Null
Format
Message Format: BnH 64H 7FH
BnH 65H 7FH
n: MIDI Channel Number
Send
Sent after the Bend Range is changed on the CTK-5000, WK-500, or CDP-200R.
Receive
Receipt deselects RPN.
9.14All Sound Off (78H)
Format
Message Format: BnH 78H 00H
n: MIDI Channel Number
Send
Sent when Local is set to OFF on the Instrument.
Receive
Receipt stops all voices that are sounding.
9.15Reset All Controllers (79H)
Format
Message Format: BnH 79H 00H
n: MIDI Channel Number
Send
Sent when MIDI send related settings are changed on the Instrument.
Receive
Receipt initializes each performance controller.
15
10Mode Message
10.1All Notes Off (7BH)
Format
Message Format: BnH 7BH 00H
n: MIDI Channel Number
Send
Sent when MIDI send related settings are changed on the Instrument, or when auto play is stopped, etc.
Receive
Receipt of any of this message releases the currently sounding voice (same as releasing the keyboard key).
10.2Omni Off (7CH)
Format
Message Format: BnH 7CH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message performs the same operation as when All Notes Off is received.
10.3Omni On (7DH)
Format
Message Format: BnH 7DH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message performs the same operation as when All Notes Off is received.
10.4Mono (7EH)
Format
Message Format: BnH 7EH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message performs the same operation as when All Notes Off is received.
16
10.5Poly (7FH)
Format
Message Format: BnH 7FH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message performs the same operation as when All Notes Off is received.
11Program Change
Format
Message Format: CnH ppH
n: MIDI Channel Number
pp: Program Number (Note1)
Note 1:
For details about the relationship between the program number and the tone, see the Tone List that comes with the Instrument.
Send
Sent when a tone is selected.
Receive
Receipt of this message changes the tone of the part that corresponds to the MIDI channel.
The selected tone is determined by the program value of this message and the Bank Select message value received prior
to this message.
Also note that receipt of this message also may change the Timbre Type that corresponds to the selected tone. For more
information, see "11.1 About the Timbre Type" below.
11.1About the Timbre Type
Tones that are selected by each Instrument part have an attribute that depends on the sound source operation type. This
attribute is called the "timbre type," which is one of the types described below.
•Melody
This timbre type optimizes for normal melody tones.
•Drum
This setting optimizes for drum sounds. The damper pedal does not function. The Hold1, Channel Coarse Tune,
and Master Coarse Tune messages are ignored if they are received.
17
12Channel Aftertouch
Format
Message Format: DnH vvH
n: MIDI Channel Number
vv: Value
Send
These messages are never sent.
Receive
Receipt of this message adds modulation to the voice that is sounding. The modulation effect differs according to the tone
being used.
13Pitch Bend
Format
Message Format: EnH llH mmH
n: MIDI Channel Number
ll: Value LSB
mm: Value MSB
Send
Sent when a pitch bender operation is performed on the CTK-5000, WK-500, or CDP-200R.
Receive
Receipt changes the pitch of the currently sounding note. The range of the pitch change depends on the Bend Range value
setting.
18
Part III
System Messages
14Timing Clock
Format
Message Format: F8H
Send
Sent when auto accompaniment is used.
Receive
This message is not received by this Instrument.
15Start
Format
Message Format: FAH
Send
Sent when auto accompaniment is used.
Receive
This message is not received by this Instrument.
16Stop
Format
Message Format: FCH
Send
Sent when auto accompaniment is used.
Receive
This message is not received by this Instrument.
17Active Sensing
Format
Message Format: FEH
Send
This message is never sent.
19
Receive
Once this message is received, the Active Sensing mode is entered. If no MIDI message is received for a specified amount
of time, voices being sounded by the Instrument's sound source are released, the controller is reset, and the Active Sensing
mode is exited.
18System Exclusive Message
Format
Message Format: F0H....F7H
The Instrument sends and receives standard universal system exclusive messages, and system exclusive messages that have
Instrument-specific formats.
18.1Universal Realtime System Exclusive Message
Format
Message Format: F0H 7FH....F7H
18.1.1Master Volume
Format
Message Format: F0H 7FH 7FH 04H 01H llH mmH F7H
ll: LSB Value
mm: MSB Value
Send
This message is never sent.
Receive
Receipt changes the Master Volume parameter. Note that the Master Volume parameter cannot be changed with an Instrument
operation.
18.1.2Master Fine Tuning
Format
Message Format: F0H 7FH 7FH 04H 03H llH mmH F7H
mm: MSB Value(Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "33.4 -100 - 0 - +99 Setting
Value Table" in "Part VII Setting Values and Send/Receive Values" of this document.
Send
This message is sent when the tuning setting is changed.
Receive
Receipt changes the tuning setting.
20
18.1.3Master Coarse Tuning
Format
Message Format: F0H 7FH 7FH 04H 04H 00H mmH F7H
ll: LSB Value
mm: MSB Value
Send
Sent when Transpose is changed.
Receive
Receipt changes the Transpose parameter. Does not affect sound source operation when the Timbre Type is Drum.
18.1.4Reverb Parameter
Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 01H ppH vvH F7H
pp: Parameter
vv: Value
Time Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 01H 01H vvH F7H
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "33.5 Reverb Time Setting Value
Table" in "Part VII Setting Values and Send/Receive Values" of this document.
Send
Sent when the Reverb duration is changed.
Receive
Receipt changes the Reverb duration.
18.1.5Chorus Parameter
Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H ppH vvH F7H
pp: Parameter
vv: Value
Type Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H 00H vvH F7H
vv: Value (Note1)
21
Note 1:
For information about the relationship between setting values and send/receive values, see "33.6 Chorus Type Setting Value
Table" in "Part VII Setting Values and Send/Receive Values".
Send
This message is sent when the System Chorus Type setting is changed.
Receive
Receipt changes the System Chorus Type parameter.
Rate Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H 01H vvH F7H
vv: Value (Note1)
Note 1:
The setting value matches the value that is sent and received.
Send
This message is never sent.
Receive
Receipt changes the System Chorus Rate parameter.
18.1.6GM System Message
GM System On Format
Message Format: F0H 7EH 7FH 09H 01H F7H
Send
This message is never sent.
Receive
Receipt puts the sound source into a GM sound source mode.
GM System Off Format
Message Format: F0H 7EH 7FH 09H 02H F7H
Send
This message is never sent.
Receive
Receipt changes the sound source setting to the Instrument presetting.
GM2 System On Format
Message Format: F0H 7EH 7FH 09H 03H F7H
Send
This message is never sent.
Receive
Though the Instrument does not support GM2, receipt of the GM2 System On message has the same result as receipt of
the GM System On message.
Receipt performs the same operation as when the GM System On message is received.
18.2Instrument-Specific System Exclusive Message
Format
Message Format: F0H 44H 16H 01H....F7H
This message can be used to send the Instrument memory status, for two-way transfer of special operation commands and
user data, to perform sound source parameter operations, etc.
For more information, see "Part IV Instrument-Specific System Exclusive Messages".
23
Part IV
Instrument-Specific System Exclusive Messages
19Format
This section explains the format of the Instrument-specific System Exclusive Messages. See "Part V Parameter List" and
"Part VI Parameter Set List" for information about how parameter sets actually are transferred.
19.1Message Classifications
Basically, the operation that corresponds to Instrument-specific system exclusive messages is parameter data transfer. The
following operations can be performed from an external device using this parameter transfer message.
•Modification of an individual Instrument parameter
•Batch modification of a particular Instrument parameter set
•Import of an individual Instrument parameter value
•Batch import of a particular Instrument parameter set
In addition to parameters being used as device setting values, some parameters act as commands when received by the
Instrument and as device status information when sent from the Instrument. The following table shows the parameter category
for each type of transfer.
Function Section Parameter Category Description
SystemSystemCommands to the Instrument, Instrument stats
ToneSampled sound (melody/drum) selected by the user
DrumSampled sound (drum) referenced from "Tone" category
parameters
InstrumentIndividual instrument setting referenced from
"Drum" category parameters
Wave ParameterSampled sound Wave setting
Wave DataWaveform actual data referenced from "Wave
Parameter" category parameters
24
19.2Basic Message Structure
Instrument-specific system exclusive message operation can be broadly divided between two methods: Individual Parameter
Transfer (single parameter send/receive) and Bulk Parameter Set Transfer (batch parameter send/receive). Each method
includes a number of different messages. The field in the SysEx message that specifies the message type is the action (act)
field. The format of the "body" part of the message depends on the "act" value.
The table below shows the body format for each action of Instrument-specific system exclusive messages. An actual message
consists of the items indicated by "Y", from left to right.
actSXMAN MODdevactbody (Depends on act)EOX
catmem psetblkpktprmidxlendataimgsum
NOPYYYYY-----------Y
IPRYYYYYYYYY-YYY---Y
IPSYYYYYYYYY-YYYY--Y
OBRYYYYYYYY--------Y
OBSYYYYYYYY-Y--Y-YYY
HBRYYYYYYYY--------Y
HBSYYYYYYYY-Y--Y-YYY
ACKYYYYYYYY--------Y
BSYYYYYYYYY--------Y
RJCYYYYYYYY--------Y
EODYYYYYYYY--------Y
EOSYYYYYYYY--------Y
ERRYYYYYYYY--------Y
19.3Format of Each Field
19.3.1SX : System Exclusive Message Status
Format: 11110000B
System Exclusive message Status = F0H
19.3.2MAN : Manufacturer's ID
Format: 01000100B
Manufacturer's ID = 44H (CASIO)
19.3.3MOD : Model ID
Format: 00010101B (MSB)00000001B (LSB)
The Model ID of the series to which the Instrument belongs is shown by two consecutive bytes (MSB, LSB).
(CTK-4000/CTK-5000/LK-270/LK-205/WK-200/WK-500/CDP-200R Model ID MSB = 16H, LSB = 01H)
25
19.3.4dev : MIDI Device ID 00H-7FH
Format: 0dddddddB
The contents of this field in a received message are compared with the Model's MIDI Device ID, and receipt of the incoming
message is allowed only when the two IDs match. When a message containing 7FH is received, receipt of the message is
always allowed, regardless of the Instrument's ID setting.
Note, however, that the Instrument does not have a specific Device ID, so use only 7FH for send and receive.
19.3.5act : Action
Format: 0aaaaaaaB
aaaaaaaB = Action
This field indicates the operation of the Instrument-specific System Exclusive Message.
aaaaaaaB ActionFunction
00H NOPNo Operation
01H IPRIndividual Parameter Request
02H IPSIndividual Parameter Send
03H OBROneway Bulk Parameter Set Request
04H OBSOneway Bulk Parameter Set Send
05H HBRHandshake Bulk Parameter Set Request
06H HBSHandshake Bulk Parameter Set Send
0AH ACKAcknowledge
0BH BSYBusy
0CH RJCReject
0DH EODEnd of Data
0EH EOSEnd of Session
0FH ERRError
NOP: No Operation
No operation is performed when this action is received.
IPR: Individual Parameter Request
Indicates an individual parameter value send request message. When the Instrument receives this action, it uses an IPS
message to return the specified parameter value.
IPS: Individual Parameter Send
Indicates an individual parameter value send message. When the Instrument receives this action, it rewrites the value specified
by the data field with the specified parameter value.
OBR: Oneway Bulk Parameter Set Request
Indicates a send request message using parameter set image one-way mode. When the Instrument receives this action, it
uses an OBS message to return the specified parameter set.
OBS: Oneway Bulk Parameter Set Send
Indicates a parameter set image send message using one-way mode. The parameter set to be transferred is divided into
multiple packets when it is greater than a prescribed size. At this time, packets are transferred at intervals of the prescribed
time (20 msec) or greater.
HBR: Handshake Bulk Parameter Set Request
Indicates a send request message using the parameter set image handshake mode. When the Instrument receives this action,
it uses an HBS message to return the specified parameter set.
26
HBS: Handshake Bulk Parameter Set Send
Indicates a parameter set image send message using handshake mode. The parameter set to be transferred is divided into
multiple packets when it is greater than a prescribed size. The packets are transferred in accordance with handshake mode.
ACK: Acknowledge
Indicates a message used by the receiver during parameter set handshake mode transfer to convey to the sender that it is
ready for send of the next packet. The cat, mem, and pset fields indicate the value carried by the last received message.
BSY: Busy
Indicates a message to convey to the requester that that the Instrument cannot send back data after a parameter set oneway mode or handshake mode send request is received. The cat, mem, and pset fields indicate the value carried by the
last received message.
RJC: Reject
Indicates a message to convey to the other side that an ongoing parameter set one-way mode or handshake mode send or
receive session was interrupted. The cat, mem, and pset fields indicate the value carried by the last received message.
EOD: End of Data
Indicates a message to convey to the receiver that a one-way mode or handshake mode serial packet transfer for sending
a sub-session (one parameter set) is complete. The cat, mem, and pset fields indicate the value carried by the last received
message.
EOS: End of Session
Indicates a message to convey to the receiver that a one-way mode or handshake mode serial parameter set transfer session
send, which was launched by some operation, is complete. The cat, mem, and pset fields indicate the value carried by the
last received message.
ERR: Error
Indicates a message to convey to the sender that the checksum or message format of the previous packet was not correct
when receiving a parameter set with handshake mode. The cat, mem, and pset fields indicate the value carried by the last
received message.
27
19.3.6cat : Category
Format: 0cccccccB
0cccccccB = Category (7bit)
The category indicates the categories of data handled by the System Exclusive Message. The ID number (ID) of the Category
is indicated on the left, while the communication operation (Action) is indicated on the right.
CategoryTransfer
ID (c)Parameter SetIndividual ParameterOne Way BulkHandshake Bulk
00HSystemA--
02HPatchA--
03HToneAAA
06HDrumAAA
0DHInstrumentAAA
0EHWave ParameterAAA
0FHWave DataFAA
12HScale MemoryAAA
1FHAllFAA
20HSongFAA
21HSequenceFAA
22HRegistrationFAA
23HLesson RecFAA
24HRhythmFAA
A .. Available (Also including when only some parameters are available.)
F... File Information (Not the data itself. Name, size, and other file information only.)
-... Not Available
19.3.7mem : Memory Area ID
Format: 0mmmmmmmB
Specifies the memory area that is the object of the parameter transfer. The following are defined for this Instrument.
MemTypeMeaning
0User areaRead/write enabled
1Preset areaRead/write disabled
19.3.8pset : Parameter Set Number
Format: 0nnnnnnnB (LSB)0mmmmmmmB (MSB)
This field is a 2-byte (LSB, MSB) value indicating the number of the parameter set (mmmmmmmnnnnnnnB, Binary)
being transferred.
28
19.3.9blk : Block Number
The block number is a supplementary number that specifies which block parameter is to be accessed.
Format: 0iiiiiiiB (LSB)0jjjjjjjB0kkkkkkkB (MSB)
Block Bit Field Division
When the parameter block has a multi-dimensional array structure, bit 21 of the block number is divided into prescribed
bit fields based on the rules explained below.
•Case 1
When an array has three or fewer nesting levels and the number of arrays in each dimension is 128 or less, they are assigned
below the three 7-bit fields. Unused regions are filled will zeros.
Example:
parameter [A][B][C]
With a 3-dimensional array parameter that consists of A=8 (3 bits), B=5 (3 bits) and C=10 (4 bits), the block bit fields are
allocated as: Block = 0000aaa 000bbb ccccccc (Binary).
•Case 2
When Case 1 conditions are not satisfied, the minimal number of fields required for each number of arrays is reserved from
the lower bit of the block. Unused regions are filled will zeros. (This case does not apply with this Instrument.)
Example 1:
parameter [A][B][C][D]
With a 4-dimensional array parameter that consists of A=3 (2 bits), B=4 (2 bits), C=3 (2 bits) and D=4 (2 bits) like the one
shown above, the block bit fields are allocated as: Block = 0000000 00000a abbccdd (Binary).
Example 2:
parameter [A][B]
A=3 (2 bits), B=200 (8 bits)
With a 2-dimensional array parameter like the one shown above, the block bit fields are allocated as: Block = 0000000 000aab bbbbbbb (Binary).
19.3.10pkt : Packet Number
Format: 0iiiiiiiB (LSB)0jjjjjjjB0kkkkkkkB (MSB)
This is the divided packet number kkkkkkkjjjjjjjiiiiiiiB (Binary) for transferring a single parameter set.
19.3.11prm : Parameter ID
Format: 0pppppppB (LSB) 0qqqqqqqB (MSB)
The Parameter ID indicates the parameter type. When transferring parameters (see "Part V Parameter List" below) individually
(as opposed to bulk transfer), this field is used to identify the parameter being transferred by its parameter ID.
19.3.12idx : Data Index Number
Format: 0iiiiiiiB (LSB) 0jjjjjjjB (MSB)
The data index number indicates the first array number of the array from which transfer starts.
29
19.3.13len : Data Length
Format: 0lllllllB (LSB) 0mmmmmmmB (MSB)
As shown below, the meaning of this field differs depending on whether an individual transfer or a bulk parameter set
transfer is being performed.
Individual Parameter Transfer
Data length indicates the length of the array being transferred minus 1 when the parameter contains a character string or
other similar array structure.
Bulk Parameter Set Transfer
Data length indicates the number of bytes of data included within a packet. When this value is zero, it means there is no
actual data.
Parameter data indicates the parameter value. Data that is the size of the number of arrays equivalent to len + 1 follows.
For the structure of one data item, the length depends on the data bit width, as shown below.
dddddB + 1Number of Data
1 - 71
8 - 142
15 - 213
22 - 284
29 - 325
Each block of data is packed from the lowest order byte first. In the case of multiple-byte data, the lowest weighted bit
is the LSB of the first "data" block, and the highest weighted bit is the MSB of the final "data" block. The following
shows an example of how data would be divided for transfer in the case of 32-bit data.
With the Instrument's system exclusive message format, the size of a single message cannot exceed 256 bytes. The data
size and the array size, however, can cause a packet to exceed 256 bytes when transferring a single parameter array. In
this case, the IPS and IPR message data length and data index number values can be modified to enable division of a
single parameter value into multiple messages so it can be sent that way.
30
19.3.16img : Parameter Set Image
Format: 0dddddddB0cccccccB000000abB
For a bulk data transfer operation, the parameter set data to be transferred is read sequentially in 16-bit units starting from
the top address. Read values are divided into 3-byte segments as shown below, and then sent in sequence.
The following is the conversion format, which is the same as the individual parameter 16-bit transfer detailed above.
16-bit Memory Image
MSB: abccccccB
LSB: cdddddddB
↓
data0: 0dddddddB
data1: 0cccccccB
data2: 000000abB
If the length of the data being transferred is an odd number of bytes, the final bit field is filled in with zero.
Parameter Set Packet Division
The maximum image size of the parameter set that can be sent with one packet is 128 bytes. When data that exceeds 128
bytes is transferred, data is always divided into 128-byte units, except for the final packet. Because of this, the data in
received packets can be stored in an areas the size of [Parameter Set Start Address] + [Packet Number] × 128.
For bulk parameter set transfer, the 16-bit image is divided in 3-byte groups, so the img field length is the value produced
by multiplying the len value (len + 1 when len is an odd number) by 3/2. Note, however, that a parameter set of 128 bytes
or less can be sent using a single packet, and anything greater than 128 bytes is divided among multiple packets. This
means that the maximum length "data" field is 128 × 3/2 = 192 bytes.
Only one parameter set can be transferred per session, and data from different parameter sets cannot be mixed within a
single packet, even when sending multiple parameter sets. Different parameter sets are always divided into separate packets.
19.3.17sum : Check Sum
Format: 0sssssssB
In this case, this "sum" field contains a value, which, when added to the total value of the "img" field, makes the lower
seven bits 0.
The receiving side checks if this is true, and performs error handling (re-request, etc.) if it is not.
19.3.18EOX : End of System Exclusive Message
Format: 11110111B
(End of System Exclusive message Status = F7H)
31
20Individual Parameter Operations
There are two parameter unit operations: Individual Parameter Transfer and Individual Parameter Request.
For one session, in response to an IPR (Individual Parameter Request) from an external device, this Instrument returns an
IPS (Individual Parameter Send) or the session is concluded when the external device or this Instrument spontaneously
sends an IPS. If this Instrument received an IPS, the value of the applicable parameter is changed.
Depending on the function of a parameter, Individual Parameter Send may be used to issue a command to the Instrument
and Individual Parameter Request may be used to check Instrument status information.
Data ReceiverData SenderOperation
IPR →Send Request (Optional)
← IPSData Transfer
21Parameter Set Transfer
21.1Communication Modes
21.1.1One-way and Handshake
In order to ensure maximum speed for bulk dumping of Parameter Sets, the data format is different from the data format
used for Individual Parameter Send. Data is transferred as-is, using the Model's memory image.
Parameter Sets can be transferred by bulk dump using the message exchange types described below.
•One-way mode Parameter Set send/receive
•One-way mode Parameter Set send request send/receive
With the one-way mode, the sending device sends data and ends the session without regard to the response of the receiving
device. This mode is best for one-way transfers from a sequencer or similar device. With the handshake mode, the sending
device sends the data and then waits for a response from the receiving device before advancing to the next session. This
is a high-speed mode in which there is no time wasted waiting.
See "Part VI Parameter Set List" for details about Instrument parameter sets.
32
21.1.2Session and Subsession
Subsession
"One subsession" refers to transfer of one parameter set. A subsession transfers one parameter set or a parameter set that
has been divided into multiple packets for transfer, with EOD (End of Data) at the end to terminate the send.
Division of a parameter set into multiple packets is used when the size of the parameter set is greater than a prescribed
size. The packet number in the packet index field indicates the sequential position of a packet relative to the other packets.
A single packet cannot be used to transfer multiple small parameter sets. A parameter set delimiter always must be transferred
as a packet delimiter.
Session
"One session" refers to a series of processes that occur for one user operation. One subsession or multiple subsessions
make up a session. The sender sends EOS (End of Session) to end a session.
Regardless of whether there is a single parameter set or multiple parameter sets being transferred, a bulk dump always
takes the form of a session, never a subsession only.
21.2One-way Mode Communication Flow
A session starts with the receiving device sending a request using an OBR, or with the sending device sending OBS data.
The session ends after transfer of all the data in the parameter set being transferred by the sending device is complete.
The transferred messages of a single parameter set cannot exceed 256 bytes. When 256 bytes are exceeded, data is divided
into multiple packets of 256 bytes or less each and transferred at fixed intervals (20 msec).
A final EOD informs the receiving device when the session is ended.
Data Receiver
(External Device)
OBR →Send Request (Optional)
Other subsessions
Data Sender
(This Instrument)
←OBS
(20 msec or greater interval)
←OBS
(20 msec or greater interval)
←OBS
(20 msec or greater interval)
:
:
←EODEnd of Data
:
:
←EOSEnd of Session
Operation
Data Transfer
Data Transfer
Data Transfer
33
21.3Handshake Mode Communication Flow
A session starts with the receiving device sending a request using a HBR, or with the sending device sending HBS data.
The sending device does not send the next packet until it receives an ACK from the receiving device. The maximum wait
time of at least 2000 msec is reserved. Failure of a response to arrive within the wait time is treated as a timeout error,
and data communication is terminated.
The receiving devices returns ERR (error) when there is mismatch in the received data checksum or when an incompatible
data format is discovered. When the sending device receives ERR (error) from the receiving device, it resends the last data
sent. If an error repeats a number of times (three times or more for this Instrument), either the sending device or the receiving
device sends an RJC to terminate the session.
A session ends after the sending device transfers the volume of data determined by the number of parameter sets being
transferred, and sends EOD and EOS in response to an ACK from the sending device.
Data ReceiverData SenderOperation
HBR→Send Request (Optional)
←HBSData Send
ACK→Acknowledge
←HBSData Send
ACK→Acknowledge
:
:
ACK→Acknowledge
←EODEnd of Data
:
Other subsessions
:
←EOSEnd of Session
34
The packed with the same packet number is resent when a checksum mismatch or incompatible data format error is detected.
Data ReceiverData SenderOperation
HBR→Send Request (Optional)
←HBSData Send
ACK→Acknowledge
←HBSData Send 1
ERR→Error
←HBSData Send 2 (Retry 1)
ERR→Error
←HBSData Send 3 (Retry 2)
ACK→Acknowledge
:
:
ACK→Acknowledge
←EODEnd of Data
:
Other subsessions
:
←EOSEnd of Session
Session terminates if ERR is detected a number of times.
Data ReceiverData SenderOperation
HBR→Send Request (Optional)
←HBSData Send
ACK→Acknowledge
←HBSData Send
(Error generated)
ERR→Error
←HBSData Send (Retry 1)
(Error generated)
ERR→Error
←HBSData Send (Retry 2)
(Error generated)
ERR
(Error generated)
RJC→Session stopped
→Error
←HBSData Send (Retry 3)
35
RJC is sent to terminate the session in case ACK cannot be recognized.
Data ReceiverData SenderOperation
HBR →Send Request (Optional)
← HBSData Send
:
(Fixed amount of time elapses)
RJC ←Timeout error
The session can be canceled for any reason by sending an RJC. RJC can be sent by the sending device or the receiving
device. The bulk dump session is terminated immediately upon receipt of an RJC.
Data ReceiverData SenderOperation
HBR →Send Request (Optional)
← HBSData Send
ACK →Acknowledge
← HBSData Send
:
:
(Terminate operation)
RJC →Data Receive Canceled
Data ReceiverData SenderOperation
HBR →Send Request (Optional)
ACK →Acknowledge
← HBSData Send
ACK →Acknowledge
← HBSData Send
:
:
(Terminate operation)
← RJCData Send Canceled
BSY is returned to the external device when OBS, OBR, HBS, or HBR is sent while the Instrument mode is not suitable
to perform bulk dump, etc. After BSY is received, the external device should wait until the Instrument enters a mode in
which the session is enabled.
Data ReceiverData SenderOperation
OBR →Send Request
← BSYSend Rejected
36
Data ReceiverData SenderOperation
← OBSData Send
BSY →Receive Rejected
Data ReceiverData SenderOperation
HBR →Send Request
← BSYSend Rejected
Data ReceiverData SenderOperation
← HBSData Send
BSY →Receive Rejected
37
Part V
Parameter List
This section explains the parameters that actually can be transferred by the Instrument.
22Using the Parameter List
•Parameter field
Shows the parameter name.
•ID field
Shows the parameter ID as a hexadecimal number.
•R/W field
Shows "R" to indicate that an IPR (Individual Parameter Request) read operation (Read) is possible or "W" to
indicate that an IPS (Individual Parameter Send) write operation is possible.
•Block field
Shows the bit field allocation of the block number. The bit field position is shown as a decimal format number.
•Size field
Shows the parameter bit width as a decimal format value.
•Array field
Shows the parameter array size as a hexadecimal value.
•Min-Def-Max field
Shows the minimum value, default value, and maximum value for parameter acquisition as a hexadecimal value.
•Description field
Explains the meaning of parameter values. Unless otherwise specified, setting values are all indicated in decimal
format.
23System Parameters
These parameters make it possible for an external device to check the status of the Instrument and for an external device
to command some operation of the Instrument.
23.1System Information Parameter
This parameter is a container for system information.
Shows the parameter set number value.
Applicable parameter set numbers are those in the user area where the top number is zero, and are not the same
numbers as those displayed by the Instrument.
43
Part VII
Setting Values and Send
/
Receive Values
33Setting Value Tables
33.4-100 - 0 - +99 Setting Value Table
Transmit/Receive ValueParameter
(MSB-LSB)
00H-00H-100
::
40H-00H0
::
7FH-7FH99
33.1Off/On Setting Value Table
Transmit ValueReceive ValueParameter
00H00H - 3FHOff
7FH40H - 7FHOn
33.2-64 - 0 - +63 Setting Value Table
Transmit/Receive ValueParameter
00H-64
01H-63
::
40H0
::
7EH62
7FH63
33.3Pan Setting Value Table
Transmit/Receive ValueParameter
00HLeft
::
40HCenter
::
7FHRight
33.5Reverb Time Setting Value Table
Transmit/Receive ValueParameter
00H OFF
0CH1
18H2
24H3
30H4
3CH5
48H6
54H7
60H8
6CH9
72H10
33.6Chorus Type Setting Value Table
Transmit/Receive ValueParameter
00HChorus Type1
01HChorus Type2
02HChorus Type3
03HChorus Type4
04HChorus Type5
44
Part VIII
MIDI Implementation
Notation
34Value Notation
34.1Hexadecimal Notation
MIDI implementation sometimes requires that data be
expressed in hexadecimal format. Hexadecimal values are
indicated by the letter "H" after the value. The hexadecimal
equivalents of decimal values 10 through 15 are expressed
as the letters A through F. The table below shows the
hexadecimal equivalents for decimal values 0 through 127,
which are often used in MIDI messages.
Decimal
Hexadecimal
000H3220H6440H9660H
101H3321H6541H9761H
202H3422H6642H9862H
303H3523H6743H9963H
404H3624H6844H10064H
505H3725H6945H10165H
606H3826H7046H10266H
707H3927H7147H10367H
808H4028H7248H10468H
909H4129H7349H10569H
100AH422AH744AH1066AH
110BH432BH754BH1076BH
120CH442CH764CH1086CH
130DH452DH774DH1096DH
140EH462EH784EH1106EH
150FH472FH794FH1116FH
1610H4830H8050H11270H
1711H4931H8151H11371H
1812H5032H8252H11472H
1913H5133H8353H11573H
2014H5234H8454H11674H
2115H5335H8555H11775H
2216H5436H8656H11876H
2317H5537H8757H11977H
2418H5638H8858H12078H
2519H5739H8959H12179H
261AH583AH905AH1227AH
271BH593BH915BH1237BH
281CH603CH925CH1247CH
291DH613DH935DH1257DH
301EH623EH945EH1267EH
311FH633FH955FH1277FH
Decimal
Hexadecimal
Decimal
Hexadecimal
Decimal
Hexadecimal
34.2Binary Notation
When a MIDI implementation data value is expressed in
binary, the letter "B" (for "binary") is affixed at the end of
the value. The table below shows the binary equivalents for
the decimal values 0 through 127, which are often used for
settings.
Decimal
1257DH01111101B
1267EH01111110B
1277FH01111111B
Hexadecimal
000H00000000B
101H00000001B
202H00000010B
303H00000011B
404H00000100B
505H00000101B
606H00000110B
707H00000111B
808H00001000B
909H00001001B
100AH00001010B
110BH00001011B
120CH00001100B
130DH00001101B
140EH00001110B
150FH00001111B
1610H00010000B
::
Binary
45
CASIO COMPUTER CO.,LTD.
6-2, Hon-machi 1-chome
Shibuya-ku, Tokyo 151-8543, Japan
MA0812-A
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.