MIDI Implementation
9
z
Data Set 1 (DT1)
This is the message of actual data transmission. Use this when you want to set data
to the unit.
Status
Data Byte Status
F0H
41H, dev, 00H, 00H, 00H, 20H, 12H, aaH,
F7H
bbH, ccH, ddH, ..., eeH, sum
Byte
Explanation
F0H
Exclusive Status
41H
Manufacturer ID (Roland)
dev
Device ID (dev: 00H–1FH,10H is default)
00H
1st byte of model ID (V-1HD)
00H
2nd byte of model ID (V-1HD)
00H
3rd byte of model ID (V-1HD)
20H
4th byte of model ID (V-1HD)
12H
Command ID (RQ1)
aaH
Address upper byte
bbH
Address middle byte
ccH
Address lower byte
ddH
Data: actual data to transmit. Multiple byte data is sent in address order.
:
:
eeH Data
sum Checksum
F7H
EOX (end of exclusive)
* Depending on the data type, the amount of single-time transmission is specified.
It is necessary to execute data request according to the specified first address and
size. Refer to the “3. Parameter Address Map” (p. 12) for address and size.
* See “Example of an Exclusive Message and Calculating a Checksum” (p. 20) for
checksum.
* Data exceeding 256 bytes should be divided into packets of 256 bytes or smaller. If
you send data set 1 successively, set interval of 20 ms or longer between packets.
z
MIDI Visual Control Message
Status
Data Byte Status
F0H
7EH, dev, 0CH, 01H,
F7H
aaH, bbH, ccH, ddH, ...,eeH, sum
Byte
Explanation
F0H
System Exclusive Status
7EH
Universal System Exclusive Non-Realtime Header
dev
Device ID (dev : F00H–1FH; MVC default= 00H)
0CH
Sub ID #1 (MIDI Visual Control)
01H
Sub ID #2 (MVC command set ID; 01H= “Version 1.0”)
aaH
Upper byte of the address
bbH Address
ccH Address
ddH
Actual Data: The data body. The data of multiple bytes should
be submitted in address order.
:
:
eeH Data
sum Checksum
F7H
EOX (End of Exclusive)
* Depending on the data type, the amount of single-time transmission is specified.
It is necessary to execute data request according to the specified first address and
size. Refer to the “3-2. MIDI Visual Control” (p. 18) for address and size.
* See “Example of an Exclusive Message and Calculating a Checksum” (p. 20) for
checksum.
* Data exceeding 256 bytes should be divided into packets smaller than 256 bytes. If
you send sequentially, the intervals of packets should be longer than 20 ms.
z
V-LINK Message
Status
Data Byte Status
F0H
41H, dev, 00H, 51H, 12H,
F7H
aaH, bbH, ccH, ddH, ...,eeH, sum
Byte
Explanation
F0H
System Exclusive Status
41H
ID Number (Roland)
dev
Device ID (dev : 00H–1FH ; default is 10H)
00H
Model ID upper byte (V-LINK)
51H
Model ID lower byte (V-LINK)
12H
Command ID (DT1)
aaH
Upper byte of the address
bbH Address
ccH Address
ddH
Actual Data : The data body. The data of multiple bytes should
:
:
eeH Data
sum Checksum
F7H
EOX (End of Exclusive)
* Depending on the data type, the amount of single-time transmission is specified.
It is necessary to execute data request according to the specified first address and
size. Refer to “3.3 V-LINK” (p. 19) for the address and data.
* See “Example of an Exclusive Message and Calculating a Checksum” (p. 20) for
checksum.
* Data exceeding 256 bytes should be divided into packets smaller than 256 bytes. If
you send sequentially, the intervals of packets should be longer than 20 ms.