Skip to content

Add generic DVI-I and DVI-D connectors

Patrick Baus requested to merge PatrickBaus/kicad-symbols:add_DVI into master

This MR adds two new symbols: DVI-I_Dual_Link and DVI-D_Dual_Link.

I have added a DVI-D (digital only) and DVI-I (integrated analog and digital) connectors to KiCad. I did not bother with neither the DVI-A (analog only) nor the single link connectors since they are practically obsolete nowadays.

Additionally, this MR comes with a new footprint and 3D model for each type of connector.

Footprints: kicad-footprints!3586 (merged)

3D models: kicad-packages3D!990 (merged)

The pin layout image is blatantly stolen from Wikipedia, but that image says it all:

DVI_pinout_no_info

Additionally, I have used the DVI-I Molex 74320-1004 datasheet and DVI-D Molex 74320-4004 datasheet as a reference.

The difference between the DVI-I connector (all pins connected) and the DVI-D connector is that DVI-D does not have the analog pins on the right-hand-side and additionally pin 8 is not connected inside a DVI-D cable, so I did not connect those in the symbol as well.

These are are the two symbols I have crafted based off the HDMI connectors:

DVI-I_Dual_Link

Symbol

DVI-I_symbol

Properties

DVI-I_properties

Pins

DVI-I_pins_1 DVI-I_pins_2

DVI-D_Dual_Link

Symbol

DVI-D_symbol

Properties

DVI-D_properties

Pins

DVI-D_pins

Notes:

The KLC S3.3 violation is a false positive, because the CI KLC check picks the wrong rectangle. It picks one of the DVI connector pins instead of the bounding box.

The footprint filter is set to DVI-I* and DVI-D*. The dash is included because it is part of the name and does not separate any properties.


  • Remove the instructional content of this template
  • Provide a URL to a datasheet for the symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, provide link(s) as appropriate
  • Check the output of the automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.
Edited by Patrick Baus

Merge request reports