MSA Firmware Version 3.2 User Manual

Add to My manuals
15 Pages

advertisement

MSA Firmware Version 3.2 User Manual | Manualzz

Highly Liquid MSA Firmware V. 3.2

3.2.2 Store Command (s0, s1)

The Store Command is the MIDI message used to trigger storage of a preset state when using the Learn

Method. s0 specifies the message type as defined in

Table 3-b

. s1 specifies the program number, CC

number, or note number.

Table 3-b: Store Command Types

s0 (Hex)

00

01

02

04

Message Type

No MIDI store command.

Program Change

CC

Note

3.2.3 Outputs Controlled by Preset

Byte bb specifies which MSA outputs will be under both preset control and individual output control, and

which MSA outputs will be under individual output control only. See

Table 3-c

.

Table 3-c: Outputs under Preset Control

bb (Hex)

04

05

06

00

01

02

03

07

08

Outputs under both preset and individual output control

none

0

0, 1

0, 1, 2

0, 1, 2, 3

0, 1, 2, 3, 4

0, 1, 2, 3, 4, 5

0, 1, 2, 3, 4, 5, 6

0, 1, 2, 3, 4, 5, 6, 7

Outputs under individual output control only

0, 1, 2, 3, 4, 5, 6, 7

1, 2, 3, 4, 5, 6, 7

2, 3, 4, 5, 6, 7

3, 4, 5, 6, 7

4, 5, 6, 7

5, 6, 7

6, 7

7 none

3.2.4 Preset State (nn, k0-k7)

Byte nn specifies the number of the preset defined by the following 8 bytes. nn corresponds to the MIDI program, CC, or note number used to recall the preset. The MSA can store up to 128 presets. The valid range for nn is 00h-7Fh.

Byte k0-k7 specify the states of MSA outputs 0-7. For these bytes, a value of 00h sets the output to off, and a value of 01h sets the value to on.

© 2013 Sonarcana LLC Page 9 / 15

Highly Liquid MSA Firmware V. 3.2

4.0 Factory Default Configuration

By default, MSA outputs 0-7 respond individually to MIDI notes 60-67. Presets are recalled by Program

Change messages. The default configuration can be expressed as one Individual Output Configuration

Sysex message and one Preset Configuration Message as shown in

Figure 4-1

and

Figure 4-2

.

Figure 4-1: Factory Default Individual Output Configuration SysEx Message

SysEx Data (Hex) Meaning

F0 00 01 5D 05 01 Fixed header

00

01 3C 01

Unit ID (00h = all units)

Output 0 configuration

01 3D 01

01 3E 01

01 3F 01

Output 1 configuration

Output 2 configuration

Output 3 configuration

01 40 01

01 41 01

01 42 01

01 43 01

07 67

F7

Output 4 configuration

Output 5 configuration

Output 6 configuration

Output 7 configuration

Pulse length: 500ms

(Not used by factory default output modes.)

Fixed footer

Figure 4-2: Factory Default Preset Configuration SysEx Message

SysEx Data (Hex)

F0 00 01 5D 05 02

00

01

02 7F

08

Meaning

Fixed header

Unit ID (00h = All Units)

Recall type: Program Change

Store command: CC #127

Outputs under both preset and individual output control: all

00 00 00 00 00 00 00 00 00

. . .

7F 00 00 00 00 00 00 00 00

F7

All outputs off for presets 0-127.

Fixed footer

© 2013 Sonarcana LLC Page 10 / 15

Highly Liquid MSA Firmware V. 3.2

5.0 Configuration Retrieval

5.1 Identity Request / Identity Reply

The MSA responds to the standard “Identity Request” SysEx command. If the MSA receives the SysEx

message described in Figure 5-1, it will respond with the standard “Identity Reply” message described in

Figure 5-2.

Figure 5-1: Identity Request SysEx Message

SysEx Data (Hex) Meaning

F0 7E 7F 06 01 F7 Fixed Message

Figure 5-2: Identity Reply SysEx Message

SysEx Data (Hex)

F0 7E 7F 06 02

00 01 5D

00 00

00 05

00 vv

id tt

F7

Meaning

Fixed Header

Manufacturer ID

Family Code (MIDI Decoder)

Model (MSA Rev K)

Version, where vv is the firmware version number

as described in

Table 5-a

.

Unit ID

Reserved for future use.

Fixed Footer

Table 5-a: Firmware Version

vv (Hex)

00

01

02

03

04 thru 7F

Firmware Version

3.0

3.1

3.2 beta

3.2 production

Reserved for future versions.

