UMC-200: OFFICIAL UPDATE TIPS AND HELP

[KeithL]

We tried to make the firmware update as straightforward as possible - by NOT offering multiple methods and "recovery" options - but that clearly hasn't worked for everyone.

I'm locking this thread because I want to keep the volume to a minimum so folks can just look here for tips and such without wading through a lot of posts. I'll put what I think is important here.

If you specifically think that I missed something, PM me and I'll consider adding it.

[KeithL]

***DO NOT*** leave a USB "update cable" plugged into the back panel of the UMC-200 when you are not actually doing an update.

I've heard from a few people who had left a short USB cable plugged into the update USB port on the rear of the UMC-200 so they could access it conveniently after installing the unit in a rack.

While this sounds like a good idea, having a cable plugged into that USB port *EVEN IF NOTHING IS ATTACHED TO THE OTHER END* can cause your UMC-200 to behave erratically. (Some symptoms include intermittent loss of the entire video output, loss of just the OSD, occasional DSP Faults, and other weird behavior.)

THESE FAULTS ARE NOT "REAL"! They are caused by electrical noise picked up by the cable interfering with the processor functions of the UMC-200. Simply AVOID leaving a USB cable plugged in when you're not actually doing an update and these "mysterious" problems will go away!

[KeithL]

The "official" update procedure (described in the PDF file) was very carefully orchestrated to give the most users the best chance of a simple and successful update. We also chose to offer only one method, and to avoid "complications" like "recovery options".

Some users had problems getting it to work and, for some of them, one or another of the "alternate methods" solved those problems.

HOWEVER, we still STRONGLY suggest that you try the recommended procedure FIRST; we're quite sure that it is the most likely to work with the least problems for the most people.

Also, please note that every detail in the procedure is there for a reason, and has been carefully thought out. There is a reason why we recommend connecting the USB cable first, and not plugging and unplugging it during the procedure (because unplugging and plugging the cable can sometimes cause the processors to glitch), and a very good reason why we recommend installing the modules one at a time instead of checking all four (it takes longer but is much more likely to succeed on every module).

Try to follow each step (as if you didn't "know any better"); if we did something that seems like the slow way around, or tell you every time to check that Re-Program button, rest assured that there is a reason. Even details which seem to be unimportant (like whether you unplug the wire or not) can absolutely affect the outcome (or how long it takes you to get there).

[KeithL]

If you initially get a Fail when loading a module, you may find that when you try to repeat loading it the Status cell jumps directly to Fail (or even to Success) without your seeing the thermometer bar move from left to right - even for a few seconds.

This indicates a problem.

FIRST, make sure that you are checking the RE-PROGRAMMING button; The updater application defaults to SKIP mode, in which mode it will not reinstall a module that it detects is already installed. We do not EVER use this mode.

SECOND, make sure that you have checked only one module (unless specifically told to do otherwise); By default, all four modules will be checked and you MUST UNCHECK the ones you don't want to install.

If you do this correctly, after a fail you can usually RE-CHECK the module, RE-CHECK the Re-Programming button, and hit START again and get a successful install.

IF, at this point, you get the "jump to done", then you PROBABLY have a copy of the firmware updater application "stuck" in Windows memory. If this happens, when you try to run it next time it will "double load" and then not work correctly.

[This can also happen if you exit the application using the "Windows close X" in the upper right corner instead of the QUIT button.]

If this happens, close the current copy of the updater application, and then use Windows Task Manager to locate and close the "orphaned process" copy of it that remains in memory. If you're not comfortable with Task Manager, simply rebooting the computer will do the job (but will take a bit longer).

[KeithL]

It is quite unusual to end up with a bad load if all four modules reported that they loaded successfully. However, it is possible, which is why the first thing to do is to try reloading all four modules.

Also, of course, make sure that you DISCONNECT THE USB UPDATE CABLE AND DO A LOAD DEFAULTS before you conclude that there's a problem.

---------------------------------

With the UMC-200, the "eternal loading loop" doesn't usually occur, even with a failed update. However, if it does, here's an alternative method that may solve the problem:
(let's call it "the Jumpstart method").

1) start the updater program on your PC with the UMC-200 Off (or disconnected)

2) set the updater program to update the fourth module.
(BE SURE TO SELECT RE-PROGRAM.)

