Thanks, Patrick and Andy, you guys were right, looking in the text library file I could see the pins were duplicated. For some unexplained reason, however, I could not see that in the library editor. I made that component myself, but I did not make it from scratch, but by taking a former 28-pin component, renaming the pins, and then adding more pins up to a total of 64. After manually deleting the double entries from the library (in text file mode) it now works ok.
Thanks for the help and for the investigative work. Regards, Cristian --- On Tue, 10/20/09, Patrick Maupin <[email protected]> wrote: From: Patrick Maupin <[email protected]> Subject: Re: [kicad-users] Additional attachement: NC pins appear differently in PCBnew To: [email protected] Date: Tuesday, October 20, 2009, 6:47 PM On Tue, Oct 20, 2009 at 12:32 AM, Berceanu Cristian <[email protected]> wrote: > > > > Hi, just for reference, I have archived the project and added it to the Files > of this group. The archive is "test.zip". Just check pins 64 and 2 of the > micro. They are identical, they are marked as NC, but pin 64 is assigned a > N-000047 net name (unique, so it is not connected to any other pins) while > Pin 2 is assigned the "?" net name. I fail to see any reason for this. > > Regards, > Cristian > I have run my ERC script against this file. It reports some real strange stuff. Apparently there are duplicated library pins on your part. There are also other issues that you might be concerned about. I have annotated the generated warnings below with ***** in front of my comments. You can download the Python script from kipy.org and run it yourself. Just look at the readme for details. Checking 1 pages ***** These NoConn warnings are because multiple pins are "connected" at these locations. Warning on page test: Ignoring unexpected NoConn on page test at (6000, 3650) Ignoring unexpected NoConn on page test at (6000, 3750) Ignoring unexpected NoConn on page test at (6000, 3850) Ignoring unexpected NoConn on page test at (10200, 3150) Ignoring unexpected NoConn on page test at (10200, 3250) Ignoring unexpected NoConn on page test at (10200, 3800) Ignoring unexpected NoConn on page test at (10200, 3900) Ignoring unexpected NoConn on page test at (10200, 4000) Ignoring unexpected NoConn on page test at (10200, 4100) Ignoring unexpected NoConn on page test at (10200, 4200) Ignoring unexpected NoConn on page test at (10200, 4300) Ignoring unexpected NoConn on page test at (10200, 4600) Ignoring unexpected NoConn on page test at (10200, 4700) Ignoring unexpected NoConn on page test at (10200, 4800) Ignoring unexpected NoConn on page test at (10200, 4900) Ignoring unexpected NoConn on page test at (10200, 5000) Ignoring unexpected NoConn on page test at (10200, 5100) ***** These are the real problems, I think. Warning: Duplicate pin number Component PIC32MX440F512H_TQFP64 U201 pin 15 (PGEC1/AN1/VREF-/CVREF-/CN3/RB1) on page test at (6000, 5700) Component PIC32MX440F512H_TQFP64 U201 pin 16 (PGED1/EMUD1/PMA6/AN0/VREF+/CVREF+/CN2/RB0) on page test at (6000, 5800) Component PIC32MX440F512H_TQFP64 U201 pin 17 (PGEC2/AN6/OCFA/RB6) on page test at (6000, 5300) Component PIC32MX440F512H_TQFP64 U201 pin 18 (PGED2/AN7/RB7) on page test at (6000, 5200) Component PIC32MX440F512H_TQFP64 U201 pin 19 (AVDD) on page test at (8400, 2650) Component PIC32MX440F512H_TQFP64 U201 pin 20 (AVSS) on page test at (8400, 7350) Component PIC32MX440F512H_TQFP64 U201 pin 21 (U2CTS/C1OUT/AN8/RB8) on page test at (10200, 3550) Component PIC32MX440F512H_TQFP64 U201 pin 22 (PMA7/C2OUT/AN9/RB9) on page test at (10200, 3450) Component PIC32MX440F512H_TQFP64 U201 pin 23 (TMS/CVREFOUT/PMA13/AN10/RB10) on page test at (10200, 3350) Component PIC32MX440F512H_TQFP64 U201 pin 24 (TDO/PMA12/AN11/RB11) on page test at (10200, 3250) Component PIC32MX440F512H_TQFP64 U201 pin 25 (VSS) on page test at (8200, 7350) Component PIC32MX440F512H_TQFP64 U201 pin 26 (VDD) on page test at (8200, 2650) Component PIC32MX440F512H_TQFP64 U201 pin 27 (TCK/PMA11/AN12/RB12) on page test at (10200, 3150) Component PIC32MX440F512H_TQFP64 U201 pin 28 (TDI/PMA10/AN13/RB13) on page test at (10200, 3050) Component PIC32MX440F512H_TQFP64 U201 pin 29 (PMALH/PMA1/U2RTS/BCLK2/AN14/RB14) on page test at (10200, 4500) Component PIC32MX440F512H_TQFP64 U201 pin 30 (PMALL/PMA0/AN15/OCFB/CN12/RB15) on page test at (10200, 4400) Component PIC32MX440F512H_TQFP64 U201 pin 31 (PMA9/U2RX/SDA2/CN17/RF4) on page test at (10200, 6950) Component PIC32MX440F512H_TQFP64 U201 pin 32 (PMA8/U2TX/SCL2/CN18/RF5) on page test at (10200, 6850) Component PIC32MX440F512H_TQFP64 U201 pin 33 (USBID/RF3) on page test at (10200, 6150) Component PIC32MX440F512H_TQFP64 U201 pin 34 (VBUS) on page test at (10200, 6050) Component PIC32MX440F512H_TQFP64 U201 pin 35 (VUSB) on page test at (8600, 2650) Component PIC32MX440F512H_TQFP64 U201 pin 36 (D-/RG3) on page test at (10200, 5750) Component PIC32MX440F512H_TQFP64 U201 pin 37 (D+/RG2) on page test at (10200, 5650) Component PIC32MX440F512H_TQFP64 U201 pin 38 (VDD) on page test at (8000, 2650) Component PIC32MX440F512H_TQFP64 U201 pin 39 (OSC1/CLKI/RC12) on page test at (6000, 6950) Component PIC32MX440F512H_TQFP64 U201 pin 40 (OSC2/CLKO/RC15) on page test at (6000, 6350) Component PIC32MX440F512H_TQFP64 U201 pin 41 (VSS) on page test at (8000, 7350) Component PIC32MX440F512H_TQFP64 U201 pin 42 (IC1/RTCC/INT1/RD8) on page test at (10200, 5200) Component PIC32MX440F512H_TQFP64 U201 pin 43 (IC2/U1CTS//INT2/SDA1/RD9) on page test at (10200, 5100) Component PIC32MX440F512H_TQFP64 U201 pin 44 (IC3/PMCS2/PMA15/INT3/SCL1/RD10) on page test at (10200, 5000) Component PIC32MX440F512H_TQFP64 U201 pin 45 (IC4/PMCS1/PMA14/INT4/RD11) on page test at (10200, 4900) Component PIC32MX440F512H_TQFP64 U201 pin 46 (OC1/INT0/RD0) on page test at (10200, 5300) Component PIC32MX440F512H_TQFP64 U201 pin 47 (SOSCI/CN1/RC13) on page test at (10200, 4800) Component PIC32MX440F512H_TQFP64 U201 pin 48 (SOSCO/T1CK/CN0/RC14) on page test at (10200, 4700) Component PIC32MX440F512H_TQFP64 U201 pin 49 (OC2/U1RTS/BCLK1/RD1) on page test at (10200, 4600) Component PIC32MX440F512H_TQFP64 U201 pin 50 (OC3/U1RX/RD2) on page test at (10200, 6600) Component PIC32MX440F512H_TQFP64 U201 pin 51 (OC4/U1TX/RD3) on page test at (10200, 6500) Component PIC32MX440F512H_TQFP64 U201 pin 52 (PMWR/OC5/IC5/CN13/RD4) on page test at (10200, 4300) Component PIC32MX440F512H_TQFP64 U201 pin 53 (PMRD/CN14/RD5) on page test at (10200, 4200) Component PIC32MX440F512H_TQFP64 U201 pin 54 (CN15/RD6) on page test at (10200, 4100) Component PIC32MX440F512H_TQFP64 U201 pin 55 (CN16/RD7) on page test at (10200, 4000) Component PIC32MX440F512H_TQFP64 U201 pin 56 (VCAP/VDDCORE) on page test at (7600, 2650) Component PIC32MX440F512H_TQFP64 U201 pin 57 (ENVREG) on page test at (6000, 3050) Component PIC32MX440F512H_TQFP64 U201 pin 58 (RF0) on page test at (10200, 3900) Component PIC32MX440F512H_TQFP64 U201 pin 59 (RF1) on page test at (10200, 3800) Component PIC32MX440F512H_TQFP64 U201 pin 60 (PMD0/RE0) on page test at (6000, 3450) Component PIC32MX440F512H_TQFP64 U201 pin 61 (PMD1/RE1) on page test at (6000, 3550) Component PIC32MX440F512H_TQFP64 U201 pin 62 (PMD2/RE2) on page test at (6000, 3650) Component PIC32MX440F512H_TQFP64 U201 pin 63 (PMD3/RE3) on page test at (6000, 3750) Component PIC32MX440F512H_TQFP64 U201 pin 64 (PMD4/RE4) on page test at (6000, 3850) ***** These "Connection dot not used" warnings will probably go away when you fix the previous ones. My script expects a connection dot where two pins meet a wire. Warning: Connection dot not used: Page test at (6000, 3050), Page test at (6000, 3450), Page test at (6000, 3550), Page test at (6000, 5200), Page test at (6000, 5300), Page test at (6000, 5700), Page test at (6000, 5800), Page test at (6000, 6350), Page test at (6000, 6950), Page test at (7600, 2650), Page test at (8000, 2650), Page test at (8000, 7350), Page test at (8200, 2650), Page test at (8200, 7350), Page test at (8400, 2650), Page test at (8400, 7350), Page test at (8600, 2650), Page test at (10200, 3050), Page test at (10200, 3350), Page test at (10200, 3450), Page test at (10200, 3550), Page test at (10200, 4400), Page test at (10200, 4500), Page test at (10200, 5200), Page test at (10200, 5300), Page test at (10200, 5650), Page test at (10200, 5750), Page test at (10200, 6050), Page test at (10200, 6150), Page test at (10200, 6500), Page test at (10200, 6600), Page test at (10200, 6850), Page test at (10200, 6950) ***** The next warning is a style issue that my script reports. Warning: Connection dot used to connect crossed lines: Page test at (8200, 2600) ***** Dangling wires are something I would not like to see on a schematic. Warning: Dangling wire end: Page test at (9450, 1100) ***** It is often indicative of forgetting to hook up something if a global net only appears on a single page. Warning: Global net only used on one page: /CS1, /CS2, /D+, /D_, /LED1, /LED2, /LED3, /LED4, /MISO, /MOSI, /PGC, /PGD, /RST, /RXD1, /RXD2, /SCK, /SCL, /SDA, /TXD1, /TXD2, /UART_CABLE_IN, /USB_CABLE_IN, /VBUSON ***** It is often indicative of a cut and paste error if the same global net appears multiple times on a page. Warning: Multiple connections to global signal on sheet /CS1, /D+, /D_, /LED1, /LED2, /LED3, /LED4, /MISO, /MOSI, /PGC, /PGD, /RST, /RXD1, /RXD2, /SCK, /SCL, /SDA, /TXD1, /TXD2, /UART_CABLE_IN, /USB_CABLE_IN, /VBUSON ***** It is usually an error if you have a named net that only has one pin on it. Warning: Net connects no other pins -- net name ignored Net DEBUG_USBDM, Component FT232R U501 pin 16 (USBDM) on page test at (2600, 5400) Net DEBUG_USBDP, Component FT232R U501 pin 15 (USBDP) on page test at (2600, 5500) ***** The next warnings are internally generated because of the multiple pins with the same name. Fix that and these go away. Warning: Pins on part but not found in netlist U201._badpin_15_0, U201._badpin_16_0, U201._badpin_17_0, U201._badpin_18_0, U201._badpin_19_0, U201._badpin_20_0, U201._badpin_21_0, U201._badpin_22_0, U201._badpin_23_0, U201._badpin_24_0, U201._badpin_25_0, U201._badpin_26_0, U201._badpin_27_0, U201._badpin_28_0, U201._badpin_29_0, U201._badpin_30_0, U201._badpin_31_0, U201._badpin_32_0, U201._badpin_33_0, U201._badpin_34_0, U201._badpin_35_0, U201._badpin_36_0, U201._badpin_37_0, U201._badpin_38_0, U201._badpin_39_0, U201._badpin_40_0, U201._badpin_41_0, U201._badpin_42_0, U201._badpin_43_0, U201._badpin_44_0, U201._badpin_45_0, U201._badpin_46_0, U201._badpin_47_0, U201._badpin_48_0, U201._badpin_49_0, U201._badpin_50_0, U201._badpin_51_0, U201._badpin_52_0, U201._badpin_53_0, U201._badpin_54_0, U201._badpin_55_0, U201._badpin_56_0, U201._badpin_57_0, U201._badpin_58_0, U201._badpin_59_0, U201._badpin_60_0, U201._badpin_61_0, U201._badpin_62_0, U201._badpin_63_0, U201._badpin_64_0 HTH, Pat ------------------------------------ Please read the Kicad FAQ in the group files section before posting your question. Please post your bug reports here. They will be picked up by the creator of Kicad. Please visit http://www.kicadlib.org for details of how to contribute your symbols/modules to the kicad library. For building Kicad from source and other development questions visit the kicad-devel group at http://groups.yahoo.com/group/kicad-develYahoo! Groups Links
