Difference between revisions of "Firmware-72 Format"
(→Command and Message IDs and [Main Data]) |
|||
| Line 1: | Line 1: | ||
| − | + | The USB-microDig MIDI implementation uses the following data format for all system exclusive messages: | |
{| | {| | ||
Revision as of 17:48, 3 November 2015
The USB-microDig MIDI implementation uses the following data format for all system exclusive messages:
| Byte | Description |
|---|---|
| 240 (F0h) | System Exclusive Status |
| 125 (7Dh) | Manufacturer ID |
| {DEV} | Device ID |
| {CMD} | Command or Message ID |
| [BODY] | Main Data |
| 247 (F7h) | End of System Exclusive |
Manufacturer ID
The manufacturer identifies the manufacturer of a MIDI device. Infusion Systems uses the number 125 (7Dh). Infusion Systems does not own the manufacturer ID 125 (7Dh). This ID is usually reserved for general educational and/or research equipment. Please ensure that you do not have any devices with manufacturer ID 125 (7Dh) in your MIDI chain.
Device ID
This ID identifies a specific USB-microDig in setups with multiple USB-microDigs. This setting should remain 0 for use of the USB-microDig in stand-alone mode. Host mode allows for device IDs other than 0.
Command and Message IDs and [Main Data]
The Command and Message IDs and [Main Data] form the protocol for communication with the USB-microDig. The protocol consists of commands that are sent to the USB-microDig and messages that are sent by the USB-microDig.
