![enter image description here][1]
![enter image description here][2]
[1]: /editor/20151128/565936b9d9057.png
[2]: /editor/20151128/565937398ada8.png
Can you see these 2 images?
Ken
If you read my link, you may know how to fix this error.
The U5's symbol pad number is VDD VSS SCL SDA, but your package's pad number is 1 2 3 4.
You can change the package's pad number to VDD, VSS SCL SDA or change the symbol's pin number
@Reefhermit,
Symbol and Package (and spice pin!) pin numbering can take a bit of getting used to.
:)
The problem is that your PCB package pads are numbered (or named) differently from the pin numbers (or names) of the Schematic symbol that is calling up the package.
If you either change the pin identification applied to the symbol in the schematic or the pin identification applied to the package footprint in the PCB then the error will clear.
Note that changing either set of identifiers will change only the symbol or footprint instance that you have changed. It will not affect any others or the source symbols or packages in the library.
One way to deal with the pin ident problem is when you create any schematic, if you also create dedicated symbols for each unique part that you use and you also create PCB footprints with the same or derived names. Then you never have the problem of mismatched pin idents.
It sounds like a lot of extra work but in the long run it can save a lot of trouble, especially if you have parts you use in other designs.
There are some examples of this such as the BC547 and BC557 in:
https://easyeda.com/editor#id=qoiASa4mE
or the BC557B and associated BC557_TO92_TRIPOD footprint in:
https://easyeda.com/editor#id=FxrlDVP7p
(For future reference: your spice pin numbering has to be numbered and not named.
For more see the link I posted earlier:
https://easyeda.com/Doc/Simulation-eBook/Schematic-symbols-prefixes-and-pin-numbers.htm#Schematicsymbols:prefixesandpinnumbers)
:)
Our website uses essential cookies to help us ensure that it is working as expected, and uses optional analytics cookies to offer you a better browsing experience. To find out more, read our Cookie Notice