RE: PADS Logic Library Editor

242 views

Skip to first unread message

Phillip Restall

unread,

Nov 19, 2008, 4:18:51 AM11/19/08

to Talk Mailing List

Paul

Contact me via my website and I'll give you some code snippets off list to
get you started.

Phillip Restall
http://www.CAD-HQ.com

-----Original Message-----
From: Paul E. Schoen [mailto:pst...@smart.nettalk@listserver.pads.com]
Sent: 18 November 2008 23:05
To: Talk Mailing List
Subject: Re: PADS Logic Library Editor

I am curious about how you were able to do this. For the Parts Definition
files, ".P", the first line is the header (which contains PCB decals,
number of attributes, etc),, and then subsequent lines are attributes, gate
information, etc. Each part has perhaps as many as 50 or more lines of
information, and then there is a blank line between each part definition.
So, it might be possible to put the text in each line into columns in an
Excel sheet, but the columns would have different kinds of information.

It may be just as easy to use a text editor to clean up the ASCII files,
and then import back into the library. But you do need to be careful if you
add or delete attributes, or make other changes, because the header
information must be updated properly, or you may run the risk of trashing
the file. Mostly I want to eliminate unused attributes, change names of
some parts, and make corrections to attributes.

What would really be nice would be the ability to examine the PCB decal for
each part and check the footprint dimensions and pin numbers. Maybe the new
part library manager for PADS will have those features, but it's not worth
the expense for me to upgrade now. Maybe I can make a simple utility to
make library editing a little easier, but it might just not be worth the
effort.

Paul

