> Also with the bigger parts they are commonly made with > multiple parts not sure if you can handle that also. > > A check for missing pins or duplicate pins would also > catch some errors.
See, these are thing I should know before I code the Schematic component generator for proper implementation. Other suggestions? ____________ Brian Guralnick [EMAIL PROTECTED] (514) 624-4003 ----- Original Message ----- From: "Darren" <[EMAIL PROTECTED]> To: "'Protel EDA Forum'" <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 9:44 AM Subject: Re: [PEDA] ClientBasic Schematic Library component synthesiser. WAS -> Making of 956 pin SCH component (boring) > Brian, > > That sounds great, I think once the part with all the > pins numbered and labelled (also the pin type in, out > etc) most of the work is done and this is where most > the manual human errors are made. The arranging of the > pins is the easy bit to do by hand. > > Also with the bigger parts they are commonly made with > multiple parts not sure if you can handle that also. > > A check for missing pins or duplicate pins would also > catch some errors. > > Darren Moore > > > -----Original Message----- > > From: Brian Guralnick [mailto:[EMAIL PROTECTED]] > > > > Now, this is a useful / valuable client-script to generate. > > > > OK, here is my planed ClientScript for next week. > > > > 1. The script generator will take in spread sheet pin name & > > data, including multiple pins with using 1 label on the same entry > > line. (Sold separately, a PDF document decrypt hack which > > will recover the pinout tables. I'm not sure why IC data sheets are > > encrypted in the first place.) > > > > 2. It will make a library schematic component in 3 ways: > > a) Pins sorted into an orientation similar to the > > device package. > > b) Pins sorted by pin numbers. > > c) Pins intelligently grouped by pin names. > > The order of the pins in the source spread sheet will not matter. > > > > 3. Generate a report file of all the generated pins for > > cross reference & proof reading. > > > > Comments? Additional things I should add/consider as I > > generate the code? > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * To post a message: mailto:[EMAIL PROTECTED] * * To leave this list visit: * http://www.techservinc.com/protelusers/leave.html * * Contact the list manager: * mailto:[EMAIL PROTECTED] * * Forum Guidelines Rules: * http://www.techservinc.com/protelusers/forumrules.html * * Browse or Search previous postings: * http://www.mail-archive.com/[email protected] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