© 2013 Sonarcana LLC Page 11 / 15

Highly Liquid MSA Firmware V. 3.2

5.2 Output Configuration Retrieval

The current MSA configuration can be retrieved via the MSA MIDI Out port.

If the MSA receives a SysEx message as described in

Figure 5-3

, it will send its configuration as an

Individual Output Configuration SysEx Message.

If the MSA receives a SysEx message as described in

Figure 5-4

or

Figure 5-5,

it will send its

configuration as a Preset Configuration SysEx Message.

Figure 5-3: Individual Output Configuration Request SysEx Message

SysEx Data (Hex) Meaning

F0 00 01 5D 05 00 00 01 F7 Fixed Message

Figure 5-4: Preset Request (Single Preset) SysEx Message

SysEx Data (Hex) Meaning

F0 00 01 5D 05 00 00 02 Fixed Header

pp

Preset #

F7 Fixed Footer

Figure 5-5: Preset Request (128-Preset Dump) SysEx Message

SysEx Data (Hex) Meaning

F0 00 01 5D 05 00 00 04 F7 Fixed Message

© 2013 Sonarcana LLC Page 12 / 15

Highly Liquid MSA Firmware V. 3.2

6.0 DIP Switch

The MSA DIP switch serves two main purposes: to set the MIDI channel for MIDI input, and to set the

“Unit ID”. See

Table 6-a

.

6.1 MIDI Channel

The MSA DIP switch is used to specify the MIDI channel for incoming MIDI messages. During normal operation, the MSA will respond only to messages received on this channel.

6.2 Unit ID

Each configuration SysEx message contains a Unit ID byte.

If the Unit ID byte is 00h, any MSA unit receiving the message will configure itself as directed by the message.

If the Unit ID byte is between 1 and 16 (01h to 10h), any MSA receiving the message will update its

configuration only if its DIP Switch setting matches the Unit ID. This allows the user to target &

configure a single MSA within a chain of multiple units.

Table 6-a: MIDI Channel / Unit ID DIP Switch Settings

1 on on on

off off off

on

off off off off off

on on on on

10

11

12

8

9

6

7

MIDI

Channel /

Unit ID

1

2

3

4

5

13

14

15

16

SW1 Setting

2 3

off off off

on on on

off off off off off

on on on on on

off

on on

off

on on

off off off

on on

off off off

on on

4 on

off

on on

off

on

off off

on

off

on

off off

on

off

on

© 2013 Sonarcana LLC Page 13 / 15

Highly Liquid MSA Firmware V. 3.2

7.0 Activity LED

The MSA activity LED performs several functions:

Self test: Upon power-up or device reset, the activity LED lights briefly before normal operation begins.

Configuration update indication: The LED blinks 3 times when the MSA configuration is updated via a MIDI SysEx message. If no LED activity is observed, then the attempted configuration was unsuccessful.

MIDI activity indication: The LED blinks when a MIDI message is received that affects the

MSA output state. Other MIDI messages will not cause an activity indication.

Individual output control learn mode indication: The LED will blink slowly while the MSA awaits MIDI messages during Learn Mode.

Preset store: The LED blinks twice when a preset state is stored using the Preset Control Learn

Method.

Firmware update error: The LED blinks continuously when the receipt of a firmware update

SysEx message has failed, or when the firmware has become corrupt.

© 2013 Sonarcana LLC Page 14 / 15

Highly Liquid MSA Firmware V. 3.2

8.0 Firmware Update

MSA firmware can be upgraded via MIDI SysEx message. Firmware update files, when available, can be downloaded from the MSA product page at highlyliquid.com.

8.1 Firmware Update Procedure

1. Download and unzip the firmware update SysEx message. The resulting file should have the extension “.syx”.

2. Disconnect power to the MSA.

3. Press and hold the PRGM switch. (See MSA Hardware User Manual.)

4. Reconnect power to the MSA. The activity LED will remain lighted.

5. Send the firmware update SysEx message to the MSA. Transmission of the message may require several seconds.

6. Upon completion of the update, the activity LED will deactivate.

7. Release the PRGM switch.

8. Disconnect power to the MSA.

8.2 Notes

Do not interrupt the transmission of the firmware update SysEx message.

A continuously blinking activity LED indicates an error in the transmission of the firmware update SysEx message.

If a continuously blinking activity LED is observed, repeat the procedure from the beginning.

The current firmware version can be retrieved via Identity Request / Identity Reply SysEx

messages.

© 2013 Sonarcana LLC Page 15 / 15

advertisement

Related manuals

advertisement