🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lsi
Article #1030

Re: Posting schematics...

#1030
From: EDIF Committee
Date: Fri, 18 Mar 1988 23:28
54 lines
3435 bytes
In article <920@cfa.cfa.harvard.EDU> ward@cfa.harvard.EDU (Steve Ward) writes:
>
>
>I may be mistaken, but I thought the original idea was to formulate a
>simple, inexpensive, universal way to interchange schematics to the
>great masses awaiting electronic enlightment :-)  It does seem to me
>that there are two ways to go: first, what is admittedly the "right"
>way, which is to say EDIF.  Second, to do something that is readily
>available and affordable to everyone, including basement amatueurs.
>
   WRONG _ EDIF CAN be "simple" for simple tasks, so far most of the 
   implementations have been for "high end" stuff, but I have written a
   100 line program to extract JUST the graphics for a Commodore 64!

   Leaves out A LOT, but its intended to be SIMPLE!

>definition of graphics symbol to plot mapping to be done by the user.
 
 EDIF does NOT define symbols, but there exists an ANSI standard for that
 (I forget the RS number). I.E. EDIF does not say a NAND gate looks like ...

>In other words, EDIF does not provide a specific schematic definition
>If my understanding is correct, then a definition of how to reprsent
>schematics in EDIF with respect to a coordinate system, scale
>information, parts (graphics symbols)  defiintions (presumably vectors)
>etc will have to agreed upon.  If I am wrong, then EDIF provides a full
>graphics description capability as well as circuit topology capability
>and  this particular concern is unfounded.  In any case,  it does leave

 If I understand the question - you are wrong, EDIF provides definition for
 scaling, grids etc. for a complete 2D coordinate system. With a trivial
 extension to the POINT construct it allows N dimensional graphics!

>a lot of software to be generated if the intent is to provide lowly PC
>(and clones), MAC's, and variouus workstation users to interchange
>schematics.  I suppose the two critical pieces of software would be the

  If the data is simple and straightforward the interface should be!
  Be careful that the data may be MUCH more complex than you think though.

>If the idea is really to provide interchange for those using  commercial
>CAE/CAD workstation systems, then NEVER MIND!

   NO WAY!!! THis weeks EDN has an ad for PC AT based PCADS interface, ORCAD,
   and about a dozen other PC/MAC based companaies have translators!
   They are relatively sophisticated, but for the 20 transistor/gate
   one page schematic the amateur usually wants a very simple interface
   should be fine since almost everything is fixed! (library, cell etc.)
   If I get the time I will resurect my simple C 64 one and post it, but
   you might get your interface finished by the time I get it!
   To start: look for "(EDIF", ignore everything looking for "(CELL", look
   for ports, nets etc. the same way. Leves out A LOT, but it works!

Mike Waters EDIF TC
Technical Details
Message-ID: <1654@pasteur.Berkeley.Edu>
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!cad.Berkeley.EDU!moto
References: <915@cfa.cfa.harvard.EDU> <8803112135.AA17866@venera.isi.edu> <3908@cup.portal.com> <920@cfa.cfa.harvard.EDU>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!cad.Berkeley.EDU!moto
From: moto@cad.Berkeley.EDU (EDIF Committee)
Newsgroups: comp.lsi
Subject: Re: Posting schematics...
Message-ID: <1654@pasteur.Berkeley.Edu>
Date: 18 Mar 88 23:28:59 GMT
References: <915@cfa.cfa.harvard.EDU> <8803112135.AA17866@venera.isi.edu> <3908@cup.portal.com> <920@cfa.cfa.harvard.EDU>
Sender: news@pasteur.Berkeley.Edu
Reply-To: moto@cad.Berkeley.EDU.UUCP (EDIF Committee)
Organization: University of California, Berkeley
Lines: 53