What is Pin 9 on a VGA cable?

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

On Thu, 10 Jun 2010 16:46:56 -0400, TVeblen
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

TVeblen wrote:
I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?
Be glad that it is missing.
I blew 5-6 ground traces in an expensive computer.
The vga display had 5 volt without current limit on pin 9,
and the computer had it connected to ground.
As luck would have it, I found the traces,and could re-wire them.
Thee is no known benefit for the presence of pin 9.

On 6/10/2010 5:26 PM, Franc Zabkar wrote:
On Thu, 10 Jun 2010 16:46:56 -0400,
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar

This was correct Franc.

I received my new cable yesterday. I replaced the 6 foot "True 15 pin"
VGA cable that came with the Dell 2007FP monitor with the new 10 foot
"14 pin" VGA cable and booted. There was a momentary screen flicker as
Windows (XP-SP3) loaded, but the desktop came up and all was good.

But - In device manager the monitor was no longer recognized as the
2007FP, but as "Generic Plug & Play Monitor", and the Dell driver was
replaced by a Windows Driver.

This is one of my old secondary computers I use in my office
occasionally, I just needed to move it to a more convenient location, so
I'm thinking I'm not going to bother too much with it.

But I'm wondering if I could re-install the Dell Driver, or if without
receiving the EEPROM data it would not make any difference?

Do I have any pressing reason why I need a "true" 15-pin VGA cable?
It is pretty annoying how hard it is to find one of these in the cable's
specs on Newegg.

TVeblen wrote:
On 6/10/2010 5:26 PM, Franc Zabkar wrote:
On Thu, 10 Jun 2010 16:46:56 -0400,
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar

This was correct Franc.

I received my new cable yesterday. I replaced the 6 foot "True 15 pin"
VGA cable that came with the Dell 2007FP monitor with the new 10 foot
"14 pin" VGA cable and booted. There was a momentary screen flicker as
Windows (XP-SP3) loaded, but the desktop came up and all was good.

But - In device manager the monitor was no longer recognized as the
2007FP, but as "Generic Plug & Play Monitor", and the Dell driver was
replaced by a Windows Driver.

This is one of my old secondary computers I use in my office
occasionally, I just needed to move it to a more convenient location, so
I'm thinking I'm not going to bother too much with it.

But I'm wondering if I could re-install the Dell Driver, or if without
receiving the EEPROM data it would not make any difference?

Do I have any pressing reason why I need a "true" 15-pin VGA cable?
It is pretty annoying how hard it is to find one of these in the cable's
specs on Newegg.


Why not test with Monitor Asset Manager ?

