2
\$\begingroup\$

I made a custom library for a 1x3 header with 5mm pitch on Cadsoft Eagle. Since I had to make the pins in metric, I'm having an issue now connected to the 0.1 inch grid that the rest of my schematic is in.

Picture 1 - It's two pictures combined. Top picture shows the pin and ground, bottom shows that they don't match up "exactly" on the grid.

Picture 1

After scurring around on the web some, I found several posts generic posts saying to just change the grid to a very small size (0.001/0.0001 inch) to make a bunch of connections then throw a Junction over top and it will work out fine. If I do this, then the ERC will have many more errors about overlapping.

Unfortunately, after looking at the ERC Errors, it still says it's not connected.

Picture 2

Notes:

The ground is only so close that the junction is covering so I could get a good close picture. In reality, I would move it to the right more.

I took pictures after saving and restarting Eagle. I know that can be problematic at times also. I'm also using Net's, not wire.

My questions:

  1. Will using a tiny grid and having a Junction still count/pass as a connection when I go to have the PCB made? I know the ERC can be sketchy at times. I have the same issue with Pin 2 but used the grid change/Junction method also.

  2. I made the part library using 5mm to inch conversion, then placed the pins at (-0.19685 0), (0 0), (0.19685 0 ) so they were technically placed on the inches graph. Is changing the grid to 0.19685 then connecting the net's an effective solution?

  3. Is there a proper way to make metric components to fit on the 0.1 inch grid? I know it's a general rule to keep the 0.1 inch grid.

  4. I've read/seen Youtube video's that says to take the ERC with a grain of salt. Should it be taken "seriously"? IE correct all of the errors?

\$\endgroup\$
3
  • 6
    \$\begingroup\$ Always draw the symbol on a 0.1" grid! Just because the footprint is metric doesn't mean the symbol has to be. \$\endgroup\$ Oct 27, 2015 at 14:22
  • \$\begingroup\$ Give the nets names. The PCB will read any wires with the same net name as being connected. \$\endgroup\$
    – DerStrom8
    Oct 27, 2015 at 14:49
  • \$\begingroup\$ @derstrom8, I already did that for the major nets (VCC, Ground, ect). Nice tip though \$\endgroup\$
    – Luke
    Oct 27, 2015 at 15:12

2 Answers 2

5
\$\begingroup\$

Basically for compatibility with everything else, you should always lay the pins on your schematic symbol on a 0.1" grid. Either set the grid in the symbol editor to be 2.54mm or set it to be 0.1".

If you need to make a metric footprint you can do so, use whatever grid you want to in the package editor.

The packages don't appear in the schematic so you don't need to worry about them being on-grid. The symbols don't appear in the layout so you don't need to worry about them not matching the dimensions of the part.

\$\endgroup\$
1
  • \$\begingroup\$ Just as I did for Olin's answer. I thought the schematic symbol had to be in metric also! \$\endgroup\$
    – Luke
    Oct 27, 2015 at 14:30
5
\$\begingroup\$
I made a custom library for a 1x3 header with 5mm pitch on Cadsoft Eagle. Since I had to make the pins in metric, I'm having an issue now connected to the 0.1 inch grid that the rest of my schematic is in.

This makes no sense. The physical pins in the package need to be what the real connector has, but that has no bearing whatsoever on how they must be depicted in the symbol. It is the symbol that appears in your schematic. The package defines the footprint and other properties on the physical board.

Always use .1 inch grid for schematic symbols, since everything in Eagle is standardized on that. Again, this has no bearing at all on what the package looks like or what pitch the physical pins have.

\$\endgroup\$
1
  • \$\begingroup\$ Ah! I thought the symbol had to be in metric also!!! \$\endgroup\$
    – Luke
    Oct 27, 2015 at 14:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.