1st Qu16 integration question!!

Hi there... So I'm all in - Bome box Should Arrive today; and just programming up some test stuff via computer / Bome Translator Pro that I bought this morning... Or... umm... trying to ahah...

I read the manual last night. Seems logical - thing is, that I'm a little stuck on the more complex NRPN messages the Qu16 requires. Briefly:

I want to setup the Qu16 custom layer faders as MIDI only. Then I'll translate those to do whatever I want both in the Qu16 and on other external equipment. Things like the QU FX-sends per channel etc. which are not accessible via the custom layer.

SO... I have connected things, and wrote a quick translator to see if I can move the channel 2 MIDI fader with the channel 1 MIDI fader... I can!! :) Good... so things are connected and communicating!!

The MIDI Faders send CC#0-CC#15 at standard 0-127 values. So CC to CC is a walk in the park :)

Ok - so now I want to dive in and go crazy!! But all I'm doing is the going crazy part haha... My current issue is I'd like to now control a channels FX send level with one of these faders... But it's a fairly complex NRPN (well - sorry - it's NRPN, which I find fairly complex!)...

When I Capture the midi data of fx send... it's pretty intense. Switch to raw data and it looks more manageable:

B0 63 22

B0 62 20

B0 06 [VAR]

B0 26 10

This is great - because I recognise the NRPN and Data MSB/LSB of ALL of these via the QU Midi protocol. The [VAR] is the only variable value too, and it seems to be in Hex Dec (00 - 7F)...

So, I have:

Incoming: MIDI fader Data; Value = oo (user defined as 'oo')

Outgoing: I've popped all of the raw midi in a single line string in "Outgoing" that looks like: "B0 63 22 B0 62 20 B0 06 oo B0 26 10" (where 'oo' is the variable... )

But nothing happens - well - the only thing that happens is if I pop my midi fader down to zero; the send fader will snap to zero... any other value for the midi fader and nothing happens.

Am I executing the raw data string incorrectly?? I tried using the non-raw data, but I don't recognise any of the stuff popping out (I was relieved to see the raw data spit out the exact values I was looking for!)...

Do I need to send multiple separate messages perhaps? Sorry - I'm trying my best to read manuals and learn, but I'm a bit stuck already. Luckily - this is also probably as hard as I'll need to program ;)

FWIW - I think I'd actually like to use this raw data format, as it's what the QU16 protocol is written in - so any help in excuting it in that format would be great!...

I really appreciate any help :)

Waiiit.. wait wait wait... I did it!!!!! Yay.. I'd actually accidentally changed the incoming trigger off "any value".... it was waiting for an 'oo' that would never come :) This is gonna be rad !!! Soo freaking rad... And it's my Birthday today too - so my present to myself, other than BomeBox and software, is to nerd it up and program a cray live elctronic setup into my QU 16... :)

One last comment... HAving resolved the issue... This is so much fun already... I have a kick channel on my Qu with a single fader controlling up the HP filter then at value 30+ it starts feeding in reverb, and then at 70+ a little delay... I'm loving just playing with a 4-4 kick drum at the moment haha...