User manual ROLAND SYSTEM-100-102

[. . . ] Divide the value of DATA section by that of SIZE section. Example: Set UTILITY GLOBAL BPM on 180BPM 1. Refer to Parameter Address Map to calculate UTILITY GLOBAL BPM Address. From ADDRESS BLOCK MAP, BASE ADDRESS of UTILITY BLOCK is 08 00 00H Next, from UTILITY AREA TABLE, OFFSET ADDRESS of GLOBAL BPM PARAMETER is ** 01 2CH And then, calculate the actual address. [. . . ] F0 41 00 00 23 12 08 01 2C (1) (2) (3) (4) (5) (6) ^^^^^^^^^^ (7) (1) Exclusive Status (2) Manufacture ID (Roland) (3) Device ID (DEV:00H - 1FH) (4) MODEL ID MSB (SYSTEM-100-102:00H) (5) MODEL ID LSB (SYSTEM-100-102:23H) (6) Common ID (DT1) (7) Address (8) Data (4bit nibbled, MSB first) (9) Checksum (10) End of Exclusive 4. (7) Address + (8) Data = 08H + 01H + 2CH + 00H + 00H + 0BH + 04H = 44H(sum) 8 + 1 + 44 + 0 + 0 + 11 + 4 = 68 68(sum) / 128 = 0(quotient). . . 68(remainder) checksum = 128 - 68(remainder) = 60 = 3CH 00 00 0B 04 ^^^^^^^^^^^^^^ (8) ???ADDRESS MAPPING OF PARAMETER The address and size are displayed under 7-bit hexadecimal notation. Address 0aaa aaaa AA Size 0sss ssss SS MSB 0bbb bbbb BB MSB 0ttt tttt TT LSB 0ccc cccc CC LSB 0uuu uuuu UU Binary 7-bit Hexadecimal Binary 7-bit Hexadecimal s Parameter base address The actual address of each parameter is the start address of the block plus the offset address. Address Block Map Base Address Block Sub Block Note 00 00 00 +-------------------+ +-----------------+ | User Patch | | USER PATCH A001 |····Bulk | | +-----------------+ 00 04 00 | | +-----------------+ | | | USER PATCH A002 | | | +-----------------+ : | | : : | | : 03 10 00 | | +-----------------+ | | | USER PATCH A101 | | | +-----------------+ 04 00 00 | | +-----------------+ | | | USER PATCH B001 | | | +-----------------+ : | | : : | | : 07 10 00 | | +-----------------+ | | | USER PATCH B101 | +-------------------+ +-----------------+ 08 00 00 +---------------------------------------+ | UTILITY |····Individual +---------------------------------------+ 10 00 00 +---------------------------------------+ | TEMPORARY AREA |····Bulk +---------------------------------------+ 20 00 00 +---------------------------------------+ | INDIVIDUAL TEMPORARY AREA |····Individual(Write Only) +---------------------------------------+ 60 00 00 +---------------------------------------+ | SOUND CHANGE REQUEST (SCR) |····Individual +---------------------------------------+ 70 00 00 +---------------------------------------+ | PATCH WRITE REQUEST (PWR) |····Bulk +---------------------------------------+ * * The SYSTEM-100-102 can use two methods of communication; Individual Parameter and Bulk Dump. Bulk data can be received when the Bulk Load Ready function is accessed in Utility mode. Although individual data can be received at any time, be sure to appropriately describe the value for one parameter in one packet [F0. . . F7]. When a data request is to be received, use Bulk Load Ready in the utility. Parameters for which Size is 2 or higher should not be separated; make sure these are sent in the same packet. A Sound Change Request (SCR) is valid only for the Temporary Area (Bulk). To Change data in the Temporary Area(Bulk) using Exclusive(SysEx) messages, it is necessary to first send the parameter data, then send the data to the SCR address. (refer to Table37. [SCR]) Patch Write Request (PWR) is valid for User Patch and UTILITY MIDI PC MAP. If the unit recognize this message, the data of User Patch and UTILITY MIDI PC MAP are memorized. The Model ID format may contain 00H in one or more places to provide an extended data field. The following are examples of valid Model IDs, each representing a unique model: 01H 02H 03H 00H, 01H 00H, 02H 00H, 00H, 01H 3. One-way Transfer Procedure This procedure sends out data until it has all been sent and is used when the messages are so short that answerbacks need not be checked. For longer messages, however, the receiving device must acquire each message in time with the transfer sequence, which inserts 20 milliseconds intervals. Types of Messages Message Request data 1 Data set 1 Command ID RQ1 (11H) DT1 (12H) ·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. The following are examples of valid Command IDs, each representing a unique function: 01H 02H 03H 00H, 01H 00H, 02H 00H, 00H, 01H ·Request data #1: RQ1 (11H) 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 specify designation and length, respectively, of data required. On receiving an RQ1 message, 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 device will transmit a "Data set 1 (DT1)" message, which contains the requested data. Otherwise, the device won't send out anything. Byte F0H 41H DEV MDL 11H aaH | | ssH | | sum F7H Size Description Exclusive Status Manufacturer ID (Roland) Device ID Model ID Command ID Address MSB | | LSB MSB | | LSB Check sum End of exclusive ·Main data: BODY This field contains a message to be exchanged across an interface. [. . . ] Requested data, for example, may have a limit in length or must be divided into predetermined address fields before it is exchanged across the interface. * The same number of bytes comprises address and size data, which, however, vary with the Model ID. * The error-checking process uses a checksum that provides a bit pattern where the last 7 bits are zero when values for an address, size, and that checksum are summed. ·Data set 1: DT1 (12H) This message corresponds to the actual data transfer process. Because every byte in the data is assigned a unique address, a DT1 message can convey the starting address of one or more bits of data as well as a series of data formatted in an address-dependent order. [. . . ]