Post by The History Kid on Jun 15, 2015 0:16:48 GMT -5
Hey all,
I've run into what I find to be a particularly peculiar problem that I'm hoping I can get some advice on here before calling Emotiva.
I have both an XDA-2 Gen 1 and a Fusion 8100. Usually they work in perfect harmony together, remotes and all. But tonight, something rather strange happened. For starters, the XDA would not power with the remote, and when I turned it on manually, all of the buttons acted as "SRC BYPASS" buttons on the remote. Even the volume control. Thinking nothing of it, I went to get a few batteries - thinking it was an issue with them. When I returned, my Fusion 8100 volume was MAXED. Every time I went to turn the Fusion down, it would turn itself back up. When I would hit the volume down on the remote of the Fusion it would reduce the volume all the way to 0, and when I hit the up button it MAXED the volume.
My immediate thought was to replace the batteries in both, so I began with the Fusion, thinking it was just a coincidence that they both started acting up. Well, that didn't do the trick. So I did a hard power cycle on the Fusion to see if that would resolve the issue. Nothing. Finally I decided that I at least wanted to get my XDA working, since if I had to send the Fusion in, I could still use the XDA with my UPA-2. When I removed the batteries from the XDA-2's remote, the Fusion stopped acting crazy and returned to normal operation. The volume controls now work like they should on the Fusion and don't totally spaz out. However, when I added brand new batteries, the problem started again on the Fusion and the XDA continued to only receive volume, power, and source commands as "SRC BYPASS".
So...while I've never had this issue with these two devices before, and it seems an odd problem to boot, I'm forced to believe the problem is with the XDA-2's remote. Does anyone have any kind of idea what could cause something like this to happen? Anyone seen this before? It just seems odd since the only relative commands between the two units would be power and volume - nothing else. Ideas of what to troubleshoot in addition before calling for a remote replacement?
Thanks guys!
I've run into what I find to be a particularly peculiar problem that I'm hoping I can get some advice on here before calling Emotiva.
I have both an XDA-2 Gen 1 and a Fusion 8100. Usually they work in perfect harmony together, remotes and all. But tonight, something rather strange happened. For starters, the XDA would not power with the remote, and when I turned it on manually, all of the buttons acted as "SRC BYPASS" buttons on the remote. Even the volume control. Thinking nothing of it, I went to get a few batteries - thinking it was an issue with them. When I returned, my Fusion 8100 volume was MAXED. Every time I went to turn the Fusion down, it would turn itself back up. When I would hit the volume down on the remote of the Fusion it would reduce the volume all the way to 0, and when I hit the up button it MAXED the volume.
My immediate thought was to replace the batteries in both, so I began with the Fusion, thinking it was just a coincidence that they both started acting up. Well, that didn't do the trick. So I did a hard power cycle on the Fusion to see if that would resolve the issue. Nothing. Finally I decided that I at least wanted to get my XDA working, since if I had to send the Fusion in, I could still use the XDA with my UPA-2. When I removed the batteries from the XDA-2's remote, the Fusion stopped acting crazy and returned to normal operation. The volume controls now work like they should on the Fusion and don't totally spaz out. However, when I added brand new batteries, the problem started again on the Fusion and the XDA continued to only receive volume, power, and source commands as "SRC BYPASS".
So...while I've never had this issue with these two devices before, and it seems an odd problem to boot, I'm forced to believe the problem is with the XDA-2's remote. Does anyone have any kind of idea what could cause something like this to happen? Anyone seen this before? It just seems odd since the only relative commands between the two units would be power and volume - nothing else. Ideas of what to troubleshoot in addition before calling for a remote replacement?
Thanks guys!