"$subst ('member.fullname')" <ta...@listserver.pads.com> wrote in message
news:100297@talk...
>I have done this for an old company I worked for.
> It would seamlessly export all the information from every library in the
> library list to excel including attributes, decals alternate decals, CAE
> decals used. I personally used ASCII (.d and .p file) as you cant get all
> the info you need otherwise.
>
> When in excel you could apply filters for example, to see every part a
> certain decal was used on. Most useful.
>
> Phillip Restall
> http://www.CAD-HQ.com
>
> -----Original Message-----
> From: Paul E. Schoen [mailto:pst...@smart.nettalk@listserver.pads.com]
> Sent: 17 November 2008 19:01
> To: Talk Mailing List
> Subject: Re: PADS Logic Library Editor
>
> I have made some progress, but it is tedious to parse the gate, pin, and
> signal details. However, I think the only things that needs to be
> examined
> and edited outside of the PADS editor are the part name(type), PCB
> Decals,
> attributes, and possibly gate decals. I have some different attribute
> names, and they vary from part to part, so the entire file may need to be
> scanned to get all of them as columns, and then rescanned to populate the
> spreadsheet.
>
> I don't have anything newer than PADS2004sp2, although I have access to
> PADS2005sp1 elsewhere. That's where some of my library seems to have
> gotten
> messed up. I think it was in the schematic decal files, where the fancy
> fonts were added.
>
> I'll let you know if I have success in making a useful application to
> examine and edit these fields.
>
> There does not appear to be any way to make a script that can place parts
> from the library onto a schematic, or save them to the library. It seems
> that must be done manually.
>
> Paul
>
> "$subst ('member.fullname')" <ta...@listserver.pads.com> wrote in message
> news:100276@talk...
>> So for someone who does Excel Macros/VB script all the time it seems
>> this
>> should be an easy task. Perhaps 1-2 days work. Even shorter if they
>> already knew the PADS ASCII export format.
>>
>> The big question is how do you support the different library formats
>> from
>> V4 (used from PADS 4.x to 2004) and the many that came after that. Would
>> the script work for newer library formats and older ones?
>>
>> Looking at an export the task seems to be to break apart a part
>> definition and sort it to fields. then from those fields back to the
>> part
>> definitions. Some fields are obvious, some may take more time to
>> understand, but there are not many. Below is an example from an existing
>> library. I tried to understand these from the logic ASCII file but it
>> was
>> not 100% clear for all fields.
>>
>> US_TL072_SOIC-8 SO8-150MIL(M):SO-8 I ANA 11 3 0 0 0 8
>> "MFG" TEXAS INSTRUMENTS
>> "VALUE" TL072
>> "PART DESC" IC, OP AMP-DUAL TL072D SOIC-8
>> "P/N" TL072CDR
>> "BY" RSS 110308
>> "Geometry.Height" 1.75mm
>> "NOPOP"
>> "NOTE"
>> "ROHS" YES
>> "WATT/VOLT/TOL"
>> "PRICE" $0.29
>> G:OPAMP_-UP-MED:OPAMP_+UP-MED:OPAMP_-UP-LARGE:OPAMP_+UP-LARGE 1 3
>> 2.0.U.- 3.0.U.+ 1.0.U.OUT
>> G:OPAMP_-UP-MED:OPAMP_+UP-MED:OPAMP_-UP-LARGE:OPAMP_+UP-LARGE 1 3
>> 6.0.U.- 5.0.U.+ 7.0.U.OUT
>> G:OPAMP_PWR-MED:OPAMP_PWR-LARGE:OPAMP_PWR-SMALL 0 2
>> 8.0.U.VCC+ 4.0.U.VCC-
>>
>>
>> On 11/17/2008 9:08 AM, Hawker wrote:
>>> Hey Paul,
>>>
>>> This all sounds very interesting. And very usefull. I have libraries
>>> from so many odd sources done willy nilly by so many different people.
>>> It would be nice ot be able to say port my libraries from one client to
>>> use for another client, this is why I need this stuff.
>>> Ideally what I want to tweak is not the .L files but the .P files.
>>>
>>> Sorin.s script looks to be the most promising right now once I figure
>>> out a script to dump all parts to the blank schematic page.
>>>
>>> Off the top of my head I see three main issues with Sorins script.
>>> 1) If I understand things correctly, I can't tweak the "Grey" fields
>>> of
>>> which Part type and PCB footprint are part of that. And those fields
>>> are
>>> exactly the ones I need to edit most.
>>> 2)The script does not seem to properly handle when there are multiple
>>> PCB footprints available for the same part type.
>>> 3) The script does not let me change gate names, pin and gate swap
>>> info.
>>>
>>> I'm assuming to tweak this kind of stuff I would have to work on the
>>> exported .P file and not what I have here to work with.
>>>
>>>
>>> On 11/15/2008 2:47 PM, Paul E. Schoen wrote:
>>>> I'm coming into this a little late, but about a year ago I started a
>>>> project to read the ASCII export files of the PADS libraries into a
>>>> database, but I only got so far as the schematic decals (Libname.L). I
>>>> tried to display the actual decal, and ran into problems with the
>>>> graphics. I need to clean up my libraries as well, and it would be
>>>> much
>>>> easier in a spreadsheet format. The ASCII export files are fairly
>>>> simple and well-defined in the documentation, so I think it should be
>>>> relatively easy to generate a tab-delimited file of all part types and
>>>> their attributes, which are contained in the "L" file. Then the
>>>> attributes can be cleaned up and saved back into an "L" file format,
>>>> and imported back into the PADS library.
>>>>
>>>> I am also trying to use Bob Kondner's system of BOMbuilder and P&V. I
>>>> have had some success, but we differ on the details of having vendor
>>>> and manufacturer information in the PADS library as opposed to having
>>>> that only in the external P&V database. I was able to export my parts
>>>> from a design into an Excel spreadsheet, and then import that into
>>>> P&V.
>>>> It would be even better if I could do that with the entire libraries
>>>> that I have built.
>>>>
>>>> If this would be a useful utility, I might spend more time on it and
>>>> offer it to to anyone who can use it. It would be a stand-alone
>>>> utility, and not a script. You would need to export the library from
>>>> PADS Logic, and then import back in.
>>>>
>>>> I'll keep you posted on my progress if I decide to undertake this
>>>> project.
>>>>
>>>> I haven't tried Sorin's script, but it looks like it only works on the
>>>> parts in a schematic design, and not the entire library. I could not
>>>> find any OLE functions that would allow direct access to individual
>>>> attributes, or even to retrieve and save components from/to a library.
>>>> So it looks like it must be done externally.
>>>>
>>>>
>>>>
>>>
>>
>
>
>
> -END-
> SupportNet: http://www.mentor.com/supportnet
> To unsubscribe send a blank email to:
> leave-ta...@listserver.pads.com
> For assistance please send mail to talkli...@mentor.com
>
>
>

-END-
SupportNet: http://www.mentor.com/supportnet
To unsubscribe send a blank email to: leave-ta...@listserver.pads.com
For assistance please send mail to talkli...@mentor.com

Reply all

Reply to author

Forward

0 new messages