I've tried posting this elsewhere, without much help--hoping someone here has successfully resolved a similar issue...
I've had a Onkyo TX-NR708 for a couple years. I ran Audyssey successfully when I first got the receiver. However, I just bought a completely new set of speakers (JBL ES series) and I'm having trouble re-running the Audyssey set-up. My first few attempts failed with Audyssey failing to detect a speaker--but it was not always the same speaker. Sometimes it failed on the FL, sometimes center, sometimes FR.
So I did a full reset on the receiver. Now, when I run Audyssey, only a single chirp will sound for FL (rather than the usual series of chirps), and the system goes silent. Then, a few seconds later, I get the speaker detect error screen. This happens every single time now. I cannot get last that first, single chirp.
I'm getting sound just fine from all speakers, and the test tones in manual set-up play just fine.
I went ahead and ordered a new mic from Onkyo. Interestingly, although I ordered the mic for this specific model, the new mic is black in color (the one the came with my receiver was silver).
However, as I feared, I get the exact same issue--Audyssey quits after a single "chirp" in the left front speaker, and then goes to a speaker detect error screen.
Anyone have any ideas for troubleshooting this?
Hi Andrew, from reading your post it appears you've done all the logical troubleshooting. IMO, the mic is not at fault. If it was you'd likely has odd readings with other speakers, not the same one all the time. At this point you have 2 options: flash/update the receiver's firmware, or send it in for service/repair. Since service/repair will likely involve flashing the firmware again, you might as well give it a try at home. WARNING: flashing or updating the firmware is not a difficult task, but you will lose any/all settings on your receiver and will need to perform a complete setup. Write down any unique settings you have before updating the firmware. After you update the firmware, run Audyssey and see if that solved the problem. If it didn't you'll need to send it in for service.