Votes - , Average rating:
(
)
)
Manafacture: Casio
File size: 2.36 mb
File name:
Language of manual:
The document is loading, please wait
 |
The document is loading, please wait
Other manuals for this model:
manual abstract
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. act SX MAN MOD dev act body (Depends on act.) EOX cat mem pset blk pkt prm idx len data IPR Y Y Y Y Y Y Y Y Y Y Y Y Y -Y IPS Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 28 16.3 Field Formats 16.3.1 SX : System Exclusive Message Status Format: 11110000B (F0H) This is the System Exclusive Message status byte established by the MIDI standard. 16.3.2 MAN : Manufacturer’s ID Format: 01000100B (CASIO = 44H) Indicates this Instrument’s manufacturer ID. 16.3.3 MOD : Model ID Format: MSB 00010101B (15H) LSB 00000010B (02H) These two successive bytes (MSB, LSB) indicate the PX-130, 330, 730, 830, and AP-220, 420, 620 model ID. 16.3.4 dev : MIDI DeviceID 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. 16.3.5 act : Action Format: 0aaaaaaaB This field indicates the operation of the Instrument-specific System Exclusive Message. aaaaaaaB Action Function 00H IPR Individual Parameter Request 01H IPS Individual Parameter Send 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. 29 16.3.6 cat : 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. Category Transfer ID (c) Parameter Set Individual Parameter 00H System A 01H Setup A 02H Patch A 03H Tone A 21H Music Library F A .. Available (Also including when only some parameters are available.) F... File Information (Not the data itself. Name, size, and other file information only.) 16.3.7 mem : Memory Area ID Format: 0mmmmmmmB Specifies the memory area that is the object of the parameter transfer. The following are defined for this Instrument. Basically, Instrument-specific System Exclusive messages are valid for user area data only. mem Data Type Meaning 0 User area Read/write enabled 1 Preset area Read/write disabled 16.3.8 pset : Parameter Set Number Format: LSB 0nnnnnnnB MSB 0mmmmmmmB This field is a 2-byte (LSB, MSB) value indicating the number of the parameter set (mmmmmmmnnnnnnnB, binary) being transferred. 16.3.9 blk : Block Number This supplementary number specifies which block is the object when there are multiple blocks within the same parameter set. Format: 0iiiiiiiB (LSB) 0jjjjjjjB 0kkkkkkkB (MSB) When there are multiple parameters with the same ID inside the same category, as with the mixer channel volume setting for example, the block number required to specify to which block data belongs is specified 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. 30 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 with 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] With an A=3 (2bit), B=200 (8bit) 2-dimensional array parameter, the block bit fields are allocated as: Block = 0000000 000aab bbbbbbb (Binary). 16.3.10 prm : Par...