|
Post by serafis on Sept 10, 2022 0:23:27 GMT -5
This is the VSX-920K I got working back in Fed 22, thanks to help from this forum, details in my earlier post. The amp has been working fine since then. I've never used headphones on this amp until today. When I did, they worked for about 5 minutes, then the amp powered off in DC Protect mode. After releasing it from Protect Mode, now, if anything is inserted into the headphone socket enough to trigger the detection circuit (even a plastic tube or Q-tip), the amp immediately goes to DC Protect. Apart from this, the amp still works fine. While I seldom use headphones, it would be nice to find a solution to this. The service manual for the VSX-920K is completely wrong, as noted in other posts (e.g. the HDMI board is shown down the side when it's actually across the top). The service manual for the VSX-1020K seems to be more accurate for this amp, and can be found here at manualslib. I've followed the schematics as far as I'm able, but I don't really know what I should be looking for as DC Protect never triggers when used normally with speakers. Supply voltages measure within reasonable limits. I've measured XHPDET (HP detect) on the 'scope as normally high at 3.3V where it enters the Digital Main Assembly, dropping to zero as soon as something is inserted into the headphone socket. I assume what should happen then is that the microprocessor detects this and turns off all the speaker relays and turns on the headphone relay. But instead, it immediately goes to DC Protect. When running normally with no inputs, the speaker terminals measure around -25 to -65mV DC. Not sure what else to check so any help greatly appreciated.
|
|
|
Post by mastertech on Sept 10, 2022 17:43:15 GMT -5
I would be checking the headphone jack itself first. Disconnect the harness or pull that board which ever it is, I am seeing J6 in the manual. Then use your ohm meter and see if any pins show short when plugging something into the jack like your plastic tube. Headphones may show some normal resistance. If either pins 2 or 4 are being partially connected to pins 3 or 1 when something is inserted, it would most likely trigger a protect error.
|
|
|
Post by serafis on Sept 10, 2022 18:46:47 GMT -5
Thanks. No shorts in the socket. Pins 1 & 3 (L/R) aren't shorted to either Pin 2 (GND) or 4 (HPDET), or to each other when something inserted. Pin 2 to Pin 4 shows 1K, which is correct according the schematic.
|
|
|
Post by mastertech on Sept 10, 2022 18:54:21 GMT -5
What manual are you looking at? This is what I am looking at.
|
|
|
Post by serafis on Sept 10, 2022 19:34:45 GMT -5
Ah, sorry... I was looking at the other end of J6 where it joins the main board.
Looking at the same end you're looking at, Pins 2 & 4 (L/R) are not shorted to either Pin 1 (HPDET) or Pin 3 (GND) or to each other; and Pin 1 to Pin 3 shows N/C until something inserted, then 1K as expected.
|
|
|
Post by mastertech on Sept 10, 2022 20:23:47 GMT -5
I am still a little baffled here. When I look at this diagram it tells me you should not have the 3.3v when something is not plugged in and then you should have the 3.3v when something is plugged in. But you say the opposite, and your scope test is also opposite. Now I know yours is a 920 and this is a 1020 diagram so I am not sure what is up here.
|
|
|
Post by mastertech on Sept 10, 2022 20:35:23 GMT -5
Skipping past that for a minute I just noticed R117 and R116, (1w/150 ohm). I am assuming these are to attenuate the signal and I wonder if their value have changed. That could cause a protect. I would check them.
|
|
|
Post by serafis on Sept 10, 2022 20:52:02 GMT -5
Yes, I'm a bit baffled too. From the Headphone Assy schematic, if I'm reading it right, I expected that HPDET to GND with nothing inserted would be 1K (assuming the beads are zero resistance); then when something is inserted it breaks the internal connection to GND, and XHPDET would go high. But the scope shows otherwise, and the socket appears to be doing the exact opposite, and I'm wondering if it is faulty or if I'm misunderstanding something here.
R117 and R116 both read 150 ohms as they should.
|
|
|
Post by mastertech on Sept 10, 2022 21:00:20 GMT -5
I think if it was me, I would try removing the R116 and R117 just to see if it still goes into protect.
I just would not plug in the headphones.
|
|
|
Post by serafis on Sept 10, 2022 21:39:52 GMT -5
I will try that. In the meantime, I desoldered the headphone socket from the board and carefully opened it to check the condition of the internal contacts - all seemed OK. However, what I did find is that, contrary to what the diagram in the manual implies, the connections between XHPDET and GND are in fact normally open, and only close (via the 1K resistor) when something is inserted. So it appears to be operating correctly as measured.
I'm also wondering why the headphones worked fine for around 5-10 minutes before triggering protection, but now protection gets triggered immediately when something is inserted.
|
|
|
Post by serafis on Sept 11, 2022 0:53:21 GMT -5
I disassembled it completely to remove the mainboard, desoldered one end of R116 and R117 and reassembled. With repeated insertion into the headphone socket it only went into Protect once. So I disassembled it again, reconnected R16 and R17 and reassembled. No Protect mode (yet). Since I haven't actually changed anything, I'm not at all confident the problem is solved, but I'll let it run for a while and see how it goes. Thanks for the help so far.
|
|
|
Post by mastertech on Sept 11, 2022 10:58:10 GMT -5
The only other thing I see involved in that circuit is R5305 and R5306. Any change in value of either resistor could trigger a protection.
|
|
|
Post by serafis on Sept 11, 2022 17:17:58 GMT -5
They both measure OK, and since I reassembled it it's working fine. I left it on for an hour or so with headphones connected and it was still OK. Very strange, as I didn't change anything other than disassembling and reassembling the headphone socket (very finicky - lots of internal bits). Anyway, I'll leave it for now on the "if it ain't broke don't fix it" principle, and as I seldom use headphones which are working now for the moment at least. Thanks again for the help.
|
|