Table of Contents
Advertisement
Roland Exclusive Messages
niDataFormatior
= One way transfer procedure (See Section 3 for details.)
Roland's MIDI implementation uses the following data format for all
exclusive messages (type ll.-'):
:
'
' ' r i;r ::T_t;:_ __ 77. 7 ——
'
..;_ ___ _ _ _ _:_____;__—;_7__:uuc.;fi :11.
_>
Byte
Description
_,____ W ~_~__
.
. ~
......
:;,.:,_:__ , ___<____,__,._
%_:;:_s.*
.
FOH
w Exclusive status
.
_ _ _ ; r _ ____;
'
diH
1: Manufacturer if) (Ftoiand)
U
1
DEV
1 1 Device ID
MDL
= Mode! lD
CMD
Command ID
1'
[BODY]
Main data
l
1 l
.1 MIDI status : FOH, F7H
An exclusive message must be flanked by a pair of status codes, starting
with a Manufacturer-ID immediately after FOH (MIDI versionl.O).
.1 Manufacturer-ID : 41H
The Manufacturer-ID identities the manufacturer of a Mini instrument
that triggers an exclusive message. Value 4lli represents Roiand's
Manufacturer~llJ.
.' - : Device~lD : DEV
The Device-ID contains a unique value that identifies the individual device
in the multiple implementation of MIDI instruments. it is usuaily set to
OOH - DFH. a value smaller by one than that of a basic channel. but
value OOH — ll"-'it may be used tor a device with multiple basic channels.
e Model-ID : MDL
The Model-ID contains a value that uniquely identities one tnodei from
another. Different models. however, may share an identical Mocleilfi if
they handle similar data.
The Model-H) format may contain can in one or more places to pmvidc
an extended data lit".-id. The lnilowing are examples of valid Model H35.
each representing a unique model:
Oltl
02H
()3!-I
OOH. 011-l
OOH. 02H
OOH, OOH. Olil
:..-Command.lD; CMD
The Command-ID indicates the function of an exclusive message. The
Command-ID format may contain OOH in one or more places to provide
an extended data field. The loiiowing are examples oi valid Command
IDs. each representing a unique function:
O i I-I
02H
U3]-I
This procedure I5 suited for the transfer oi a small amount of data.
it sends out an exclusive message completely independent of a receiving
device status.
Connection Diagram
Device (A)
Device (B)
l
Mini out
no lhl
MlDl IN
"5"" M151 OU1
Connecliort at point 1- . ' is essential For "itequesl tilaia" tJrot':ci'.lu|'t:s. (Sec
Section 3.)
rrn
End of eicciusive
=Har_idshak_e transfer procedure _
"-~"" "
r-~ -—
"Tr ~ r*""<~
{This device does not cover this procedure)
This procedure initiates a predetermined transfer sequence (handshakingfl
across the interface be-lore data transfer tal-tes place. llandshaking ensures
that reliability and transfer speed are high enough to handle a large
arnount of data.
Connection Diagram
Device (A)
Device (E3)
MlDl our
'
snot iN
MlDl in
2
mics our
Connection at points I and 2 is essential.
Notes on the above two procedures
=l =
There are separate Command-li.)s lor diilercnt transit-r procedures.
*
Devices A and li cannot exchange data unless they use the same
lranslcr procedure. share identical Device-ll.') and Model ll), and are
ready for cornniunication.
filransfer Procedure]
This procedure sends out data all the way until it stops and is used
when the messages an: so short that answcrbactts need not --he checked.
For lone messages. however. the receiving device must acquire each
message in time with the transfer sequence. which inserts intervais oi
at least 20 miiliscconds in between.
Typos of Messages
Request data l
R0! (ill-l]
Data set l
OT! (l2l-1)
i.i;......i.i i
} ca§i§}{{.Y=-la 15" f W
*
0914,0114
.-=Request data =1 ; R01 (HH)
OOH. 02H
OOH, OOH. Oil-I
.~=Main data: BODY
This field contains a message to be exchanged across an interface.
The exact data size and contents will vary with the Model-ID and
Command-It).
lAddre=»r~=m=@d Pm T'=~=ferl
Address mapping is a technique lor translerring messages conforming
to the data Iormat given in Section l. ll assigns a series of memory-
resident records-waveform and tone data. switch status, and parameters.
tor example-to specific locations in a machine-dependent address space.
thereby atiowing access to data
residing at the address a message
specifies.
Address-mapped data transfer is therefore independent of models and
data categories. This technique allows use of two different transfer
procedures: one-way transfer and handshake transfer.
This message is sent out when there is a need to acquire data from
a device at the other end of the interface. it contains data for the address
and size that specii)-'-designation and length. respectively. ol data required.
On receiving an RE)! message. the remote device checks its l'llL'lli{.!f}' lo!
the data address and size that satisly the request.
it it linds thcrn and is ready tor communication. the device will transmit
a "Data set 1
ti}'l'I)" message. which contains the requested data.
Otherwise. the device vviil send out nothing.
i
Byte
Deseriotion
, , , , 4 , , , . . . . . . n 4
FOH
Exclusive status
41H
Manufacturer ID (Fioiand)
DEV
Device iD
MDL
Model ID
HH
Commend ID
'
Address lvlSB
ca
. . . . . . in
I.
3
*
LSB
Size
M55
oi
... . .
so
I
_ h _ _ _ _ 4
~
LS8
'
sum
1
Check sum
»
FT}-l
End of exclusive
Hide quick links:
Advertisement
Table of Contents
