Succ-U-Bus

[dmitri]

I wanted to see if it works on a real device because for me, all this time, with virtual ports I have been able to send the firmware correctly.

Can you describe/explain to me how you do it because for me it doesn't work even with virtual ports?
And if it does work as you describe, please post an MCT version here where firmware update for v3/v4 bootloaders is not disabled.

[Ken Forgettable]

I wanted to see if it works on a real device because for me, all this time, with virtual ports I have been able to send the firmware correctly.

You are using Linux? Does the Mac/Linux code use SendBigSysEx() ?!
Your code uses SenBigSysEx() for windows.

When using XP and the secure bootloaders, I have found MCT fails to send the firmware after the Erase SysEx for reasons I explained before. It doesn't work on real hardware or virtual ports either.
The test code I posted fixes the problem for virtual ports and I have no reason to think it doesn't work for the real hardware. I also think it is compatable with *all* the bootloaders (except of course that Succ-U-Bus requires more message passing).

If you have time, release MCT with the altered SendBigSysEx() and if it doesn't work, we can blame Dmitri

Cheers chaps!

[dmitri]

I tried the test version and it doesn't work - neither as a split sysex and as a single sysex. Tried both MegaDrum USB and virtual ports. The weird thing is that it now gives an error even when set to versions 1 or 2. The application log shows this:
01:32:13 INFO: Opening MIDI port (1) to send firmware...
01:32:13 ERROR: Trying to send BIG SYSEX message
The error was: MIDI error return code: 4
01:32:13 ERROR: Updating firmware

Tried it on Linux and got the same error.

[elrules]

What virtual ports do you use? I saw once you had Maple Midi, hadn't you?
I use Midi Yoke and it works with them

[dmitri]

What virtual ports do you use? I saw once you had Maple Midi, hadn't you?
I use Midi Yoke and it works with them

Maple MIDI. But it doesn't work with MegaDrum USB either, both on Windows and Linux.

[Ken Forgettable]

I tried the test version and it doesn't work -
*- cut -*
01:32:13 ERROR: Trying to send BIG SYSEX message
The error was: MIDI error return code: 4

This is not an error in sending the SysEx!
'Sending firmware... is entered into the log before the SysEx is sent so
'MIDI error return code: 4' is to do with identifying and opening the port

[dmitri]

I tried the test version and it doesn't work -
*- cut -*
01:32:13 ERROR: Trying to send BIG SYSEX message
The error was: MIDI error return code: 4

This is not an error in sending the SysEx!
'Sending firmware... is entered into the log before the SysEx is sent so
'MIDI error return code: 4' is to do with identifying and opening the port

And?

[Ken Forgettable]

And?

The test fix was for SysEx data getting corrupted or truncated, I was not aware of problems opening the ports - I am using XP and MidiYoke.
+ I can't find the source for Maple - is it available?
+ You can build MCT for youself now, is that correct?
Try MidiYoke.

The weird thing is that it now gives an error even when set to versions 1 or 2.

Oh buttocks.

[dmitri]

What virtual ports do you use? I saw once you had Maple Midi, hadn't you?
I use Midi Yoke and it works with them

It works! Almost.

I've installed MIDI Yoke.
1. When I configure MCT to use MIDI Yoke ports and do MIDI routing in MIDI-OX the firmware update using v3 bootloader the update goes smoothly both with a split and and single Sysex.
2. When I configure MCT to use MIDI Yoke ports and do MIDI routing in MIDI-OX the firmware update using v4 bootloader the update forgets to send the 'erase_sysex' but it doesn't report any errors and MIDI-OX shows that MCT does send the firmware sysex. I guess with the fixed 'erase_sysex' it will work just as well as with v3.
3. When I configure MCT to use MegaDrum USB directly the firmware update errors both with v3 and v4 bootloader. Seems strange.

I appologise for insisting that the update didn't work with v3/v4 bootloaders. It turns out it does work with MIDI Yoke but still have problems when using MegaDrum USB directly (and of course using Maple MIDI).

[elrules]

Maybe I should open a midi port through MidiPort library, and keep it open in a variable in the MegadrumConfigTool class, so when you want to update you just call midiportOutput.send(...)

Now it is like this:
midi outpu is opened with standard java midi library. It keeps opened all the app execution and closed when you close the app.
When you try to send firmware it tries to open the output with the MidiPort library and it gives error 4, that is, error opening port, maybe due to a lock by the java library

So one possibility would be to open a MidiPort output at the begining of execution before opening the output with java library, and keep them both opened, and send messages through them as requested. Don't know if that wil fix the problem but we could try