Roland FC-300 用户手册
59
MIDI FOOT CONTROLLER
Model FC-300
Apr. 1, 2007
Version 1.00
MIDI Implementation
Roland’s MIDI implementation uses the following data format for all
Exclusive messages (type IV):
Exclusive messages (type IV):
MIDI status: F0H, F7H
An Exclusive message must be flanked by a pair of status codes,
starting with a Manufacturer ID immediately after F0H (MIDI version
1.0).
starting with a Manufacturer ID immediately after F0H (MIDI version
1.0).
Manufacturer ID: 41H
The Manufacturer ID identifies the manufacturer of a MIDI
instrument that sends an System Exclusive message. Value 41H
represents Roland’s Manufacturer ID.
instrument that sends an System Exclusive message. Value 41H
represents Roland’s Manufacturer ID.
Device ID: DEV
The Device ID contains a unique value that identifies individual
devices in the implementation of several MIDI instruments.
devices in the implementation of several MIDI instruments.
It is usually set to 00H–0FH, a value smaller by one than that of a basic
channel, but value 00H–1FH may be used for a device with several
basic channels.
channel, but value 00H–1FH may be used for a device with several
basic channels.
Model ID: MDL
The Model ID contains a value that identifies one model from another.
Different models, however, may share an identical Model ID if they
handle similar data.
handle similar data.
The Model ID format may contain 00H in one or more places to
provide an extended data field.
provide an extended data field.
The following are examples of valid Model IDs, each representing a
unique model:
unique model:
01H
02H
03H
00H, 01H
00H, 02H
00H, 00H, 01H
Command ID: CMD
The Command ID indicates the function of an Exclusive message.
The Command ID format may contain 00H in one or more places to
provide an extended data field.
provide an extended data field.
The following are examples of valid Command IDs, each representing
a unique function:
a unique function:
01H
02H
03H
00H, 01H
00H, 02H
00H, 00H, 01H
Main data: BODY
This field contains a message to be exchanged across an interface.
The exact data size and content will vary with the Model ID and
Command ID.
Command ID.
Address mapping is a technique for transferring messages
conforming to the data format given in Section 1.
conforming to the data format given in Section 1.
It assigns a series of memory-resident records–waveform and tone
data, switch status, and parameters, for example, to specific locations
in a machine-dependent address space, thereby allowing access to
data residing at the address a message specifies.
data, switch status, and parameters, for example, to specific locations
in a machine-dependent address space, thereby allowing access to
data residing at the address a message specifies.
Address-mapped data transfer is therefore independent of models
and data categories.
and data categories.
This technique allows use of two different transfer procedures: one-
way transfer and handshake transfer.
way transfer and handshake transfer.
One-way transfer procedure
(See Section 3 for details.)
(See Section 3 for details.)
This procedure is suited to the transfer of a small amount of data.
It sends out an Exclusive message completely independent of the
receiving device’s status.
receiving device’s status.
fig.Connection-Diagram1.eps
Connection at point 2 is essential for “Request data” procedures. (See
Section 3.)
Section 3.)
Roland System Exclusive
Messages
Messages
1. Data Format for Exclusive
Messages
Messages
Byte
Description
F0H
System Exclusive Status
41H
Manufacturer ID (Roland)
DEV
Device ID
MDL
Model ID
CMD
Command ID
[BODY]
Main data
F7H
EOX (End of System Exclusive)
2. Address-mapped Data Transfer
Device (B)
MIDI IN
MIDI OUT
Device (A)
MIDI OUT
MIDI IN
1
2
FC-300_e1.book 59 ページ ２００７年４月２４日 火曜日 午前１０時１０分