m16
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
m16 [2018/09/08 13:16] antichambre [Dimension] |
m16 [2018/09/08 14:10] antichambre [Special command messages] |
||
|---|---|---|---|
| Line 145: | Line 145: | ||
| The **m16** can receive some specifics commands and send back some status messages.\\ | The **m16** can receive some specifics commands and send back some status messages.\\ | ||
| when **CIN=0x1**(local command), the **m16** will parse the message as a command and apply the requested change.\\ | when **CIN=0x1**(local command), the **m16** will parse the message as a command and apply the requested change.\\ | ||
| - | * Port(Cable)value becomes Group Command Code.\\ | + | * Port(Cable)value becomes Group Command Code(GCC).\\ |
| - | * evnt0 is the command number.\\ | + | * evnt0 is the command number(CMD.\\ |
| * evnt1 and evnt2 are the value bytes.\\ | * evnt1 and evnt2 are the value bytes.\\ | ||
| List of the commands:\\ | List of the commands:\\ | ||
| Line 154: | Line 154: | ||
| </WRAP>\\ | </WRAP>\\ | ||
| </WRAP>\\ | </WRAP>\\ | ||
| + | With System commands, you will be able to | ||
| + | * Put SPI or UARTs in loopback for testing purpose. | ||
| + | * Enable MIDI activity status messages over SPI(MISO). | ||
| + | |||
| + | There's only one MIDI configuration command, for Running Status enabler.\\ | ||
| + | |||
| + | With GPIOx commands, you can configure and set the GPIO ports.\\ | ||
| \\ | \\ | ||
m16.txt · Last modified: 2018/10/08 09:12 by antichambre
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
