|
Post by TheTerrorBeyond on Apr 27, 2021 9:12:37 GMT -5
My XMC-2 failed this morning with this error: It would not restart or anything, so I pulled the power and it came back to life. Any ideas what this error is, or if it is something I should be worried about?
|
|
|
Post by TheTerrorBeyond on Apr 29, 2021 9:43:51 GMT -5
No ideas what this error message means? Anyone?
|
|
|
Post by doc1963 on Apr 29, 2021 12:02:56 GMT -5
No ideas what this error message means? Anyone? I've never encountered this and I think the "crickets" are speaking pretty loudly... You'll likely get a quicker answer by contacting Emotiva directly...
|
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,881
|
Post by cawgijoe on Apr 29, 2021 13:03:04 GMT -5
No ideas what this error message means? Anyone? I've never encountered this and I think the "crickets" are speaking pretty loudly... You'll likely get a quicker answer by contacting Emotiva directly... I find it quicker to call them and ask for support as opposed to email....YMMV.
|
|
|
Post by TheTerrorBeyond on Apr 29, 2021 14:44:18 GMT -5
I got a response:
Tony,
Since a Home Theater Processor is really a very complicated PC made to look like a piece of ordinary stereo equipment, sometimes errors crop up during boot sequences (like a PC with a keyboard key stuck down will give a keyboard error for a moment).
You may never see that error again, but if it becomes regular or starts concerning you, please reach back out to us. It could be a partially disconnected HDMI cable on the back or a ROKU device running a FW update during boot that causes the prepro to hiccup, etc..
Hope this helps,
|
|
|
Post by aliensoundtome on Apr 29, 2021 15:02:40 GMT -5
I got this error the first time I updated to firmware 2.2. The only way I could get the XMC-2 to boot was to hold the front panel button for at least 10 seconds. If it did not reset or if it did I still turned off via the power switch in the back for 5 minutes before turning back on. Have not seen error since I did this. Just in case I also factory reset too after it booted up without the error. Had a backup from previous version to restore.
|
|