6Note Off ........................................................................................................................................... 8
7Note On ........................................................................................................................................... 8
9.17.1Pitch Bend Sensitivity ..........................................................................................................................15
10.1All Notes Off (7BH) ............................................................................................................................ 17
10.2Omni Off (7CH).................................................................................................................................. 18
10.3Omni On (7DH).................................................................................................................................. 18
11 Program Change ........................................................................................................................... 19
11.1About the Timbre Type ...................................................................................................................... 19
11.2DSP Assignments During Tone Selection ......................................................................................... 19
11.2.1DSP Line Structure...............................................................................................................................19
11.2.2DSP Line Assignment............................. .............................................................................................19
11.2.3Use of the Same DSP Line by Multiple Parts......................................................................................20
15.1.3Master Fine Tuning ..............................................................................................................................22
15.2Instrument-Specific System Exclusive Message ............................................................................... 26
Part IVInstrument-Specific System Exclusive Messages
16 Format ........................................................................................................................................... 27
16.3Format of Each Field ......................................................................................................................... 28
16.3.1SX : System Exclusive Message Status ...............................................................................................28
16.3.2MAN : Manufacturer's ID ....................................................................................................................28
16.3.3MOD : Model ID..................................................................................................................................28
16.3.7mem : Memory Area ID .......................................................................................................................31
16.3.8pset : Parameter Set Number................................................................................................................31
16.3.9blk : Block Number ..............................................................................................................................31
16.3.10 pkt : Packet Number .............................................................................................................................32
16.3.12 idx : Data Index Number ......................................................................................................................32
16.3.13 len : Data Length..................................................................................................................................32
16.3.14 data : Parameter Data...........................................................................................................................32
16.3.15 img : Parameter Set Image ...................................................................................................................33
16.3.16 sum : Check Sum..................................................................................................................................33
16.3.17 EOX : End of System Exclusive Message ...........................................................................................34
18.1.1One-way and Handshake......................................................................................................................34
18.1.2Session and Subsession........................... .............................................................................................35
18.2One-way Mode Communication Flow................................................................................................ 35
18.3Handshake Mode Communication Flow ............................................................................................ 36
Part VParameter List
19 System Parameters ....................................................................................................................... 39
19.1System Information Parameter.......................................................................................................... 39
As a MIDI device, the instrument consists of the System Section, Performance Controller Section, and Sound Generator
Section described below. Each of these sections can send and receive specific MIDI Messages in acco rdance with its function.
•System Section
– Device Settings
•Sound Generator Section
– Common
∗ Sound Generator Common Block
∗ System Effect Block
∗ Master Effect Block (Brilliance Function)
∗ Mixer Ma ster Block
•Performance Controller Section
– Keyboard
– Pedal and other real-time controllers
– Auto Accompaniment and Auto Accompaniment function
1.1System Section
The System Section is divided between a sound generator and functions that are not directly related to Instrument play.
In addition to manipulating Instrument setting parameters, this section is also used to exchange commands and information.
For example, parameters can be initialized upon receipt of a System Section MIDI message, and memory use information
can be sent.
1.2Performance Controller Section
The Performance Controller Section consists of the keyboard, pedal and other real-time controllers, as well as blocks that
generate auto accompaniment, auto performance, and other performance information.
An operation causes the corresponding message to be transmitted to the sound generator and to be sent from MIDI OUT.
The channel number of the sent message is in accordance with Instrument's part number.
1.3Auto Accompaniment and Auto Performance MIDI Send
This document includes information for each type of information that describes what operation causes the message to be
sent. However, since there are so many messages sent by an auto accompaniment or auto performance operation, those
messages are not covered herein.
5
1.4Sound Generator Section
The Sound Generator Section consists of a common part that does not depend on the channel and a part that specific to
each channel. Mainly it receives performance information and performs operations.
1.4.1Sound Generator Common Block
The common section consists of a sound generator setting blocks that do not depend on the sound generator part, such as
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.
1.4.2Part Block
The parts of the sound generator can be operated and their settings can be changed with Instrument-specific system exclusive
messages and channel messages. This function consists of 32 parts, but channel messages can control only Group B.
The following table shows the fixed relationships between the part numbers and channel numbers of channel messages.
All MIDI message send and receive is temporarily disabled while any one of the following processes is in progress.
•Demo data performance in progress
•Music Library data performance in progress
•SD memory card format in progress
3Timbre Type Specific Operation
The operation that is 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 part. Applicable information is provided in the
explanations for each message.
7
Part II
Channel Message
4Receive Channel
The channel number of the channel message received by each part is shown in the table under "1.4.2 Part Block".
The channel number of a channel message that changes the settings of a DSP coincides with the channel of the part that
is using the DSP.
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: 9nH kkH 00H (receive only)
8nH kkH **H
n: MIDI Channel Number
kk:
Key Number
**:
Ignored
Send
Sent when something is played on the keyboard.
Receive
Received over MIDI channels that correspond to each part. A part that is turned off by the Part Enable Parameter value
explained under "21.7 Part Parameter" is not received. The velocity value is ignored.
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.
Receive
Received over MIDI channels that correspond to each part. A part that is turned off by the Part Enable Parameter value
explained under "21.7 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 Operation
This message is not sent by this Instrument.
Receive Operation
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 Instrument mode or the corresponding parameter.
9.1Bank Select (00H)
Format
Message Format: BnH 00H vvH (MSB)
BnH 20H **H (LSB)
n: MIDI Channel Number
vv:
Value
**:
Ignored
Send
Sent when a tone is selected. See the Tone List in the Instrument's User's Guide for details.
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" in this document, and the Tone List in the Instrument's User's Guide.
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 vvH (MSB)
BnH 26H vvH (LSB)
n: MIDI Channel Number
vv: Value
Send
This message is not sent by this Instrument.
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 metronome volume or layer balance is adjusted.
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 "28.5 Pan Setting Value Table"
in "Part VIII Setting Values and Send/Receive Values".
Send
This message is sent at initialization.
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 there is a change in the Expression value by an accompaniment function.
Receive
Receipt changes the Expression value.
9.7General Use Controllers 1 through 8 (10H through 13H, 50H through 53H)
Receipt change the value of Parameter7 [0-7] (7-Bit Parameter) explained under "22.3 DSP Parameter".
Any message received that corresponds to the parameter of a number not being used by the currently selected DSP is ignored.
11
Note 1: Received values and parameter setting values
The range of the value of each DSP Parameter 7 array element depends on the selected DSP or array number.
Unlike manipulation of a DSP parameter using a System Exclusive Message, a value rec eiv ed by this co ntrol ch ange me ssa ge
is always a value from 0 to 127, but the value is changed in accordance with the setting range of the applicable parameter
setting. Because of this, it is impossible for a value to be outside of the range of the applicable parameter setting.
Conversion from the value received with the message to the parameter setting value is performed can be represented in
general terms by the expression shown below.
Parameter
For details about Parameter 7 of each DSP, see the explanations under "VII DSP Parameter List".
Setting V alue =
Parameter
Minimum V alue + (
Parameter
Maximum V alue -
Parameter
Minimum V alue)
Received Value
×
127
9.8Hold1 (40H)
Format
Message Format: BnH 40H vvH
n: MIDI Channel Number
vv: Value
Send
Sent when a pedal that has a sustain (damper) function is operated.
Receive
Receipt performs an operation equivalent to a sustain (damper) pedal operation.
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. For information about
the relationship between setting values and send/receive values, see the "28.1 Off/On Setting Value Table" in "Part
VIII Setting Values and Send/Receive Values" of this document.
•Timbre Type: Piano
Continuous control of the piano tone decay rate and the decay rate of Acoustic Resonance effect resonance is
performed in accordance with the value of the received message.
•Timbre Type: Drum
The received message does not affect sound source operation.
Acoustic Resonance
When a part that is using Acoustic Resonance receives this message, the resonance characteristics of Acoustic Resonance
are continually altered in accordance with the message value.
9.9Sostenuto (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 "28.1 Off/On Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values" of this document.
12
Send
Sent when a pedal that has a sostenuto function is operated.
Receive
Receipt performs an operation equivalent to a sostenuto pedal operation.
9.10Soft (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 "28.1 Off/On Setting Value
Table" in "Part VIII 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.11Vibrato Rate (4CH)
Format
Message Format: BnH 4CH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.4 -64 - 0 - 63 Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values" of this document.
Send
This message is not sent by this Instrument.
Receive
Receipt changes the vibrato rate of the tone that is currently selected by the applicable part.
9.12Vibrato Depth (4DH)
Format
Message Format: BnH 4DH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.4 -64 - 0 - 63 Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values" of this document.
13
Send
This message is not sent by this Instrument.
Receive
Receipt changes the vibrato auto depth of the tone that is currently selected by the applicable part.
9.13Vibrato Delay (4EH)
Format
Message Format: BnH 4EH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.4 -64 - 0 - 63 Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values" of this document.
Send
This message is not sent by this Instrument.
Receive
Receipt changes the vibrato auto delay of the tone that is currently selected by the applicable part.
9.14Reverb Send (5BH)
Format
Message Format: BnH 5BH vvH
n: MIDI Channel Number
vv: Value (Note1)
Note 1:
The setting value matches the value that is sent and received.
Send
Sent when a GM tone is selected.
Receive
Changes Reverb Send.
9.15Chorus 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.
14
Send
This message is sent at initialization, when the panel tone selection is changed, and when a chorus on/off operation is
performed.
Receive
Changes Chorus Send.
9.16NRPN (62H,63H)
Format
Message Format: BnH 62H vvH (LSB)
BnH 63H vvH (MSB)
n: MIDI Channel Number
vv: Value
Send
This message is not sent by this Instrument.
Receive
This Instrument does not have a corresponding NRPN message.
The setting value matches the value that is sent and received.
Send
This message is never sent.
Receive
Receipt changes the vibrato modulation depth of the tone that is currently selected by the applicable part.
9.17.5Null
Format
Message Format: BnH 64H 7FH 65H 7F
n: MIDI Channel Number
16
Send
This message is never sent.
Receive
Receipt deselects RPN.
9.18All Sound Off (78H)
Format
Message Format: BnH 78H 00H
n: MIDI Channel Number
Send
Sent when an SD memory card is inserted or removed, or when a memory card operation is performed.
Receive
Receipt stops all voices that are sounding.
9.19Reset All Controllers (79H)
Format
Message Format: BnH 79H 00H
n: MIDI Channel Number
Send
This message is sent when the keyboard channel is changed and when the recorder function is used.
Receive
Receipt initializes each performance controller.
10Mode Message
10.1All Notes Off (7BH)
Format
Message Format: BnH 7BH 00H
n: MIDI Channel Number
Send
This message is sent when a Music Library or recorder operation is performed.
Receive
Receipt of any of this message releases the currently sounding voice (same as releasing the keyboard key).
17
10.2Omni Off (7CH)
Format
Message Format: BnH 7CH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of any of this message releases the currently sounding voice (same as releasing the keyboard key).
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 releases the currently sounding voice (same as releasing the keyboard key).
10.4Mono (7EH)
Format
Message Format: BnH 7EH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message stops the currently sounding voice.
10.5Poly (7FH)
Format
Message Format: BnH 7FH 00H
n: MIDI Channel Number
Send
This message is never sent.
Receive
Receipt of this message stops the currently sounding voice.
18
11Program Change
Format
Message Format: CnH ppH
n: MIDI Channel Number
pp: Program Number
Send
Sent when a tone is selected. See the "Tone List" of the Instrument's User's Guide for details about program numbers.
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. See the Tone List in the Instrument's User's Guide for information about actually selecting tones, etc.
Also note that receipt of this message may also change the Timbre Type parameter at the same time. For more information,
see "11.1 About the Timbre Type" below.
11.1About the Timbre Type
The tone selected by each part of this Instrument has a "Timbre Type" parameter that specifies the type of sound source
for the tone. As explained under "22.1 Basic Parameters", there are three Timbre Type settings: Melody, Piano, and Drum.
The following explains how each of these operates.
•Timbre Type: Melody
This timbre type optimizes for normal melody tones. It performs damper pedal on/off operation.
•Timbre Type: Piano
This setting optimizes for piano tones. The decay rate of the voice being sounded and Acoustic Resonance effect
characteristics are continually altered in accordance with the damper pedal position.
•Timbre Type: Drum
This setting optimizes for drum sounds. The damper pedal does not function.
11.2DSP Assignments During Tone Selection
11.2.1DSP Line Structure
Though the Instrument has four DSP lines that can be used simultaneously, selecting a tone that uses DSP causes the required
number of DSP lines to become reserved so the tone is configured with the requisite DSP.
Tones listed under "26.1 Monaural Tone DSP" use only one DSP line, while the tones under "26.2 Stereo Tone DSP" use
two DSP lines.
For information about tones that use DSP, see "25 Tone with DSP List".
11.2.2DSP Line Assignment
Selecting multiple tones with DSP at the same time creates the possibility that there will not be enough DSP lines. In this
case, the last selected tone with DS P is given priority. Some DSP line(s) already being used will be released so they can
be assigned to the last selected tone.
19
11.2.3Use of the Same DSP Line by Multiple Parts
When multiple parts that select tones that use DSP and all of the following settings are the same, the same DSP line is
assigned to all of the parts in order to maximize DSP line availability.
•Tone Number
•Part Volume
•Part Pan
•All DSP parameters
After the same DSP line is assigned to different parts as described here, Part Volume, Pan, Reverb Send, Chorus Send,
Acoustic Resonance Send, and all DSP parameter settings are common to all parts. Note that changing the settings on any
part will also affect all of the other parts that are sharing the DSP line. To assign the parts to a different DSP line, you
need to change one of the parameters listed above before selecting the tone.
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
These messages are never sent.
Receive
Receipt changes the pitch of the currently sounding note. The change depends on the pitch bend sensitivity configured
with RPN.
20
Part III
System Messages
14Active Sensing
Format
Message Format: FEH
Send
This message is never sent.
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.
15System 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.
15.1Universal Realtime System Exclusive Message
Format
Message Format: F0H 7FH....F7H
15.1.1Master Volume
Format
Message Format: F0H 7FH 7FH 04H 01H llH mmH F7H
ll: Value LSB (Note1)
mm: Value MSB (Note1)
Note 1:
The setting value matches the value that is sent and received.
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.
21
15.1.2Master Balance
Format
Message Format: F0H 7FH 7FH 04H 02H llH mmH F7H
ll: Value LSB (Note1)
mm: Value MSB (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.5 Pan Setting Value Table"
in "Part VIII Setting Values and Send/Receive Values".
Send
This message is never sent.
Receive
Receipt changes the Master Pan parameter. Note that the Master Pan parameter cannot be changed with an Instrument
operation.
15.1.3Master Fine Tuning
Format
Message Format: F0H 7FH 7FH 04H 03H llH mmH F7H
mm: Value MSB(Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.6 -100 - 0 - 99 Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values" of this document.
Send
This message is sent when the tuning setting is changed.
Receive
Receipt changes the Fine Tune parameter.
Acoustic Resonance Actions
Acoustic Resonance acoustic characteristics also alter Fine Tune of the strings that simulate resonance in accordance with
the Master Fine Tune value. Because of this, receipt of this message may cause the resonance interval to change temporarily.
15.1.4Master Coarse Tuning
Format
Message Format: F0H 7FH 7FH 04H 04H 00H mmH F7H
ll: Value LSB
mm: Value MSB
Send
Sent when Transpose is changed.
Receive
Receipt changes the Transpose parameter.
22
15.1.5Reverb Parameter
Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 01H ppH vvH F7H
pp: Parameter
vv: Value
Type Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 01H 00H vvH F7H
vv: Value (Note1)
Note 1:
For information about the relationship between setting values and send/receive values, see "28.7 Reverb Type Setting Value
Table" in "Part VIII Setting Values and Send/Receive Values".
Send
This message is sent when the System Reverb Type setting is changed.
Receive
Receipt changes the Reverb Type parameter.
Time Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 01H 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 Reverb Time parameter.
15.1.6Chorus 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)
23
Note 1:
For information about the relationship between setting values and send/receive values, see "28.8 Chorus Type Setting Value
Table" in "Part VIII 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.
Depth Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H 02H 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 Depth parameter.
Feedback Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H 03H vvH F7H
vv: Value (Note1)
Note 1:
The setting value is the same as the value that is sent.
Send
This message is never sent.
Receive
Receipt changes the System Chorus Feedback parameter.
24
Send To Reverb Format
Message Format: F0H 7FH 7FH 04H 05H 01H 01H 01H
01H 02H 04H vvH F7H
vv: Value (Note1)
Note 1:
The setting value is the same as the value that is sent.
Send
This message is never sent.
Receive
Receipt changes the Chorus Send To Reverb parameter.
15.1.7GM 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 returns the Instrument's sound source to its power on default settings.
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.
15.2Instrument-Specific System Exclusive Message
Format
Message Format: F0H 44H 12H 01H....F7H
Most Instrument parameters and user data, and some operation commands can be controlled using this message.
For more information, see "Part IV Instrument-Specific System Exclusive Messages".
26
Part IV
Instrument-Specific System Exclusive Messages
16Format
16.1Message Classifications
The SysEx operation of this Instrument is basically a parameter data transfer operation. The following operations can be
performed from an external device using this parameter transfer message.
•Change of a specific Instrument parameter value
•Batch change of multiple Instrument parameter values
•Import of a specific Instrument parameter value
•Batch import of multiple Instrument parameter values
Parameters can be used for more than just device setting values. There are parameters when writing data that operate as
commands, and parameters when reading data that indicate the status of the Instrument. The following table shows the
parameter category for each type of transfer.
Function Section Parameter Category Description
SystemSystemCommands, Instrument status
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.
27
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.
The Model ID of the series to which the Instrument belongs is shown by two consecutive bytes (MSB, LSB).
(PX-200/PX-800/AP-500/PX-120/PX-720/PX-320 Model ID MSB = 15H, LSB = 01H)
16.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. The default value for this field is 10H. When a message containing
7FH is received, receipt of the message is always allowed, regardless of the Instrument's ID setting.
MIDI Device ID is a Patch Parameter, and it can be changed with a System Exclusive Message. In this case, the Device
ID of the MIDI System Exclusive Message must be set to 7FH before it is sent.
28
16.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 recei ves this action, it rewrit es the value speci fied
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.
Though OBR is defined as a series common format, one-way mode transfer is not supported by this Instrument.
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. The packets are transferred at fixed intervals.
Though OBS is defined as a series common format, one-way mode transfer is not supported by this Instrument.
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.
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 prescr ibed size. The packets are transferred in a ccordance 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.
29
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.
16.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--
01HSetupA-A
02HPatchA-A
03HToneA-A
21HMusic LibraryF-A
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
30
16.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.
MemType
0User area (rewriting allowed)
1Preset area (rewriting not allowed)
16.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.
16.3.9blk : Block Number
This supplementary number specifies which block is the object when there are multiple blocks within the same parameter set.
Format: 0iiiiiiiB (LSB)0jjjjjjjB0kkkkkkkB (MSB)
In the cases when there are multiple parameters in a category with the same ID (such as the mixer channel volume setting),
for example, the block number required in order to specify the block where the data belongs is indicated as
kkkkkkkjjjjjjjiiiiiiiB (Binary).
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.
Block Bit Field Division
•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.
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 sh own above, the block bit fields are allocated as: Block = 0000000 000aab bbbbbbb (Binary).
31
16.3.10pkt : Packet Number
Format: 0iiiiiiiB (LSB)0jjjjjjjB0kkkkkkkB (MSB)
This is the divided packet number kkkkkkkjjjjjjjiiiiiiiB (Binary) for transferring a single parameter set.
16.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.
16.3.12idx : Data Index Number
Format: 0iiiiiiiB
The data index number indicates the first array number of the array from which transfer starts.
16.3.13len : Data Length
Format: 0lllllllB
Data length indicates the transfer array length minus 1 for individual parameter transfer when the parameter contains a
character string or other similar array structure.
In the case of bulk parameter set transfer, data length indicates the number of data words (16-bit data) included within a
packet minus 1.
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.
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.
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.
The img length is the img length indicated by len multiplied by 3. This means that the data length is always a multiple
of 3. 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/2 × 3 = 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.
16.3.16sum : 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.
33
16.3.17EOX : End of System Exclusive Message
Format: 11110111B
(End of System Exclusive message Status = F7H)
17Individual 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 receive d an IPS, the value of the applicable parameter is changed.
An Individual Parameter Send can also be used to issue some command to the Instrument, and the Individual Parameter
Request can be used to check Instrument status information.
Data ReceiverData SenderOperation
IPR →Send Request (Optional)
← IPSData Transfer
See "Part V Parameter List" for information about how parameters can actually be sent.
18Parameter Set Transfer Modes
18.1Communication Modes
18.1.1One-way and Handshake
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.
Important!
Though the one-way mode format is defined, there is no Parameter Set category that corresponds to this Model. This is
because the time required to write to flash memory is indefinite, which makes it necessary to maintain a very long interval
between packets and makes communication impossible for all practical purposes.
See "VI Parameter Set List" for information about how Parameter Sets are actually allocated. 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.
34
18.1.2Session and Subsession
Subsession
One Parameter Set can be transferred per subsession. Subsession transfers one Parameter Set or data that is broken down
into multiple packets for transfer, with EOD (End of Data) sent at the end to terminate the send.
Data is divided into multiple packets when a single Parameter Set is larger than a certain size . The Packet Number in the
packet's index field is used to indicate the sequential position of a packet relative to the other packets. Even if Parameter
Sets are small, they cannot be grouped together and sent as a single packet. A Parameter Set delimiter is always treated
as a packet delimiter for transfer.
Session
One Parameter Set or multiple Parameter Sets can be transferred by one session. A session can consist of one subsession
or multiple subsessions, with EOS (End of Session) sent at the end to terminate the send.
Regardless of whether there is a single Parameter Se t or multiple Parameter sets, an actual bulk dump always takes the
form of a session, never a subsession only.
18.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.
Data is divided into multiple packets of 256 bytes or less each, and transfers them 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
35
18.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 (at least 2000 msec) is treated
as a timeout error, and data communication is termin ated.
The sending device resends the last data if the receiving device returns an ERR (error) due to checksum mismatch,
incompatible data structure, or some other reason. If an error repeats a number of times (undefined), either the sending
device or the receiving device sends an RJC to terminate the ses sion.
A session ends after the sending device sends all the parameter sets, and sends a final EOD in response to an ACK (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
The same packet is resent when a checksum mismat ch or incompatible data structure error is detected.
Data ReceiverData SenderOperation
HBR→Send Request (Optional)
←HBSData Send
ACK→Acknowledge
←HBSData Send
ERR→Error
←HBSData Resend
:
:
ERR→Error
←EODEnd of Data
:
Other subsessions
:
←EOSEnd of Session
36
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 ←Rejection
(Send Canceled)
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
:
:
RJC →Data Receive Rejected
(Send Canceled)
Data ReceiverData SenderOperation
HBR →Send Request (Optional)
ACK →Acknowledge
← HBSData Send
ACK →Acknowledge
← HBSData Send
:
:
← RJCData Receive Rejected
(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
← BSYBusy
(Send Canceled)
37
Data ReceiverData SenderOperation
OBS →Data Send
← BSYBusy
(Send Canceled)
Data ReceiverData SenderOperation
HBR →Send Request
← BSYBusy
(Send Canceled)
Data ReceiverData SenderOperation
HBS →Data Send
← BSYBusy
(Send Canceled)
See "Part VI Parameter Set List" for information about how parameter sets can actually be transferred.
38
Part V
Parameter List
How to Read the Tables
Number Base Notation
"Size" indicates the parameter value bit width as a decimal value.
The bit field position of "Block" as a decimal value.
Values used in the explanations under "Description" are all decimal values, unless specified otherwise.
Values other than those described above are all hexadecimal.
R/W Field
The R/W field indicates whether an IPR (Individual Parameter Request) read operation or IPS (Individual Parameter Send)
write operation is enabled.
19System 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.
19.1System Information Parameter
This parameter is a container for system information.
ParameterIDR/WBlockSize Array Min-Def-Max Description
Model
Version
Internal Timestamp
External Timestamp
0000
0001
0002
0003
R
R
R/W
R/W
000000
000000
000000
000000
7
01
7
01
7
10
7
10
00-00-7F
00-00-7F
00-20-7F
00-20-7F
0...reserved
1...PX-200
2...PX-800
3...AP-500
4...PX-120
5...PX-720
6...PX-320
Version Number
Ascii Character
Ascii Character
19.2Data Management Parameter
This is a message command computer-based data management software.
Selects the System Chorus preset type. Receipt of GM/GS Reset selects Chorus3.
The value of this type is also linked to System Chorus parameters, and to the Chorus Send to Reverb and System Chorus
Return Level parameters, and its setting causes these parameters to change to prescribed values.
For details about the preset type list, see "28.8 Chorus Type Setting Value Table".
Selects the System Reverb preset type. Receipt of GM/ GS Reset selects Hall2.
This type is also linked to System Reverb parameters, and to the System Reverb Return Level parameter, and its setting
causes these parameters to change to prescribed values.
For details about the preset type list, see "28.7 Reverb Type Setting Value Table".
Changing this parameter configures the Tuning setting of System Acoustic Resonance.
When the Instrument's Master Fine Tune setting is changed, this parameter is reset to the Master Fine Tune value.
Note 2:
Changing this parameter performs a Damper Pedal operation on System Acoustic Resonance.
When the Damper Pedal parameter of the part being used by System Acoustic Resonance is manipulated, this parameter
is reset to the manipulated Damper Pedal depth.
Note 3:
The value is set when the damper pedal is completely released.
Note 4:
The value is set when the damper pedal is completely depressed.
21.6Brilliance Parameter
ParameterIDR/WBlockSize ArrayMin-Def-MaxDescription
Type
Mid6 Gain
Note 1:
Selects Master EQ mid 6 (Brilliance) gain. See "28.11 Brilliance Gain Setting Value Table".
0047
0055
R/W
R/W
000000
00000077
01
01
00-00-01
00-0C-18
0...For Speaker
1...For Phones
-12 - 0 - +12(Brilliance)(Note1)
41
21.7Part Parameter
ParameterIDR/WBlockSize ArrayMin-Def-MaxDescription
Part Enable
Tone Num
Fine Tune
Coarse Tune
Volume
Acmp Volume
Pan
Cho Send
Rev Send
Acou Reso Send
Bend Range
ParameterIDR/WBlockSize ArrayMin-Def-MaxDescription
Name
Timbre Type
Timbre Num
Oct Shift
Line Select
Level
Touch Sens
Sys Fx Send Override
Cho Send
Rev Send
Acou Reso Send
0000
0001
0002
0003
0004
0005
0006
0007
0008
0009
000A
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
7
4
14
3
1
7
7
1
7
7
7
10
01
0000-0000-3FFF
01
01
01
01
01
01
01
01
01
00-20-7F
00-00-0F
02-04-06
00-00-01
00-7F-7F
00-7F-7F
00-00-01
00-00-7F
00-28-7F
00-00-7F
Ascii Character
0...Melody
1...Piano
2...Drum
0 - 16383
-2 - 0 - +2
0...Direct
1...DSP
0 - 127
-64 - 0 - +63
0...No (Note1)
1...Yes
0 - 127
0 - 127
0 - 127
Note 1:
When a tone is selected whose Sys Fx Send Override parameter setting is "Yes", the send level setting value to the System
Chorus, System Reverb, and System Acoustic Resonance of the part assigned to this tone is rewritten to the value that is
stored by this tone.
Vib Rate
Vib Auto Delay
Vib Auto Rise
Vib Auto Depth
Vib Mod Depth
Vib After Depth
Lfo Wave
Lfo Rate
Lfo Fil Auto Delay
Lfo Fil Auto Rise
Lfo Fil Auto Depth
Lfo Fil Mod Depth
Lfo Fil After Depth
Lfo Amp Auto Delay
Lfo Amp Auto Rise
Lfo Amp Auto Depth
Lfo Amp Mod Depth
Lfo Amp After Depth
The function of this parameter is to relatively change the original setting value of the tone. The parameter is set to the
maximum value when the maximum is exceeded, and to the minimum when the minimum is exceeded.
22.3DSP Parameter
ParameterIDR/WBlockSize ArrayMin-Def-MaxDescription
Name
Algorithm
Cho Send
Rev Send
Acou Reso Send
Parameter7
Parameter16
Note 1:
This value is the DSP algorithm ID, which cannot be changed directly at the user level. Changing the DSP Type or Tone
Number causes the algorithm ID of the original DSP to be copied automatically to this area. See "26 DSP Algorithm ID
Table".
002C
002D
002E
002F
0030
0032
0033
R/W
R/W
R/W
R/W
R/W
R/W
R/W
000000
000000
000000
000000
000000
000000
000000
14
16
10
7
01
01
7
01
7
01
7
7
20
10
00-20-7F
0000-0000-3FFF
00-00-7F
00-28-7F
00-00-7F
00-40-7F
0000-8000-FFFF
43
Ascii Character
Serial Number
(Note1)
0 - 127
0 - 127
0 - 127
0 - 127
0x0000 - 0xFFFF
23Music Library Parameter
This parameter is a container for Music Library related information.
ParameterIDR/WBlockSize ArrayMin-Def-MaxDescription
Name
Address
Size
0000
0001
0002
R
R
R
000000
000000
000000
7
32
32
0C
00000000-00000000-00FFFFFF
01
00000000-00000000-00FFFFFF
01
20-20-7F
Ascii Character
0 - 0xFFFFFFFF
0 - 0xFFFFFFFF
44
Part VI
Parameter Set List
This list shows the parameter sets that can be transferred using System Exclusive Message Bulk Dump.
24Music Library Parameter Set
System Exclusive Format
FieldValue
01SYSEXF0
02MAN44
03MOD15, 01
04dev00 - 7F
05act04(HDS), 05(HDR), 07(Control)
06catMusic Library = 21
07mem0 = User
08psetMusic Library Number to be transferred
09pktSee "IV Instrument-Specific System Exclusive Messages".
10lenSee "IV Instrument-Specific System Exclusive Messages".
11imgSee "IV Instrument-Specific System Exclusive Messages".
12sumSee "IV Instrument-Specific System Exclusive Messages".
13EOXF7
45
Part VII
DSP Parameter List
25Tone with DSP List
This is a list of tones that use DSP.
Tone NumberTone NameMono/StereoDSP Algorithm
01Panel GRAND PIANO MODERNStereoWide 3Band EQ
02Panel GRAND PIANO CLASSICStereoWide 3Band EQ
04Panel ROCK PIANOStereoWide 3Band EQ
07Panel 60’S E.PIANOMonoTremolo
08Panel ROCK ORGANStereoDrive Rotary
Note: The gain value does not exactly correspond to
decibels (dB).
52
Part IX
MIDI Implementation
Notation
29Value Notation
29.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 the decimal values 0 through
127, which are often used for settings.
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.