|
|
|
URC's Consumer Remotes Forum - View Post
|
|
|
|
|
|
|
The following page was printed from RemoteCentral.com:
Topic: | MX-850 Aeros and MRF-350 This thread has 3 replies. Displaying all posts. |
|
Post 1 made on Monday February 19, 2018 at 15:11 |
urcuser Lurking Member |
Joined: Posts: | February 2018 8 |
|
|
I'm wondering if anybody has seen this before:
I purchased a used MX-850 Aeros & MRF-350 with included RFX antenna from a helpful/knowledgeable user on this forum. I also got another remote, the MX-850 Orion from the same seller. Both remotes came with some pre-programmed codesets from the CCP software (at least I assume it's live-updatable software because the codesets -- Comcast Xfinity -- are not included in the database of the NX-RM820 Editor Software that I've downloaded from this forum). Let's be clear, I do not have access to live-updatable software, hence why I purchased the remotes with the codesets pre-loaded from someone who does.
When I set up the equipment, the RF of both remotes worked just fine with the MRF-350 (base station is set to ID #0).
I went into my "old" NX-RM820 Editor and added a few devices, keeping the pre-programmed Xfinity codesets right where they were. In the RF Setup I made sure everything was set to RF & IR and the receiver is on ID #0. Downloaded to the Aeros remote which overwrote the pre-existing data in the remote. I have not touched the Orion remote at this point.
Now, when I try to operate the Aeros remote it works IR only. The RF doesn't work at all. The status light doesn't blink on the RFX antenna (nor on the MRF-350 base station). I've noted that the firmware in the Aeros MX-850 is from October 2, 2008 (v 1.04, that's the firmware that the NX-RM820 is pushing to it. I do not know what the firmware was in the remote when I first received it; I did not think to check).
Therefore, is it possible that RF will be disabled permanently with the Aeros remote given the "old" nature of the NX-RM820 editor software? Are there any workarounds? I have no other solution -- the RF from this very same remote worked fine with the MRF-350 when i received it. The only change I can think of is that, likely, the firmware was newer when I received the remote from the seller because he had loaded from a newer editor software. And when I downloaded from the NX-RM820 software I overwrote that firmware with an older version which is incompatible with the MRF350?
Does this seem likely? Again I know the Aeros remote is capable of emitting RF and working with my MRF-350 because it did work until I updated the remote from the NX-RM820 software.
Side note -- My pre-existing setup used an MX-600 RF remote with MRF100 base station. I note the following additional things: (1) When sending signals from the Aeros, the MRF100 base station does not even light up, even though that base station is almost as old as the Aeros remote. (Again, before hooking it up to NX-RM820 software, the Aeros was able to communicate with both the MRF100 and MRF350).
(2) My MX-600 (non computer-programmable) is able to communicate just fine with the MRF-350, even though it may actually be older than the Aeros. Looking at the sticker in the battery compartment of the MX-600, it has a serial number of A131106. I read somewhere that the 6 digits represents the date of manufacture, but "13" is not a valid month so I don't know what that means. I've read elsewhere that Nov 1, 2006 is an important date. The serial number of the Aeros MX-850 is A071206.
(3) The Orion remote, which currently works fine, has not been "downloaded to" from the NX-RM820 software because I'm afraid of messing this remote up too. It works with both the MRF100 and the MRF350. I could check the firmware version of this remote in the editor software; however, I'm afraid to for fear of tainting it like I did the other one. Although the Orion works now, it does not have the devices/macros I want, hence why I'd like to have the ability to download from the NX-RM820 software but if I lose RF capability then it's pointless. I cannot determine the serial number of this remote since there is no sticker in the battery compartment.
Just curious if anybody can confirm that firmware is my problem with the Aeros OR if I'm just doing something stupid. I'm new to the editor software and have never successfully downloaded to an MX-800/MX-850 since my previous setup used the non-computer programmable MX-600. Again, ID is set to 0 at the bottom of the MRF350 and inside the editor software. RF is enabled in the software but I can't get the remote to even be recognized by the MRF100 or MRF350 even though IR is working fine.
Sorry for the long winded post but I'm just baffled at this point. Looking to see if anybody knows what's going on (even if there is no solution). Of course if there is a solution, please share :) Thanks,
|
|
Post 2 made on Sunday February 25, 2018 at 10:55 |
goldenzrule Loyal Member |
Joined: Posts: | July 2007 8,482 |
|
|
What are the RF setting set to in software? Get it off ID#0 also.
|
|
OP | Post 3 made on Tuesday February 27, 2018 at 19:00 |
urcuser Lurking Member |
Joined: Posts: | February 2018 8 |
|
|
I tried ID 0, 1 and A within the programming software. I experimented with the mrf-350 in every possible position on the dial at the bottom of the base station, including 0, 1 and A to match what was set in the software.
I read that sometimes older (pre nov 2006) mx-850s might not communicate properly with the narrow band of the mrf-350. But if that was the problem, it would communicate with my wide band mrf-100 and it did not.
I factory reset the aeros by holding down main+stop for a long time. This did not have any effect either.
Honestly I think the RF is just broke. While I thought I tested the RF when I first received it, perhaps I got confused. I got 2 mx-850's together. The Orion works and maybe I only tested the IR on the Aeros but not the RF. Who knows.
I appreciate the response and if you have any other ideas for me I'm all ears. Thanks!
|
|
Post 4 made on Tuesday February 27, 2018 at 22:00 |
goldenzrule Loyal Member |
Joined: Posts: | July 2007 8,482 |
|
|
ID 0 is sniffer mode (searches for RF interference). Do not use that, ever. It will accept commands from all IDs which can and will cause problems. The 850 had an RF antenna on the front of the remote that was known to sometime break off. If you hear a rattle in the remote it could be that. Only way to confirm is opening up the remote.
|
|
|
Before you can reply to a message... |
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now. |
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.
|
|
|
|