Error while updating OS on Voyager!!!!

Hi!
I’m Alessandro.
that’s my frist time I try to upgrade my machine. Current Os is 3.3.
I was trying to upgrade directly to 3.5 (and it didn’t work), but reading the other posts in this forum, I gave a chance to 3.4 Os. Nothing.
That’s the message on lcd screen:
“System Exclusive transfer has failed !!!”
I’ve used Moog voyager editor/librarian software and also this one
http://www.snoize.com/SysExLibrarian/
Still the same problem. I’ve also checked my midi cables, but they are ok.
What can I do?
thanx
p.s. that’s my frist post here also. :slight_smile:

Hi Alessandro,

welcome to the forum. Make sure that the order in which you send the banks to the Voyager is:

B
A
C
D

:slight_smile: :slight_smile:

HI
yep, the order is the right one.
I think it’s very strange that the upgrade to 3.4 also has the same problem.
damn…
:question:
edit: I can be more accurate: EVERY upgrade’s bank (doesn’t matter if 3.4 or 3.5) give me the same problem.
Maybe a wrong general setting?

Is this a hidden message?

BTW, OS 3.6 has to be installed in the following order:
A
C
A
B
:wink:

Why not…

D
D
D
A

?

:smiley:

c’mon
please…
any serious suggestion? :open_mouth:

Well, since the upgrade goes wrong with both 3.4 and 3.5, then perhaps you should check to see the settings in the application that you are using in order to transmit the syx files. You need to make sure that the app transmits sysex files in bulks that are > 37 KB since that’s the size of the sys-ex for the Voyager.

ok! :smiley:
the problem wasn’t the data’s size but the transfer-rate. It was too fast.
So with sysex librarian, you have to set the speed at 30% or 40% and it works!
thanx

Yup, obviously it choked the Voyager. Nice to hear it works now. :sunglasses:

For those still having trouble updating, this link helped me out again.
Leads you to Rudi’s picture with the midi ox settings.
http://www.moogmusic.com/forum/viewtopic.php?t=6780&highlight=update&sid=42f5ce17e0d38308b0acbb20f15fe42f

Thanks Rudi & Moog for the update, cheers.

According to the docs it’s BDACD - D is requested at the end of the process as well.

I would say the next update needs to address this issue - somehow it has to be able to fixed so it’s just ABCD DONE! Better yet, A DONE.

Thanks for the update, regardless! I’m excited to load it up!

OK, here’s the right order:

  1. Start with bank B (this is the boot system and it makes really sense to start with that bank first)
  2. Then when the system asks for bank D leave “NO” and press ENTER.
  3. Then press MASTER (page 2.4) and load the banks A,C and D.

That’s it!
Have fun,
Rudi

This thread and the one linked above should be stickied.

I’ve always wondered why the banks are “requested” out of order. Perhaps to make sure people RTFM?