Roland Exclusive Messages - Roland GR-33 Owner's Manual

Hide thumbs Also See for GR-33:
Table of Contents

Advertisement

Roland Exclusive Messages
1. Data Format for Exclusive Messages
Rol,md's MIDI implementation uses the follmving data format for aJl
Exdusivt> mPssagt>s (type> IV):
By1e
Oescnpbon
FOH
Exclusive Status
41H
Manufacturer ID ( Roland)
DEV
Device 10
MOL
Model ID
CMD
Command ID
(BODY]
Main data
F7H
End ol exdusive
• MIDI status: FOH, F7H
An E\dusi\'t' rnPssagE' must he flanked hy a pair of status codes, starting
wilh
a
Manufacturer ID immediately after FOH (MJDI version 1.0).
• Manufacturer ID: 41 H
The Manufacturer ID idt•ntifies the manufacturer of a MIDI instrumt>nt that
semb an Exdu~ive mcss.1~e. V,1Juc 41H represents Roland's Manufocturer ID.
• Device ID: DEV
The Uevice IlJ cnntains a unique \·alue that identifies individual devices in
the implementation of se\'eral MIDI instruments. It b usually set lo
OOH-OFH,
a
value smaller bv one than that of a basic channel, but value
OOH-I FH may be used for a d~vice with sevt1r.1l basic channels
•Model ID: MDL
The Model ID contains a value that identifit>s one model from another.
Different
mL1dcls, ho\W\'Cf, m.1y
sh.ue
an
idenlkal MCR.iel ID ii they handle
similar data.
The Model ID format may contain OOH in nnc or more places to provide an
cxtendt.,"l.i data field. The fo!Jowin,g are examples of valid Modt.>l IDs, e,1ch
representing a unique model·
01H
02H
03H
OOH, OIH
mlH,02H
lXlH, OOH, 01 H
•Command ID: CMD
The Command JD indicates thP function of an Exclusive mCJsf..-1ge. The
Command JD format may contain OOH in one or more places to provide an
extended data field. The following are examples of valid Command IDs,
cnch representing
i.1
unique function:
OlH
02H
03H
OOH, OlH
OOH,
02H
001!, 0011, OJI I
• Main data: BODY
This field contains
a
messa~e to be exchanged across ,in interface Thf" pxact
data size ;md rontPnt will \'ory with tlw Mot.it"! ID ,ind Command ID.
2. Address-mapped Data Transfer
Address mapping is a tt.>chniquc for tr,m!>ferrin,g
rne.Sdgcs
conforming lo lhe
dnta format given in Section
1.
It
,1ssigns a series of memory-resident
rl'cords-waveforrn and tone data, switch
st.ih1s,
and par..imef'ers, for
example, lo specific locations in n machine-depl'ndent address space, thereby
,1llowing access to dat.:i residing at the addre5s a messi"lge spedties.
A,ddress-mapped d.itc1 transfer h; therefore inJcpendenl of models and
tfat,1
categories. This technique allows use of two different tran.o:;fer procedures:
one-w.ty tran:,;for and handshilkc tr,msfcr.
Chapter 11 Appendices
•One-way transfer procedure (See Section 3
for details.)
This prncedure is suited to the transfer of a smi.lll amount of data.
It
sends out
an Exclusive message completely independent of the receiving de\"icc·s status.
Connection Diagram
Device A
MIDI OUT
MIDIIN
Device
B
MIDI IN
MIDI OUT
Connection at point
2
i:- essential for "Request data" procedures.
(See
St...-..:tion
3.)
• Handshake-transfer procedure (This device
does not use this procedure)
This procedure initiates a predetennined transfer se,1uence (handshaking)
acrnsfo> the interface before data transfer takes place. Handshaking ensures that
reliability and transfer speed are high enough to handle a large amount of data.
Connection Diagram
Device A
Device
B
MIDI
OUT
MIDIIN
MIOIIN
MIDI OUT
Connt:.>Ltion at point:,. 1 ,md 2 i~ cssl:'nlial.
Notes on the above procedures
~
TltL•rc arc ~l'pamtc Comm1111d
ffJs_ft,r d{(ft·mll
lranef,·r 11ron•,i11res.
• Dt..1
1
iccs
A a11d B
n111m1f
c.tt.'lumgc
data
unkss tlu•y
1/St.'
lire same transfer
prorc,iurc,
f;/iarl' iifentical Dtl'icc ID mid Mc>dd ID, mid
11rc
nwlyfor wmm1111irnli1111.
3. One-way Transfer Procedure
This procedure sends out data until it hm• all been sent and is used when the
messages are so short that answerbacks neet.i not be checked.
for longer messages, however, the recch•ing device must acquire each
message in time with the transfer sequence, tvhich inserts 20 milliseconds
intervals.
Types of Messages
Message
Command ID
Request data 1
AQt {11H)
Data set 1
DT1 (12H)
•Request data #1: RQl (11H)
TI1is me~sage is sent oul when there is a need to acquire data from
,1
device
.it
the other end of the interface. It contains data for the address and size that
specify designation and lt'>flgth, rt"spt><·tivt"I)', nf datc1 required.
On receiving an RQl messa~e. the remote device checks its memory for the
data address and size that satisfy the request.
If
it
finds them and is ready for communication. the de\"ice
will
transmit a
"Data set 1 (l)Tl)" message, which contains the requested data. Othcnvise,
the device won't send out anything.
By1e
Description
FOH
Exclusive
S1atus
41H
Manufacturer ID (Roland)
DEV
Device ID
MDL
Model ID
11H
Command ID
aaH
Address MSB
I
I
I
I
LSB
ssH
Size
MSB
I
I
I
I
LSB
sum
Check sum
F7H
End of exclusive
103
I

Advertisement

Table of Contents
loading

Table of Contents