I have been messing around with HTM remotes for many years now and have 5 in the various systems in the house but I seem to have struck a brick wall and have bricked two remotes.

I get the error message about bad port or faulty cable but that is not the case. I have this PC and two notebooks and the same problem is occurring on all 3. Connect one of the other working remotes and it uploads the data so there is NOT a cable of COMM problem. But as soon as I connect the troublesome remotes I get the error. As a last resort I initialised them both and all tests showed it was good.

But the try to download to either and that rotten error immediately appears. VERY frustrating as the other day I was able to download a set of files to one but got the error immediately I tried to learn a code and it has refused to communicate ever since. It will not download any of the files I have.

I thought one of the 5 remotes was faulty a week or so ago when all the above happened (although it worked OK before) so purchased another. The replacement initially worked OK but has now also got bricked and will not communicate.

So I now have 2 MX850 (one branded "Aeros") that refuse to communicate with any of the three PCs here (yet other remotes do communicate) yet show "GOOD" for all internal tests.

I have tried:
1. Removing batteries - no difference
2. Initializing the remote - even worse, both are now useless with no programs on board and refusing to communicate
3. Deleting the MX850 program and re-installing it - no help
4. Deliberately changed the COMM setting from the correct 4 to COMM 1 and tried to download. It took awhile before coming up with the error message. Then set it back to 4 and instantly came up with an error message - it did not even appear to "look"!!

The "Aeros" is A070910 no 0269389 while the MX850 is A070213 No 0301672 so both should work (and they did at one stage) using the later MX850 program. That program works on an older MX700 I had so the program does not appear to be the problem. I've reloaded that program several times on different PCs, disabled and then re installed the USB converter (and BTW I have 3 different ones, one on each of the PCs and all give the same behaviour)

NOTE I've checked all the following:

1.In MX-Editor click "COMMUNICATIONS"
2.Click "SETTINGS"
3.Write down the COM PORT NUMBER
4.Go to your Windows Device Manager (Usually found under "Control Panel", "System", then the "Hardware" tab)
5.Click the "+" next to "PORTS"
6.Find the port that has "(COM ...)" at the end of it and make sure it matches the COM Port number you wrote down in step 3
7.If the number matches, right click on that port and select "PROPERTIES"
8.Select the "PORT SETTINGS" tab
9.The settings should read as follows:

Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow Control: None
Click "ADVANCED"
Make sure "Use FIFO buffers..." is CHECKED
Make sure both sliders for "RECEIVE BUFFERS" and "TRANSMIT BUFFERS" are all the way to the right
Make sure the "COM PORT NUMBER" matches the Com Port you wrote down in step 3
Click "OK" until you have closed the Device Manager and Control Panel
10.Reopen the MX-Editor software and test it by attempting to do a download to the remote (Full Download) "

All correct - still get the error message. Bah!!!

Can anyone help PLEASE?

TIA

John

All sorted thank you. Both now working again.

John

What was your fix?

Yet another solution that may work if anyone else is forced into this dilemma, as I was :(  I hope so.  I almost took that old, but new remote into the back yard to fine tune with a 12 ga.

After three hours of trying every combination of iterations I'd read about, always knowing in my heart that Windoze knows not what it does at any given time, I finally had a rush of brains to the head!

This is for my SIIG adapter, curiously named "USB to Serial-Value", and my Win10 Ultrabook.

Clean out the ports' existing driver info. For me Prolific 3.8.12.0 taunted me with mentions of Win7-8-&10, obtained here:

[Link: prolific.com.tw]

and install. Re-boot. Plug in the adapter, check Devmgr for assigned port if you didn't catch it, and launch the Editor in Compatibility Mode for Win 7. Set that port, use default properties, or slow the baud and lower the buffers, I did this, even to start out. I always run in superuser or Admin, so I don't know if it helped or not.

Plug in the Aeros MX-850 with good batteries, and if it gives you the firmware back you should be good to go.

Bruce

I keep my old xp laptop in my bag because I couldn't get my RadioShack USB to serial adapter to ever work with my Windows 7 laptop . Probably something simple but I couldn't figure it out .

Anyway all of a sudden a few years ago I started having to go into communications tab, change it off the correct comport, reenter communications tab, then change it back to the correct one to get it to work .

Yes, Tassie Devil, don't leave us here with all your story of misery, failure, and technical prowess but lack of success! What EVER did you do?

Being as this is a necro from 2014, I doubt hes going to tell us now.

"A necro." GREAT! And yup, we all missed it.