Serious problem trying update OS

Everything Phatty.
Post Reply
edobedo
Posts: 15
Joined: Wed Nov 29, 2006 10:15 am
Location: Italy

Serious problem trying update OS

Post by edobedo » Sun Dec 24, 2006 6:11 pm

Hi, I tried to upgrade my Little Phatty n.232 to OS version 1.02d.
I used a Mac OS9 and a MOTU Micro Express USB,
Software was OMS SysEx Sender.
Instructions says tha after the message "STAGE 2" the LP will reboot.

I waited something as 10 minutes but nothing happened,
so I tried to send again the file LP_T_v102d.syx, but after doing it
the display reported the message "SEND FIRMWARE SX"

Now the LP is like dead, all leds are illuminated.

If I shutdown and reboot, the displays shows for a while
the message

"Little Phatty
Version: 1.02d"

and after, again, "SEND FIRMWARE SX"

What can I do?
Can it be a software problem?
Or MIDI interface?
Tomorrow I'll try again using a MidiSport 2x2 and OSX

I never bought an old Moog because I don't want problems...

Happy Holidays

Edo, from Italy

User avatar
goldphinga
Posts: 626
Joined: Fri Apr 23, 2004 4:38 pm
Location: UK
Contact:

Post by goldphinga » Sun Dec 24, 2006 7:03 pm

You need to contact Moog about this asap.They will be able to sort it out for you.
Moog Gear: Voyager AE,LP Stage 2+CV outs (Blue LED's/Wheels, MF104SD, MF101 Filter, MF103 Phaser, Source, Memorymoog+, Minitaur.

edobedo
Posts: 15
Joined: Wed Nov 29, 2006 10:15 am
Location: Italy

Post by edobedo » Sun Dec 24, 2006 7:55 pm

I hope it, because I'm really distant from any repair center...
I sent an email to the address reported on the instructions pdf.

I hope in a fast resolution, because I need my LP working
not only because I like his sound (I never had a Moog before, now I must admit that is the more musical sound I ever had)
but also because I'm starting a new project with other musicians,
and I liked to include my LP for the soloes and as controller for my A-Station and Evolver.

The couple LP+Evolver is a killer solution

edobedo
Posts: 15
Joined: Wed Nov 29, 2006 10:15 am
Location: Italy

Post by edobedo » Mon Dec 25, 2006 9:49 am

Hi, i solved the problem using SysEx Librarian.
i think OMS SysEx Sender sent data too much fast,
so fast to cause a data overflow.
SysEx Librarian takes much time to do this,
and you can also slowdown the velocity transfert.

Now it's christmas with my Little Phatty!

Edo

MarkM
Posts: 909
Joined: Wed Mar 30, 2005 5:28 pm
Location: Northeast Tennessee, USA

Post by MarkM » Tue Dec 26, 2006 4:50 pm

Glad to hear yo worked it out.
Mark Mahoney
http://www.reverbnation.com/markmahoney
www.cdbaby.com/cd/mmahoneympeck
www.cdbaby.com/cd/markmahoney

edobedo
Posts: 15
Joined: Wed Nov 29, 2006 10:15 am
Location: Italy

Post by edobedo » Wed Dec 27, 2006 5:18 am

Yesss!!! :lol:

Post Reply