Moog Voyager Select - OS & Presets Issue

[DeeTaG]

Hi everybody.

I have my Moog Voyager Select since almost one month and it worked really great so far.
Since this morning, I don't know why, I have trouble with the Moog and really don't know how to solve the issues.

Maybe you guys know what to do in this case.

I have the following two problems:
- Almost all the factory presets from bank A to bank G are gone or damaged.
Some of them are displayed with really strange signs, others don't even make any sound.
Here is a screenshot of what some of the presets are displayed like at the moment:
http://www.deetag.de/stuff/moog/IMG_1901.JPG

- The second problem is, that the OS of the Voyager seems to be damaged.
Everytime I turn on the device, I get the following message:
"The Operation System has to be re-loaded! Re-load Bank D?"
http://www.deetag.de/stuff/moog/IMG_1897.JPG


I'm trying to reinstall the 3.5 OS now since several hours, but still no luck. I downloaded the latest update from the moog page:
http://www.moogmusic.com/products/minim ... nloads-tab

Just for the technical background...
My Moog is connected to my AKAI MPD32 via Midi, the Akai is connected to my Macbook via USB.
I'm working with the "SysEx Librarian" Tool

The data transfer is starting without any problem, but after about a fifth of the whole progress bar, the transfer aborts with the following message:
"System Exclusive Transfer has failed !!!!!!!!!!".
http://www.deetag.de/stuff/moog/IMG_1898.JPG


Is there any possibility to get the 3.5 OS back with all the factory settings?
I really don't know what I did do to that Moog to get this failures. Yesterday evening, everything was still fine...

I hope you guys can help me. I don't really know what to do at the moment.


Thank you so much in advance

Greetings,
Dominik.

[till]

Had you ever tested your Midi setup for transferring to and from the Voyager to your Mac before this happens?
Some Midi interfaces don't like big sysex data files.

What OS was installed before? The same as the one you tried to load as requested by the Voyager?

Some tests:
Don't use USB hubs.
Just route the Midi interface into the Voyager and no Midi from the Voyager to the interface to be sure there is no Midi loop.

Sysex Librarian works fine here for my Mac since years. So this is most likely not the problem.
As the Voyager is doing a self check on booting, you get this message about reloading a system bank. Strange that this happens. What did you before this message and the scrambled sound names happened? There might be a problem with your Voyager's hardware.

Maybe Rudi Linhard knows what happens. He wrote the software of the Voyager system. he is reading the forum regularly.

[DeeTaG]

Hi Till.

Thank you for your answer and sorry for the really late reply...
I didn't notice that you answered my topic

The problem is already solved.
Rudi told me to try another Midi-Interface.
I bought a new midi interface (M-Audio Midisport 2x2) and it's just running fine.
As you and Rudi metioned, I guess the AKAI can't handle the big sysex files.

So... Thank you very much Till and especially Rudi for you quick help!!
I really appreciated it!

Have a great day.

[lockeness]

Were you able to reinstall operating system 3.6 through SysEx librarian? I haven't been able to find a copy of 3.6 online. Only 3.5.

If so, is there a special setting the Voyager needs to be on to receive it?

My Voyager is not generating audio. I can send midi, update the presets. When I turn up the volume all the way, I can hear a slight Noise sound when I hit a key. I'm hoping it's not a hardware issue!

Any thoughts would be most helpful. Thanks!

[Vsyevolod]

That happened to me the other day. Then I noticed that I had an insert cable plugged into the back with the other ends not connected to anything... [facepalm]

Stephen




.

[Confusion]

I had the same problem and when I reinstalled the OS and the presets everything works fine... Until the preset return damaged.
The problem is the the my moog voyager RME is unable to retain is memory anymore. I have open my voyager and found that there is a battery 3032 3V soldered on the board. I tested it with a voltmeter and it indicate only 0.156 volt. A new battery cost around 25$. Manufacturer Part Number
VL-3032/GUFN
http://www.digikey.ca/product-detail/en ... -ND/119930

Conclusion: I have replace the battery myself by cutting the legs of the old ine without touching the board. I soldered the new one on the legs of the old battery. It was easier that way for me... You can send your voyager to service if your not confortable and have extra money.

[RL]

BTW, the battery of the Voyager is rechargeable and in most cases it will be full charged when the power is on for a few hours. If you do not switch on your Voyager for one year the battery gets discharged and all presets are gone.

[Ledbetter]

After I read this, I turned my Voyager on to make sue the battery is charged. Haven't used it for a few months, but presets still there. Thanks, RL, for the heads up.

[Confusion]

In my case the battery wasn't able to kept his charge anymore.