Hi Tim, thanks for your input. Just trying to understand more what's going on here. Sorry for the brain dump.
It's very unlikely that the SYNC pin on these 3 saturn consoles ever got used. Not in this part of the world anyways. These consoles for the most part were used using the pack-in composite video cable. Yet for some reason, the EMI filter is shot on the CSYNC output / pin 1 of the 10 pin mini DIN port. 1 console, ok, 2.. maybe. But 3 in 1 month?
The SCART RGB cable I'm using (to connect to my PVM) is straight through. I confirmed it. It has no extra components in the cable.
Maybe the CSYNC pin was never meant to be used. But for some reason is there. According to the schematics I found for for a VA 0.5 (
http://www.geocities.jp/atx197/Ssmn052S1_10.pdf) going backwards from the output port:
- CSYNC exits out of CN5 / AV out and can be verified on TP4
- if goes through a 100pF EMI filter (EM4)
- following CN5-1 --> it is used as input into CXA1645M via 2.2K resistor but feeds from VIDEO-SYNC (_H34)
- _H34 originates on pin 86 of 315-5690 / FH3006(YAMAHA) / Video Display Processor2
The above is for Model 1. But the 2 I fixed recently were all VA7 model 2. The only major difference is the EM filter marking, but the rest is pretty much the same between the model 1 and model 2 for the CSYNC circuit.
It seems I'm not the only one that discovered this issue only with the model 2 systems. Take a look at what RetroRGB posted:
http://retrorgb.com/saturncompare.html
"I found that the handful of Model 2 units I had produced weird horizontal lines on the screen when using a cable that gets sync from the composite sync pin".
retro_console_accessories has this warning on her CSYNC Sega Saturn SCART cables:
"Some Model 2s have a compromised picture with csync, it isn't all of them or even most of them (per my testing) but it's enough that we have to include this warning. White Japanese Saturns especially suffer from this issue as it seems the majority of them use the problematic circuitry involved."
So why do you suppose that only model 2 are seeing this failure? Why do you suppose no model 1 consoles are seeing this issue? I wish I had a model 1 + 2 so I can fully trace it out.