This program claims to access the hardware EEPROM data directly, if available.
(I.e. It won't take a cached copy from somewhere else in the OS.)
If you can see the block of data coming from your monitor, then the
interface is working fine. If nothing comes across, that would be
an entirely different matter. Note that the menu on the left has
entries for direct access and for copies from the registry.

http://www.entechtaiwan.com/util/moninfo.shtm

I have the same problem as you - a monitor with what appears to be a
working EEPROM, yet reported as a generic monitor within Windows.
I installed the 6KB "monitor driver" from NEC for my monitor, and
that is how I work around it. Not every monitor has a monitor driver
package, as some companies feel the Plug and Play method is bulletproof.
The monitor driver package is probably shipped, because of the
color management file included in it, rather than being created
expressly as a means of fixing PNP problems. The color management file
is something that would be useful to a Photoshop user, so the screen
colors match other media devices.

Paul

On Tue, 15 Jun 2010 09:09:35 -0400, TVeblen
put finger to keyboard and composed:

Do I have any pressing reason why I need a "true" 15-pin VGA cable?

I extended my existing 15-pin cable (by adding a KVM box) with a cable
from an old pre-EDID VGA monitor. I used the INF supplied with the
monitor and all is well.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On 6/15/2010 3:47 PM, Paul wrote:
TVeblen wrote:
On 6/10/2010 5:26 PM, Franc Zabkar wrote:
On Thu, 10 Jun 2010 16:46:56 -0400,
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar

This was correct Franc.

I received my new cable yesterday. I replaced the 6 foot "True 15 pin"
VGA cable that came with the Dell 2007FP monitor with the new 10 foot
"14 pin" VGA cable and booted. There was a momentary screen flicker as
Windows (XP-SP3) loaded, but the desktop came up and all was good.

But - In device manager the monitor was no longer recognized as the
2007FP, but as "Generic Plug & Play Monitor", and the Dell driver was
replaced by a Windows Driver.

This is one of my old secondary computers I use in my office
occasionally, I just needed to move it to a more convenient location,
so I'm thinking I'm not going to bother too much with it.

But I'm wondering if I could re-install the Dell Driver, or if without
receiving the EEPROM data it would not make any difference?

Do I have any pressing reason why I need a "true" 15-pin VGA cable?
It is pretty annoying how hard it is to find one of these in the
cable's specs on Newegg.


Why not test with Monitor Asset Manager ?

This program claims to access the hardware EEPROM data directly, if
available.
(I.e. It won't take a cached copy from somewhere else in the OS.)
If you can see the block of data coming from your monitor, then the
interface is working fine. If nothing comes across, that would be
an entirely different matter. Note that the menu on the left has
entries for direct access and for copies from the registry.

http://www.entechtaiwan.com/util/moninfo.shtm

I have the same problem as you - a monitor with what appears to be a
working EEPROM, yet reported as a generic monitor within Windows.
I installed the 6KB "monitor driver" from NEC for my monitor, and
that is how I work around it. Not every monitor has a monitor driver
package, as some companies feel the Plug and Play method is bulletproof.
The monitor driver package is probably shipped, because of the
color management file included in it, rather than being created
expressly as a means of fixing PNP problems. The color management file
is something that would be useful to a Photoshop user, so the screen
colors match other media devices.

Paul

I'll give that utility a go Paul, thanks. It should shed some light.

I find it interesting that the monitor (that had been hooked up to the
subject computer for quite a while) was no longer recognized, as it had
been, just because a new cable was used without pin #9. I'm now
wondering if just Dell uses this "non functioning" pin to transmit an
ID, or do all digital monitors do so?

I will play with it as time permits and post back in case anyone is
interested.

TVeblen wrote:
On 6/15/2010 3:47 PM, Paul wrote:
TVeblen wrote:
On 6/10/2010 5:26 PM, Franc Zabkar wrote:
On Thu, 10 Jun 2010 16:46:56 -0400,
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar

This was correct Franc.

I received my new cable yesterday. I replaced the 6 foot "True 15 pin"
VGA cable that came with the Dell 2007FP monitor with the new 10 foot
"14 pin" VGA cable and booted. There was a momentary screen flicker as
Windows (XP-SP3) loaded, but the desktop came up and all was good.

But - In device manager the monitor was no longer recognized as the
2007FP, but as "Generic Plug & Play Monitor", and the Dell driver was
replaced by a Windows Driver.

This is one of my old secondary computers I use in my office
occasionally, I just needed to move it to a more convenient location,
so I'm thinking I'm not going to bother too much with it.

But I'm wondering if I could re-install the Dell Driver, or if without
receiving the EEPROM data it would not make any difference?

Do I have any pressing reason why I need a "true" 15-pin VGA cable?
It is pretty annoying how hard it is to find one of these in the
cable's specs on Newegg.


Why not test with Monitor Asset Manager ?

This program claims to access the hardware EEPROM data directly, if
available.
(I.e. It won't take a cached copy from somewhere else in the OS.)
If you can see the block of data coming from your monitor, then the
interface is working fine. If nothing comes across, that would be
an entirely different matter. Note that the menu on the left has
entries for direct access and for copies from the registry.

http://www.entechtaiwan.com/util/moninfo.shtm

I have the same problem as you - a monitor with what appears to be a
working EEPROM, yet reported as a generic monitor within Windows.
I installed the 6KB "monitor driver" from NEC for my monitor, and
that is how I work around it. Not every monitor has a monitor driver
package, as some companies feel the Plug and Play method is bulletproof.
The monitor driver package is probably shipped, because of the
color management file included in it, rather than being created
expressly as a means of fixing PNP problems. The color management file
is something that would be useful to a Photoshop user, so the screen
colors match other media devices.

Paul

I'll give that utility a go Paul, thanks. It should shed some light.

I find it interesting that the monitor (that had been hooked up to the
subject computer for quite a while) was no longer recognized, as it had
been, just because a new cable was used without pin #9. I'm now
wondering if just Dell uses this "non functioning" pin to transmit an
ID, or do all digital monitors do so?

I will play with it as time permits and post back in case anyone is
interested.

As Franc explained, Pin 9 is a (redundant) power source.

The monitor has its own power source, and can use that to deliver 5V
to the EEPROM inside the monitor. The intention of pin 9, was to cover
cases where the monitor was turned off, and had no internal power. If
pin 9 existed on the cable, then power could come from the computer.

My first VGA cable, had pin 9 removed, so someone must have known that
it isn't a good idea to ship power on data cables like that.

All that the missing pin 9 should do, is prevent the computer from
reading the monitor, when the monitor is completely without power. If
the monitor is sitting in standby (monitor LED indicates "no signal"),
there should still be power flowing to the EEPROM, and the serial clock
and data should be working at that point. Missing the pin 9 thing
should not prevent it from working. I leave my monitor in standby all
the time, and the monitor lights up the backlight, as soon as
the computer starts, and there is a signal on the VGA cable
on the R-G-B-H-V lines.

If the monitor had protection internally on its +5V, and a fuse or
something had opened up, that might be a reason you suddenly have
a dependence on pin 9 as a source of power. (That would imply that
the monitor's internal power source, is no longer connected to
the EEPROM.) You'd have to check with the manufacturer, to see
if there was protection on it. That's the only thing I can think
of, to account for your symptoms. Normally, the power sources
would be wired-OR, and either one power source or the other, would
power the EEPROM. For unregulated power rails, you can use
simple diodes, to isolate the potential power sources, and
select the power source with the highest voltage.

--
Pin 9 ---------------- diode -----+
|
Internal Power ------- diode -----+----- +5 EEPROM
-- | |
I2C clk data
| |
| |
to_video_card

Paul

On 6/15/2010 10:29 PM, Paul wrote:
TVeblen wrote:
On 6/15/2010 3:47 PM, Paul wrote:
TVeblen wrote:
On 6/10/2010 5:26 PM, Franc Zabkar wrote:
On Thu, 10 Jun 2010 16:46:56 -0400,
put finger to keyboard and composed:

I see a lot of VGA cables being sold on Newegg that do not have
all 15
pins. It looks like Pin 9 is missing. Wikipedia says that Pin 9 is
KEY/PWR (+5V). I don't know what that means.

Does it make any difference whether you have all 15 pins or not?

Pin 9 powers the EDID EEPROM chip in the monitor. If the EDID cannot
be read, then PnP won't be able to determine the monitor's specs. If
the EEPROM is powered by the monitor, then pin 9 may not be necessary.
I'm not certain, though. What is certain, however, is that you will
need pins 12 and 15 (data and clock) for PnP. If these are absent,
then you will still be able to use the monitor, but you will need to
set it up manually with the correct INF file.

http://en.wikipedia.org/wiki/Extende...ification_data

http://pinouts.ru/Video/VGA15_pinout.shtml

- Franc Zabkar

This was correct Franc.

I received my new cable yesterday. I replaced the 6 foot "True 15 pin"
VGA cable that came with the Dell 2007FP monitor with the new 10 foot
"14 pin" VGA cable and booted. There was a momentary screen flicker as
Windows (XP-SP3) loaded, but the desktop came up and all was good.

But - In device manager the monitor was no longer recognized as the
2007FP, but as "Generic Plug & Play Monitor", and the Dell driver was
replaced by a Windows Driver.

This is one of my old secondary computers I use in my office
occasionally, I just needed to move it to a more convenient location,
so I'm thinking I'm not going to bother too much with it.

But I'm wondering if I could re-install the Dell Driver, or if without
receiving the EEPROM data it would not make any difference?

Do I have any pressing reason why I need a "true" 15-pin VGA cable?
It is pretty annoying how hard it is to find one of these in the
cable's specs on Newegg.


Why not test with Monitor Asset Manager ?

This program claims to access the hardware EEPROM data directly, if
available.
(I.e. It won't take a cached copy from somewhere else in the OS.)
If you can see the block of data coming from your monitor, then the
interface is working fine. If nothing comes across, that would be
an entirely different matter. Note that the menu on the left has
entries for direct access and for copies from the registry.

http://www.entechtaiwan.com/util/moninfo.shtm

I have the same problem as you - a monitor with what appears to be a
working EEPROM, yet reported as a generic monitor within Windows.
I installed the 6KB "monitor driver" from NEC for my monitor, and
that is how I work around it. Not every monitor has a monitor driver
package, as some companies feel the Plug and Play method is bulletproof.
The monitor driver package is probably shipped, because of the
color management file included in it, rather than being created
expressly as a means of fixing PNP problems. The color management file
is something that would be useful to a Photoshop user, so the screen
colors match other media devices.

Paul

I'll give that utility a go Paul, thanks. It should shed some light.

I find it interesting that the monitor (that had been hooked up to the
subject computer for quite a while) was no longer recognized, as it
had been, just because a new cable was used without pin #9. I'm now
wondering if just Dell uses this "non functioning" pin to transmit an
ID, or do all digital monitors do so?

I will play with it as time permits and post back in case anyone is
interested.

As Franc explained, Pin 9 is a (redundant) power source.

The monitor has its own power source, and can use that to deliver 5V
to the EEPROM inside the monitor. The intention of pin 9, was to cover
cases where the monitor was turned off, and had no internal power. If
pin 9 existed on the cable, then power could come from the computer.

My first VGA cable, had pin 9 removed, so someone must have known that
it isn't a good idea to ship power on data cables like that.

All that the missing pin 9 should do, is prevent the computer from
reading the monitor, when the monitor is completely without power. If
the monitor is sitting in standby (monitor LED indicates "no signal"),
there should still be power flowing to the EEPROM, and the serial clock
and data should be working at that point. Missing the pin 9 thing
should not prevent it from working. I leave my monitor in standby all
the time, and the monitor lights up the backlight, as soon as
the computer starts, and there is a signal on the VGA cable
on the R-G-B-H-V lines.

If the monitor had protection internally on its +5V, and a fuse or
something had opened up, that might be a reason you suddenly have
a dependence on pin 9 as a source of power. (That would imply that
the monitor's internal power source, is no longer connected to
the EEPROM.) You'd have to check with the manufacturer, to see
if there was protection on it. That's the only thing I can think
of, to account for your symptoms. Normally, the power sources
would be wired-OR, and either one power source or the other, would
power the EEPROM. For unregulated power rails, you can use
simple diodes, to isolate the potential power sources, and
select the power source with the highest voltage.

--
Pin 9 ---------------- diode -----+
|
Internal Power ------- diode -----+----- +5 EEPROM
-- | |
I2C clk data
| |
| |
to_video_card

Paul

Today I attempted to install the INF file "driver" from the monitor's
CD. No go. (Monitor properties Driver Update Driver). "Windows
cannot update this driver".

So if pin 9 has nothing to do with the symptom (monitor no longer
recognized as 2007FP after replacing the VGA cable when it was before),
does that mean that the cable is potentially defective?

Next step with be that monitor utility.

I had been struggling to find a way to get both my 1920x1080 LG monitors
to work correctly (they are different models, m237wd and w2353VP) on my
win xp pro 32 bit system. After much effort, I finally have it working.
Here's my story in case it helps someone else.

One monitor, is attached to my intel MB g965 internal graphics and it
would work fine with any cable I used, 15 or 14 pin. This interface also
worked fine with either monitor.

The other monitor, is attached to a Radeon 7000 and at 1920x1080 it
would go into *-panning mode -*(monitor saying it's actually set to
1280x1024 and it would pan as I moved the mouse on the screen). I could
get to 1600x1200 w/o the panning but I still wanted the monitor's native
resolution w/o the panning.

I thought my card didn't have enough memory (32mb) so I bought a (now
cheap) radeon 9200 but it had the same problem and was visibly slower.
So, I returned to the 7000.

Finally, it turned out the cable from the Radeon 7000 had all 15 pins
which apparently caused the panning problem. I switched to a cable with
only 14 pins, pin 9 missing, and it worked at full resolution.

However, along the way I also had manually loaded the drivers (a .ICM
file is all that shows up when you request driver details). I'm not sure
where it got all the drivers from, but when I choose manual update
driver and unchecked show compatible hardware, I was able to find my LG
monitor model in the very large set of manufactures and model numbers.

Before that, the monitor had said either default monitor or plug and
play. Now, it correctly notes the monitor type and which interface it's
on.

I'm still confused as to why using all 15 pins causes it to not work at
full monitor resolution, but now that it works, I'm done fixing it, so I
don't know if pin 9 is really the problem or a combination of pin 9 and
the monitor driver files. But there's something about that 15 pin cable
and my Radeon interface that it doesn't like.