
SLMKII MIDI Programmer’s Reference
Page 7 of 33
4. Sysex Headers and Commands
There are three special sysex header groups for controlling and retrieving information
from the SLMII:
1.
The Original Automap Sysex Header.
2.
The Data-Block Change/Request Sysex Header.
3.
The TEST ‘Simulation’ Sysex Header.
The Automap commands are directly associated with special Templates, such as the
Main Automap Template, and the Ableton Template.
The Data-Block commands are three pairs of Request and Change memory block
commands for retrieving and manipulating Global, Template header and Control
data.
The Simulation sysex header is primarily concerned with operations for simulating
physical control changes at the SLMKII, mainly for TEST purposes – and is NOT part
of the normal operation of the unit. By sending this header to the unit, with additional
command numbers and values – the unit is made to behave as if a user had actually
operated a physical control. Accompanying these simulation commands are request
commands; for requesting the current LCD text, all LED states and memory blocks at
specific addresses.
Data-Block and Simulation commands do NOT require a Special-Template to be
loaded on the unit.
AUTOMAP SYSEX HEADER:
Novation MIDI-Id
Automap
Versn - Beta
Tmpl
Spare
Data
F0
00
20
29
03
03
VV
Bb
02
00
. . . .
F7
All Automap sysex messages have the header above.
VERSION-BETA: these two bytes indicate the main and beta version numbers of the
SLMKII when the particular version of the protocol was introduced – currently they
should be set to 12h : 00h – and are expressed in BCD form.
(12:00 = New (LEDs) Live Version)
SPECIAL TEMPLATE NUMBER: for Automap specific messages this is set to 02.
Originally there were 8 ‘special’ Templates – eg 04h is the Ableton Template – all
other special Template numbers are now redundant.
DATA: The Data section will have a Command byte followed by zero or more header
and/or data bytes.