I went to update the OS from 1.3 to 2.2, but it failed, tried a couple of times, used both the editor demo, and Midi Librarian (OS X). Each time it stuck at stage 1, and now some of the lights come on, (different set of lights each time I power up), the display lights up, but the screen is blank. It also has no sounds.
I phoned the service number in the UK listed on the site, Hammond Hire Company, who couldn’t help, who then put me on to Funky Junk, who also couldn’t help, and then put me on to HHB.
I spoke to a guy there who suggested trying the alternative boot sequence (Cursor/Enter/Down whilst powering up). He then suggested I sent it to him which proved costly. I asked if this was something I could do myself, and he suggested a Silabs USB Debug Adaptor.
He also said he would supply the necessary files & data to perform the task via email. I gave him the email address over the phone, but the files have not got to me yet (I’m presuming he may have misheard my email address over the phone).
The setup I used was as follows:
Macbook Pro
Behringer BCR2000
Little Phatty Editor demo / Sysex Librarian
Little Phatty Stage edition
I’m wondering if this problem can be solved easily, provided I can obtain the necessary files and hardware, or will I have to send it off to some service centre?
The Silabs USB debug adapter requires a windows-PC to use (Silabs don’t seem to have programming software for the Mac). If you have access to a PC, though, it’s not a difficult process and the only expense would be for the debug adapter. One of our forumites even posted a Youtube video showing how to do it. It’s a fairly quick process once you’ve got the debug adapter and software.
Hi, I just signed up here to report another dead Phatty.
Was using the librarian to update firmware from v2.0 to 2.1 via Macbook Pro and it froze, crashed the MIDI framework, and left the Phatty screen stuck on “RX Firmware Stage 5”. After 20 minutes, hoping it might fix itself, I power cycled it and all the characters on the screen were garbled. Tried to re-do firmware, but librarian wouldn’t start the process, power cycled the Phatty again and now it’s dead. Blank screen, no sound, and the only other lights on are the 4 pot indicator lights, stuck all the way to the right.
Seems like some sort of librarian jibjab is going on, which is a pity because I was ready to buy it.
Any ideas on what I should do? Already contacted tech support… waiting… tried the phone… no answer during business hours.
Sounds like others have had to find a usb debugger thingy, software, PC emulator and some special secret firmware that only is bestowed on those worth enough to embark upon this quest.
Does anyone know of a reset I can do on the Phatty itself? No way to hold down a few keys on start and reboot the sucker? It’s too nice for the hammer solution, though if times get desperate I may have to give this sucker a reckoning.
I unfortunaly have yet another phatty to report dead… I tried updating my tribute edition today and it froze in stage 1 saying “stage 1 error, power cycle” It then wouldnt respond and I turned it off. Now when i turn it on all i get is “send firmware sx” all the lights are on and it doesnt respond. I am sad.
The problem is that the Phatty’s earth and common grounds are not always making connection together if at all. The digital aspect of the LP behaves in unexpected way as such. It’s a quirk of the LP’s design. My LP was experiencing issues with my modular when I moved down to Florida but I was able to figure out that the LP’s grounding issue was related to the new setup. The LP’s metal case is not correctly connected to the ground of the LP’s electronics in some if not most LP’s.
I asked Rosser at Moog about this grounding issue and this is what he had to say. “Are you talking about the “SEND FIRMWARE SX” problem? That is not caused by any sort of grounding issue.We are not sure what causes the problem to happen, but our engineers have checked and re-checked the grounding planes and they are confident that they are secure and stable.”
No it isn’t. The Voyager has a complete ground from the metal casing to the rest of the electronics and the LP doesn’t (the big round pin on you’re IEC cable)!
Just a further confirmation that issues with firmware update are not chassis ground related… but they are DEFINITELY midi driver related! 99% of the time, an error during firmware update is due to some problem on the computer side, be it the MIDI interface hardware or more likely the drivers installed. Please please, make certain you have the latest drivers for your computer operating system and MIDI hardware before attempting an LP firmware update.
In related news, we’re working on a firmware version that will be un-crashable even in the event of an error like this.
I’ll have more information about that as the project continues, but I can say it will definitely happen this year.
Just chiming in to report another dead LP (stage 1)
I’m using a PC with a MOTU Midi Express XT interface. Demo version of the editor librarian, going from OS 2.0 to 2.1. Got to RX STAGE 2 (or similar wording) on the LP and now is stuck saying SEND FIRMWARE SX CODE ERROR 2.
I’ve emailed Moog and will share anything useful here. Just really upset that my prize possession is now a paperweight.
it is always always a good idea to make sure you’re using the very latest drivers for your MIDI hardware before attempting a firmware update. Sounds like something failed during stage 2 in this case. Still worth trying to update your MIDI drivers before attempting to send firmware again… the only question now is, “will the unit respond” to a successful firmware-sending attempt. If so, you can recover gracefully from this. If not, you will need a USB debug adapter from silicon labs in order to re-load the firmware. The debug adapter is available for $35 from SiLabs, or perhaps another forum member could loan you one. I’ll email you with more info here in a moment.
Turns out the solution for me was as follows. Download MIDIOX, set the buffers to 1024 over 256 for both input and output, and manually send the sysex file to the phatty. It went through all five stages of recieving the file (rather than bombing out on stage 2 like last time) and now works perfectly. And if that wasn’t enough, its kept all my presets. Amazing.
I would like to thank Rosser and Amos for answering my query here and via email in a remarkably short space of time, and just generally being brilliant to a customer. Guys, you have confirmed my status as a Moogaholic. I’m addicted to Moogahol!
I was trying to sync logic to send the midi clock to the Slim Phatty and I went into the Arpeggiator settings on the master settings on the SP and then a message flashed up on the screen saying ‘erasing flash…’. Nothing happened for 10 mins so I assumed it had crashed and turned off the SP. Now when I turn it back on the screen is blank and all the four LED dials point to the bottom right. It is not responsive so I can’t update the firmware!
Also, It might be worth noting that I am using a powered USB hub with a Macbook 2.4gz Intel Core Duo. I wonder if the USB hub has send mixed up messages to wipe the SP??
Can’t wait!