3) hit START on the updater.
(At this point you will get an error box. DO NOT click OK on the box.)

4) NOW connect and power on the UMC-200.
(The error box should disappear and your load should proceed normally.)

5) You can then go back and install the other three modules.
(They can usually be installed out of order with no problem).

We usually install the fourth module only, then go back and install the first three -
one at a time.

-----------------------------------

Denist has suggested an alternate sequence, which works better for some people:

1) start the updater program on your PC with the UMC-200 Off (or disconnected)

2) leave the updater set to update all four modules (all four checked).
(BE SURE TO SELECT RE-PROGRAM.)

3) hit START on the updater.
(At this point you will get an error box. DO NOT click OK on the box.)

4) NOW connect and power on the UMC-200.
(The error box should disappear and your load should proceed normally.)

------------------------

The reason we don't recommend either of these as the default way of doing the update is that connecting the USB cable during the update process (while the power is on) CAN cause other issues - so the way we told you to do it in the instructions (leaving the wire connected) is normally more reliable.

[KeithL]

Just to re-state a few basics.....

1) Make sure you use a short USB cable (try to keep it to six feet or under).

2) AVOID using any specialty or "audiophile" USB cables. While they may (or may NOT) affect sound quality, many audiophile USB cables fail to meet basic USB data cable standards and will NOT work to perform an update.

3) Run the USB cable directly from your computer to the UMC-200; DO NOT run it through external hubs or extension cables.

4) Even if you followed these suggestions, sometimes simply trying a different USB cable, or a different USB port on your computer, will make things work as they should. [We've had good luck with Belden or Amazon Basics cables.]

5) Make sure you only plug in the cable to do the update, and unplug it FROM THE BACK OF THE UMC-200 when told to do so.

6) It shouldn't matter, but you could also try disconnecting your UMC-200 from your source components and monitor.

[KeithL]

If all else fails, you can of course call Emotiva Technical Support.

Unlike some other vendors, we'll always be here (well, maybe not on weekends) and ready to help.

And, finally, if you end up with something we can't help you through, or we suspect a hardware problem, or you just plain can't do the update yourself, you can always return the unit to us and we'll be happy to update it for you...

[KeithL]

We have tested the updater with Windows XP running on a Mac under Boot Camp and it worked just as expected. We believe that Windows 7 should also work under Boot Camp, but haven't had a chance to try it yet.

Unfortunately, we cannot support you with installing or running Boot Camp, but there are no special settings required to run the updater under it once you have it installed.

[KeithL]

During the update:

You probably want to turn off or disconnect any amps you have connected - especially if they are on triggers. Not only will they be switched on and off several times unnecessarily, but you could get odd noises out of the UMC-200 during the procedure.

Also, you probably want to disconnect (or, at least, turn off) any HDMI devices you have connected to your UMC-200. (We've done the update here with stuff connected with no problems, but it's possible that HDMI handshaking while the process is going on could "distract" the UMC-200 and so cause some sort of problem.)

[KeithL]

The joys of Windows:

IF you close the updater application using the red X in the top right corner instead of the QUIT button.....

or IF you have any sort of Fail at any step.....

or IF Windows just happens to be in a bad mood......


You might get a copy of the updater application "stuck" in memory. What this means is that, even after you close it, there is a piece of it still running in memory. This is a pretty common problem with any program running in Windows (it's a Windows thing). If this happens, any subsequent attempts to load modules will probably fail.

If it happens, or if you even suspect it has happened, the solution is pretty simple:

Assuming you are familiar with Windows and Task Manager, open Task Manager, look for the program still being listed as a Running Process even though you don't have it open, and END it if it is still running.

If you're not comfortable with Task Manager, simply rebooting your computer will do the same thing.

IN FACT, IF YOU HAD A FAULT AND NOW YOU CAN'T GET ANY MODULES TO LOAD SUCCESSFULLY, NOW WOULD PROBABLY BE A GOOD TIME TO REBOOT YOUR COMPUTER.