IT WORKS !! 
something like this.
cc to sysex.axo (2.6 KB)
since sending SysEX to DIN and USB requires different code, the choice of destination port is unconventionally controlled by sendDIN switch – when it's active, SysEx messages are sent to DIN, otherwise to USB.
also, deviceID is made as attribute, because it can be set different.
moar details in K-rate code comments.
just showing off some work in progress (this time screenshot only).
made Model ID bytes attributes too, to make my objects more reusable with less code rewriting.
i believe that Roland uses same SysEx with different Model IDs in many other machines MIDI implementation.
also, object for controlling Yamaha XG machines are in progress.
they should work with (nearly) any XG machine, because typically all those machines have one generic Model ID.
and also i'm going to make inlet versions of my cc-to-SysEx objects to allow incoming CC to be processed in the patch before they converted to SysEx.
testlab 
EDIT: just finished the most tedious part of the project — documenting what Roland documented poorly.
Yamaha XG is documented far better.
Hey @chaocrator 
Have been playing around with an edited version of the object today. Really good
Did you also try sending the sysex via Axolotis device port, to the computer?
not yet, just did not ever need that (i use Axoloti for 100% hardware solutions to do things).
anyway, should not be a problem, device port uses the same USB MIDI protocol to communicate.
Thank you foe the answer.
I tried a few things and had no luck yet.
I am realising that maybe it is the app that i am using to route the sysex data to it's destination, that maybe doesn't support sysex. I wrote the developer and asked, still waiting for a answer.
