Major issue: booting never ends

[Krotitelklistat]

Hello dear sequentials!

I own ob6 and have encountered major issue - please see my video on youtube


It worked last time I left the place.
Now, when I came back, it does this funny boot sequence. 

Any ideas where might be the issues?

[RobustAmerican]

Sorry to hear and see your troubles there...I've never seen anything like that here with my desktop version. Also can't remember seeing anyone here on the forum with a boot issue. Though I could be wrong there. I would shoot an email to the official Sequential Support folks. They have a kick-ass policy when it comes to repairs that require sending the unit in. Probably the best policy in the industry.

Good luck!

[AlainHubert]

Looks like the FlashRAM might have become corrupt perhaps? You could always try to use the embedded BootLoader and resend the Operating System?

[from the OB6 user manual]

To restore your OB-6 if it is frozen.

1. Power on the OB-6 while holding the Write switch to enter bootloader mode. You’ll see an animation in the Effects Parameter 1 display.

2. Use a MIDI cable (not USB) to transmit the new OS to your synth. You must use a standard MIDI cable for this. USB MIDI doesn’t work in bootloader mode.

3. As the OS loads, you will see the main display count backwards from 999. When it gets to 0, another countdown will begin between the main display and the FX Parameter 1 display. Do not power down until this countdown has finished. The OB-6 will restart itself when it is done.

(the synth might hang at the end of the last step. If so, after waiting for 5 minutes, you can power-cycle the synth off and on.)

[Krotitelklistat]

I've sent it to dealer, since I bought it in Thomann.de and still have it under warranty.
They've fixed it in no time and now I've got it back fully working.

They've reported this:
- reconnected the losing ribbon cable; recalibrated the pitchwheel, modulation wheel & osc/filt; performed a visual inspection, VDE-safety check & functional check = issue resolved/staff1338

So I'm not really sure, what was the problem, but all is good now. :-)

[AlainHubert]

Thanks for the follow-up. Loose ribbon cable seems to have been the culprit here.