MB Link and Sysex?

Testing/Troubleshooting
1

Hello,

I’m in the middle of building my own Midibox DIY synth. Both SID and FM modules works fine, so I deciced to build them together.

My current config looks like this:

Midi In –> Core1 (for SID) –> MBLink –> Core2 (for FM) –> Midi Out

Almost everything works (ordinary midi messaged are processed well), except sysex messages. Core2 can be accessed fine with sysex, I can upload patches, firmware. Core1 does not work, when I try to reload firmware, I get “Received unexpected MIOS SysEx message = 00007E40020E0B00F7  expected = 00007E4001” message.

Core1 configured to MBLink forward point, device id 1, and Core2 configured to link endpoint and device id 2.

Am I missed something important?

Thanks.

Regards,

Gyurek

2

Hi Gyrurek,

the second core sends “0b” status core, which means: MIDI overrun.

It seems that the MBFM firmware loads the CPU already so much, that merging cannot be done this way :frowning:

If you’ve luck, it will work better when a “primitive patch” (which doesn’t use the modulation features) is selcted.

Best Regards, Thorsten.