I've searched on this topic, and I found some similar issues for other users. But, my situation seems unique.

I am getting FAIL! codes (0, 6, 7, 8, 9, etc.) when I simply plug in the serial -> 1/8" plug from the computer to the remote. I have not done any downloading or uploading yet, and this happens regardless of whether the MX Editor is running. When I remove the cord from the remote, it "reboots" the remote, and all the tests pass with GOOD!.

Does anyone know why I'd get fail codes for just plugging in the cord? I'd like to upload my current configuration from the remote and change a couple of things, but I can't get past this first step.

Any help would be appreciated!

Maui_Boy

Did you try new batteries?

Yes, I just did. And, I still got a "FAIL! 1". Any other ideas?

How old is the remote?

Is the cable damaged?

Look at the end that goes into your computer? Any bent pins?

Push the cable in slowly and not quite all the way in. Keep trying until you can insert it as far in as possible but without the error code.

Then see if the Editor software recognizes the remote.

Let us know.

The remote is about 2-3 years old. It works just fine by itself.

The cable does not appear damaged. I typically coil it up in a 6" circle when not using it, and I keep it in a drawer.

No bent pins. The cable has a female RS-232 end on the computer side, so bent pins would be unlikely. :-)

Interesting...pushing the cable in very slowly (I mean _very_ slowly) caused the remote to reboot twice and then not show a FAIL! code. However, the remote will still not communicate with the MX Editor software. I get the following error:

"Error detected while communicating with your Remote Control.
Error code: 101-07UU-0000

The com port is being used by another program. Please
identify and exit the program that is using the com port."

So, I physically change COM port connection from COM1 to COM2 and change the settings in the MX Editor. And, I get the following error:

"Error detected while communicating with your Remote Control.
Error code: 102-27UU-0000

Either the com port setting is incorrect (Communications
Menu) or the cable is defective."

Strange thing is, now I am not getting FAIL! codes at all when inserting the cable again. The remote reboots once, and then it just shows "MAIN" where the FAIL! codes were before. Well, actually, it seems to alternate between FAIL! codes and the above behavior now.

Could this somehow be related to the settings on the COM port in my BIOS? Does it have to be set to something specific to allow the proper communications? I don't think there are different protocols, like there are with parallel ports (ECP, EPP, etc.).

Confused and frustrated... :-(

I'm thinking the MX-700 / cable combination is the problem. If you aren't even connected to the computer and it gives you a reboot and sometimes a FAIL message, then your computer serial settings are a non-issue at this point.

Duracell batteries are usually shipped with all URC remotes. Have you tried brand new Duracell batteries?

If you have, then I would order a new cable from URC to start with or if your have a dealer in your town, then take the remote down there and have them insert one of their cables (if you bought it here). If not, get your dealer to send you a new cable.

This has to be done one step at a time.

Interesting point. I had not tried the cable itself, free from the computer. I always tried it with it plugged into the serial port. I tried it by itself, and nothing happened on the remote, whatsoever. I'll try to download the software to another PC when I get a chance. Maybe it just doesn't like this PC.

Oh, and I did, in fact, try new Duracells. They didn't make a difference.

Thanks!

Well, if the MX-Editor is correct, there's a program running on your PC using COM1. Maybe it's configured for a modem? Or who knows? That program may have been crashing the remote control.

Best bet is to try another PC.

You might also try a USB to serial dongle if your USB port has been reliable.

Well, good news then. At least we know the remote is probably good.

And Jon's point about another program using COM1 is certainly valid. There are all sorts of programs that like to claim COM1 or COM2, without telling you, even though you aren't going to use it with the serial port. It can cause all kinds of havoc.

Let us know what happens on another PC.