Quote:
Originally Posted by LVS /t/1356456/roomie-remote/1170#post_23811876
I am trying to control an Anthem MRX-300 receiver via IR. I am having mixed results. Device Powers on and off but after that I can’t really get it to change inputs reliably. Any ideas? I have tried increasing the retry counts but that does not seem to change this behavior.
Another issue is after powering the receiver on you need to wait about 10-seconds before sending it any additional commands. Is there any way to delay only when the device is powering on from the Off state. For switching inputs when the device is already powered I only need a minimal delay.
With the AVM50 and D2 series—even going back to the AVM20—you could send commands to the units at any time and they would execute. While those prepros are powering up, you can still send commands, but they don't seem to execute until the devices have properly powered up. If you're saying that the commands never get executed, then you need to email Anthem support and ask that question specifically. That seems like it's more of an Anthem issue than a Roomie issue.
I will say, however, that I'd be surprised if that's the case with the MRX receivers.
In my experience with the 50v, increasing the retry count to 250 seems to be perfect. I rarely need to do anything with the AVM50v. I've used it with both IR and Serial with Roomie with the same positive results.
Now to your question about changing inputs: have you triple-checked that the IR is right on top of the Anthem's sensor? Do you also have IR units with feedback enabled so that you can confirm that your commands are being properly sent and received via IR? I use Niles IR flashers with feedback and not the stock iTach ones. I find that the Niles IR flashers are much more reliable and work better in my experience. I've had the iTach ones fail or get funky and I've replaced them all with the Niles versions.
I think you're still going to be in that interesting debugging stage for a bit. I suggest being patient with it but certainly contact Anthem support. There just may be something anomalous happening with the Anthem's IR port.