Michael,
        Your paragraph below still seems to indicate to me that you have 
components off in the negative quadrants of the database. When you make the 
library and it has the parts that you can't find then it is highly likely that 
they are off the visible quadrant. At least as long as there are no other 
copies of the same footprint that are in the positive/visible visible.

        You are aware also that the update will not typically replace 
footprints with different pin counts. Sounds like you may have some of that 
going on because of your comment about the macros that won't execute. You can 
delete the old part and replace it with the new part through an update but 
usually update won't replace parts with dissimilar pin counts.

        Dennis' comments about doing the old fashion remove all nets, then 
update using the netlist format is also a good operation to try.

Sincerely,
Brad Velander
Senior PCB Designer
Northern Airborne Technology
#14 - 1925 Kirschner Road,
Kelowna, BC, V1Y 4N7.
tel (250) 763-2329 ext. 225
fax (250) 762-3374



-----Original Message-----
From: Robison, Michael R NAVSEA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 6:27 AM
To: Protel EDA Discussion List
Subject: RE: [PEDA] Components not transferring to PCB



>From the PCB, I generated a footprint library and it has all the footprints 
(including the ones that are not visible on the PCB).  I'm thinking about moving
my files to another computer and see if the problem follows, using that to 
isolate between problems with the Protel application itself and my DDB files.

Thanks again, Michael

 


____________________________________________________________
You are subscribed to the PEDA discussion forum

To Post messages:
mailto:[email protected]

Unsubscribe and Other Options:
http://techservinc.com/mailman/listinfo/peda_techservinc.com

Browse or Search Old Archives (2001-2004):
http://www.mail-archive.com/[email protected]

Browse or Search Current Archives (2004-Current):
http://www.mail-archive.com/[email protected]

Reply via email to